1、 I n t e r n a t i o n a l T e l e c o m m u n i c a t i o n U n i o n ITU-T Y.4500.5 TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (03/2018) SERIES Y: GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS, NEXT-GENERATION NETWORKS, INTERNET OF THINGS AND SMART CITIES Internet of things and
2、 smart cities and communities Frameworks, architectures and protocols oneM2M Management enablement (OMA) Recommendation ITU-T Y.4500.5 ITU-T Y-SERIES RECOMMENDATIONS GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS, NEXT-GENERATION NETWORKS, INTERNET OF THINGS AND SMART CITIES GLOBAL INF
3、ORMATION INFRASTRUCTURE General Y.100Y.199 Services, applications and middleware Y.200Y.299 Network aspects Y.300Y.399 Interfaces and protocols Y.400Y.499 Numbering, addressing and naming Y.500Y.599 Operation, administration and maintenance Y.600Y.699 Security Y.700Y.799 Performances Y.800Y.899 INTE
4、RNET PROTOCOL ASPECTS General Y.1000Y.1099 Services and applications Y.1100Y.1199 Architecture, access, network capabilities and resource management Y.1200Y.1299 Transport Y.1300Y.1399 Interworking Y.1400Y.1499 Quality of service and network performance Y.1500Y.1599 Signalling Y.1600Y.1699 Operation
5、, administration and maintenance Y.1700Y.1799 Charging Y.1800Y.1899 IPTV over NGN Y.1900Y.1999 NEXT GENERATION NETWORKS Frameworks and functional architecture models Y.2000Y.2099 Quality of Service and performance Y.2100Y.2199 Service aspects: Service capabilities and service architecture Y.2200Y.22
6、49 Service aspects: Interoperability of services and networks in NGN Y.2250Y.2299 Enhancements to NGN Y.2300Y.2399 Network management Y.2400Y.2499 Network control architectures and protocols Y.2500Y.2599 Packet-based Networks Y.2600Y.2699 Security Y.2700Y.2799 Generalized mobility Y.2800Y.2899 Carri
7、er grade open environment Y.2900Y.2999 FUTURE NETWORKS Y.3000Y.3499 CLOUD COMPUTING Y.3500Y.3999 INTERNET OF THINGS AND SMART CITIES AND COMMUNITIES General Y.4000Y.4049 Definitions and terminologies Y.4050Y.4099 Requirements and use cases Y.4100Y.4249 Infrastructure, connectivity and networks Y.425
8、0Y.4399 Frameworks, architectures and protocols Y.4400Y.4549 Services, applications, computation and data processing Y.4550Y.4699 Management, control and performance Y.4700Y.4799 Identification and security Y.4800Y.4899 Evaluation and assessment Y.4900Y.4999 For further details, please refer to the
9、list of ITU-T Recommendations. Rec. ITU-T Y.4500.5 (03/2018) i Recommendation ITU-T Y.4500.5 oneM2M Management enablement (OMA) Summary Recommendation ITU-T Y.4500.5 specifies the usage of Open Mobile Alliance device management (OMA DM) and OMA Lightweight M2M (LwM2M) resources and the corresponding
10、 message flows, including normal cases, as well as error cases to fulfil the oneM2M management requirements. History Edition Recommendation Approval Study Group Unique ID* 1.0 ITU-T Y.4500.5 2018-03-01 20 11.1002/1000/13501 Keywords Device management, OMA DM, OMA LwM2M, oneM2M. * To access the Recom
11、mendation, type the URL http:/handle.itu.int/ in the address field of your web browser, followed by the Recommendations unique ID. For example, http:/handle.itu.int/11.1002/1000/11830-en. ii Rec. ITU-T Y.4500.5 (03/2018) FOREWORD The International Telecommunication Union (ITU) is the United Nations
12、specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on t
13、hem with a view to standardizing telecommunications on a worldwide basis. The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. The approval of ITU
14、-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. In some areas of information technology which fall within ITU-Ts purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. NOTE In this Recommendation, the expression “Administration“ is use
15、d for conciseness to indicate both a telecommunication administration and a recognized operating agency. Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the
16、 Recommendation is achieved when all of these mandatory provisions are met. The words “shall“ or some other obligatory language such as “must“ and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of
17、any party. INTELLECTUAL PROPERTY RIGHTSITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Prop
18、erty Rights, whether asserted by ITU members or others outside of the Recommendation development process. As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, im
19、plementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at http:/www.itu.int/ITU-T/ipr/. NOTE This Recommendation departs slightly from the usual editorial style of ITU-T Recommendations to preserve existing cros
20、s-referencing from external documents. ITU 2018 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. Rec. ITU-T Y.4500.5 (03/2018) iii Table of Contents Page 1 Scope . 1 2 References . 1 3 Definitions 2 3.1 Terms de
21、fined elsewhere 2 3.2 Terms defined in this Recommendation . 2 4 Abbreviations and acronyms 2 5 Conventions 3 6 OMA DM 1.3 and OMA DM 2.0 . 3 6.1 Mapping of basic data types . 3 6.2 Mapping of identifiers 4 6.3 Mapping of resources . 5 6.4 Mapping of procedures for management 14 6.5 DM server intera
22、ctions . 30 6.6 New management objects . 31 7 OMA Lightweight M2M 1.0 42 7.1 Mapping of basic data types . 42 7.2 Mapping of identifiers 42 7.3 Mapping of resources . 43 7.4 Mapping of procedures for management 53 7.5 LWM2M server interactions 57 7.6 New LWM2M objects 58 Annex A oneM2M Specification
23、 Update and Maintenance Control Procedure . 63 Bibliography. 64 Rec. ITU-T Y.4500.5 (03/2018) 1 Recommendation ITU-T Y.4500.5 oneM2M Management enablement (OMA) 1 Scope This Recommendation specifies the protocol translation and mappings between the oneM2M service layer and the management technologie
24、s 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 this Recommendation. This Recommendation contains oneM2M Release 2 specification oneM2M Management Enablement (OMA) V2.0.0 and is equivalent to stand
25、ards of oneM2M partners including ARIB, ATIS ATIS.oneM2M.TS0005V200-2016, CCSA CCSA M2M-TS-0005-V2.0.0, ETSI ETSI TS 118 105 V2.0.0, TIA, TSDSI TSDSI STD T1.oneM2M TS-0005-2.0.0 V1.0.0, TTA TTAT.MM-TS.0005 v2.0.0 and TTC TTC TS-M2M-0005v2.0.0. 2 References The following ITU-T Recommendations and oth
26、er references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged
27、 to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document
28、, the status of a Recommendation. ITU-T Y.4500.1 Recommendation ITU-T Y.4500.1 (2018), oneM2M Functional architecture. ITU-T Y.4500.4 Recommendation ITU-T Y.4500.4 (2018), oneM2M Service layer core protocol. ITU-T Y.4500.11 Recommendation ITU-T Y.4500.11 (2018), oneM2M Common terminology. BBF TR-069
29、 BBF TR-069 (2013), CPE WAN Management Protocol, Issue: 1 Amendment 5, November 2013. ETSI TS 103 092 ETSI TS 103 092 (2013), Machine-to-Machine communications (M2M); OMA DM compatible Management Objects for ETSI M2M. ETSI TS 123 003 ETSI TS 123 003 (2014), Numbering, addressing and identification.
30、IETF RFC 4122 IETF RFC 4122 (2005), A Universally Unique Identifier (UUID) URN Namespace. IETF RFC 7252 IETF RFC 7252 (2014), The Constrained Application Protocol (CoAP). ISO 8601:2000 ISO 8601:2004, Data elements and interchange formats Information interchange Representation of dates and times. OMA
31、 DiagMon Open Mobile Alliance (2013), OMA Diagnostics and Monitoring Management Object Framework. 2 Rec. ITU-T Y.4500.5 (03/2018) OMA DCMO Open Mobile Alliance (2012), OMA Device Capability Management Object. OMA DM 1.3 Open Mobile Alliance (2016), OMA Device Management Protocol, Version 1.3. OMA DM
32、 2.0 Open Mobile Alliance (2016), OMA Device Management Protocol, Version 2.0. OMA FUMO Open Mobile Alliance (2009), OMA Firmware Update Management Object. OMA LwM2M 1.0 Open Mobile Alliance (2017), OMA LightweightM2M, Lightweight Machine to Machine, Version 1.0. OMA LwM2M DevCapMgmt Open Mobile All
33、iance (2017), OMA LightweightM2M Device Capability Management Object. OMA LwM2M SWMGMT Open Mobile Alliance (2018), OMA LightweightM2M Software Management Object, Version 1.0. OMA M2Minterface Open Mobile Alliance (2015), OMA Management Interface to M2M Requirements. OMA SCOMO Open Mobile Alliance (
34、2013), OMA Software Component Management Object. W3C XML Schema 2 W3C Recommendation (2001), XML Schema Part 2: Datatypes. 3 Definitions For the purposes of this Recommendation, the terms and definitions given in oneM2M TS-0011 ITU-T Y. 4500.11 apply. 3.1 Terms defined elsewhere This Recommendation
35、uses the following terms defined elsewhere: 3.1.1 application entity ITU-T Y.4500.11: This represents an instantiation of application logic for end-to-end M2M solutions. 3.1.2 common services entity (CSE) ITU-T Y.4500.11: This represents an instantiation of a set of common service functions of the M
36、2M environments. Such service functions are exposed to other entities through reference points. 3.2 Terms defined in this Recommendation None. 4 Abbreviations and acronyms This Recommendation uses the following abbreviations and acronyms: AE Application Entity CSE Common Services Entity LWM2M Lightw
37、eight Machine to Machine MCMDHMO M2M CMDH Policies MO OMA Open Mobile Alliance OMA-DM Open Mobile Alliance Device Management Rec. ITU-T Y.4500.5 (03/2018) 3 OMNA OMA Naming Authority 5 Conventions The keywords “Shall“, “Shall not“, “May“, “Need not“, “Should“, “Should not“ in this Recommendation are
38、 to be interpreted as described: Shall/Shall not: Requirements 1) Effect on this Recommendation: This Recommendation needs to describe the required feature (i.e. specify a technical solution for the requirement); 2) Effect on products: Every implementation (M2M solution that complies to this Recomme
39、ndation) must support it. 3) Effect on deployments: Every deployment (M2M service based on this Recommendation) must use the standardized feature where applicable otherwise e.g. interoperability problems with other services could arise. Should/Should not: Recommendation 1) Effect on this Recommendat
40、ion: This Recommendation needs to describe a solution that allows the presence and the absence of the feature. 2) Effect on products: An implementation may or may not support it; however support is recommended. 3) Effect on deployments: A deployment may or may not use it; however usage is recommende
41、d. May/Need not: Permission/Option 1) Effect on this Recommendation: This Recommendation needs to describe a solution that allows the presence and the absence of the required feature. 2) Effect on products: An implementation may or may not support it. 3) Effect on deployments: A deployment may or ma
42、y not use it. 6 OMA DM 1.3 and OMA DM 2.0 6.1 Mapping of basic data types oneM2M has defined the data types that describe the format of the value stored with the attribute. These oneM2M data types are listed in the table below, and mapped to the data types specified by OMA DM Protocol OMA DM 1.3 and
43、 OMA DM 2.0. Note that OMA DM 1.3 OMA DM 1.3 and OMA DM 2.0 OMA DM 2.0 use the same data types. Table 6.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-enco
44、ded binary data xs:base64Binary bin Data type for binary data 4 Rec. ITU-T Y.4500.5 (03/2018) Table 6.1-1 Basic data types oneM2M data types Mapping to data types in OMA DM Description xs:boolean bool Data type for Boolean xs:string chr Data type for text. The length limitation should be considered
45、for the mapping xs:integer int Data type for 32-bit signed integer xs:date date Data type for date in ISO 8601 ISO 8601:2000 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 ISO 8601:2000 format xs:float float Data type fo
46、r a single precision 32-bit floating point type as defined in XML Schema 1.0 W3C XML Schema 2 as the float primitive type xs:nonNegativeInteger int Data type for numbers equal to or larger than 0, mapped from 64-bit to 32-bit representation xs:positiveInteger int Data type for numbers equal to or la
47、rger 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 nodes. The mgmtLi
48、nk attribute in the resource supports the hierarchy of resource. Note that this is not data type mapping. 6.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 t
49、he device management using OMA DM protocol, oneM2M identifiers need to be mapped to identifiers specified by the OMA DM protocol. The table below shows the oneM2M identifiers that need to be mapped to the OMA DM protocol. Table 6.2-1 Map of identifiers oneM2M Mapping to OMA DM identifiers Description M2M-Node-ID. Device identifier (i.e., DevId node in DevInfo MO) In OMA DM, the device identifier is a unique identifier for
