6.3 Semantics Requirements
6.3.1 Ontology Related Requirements
Table 3: Ontology Requirements
| Requirement ID | Description | Release |
|---|---|---|
| ONT-001 See REQ-2015-0521R01 |
The M2M System shall support a standardized format for the rules/policies used to define service logic. | Not implemented |
| ONT-002 See REQ-2015-0521R01 |
The M2M System shall support modelling semantic descriptions of Things (including relationships among them) by using ontologies. | Implemented in Rel-2 |
| ONT-003 See REQ-2015-0521R01 |
The M2M System shall support a common modelling language for ontologies (e.g. OWL). | Implemented in Rel-2 |
| ONT-004 See REQ-2015-0521R01 |
The M2M System should be able to provide translation capabilities from different modelling languages for ontologies to the language adopted by oneM2M if the expressiveness of the imported ontology allows. | Not implemented |
| ONT-005 See REQ-2015-0521R01 |
The M2M System shall provide the capability to retrieve semantic descriptions and ontologies stored outside of the M2M System. | Not implemented |
| ONT-006 See REQ-2015-0521R01 |
The M2M System shall provide support for linking ontologies defined in the context of the M2M System with ontologies defined outside this context. | Not implemented |
| ONT-007 See REQ-2015-0521R01 |
The M2M System shall be able to support extending ontologies in the M2M System. | Not implemented |
| ONT-008 See REQ-2015-0521R01 |
The M2M System shall be able to use ontologies that contain concepts representing aspects (e.g. a room) that are not represented by resources of the M2M System. | Implemented in Rel-2 |
| ONT-009 See REQ-2015-0521R01 |
The M2M System shall be able to re-use common ontologies (e.g. location, time ontologies, etc.) which are commonly used in M2M Applications. | Not implemented |
| ONT-010 See REQ-2015-0521R01 |
The M2M System shall be able to support simultaneous usage of multiple ontologies for the same M2M resource. | Implemented in Rel-2 |
| ONT-011 See REQ-2015-0521R01 |
The M2M System shall provide the capability for making ontology available in the M2M System, e.g. through announcement. | Not implemented |
| ONT-012 See REQ-2015-0521R01 |
The M2M System shall be able to support mechanisms to import external ontologies into the M2M System. | Not implemented |
| ONT-013 See REQ-2015-0521R01 |
The M2M System shall be able to support update of ontologies. | Not implemented |
| ONT-014 See REQ-2015-0521R01 |
The M2M System shall enable functions for data conversion based on ontologies. | Not implemented |
| ONT-015 See REQ-2015-0521R01 |
The M2M System shall be able to model devices based on ontologies which may be available outside the M2M System (e.g. HGI device template). | Implemented in Rel-2 |
| ONT-016 See REQ-2015-0521R01 |
The M2M System shall support storage, management and discovery of ontologies. | Not implemented |
| ONT-017 See REQ-2015-0609 |
The oneM2M System shall support a semantic relation ("Is Paired To") between two M2M Devices. | Not implemented |
| ONT-018 See REQ-2018-0057R01 |
The oneM2M system shall support semantic query and discovery across heterogeneous ontologies including support of automatic ontology mapping and semantic reasoning. | 4 |
| ONT-019 REQ-2018-0058R01 |
The oneM2M system shall be able to support semantic control of devices with support of addtional capabilities e.g. automatic ontology mapping and semantic reasoning. | 4 |
| ONT-020 See REQ-2018-0049R03 |
The oneM2M system shall be able to detect ontology's mapping conflicts and repair them. |
Not implemented |
| ONT-021 See RDM-2019-0093 |
The oneM2M System shall be able to provide machine understandable semantic information for object identifiers to map the identified objects to corresponding classes in the IoT ontology and enable objects to identify what the interactive object is independently. | 5 |
6.3.2 Semantics Annotation Requirements
Table 4: Semantics Annotation Requirements
| Requirement ID | Description | Release |
|---|---|---|
| ANN-001 See REQ-2015-0521R01 |
The oneM2M System shall provide capabilities to manage semantic information about the oneM2M resources, e.g. create, retrieve, update, delete, associate/link. | Implemented in Rel-2 |
| ANN-002 See REQ-2015-0521R01 |
The oneM2M System shall support a common language for semantic description, e.g. RDF. | Implemented in Rel-2 |
| ANN-003 See REQ-2015-0521R01 |
The oneM2M System shall support semantic annotation of oneM2M resources for example application related data contained in containers. | Implemented in Rel-2 |
| ANN-004 See REQ-2015-0521R01 |
The oneM2M System shall support semantic annotation based on related ontologies. | Implemented in Rel-2 |
| ANN-005 See REQ-2015-0521R01 |
The oneM2M System shall provide the capability for making semantic descriptions available in the M2M System, e.g. announcement. | Implemented in Rel-2 |
| ANN-006 See REQ-2015-0521R01 |
The oneM2M System shall enable applications to retrieve an ontology representation related to semantic information used in the M2M System. | Not implemented |
| ANN-007 See REQ-2015-0521R01 |
The oneM2M system shall provide capabilities to manage data quality descriptions of resource. | Not implemented |
6.3.3 Semantics Query Requirements
Table 5: Semantics Query Requirements
| Requirement ID | Description | Release |
|---|---|---|
| QRY-001 See REQ-2015-0521R01 |
The oneM2M System shall provide capabilities to discover M2M Resources based on semantic descriptions. | Implemented in Rel-2 |
6.3.4 Semantics Mashup Requirements
Table 6: Semantics Mashup Requirements
| Requirement ID | Description | Release |
|---|---|---|
| MSH-001 See REQ-2015-0521R01 |
The oneM2M System shall provide the capability to host processing functions for mash-up. | Not implemented |
| MSH-002 See REQ-2015-0521R01 |
The oneM2M System shall enable M2M Applications to provide processing functions for mash-up. | Not implemented |
| MSH-003 See REQ-2015-0521R01 |
The oneM2M System itself may provide pre-provisioned or dynamically created processing functions for mash-up. | Not implemented |
| MSH-004 See REQ-2015-0521R01 |
The oneM2M System shall be able to create and execute mash-ups based on processing functions. | Not implemented |
| MSH-005 See REQ-2015-0521R01 |
The oneM2M System shall be able to expose mash-ups as resources e.g. virtual devices. | Not implemented |
6.3.5 Semantics Reasoning Requirements
Table 7: Semantics Reasoning Requirements
| Requirement ID | Description | Release |
|---|---|---|
| RES-001 See REQ-2015-0521R01 |
The oneM2M System shall be able to update ontologies as a result of the ontology reasoning. | Not implemented |
| RES-002 See REQ-2015-0521R01 |
The oneM2M System shall be able to support semantic reasoning e.g. ontology reasoning or semantic rule-based reasoning. | Not implemented |
| RES-003 See REQ-2015-0521R01 |
The oneM2M System shall be able to support adding and updating semantic information based on semantic reasoning. | Not implemented |
6.3.6 Data Analytics Requirements
Table 8: Data Analytics Requirements
| Requirement ID | Description | Release |
|---|---|---|
| ANA-001 See REQ-2015-0521R01 |
The oneM2M System shall be able to support capabilities (e.g. processing function) for performing M2M data analytics based on semantic descriptions from M2M Applications and /or from the M2M System. | Not implemented |
| ANA-002 See REQ-2015-0521R01 |
The oneM2M System shall provide the capability of interpreting and applying service logic (e.g. rules/policies of triggering operations upon other resources or attributes according to the change of the monitored resource) described with semantic annotation and ontology. | Not implemented |
| ANA-003 See REQ-2015-0521R01 |
The oneM2M System shall support a standardized format for the rules/policies used to define service logic. | Not implemented |
6.3.7 Domain specific requirements
Table 9: Smart Lift Requirements
| Requirement ID | Description | Release |
|---|---|---|
| SLS-001 | oneM2M shall support Smart Lift data model and its possible evolution, e.g. as identified in [i.4] and [i.5]. | R4 |
NOTE1: No specific additional new feature is currently identified in oneM2M to support the Smart Lifts. The oneM2M system supports properly the Smart Lift domain. It remains necessary to include the data structure to be exchanged by Smart Lifts in the oneM2M semantic work. As it is also deemed to be included in the ETSI SAREF package to assure proper semantic interoperability with other systems.
6.3.8 Advanced Semantic Discovery Requirements
Table 9-bis: Advanced Semantic Discovery Requirements
| Requirement ID | Description | Release |
|---|---|---|
| ASD-001 See RDM-2020-0063 |
The oneM2M system shall provide mechanisms for Advanced Semantic Discovery (ASD) across a distributed network of IoT nodes within a single oneM2M Service Provider and across different IoT Service Providers. | Rel-5 |
| ASD-002 See RDM-2020-0063 |
A CSE receiving an Advanced Semantic Discovery Query (ASDQ) shall extract the Semantic Discovery Query (SDQ), embedded in the packet payload, and shall resolve the query with respect to the locally available information and shall forward to other suitable CSEs the Advanced Semantic Discovery Query (ASDQ) to complete the discovery. | Rel-5 |
| ASD-003 See REQ-2015-0521R01 |
To support Advanced Semantic Discovery the oneM2M system shall provide: An Advanced Semantic Discovery Query Language (ASDQL) that the ability to write Advanced Semantic Discovery Query (ASDQ); A Semantic Discovery Agreement (SDA) to state some communication agreements between CSE; A Semantic Query Resolution (SQR) that allows to locally translate an Advanced Semantic Discovery Query (ASDQ) into some elementary oneM2M Semantic Discovery Queries (SDQ); A Semantic Discovery Routing (SDR) to route an Advanced Semantic Discovery Query (ASDQ) between different CSEs. |
Rel-5 |
| ASD-004 See RDM-2020-0063 |
The oneM2M system shall integrate already standardized ontology extensions to the current oneM2M ontology to cope with new specific domains (ex: SAREF core and its extensions SAREF4BLDG, SAREF4ENVI, SAREF4ENERGY, SAREF4CITY, SAREF4AGRI, SAREF4WATER). | Rel-5 |
| ASD-005 See RDM-2020-0063 |
Based on semantic information, the oneM2M system shall take routing decisions for forwarding a received Advanced Semantic Discovery Query (ASDQ). The semantic information will allow the oneM2M system to maximize and to accelerate the semantic discovery process. | Rel-5 |
| ASD-006 See RDM-2020-0063 |
Advanced Semantic Discovery shall support queries written with specific domain ontologies, e.g. SAREF. | Rel-5 |
| ASD-007 See RDM-2020-0063 |
Advanced Semantic Discovery shall support semantic reasoning between the baseline oneM2M ontology and the identified domain specific ontologies, e.g. SAREF. As example, if a query is looking for a oneM2M device observing Celsius temperature, then the Advanced Semantic Discovery would potentially return a SAREF temperature sensor | Rel-5 |
| ASD-008 See RDM-2020-0063 |
Advanced Semantic Discovery shall provide capabilities to identify multiple set of targets, and a multiplicity of searches (e.g. by setting parameters or filters). | Rel-5 |
| ASD-009 See RDM-2020-0063 |
The oneM2M Access Control Policy shall include discovery permissions to support Advanced Semantic Discovery. When an Advanced Semantic Discovery is performed by the oneM2M System, it shall operate according to the indications associated with the desired information. | Rel-5 |
| ASD-010 See RDM-2020-0063 |
Advanced Semantic Discovery shall prioritize queries, e.g. to ensure a quick response to urgent situations. | Rel-5 |
| ASD-011 See RDM-2020-0063 |
Advanced Semantic Discovery shall minimize complexity to avoid impacting negatively the oneM2M system performance. | Rel-5 |
NOTE 1: These requirement are derived from the Advances Semantic Discovery studies in [i.4] and [i.6].
NOTE2: The solution would be based an evolution of the current oneM2M architecture and functionality and would reuse existing standard ontology mechanisms e.g. considering the SAREF standard developed in ETSI TC SmartM2M (which is also aligned with the W3C ontology approach). This intends to assure also a smooth interworking with relevant non-oneM2M solutions.
NOTE3: The solution would be complete and will be a part of the oneM2M core functions, to avoid the need of ad hoc applications designed to expand the oneM2M functionality with the risk of being implemented with different flavours.