1、 ETSI TS 118 122 V2.0.0 (2017-05) oneM2M Field Device Configuration (oneM2M TS-0022 version 2.0.0 Release 2) TECHNICAL SPECIFICATION ETSI ETSI TS 118 122 V2.0.0 (2017-05)2oneM2M TS-0022 version 2.0.0 Release 2Reference DTS/oneM2M-000022 Keywords configuration, IoT, M2M ETSI 650 Route des Lucioles F-
2、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 enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice The present document can be downloaded from: http:/www.etsi.org/standards-sea
3、rch 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 betwee
4、n such versions 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. Informati
5、on 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 Noti
6、fication 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
7、 and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2017. 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 regist
8、ered for the benefit of its Members and of the 3GPP Organizational Partners. oneM2M logo is protected for the benefit of its Members GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 118 122 V2.0.0 (2017-05)3oneM2M TS-0022 version 2.0.0 Release 2Contents
9、Intellectual Property Rights 5g3Foreword . 5g31 Scope 6g32 References 6g32.1 Normative references . 6g32.2 Informative references 6g33 Definitions and abbreviations . 7g33.1 Definition . 7g33.2 Abbreviations . 7g34 Conventions 7g35 Introduction 7g36 Architectural Aspects . 8g36.1 Introduction 8g36.2
10、 Information needed for M2M Service Layer operation 9g36.2.1 Introduction. 9g36.2.2 Information elements required for M2M Service Layer operation . 9g36.2.2.1 Introduction . 9g36.2.2.2 M2M Service Layer registration information elements 9g36.2.2.3 Application configuration information elements . 10g
11、36.2.2.4 Authentication profile information elements 10g36.2.2.5 My certificate file credential information elements 10g36.2.2.6 Trust anchor credential information elements . 10g36.2.2.7 MAF Client registration configuration information elements . 11g37 Resource type and data format definitions . 1
12、1g37.1 Resource type specializations 11g37.1.1 Introduction. 11g37.1.2 Resource registration 11g37.1.3 Resource dataCollection . 13g37.1.4 Resource authenticationProfile 15g37.1.5 Resource myCertFileCred 19g37.1.6 Resource trustAnchorCred . 21g37.1.7 Resource MAFClientRegCfg . 23g37.2 Resource-Type
13、specific procedures and definitions . 24g37.2.1 Introduction. 24g37.2.2 Resource registration 24g37.2.2.1 Introduction . 24g37.2.2.2 Resource specific procedure on CRUD operations . 25g37.2.3 Resource dataCollection . 25g37.2.3.1 Introduction . 25g37.2.3.2 Resource specific procedure on CRUD operati
14、ons . 26g37.2.4 Resource authenticationProfile 26g37.2.4.1 Introduction . 26g37.2.4.2 Resource specific procedure on CRUD operations . 27g37.2.5 Resource myCertFileCred 27g37.2.5.1 Introduction . 27g37.2.5.2 Resource specific procedure on CRUD operations . 28g37.2.6 Resource trustAnchorCred . 28g37.
15、2.6.1 Introduction . 28g37.2.6.2 Resource specific procedure on CRUD operations . 29g37.2.7 Resource MAFClientRegCfg . 29g37.2.7.1 Introduction . 29g37.3 Data formats for device configuration 30g37.3.1 Introduction. 30g3ETSI ETSI TS 118 122 V2.0.0 (2017-05)4oneM2M TS-0022 version 2.0.0 Release 27.3.
16、2 Simple oneM2M data types for device configuration . 30g38 Procedures 30g38.1 life cycle procedures 30g38.1.1 Introduction. 30g38.1.2 Setting configuration information on resource . 31g38.1.3 Management of resource on ASN/MN/ADN nodes . 31g38.1.3.1 Introduction . 31g38.1.3.2 Management using device
17、 management technologies. 31g38.1.3.3 Management using the Mcc reference point . 32g38.1.3.4 Management using the oneM2M IPE technology . 33g38.2 Obtaining authentication credential procedure . 34g38.3 AE and CSE registration procedure 35g38.4 Enabling data collection by dataCollection resource . 35
18、g3History 36g3ETSI ETSI TS 118 122 V2.0.0 (2017-05)5oneM2M TS-0022 version 2.0.0 Release 2Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for
19、 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
20、:/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, essent
21、ial to the present document. Foreword This Technical Specification (TS) has been produced by ETSI Partnership Project oneM2M (oneM2M). ETSI ETSI TS 118 122 V2.0.0 (2017-05)6oneM2M TS-0022 version 2.0.0 Release 21 Scope The present document specifies the architectural options, resources and procedure
22、s needed to pre-provision and maintain devices in the Field Domain (e.g. ADN, ASN/MN) in order to establish M2M Service Layer operation between the devices AE and/or CSE and a Registrar and/Hosting CSE. The resources and procedures includes information about the Registrar CSE and/or Hosting CSE need
23、ed by the AE or CSE to begin M2M Service Layer operation. 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 refere
24、nces, 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
25、 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 111: “oneM2M; Common Terminology (oneM2M TS-0011)“. 2 ETSI TS 118 101: “oneM2M; Functional Architecture (oneM2M TS-0001)“.
26、 3 ETSI TS 118 103: “oneM2M; Security solutions (oneM2M TS-0003)“. 4 ETSI TS 118 104: “oneM2M; Service Layer Core Protocol Specification (oneM2M TS-0004)“. 5 ETSI TS 118 105: “oneM2M; Management Enablement (OMA) (oneM2M TS-0005)“. 6 ETSI TS 118 106: “oneM2M; Management Enablement (BBF) (oneM2M TS-00
27、06)“. 7 IETF RFC 6920: “Naming Things with Hashes“. 8 IANA TLS Cipher Suite Registry. NOTE: Available at http:/www.iana.org/assignments/tls-parameters/tls-parameters.xhtml. 2.2 Informative references References are either specific (identified by date of publication and/or edition number or version n
28、umber) 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 guaran
29、tee 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.
30、 ETSI ETSI TS 118 122 V2.0.0 (2017-05)7oneM2M TS-0022 version 2.0.0 Release 23 Definitions and abbreviations 3.1 Definition For the purposes of the present document, the terms and definitions given in ETSI TS 118 111 1, ETSI TS 118 101 2 and the following apply: Application Configuration: procedure
31、that configures an AE on an M2M Node in the Field Domain for M2M Service Layer operation authentication profile: security information needed to establish mutually-authenticated secure communications Configuration AE: AE whose role is to configure the M2M System, including the M2M Node in the Field D
32、omain Configuration IPE: IPE that provides the capability to configure the M2M Node in the Field Domain by interworking the exchange of information between the M2M Node and the M2M System credential object: end-point of a security protocol Service Layer Configuration: procedure that configures a CSE
33、 on an M2M Node in the Field Domain for M2M Service Layer operation 3.2 Abbreviations For the purposes of the present document, the abbreviations given in ETSI TS 118 111 1, ETSI TS 118 101 2 and the following apply: MO Managed Object (BBF specified management) or Management Object (OMA specified ma
34、nagement) NP Not Present XML eXtensible Markup Language XSD XML Schema Definition 4 Conventions The key words “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 Introduction Devices in the Fie
35、ld Domain that host oneM2M AEs and CSEs require configuration that permits the AE or CSE to successfully operate in the M2M Service Layer. ETSI TS 118 101 2 and ETSI TS 118 103 3 specifies much of what is needed to configure these devices in the Field Domain (i.e. ADN, ASN/MN). Specifically, ETSI TS
36、 118 101 2 provides: Guidance on how a CSE is minimally provisioned in Annex E of the specification 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
37、 nodes and M2M Applications are enrolled in the M2M System such that the node in the Field domain can establish connectivity with a CSE. ETSI TS 118 101 2 heavily relies on clause 6 and on the Remote Security Provisioning Framework (RSPF) of ETSI TS 118 103 3 to specify how the security credentials
38、of ASN/MN and ADN nodes and M2M Applications are established in the M2M System for the enrolment of the node or M2M Application in the M2M System. ETSI ETSI TS 118 122 V2.0.0 (2017-05)8oneM2M TS-0022 version 2.0.0 Release 2 Specifications for how the ADN and ASN/MN nodes in the Field Domain are mana
39、ged using external management technologies in clause 6.2.4 of ETSI TS 118 101 2. Guidance for how the ADN and ASN/MN nodes in the Field Domain can be configured without the support of external management technologies in clause 8.1.2. The above clauses in ETSI TS 118 101 2 assume that, for a M2M Appl
40、ication to operate in the M2M System, all required information needed to establish M2M Service operation between a Registrar or Hosting CSE and the AE or CSE in the Field Domain is configured before registration of the AE or CSE to the M2M System. The present document specifies the additional archit
41、ectural elements, resources and procedures necessary to configure ASN/MN and ADN nodes in the Field Domain in order for that device to establish M2M Service Layer operation. These architectural elements, resources and procedures are in addition to the architectural elements, resources and procedures
42、 already defined in ETSI TS 118 101 2 and ETSI TS 118 103 3. 6 Architectural Aspects 6.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 ETSI TS 118 101 2 in order to convey the information ele
43、ments to the ASN/MN or ADN nodes that host the AE or CSE prior to or during M2M Service Layer operation and to the AE or CSE during M2M Service Layer operation. uni0043uni006Funi006Euni0066uni0069uni0067uni0075uni0072uni0061uni0074uni0069uni006Funi006Euni0020uni0041uni0045uni004Duni0063uni0061uni004
44、9uni006Euni0066uni0072uni0061uni0073uni0074uni0072uni0075uni0063uni0074uni0075uni0072uni0065uni0020uni0044uni006Funi006Duni0061uni0069uni006Euni0046uni0069uni0065uni006Cuni0064uni0020uni0044uni006Funi006Duni0061uni0069uni006Euni0043uni006Funi006Euni0066uni0069uni0067uni0075uni0072uni0061uni0074uni00
45、69uni006Funi006Euni0020uni0049uni0050uni0045uni0075uni006Euni0073uni0070uni0065uni0063uni0069uni0066uni0069uni0065uni0064uni0049uni004Euni002Duni0043uni0053uni0045uni004Duni0063uni0061ASN/MNuni0043uni0053uni0045uni0041uni0045uni004Duni0063uni0061uni004Duni0063uni0063ADNuni0041uni0045uni004Duni0063un
46、i0061uni0044uni004Duni0020uni0053uni0065uni0072uni0076uni0065uni0072uni004Duni0063uni006Euni0020uni0028uni006Duni0073uni0029uni006Duni0063uni006Duni0063uni006Duni0063Figure 6.1-1: Architectural Aspects for Configuration of ASN/MN and ADN Nodes ETSI ETSI TS 118 122 V2.0.0 (2017-05)9oneM2M TS-0022 ver
47、sion 2.0.0 Release 2Figure 6.1-1 depicts three (3) methods, in which ADN or ASN/MN nodes are configured using the following: 1) Device Management technologies using the mc reference point defined in clause 6 of ETSI TS 118 101 2. Using this method, the information that is used to configure the ASN/M
48、N or ADN is described as resource types that are hosted in the IN-CSE. 2) oneM2M Mcc and Mca reference point when M2M Service Layer operation has been established to the AE or CSE. Establishment of the M2M Service Layer operation includes actions such as setting up security associations and registra
49、tion of the M2M entities as per ETSI TS 118 103 3 and ETSI TS 118 101 2. 3) oneM2M IPE technology where the IPE interworks the information exchange between the ADN and ASN/MN and the IN-CSE. This type of IPE is called a Configuration IPE in order to depict the role and capabilities of the IPE related to the present document. NOTE: The reference point between the Configuration IPE and the ADN and ASN/MN is unspecified in the present document. In addition, figure 6.1-1 introduces an AE w
