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.22 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 an
2、d smart cities and communities Frameworks, architectures and protocols oneM2M Field device configuration Recommendation ITU-T Y.4500.22 ITU-T Y-SERIES RECOMMENDATIONS GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS, NEXT-GENERATION NETWORKS, INTERNET OF THINGS AND SMART CITIES GLOBAL IN
3、FORMATION 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 INT
4、ERNET 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 Operatio
5、n, 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.2
6、249 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 Carr
7、ier 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.42
8、50Y.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.22 (03/2018) i Recommendation ITU-T Y.4500.22 oneM2M Field device configuration Summary Recommendation ITU-T Y.4500.22 specifies the architectural options, resources and procedures needed to provision and maintain devices in the field domain in order
10、 to establish M2M service layer operation. History Edition Recommendation Approval Study Group Unique ID* 1.0 ITU-T Y.4500.22 2018-03-01 20 11.1002/1000/13512 Keywords Device management, device configuration, oneM2M. * To access the Recommendation, type the URL http:/handle.itu.int/ in the address f
11、ield 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.22 (03/2018) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, inform
12、ation 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 them with a view to standardizing telecommunications on a worl
13、dwide 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-T Recommendations is covered by the procedure laid down in W
14、TSA 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 used for conciseness to indicate both a telecommunication admini
15、stration 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 Recommendation is achieved when all of these mandatory provi
16、sions 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 any party. NOTE This Recommendation departs slightly from the
17、 usual editorial style of ITU-T Recommendations to preserve existing cross-referencing from external documents. 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.
18、ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property 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 intellectua
19、l property, protected by patents, which may be required to implement this Recommendation. However, implementers 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/. ITU 2018 All rights re
20、served. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. Rec. ITU-T Y.4500.22 (03/2018) iii Table of Contents Page 1 Scope . 1 2 References . 1 3 Definitions 1 3.1 Terms defined elsewhere 1 3.2 Terms defined in this Recommendation .
21、 2 4 Abbreviations and acronyms 2 5 Conventions 2 6 Introduction . 3 7 Architectural aspects . 4 7.1 Introduction 4 7.2 Information needed for M2M service layer operation . 5 8 Resource type and data format definitions . 7 8.1 Resource type specializations 7 8.2 Resource-type specific procedures and
22、 definitions 25 8.3 Data formats for device configuration 34 9 Procedures . 35 9.1 life cycle procedures 35 9.2 Obtaining authentication credential procedure . 38 9.3 AE and CSE registration procedure . 39 9.4 Enabling data collection by dataCollection resource . 39 Annex A oneM2M Specification upda
23、te and maintenance control procedure . 41 Bibliography. 42 Rec. ITU-T Y.4500.22 (03/2018) 1 Recommendation ITU-T Y.4500.22 oneM2M Field device configuration 1 Scope This Recommendation specifies the architectural options, resources and procedures needed to pre-provision and maintain devices in the f
24、ield domain (e.g., ADN, ASN/MN) in order to establish M2M service layer operation between the devices application entity (AE) and/or common services entity (CSE) and a registrar and/or hosting CSE. The resources and procedures include information about the registrar CSE and/or hosting CSE needed by
25、the AE or CSE to begin machine to machine (M2M) service layer operation. This Recommendation contains oneM2M Release 2 specification oneM2M Field Device Configuration V2.0.0 and is equivalent to standards of oneM2M partners including ARIB, ATIS, CCSA, ETSI b-ETSI TS 118 122, TIA, TSDSI, TTA and TTC.
26、 2 References The following ITU-T Recommendations and other 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 revisi
27、on; users of this Recommendation are therefore encouraged 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 R
28、ecommendation does not give it, as a stand-alone document, the status of a Recommendation. The following referenced documents are necessary for the application of this Recommendation. ITU-T Y.4500.1 Recommendation ITU-T Y.4500.1 (2018), oneM2M Functional architecture. ITU-T Y.4500.4 Recommendation I
29、TU-T Y.4500.4 (2018), oneM2M Service layer core protocol. ITU-T Y.4500.5 Recommendation ITU-T Y.4500.5 (2018), oneM2M Management enablement (OMA). ITU-T Y.4500.6 Recommendation ITU-T Y.4500.6 (2018), oneM2M Management enablement (BBF). ITU-T Y.4500.11 Recommendation ITU-T Y.4500.11 (2018), oneM2M Co
30、mmon terminology. ETSI TS 118 103 ETSI TS 118 103 (2016), oneM2M; Security solutions. FIPS 180-4 NIST, FIPS 180-4 (2015), Secure Hash Standard (SHS). IETF RFC 6920 IETF RFC 6920 (2013), Naming Things with Hashes. 3 Definitions For the purposes of this Recommendation, the terms and definitions given
31、in oneM2M TS-0011 ITU-T Y.4500.11 apply. 3.1 Terms defined elsewhere 3.1.1 application entity (AE) ITU-T Y.4500.11: This represents an instantiation of application logic for end-to-end M2M solutions. 2 Rec. ITU-T Y.4500.22 (03/2018) 3.1.2 common services entity (CSE) ITU-T Y.4500.11: This represents
32、 an instantiation of a set of common service functions of the M2M environment. Such service functions are exposed to other entities through reference points. 3.1.3 (oneM2M) security principal ITU-T Y.4500.11: CSE or AE or node or M2M device which can be authenticated. NOTE When the security principa
33、l is a node or M2M device, then the node or M2M device is acting on behalf of the CSE and/or AE executing on the node or M2M device. 3.2 Terms defined in this Recommendation 3.2.1 application configuration: A procedure that configures an AE on an M2M node in the field domain for M2M service layer op
34、eration. 3.2.2 authentication profile: Security information that is needed to establish mutually-authenticated secure communications. 3.2.3 configuration AE: An AE whose role is to configure the M2M system, including the M2M node in the field domain. 3.2.4 configuration IPE: An IPE that provides the
35、 capability to configure the M2M node in the field domain by interworking the exchange of information between the M2M node and the M2M system. 3.2.5 service layer configuration: A procedure that configures a CSE on an M2M node in the field domain for M2M service layer operation. 4 Abbreviations and
36、acronyms For the purposes of this Recommendation, the abbreviations given in oneM2M TS-0011 ITU-T Y.4500.11, oneM2M TS-0001 ITU-T Y.4500.1 and the following apply: AE Application Entity CSE Common Services Entity M2M Machine to Machine MAF M2M Authentication Function MEF M2M Enrolment Function MO Ma
37、naged Object (BBF specified management) or Management Object (OMA specified management) NP Not Present RSPF Remote Security Provisioning Framework SAEF Security Associated Establishment Framework SUID Security Usage Identifier XML extensible Markup Language XSD XML Schema Definition 5 Conventions Th
38、e key words “Shall“, “Shall not“, “May“, “Need not“, “Should“, “Should not“ in this Recommendation are to be interpreted as described: Shall/Shall not: Rec. ITU-T Y.4500.22 (03/2018) 3 Requirements: 1) Effect on this Recommendation: This Recommendation needs to describe the required feature (i.e., s
39、pecify a technical solution for the requirement); 2) Effect on products: Every implementation (M2M solution that complies to this Recommendation) must support it. 3) Effect on deployments: Every deployment (M2M service based on this Recommendation) must use the standardized feature where applicable
40、otherwise e.g., interoperability problems with other services could arise. Should/Should not: Recommendation: 1) Effect on this Recommendation: 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 ma
41、y not support it; however support is recommended. 3) Effect on deployments: A deployment may or may not use it; however usage is recommended. May/Need not: Permission/Option: 1) Effect on this Recommendation: This Recommendation needs to describe a solution that allows the presence and the absence o
42、f the required feature. 2) Effect on products: An implementation may or may not support it. 3) Effect on deployments: A deployment may or may not use it. 6 Introduction Devices in the field domain that host oneM2M AEs and CSEs require configuration that permits the AE or CSE to successfully operate
43、in the M2M service layer. TS-0001 ITU-T Y.4500.1 and TS-0003 ETSI TS 118 103 specify much of what is needed to configure these devices in the field domain (i.e., ADN, ASN/MN). Specifically, TS-0001 ITU-T Y.4500.1 provides: guidance on how a CSE is minimally provisioned in Annex E of the specificatio
44、n including how a user AE is established within a hosting CSE; specification of the general communication flows across the Mca and Mcc reference points in clause 8; specifications for how ASN/MN and ADN nodes and M2M applications are enrolled in the M2M system so that the node in the field domain ca
45、n establish connectivity with a CSE. TS-0001 ITU-T Y.4500.1 heavily relies on clause 6 and on the remote security provisioning framework (RSPF) of TS-0003 ETSI TS 118 103 to specify how the security credentials of ASN/MN and ADN nodes and M2M applications are established in the M2M system for the en
46、rolment of the node or M2M application in the M2M system; specifications for how the ADN and ASN/MN nodes in the field domain are managed using external management technologies in clause 6.2.4; guidance for how the ADN and ASN/MN nodes in the field domain can be configured without the support of ext
47、ernal management technologies in clause 9.1.2. The above clauses in TS-0001 ITU-T Y.4500.1 assume that, for an M2M application to operate in the M2M system, all required information needed to establish M2M service operation between a 4 Rec. ITU-T Y.4500.22 (03/2018) registrar or hosting CSE and the
48、AE or CSE in the field domain is configured before registration of the AE or CSE to the M2M system. This Recommendation specifies the additional architectural elements, resources and procedures necessary to configure ASN/MN and ADN nodes in the field domain in order for that device to establish M2M
49、service layer operation. These architectural elements, resources and procedures are in addition to the architectural elements, resources and procedures already defined in TS-0001 ITU-T Y.4500.1 and TS-0003 ETSI TS 118 103. 7 Architectural aspects 7.1 Introduction The information needed by the remote AE or CSE in the field domain to establish M2M service layer operation uses the architectural aspects of TS-0001 ITU-T Y.4500.1 in order to convey the i
