1、 ETSI TS 118 106 V1.1.0 (2016-03) oneM2M; Management Enablement (BBF) (oneM2M TS-0006 version 1.1.4 Release 1) floppy3TECHNICAL SPECIFICATION oneM2M TS-0006 version 1.1.4 Release 1 ETSI ETSI TS 118 106 V1.1.0 (2016-03)2Reference RTS/oneM2M-000006v110 Keywords IoT, M2M ETSI 650 Route des Lucioles F-0
2、6921 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-sear
3、ch 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
4、 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. Informatio
5、n 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 Notif
6、ication 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 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 registe
8、red for 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-0006 version 1.1.4 Release 1 ETSI ETSI TS 118 106 V1.1.0 (2016-03)3Contents Intellectual Property Rights 5g3Foreword . 5g31. Scope 6
9、g32 References 6g32.1 Normative references . 6g32.2 Informative references 6g33 Definitions, abbreviations and acronyms . 6g33.1 Definitions 6g33.2 Abbreviations . 7g33.3 Acronyms . 7g34 Conventions 7g35 Mapping of basic data types . 7g36 Mapping of identifiers 8g36.0 Introduction 8g36.1 Mapping of
10、Device identifiers to the Node Resource 8g36.2 Identifier of an object instance . 8g37 Mapping of resources . 9g37.0 Introduction 9g37.1 General mapping assumptions 9g37.1.0 General 9g37.1.1 Mapping of Device identifiers 9g37.1.2 Mapping of Embedded Devices 9g37.2 Resource deviceInfo 9g37.3 Resource
11、 memory 10g37.4 Resource battery 10g37.5 Resource areaNwkInfo 11g37.6 Resource areaNwkDeviceInfo . 11g37.7 Resource eventLog 11g37.8 Resource deviceCapability 12g37.9 Resource firmware . 13g37.10 Resource software 14g37.11 Resource reboot . 15g37.12 Resource cmdhPolicy 15g37.12.0 Introduction. 15g37
12、.12.1 Resource activeCmdhPolicy 15g37.12.2 Resource cmdhDefaults . 16g37.12.3 Resource cmdhDefEcValue . 16g37.12.4 Resource cmdhEcDefParamValues 17g37.12.5 Resource cmdhLimits . 17g37.12.6 Resource cmdhNetworkAccessRules . 18g37.12.7 Resource cmdhNwAccessRule 18g37.12.8 Resource cmdhBuffer . 18g37.1
13、3 Resource Type . 19g37.14 Resource Type 19g38 Mapping of procedures for management 19g38.0 Introduction 19g38.1 Resource Type primitive mappings . 19g38.1.0 Introduction. 19g38.1.1 Alias-Based Addressing Mechanism 20g38.1.2 Create primitive mapping . 20g38.1.2.0 Introduction . 20g38.1.2.1 M2M Servi
14、ce Layer Resource Instance Identifier mapping 20g38.1.3 Delete primitive mapping . 20g3oneM2M TS-0006 version 1.1.4 Release 1 ETSI ETSI TS 118 106 V1.1.0 (2016-03)48.1.3.1 Delete primitive mapping for deletion of Object Instances . 20g38.1.3.2 Delete primitive mapping for software un-install operati
15、on . 20g38.1.4 Update primitive mapping 22g38.1.4.1 Update primitive mapping for Parameter modifications . 22g38.1.4.2 Update primitive mapping for upload file transfer operations 22g38.1.4.3 Update primitive mapping for download file transfer operations . 23g38.1.4.4 Update primitive mapping for re
16、boot operation 25g38.1.4.5 Update primitive mapping for factory reset operation 25g38.1.4.6 Update primitive mapping for software install operation 25g38.1.5 Retrieve primitive mapping 27g38.1.6 Notify primitive mapping . 27g38.1.6.0 Introduction . 27g38.1.6.1 Procedure for subscribed Resource attri
17、butes. 27g38.1.6.2 Notification primitive mapping . 28g38.2 and resource primitive mappings . 28g38.2.1 Update (Execute) primitive for the resource 28g38.2.1.0 Introduction . 28g38.2.1.1 Execute File Download . 29g38.2.1.2 Execute File Upload Operations . 29g38.2.1.3 Report Results using TransferCom
18、plete RPC . 29g38.2.1.4 Execute Software Operations with ChangeDUState RPC . 30g38.2.1.5 Report Results with ChangeDUStateComplete RPC 31g38.2.1.6 Execute Reboot operation . 32g38.2.1.7 Execute Factory Reset operation . 32g38.2.2 Delete resource primitive mapping 32g38.2.3 Update (Cancel) primitive
19、mapping 33g38.2.4 Delete primitive mapping . 34g39 Server Interactions 34g39.0 Introduction 34g39.1 Communication Session Establishment 34g39.1.1 IN-CSE to ACS Communication Session Establishment . 34g39.1.2 ACS to IN-CSE Communication Session Establishment . 35g39.1.3 ACS and IN-CSE Communication S
20、ession Requirements . 35g39.2 Processing of Requests and Responses 35g39.2.1 Request and Notification Formatting 35g39.2.2 ACS Request Processing Requirements . 35g39.2.3 ACS Notification Processing Requirements . 35g39.3 Discovery and Synchronization of Resources 36g39.4 Access Management . 36g39.4
21、.1 Access Management Requirements 36g310 New Management Technology Specific Resources . 36g3History 37g3oneM2M TS-0006 version 1.1.4 Release 1 ETSI ETSI TS 118 106 V1.1.0 (2016-03)5Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to
22、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 avai
23、lable 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
24、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-0006 version 1.1.4 Release 1 ETSI ETSI TS 118 106 V1.1.0 (2016-0
25、3)61. Scope The present document describes the protocol mappings between the management Resources for oneM2M and the BBF TR-181i2 Data Model 6. 2 References 2.1 Normative references References are either specific (identified by date of publication and/or edition number or version number) or non-spec
26、ific. 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 ter
27、m 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 ETSI TS 118 111: “oneM2M; Common
28、 Terminology (oneM2M TS-0011)“. 4 BroadBand Forum TR-069: “CPE WAN Management Protocol“ Issue: 1 Amendment 5, November 2013. 5 BroadBand Forum TR-106: “Data Model Template for TR-069-Enabled Devices“, Issue 1, Amendment 7, September 2013. 6 BroadBand Forum TR-181: “Device Data Model for TR-069“, Iss
29、ue 2 Amendment 8, September 2014. 7 BroadBand Forum TR-131: “ACS Northbound Interface Requirements“, Issue: 1, November 2009. 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
30、, 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 ref
31、erenced 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. 3 Definitions, abbreviations and acronyms 3.1
32、Definitions For the purposes of the present document, the terms and definitions given in ETSI TS 118 111 3 and the following apply: CPE Proxier: CPE that is capable of proxying the communication between an ACS and a Proxied Device as defined in BBF TR-069 4 oneM2M TS-0006 version 1.1.4 Release 1 ETS
33、I ETSI TS 118 106 V1.1.0 (2016-03)73.2 Abbreviations For the purposes of the present document, the abbreviations given in ETSI TS 118 111 3 and the following apply: ACS Auto-Configuration Server ADN Application Dedicated Node AE Application Entity ASN Application Service Node BBF Broadband Forum CMD
34、H Communication Management and Delivery Handling CPE Customer Premise Equipment CSE Common Services Entity CWMP CPE WAN Management Protocol DM Device Management DU Deployment UnitIN-CSE CSE which resides in the Infrastructure Node LAN Local Area Network MN Middle Node OUI Organizationally Unique Ide
35、ntifier PC Product Class RPC Remote Procedure Call SN Serial Number UPA Universal Powerline Association URI Uniform Resource Identifier URL Uniform Resource Locator USB Universal Serial Bus UUID Universal Unique Identifier XML Extensible Markup Language 3.3 Acronyms For the purposes of the present d
36、ocument, the acronyms given in ETSI TS 118 111 3 apply. 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 Mapping of basic data types BBF TR-106 5 specifies the ob
37、ject structure supported by TR-069 enabled devices and specifies the structural requirements for the data hierarchy. This clause includes the mapping attribute data types to BBF TR-181 6 parameters which follows the conventions of section 3 of BBF TR-106 5 and data types described in table 4 of BBF
38、TR-106 5. Table 5-1: Data Type Mapping oneM2M Data Types Mapping to data types in BBF TR-106 5 Conversion Notes xs:boolean boolean xs:string string Mapping is constrained to the size of the string xs:unsignedInt unsignedInt xs:unsignedLong unsignedLong xs:integer long Mapping is constrained to the s
39、ize of the long data type Xs:positiveInteger unsignedLong Mapping is constrained to a lower limit of 1 and the size of the unsignedLong data type Xs:nonNegativeInteger unsignedLong Mapping is constrained the size of the unsignedLong data type Comma separated Lists Comma separated Lists Data structur
40、e is represented by comma separated list as described in section 3.2.3 of BBF TR-106 5 oneM2M TS-0006 version 1.1.4 Release 1 ETSI ETSI TS 118 106 V1.1.0 (2016-03)8In some instances the conversion of the contents between data types will cause an error to occur (e.g. xs:integer to long). When an erro
41、r occurs in the conversion of a data type, the STATUS_BAD_REQUEST response status code. 6 Mapping of identifiers 6.0 Introduction The BBF TR-069 4 specification defines three (3) types of devices, known as CPEs, that are capable of being managed from the perspective of the TR-069 agent: CPE that hos
42、ts the TR-069 agent: section A.3.3.1 Inform of BBF TR-069 4 defines the required fields for a CPE to be identified. These fields include the OUI and Serial Number of the CPE assigned by the CPE manufacturer. Optionally the manufacturer may assign a Product Class to the CPE. The format of the identif
43、ier is as follows: OUI-PC-SN. Virtual Device: This type of device is addressed as a CPE. The Virtual Device has its own OUI-PC-SN as represented by the CPE Proxier. The CPE Proxier emulates a CWMP agent for each Virtual Device. Embedded Device: This type of device is addressed as one or more objects
44、 within the data model of the CPE that hosts the TR-069 agent. 6.1 Mapping of Device identifiers to the Node Resource Node Resources are identified for each instance of an ADN, ASN and MN node and are identified using the M2M Node Identifier (M2M-Node-ID) defined in ETSI TS 118 101 1. CPE Device ide
45、ntifiers shall map to the nodeID attribute of the resource. The CPE Device identifiers are obtained from the contents of the following attributes: Device.DeviceInfo.ManufacturerOUI Device.DeviceInfo.ProductClass Device.DeviceInfo.SerialNumber Virtual Device identifiers shall map to the nodeID attrib
46、ute of the resource. The Virtual Device identifiers are obtained from the CPE Proxier using the contents of the attributes: Device.ManagementServer.VirtualDevice.i.ManufacturerOUI Device.ManagementServer.VirtualDevice.i.ProductClass Device.ManagementServer.VirtualDevice.i.SerialNumber Embedded Devic
47、e identifiers shall map to the nodeID attribute of the resource. The Embedded Device identifiers are obtained using the containing CPE Device or Virtual Device identifiers along with the contents of the attributes of the: Device.ManagementServer.EmbeddedDevice.i.ControllerID Device.ManagementServer.
48、EmbeddedDevice.i.ProxiedDeviceID 6.2 Identifier of an object instance The BBF TR-069 4 specification permits objects to have multiple object instances where each object instance is contained within the objectPath attribute of the Resource within the context of the Resources objectId as defined in cl
49、ause 7.1. oneM2M TS-0006 version 1.1.4 Release 1 ETSI ETSI TS 118 106 V1.1.0 (2016-03)9In order to allow the AE or CSE that originated the request that manipulates a Resource to easily align the M2M Service Layer with the Resources external technology identifier, the value of the object instance “i“ should be a part of the identifier of the Resource in the M2M Service Layer where possible. For example if the areaNetwork resource has an object instan
