hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 6.1 Mapping of basic data types | oneM2M has defined the data types that describe the format of the value stored at the attribute. Those oneM2M data types are listed in table 6.1-1 and mapped to the data types specified by OMA Lightweight M2M 1.0 [5] (shortened in OMA LwM2M). Table 6.1-1: Basic data types oneM2M Data Types Mapping to data types in OMA ... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 6.2 Mapping of Identifiers | |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 6.2.0 Introduction | OMA LwM2M [5] defines specific identifiers for entities (e.g. End Point Client Name or Device Identifier, Server identifier, Objects identifiers). To enable the device management using OMA LwM2M [5], oneM2M identifiers needs to be mapped to identifiers specified by OMA LwM2M [5]. |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 6.2.1 Device identifier | A unique identifier is assigned to the Device and referenced as Endpoint Client Name in OMA LwM2M [5]. This value is globally unique and is formatted as a URN. Several URN formats are recommended in OMA LwM2M [5] as UUID URN defined in IETF RFC 4122 [14], OPS URN defined in BBF TR-069 [16], IMEI URN defined in 3GPP TS ... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 6.2.2 Object identifier | In OMA LwM2M [5], each object is characterized by a unique identifier represented by an integer. This identifier is provided by OMNA (OMA Naming Authority) and is registered as a unique URN: • urn:oma:lwm2m:{oma,ext,x}:objectID[ :{version}] (e.g. the LwM2M 1.0 Device Object (ObjectID:3) is registered as urn:oma:lwm2m:o... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 6.2.3 Object Instance Identifier | OMA LwM2M [5] permits objects to have multiple object instances where each object instance is contained in the objectPath attribute of the <mgmtObj> Resource within the context of the Resource's objectIDs as described in clause 6.2.2. The objectPath attribute in <mgmtObj> Resource contains one (or several) element(s) r... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 6.3 Mapping of resources | |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 6.3.0 Introduction | Clause 6.3 describes how to map the <mgmtObj> Resources specified in annex D of ETSI TS 118 101 [1] to the relevant Objects specified in OMA LwM2M [5]. |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 6.3.1 General Mapping Assumptions | OMA LwM2M [5] implements the functionalities of the device management and M2M service enablement as Objects. An Object is a collection of resources which are related to a specific management functionality. For example, the Firmware Update Object contains all the resources used for firmware update purpose. Before to be ... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 6.3.2 Resource [firmware] | The resource [firmware] is for firmware management in the service layer. The context of this Resource is the following. Table 6.3.2-1: Context of resource [firmware] Context Mapping objectIDs urn:oma:lwm2m:oma:5 Firmware Update Object objectPath /5/0 The attributes of this Resource shall be mapped to specific resources... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 6.3.3 Resource [software] | The resource [software] is for software management in the service layer. The context of this Resource is the following. Table 6.3.3-1: Context of resource [software] Context Mapping objectIDs urn:oma:lwm2m:oma:9 objectPath /9/{i} The attributes of this Resource shall be mapped to specific resources of the LwM2M Softwar... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 6.3.4 Resource [memory] | The Resource [memory] provides memory related information. For OMA LwM2M, this Resource shall be mapped to the unique Instance of LwM2M Device Object (LwM2M ObjectID: 3). The context of this Resource is as follows. Table 6.3.4-1: Context of resource [memory] Context Mapping objectIDs urn:oma:lwm2m:oma:3 objectPath /3/0... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 6.3.5 Resource [areaNwkInfo] | The resource [areaNwkInfo] is for managing the area network. NOTE: There is currently no defined LwM2M object yet. This mapping is not available in the present document. |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 6.3.6 Resource [areaNwkDeviceInfo] | The resource [areaNwkDeviceInfo] is for managing the device of the area network as well as acquiring information about devices in the area network. NOTE: There is currently no defined LwM2M object yet. This mapping is not available in the present document. |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 6.3.7 Resource [battery] | The Resource [battery] provides battery related information. For OMA LwM2M, this Resource shall be mapped to the unique Instance of LwM2M Device Object (LwM2M ObjectID: 3). The context of this Resource is as follows. Table 6.3.7-1: Context of resource [battery] Context Mapping objectIDs urn:oma:lwm2m:oma:3 objectPath /... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 6.3.8 Resource [deviceInfo] | The Resource [deviceInfo] provides device related information. For OMA LwM2M, this Resource shall be mapped to the unique Instance of LwM2M Device Object (LwM2M ObjectID: 3). The context of this Resource is the following. Table 6.3.8-1: Context of resource [deviceInfo] Context Mapping objectIDs urn:oma:lwm2m:oma:3 obje... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 6.3.9 Resource [deviceCapability] | The Resource [deviceCapability] is to manage the device capabilities such USB, camera, etc. The Resource [deviceCapability] is mapped to the LwM2M Device Capability Management Object (urn:oma:lwm2m:oma:15 [19]). The context of this Resource is the following. Table 6.3.9-1: Context of resource [deviceCapability] Context... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 6.3.10 Resource [reboot] | The Resource [reboot] is used for rebooting the device. For OMA LwM2M, this Resource shall be mapped to the unique Instance of LwM2M Device Object (LwM2M ObjectID: 3). The context of this Resource is as follows. Table 6.3.10-1: Context of resource [reboot] Context Mapping objectIDs urn:oma:lwm2m:oma:3 objectPath /3/0 T... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 6.3.11 Resource [eventLog] | The Resource [eventLog] is to record the event log for the device. For OMA LwM2M, this Resource shall be mapped to one instance of LwM2M Event Log Object (LwM2M Object: {20}). The context of this Resource is as follows. Table 6.3.11-1: Context of resource [eventLog] Context Mapping objectIDs urn:oma:lwm2m:oma:{20} obje... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 6.3.12 Resource [cmdhPolicy] | |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 6.3.12.0 Introduction | The Resource Type [cmdhPolicy] represents a set of rules associated with a specific CSE that govern the behaviour of that CSE regarding rejecting, buffering and sending request or response messages via the Mcc reference point. See clause D.12 of ETSI TS 118 101 [1] for a detailed high-level description of the overall s... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 6.3.12.1 Resource [activeCmdhPolicy] | The Resource [activeCmdhPolicy] provides a link to the currently active set of CMDH policies, see clause D.12.1 of ETSI TS 118 101 [1]. The Resource [activeCmdhPolicy] includes an attribute cmdhPolicy which is mapped on the ActiveLink resource of the LwM2M ActiveCmdhPolicy Object instance pointing to the active instanc... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 6.3.12.2 Resource [cmdhDefaults] | The Resource [cmdhDefaults] defines default CMDH policy values, see clause D.12.2 of ETSI TS 118 101 [1]. The Resource [cmdhDefaults] is a multi-instance Resource where each instance of the Resource shall map to an instance of the LwM2M cmdhDefaults Object. The context of this Resource is as follows. Table 6.3.12.2-1: ... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 6.3.12.3 Resource [cmdhDefEcValue] | The Resource [cmdhDefEcValue] represents a default value for the ec (event category) parameter of an incoming request, see clause D.12.3 of ETSI TS 118 101 [1]. The context of this Resource is as follows. Table 6.3.12.3-1: Context of resource [cmdhDefEcValue] Context Mapping objectIDs urn:oma:lwm2m:ext:2051 objectPath ... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 6.3.12.4 Resource [cmdhEcDefParamValues] | The Resource [cmdhEcDefParamValues] represents a specific set of default values for the CMDH related parameters rqet (request expiration timestamp), rset (result expiration timestamp), oet (operational execution time), rp (response persistence) and da (delivery aggregation) that are applicable for a given ec (event cat... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 6.3.12.5 Resource [cmdhLimits] | The Resource [cmdhLimits] represents limits for CMDH related parameter values, see clause D.12.5 of ETSI TS 118 101 [1]. The context of this Resource is as follows. Table 6.3.12.5-1: Context of resource [cmdhLimits] Context Mapping objectIDs urn:oma:lwm2m:ext:2053 objectPath /2053/{i} The Resource [cmdhLimits] is a mul... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 6.3.12.6 Resource [cmdhNetworkAccessRules] | The Resource [cmdhNetworkAccessRules] defines the usage of underlying networks for forwarding information to other CSEs during processing of CMDH-related requests in a CSE, see clause D.12.6 of ETSI TS 118 101 [1]. The context of this Resource is as follows. Table 6.3.12.6-1: Context of resource [cmdhNetworkAccessRules... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 6.3.12.7 Resource [cmdhNwAccessRule] | The Resource [cmdhNwAccessRule] defines limits in usage of specific underlying networks for forwarding information to other CSEs during processing of CMDH-related requests, see clause D.12.7 of ETSI TS 118 101 [1]. The context of this Resource is as follows. Table 6.3.12.7-1: Context of resource [cmdhNwAccessRule] Cont... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 6.3.12.8 Resource [cmdhBuffer] | The Resource [cmdhBuffer] represents limits in usage of buffers for temporarily storing information that needs to be forwarded to other CSEs during processing of CMDH-related requests in a CSE, see clause D.12.8 of ETSI TS 118 101 [1]. The context of this Resource is as follows. Table 6.3.12.8-1: Context of resource [c... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 6.4 Mapping of procedures for management | |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 6.4.0 Introduction | In clause 6.4, the oneM2M Primitives (i.e. Create, Retrieve, Update, Delete, and Notify) are mapped to logical operations defined in OMA LwM2M. The LwM2M operations involved in that mapping (i.e. Create, Read, Write, Execute, Delete, Observe,Write Attributes and Notify operations) are mapped on CoAP methods [17]. Creat... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 6.4.1 Create primitive for <mgmtObj> Resource | Depending on the mgmtDefinition attribute of the <mgmtObj> Resource (i.e. [memory], [battery], [deviceInfo], etc.), an instance of the associated LwM2M Object as specified in clause 6.3 should be created. Receiving Create Request primitive does not imply that the LwM2M Create operations shall be always performed since,... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 6.4.2 Retrieve primitive for <mgmtObj> Resource | Depending on the mgmtDefinition attribute of the <mgmtObj> Resource (i.e. [memory], [battery], [deviceInfo], etc.), the associated LwM2M Object resources as specified in clause 6.3 shall be retrieved. The Retrieve primitive shall map to the LwM2M Read operation and shall return one of the codes described in table 6.4.2... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 6.4.3 Update primitive for <mgmtObj> Resource | |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 6.4.3.0 Introduction | The Update Request Primitive for <mgmtObj> Resource can be used to modify the resources of a LwM2M Object instance or to execute the action related to a resource of a LwM2M Object instance. The mapping in either case shall be different. ETSI ETSI TS 118 105 V4.0.1 (2025-09) 64 oneM2M TS-0005 version 4.0.1 Release 4 |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 6.4.3.1 Update primitive for replacing data | Depending on the mgmtDefinition attribute of the <mgmtObj> Resource (i.e. [memory], [battery], [deviceInfo], etc.), the associated resource(s) of the LwM2M Object instance as specified in clause 6.3 shall be updated. The Update primitive shall map to the LwM2M Write operation and shall return one of the codes described... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 6.4.3.2 Update primitive for execution operation | This is the case that the Update Primitive targets the attribute that is mapped to a LwM2M resource that supports the Execute operation. The Update primitive shall map to the LwM2M Execute operation and shall return one of the codes described in table 6.4.3.2-1. Table 6.4.3.2-1: Execute Returned Codes Mapping oneM2M Pr... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 6.4.4 Delete primitive for <mgmtObj> Resource | Depending on the mgmtDefinition attribute of the <mgmtObj> Resource (i.e. [memory], [battery], [deviceInfo], etc.), the associated LwM2M Object instance as specified in clause 6.3 should be deleted. Receiving Delete Request primitive does not imply that the corresponding LwM2M Object Instance shall always be deleted. T... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 6.4.5 Notify Primitive for <mgmtObj> Resource | |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 6.4.5.0 Introduction | The Notify primitive permits notifications to Originators that have subscribed to a Resource. In LwM2M, "subscription for notification" can address: either a specific resource, or all the resources of an Object Instance, or all the resources of all the Object Instances of a given Object in the LwM2M Client. |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 6.4.5.1 Notify Primitive mapping for subscription to Resource attributes | The Notify Primitive for subscription shall map to a combination of OMA LwM2M Write Attributes and Observe operations. Write Attributes allows to set notification parameters, e.g. Notification Periodicity. According to the parameters provided to the Observe operation, a subscription for change to a specific resource, a... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 6.4.5.2 Notify Primitive mapping for subscription cancellation to Resource attributes | The Notify Primitive for cancelling subscription shall map to the OMA LwM2M Cancel Observation operation: this LwM2M Cancel Observation operation is sent from the LwM2M Server to the LwM2M client to end an observation relationship for Object Instance or Resource(s). LwM2M enabler provides two ways for the LwM2M Server ... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 6.4.5.3 Notify Primitive mapping for Notification | The Notify Primitive for Notification shall map to the OMA LwM2M Notify operation which carries the changed value(s) of the Object Instance Resource(s) and the code described in table 6.4.5.3-1. Table 6.4.5.3-1: Notify for Notification Returned Codes Mapping oneM2M Primitive Status Code Returned Codes Description succe... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 6.4.6 Management Resource Specific Procedure Mapping | |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 6.4.6.1 Resource [firmware] | The generic <mgmtObj> mappings described in clauses 6.4.1 and 6.4.5 shall apply, and no specific mapping is necessary. In addition to the status code mapping for the <mgmtObj> CRUD Operations, no [firmware] specific status code is defined in [5]. |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 6.4.6.2 Resource [software] | The generic <mgmtObj> mappings described in clauses 6.4.1 and 6.4.5 shall apply, and no specific mapping is necessary. In addition to the status code mapping for the <mgmtObj> CRUD Operations, no [software] specific status code is defined in [5]. |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 6.4.6.3 Resource [memory] | The generic <mgmtObj> mappings described in clauses 6.4.1 and 6.4.5 shall apply, and no specific mapping is necessary. In addition to the status code mapping for the <mgmtObj> CRUD Operations, no [memory] specific status codes are defined in [5]. |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 6.4.6.4 Resource [battery] | The generic <mgmtObj> mappings described in clauses 6.4.1 and 6.4.5 shall apply, and no specific mapping is necessary. In addition to the status code mapping for the <mgmtObj> CRUD Operations, no [battery] specific status codes are defined in [5]. |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 6.4.6.5 Resource [deviceInfo] | The generic <mgmtObj> mappings described in clauses 6.4.1 and 6.4.5 shall apply, and no specific mapping is necessary. In addition to the status code mapping for the <mgmtObj> CRUD Operations, no [deviceInfo] specific status codes are defined in [5]. ETSI ETSI TS 118 105 V4.0.1 (2025-09) 67 oneM2M TS-0005 version 4.0.1... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 6.4.6.6 Resource [deviceCapability] | The generic <mgmtObj> mappings described in clauses 6.4.1 and 6.4.5 shall apply, and no specific mapping is necessary. In addition to the status code mapping for the <mgmtObj> CRUD Operations, no [deviceCapability] specific status code is defined in [5]. |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 6.4.6.7 Resource [reboot] | The generic <mgmtObj> mappings described in clauses 6.4.1 and 6.4.5 shall apply, and no specific mapping is necessary. In addition to the status code mapping for the <mgmtObj> CRUD Operations, no [reboot] specific status codes are defined in [5]. |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 6.5 LwM2M Server Interactions | |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 6.5.0 Introduction | Clause 6.5 describes how the IN-CSE interacts with a LwM2M Server in order to manage the devices. The interaction between the IN-CSE and the LwM2M Server includes the following: • Communication session establishment. • Translations for requests/responses and notifications between the oneM2M service layer and the LwM2M ... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 6.5.1 Communication Session Establishment | The communication session can be initiated by the IN-CSE or by the LwM2M Server. The IN-CSE can initiate the communication session if the IN-CSE needs to interact with the LwM2M Objects in the device through the LwM2M Server (e.g. an IN-AE sends firmware update Requests by using the [firmware] Resource in the IN-CSE). ... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 6.5.3 Discovery and Subscription for LwM2M Objects | Being triggered by oneM2M service layer, the interactions between the IN-CSE and the LwM2M Server can provide the following functionalities: • Discovery of LwM2M Objects in the devices of interest. • Subscription to LwM2M Objects for being notified for the interested events. With the discovery and the subscription to t... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 6.5.4 Access Control Management | For a device under managements, the IN-CSE can have multiple LwM2M Servers that can connect to the device. When receiving the oneM2M service layer Requests, the IN-CSE shall first authorize the Request based on the <accessControlPoilicy> resource associated with the addressed <mgmtObj> resource, Then, among those LwM2M... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 6.6 New LwM2M Objects | |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 6.6.0 Introduction | These LwM2M Objects are specified by oneM2M organization. They have to be registered using the process defined by OMNA (Open Mobile Naming Authority). The Object ID (e.g. "X") of the LwM2M Objects specified here, shall be allocated by OMNA, and will be in the range [2 048 - 10 240]. |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 6.6.1 LwM2M CMDH Policy Objects | |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 6.6.1.0 Introduction | The LwM2M Objects specified here are used for mapping the CMDH Policy Resources defined in oneM2M. This oneM2M CMDH Policy mapping is addressed through the specification of 10 specific LwM2M Objects registered in OMNA: • CmdhPolicy Object (urn:oma:lwm2m:ext:2048) • ActiveCmdhPolicy Object (urn:oma:lwm2m:ext:2049) • Cmd... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 6.6.1.1 CmdhPolicy Object | The CmdhPolicy Object provides links to set of rules associated with a specific CSE that governs the behavior of that CSE regarding rejecting, buffering and sending request or response messages via the Mcc reference point. Table 6.6.1.1-1: Object definition Name Object ID Instances Mandatory Object URN CmdhPolicy 2048 ... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 6.6.1.2 ActiveCmdhPolicy Object | The ActiveCmdhPolicy Object provides a link to the currently active set of CMDH policies. Table 6.6.1.2-1: Object definition Name Object ID Instances Mandatory Object URN ActiveCmdhPolicy 2049 Single Optional urn:oma:lwm2m:ext:2049 Table 6.6.1.2-2: Resource definitions ID Name Operations Instances Mandatory Type Range ... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 6.6.1.3 CmdhDefaults Object | The CmdhDefaults Object defines which CMDH related parameters will be used by default when a request or response message contains the Event Category parameter but not any other CMDH related parameters and which default Event Category parameter shall be used when none is given in the request or response message. ETSI ET... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 6.6.1.4 CmdhDefEcValues Object | The CmdhDefEcValues Object represents the default set of values for the Event Category parameter of an incoming request or response message. Table 6.6.1.4-1: Object definition Name Object ID Instances Mandatory Object URN CmdhDefEcValues 2051 Multiple Optional urn:oma:lwm2m:ext:2051 Table 6.6.1.4-2: Resource definition... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 6.6.1.5 CmdhEcDefParamValues Object | The CmdhEcDefParamValues Object represents a specific set of default values for the CMDH related parameters Request Expiration Timestamp, Result Expiration Timestamp, Operational Execution Time, Result Persistence and Delivery Aggregation that are applicable for a given Event Category if these parameters are not specif... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 6.6.1.6 CmdhLimits Object | The CmdhLimits Object represents limits for CMDH related parameter values. Table 6.6.1.6-1: Object definition Name Object ID Instances Mandatory Object URN CmdhLimits 2053 Multiple Optional urn:oma:lwm2m:ext:2053 Table 6.6.1.6-2: Resource definitions ID Name Operations Instances Mandatory Type Range or Enumeration Unit... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 6.6.1.7 CmdhNetworkAccessRules Object | The CmdhNetworkAccessRules Object defines the usage of underlying networks for forwarding information to other CSEs during processing of CMDH-related requests in a CSE. Table 6.6.1.7-1: Object definition Name Object ID Instances Mandatory Object URN CmdhNetworkAccessRules 2054 Multiple Optional urn:oma:lwm2m:ext:2054 T... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 6.6.1.8 CmdhNwAccessRule Object | The CmdhNwAccessRule Object defines limits in usage of specific underlying networks for forwarding information to other CSEs during processing of CMDH-related requests in a CSE. Table 6.6.1.8-1: Object definition Name Object ID Instances Mandatory Object URN CmdhNwAccessRule 2055 Multiple Optional urn:oma:lwm2m:ext:205... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 6.6.1.9 CmdhBuffer Object | The CmdhBuffer Object defines limits in usage of buffers for temporarily storing information that needs to be forwarded to other CSEs during processing of CMDH-related requests in a CSE. Table 6.6.1.9-1: Object definition Name Object ID Instances Mandatory Object URN CmdhBuffer 2056 Multiple Optional urn:oma:lwm2m:ext:... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 6.6.1.10 CmdhBackOffParametersSet Object | The CmdhBackOffParametersSet Object defines set of parameters which can be referenced by a specific Instance of the CmdhNwAccessRule Object (ID: 2055). Table 6.6.1.10-1: Object definition Name Object ID Instances Mandatory Object URN CmdhBackOffParamet ersSet 2057 Multiple Optional urn:oma:lwm2m:ext:2057 Table 6.6.1.10... |
d87eb3f66919df49f65eccf89c57cbd3 | 118 102 | 1 Scope | The present document contains an informative functional role model and normative technical requirements for oneM2M. |
d87eb3f66919df49f65eccf89c57cbd3 | 118 102 | 2 References | |
d87eb3f66919df49f65eccf89c57cbd3 | 118 102 | 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... |
d87eb3f66919df49f65eccf89c57cbd3 | 118 102 | 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... |
d87eb3f66919df49f65eccf89c57cbd3 | 118 102 | 3 Definition of terms, symbols and abbreviations | |
d87eb3f66919df49f65eccf89c57cbd3 | 118 102 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TS 118 111 [i.2] apply. ETSI ETSI TS 118 102 V3.1.2 (2021-01) 6 oneM2M TS-0002 version 3.1.2 Release 3 |
d87eb3f66919df49f65eccf89c57cbd3 | 118 102 | 3.2 Symbols | Void. |
d87eb3f66919df49f65eccf89c57cbd3 | 118 102 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: AE Application Entity API Application Program Interface BBF BroadBand Forum CHA Continua Health Alliance CMDH Communication Management and Delivery Handling CPU Central Processing Unit CSE Common Services Entity DM Device Management GBA Generi... |
d87eb3f66919df49f65eccf89c57cbd3 | 118 102 | 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]. ETSI ETSI TS 118 102 V3.1.2 (2021-01) 7 oneM2M TS-0002 version 3.1.2 Release 3 |
d87eb3f66919df49f65eccf89c57cbd3 | 118 102 | 5 Introduction to the M2M ecosystem | |
d87eb3f66919df49f65eccf89c57cbd3 | 118 102 | 5.1 Functional roles description | M2M Application M2M Common Service M2M Appl. M2M CS Underlying Network M2M Service Providers Network Operators operates operates operates an M2M Solution …. … … (end) user Connectivity Services Underlying Network M2M Common Services M2M Applications Application Service Providers Figure 1: Functional Roles in the M2M Ec... |
d87eb3f66919df49f65eccf89c57cbd3 | 118 102 | 6 Functional Requirements | |
d87eb3f66919df49f65eccf89c57cbd3 | 118 102 | 6.1 Overall System Requirements | Table 1: Overall System Requirements Requirement ID Description Release OSR-001 The oneM2M System shall allow communication between M2M Applications by using multiple communication means based on IP access. Implemented in Rel-1 OSR-002a The oneM2M System shall support communication means that can accommodate devices wi... |
d87eb3f66919df49f65eccf89c57cbd3 | 118 102 | 6.2 Management Requirements | Table 2: Management Requirements Requirement ID Description Release MGR-001 The oneM2M System shall be able to support management and configuration of M2M Gateways/ Devices including resource constrained M2M Devices. Implemented in Rel-1 MGR-002 The oneM2M System shall provide the capability to discover the M2M Area Ne... |
d87eb3f66919df49f65eccf89c57cbd3 | 118 102 | 6.3 Semantics Requirements | |
d87eb3f66919df49f65eccf89c57cbd3 | 118 102 | 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 (in... |
d87eb3f66919df49f65eccf89c57cbd3 | 118 102 | 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 Th... |
d87eb3f66919df49f65eccf89c57cbd3 | 118 102 | 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 |
d87eb3f66919df49f65eccf89c57cbd3 | 118 102 | 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 f... |
d87eb3f66919df49f65eccf89c57cbd3 | 118 102 | 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... |
d87eb3f66919df49f65eccf89c57cbd3 | 118 102 | 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... |
d87eb3f66919df49f65eccf89c57cbd3 | 118 102 | 6.4 Security Requirements | Table 9: Security Requirements Requirement ID Description Release SER-001 The oneM2M System shall incorporate protection against threats to its availability such as Denial of Service attacks. Partially implemented in Rel-1 SER-002 The oneM2M System shall be able to ensure the Confidentiality of data. Implemented in Rel... |
d87eb3f66919df49f65eccf89c57cbd3 | 118 102 | 6.5 Charging Requirements | Table 10: Charging Requirements Requirement ID Description Release CHG-001 The oneM2M System shall support collection of charging specific information related to the individual services facilitated by the oneM2M System (e.g. Data Management, Device Management and/or Connectivity Management). Collection of charging spec... |
d87eb3f66919df49f65eccf89c57cbd3 | 118 102 | 6.6 Operational Requirements | Table 11: Operational Requirements Requirement ID Description Release OPR-001 The oneM2M System shall provide the capability for monitoring and diagnostics of M2M Applications. Implemented in Rel-1 OPR-002 The oneM2M System shall provide the capability for software management of M2M Applications. Implemented in Rel-1 O... |
d87eb3f66919df49f65eccf89c57cbd3 | 118 102 | 6.7 Communication Management Requirements | Table 12: Communication Management Requirements Requirement ID Description Release CMR-001 The oneM2M System shall provide to M2M Applications a communication service which provides buffering of messages to/from M2M Gateway/Device/ Infrastructure Domain. Implemented in Rel-1 CMR-002 The oneM2M System shall be able to s... |
d87eb3f66919df49f65eccf89c57cbd3 | 118 102 | 6.8 LWM2M Interworking Requirements | Table 13: LWM2M Interworking Requirements Requirement ID Description Release LWM2M-001 See REQ-2015- 0517R04 The oneM2M System shall provide the capability to transparently transport LWM2M Objects between LWM2M Clients and M2M Applications. Implemented in Rel-2 LWM2M-002 See REQ-2015- 0517R04 The oneM2M System shall pr... |
d87eb3f66919df49f65eccf89c57cbd3 | 118 102 | 7 Non-Functional Requirements (informative) | This clause is intended to gather high-level principles and guidelines that shall govern the design of the oneM2M System. Such principles and guidelines are fundamental to the design of the oneM2M System. But as they cannot necessarily be expressed as requirements per se, they shall be introduced and expressed in this ... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 1 Scope | The present document describes the protocol mappings between the management Resources for oneM2M and the BBF TR-181 [6]. |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 2 References | |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 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... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.