ETSI - TR 103 717
SmartM2M; Study for oneM2M; Discovery and Query specification development
| Organization: | ETSI |
| Publication Date: | 1 July 2021 |
| Status: | active |
| Page Count: | 39 |
scope:
Context for the present document
In order to enhance the semantic capabilities of the oneM2M architecture by providing solid contributions to the oneM2M standards, four Technical Reports have been developed. Each of them is the outcome of a special study phase.
The study and development of Semantic Discovery and Query capabilities for oneM2M and its contribution to the oneM2M standard is composed of four phases:
1) A requirements phase where requirements and use cases are formally identified and defined. As a minimum, this work includes discovery of specific information and of aggregated information, and interaction with external sources of data and queries. The oneM2M architecture [i.5], the oneM2M semantic approach [i.6], the current oneM2M capabilities and SAREF [i.7], [i.8], [i.9], [i.10], [i.11], [i.12], [i.13] are at the basis of these use cases and requirements. This work is documented in ETSI TR 103 714 [i.1].
2) A study phase where possible approaches (existing and new ones) to a discovery and data aggregation solution are analysed with respect to the use cases and requirements. In particular, the need to plug in the solution on the oneM2M standard drives the solution analysis, to determine the best approach to be followed. The present document also looks to the query and discovery mechanisms already available, starting from the ones defined by ETSI (e.g. the one included in NGSI-LD [i.14]) to extract (and potentially adapt) the applicable components and to assure a smooth interworking with non-oneM2M solutions. This is documented in ETSI TR 103 715 [i.2].
3) A simulation phase is conducted in parallel and "circular" feedback with respect to the study phase, with the goal to provide a proof of concept, run suitable scenarios provided by previous phases and a performance evaluation to support the selection/developmen
4) A standardization phase where the Discovery and Query solution is specified and documented in ETSI TR 103 717 [i.4] (the present document).
The present document covers the fourth of the four phases and is related to the other documents listed below (the present document is highlighted in italic script in the list):
• ETSI TR 103 714: "SmartM2M; Study for oneM2M Discovery and Query use cases and requirements" [i.1];
• ETSI TR 103 715: "SmartM2M; Study for oneM2M Discovery and Query solutions analysis & selection" [i.2];
• ETSI TR 103 716: "SmartM2M; oneM2M Discovery and Query solution(s) simulation and performance evaluation" [i.3];
• ETSI TR 103 717: "SmartM2M; Study for oneM2M Discovery and Query specification development" [i.4] (the present document).
Scope of the present document
The present document develops the specification for the discovery solution selected in ETSI TR 103 715 [i.2] and which simulation is documented in ETSI TR 103 716 [i.3]. The present document specifies candidate solutions while the corresponding standardization proposals are contributed to oneM2M TS-0001 (Architecture) [i.5], oneM2M TS-0034 (Semantic support) [i.6], oneM2M TS-0033 (Interworking Framework) [i.15], oneM2M TS-0004 (Protocols) [i.16] (other oneM2M TS may be also impacted) with the help of the supporting companies active in oneM2M.
The present document is structured as follows:
• Clauses 1 to 3 set the scene and provide references as well as definitions of terms, symbols and abbreviations, which are used in the present document.
• Clause 4 describes the method used for developing the standardization proposal for oneM2M.
• Clause 5 presents an overview of the Advanced Semantic Discovery proposal, how to enhance the oneM2M architecture.
• Clause 6 illustrates oneM2M features with call flows among oneM2M entities with primitive exchange examples. This includes existing features from the oneM2M specifications as well as the newly proposed features to completely explain the solutions.
• Clause 7 proposes new primitive, parameters, resource types and relevant procedures.
• Clause 8 provides some lessons learned and conclusions.
Document History