hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
d0275cfa012b563611bd35833e616d99 | 118 110 | 6.4.3 Listening for and responding to a Request | A Receiver listens for requests arriving via MQTT by subscribing using a wildcarded Topic Filter of the following form: • /oneM2M/req/+/<receiver>/<type>: - "oneM2M" is a literal string identifying the topic as being used by oneM2M. - + is a wildcard which matches any entity. - <receiver> is the SP-relative-AE-ID or SP... |
d0275cfa012b563611bd35833e616d99 | 118 110 | 6.4.4 Initial Registration | In some security scenarios, an Originator might not initially know its AE-ID or CSE-ID. Initial registration exchanges can use the communication pattern described in clauses 6.4.1 and 6.4.2 except that they use Topics containing a credential ID rather than an AE-ID or CSE-ID, as follows: • /oneM2M/reg_req/<originator>/... |
d0275cfa012b563611bd35833e616d99 | 118 110 | 6.4.5 Request/Response Message Flow (Mca or Mcc) | MQTT Domain Non-MQTT Domain AE MQTT Client MQTT Server MQTT Client CSE Initiate Initiate Non-MQTT Domain SUBACK SUBSCRIBE SUBSCRIBE SUBACK CONNACK CONNECT CONNECT CONNACK (/oneM2M/req/+/SP-relative-AE-ID, /oneM2M/resp/SP-relative-AE-ID/+) (/oneM2M/req/+/SP-relative-CSE-ID, /oneM2M/resp/SP-relative-CSE-ID/+) Figure 6.4.... |
d0275cfa012b563611bd35833e616d99 | 118 110 | 6.5 Primitive Mapping | |
d0275cfa012b563611bd35833e616d99 | 118 110 | 6.5.1 Request primitives | A oneM2M request primitive is made up of a number of control parameters and (optionally) a content part. All the parameters in these parts are serialized into the payload of an MQTT Publish Packet, using the rules given in clause 8 of ETSI TS 118 104 [3] applied to m2m:requestPrimitive defined in clause 6.4.1 of ETSI T... |
d0275cfa012b563611bd35833e616d99 | 118 110 | 6.5.2 Response primitives | A oneM2M response primitive is serialized using the rules given in clause 8 of ETSI TS 118 104 [3] applied to m2m:responsePrimitive defined in clause 6.4.2 of ETSI TS 118 104 [3]. In particular, each response primitive shall include the Response Status Code parameter to indicate success or failure of the operation and ... |
d0275cfa012b563611bd35833e616d99 | 118 110 | 6.5.3 Serialization Format Negotiation | When sending a response primitive over MQTT, the Receiver should use the same serialization that was used in the corresponding request primitive. |
d0275cfa012b563611bd35833e616d99 | 118 110 | 6.5.4 Content-type | An MQTT message payload contains a oneM2M request or response primitive which is serialized using the XML, the JSON or the CBOR encoding given in clause 8 of ETSI TS 118 104 [3]. When an MQTT client publishes a message, it shall use a Topic name to indicate the format of the payload included in a PUBLISH message. As de... |
d0275cfa012b563611bd35833e616d99 | 118 110 | 6.6 URI format | oneM2M defines an MQTT URI format to be used in the pointOfAccess attributes in several entity resource types (e.g. <CSEBase>, <remoteCSE>, <AE>) and also in the Response Type parameter and in the notificationURI attributes of the <subscription> resource type. A pointOfAccess attribute contains a list of one or more st... |
d0275cfa012b563611bd35833e616d99 | 118 110 | 7 Security | |
d0275cfa012b563611bd35833e616d99 | 118 110 | 7.1 Introduction | The MQTT servers authenticate the clients (both CSEs and AEs) that connect to them and authorize access to Topics used to communicate. The clients do not authenticate each other, instead they use the MQTT server to do this. ETSI ETSI TS 118 110 V4.0.1 (2023-08) 25 oneM2M TS-0010 version 4.0.1 Release 4 Background. The ... |
d0275cfa012b563611bd35833e616d99 | 118 110 | 7.2 Authorization | There are two levels of authorization in the oneM2M binding to MQTT: • The MQTT Server is responsible for verifying identifiers, for routing messages to the expected CSE or AE, and providing the correct Credential-ID during initial registration The MQTT Server is responsible for verifying that the Client Identifier fie... |
d0275cfa012b563611bd35833e616d99 | 118 110 | 7.3 Authentication | An MQTT Client and MQTT Server shall apply Transport Layer Security (TLS) using any of the Security Association Establishment Frameworks in ETSI TS 118 103 [7]. ETSI ETSI TS 118 110 V4.0.1 (2023-08) 26 oneM2M TS-0010 version 4.0.1 Release 4 The Security Association Establishment Frameworks provide mutual authentication... |
d0275cfa012b563611bd35833e616d99 | 118 110 | 7.4 Authorization by the MQTT Server | This procedure describes how an MQTT Server authorizes topics to which an MQTT Client may subscribe. The M2M Service Provider is responsible for configuring the MQTT Server with the relevant information used in these authorization decisions: 1) In the case that the MQTT Server determines that the MQTT Client represents... |
d0275cfa012b563611bd35833e616d99 | 118 110 | 7.5 General Considerations | Implementors should take note of the Security considerations listed in chapter 5 of the MQTT Specification [1]. ETSI ETSI TS 118 110 V4.0.1 (2023-08) 28 oneM2M TS-0010 version 4.0.1 Release 4 Annex A (informative): Overview of MQTT A.0 Introduction This annex provides some background information on MQTT that might be u... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 1 Scope | The present document specifies the protocol translation and mappings between the oneM2M service layer and the management technologies specified by OMA such as OMA DM 1.3, OMA DM 2.0 and OMA LightweightM2M. Note that OMA DM 1.3 and OMA DM 2.0 are collectively referenced as OMA DM in the present document. |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 2 References | |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 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... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 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... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 3 Definition of terms, symbols and abbreviations | |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TS 118 111 [i.2] apply. |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 3.2 Symbols | Void. |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 3.3 Abbreviations | Void. |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 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]. |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5 OMA DM 1.3 and OMA DM 2.0 | |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5.1 Mapping of basic data types | oneM2M has defined the data types that describe the format of the value stored with the attribute. Those oneM2M data types are listed in table 5.1-1, and mapped to the data types specified by OMA DM Protocol [3] and [4]. Note that OMA DM 1.3 [3] and OMA DM 2.0 [4] use the same data types. ETSI ETSI TS 118 105 V4.0.1 (2... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5.2 Mapping of Identifiers | OMA DM 1.3 and OMA DM 2.0 specify many identifiers including device identifier, server identifier, client version identifier, manufacturer identifier, etc. To enable the device management using OMA DM Protocol, oneM2M identifiers needs to be mapped to identifiers specified by OMA DM Protocol. Table 5.2-1 shows the oneM... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5.3 Mapping of resources | |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5.3.0 Introduction | Clause 5.3 describes how to map <mgmtObj> resources specified in annex D of ETSI TS 118 101 [1] to the relevant management objects as defined by OMA DM ([3] and [4]). Since OMA DM 1.3 and OMA DM 2.0 use the same management objects except standard management objects, the resource mappings can be considered regardless of... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5.3.1 General Mapping Assumptions | OMA DM Protocol implements the management functionalities by using the Management Objects. Management Object is a collection of Nodes which are related for providing certain management functionalities. EXAMPLE: SCOMO is for the software management, and FUMO is for the firmware update, and so on. The individual manageme... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5.3.2 Resource [firmware] | The resource [firmware] is for firmware management in the service layer. Regardless of OMA DM 1.3 and OMA DM 2.0, the resource shall be mapped to FUMO (urn:oma:mo:omafumo:1.0). The attributes of the resource shall be mapped to nodes of the MO as follows. Table 5.3.2-1: Resource [firmware] Attribute Name of [firmware] M... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5.3.3 Resource [software] | The resource [software] is for software management in the service layer. Regardless of OMA DM 1.3 and OMA DM 2.0, the resource shall be mapped to SCOMO (urn:oma:mo:oma-scomo:1.0). The attributes of the resource shall be mapped to nodes of the MO as the follows. ETSI ETSI TS 118 105 V4.0.1 (2025-09) 11 oneM2M TS-0005 ve... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5.3.4 Resource [memory] | The resource [memory] is for acquire information about the total memory or available memory of the device. Regardless of OMA DM 1.3 and OMA DM 2.0, the resource shall be mapped to memory information of DiagMO (urn:oma:mo:oma-diag:memory:1.0). The attributes of the resource shall be mapped to nodes of the MO as follows.... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5.3.5 Resource [areaNwkInfo] | The resource [areaNwkInfo] is for managing the area network. Regardless of OMA DM 1.3 and OMA DM 2.0, the resource shall be mapped to MANMO (urn:oma:mo:ext-etsi-manmo:1.0). The attributes of the resource shall be mapped to nodes of the MO as follows. Table 5.3.5-1: Resource [areaNwkInfo] Attribute Name of [areaNwkInfo]... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5.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. Regardless of OMA DM 1.3 and OMA DM 2.0, the resource shall be mapped to MANDMO (urn:oma:mo:ext-etsi-mandmo:1.0). The attributes of the resource shall be mapped to nodes of... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5.3.7 Resource [battery] | The Resource [battery] is to provide battery related information. Regardless of OMA DM 1.3 and OMA DM 2.0, this Resource shall be mapped to Battery Info Management Object (MOID: "urn:oma:mo:oma-diag:batteryinfo:1.0"). The attributes of this Resource shall be mapped to Nodes in the Management Object as follows. Table 5.... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5.3.8 Resource [deviceInfo] | The Resource [deviceInfo] is to provide device related information. For OMA DM 1.3, this Resource shall be mapped to DevInfo MO (MOID: "urn:oma:mo:oma-dm-devinfo:1.1") and DevDetail MO (MOID: "urn:oma:mo:oma-dm- devdetail:1.1"). The attributes of this Resource shall be mapped to Nodes in two Management Objects as follo... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5.3.9 Resource [deviceCapability] | The Resource [deviceCapability] is to manage the device capabilities such USB, camera, etc. Regardless of OMA DM 1.3 and OMA DM 2.0, this Resource shall be mapped to Device Capability Management Object (MOID: "urn:oma:mo:oma-dcmo:1.0"). The attributes of this Resource shall be mapped to Nodes in the Management Object a... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5.3.10 Resource [reboot] | The Resource [reboot] is to reboot the device. Regardless of OMA DM 1.3 and OMA DM 2.0, this Resource shall be mapped to Restart Management Object (MOID: "urn:oma:mo:oma-diag:restart:1.0") that is specified in DiagMon [6] and Lock and Wipe Management Object (MOID: "urn:oma:mo:oma-lawmo:1.0"). The attributes of this Res... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5.3.11 Resource [eventLog] | The Resource [eventLog] is to record the event log for the device. Regardless of OMA DM 1.3 and OMA DM 2.0, this Resource shall be mapped to several Management Objects according to the logTypeId attribute of this Resource as follows: • Trap Event Logging Function Management Object (MOID: "urn:oma:mo:oma-diag:trapeventl... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5.3.12 Resource [cmdhPolicy] | |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5.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 | 5.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] and ETSI TS 118 104 [2]. The Resource [activeCmdhPolicy] includes an attribute activeCmdhPolicyLink which is mapped to a leaf node enable. The value of enable shall point to the current... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5.3.12.2 Resource [cmdhDefaults] | The Resource [cmdhDefaults] 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, see clauses... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5.3.12.3 Resource [cmdhDefEcValue] | The Resource [cmdhDefEcValue] represents a default value for the ec (event category) parameter of an incoming request or response when this parameter is not indicated in the message itself, see clauses D.12.3 of ETSI TS 118 101 [1] and ETSI TS 118 104 [2]. Regardless of OMA DM 1.3 and OMA DM 2.0, this resource shall be... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5.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 | 5.3.12.5 Resource [cmdhLimits] | The Resource [cmdhLimits] represents limits for CMDH related parameter values in request and response messages for a given setting of the ec parameter, see clause D.12.5 of ETSI TS 118 101 [1] and ETSI TS 118 104 [2]. Regardless of OMA DM 1.3 and OMA DM 2.0, this resource shall be mapped to M2M cmdhPolicies MO (MCMDHMO... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5.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 clauses D.12.6 of ETSI TS 118 101 [1] and ETSI TS 118 104 [2]. Regardless of OMA DM 1.3 and OMA DM 2.0, this resource shall be mapped to M2M cm... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5.3.12.7 Resource [cmdhNwAccessRule] | The Resource [cmdhNwAccessRule] define limits in usage of specific underlying networks for forwarding information to other CSEs during processing of CMDH-related requests, see clauses D.12.7 of ETSI TS 118 101 [1] and ETSI TS 118 104 [2]. Regardless of OMA DM 1.3 and OMA DM 2.0, this resource shall be mapped to M2M cmd... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5.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 clauses D.12.8 of ETSI TS 118 101 [1] and ETSI TS 118 104 [2]. Regardless of OMA DM 1.3 and OMA DM 2.0, this resource shal... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5.3.13 Resource related to Field Device Configuration | |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5.3.13.1 Introduction | The Resource Types addressed in clause 5.3.13 represent <mgmtObj> specializations required to configure ADN, ASN and MN in the field domain. These resource types and the related specific procedures are specified in ETSI TS 118 122 [20]. Clause 5.3.13.2 to clause 5.3.13.8 define the mapping to and from a M2M FieldDevice... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5.3.13.2 Resource [registration] | The Resource [registration] is used to convey the service layer configuration information needed to register an AE or CSE with a Registrar CSE, see clause 7.1.2 of ETSI TS 118 122 [20]. Regardless of OMA DM 1.3 and OMA DM 2.0, this resource shall be mapped to M2M FieldDeviceConfig MO (MFDCMO) (urn:oma:mo:ext-onem2m-mfd... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5.3.13.3 Resource [dataCollection] | The Resource [dataCollection] is used to convey the application configuration information needed by an AE to collect data and then transmit the data to a Hosting CSE, see clause 7.1.3 of ETSI TS 118 122 [20]. Regardless of OMA DM 1.3 and OMA DM 2.0, this resource shall be mapped to M2M FieldDeviceConfig MO (MFDCMO) (ur... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5.3.13.4 Resource [authenticationProfile] | The Resource [authenticationProfile] is used to convey the configuration information regarding establishing mutually- authenticated secure communications, see clause 7.1.4 of ETSI TS 118 122 [20]. Regardless of OMA DM 1.3 and OMA DM 2.0, this resource shall be mapped to M2M FieldDeviceConfig MO (MFDCMO) (urn:oma:mo:ext... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5.3.13.5 Resource [trustAnchorCred] | The Resource [trustAnchorCred] represents configuration information regarding certificates provided by certificate authorities used be managed entities to authenticate peer endpoints, see clause 7.1.6 of ETSI TS 118 122 [20]. Regardless of OMA DM 1.3 and OMA DM 2.0, this resource shall be mapped to M2M FieldDeviceConfi... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5.3.13.6 Resource [myCertFileCred] | The Resource [myCertFileCred] represents configuration information regarding certificates presented by the managed entity to remote entities for the establishment of secure communications, see clause 7.1.5 of ETSI TS 118 122 [20]. Regardless of OMA DM 1.3 and OMA DM 2.0, this resource shall be mapped to M2M FieldDevice... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5.3.13.7 Resource [MAFClientRegCfg] | The Resource [MAFClientRegCfg] represents configuration information that permits a MAF client to register with a MAF, see clause 7.1.7 of ETSI TS 118 122 [20]. Regardless of OMA DM 1.3 and OMA DM 2.0, this resource shall be mapped to M2M FieldDeviceConfig MO (MFDCMO) (urn:oma:mo:ext-onem2m-mfdcmo:1.0). The Resource [MA... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5.3.13.8 Resource [MEFClientRegCfg] | The Resource [MEFClientRegCfg] represents configuration information that permits a MEF client to register with a MEF, see clause 7.1.8 of ETSI TS 118 122 [20]. Regardless of OMA DM 1.3 and OMA DM 2.0, this resource shall be mapped to M2M FieldDeviceConfig MO (MFDCMO) (urn:oma:mo:ext-onem2m-mfdcmo:1.0). The Resource [ME... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5.4 Mapping of procedures for management | |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5.4.1 Mapping for <mgmtObj> Resource Primitives | |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5.4.1.1 Create Primitive for <mgmtObj> Resource | |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5.4.1.1.0 Introduction | The Create Request primitive for the <mgmtObj> Resource, as described in ETSI TS 118 104 [2], shall be mapped to technology specific requests that create the corresponding OMA DM Management Objects. Depending on the type of the <mgmtObj> Resource (i.e. [memory], [battery], [deviceInfo], etc.), the associated OMA DM Man... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5.4.1.1.1 Create Response Status Code Mapping | The result of creating the technology specific data model object should be mapped to the Create Response primitive for the <mgmtObj> Resource as indicated by the status code mapping in the present clause. Table 5.4.1.1.1-1: OMA DM 1.3 Status Code Mapping oneM2M Primitive Status Code OMA DM 1.3 Status Code Description s... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5.4.1.2 Retrieve Primitive for <mgmtObj> Resource | |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5.4.1.2.0 Introduction | The Retrieve Request primitive for the <mgmtObj> Resource, as described in ETSI TS 118 104 [2], shall be mapped to technology specific requests that retrieve the corresponding OMA DM Management Objects. Depending on the type of the <mgmtObj> Resource (i.e. [memory], [battery], [deviceInfo], etc.), the associated OMA DM... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5.4.1.2.1 Retrieve Response Status Code Mapping | The result of retrieving the technology specific data model object should be mapped to the Retrieve Response primitive for the <mgmtObj> Resource as indicated by the status code mapping in the present clause. ETSI ETSI TS 118 105 V4.0.1 (2025-09) 24 oneM2M TS-0005 version 4.0.1 Release 4 Table 5.4.1.2.1-1: OMA DM 1.3 S... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5.4.1.3 Update Primitive for <mgmtObj> Resource | |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5.4.1.3.0 Introduction | The Update Request Primitive for <mgmtObj> Resource can be used to modify the technology specific data model objects or to execute the management commands. The mapping in either case shall be different as clause 5.4.1.3.1 and clause 5.4.1.3.2 specify. |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5.4.1.3.1 Update Primitive for Replacing Data in the Management Object | 5.4.1.3.1.0 Introduction This is the case that the Update Primitive targets the attribute that is mapped to the non-executable Node in technology specific data model object as specified in clause 6.3. The Update Request primitive for the <mgmtObj> Resource, as described in ETSI TS 118 104 [2], shall be mapped to techno... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5.4.1.3.2 Update Primitive for Executing Management Commands | 5.4.1.3.2.0 Introduction This is the case that the Update Primitive targets the attribute that is mapped to the executable Node in technology specific data model object as specified in clause 6.3. The Update Request primitive for the <mgmtObj> Resource, as described in ETSI TS 118 104 [2], shall be mapped to technology... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5.4.1.4 Delete Primitive for <mgmtObj> Resource | |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5.4.1.4.0 Introduction | The Delete Request primitive for the <mgmtObj> Resource, as described in ETSI TS 118 104 [2], shall be mapped to technology specific requests that delete the corresponding OMA DM Management Objects. Depending on the type of the <mgmtObj> Resource (i.e. [memory], [battery], [deviceInfo], etc.), the associated OMA DM Man... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5.4.1.4.1 Delete Response Status Code Mapping | The result of deleting the technology specific data model object should be mapped to the Delete Response primitive for the <mgmtObj> Resource as indicated by the status code mapping in the present clause. Table 5.4.1.4.1-1: OMA DM 1.3 Status Code Mapping oneM2M Primitive Status Code OMA DM 1.3 Status Code Description s... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5.4.1.5 Notify Primitive Mapping | |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5.4.1.5.0 Introduction | The Notify Request and Response primitives permit notifications to AE or CSEs that have subscribed to a Resource. When the AE and CSE have been subscribed to the <mgmtObj> Resource, the <mgmtObj> Resource hosting CSE will send the notification to the subscriber if the <mgmtObj> Resource has been changed according to th... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5.4.1.5.1 Subscribe Procedure Mapping for OMA DM 1.3 | OMA DM 1.3 does not have the subscription mechanism that notifies the DM Server when the management objects in the device have been changed. The optional alerts DM_TREE_UNCHANGED_ALERT and DM_TREE_CHANGED_ALERT can indicate the changes occurred in the DM Tree, but those alerts are not sent to the DM Server at the time ... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5.4.1.5.2 Subscribe Procedure Mapping for OMA DM 2.0 | OMA DM 2.0 provides the SUB command that subscribe to any change occurring in a certain part of the DM Tree. When a change occurs, the DM Client will send a notification message with the changed management objects that has been subscribed. The <mgmtObj> Resource hosting CSE can use the SUB command to detect the changes... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5.4.1.5.3 Notification Procedure Mapping for OMA DM 1.3 and OMA DM 2.0 | After the subscription procedures are mapped as described in clauses 5.4.1.5.1 and 5.4.1.5.2, the <mgmtObj> Resource hosting CSE is being capable of monitoring changes for management objects in the device. By monitoring those changes for management objects, the <mgmtObj> Resource hosting CSE keeps the <mgmtObj> updated... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5.4.2 Management Resource Specific Procedure Mapping | |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5.4.2.0 Introduction | In clause 5.4.2, mappings specific to the Management Resource are described. |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5.4.2.1 Resource [firmware] | The generic <mgmtObj> mappings described in clause 5.4.1 shall apply, and no specific mapping is necessary. In addition to the status code mapping for the <mgmtObj> CRUD Operations, FUMO [7] specifies the status codes that are exclusive for FUMO. Those status codes will be used only for the execute command and shall be... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5.4.2.2 Resource [software] | The generic <mgmtObj> mappings described in clause 5.4.1 shall apply, and no specific mapping is necessary. In addition to the status code mapping for the <mgmtObj> CRUD Operations, SCOMO [8] specifies the status codes that are exclusive for SCOMO. Those status codes will be used only for the execute command and shall ... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5.4.2.3 Resource [memory] | The generic <mgmtObj> mappings described in clause 5.4.1 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 [6]. |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5.4.2.4 Resource [areaNwkInfo] | The generic <mgmtObj> mappings described in clause 5.4.1 shall apply, and no specific mapping is necessary. In addition to the status code mapping for the <mgmtObj> CRUD Operations, no [areaNwkDeviceInfo] specific status codes are defined in ETSI TS 103 092 [9]. |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5.4.2.5 Resource [areaNwkDeviceInfo] | The generic <mgmtObj> mappings described in clause 5.4.1 shall apply, and no specific mapping is necessary. In addition to the status code mapping for the <mgmtObj> CRUD Operations, no [areaNwkDeviceInfo] specific status codes are defined in ETSI TS 103 092 [9]. |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5.4.2.6 Resource [battery] | The generic <mgmtObj> mappings described in clause 5.4.1 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 [6]. |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5.4.2.7 Resource [deviceInfo] | The generic <mgmtObj> mappings described in clause 5.4.1 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 [3] and [4]. |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5.4.2.8 Resource [deviceCapability] | The generic <mgmtObj> mappings described in clause 5.4.1 shall apply, and no specific mapping is necessary. In addition to the status code mapping for the <mgmtObj> CRUD Operations, DCMO [10] specifies the status codes that are exclusive for DCMO. Those status codes will be used only for the execute command and shall b... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5.4.2.9 Resource [reboot] | The generic <mgmtObj> mappings described in clause 5.4.1 shall apply, and no specific mapping is necessary. The status code mappings specific for executing the reboot attribute in the [reboot] Resource does not require additional mapping other than the status code mapping for the <mgmtObj> CRUD Operations. In addition ... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5.4.2.10 Resource [eventLog] | The generic <mgmtObj> mappings described in clause 5.4.1 shall apply, and no specific mapping is necessary. In addition to the status code mapping for the <mgmtObj> CRUD Operations, no [eventLog] specific status codes are defined in [6]. |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5.5 DM Server Interactions | |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5.5.0 Introduction | Clause 5.5 describes how the IN-CSE interacts with a DM Server in order to manage the devices. To interact with the DM Server, the IN-CSE needs to establish the communication session with the DM Server, translate requests/responses and notifications between the IN-CSE and the DM Server and discover the management objec... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5.5.1 Communication Session Establishment | The communication session can be initiated by the IN-CSE or by the DM Server. The IN-CSE can initiate the communication session if the IN-CSE needs to interact with the management objects in the device through the DM Server (e.g. an IN-AE sends firmware update Requests by using the [firmware] Resource in the IN-CSE). O... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5.5.3 Discovery and Subscription for management objects | Being triggered by oneM2M service layer, the interactions between the IN-CSE and the DM Server can provide the following functionalities: • Discovery of management objects in the devices of interest. • Subscription to management objects for being notified for the interested events. With the discovery and the subscripti... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5.5.4 Access Control Management | For a device under management, the IN-CSE can have multiple DM 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 <accessControlPolicy> resource associated with the addressed <mgmtObj> resource. Then, among those DM Servers... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5.6 New Management Objects | |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5.6.1 M2M CMDH Policies MO (MCMDHMO) | The M2M CMDH Policies MO (MCMDHMO) resides in the Management Tree of any ASN or MN which support Device Management via OMA DM 1.3 and OMA DM 2.0. This MO corresponds to instances of the cmdhPolicy resource and its child resources which all represent subtypes of the mgmtObj resource type, as specified in clause D.12 of ... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 5.6.2 M2M FieldDeviceConfig (MFDCMO) | The M2M FieldDeviceConfig MO (MFDCMO) resides in the Management Tree of any ADN, ASN or MN which supports Device Management via OMA DM 1.3 and OMA DM 2.0. This MO corresponds to instances of the Field Device Configuration resources specified in ETSI TS 118 122 [20] which all represent specializations of the mgmtObj res... |
723d756e9f5dffed4cc46c32ba12a9c2 | 118 105 | 6 OMA Lightweight M2M 1.0 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.