ETSI TS 118 105 V2.0.2 (2020-03)

TECHNICAL SPECIFICATION
oneM2M;
Management Enablement (OMA)
(oneM2M TS-0005 version 2.0.2 Release 2A)

oneM2M TS-0005 version 2.0.2 Release 2A 2 ETSI TS 118 105 V2.0.2 (2020-03)

Reference
RTS/oneM2M-000005v2A
Keywords
IoT, M2M
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: +33 4 92 94 42 00  Fax: +33 4 93 65 47 16

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
The present document can be downloaded from:
http://www.etsi.org/standards-search
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI
deliverable is the one made publicly available in PDF format at www.etsi.org/deliver.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© ETSI 2020.
All rights reserved.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.

3GPP™ and LTE™ are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and
of the oneM2M Partners. ®
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI
oneM2M TS-0005 version 2.0.2 Release 2A 3 ETSI TS 118 105 V2.0.2 (2020-03)
Contents
Intellectual Property Rights . 6
Foreword . 6
1 Scope . 7
2 References . 7
2.1 Normative references . 7
2.2 Informative references . 8
3 Definition of terms, symbols and abbreviations . 8
3.1 Terms . 8
3.2 Symbols . 8
3.3 Abbreviations . 9
4 Conventions . 9
5 OMA DM 1.3 and OMA DM 2.0 . 9
5.1 Mapping of basic data types . 9
5.2 Mapping of Identifiers . 9
5.3 Mapping of resources . 10
5.3.0 Introduction. 10
5.3.1 General Mapping Assumptions . 10
5.3.2 Resource [firmware] . 10
5.3.3 Resource [software] . 11
5.3.4 Resource [memory]. 11
5.3.5 Resource [areaNwkInfo] . 11
5.3.6 Resource [areaNwkDeviceInfo] . 12
5.3.7 Resource [battery] . 12
5.3.8 Resource [deviceInfo] . 12
5.3.9 Resource [deviceCapability] . 13
5.3.10 Resource [reboot] . 13
5.3.11 Resource [eventLog] . 13
5.3.12 Resource [cmdhPolicy] . 14
5.3.12.0 Introduction . 14
5.3.12.1 Resource [activeCmdhPolicy] . 14
5.3.12.2 Resource [cmdhDefaults] . 15
5.3.12.3 Resource [cmdhDefEcValue] . 15
5.3.12.4 Resource [cmdhEcDefParamValues] . 16
5.3.12.5 Resource [cmdhLimits] . 16
5.3.12.6 Resource [cmdhNetworkAccessRules] . 17
5.3.12.7 Resource [cmdhNwAccessRule] . 17
5.3.12.8 Resource [cmdhBuffer] . 17
5.4 Mapping of procedures for management . 18
5.4.1 Mapping for Resource Primitives . 18
5.4.1.1 Create Primitive for Resource . 18
5.4.1.1.0 Introduction . 18
5.4.1.1.1 Create Response Status Code Mapping . 18
5.4.1.2 Retrieve Primitive for Resource . 20
5.4.1.2.0 Introduction . 20
5.4.1.2.1 Retrieve Response Status Code Mapping . 20
5.4.1.3 Update Primitive for Resource . 22
5.4.1.3.0 Introduction . 22
5.4.1.3.1 Update Primitive for Replacing Data in the Management Object . 22
5.4.1.3.2 Update Primitive for Executing Management Commands . 24
5.4.1.4 Delete Primitive for Resource . 26
5.4.1.4.0 Introduction . 26
5.4.1.4.1 Delete Response Status Code Mapping . 26
5.4.1.5 Notify Primitive Mapping . 27
5.4.1.5.0 Introduction . 27
ETSI
oneM2M TS-0005 version 2.0.2 Release 2A 4 ETSI TS 118 105 V2.0.2 (2020-03)
5.4.1.5.1 Subscribe Procedure Mapping for OMA DM 1.3 . 27
5.4.1.5.2 Subscribe Procedure Mapping for OMA DM 2.0 . 27
5.4.1.5.3 Notification Procedure Mapping for OMA DM 1.3 and OMA DM 2.0 . 28
5.4.2 Management Resource Specific Procedure Mapping . 28
5.4.2.0 Introduction . 28
5.4.2.1 Resource [firmware]. 28
5.4.2.2 Resource [software] . 29
5.4.2.3 Resource [memory] . 30
5.4.2.4 Resource [areaNwkInfo] . 30
5.4.2.5 Resource [areaNwkDeviceInfo] . 30
5.4.2.6 Resource [battery] . 30
5.4.2.7 Resource [deviceInfo] . 30
5.4.2.8 Resource [deviceCapability] . 30
5.4.2.9 Resource [reboot] . 31
5.4.2.10 Resource [eventLog] . 31
5.5 DM Server Interactions . 31
5.5.0 Introduction. 31
5.5.1 Communication Session Establishment . 31
5.5.2 Translation of Requests and Responses between IN-CSE and DM Server. 32
5.5.3 Discovery and Subscription for management objects . 32
5.5.4 Access Control Management . 32
5.6 New Management Objects . 32
5.6.1 M2M CMDH Policies MO (MCMDHMO) . 32
6 OMA Lightweight M2M 1.0 . 43
6.1 Mapping of basic data types . 43
6.2 Mapping of Identifiers . 43
6.2.0 Introduction. 43
6.2.1 Device identifier . 43
6.2.2 Object identifier . 43
6.2.3 Object Instance Identifier . 44
6.3 Mapping of resources . 44
6.3.0 Introduction. 44
6.3.1 General Mapping Assumptions . 44
6.3.2 Resource [firmware] . 44
6.3.3 Resource [software] . 45
6.3.4 Resource [memory]. 45
6.3.5 Resource [areaNwkInfo] . 46
6.3.6 Resource [areaNwkDeviceInfo] . 46
6.3.7 Resource [battery] . 46
6.3.8 Resource [deviceInfo] . 46
6.3.9 Resource [deviceCapability] . 47
6.3.10 Resource [reboot] . 47
6.3.11 Resource [eventLog] . 48
6.3.12 Resource [cmdhPolicy] . 48
6.3.12.0 Introduction . 48
6.3.12.1 Resource [activeCmdhPolicy] . 49
6.3.12.2 Resource [cmdhDefaults] . 49
6.3.12.3 Resource [cmdhDefEcValue] . 50
6.3.12.4 Resource [cmdhEcDefParamValues] . 50
6.3.12.5 Resource [cmdhLimits] . 51
6.3.12.6 Resource [cmdhNetworkAccessRules] . 51
6.3.12.7 Resource [cmdhNwAccessRule] . 52
6.3.12.8 Resource [cmdhBuffer] . 52
6.4 Mapping of procedures for management . 53
6.4.0 Introduction. 53
6.4.1 Create primitive for Resource . 53
6.4.2 Retrieve primitive for Resource . 53
6.4.3 Update primitive for Resource . 54
6.4.3.0 Introduction . 54
6.4.3.1 Update primitive for replacing data . 54
6.4.3.2 Update primitive for execution operation . 54
ETSI
oneM2M TS-0005 version 2.0.2 Release 2A 5 ETSI TS 118 105 V2.0.2 (2020-03)
6.4.4 Delete primitive for Resource . 55
6.4.5 Notify Primitive for Resource . 55
6.4.5.0 Introduction . 55
6.4.5.1 Notify Primitive mapping for subscription to Resource attributes . 55
6.4.5.2 Notify Primitive mapping for subscription cancellation to Resource attributes . 56
6.4.5.3 Notify Primitive mapping for Notification . 56
6.4.6 Management Resource Specific Procedure Mapping . 56
6.4.6.1 Resource [firmware]. 56
6.4.6.2 Resource [software] . 56
6.4.6.3 Resource [memory] . 56
6.4.6.4 Resource [battery] . 56
6.4.6.5 Resource [deviceInfo] . 57
6.4.6.6 Resource [deviceCapability] . 57
6.4.6.7 Resource [reboot] . 57
6.5 LWM2M Server Interactions . 57
6.5.0 Introduction. 57
6.5.1 Communication Session Establishment . 57
6.5.2 Translation of Requests and Responses between IN-CSE and LWM2M Server . 58
6.5.3 Discovery and Subscription for LWM2M Objects . 58
6.5.4 Access Control Management . 58
6.6 New LWM2M Objects . 58
6.6.0 Introduction. 58
6.6.1 LWM2M CMDH Policy Objects . 58
6.6.1.0 Introduction . 58
6.6.1.1 CmdhPolicy Object . 59
6.6.1.2 ActiveCmdhPolicy Object . 59
6.6.1.3 CmdhDefaults Object . 59
6.6.1.4 CmdhDef ECValues Object . 60
6.6.1.5 CmdhDefaultsECParamValues Object . 60
6.6.1.6 CmdhLimits Object . 60
6.6.1.7 CmdhNetworkAccessRules Object . 61
6.6.1.8 CmdhNwAccessRule Object . 61
6.6.1.9 CmdhBuffer Object . 62
History . 63

ETSI
oneM2M TS-0005 version 2.0.2 Release 2A 6 ETSI TS 118 105 V2.0.2 (2020-03)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (https://ipr.etsi.org/).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
Foreword
This Technical Specification (TS) has been produced by ETSI Partnership Project oneM2M (oneM2M).
ETSI
oneM2M TS-0005 version 2.0.2 Release 2A 7 ETSI TS 118 105 V2.0.2 (2020-03)
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 [3], OMA DM 2.0 [4] and OMA LightweightM2M.
Note that OMA DM 1.3 [3] and OMA DM 2.0 [4] are collectively referenced as OMA DM in the present document.
2 References
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 are not found to be publicly available in the expected location might be found at
https://docbox.etsi.org/Reference/.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
The following referenced documents are necessary for the application of the present document.
[1] ETSI TS 118 101: "oneM2M; Functional Architecture (oneM2M TS-0001)".
[2] ETSI TS 118 104: "oneM2M; Service Layer Core Protocol Specification (oneM2M TS-0004)".
[3] Open Mobile Alliance™: "Device Management Protocol", Version 1.3.
NOTE: Available at http://www.openmobilealliance.org/release/DM/V1_3-20160524-A/OMA-TS-DM_Protocol-
V1_3-20160524-A.pdf.
[4] Open Mobile Alliance™: "Device Management Protocol", Version 2.0.
NOTE: Available at http://www.openmobilealliance.org/release/DM/V2_0-20160209-A.
[5] Open Mobile Alliance™: "LightweightM2M", Version 1.0.
NOTE: Available at http://www.openmobilealliance.org/release/LightweightM2M/V1_0-00000000-C/.
[6] Open Mobile Alliance™: "Diagnostics and Monitoring Management Object Framework".
NOTE: Available at https://www.openmobilealliance.org/release/DiagMon/V1_2-20131008-A/OMA-TS-
DiagMonMOFrame-V1_2-20131008-A.pdf.
[7] Open Mobile Alliance™: "Firmware Update Management Object".
NOTE: Available at http://www.openmobilealliance.org/release/FUMO/V1_0_4-20090828-A/.
[8] Open Mobile Alliance™: "Software Component Management Object (SCOMO)".
NOTE: Available at https://www.openmobilealliance.org/release/SCOMO/V1_1-20130521-A.
[9] ETSI TS 103 092: "Machine-to-Machine communications (M2M); OMA DM compatible
Management Objects for ETSI M2M".
[10] Open Mobile Alliance™: "Device Capability Management Object".
NOTE: Available at https://www.openmobilealliance.org/release/DCMO/V1_0-20120410-A/.
[11] Open Mobile Alliance™: "Management Interface to M2M Requirements".
NOTE: Available at http://openmobilealliance.org/release/M2Minterface/V1_0-20150324-A/.
ETSI
oneM2M TS-0005 version 2.0.2 Release 2A 8 ETSI TS 118 105 V2.0.2 (2020-03)
[12] ISO 8601:2019 (all parts): "Date and time -- Representations for information interchange".
NOTE: Available at https://www.iso.org/standard/26780.html.
[13] W3C Recommendation 28 October 2004: "XML Schema Part 2: Datatypes Second Edition".
NOTE: Available at http://www.w3.org/TR/xmlschema-2/.
[14] IETF RFC 4122 (July 2005): "A Universally Unique Identifier (UUID) URN Namespace",
P. Leach, et al.
NOTE: Available at http://www.ietf.org/rfc/rfc4122.txt.
[15] ETSI TS 123 003: " Digital cellular telecommunications system (Phase 2+) (GSM); Universal
Mobile Telecommunications System (UMTS); LTE; Numbering, addressing and identification
(3GPP TS 23.003)".
[16] BBF TR-069: "CPE WAN Management Protocol", Issue: 1 Amendment 5, November 2013.
NOTE: Available at https://www.broadband-forum.org/download/TR-069_Amendment-5.pdf.
[17] IETF RFC 7252: "The Constrained Application Protocol (CoAP)".
[18] Open Mobile Alliance™ (Version 1.0): "LightweightM2M - Software Management Object
(LwM2M Object - SwMgmt)".
NOTE: Available at http://www.openmobilealliance.org/release/LWM2M_SWMGMT/V1_0-20150217-C/OMA-
TS-LWM2M_SwMgmt-V1_0-20150217-C.pdf.
[19] Open Mobile Alliance™: "LightweightM2M - Device Capability Management Object".
NOTE: Available at http://openmobilealliance.org/release/LWM2M_DevCapMgmt/V1_0-20150120-C/OMA-
TS-LWM2M_DevCapMgmt-V1_0-20150120-C.pdf.
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 included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
The following referenced documents are not necessary for the application of the present document but they assist the
user with regard to a particular subject area.
[i.1] oneM2M Drafting Rules.
NOTE: Available at http://www.onem2m.org/images/files/oneM2M-Drafting-Rules.pdf.
[i.2] ETSI TS 118 111: "oneM2M; Common Terminology (oneM2M TS-0011)".
3 Definition of terms, symbols and abbreviations
3.1 Terms
For the purposes of the present document, the terms given in ETSI TS 118 111 [i.2] apply.
3.2 Symbols
Void.
ETSI
oneM2M TS-0005 version 2.0.2 Release 2A 9 ETSI TS 118 105 V2.0.2 (2020-03)
3.3 Abbreviations
Void.
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].
5 OMA DM 1.3 and OMA DM 2.0
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.
Table 5.1-1 Basic data types
Mapping to data
oneM2M Data Types Description
types in OMA DM
TBD null OMA DM Nodes with null data type shall not store any value
xs:base64Binary b64 Data type for Base64-encoded binary data
xs:base64Binary bin Data type for binary data
xs:boolean bool Data type for Boolean
xs:string chr Data type for text. The length limitation should be considered for the
mapping
xs:integer int Data type for 32-bit signed integer
xs:date date Data type for date in ISO 8601 [12] format with the century being
included in the year
xs:time time Data type specifying that the Node value is a time in ISO 8601 [12]
format
xs:float float Data type for a single precision 32-bit floating point type as defined in
XML Schema 1.0 [13] as the float primitive type
xs:nonNegativeIntege int Data type for numbers equal or larger than 0, mapped from 64-bit to 32-
r bit representation
xs:positiveInteger int Data type for numbers equal or larger than 1, mapped from 64-bit to 32-
bit representation
xs:long int Data type for signed integer numbers, mapped from 64-bit to 32-bit
representation
The mgmtLink node The OMA DM 'node' data type describes the format of the Interior Node
attribute in the that can have child Nodes. The mgmtLink attribute in the
Resource supports the hierarchy of Resource. Note that this
Resource is not data type mapping

5.2 Mapping of Identifiers
OMA DM 1.3 [3] and OMA DM 2.0 [4] 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 oneM2M
identifiers that need to be mapped to OMA DM Protocol.
ETSI
oneM2M TS-0005 version 2.0.2 Release 2A 10 ETSI TS 118 105 V2.0.2 (2020-03)
Table 5.2-1 Map of Identifiers
oneM2M Mapping to OMA DM Identifiers Description
M2M-Node-ID. Device Identifier (i.e. DevId node in In OMA DM, the device identifier is a unique
DevInfo MO) identifier for the device. This value is globally unique
and has to be formatted as a URN.
OMA DM Gateways and OMA DM enabled devices
are assigned with the device identifiers, and each
can be mapped to the M2M-Node-ID.
See note.
The objectID attribute in
Management Object Identifier (MOID) A unique identifier of the management object. Each
resource. MO is characterized by a unique MOID, which is
generally a URN.
The objectPath attribute in URI for the local path in the device Management Objects in the device are uniquely
resource where the relevant Management addressed by a URI that is stored in the objectPath
Object is located attribute. Note that DM 1.3 [3] and DM 2.0 [4] uses
different Addressing scheme, but they are
transparent to the oneM2M service layer.
NOTE: In case the notion of the device identifier is not supported by the device, the DM Gateway can assign the local
identifier for the device, and the M2M-Node-ID should be mapped to this local identifier.

5.3 Mapping of resources
5.3.0 Introduction
This clause describes how to map 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 [3] and OMA DM 2.0 [4] use the same
management objects except standard management objects, the resource mappings can be considered regardless of the
specific version of the OMA DM Protocol.
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. For example, SCOMO is
for the software management, and FUMO is for the firmware update, and so on. The individual management operations
such as firmware update, software management can be achieved by manipulating the corresponding Management
Object. Since oneM2M Resources are for providing specific management functionalities, oneM2M
Resources shall be mapped to Management Objects specified by OMA DM [3] and [4].
5.3.2 Resource [firmware]
The resource [firmware] is for firmware management in the service layer. Regardless of OMA DM 1.3 [3] and OMA
DM 2.0 [4], 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] Mapping to Nodes in Management Object
version /PkgVersion
name /PkgName
URL /DownloadAndUpdate/PkgURL
update /DownloadAndUpdate
updateStatus /State
NOTE: Here is an interior node that acts as a placeholder for the FUMO.

ETSI
oneM2M TS-0005 version 2.0.2 Release 2A 11 ETSI TS 118 105 V2.0.2 (2020-03)
5.3.3 Resource [software]
The resource [software] is for software management in the service layer. Regardless of OMA DM 1.3 [3] and OMA
DM 2.0 [4], 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.
Table 5.3.3-1 Resource [software]
Attribute Name of [software] Mapping to Nodes in Management Object
version /Inventory/Deployed//Version
name /Download//Name (when the software package is not ready for install)
/Inventory/Delivered//Name (when the software package is ready for
install)
/Deployed//Name (when the software package is already installed)
URL /Download//PkgURL
install /Download//Operations/DownloadInstall (when the software package is not
yet available)
/Inventory/Delivered//Operations/Install (when the software package has
already been downloaded)
uninstall //Inventory/Delivered//Operations/Remove
installStatus /Download//Status (started install when the software package is not yet
available)
/Inventory/Delivered//Status (started install when the software package
has already been downloaded)
activate /Inventory/Deployed//Operations/Activate
deactivate /Inventory/Deployed//Operations/Deactivate
activeStatus /Inventory/Deployed//Status
NOTE: Here is the interior node that groups together the parameters of a Software Component Management
Object.
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 [3] and OMA DM 2.0 [4], 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.
Table 5.3.4-1 Resource [memory]
Attribute Name of [memory] Mapping to Nodes in Management Object
memAvailable /DiagMonData/RAMAvail
memTotal /DiagMonData/RAMTotal
NOTE: Here is the interior node that acts as a placeholder for the Memory MO.

5.3.5 Resource [areaNwkInfo]
The resource [areaNwkInfo] is for managing the area network. Regardless of OMA DM 1.3 [3] and OMA DM 2.0 [4],
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] Mapping to Nodes in Management Object
areaNwkType M2MAreaNwkInfo/AreaNwks//AreaNwkType
listOfDevices M2MAreaNwkInfo/AreaNwks//ListOfDevices
NOTE: Here is the interior parent node for information about a specific M2M Area Networks connecting to the
same M2M Gateway.
ETSI
oneM2M TS-0005 version 2.0.2 Release 2A 12 ETSI TS 118 105 V2.0.2 (2020-03)
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 [3] and OMA DM 2.0 [4], 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 the MO as
follows.
Table 5.3.6-1 Resource [areaNwkDeviceInfo]
Attribute Name of
Mapping to Nodes in Management Object
[areaNwkDeviceInfo]
devId DevInfo/DevId
devType DevDetail/DevType
areaNwkId /AreaNwks//AreaNwkID
sleepInterval /AreaNwks//SleepInterval
sleepDuration /AreaNwks//SleepDuration
status /AreaNwks//Status
listOfNeighbors /AreaNwks//Groups/ListOfDeviceNeighbors
NOTE: Here first instance of is the interior node that is the root node for the MANDMO. Second instance of
is the interior node that contains information related to a specific M2M Area Network that the device is
associated with.
5.3.7 Resource [battery]
The Resource [battery] is to provide battery related information. Regardless of OMA DM 1.3 [3] and OMA DM 2.0 [4],
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.3.7-1 Resource [battery]
Attribute Name of [battery] Mapping to Nodes in Management Object
batteryLevel /DiagMonData//BatteryLevel
batteryStatus /DiagMonData//BatteryStatus
NOTE: Here first instance of is the interior node that acts as a placeholder for the Battery MO. Second instance
of is the placeholder for zero or more instances of battery data.

5.3.8 Resource [deviceInfo]
The Resource [deviceInfo] is to provide device related information. For OMA DM 1.3 [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 follows.
Table 5.3.8-1 Resource [deviceInfo] mapping in OMA DM 1.3
Attribute Name of [deviceInfo] Mapping to Nodes in Management Object
deviceLabel DevInfo/DevId
manufacturer DevInfo/Man
model DevInfo/Mod
deviceType DevDetail/DevType
fwVersion DevDetail/FwV
swVersion DevDetail/SwV
hwVersion DevDetail/HwV
ETSI
oneM2M TS-0005 version 2.0.2 Release 2A 13 ETSI TS 118 105 V2.0.2 (2020-03)
For OMA DM 2.0 [4], this Resource shall be mapped to DevInfo MO (MOID: "urn:oma:mo:oma-dm-devinfo:1.2").
The attributes of this Resource shall be mapped to Nodes in the Management Object as follows.
Table 5.3.8-2 Resource [deviceInfo] mapping in OMA DM 2.0
Attribute Name of [deviceInfo] Mapping to Nodes in Management Object
deviceLabel /DevID
manufacturer /Man
model /Mod
deviceType /DevType
fwVersion /FwV
swVersion /SwV
hwVersion /HwV
NOTE: Here is the interior node that is the root node for the DevInfo MO.

5.3.9 Resource [deviceCapability]
The Resource [deviceCapability] is to manage the device capabilities such USB, camera, etc. Regardless of OMA
DM 1.3 [3] and OMA DM 2.0 [4], 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 as
follows.
Table 5.3.9-1 Resource
...