diff --git a/TR-0076-Integrating_NGSI-LD_API_in_oneM2M.md b/TR-0076-Integrating_NGSI-LD_API_in_oneM2M.md index 36097f9e863135fd9adf8d8458529f3fe18be73a..6d60ac04b76f74a7cd8bfbe5e13ad6f3ab3f0396 100644 --- a/TR-0076-Integrating_NGSI-LD_API_in_oneM2M.md +++ b/TR-0076-Integrating_NGSI-LD_API_in_oneM2M.md @@ -1,4 +1,3 @@ -  @@ -46,23 +45,23 @@ NO REPRESENTATION OR WARRANTY IS MADE THAT THE INFORMATION IS TECHNICALLY ACCURA # Contents # 1 Scope -The present document ... - +The present document discusses how key features of the NGSI-LD API can be integrated in oneM2M and studies the impacts and necessary changes to oneM2M Specifications in particular in regard to the following. -`EXAMPLE: The present document provides the necessary adaptions to the endorsed document.` +The present document +- describes the additional functionality that the integration of NGSI-LD API and its related functionality can bring to the oneM2M standard, including the resulting integrated use cases. +- studies solutions for the architectural integration of NGSI-LD and its related functionalities into oneM2M, in particular with respect to oneM2M reference points and the existing oneM2M Common Service Functions. +- studies the mapping of the information stored in oneM2M resources to the NGSI-LD information model. This includes, but is not limited to the current oneM2M semantic models (in particular SDT and the oneM2M base ontology, including SAREF integration) to the NGSI-LD information model, with the goal of making it available through an integration of NGSI-LD API and the Mca reference point. This may suggest changes to the current NGSI-LD and Mca, and the related information models. +- studies the integration of NGSI-LD into oneM2M’s management and security frameworks, in particular for registration, authentication, access control and device management. -<mark>The Scope shall not contain requirements.</mark> # 2 References -<mark>The following text block applies.</mark> - -References are either specific (identified by date of publication and/or edition number or version number) or nonspecific. For specific references,only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. - ## 2.1 Normative references <mark>As a Technical Report (TR) is entirely informative it shall not list normative references.</mark> +References are either specific (identified by date of publication and/or edition number or version number) or nonspecific. For specific references,only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. + The following referenced documents are necessary for the application of the present document. Not applicable. @@ -71,10 +70,13 @@ Not applicable. ## 2.2 Informative references <mark>Clause 2.2 shall only contain informative references which are cited in the document itself.</mark> +References are either specific (identified by date of publication and/or edition number or version number) or nonspecific. For specific references,only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. + The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. - <a name="_ref_i.1">[i.1]</a> oneM2M Drafting Rules [https://member.onem2m.org/static_Pages/others/Rules_Pages/oneM2M-Drafting-Rules-V1%202%202.doc](https://member.onem2m.org/static_Pages/others/Rules_Pages/oneM2M-Drafting-Rules-V1%202%202.doc) - +- <a name="_ref_i.2">[i.2]</a> ETSI GS CIM 009: "Context Information Management (CIM); NGSI-LD API" [https://www.etsi.org/deliver/etsi_gs/CIM/001_099/009/01.08.01_60/gs_CIM009v010801p.pdf](https://www.etsi.org/deliver/etsi_gs/CIM/001_099/009/01.08.01_60/gs_CIM009v010801p.pdf) +- <a name="_ref_i.3">[i.3]</a> ETSI GS CIM 006: "Context Information Management (CIM); Information Model" [https://www.etsi.org/deliver/etsi_gs/CIM/001_099/006/01.03.01_60/gs_CIM006v010301p.pdf](https://www.etsi.org/deliver/etsi_gs/CIM/001_099/006/01.03.01_60/gs_CIM006v010301p.pdf) # 3 Definition of terms, symbols and abbreviations <mark>Delete from the above heading the word(s) which is/are not applicable.</mark> @@ -133,12 +135,46 @@ For the purposes of the present document, the [following] abbreviations [given i The key words "Shall", "Shall not", "May", "Need not", "Should", "Should not" in this document are to be interpreted as described in the oneM2M Drafting Rules <a href="#_ref_i.1">[i.1]</a> -# 5 User defined clause(s) from here onwards -<Text> +# 5 Introduction to NGSI-LD API and NGSI-LD Information Model +## 5.1 Motivation and key concepts -## 5.1 User defined subdivisions of clause(s) from here onwards -<Text> +## 5.2 NGSI-LD Information Model + +## 5.3 NGSI-LD API + +### 5.3.1 Overview + +<mark>The NGSI-LD resource structure will be introduced here or in an additional subclause. </mark> + +### 5.3.2 Query operations + +### 5.3.3 Subscription/notification operations + +### 5.3.4 Management operations + +## 5.4 Architectural considerations + +# 6 Assessment of additional functionality brought by NGSI-LD + +<mark>Based on the introduction in clause 5, description of the additional functionality that the integration of NGSI-LD API and its related functionality can bring to the oneM2M standard, including the resulting integrated use cases. </mark> + +# 7 Architectural integration of NGSI-LD into oneM2M + +<mark>Study solutions for the architectural integration of NGSI-LD and its related functionalities into oneM2M, in particular with respect to oneM2M reference points and the existing oneM2M Common Service Functions.</mark> + +# 8 Mapping between the information stored in oneM2M resources and the NGSI-LD information model + +<mark>Study the mapping between the information stored in oneM2M resources and the NGSI-LD information model. This includes, but is not limited to the current oneM2M semantic models (in particular SDT and the oneM2M base ontology, including SAREF integration) to the NGSI-LD information model, with the goal of making it available through an integration of NGSI-LD API and the Mca reference point. This may lead to an evolution of the current NGSI-LD and Mca, and the related information models.</mark> + +# 9 Integration of NGSI-LD into oneM2M's management and security frameworks + +<mark>Study the integration of NGSI-LD into oneM2M’s management and security frameworks, in particular for registration, authentication, access control and device management.</mark> + + +# 10 Overall impact assessment and recommendations + +<mark>Study the impacts and necessary changes to oneM2M Specifications </mark> <mark>The following text is to be used when appropriate:</mark> @@ -210,7 +246,7 @@ The key words "Shall", "Shall not", "May", "Need not", "Should", "Should not" in |Draft history (to be removed on publication) |Draft history (to be removed on publication) |Draft history (to be removed on publication) | |-|-|-| -|V1.1.1 |<yyyy-mm-dd> |<CR ID> applied - <Summary of changes> | +|V5.0.1 | 2024-04-17 | Scope and Table of Contents | | | | | | | | | | | | |