Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
S SDT
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 16
    • Issues 16
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • MAS
  • SDT
  • Issues
  • #6

Closed
Open
Created May 23, 2018 by Yongjing Zhang@yongjingMaintainer

Introducing Concept of ‘Product’

Rationale:

-In real life of device manufacturing, there is an important concept of ‘Product’ (or Product Model/Type) for each specific type of devices. E.g. Huawei FIT vs Huawei Watch 2

-A ‘Product’ is NOT the ‘Device Model’ as defined in TS-0023, which is too generic and can be mapped to different vendors’ implementations, NOR a device instance of that ‘device model’ with an instantiated id, date of manufacturing, and the firmware/software version, etc. It can be ‘ordered’ by the customers, but not necessarily instantiated/manufactured.

-A ‘Product’ is a specialized model/type of ‘Device Model’ that has a specific/deterministic implementation - meaning selected Properties/Actions/Events among the optionals, and partially populated values of the properties like the manufacturer id, type, memory size, etc.

-A ‘Product’ may also extend the standardized ‘Device Model’ with additional ‘Modules’.

Suggestion: to introduce the concept of ‘Product’ in SDT4.0

-One (not oneM2M) can use SDT4.0 to specify its own ‘Product Models’ which are specialized from oneM2M ‘Device Models’, use it to generate oneM2M compatible resource mapping in an automated way, and exchange the ‘Product Models’ with business partners.

MAS-2018-0051R01-SDT_4_0_ehancement_discussion.PPT

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking