hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
5884f20096a929755c7228996f24adba | 118 109 | 7 Security Consideration | |
5884f20096a929755c7228996f24adba | 118 109 | 7.1 Authentication on HTTP Request Message | When sending the credential to be checked by the Registrar CSE, Proxy-Authorization header should be used as specified in HTTP/1.1 (see IETF RFC 7235 [Error! Reference source not found.]). When sending the credential to be checked by Hosting CSE, Authorization header should be used as specified in HTTP/1.1 [Error! Refe... |
5884f20096a929755c7228996f24adba | 118 109 | 7.2 Transport Layer Security | oneM2M primitive parameters contained in HTTP messages may be protected by TLS in a hop-by-hop manner. For the details, see the oneM2M Security Solutions specification [7]. NOTE: Some provisioning schemes of ETSI TS 118 103 [7] enable the provisioning of end-to-end credentials, but protocols to establish security assoc... |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 1 Scope | The present document specifies the interworking capabilities of the M2M Service Layer between ASN/IN/MN CSEs and LWM2M Endpoints using the architecture identified in Annex F of ETSI TS 118 101 [2] for the following interworking scenarios: • Interworking for transparent transport of encoded LWM2M Objects and commands in... |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 2 References | |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. 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 doc... |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. 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 doc... |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 3 Definition of terms, symbols and abbreviations | |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TS 118 111 [1] and ETSI TS 118 101 [2] apply. A term defined in the present document takes precedence over the definition of the same term, if any, in ETSI TS 118 111 [1] and ETSI TS 118 101 [2]. |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 3.2 Symbols | Void. |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TS 118 111 [1] and the following apply: LWM2M Lightweight M2M OMA OMA SpecWorks (formerly Open Mobile Alliance) |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 4 Conventions | The key words "Shall", "Shall not", "May", "Need not", "Should", "Should not" in the present document are to be interpreted as described in the oneM2M Drafting Rules [i.1]. |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 5 Architecture Model | |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 5.1 Introduction | The architecture model followed in the present document is based on the architecture model in Annex F of ETSI TS 118 101 [2] that describes how interworking between CSEs and non-oneM2M solutions and protocol using specialized Interworking Proxy application Entities (IPE). The present document describes the LWM2M IPE th... |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 5.2 Reference Model | The LWM2M Interworking reference model utilizes the Functional Architecture's reference model in ETSI TS 118 101 [2]; augmenting the ETSI TS 118 101 [2] reference model with capabilities provided by the LWM2M IPE. NOTE: The AE in the reference model could be registered with the same CSE as the LWM2M IPE. Figure 5.2-1: ... |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 5.3 Types of Interworking | LWM2M IPEs provide the following types of interworking: 1) Interworking using the Content Sharing Resource for transparent transport of encoded LWM2M Objects that are available to AEs as depicted in Figure 5.3-1. 2) Interworking with full mapping of the semantics of LWM2M Objects to semantically enabled resources that ... |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 5.4 Composition of the Interworking Proxy Entity | The LWM2M IPE participation in the LWM2M Protocol as described in clause 5 does so in the role of a LWM2M Server to which LWM2M Applications (LWM2M Clients) interact. For each LWM2M Client (Endpoint) that is maintained by the LWM2M Server in the LWM2M IPE, the LWM2M IPE shall instantiate and maintains an instance of a ... |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 6 Architecture Aspects | |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 6.1 Introduction | The LWM2M IPE participation in the LWM2M Protocol as described in clause 5 does so in the role of a LWM2M Server to which LWM2M Applications (LWM2M Clients) interact. As a LWM2M Server, the IPE provides the following Architecture Aspects based on the LWM2M Protocol Aspects described in clause A.2: • LWM2M Device and En... |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 6.2 LWM2M Device and Endpoint Lifecycle | |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 6.2.1 Introduction | As the LWM2M IPE discovers LWM2M Endpoints when the LWM2M IPE interacts with the LWM2M Client over the LWM2M protocol's Bootstrap and Client Registration interfaces, the LWM2M IPE shall maintain the associated resources in the CSE that represents the LWM2M Device and Endpoint. |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 6.2.2 LWM2M Device and Endpoint Resource Representation | |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 6.2.2.1 Introduction | LWM2M Endpoint provides the management and control functions for an M2M Application on a device. As such, the CSE that hosts the M2M Application shall represent the LWM2M Endpoint as a <AE> resource (LWM2M Endpoint <AE> resource). The LWM2M Device that hosts the LWM2M Endpoint shall be represented as a <node> resource. |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 6.2.2.2 LWM2M Device and Endpoint Resource Identification | LWM2M Endpoints are identified by their Endpoint Client Name described in clause 6.2.1 of the LWM2M Technical Specification [3]. The Endpoint Client Name URN without the "urn:" sequence is used as the AE-ID of the associated <AE> resource that represents the LWM2M Client. In most deployment scenarios, LWM2M Devices hos... |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 6.2.2.3 LWM2M Endpoint Lifecycle | LWM2M Endpoint's are discovered when the LWM2M Client is successfully registers with the LWM2M Server using the LWM2M Register operation. In addition to the LWM2M Register operation, the LWM2M Client can periodically refresh the LWM2M Client's registration with the LWM2M IPE using the LWM2M Update operation. Finally a ... |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 6.2.2.4 Configuration of CMDH Policies | In the present document, the CMDH Policies associated with the <Node> resource for the AE is implementation specific. |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 6.2.2.5 Registering a Registered LWM2M Endpoint | In the scenario where a LWM2M Client issues a Register operation for an AE that is already created, the LWM2M IPE shall treat the operation as if the LWM2M Client requested a De-Register (Delete <AE> resource) prior this Register operation (Create <AE> resource) as described in Table 6.2.2.3-1. The procedure for the LW... |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 6.3 LWM2M Object Discovery | |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 6.3.1 Introduction | The LWM2M Client uses the Registration Interface to provide the properties required by the LWM2M Server of the IPE to contact the LWM2M Client (e.g. Endpoint Name) and to maintain the session between these two LWM2M entities (e.g. Lifetime, Queue Mode). In addition, the LWM2M Client also provides the knowledge of the s... |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 6.3.2 LWM2M Object Identifier Representation | |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 6.3.2.1 Introduction | Through the Registration Interface, the LWM2M Client provides the list of supported LWM2M Objects and existing LWM2M Object Instances. Each element of the list is described by its path, which can be the path of an Object or an Object Instance. For example the LWM2M Client could provide the following list of paths: </1/... |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 6.3.2.2 Void | |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 6.3.2.3 LWM2M Object Lifecycle | LWM2M Endpoint's are discovered when the LWM2M Client is successfully registers with the LWM2M Server using the LWM2M Register operation. In addition to the LWM2M Register operation, the LWM2M Client can periodically refresh the LWM2M Client's registration with the LWM2M IPE using the LWM2M Update operation. Finally a ... |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 6.4 LWM2M Object Transport and Interworking | |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 6.4.1 Introduction | When an oneM2M request is addressed from a CSE/AE to a hosting CSE containing the representation of a LWM2M Client, the oneM2M response to the Originator of the request is returned through the cooperation of the hosting CSE and the IPE. The LWM2M Client uses the Device Management & Service Enablement interface to provi... |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 6.4.2 LWM2M Interworking Mechanisms | |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 6.4.2.1 Introduction | Cooperation between IPE and the oneM2M hosting CSE requires efficient mechanisms to maintain the latest state of the targeted LWM2M Objects, Object Instances and Resources. These mechanisms include data synchronization between the IPE and hosting CSE. Data synchronization relies on the oneM2M Subscription/Notification ... |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 6.4.2.2 Relevant Interworked Resource Settings | A LWM2M Object Instance that is represented in oneM2M as a <container> resource has 2 direct children resource types: a <subscription> resource and a <contentInstance> resource when used with a <container> resource. A LWM2M Object Instance that is represented in oneM2M as a <mgmtObj> resource may have 1 direct child re... |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 6.4.2.3 oneM2M RETRIEVE Procedure | This procedure describes the retrieval of a resource using the oneM2M RETRIEVE request. The information contained within the resource is related to the LWM2M Objects Instances that are interworked through the IPE. This clause shall be treated in conformance with the RETRIEVE Procedure specified in ETSI TS 118 101 [2], ... |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 6.4.2.4 oneM2M CREATE Procedure | This procedure describes the update of a LWM2M Object Instance in a LWM2M Client using the oneM2M CREATE request. The information contained in the request via the Content parameter (ETSI TS 118 101 [2], clause 8.2.1) will be used to update an Object Instance in the LWM2M context. This clause shall be treated in conform... |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 6.4.2.5 oneM2M UPDATE Procedure | This procedure describes the update of a LWM2M Object Instance or Resource in a LWM2M Client using the oneM2M UPDATE request. The information contained in the request via the Content parameter (ETSI TS 118 101 [2], clause 8.1.2) shall be used to update an Object Instance or Resource in the LWM2M context. This clause sh... |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 6.4.2.6 oneM2M DELETE Procedure | This procedure describes the removal of a LWM2M Object Instance within a LWM2M Client using the oneM2M DELETE request. This clause shall be treated in conformance with the DELETE Procedure specified in ETSI TS 118 101 [2], clauses 10.1.4 and 10.2.4.4. oneM2M TS-0014 version 4.0.1 Release 4 ETSI ETSI TS 118 114 V4.0.1 (... |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 6.4.3 oneM2M Resource Operation Responses | Table 6.4.3-1: LWM2M Response Codes to oneM2M Resource Operation Response Codes LWM2M Client Response Codes on Device Management & Service Enablement interface oneM2M Resource Operation Response Create 2.01 Created: 4.00 Bad Request 4.01 Unauthorized 4.04 Not Found 2001 Created 4000 4103 4004 Read 2.05 Content: 4.01 Un... |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 6.5 LWM2M Object Subscription and Notification | |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 6.5.1 Introduction | The LWM2M Server uses the Information Reporting Interface to provide the capabilities for a LWM2M Server to subscribe to changes to the LWM2M Objects, LWM2M Object instances and the associated LWM2M Object's resources. Likewise the LWM2M Client uses the Information Reporting Interface to notify subscribed LWM2M Server'... |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 6.5.2 LWM2M Subscription Procedure | The LWM2M IPE interworks the oneM2M resource's <subscription> child resource with the corresponding LWM2M Object using the oneM2M <subscription> resource's attributes and the corresponding LWM2M Object resource's Notification class Attributes. NOTE: Each LWM2M Object resource has an associated set of Notification class... |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 6.5.3 LWM2M Notification Procedure | When the LWM2M IPE is notified by the LWM2M Client of a change in a LWM2M Object or Object Instance the LWM2M IPE creates a new <contentInstance> for the associated <container> resource according to the procedures for the type of interworking (e.g. Transparent, Semantic) as described in clause 7 or 8. For the case wher... |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 6.6 LWM2M Object Security | |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 6.6.1 Introduction | OMA-LWM2M and oneM2M Access Control Policies shall collaborate in order to assure the interworked resources are accessible according to the oneM2M Authorisation Procedure specified in clause 11.3.4 (M2M Authorization Procedure) of ETSI TS 118 101 [2] and clause 7 (Authorization) of ETSI TS 118 103 [5]. 6.6.2 LWM2M Inte... |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 6.6.3 IPE and Object Security provisioning | In order to provide oneM2M information specified in the clause 6.6.2 (set of <accessControlPolicy> (ACPs) resources, assignment of accessControlPolicyIDs), the LWM2M IPE shall be supplied by information such as: • a list of oneM2M originators and their associated Access Control Rules likely to be exercised on the Hosti... |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 6.7 LWM2M IPE Administration and Maintenance | |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 6.7.1 Introduction | 6. |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 7.1 Introduction | The IPE described in clause 5.4 is comprised functionality that includes the LWM2M Server and the IPE's AE. This clause describes the administration and maintenance of these functional elements. oneM2M TS-0014 version 4.0.1 Release 4 ETSI ETSI TS 118 114 V4.0.1 (2023-11) 26 |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 6.7.2 Administration and Maintenance of the LWM2M Server Functionality | |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 6.7.2.1 Introduction | The LWM2M IPE provides the functionality that plays the role of the LWM2M Server in order to communicate with LWM2M Clients. In order for communication to be established information needs to be provisioned into the LWM2M Client and LWM2M Server where the following artefacts are necessary to be established for the LWM2M... |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 6.7.2.2 LWM2M Server Maintenance | The LWM2M Server maintains a set of LWM2M Server account information for each LWM2M Client that allows the LWM2M Server to access and communicate with LWM2M Client. These are: • LWM2M Server identifier associated with and assigned by the LWM2M Client (LWM2M Server identifier, registration lifetime). • Policies for defa... |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 6.7.3 Maintenance of the LWM2M IPE AE Context | |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 6.7.3.1 Introduction | The LWM2M IPE AE maintains information related to the operational context of the LWM2M IPE AE. Specifically the following elements are maintained for the LWM2M IPE AE: • List of currently registered LWM2M Endpoints. • Configuration of the Interworking Functions to be used for the LWM2M Objects and Object Instances. |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 6.7.3.2 LWM2M Endpoint List | Whenever an LWM2M Endpoint <AE> resource is created, updated or deleted as described in clause 6.2, the LWM2M IPE also manages the list of LWM2M Endpoint <AE> resources using a oneM2M <group> resource. The oneM2M <group> resource's lifecycle is linked to the LWM2M IPE <AE> resource's lifecycle. oneM2M TS-0014 version 4... |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 6.7.3.3 Configuration of Interworking Functions | Clause 5.3 describes the types of interworking functions as Transparent Interworking Function and Semantically Enabled Interworking Function. An IPE provides the capability to perform one or both types of interworking functions. The granularity (e.g. Object/Object Instance, IPE) that is used to define which interworkin... |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 6.8 LWM2M Client Provisioning (Bootstrap) | The present document makes assumptions that the LWM2M Clients and LWM2M Servers functionality of the IPE have been provisioned with the proper LWM2M credential materials in accordance to the LWM2M specification (clause A.5.3.1) in order to securely communicate between the LWM2M Client and LWM2M Server. Additionally, a ... |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 7 Transparent Interworking Function | 7.1 Introduction Clause 5.3 introduced the Transparent Interworking function as depicted in Figure 5.3-1. This clause specifies the mappings of the attributes of the <contentInstance> resource for a <container> resource in order to allow an AE that uses the Content Sharing Resource to understand that the Content Sharin... |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 7.2 Attribute Mapping for the <contentInstance> Resources | When an AE accesses a <contentInstance> resource, the AE needs to know that the <contentInstance> resource encapsulates a LWM2M Object or Object Instance as well as how the LWM2M Object or Object Instance is encoded. oneM2M TS-0014 version 4.0.1 Release 4 ETSI ETSI TS 118 114 V4.0.1 (2023-11) 28 Table 7.2-1: Transparen... |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 8.1 Introduction | Clause 5.3 introduced the Semantically Enabled Interworking function as depicted in Figure 5.3-2. This clause specifies how LWM2M Objects and their associated LWM2M Resources are organized as <container> resources in order for values associated with the LWM2M Resources be translated into <contentInstance> resources. In... |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 8.2.1 Introduction | Semantically enabled Content Sharing Resources represent the structure and content of LWM2M Objects and Object Instances by translating LWM2M Objects, Object Instances and their LWM2M Resources and LWM2M Resource Instances into a hierarchy of Content Sharing Resources using the Content Sharing Resource's parent-child r... |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 8.2.2 Lifecycle of Semantically Enabled Content Sharing Resources | Clauses 6.3 and 6.4 describe how LWM2M Objects and Object Instances are discovered and instantiated. The Semantic Interworking function uses these procedures for instantiation of the Content Sharing Resource for the LWM2M Objects and Object Instances. The Content Sharing Resources for LWM2M Resources and Resource Insta... |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 8.2.3 Mapping for the Encoding of the <contentInstance> Resource | When an AE accesses a <contentInstance> resource, the AE needs to know how the value of the Resource or Resource Instance is encoded. oneM2M TS-0014 version 4.0.1 Release 4 ETSI ETSI TS 118 114 V4.0.1 (2023-11) 30 Table 8.2.3-1: Mapping of Resource or Resource Instance Encoding Interworking Function Mapping oneM2M Reso... |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 8.3 Guidelines for Mapping to the Base Ontology | |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 8.3.1 Introduction | Clause 8.2 describes the structure and relationships of the LWM2M Objects and Object Instances along with their associated Resources and Resource Instances. Using that structure this clause provides guidance on mapping the Base Ontology described by [i.5] onto that resource structure. As ontologies are created for spec... |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 8.3.2 Mapping of the LWM2M Client | LWM2M Clients are represented as <AE> resources and are mapped to an InterworkedDevice. <AE> resources exposed by the LWM2M Server associated with the IPE are mapped to the same Area Network. 8.3.3 Mapping of the LWM2M Object, Object Instance. Resource and Resource Instance |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 8.3.3.1 Introduction | Mapping the LWM2M Object, Object Instance. Resource and Resource Instance to the Base Ontology is based on the following guidelines: • LWM2M Clients are mapped to InterworkedDevices • LWM2M Objects are mapped to Services and Functionality • LWM2M Resources that represent static (configured) properties of LWM2M Objects ... |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 9.1 Introduction | Clause 5.3 introduced the Management Object-based Interworking function as depicted in Figure 5.3-3. This clause specifies the mappings of the attributes of oneM2M resources to LWM2M objects in order to allow an AE to use the oneM2M resource without needing to understand the underlying LWM2M Object, Object Instance or ... |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 9.2 Translation of oneM2M Management Resource Types | |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 9.2.1 Introduction | These mappings and procedures are used to translate between LWM2M Objects, Object Instances and Resources and the applicable management-related oneM2M resource types. |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 9.2.2 Translation to <mgmtObj> Resource Types | |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 9.2.2.1 Mapping to <mgmtObj> Resource Types | ETSI TS 118 105 [4] provides the procedures and mappings needed to translate LWM2M Objects, Object Instances and Resources into <mgmtObj> resource types. Relevant clauses include: • Clauses 6.1 and 6.3 of ETSI TS 118 105 [4] provides mapping LWM2M Objects, Object Instances and Resources into <mgmtObj> resource types. •... |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 9.2.2.2 Interworking of <mgmtObj> Resources | |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 9.2.2.2.1 Introduction | Clause 10.2.8 of ETSI TS 118 101 [2] discusses the procedures for the <mgmtObj> resources as well as where the resources are hosted and the <mgmtObj> resource's relationship with its parent <node> resource. As the <node> resource is the parent resource of the <mgmtObj> resources for the node, clauses 6.4.2, 6.5.2 and 6... |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 9.2.2.2.2 Interworking of <mgmtObj> Resource Settings | For supporting the LWM2M interworking process, a few attributes for the <node> resource, <mgmtObj> resource and the <subscription> resource shall have a specified set of parameters. a) Attributes of <node> resource Table 9.2.2.2.2-1: <node> resource - Relevant Interworked Attributes Attributes of <mgmtObj> resource Val... |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 9.2.2.2.3 Synchronization <mgmtObj> resources | <mgmtObj> resources can be maintained by AEs and/or the LWM2M IPE on behalf of the LWM2M client. Since AEs can maintain <mgmtObj> resources, the request originator (i.e. AE, LWM2M IPE AE) shall create a subscription to notify the LWM2M IPE when the <mgmtObj> resource is created, deleted or updated using the setting as ... |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 9.2.2.3 Example of creating new specialized <mgmtObj> resources | Using the generic guidelines outlined in clause 6.7 of ETSI TS 118 105 [4], new <mgmtObj> specialization resources may be created on the CSE. Figure 9.2.2.3-1 shows the procedure a Hosting CSE executes to create a new <mgmtObj> specialization resource using the mgmtSchema attribute. The URI of the schema file for the <... |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 9.2.2.4 LWM2M Interworking Procedure | Figure 9.2.2.4-1 shows an example end-to-end procedure demonstrating how the procedures shown in Figure 9.2.2.3-1 can be utilized as part of LWM2M Interworking. The LWM2M Server and the IPE are co-located, and together they perform oneM2M procedures on behalf of the LWM2M Device. A LWM2M Device will initially register ... |
d34e080defcc243403ce1e85fbc15804 | 118 114 | 9.2.2.5 Use of oneM2M attribute level subscription in LWM2M Interworking | Once the <mgmtObj> resources are created, attribute level subscriptions can be created to get notifications for certain desired operation such as a firmware update process. With the one-to-one mapping relationship between LWM2M resources and oneM2M [objectAttribute], attribute level subscriptions can be made. Table 9.2... |
1b8e2d048ecdcc1f1241868583da88b0 | 118 108 | 1 Scope | The present document will cover the protocol specific part of communication protocol used by oneM2M compliant systems as 'RESTful CoAP binding'. The scope of the present document is (not limited to as shown below): • Binding oneM2M primitives to CoAP messages. • Binding oneM2M Response Status Codes to CoAP Response Cod... |
1b8e2d048ecdcc1f1241868583da88b0 | 118 108 | 2 References | |
1b8e2d048ecdcc1f1241868583da88b0 | 118 108 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
1b8e2d048ecdcc1f1241868583da88b0 | 118 108 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
1b8e2d048ecdcc1f1241868583da88b0 | 118 108 | 3 Definition of terms, symbols and abbreviations | |
1b8e2d048ecdcc1f1241868583da88b0 | 118 108 | 3.1 Terms | Void. |
1b8e2d048ecdcc1f1241868583da88b0 | 118 108 | 3.2 Symbols | Void. |
1b8e2d048ecdcc1f1241868583da88b0 | 118 108 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ACK CoAP Acknowledgement message AE Application Entity CON CoAP Confirmable message CSE Common Service Entity DTLS Datagram Transport Layer Security HTTP Hyper Text Transfer Protocol IANA Internet Assigned Numbers Authority IP Internet Protoco... |
1b8e2d048ecdcc1f1241868583da88b0 | 118 108 | 4 Conventions | The keywords "Shall", "Shall not", "May", "Need not", "Should", "Should not" in the present document are to be interpreted as described in the oneM2M Drafting Rules [i.1]. |
1b8e2d048ecdcc1f1241868583da88b0 | 118 108 | 5 Overview | |
1b8e2d048ecdcc1f1241868583da88b0 | 118 108 | 5.0 Introduction | The clause describes which features need to be supported in CoAP layer and introduces a message format and several features of CoAP used in this protocol binding specification. |
1b8e2d048ecdcc1f1241868583da88b0 | 118 108 | 5.1 Required Features | This clause explicitly specifies the required features of the CoAP layer for oneM2M to properly bind oneM2M primitives into CoAP messages: • The 4-byte binary CoAP message header is defined in section 3 of IETF RFC 7252 [1]. oneM2M TS-0008 version 4.4.1 Release 4 ETSI ETSI TS 118 108 V4.4.1 (2023-08) 8 • Confirmable (C... |
1b8e2d048ecdcc1f1241868583da88b0 | 118 108 | 5.2 Introduction to CoAP | |
1b8e2d048ecdcc1f1241868583da88b0 | 118 108 | 5.2.0 Introduction | This clause describes a message format, and caching and block-wise transfers features which may be used to map oneM2M primitives to CoAP messages. |
1b8e2d048ecdcc1f1241868583da88b0 | 118 108 | 5.2.1 Message Format | This clause specifies details about the CoAP [1] message format: • CoAP message occupies the data section of one UDP datagram. • CoAP message format supports a 4-byte fixed-size header. • Fixed-size header is followed by a Token value of length 0 to 8 bytes. • The Token value is followed by a sequence of zero or more C... |
1b8e2d048ecdcc1f1241868583da88b0 | 118 108 | 5.2.2 Caching | |
1b8e2d048ecdcc1f1241868583da88b0 | 118 108 | 5.2.2.0 Introduction | CoAP [1] supports caching of responses to fulfil future equivalent requests to the same resource. Caching is supported using freshness and validity information carried with CoAP [1] responses. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.