Discussions for oneM2M Semantics Standardization Group Name: WG5 Source: InterDigital Communications Meeting Date: Agenda Item: WI-0005 ASN/MN-CSE instantiation

oneM2M-XXX-2013-XXXX Part I Part I will contain the actual points to be contained in the way forward by the end of the meeting Part II is a grab-bag of material to consider, including past way forward proposals or items for clarification. The goal is to transform this input into AI and eliminate the section This document is meant as a whiteboard for focusing discussions on actionable items. Until agreed it is a skeleton for gathering inputs, and clearly incomplete Goal is to capture AIs and items with various horizons. The following “categories” are proposed to start with but can be modified: – To do for next 1-2 meetings (T1) – To do for release 1 (T2) – Ongoing, immediate start (O1) – Long term (LT) Some participants may volunteer for AI, coordination may avoid effort duplication. However, commitments are not binding and providing alternative or additional inputs is in no way discouraged 2

oneM2M-XXX-2013-XXXX Open issues/Action Items (1) 3 High level model Continue discussion on high level views as provided by NEC/ MAS R01 and Modacom/ MAS (slides at end). (-> ??) InterDigital can provide additional input on a generic and high level ontology model based on TP#9 discussions (->??) Definitions and relationships: (-> TP#10?) – e.g. Physical entity, Virtual entity, Physical world, Domain Models, Information models, Knowledge models (Ontologies) – To be started offline over so that at least the definitions could be used similarly in TP#10 contributions Study of methods and technologies from semantics web, and how it is applicable to oneM2M system (IDCC AI from TP#9, study will be based on current semantics use cases) Create Recommendation Section (-> Rel. 1) Input draft

oneM2M-XXX-2013-XXXX Open issues/Action Items (2) Device templates – Elaborate and agree on the oneM2M view (responsibilities...) on Device Information Model – Manufacturer, Domain stakeholder, Cross-Domain stakeholder – Contact PT2 – Work with ARC – Create a standard reporting by Manufacturers/SDO? Device Information Model – “musts” for syntactic interoperability – “Shoulds “ semantic info for semantic interoperability and for describing context) Toy Device Information Model, mapping to oneM2M resources Device Classification? 4 Input draft

oneM2M-XXX-2013-XXXX Open issues/Action Items (3) To be discussed/filled 5

oneM2M-XXX-2013-XXXX Background (part II) The next slides contain a variety of points or concepts discussed in the last few meetings. They have been collected here to make sure that we consider all of them in our way forward. Ideally, each of these points would be addressed such that they either: A.Map to an action item for the way forward as either 1.AI for immediate next steps/ release 1 2.AI for future next steps/future releases B.Would be agreed to not be carried over into future items as they are either: 1.accomplished, have been 2.merged into other items, 3.No longer relevant Please bring everything you consider an A item into Part I (re-formulate if needed) Not everything needs to follow this pattern, we can just add points to Part I 6 From here on for initial consideration only

oneM2M-XXX-2013-XXXX Discussions from MAS #1 Utilize existing modelling languages #2: Need to find solutions (e.g., ontologies) to support new concepts and different scopes, information models in oneM2M from existing standards and extension of them #3 Need to standardize new ontologies due to different scope #4 Semantics support on top of abstraction for oneM2M resources through semantic annotation 7

oneM2M-XXX-2013-XXXX Priorities from MAS st Specific requirements – Only high-level requirements in TS-0002 (A separate proposal on ontology requirements) 2 nd Ontologies (SMR – 1, 2) – A common vocabulary and knowledge model for oneM2M resources and information models 3 rd Semantic annotation (SMR – 1, 2) – Rules for adding meanings to oneM2M resources considering ontologies 4 th Reasoning (inference) and semantic mash-up (SMR – 4, 6, 7) – Semantic query & response and create a new resource through mash-up Semantic interoperability as common considerations (SMR – 3, 5)

oneM2M-XXX-2013-XXXX Way forward from MAS (I) Elaborate and agree on the oneM2M view (responsibilities...) on Device Information Model – Manufacturer, Domain stakeholder, Cross-Domain stakeholder Check what parameters, from oneM2M point of view: – must be contained in the Device Information Model (required for syntactic interoperability) – should additionally be contained in the Device Information Model (semantic information for semantic interoperability and for describing context) 9

oneM2M-XXX-2013-XXXX Way forward from MAS (II) Create an example (toy Device Information Model) and show the mapping into oneM2M resources Send all of that to other SDOs such that these SDOs can create the Device Template. 10

oneM2M-XXX-2013-XXXX 11

CSE Who contributes to the Device Information Model Page 12 Domain specific Manufacturer AE Context specific Manufacturer defines (at least) Syntactic Device model  Input- Output operations  Enables creation of (oneM2M) representations - resources  syntactic interoperability  Manufacture specific data Domain stakeholder (e.g. HGI) defines domain specific Semantic Device model  Generic naming of device types operation types …  Abstract devices  semantic interoperability Cross-domain stakeholders may define context specific extensions Location information  Relationships to things  Usage for Virtual Devices  Enables linking device types to the context they are used in