1、 ETSI TS 118 105 V1.1.0 (2016-03) oneM2M; Management Enablement (OMA) (oneM2M TS-0005 version 1.4.1 Release 1) TECHNICAL SPECIFICATION oneM2M TS-0005 version 1.4.1 Release 1 ETSI ETSI TS 118 105 V1.1.0 (2016-03)2 Reference RTS/oneM2M-000005v110 Keywords IoT,M2M ETSI 650 Route des Lucioles F-06921 So
2、phia 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 enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice The present document can be downloaded from: http:/www.etsi.org/standards-search The
3、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 v
4、ersions and/or in print, the only prevailing document is the print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on th
5、e 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
6、 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
7、 foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2016. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM and LTE are Trade Marks of ETSI registered for
8、 the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. oneM2M TS-0005 version 1.4.1 Release 1 ETSI ETSI TS 118 105 V1.1.0 (2016-03)3 Contents Intellectual Property Rights 6g3Foreword . 6g31 Scope 7g32 Ref
9、erences 7g32.1 Normative references . 7g32.2 Informative references 8g33 Definitions 8g34 Conventions 8g35 OMA DM 1.3 and OMA DM 2.0 . 8g35.1 Mapping of basic data types . 8g35.2 Mapping of Identifiers 9g35.3 Mapping of resources . 10g35.3.0 Introduction. 10g35.3.1 General Mapping Assumptions . 10g3
10、5.3.2 Resource firmware . 10g35.3.3 Resource software 11g35.3.4 Resource memory. 11g35.3.5 Resource areaNwkInfo . 11g35.3.6 Resource areaNwkDeviceInfo 12g35.3.7 Resource battery . 12g35.3.8 Resource deviceInfo . 12g35.3.9 Resource deviceCapability . 13g35.3.10 Resource reboot 13g35.3.11 Resource eve
11、ntLog . 13g35.3.12 Resource cmdhPolicy . 14g35.3.12.0 Introduction . 14g35.3.12.1 Resource activeCmdhPolicy . 14g35.3.12.2 Resource cmdhDefaults 15g35.3.12.3 Resource cmdhDefEcValue 15g35.3.12.4 Resource cmdhEcDefParamValues 15g35.3.12.5 Resource cmdhLimits . 16g35.3.12.6 Resource cmdhNetworkAccessR
12、ules . 16g35.3.12.7 Resource cmdhNwAccessRule . 17g35.3.12.8 Resource cmdhBuffer . 17g35.4 Mapping of procedures for management 17g35.4.1 Mapping for Resource Primitives 17g35.4.1.1 Create Primitive for Resource 17g35.4.1.1.0 Introduction . 17g35.4.1.1.1 Create Response Status Code Mapping . 18g35.4
13、.1.2 Retrieve Primitive for Resource . 19g35.4.1.2.0 Introduction . 19g35.4.1.2.1 Retrieve Response Status Code Mapping 19g35.4.1.3 Update Primitive for Resource . 21g35.4.1.3.0 Introduction . 21g35.4.1.3.1 Update Primitive for Replacing Data in the Management Object . 21g35.4.1.3.2 Update Primitive
14、 for Executing Management Commands 22g35.4.1.4 Delete Primitive for Resource 24g35.4.1.4.0 Introduction . 24g35.4.1.4.1 Delete Response Status Code Mapping . 24g35.4.1.5 Notify Primitive Mapping . 25g35.4.1.5.0 Introduction . 25g35.4.1.5.1 Subscribe Procedure Mapping for OMA DM 1.3 25g35.4.1.5.2 Sub
15、scribe Procedure Mapping for OMA DM 2.0 25g35.4.1.5.3 Notification Procedure Mapping for OMA DM 1.3 and OMA DM 2.0 26g35.4.2 Management Resource Specific Procedure Mapping . 26g3oneM2M TS-0005 version 1.4.1 Release 1 ETSI ETSI TS 118 105 V1.1.0 (2016-03)4 5.4.2.0 Introduction . 26g35.4.2.1 Resource
16、firmware 26g35.4.2.2 Resource software 27g35.4.2.3 Resource memory . 27g35.4.2.4 Resource areaNwkInfo . 28g35.4.2.5 Resource areaNwkDeviceInfo 28g35.4.2.6 Resource battery . 28g35.4.2.7 Resource deviceInfo . 28g35.4.2.8 Resource deviceCapability . 28g35.4.2.9 Resource reboot 28g35.4.2.10 Resource ev
17、entLog . 29g35.5 DM Server Interactions 29g35.5.0 Introduction. 29g35.5.1 Communication Session Establishment 29g35.5.2 Translation of Requests and Responses between IN-CSE and DM Server. 30g35.5.3 Discovery and Subscription for management objects . 30g35.5.4 Access Control Management 30g35.6 New Ma
18、nagement Objects . 30g35.6.1 M2M CMDH Policies MO (MCMDHMO) 30g36 OMA Lightweight M2M 1.0 41g36.1 Mapping of basic data types . 41g36.2 Mapping of Identifiers 41g36.2.0 Introduction. 41g36.2.1 Device identifier . 42g36.2.2 Object identifier 42g36.2.3 Object Instance Identifier 42g36.3 Mapping of res
19、ources . 42g36.2.0 Introduction. 42g36.3.1 General Mapping Assumptions . 42g36.3.2 Resource firmware . 42g36.3.3 Resource software 43g36.3.4 Resource memory. 43g36.3.5 Resource areaNwkInfo . 44g36.3.6 Resource areaNwkDeviceInfo 44g36.3.7 Resource battery . 44g36.3.8 Resource deviceInfo . 44g36.3.9 R
20、esource deviceCapability . 45g36.3.10 Resource reboot 45g36.3.11 Resource eventLog . 46g36.3.12 Resource cmdhPolicy . 46g36.3.12.0 Introduction . 46g36.3.12.1 Resource activeCmdhPolicy . 47g36.3.12.2 Resource cmdhDefaults 47g36.3.12.3 Resource cmdhDefEcValue 48g36.3.12.4 Resource cmdhEcDefParamValue
21、s 48g36.3.12.5 Resource cmdhLimits . 49g36.3.12.6 Resource cmdhNetworkAccessRules . 49g36.3.12.7 Resource cmdhNwAccessRule . 50g36.3.12.8 Resource cmdhBuffer . 50g36.4 Mapping of procedures for management 51g36.4.0 Introduction. 51g36.4.1 Create primitive for Resource 51g36.4.2 Retrieve primitive fo
22、r Resource . 51g36.4.3 Update primitive for Resource . 52g36.4.3.0 Introduction . 52g36.4.3.1 Update primitive for replacing data 52g36.4.3.2 Update primitive for execution operation . 52g36.4.4 Delete primitive for Resource 52g36.4.5 Notify Primitive for Resource 53g36.4.5.0 Introduction . 53g36.4.
23、5.1 Notify Primitive mapping for subscription to Resource attributes . 53g3oneM2M TS-0005 version 1.4.1 Release 1 ETSI ETSI TS 118 105 V1.1.0 (2016-03)5 6.4.5.2 Notify Primitive mapping for subscription cancellation to Resource attributes . 53g36.4.5.3 Notify Primitive mapping for Notification 53g36
24、.4.6 Management Resource Specific Procedure Mapping . 54g36.4.6.1 Resource firmware 54g36.4.6.2 Resource software 54g36.4.6.3 Resource memory . 54g36.4.6.4 Resource battery . 54g36.4.6.5 Resource deviceInfo . 54g36.4.6.6 Resource deviceCapability . 54g36.4.6.7 Resource reboot 54g36.5 LWM2M Server In
25、teractions . 55g36.5.0 Introduction. 55g36.5.1 Communication Session Establishment 55g36.5.2 Translation of Requests and Responses between IN-CSE and LWM2M Server 55g36.5.3 Discovery and Subscription for LWM2M Objects . 55g36.5.4 Access Control Management 56g36.6 New LWM2M Objects . 56g36.6.0 Introd
26、uction. 56g36.6.1 LWM2M CMDH Policy Objects 56g36.6.1.0 Introduction . 56g36.6.1.1 CmdhPolicy Object . 56g36.6.1.2 ActiveCmdhPolicy Object 57g36.6.1.3 CmdhDefaults Object 57g36.6.1.4 CmdhDef ECValues Object 57g36.6.1.5 CmdhDefaultsECParamValues Object 58g36.6.1.6 CmdhLimits Object 58g36.6.1.7 CmdhNe
27、tworkAccessRules Object 58g36.6.1.8 CmdhNwAccessRule Object . 59g36.6.1.9 CmdhBuffer Object . 59g3History 60g3oneM2M TS-0005 version 1.4.1 Release 1 ETSI ETSI TS 118 105 V1.1.0 (2016-03)6 Intellectual Property Rights IPRs essential or potentially essential to the present document may have been decla
28、red 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
29、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 E
30、TSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This Technical Specification (TS) has been produced by ETSI Partnership Project oneM2M (oneM2M). oneM2M TS-0005 version 1.4.1 Release 1 ETSI ETSI TS 118 105 V1.1.0
31、(2016-03)7 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 i
32、n 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 re
33、ferenced document (including any amendments) applies. The following referenced documents are necessary for the application of the present document. 1 ETSI TS 118 001: “oneM2M; Functional Architecture (oneM2M TS-0001)“. 2 ETSI TS 118 004: “Service Layer Core Protocol Specification“. 3 Open Mobile All
34、iance: “OMA Device Management Protocol“, Version 1.3. NOTE: Available at http:/www.openmobilealliance.org/. 4 Open Mobile Alliance: “OMA Device Management Protocol“, Version 2.0. NOTE: Available at http:/www.openmobilealliance.org/. 5 Open Mobile Alliance: “OMA LightweightM2M“, Version 1.0. NOTE: Av
35、ailable at http:/www.openmobilealliance.org/. 6 Open Mobile Alliance: “OMA Diagnostics and Monitoring Management Object Framework“. NOTE: Available at http:/www.openmobilealliance.org/. 7 Open Mobile Alliance: “OMA Firmware Update Management Object“. NOTE: Available at http:/www.openmobilealliance.o
36、rg/. 8 Open Mobile Alliance: “OMA Software Component Management Object“. NOTE: Available at http:/www.openmobilealliance.org/. 9 ETSI TS 103 092: “Machine-to-Machine communications (M2M); OMA DM compatible Management Objects for ETSI M2M“. 10 Open Mobile Alliance: “OMA Device Capability Management O
37、bject“. NOTE: Available at http:/www.openmobilealliance.org/. 11 Open Mobile Alliance: “OMA Management Interface to M2M Requirements“. NOTE: Available at http:/www.openmobilealliance.org/. 12 ISO 8601:2000: “Data elements and interchange formats - Information interchange - Representation of dates an
38、d times“. NOTE: Available at http:/www.iso.ch/. 13 W3C Recommendation: “XML Schema Part 2: Datatypes“, 02 May 2001. NOTE: Available at http:/www.w3.org/XML/Schema/. oneM2M TS-0005 version 1.4.1 Release 1 ETSI ETSI TS 118 105 V1.1.0 (2016-03)8 14 IETF RFC 4122: “A Universally Unique Identifier (UUID)
39、 URN Namespace“, P. Leach, et al. July 2005. NOTE: Available at http:/www.ietf.org/rfc/rfc4122.txt. 15 ETSI TS 123 003: “Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Numbering, addressing and identification (3GPP TS 23.003)“. 16 BBF: “TR-0
40、69 CPE WAN Management Protocol“ Issue: 1 Amendment 5, November 2013. 17 IETF RFC 7252: “The Constrained Application Protocol (CoAP)“. 18 Open Mobile Alliance: “OMA LightweightM2M - Software Management Object“, Version 1.0, Open Mobile Alliance. NOTE: Available at http:/www.openmobilealliance.org/. 1
41、9 Open Mobile Alliance: “OMA LightweightM2M - Device Capability Management Object“. NOTE: Available at http:/www.openmobilealliance.org/. 2.2 Informative references References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specifi
42、c references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a part
43、icular subject area. i.1 oneM2M Drafting Rules. NOTE: Available at http:/member.onem2m.org/Static_pages/Others/Rules_Pages/oneM2M-Drafting-Rules-V1_0.doc. i.2 ETSI TS 118 111: “oneM2M; Common Terminology (oneM2M TS-0011)“. 3 Definitions For the purposes of the present document, the terms and definit
44、ions given in ETSI TS 118 111 i.2 apply. 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 defi
45、ned the data types that describe the format of the value stored with the attribute. Those oneM2M data types are listed in the below table, 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. oneM2M TS-0005 version 1.4.1
46、Release 1 ETSI ETSI TS 118 105 V1.1.0 (2016-03)9 Table 5.1-1: Basic data types oneM2M Data Types Mapping to data types in OMA DM Description 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 typ
47、e 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 yea
48、r. 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:nonNegativeInteger int Data type for numbers equal or larger than 0, ma
49、pped from 64-bit to 32-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 attribute in the Resource node The OMA DM node data type describes the format of the Interior Node that can have child
