TIA-5022 006-2015 Management Enablement (BBF) (oneM2M TS-0006-v1 0 1).pdf

1、 TIA-5022.006 October 2015Management Enablement (BBF) (oneM2M TS-0006-v1.0.1) NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstandings between manufacturers and purchasers, facilitating interchangeability and improvement of pro

2、ducts, and assisting the purchaser in selecting and obtaining with minimum delay the proper product for their particular need. The existence of such Standards and Publications shall not in any respect preclude any member or non-member of TIA from manufacturing or selling products not conforming to s

3、uch Standards and Publications. Neither shall the existence of such Standards and Publications preclude their voluntary use by Non-TIA members, either domestically or internationally. Standards and Publications are adopted by TIA in accordance with the American National Standards Institute (ANSI) pa

4、tent policy. By such action, TIA does not assume any liability to any patent owner, nor does it assume any obligation whatever to parties adopting the Standard or Publication. This Standard does not purport to address all safety problems associated with its use or all applicable regulatory requireme

5、nts. It is the responsibility of the user of this Standard to establish appropriate safety and health practices and to determine the applicability of regulatory limitations before its use. Any use of trademarks in this document are for information purposes and do not constitute an endorsement by TIA

6、 or this committee of the products or services of the company. (From Project No. TIA-PN-5022.006, formulated under the cognizance of the TIA TR-50 M2M- Smart Device Communications.) Published by TELECOMMUNICATIONS INDUSTRY ASSOCIATION Technology (b) there is no assurance that the Document will be ap

7、proved by any Committee of TIA or any other body in its present or any other form; (c) the Document may be amended, modified or changed in the standards development or any editing process. The use or practice of contents of this Document may involve the use of intellectual property rights (“IPR”), i

8、ncluding pending or issued patents, or copyrights, owned by one or more parties. TIA makes no search or investigation for IPR. When IPR consisting of patents and published pending patent applications are claimed and called to TIAs attention, a statement from the holder thereof is requested, all in a

9、ccordance with the Manual. TIA takes no position with reference to, and disclaims any obligation to investigate or inquire into, the scope or validity of any claims of IPR. TIA will neither be a party to discussions of any licensing terms or conditions, which are instead left to the parties involved

10、, nor will TIA opine or judge whether proposed licensing terms or conditions are reasonable or non-discriminatory. TIA does not warrant or represent that procedures or practices suggested or provided in the Manual have been complied with as respects the Document or its contents. If the Document cont

11、ains one or more Normative References to a document published by another organization (“other SSO”) engaged in the formulation, development or publication of standards (whether designated as a standard, specification, recommendation or otherwise), whether such reference consists of mandatory, altern

12、ate or optional elements (as defined in the TIA Procedures for American National Standards) then (i) TIA disclaims any duty or obligation to search or investigate the records of any other SSO for IPR or letters of assurance relating to any such Normative Reference; (ii) TIAs policy of encouragement

13、of voluntary disclosure (see TIA Procedures for American National Standards Annex C.1.2.3) of Essential Patent(s) and published pending patent applications shall apply; and (iii) Information as to claims of IPR in the records or publications of the other SSO shall not constitute identification to TI

14、A of a claim of Essential Patent(s) or published pending patent applications. TIA does not enforce or monitor compliance with the contents of the Document. TIA does not certify, inspect, test or otherwise investigate products, designs or services or any claims of compliance with the contents of the

15、Document. ALL WARRANTIES, EXPRESS OR IMPLIED, ARE DISCLAIMED, INCLUDING WITHOUT LIMITATION, ANY AND ALL WARRANTIES CONCERNING THE ACCURACY OF THE CONTENTS, ITS FITNESS OR APPROPRIATENESS FOR A PARTICULAR PURPOSE OR USE, ITS MERCHANTABILITY AND ITS NONINFRINGEMENT OF ANY THIRD PARTYS INTELLECTUAL PRO

16、PERTY RIGHTS. TIA EXPRESSLY DISCLAIMS ANY AND ALL RESPONSIBILITIES FOR THE ACCURACY OF THE CONTENTS AND MAKES NO REPRESENTATIONS OR WARRANTIES REGARDING THE CONTENTS COMPLIANCE WITH ANY APPLICABLE STATUTE, RULE OR REGULATION, OR THE SAFETY OR HEALTH EFFECTS OF THE CONTENTS OR ANY PRODUCT OR SERVICE

17、REFERRED TO IN THE DOCUMENT OR PRODUCED OR RENDERED TO COMPLY WITH THE CONTENTS. TIA SHALL NOT BE LIABLE FOR ANY AND ALL DAMAGES, DIRECT OR INDIRECT, ARISING FROM OR RELATING TO ANY USE OF THE CONTENTS CONTAINED HEREIN, INCLUDING WITHOUT LIMITATION ANY AND ALL INDIRECT, SPECIAL, INCIDENTAL OR CONSEQ

18、UENTIAL DAMAGES (INCLUDING DAMAGES FOR LOSS OF BUSINESS, LOSS OF PROFITS, LITIGATION, OR THE LIKE), WHETHER BASED UPON BREACH OF CONTRACT, BREACH OF WARRANTY, TORT (INCLUDING NEGLIGENCE), PRODUCT LIABILITY OR OTHERWISE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. THE FOREGOING NEGATION OF DA

19、MAGES IS A FUNDAMENTAL ELEMENT OF THE USE OF THE CONTENTS HEREOF, AND THESE CONTENTS WOULD NOT BE PUBLISHED BY TIA WITHOUT SUCH LIMITATIONS. oneM2M Partners Type 1 (ARIB, ATIS, CCSA, ETSI, TIA, TTA, TTC) Page 2 of 42 This is a draft oneM2M document and should not be relied upon; the final version, i

20、f any, will be made available by oneM2M Partners Type 1. About oneM2M 18 The purpose and goal of oneM2M is to develop technical specifications which address the 19 need for a common M2M Service Layer that can be readily embedded within various 20 hardware and software, and relied upon to connect the

21、 myriad of devices in the field with 21 M2M application servers worldwide. 22 More information about oneM2M may be found at: http/www.oneM2M.org 23 Copyright Notification 24 No part of this document may be reproduced, in an electronic retrieval system or otherwise, 25 except as authorized by written

22、 permission. 26 The copyright and the foregoing restriction extend to reproduction in all media. 27 2015, oneM2M Partners Type 1 (ARIB, ATIS, CCSA, ETSI, TIA, TTA, TTC). 28 All rights reserved. 29 Notice of Disclaimer the final version, if any, will be made available by oneM2M Partners Type 1. Conte

23、nts 48 Contents . 3 49 1. Scope 5 50 2 References 5 51 2.1 Normative references . 5 52 2.2 Informative references . 5 53 3 Definitions, symbols, abbreviations and acronyms 5 54 3.1 Definitions . 5 55 3.2 Abbreviations . 5 56 3.4 Acronyms 6 57 4 Conventions . 6 58 5 Mapping of basic data types . 6 59

24、 6 Mapping of identifiers 6 60 6.1 Mapping of Device identifiers to the Node Resource 7 61 6.2 Identifier of an object instance . 7 62 7 Mapping of resources . 7 63 7.1 General mapping assumptions 8 64 7.1.1 Mapping of Device identifiers. 8 65 7.1.2 Mapping of Embedded Devices 8 66 7.2 Resource devi

25、ceInfo 8 67 7.3 Resource memory 9 68 7.4 Resource battery 9 69 7.5 Resource areaNwkInfo 10 70 7.6 Resource areaNwkDeviceInfo . 10 71 7.7 Resource eventLog 11 72 7.8 Resource deviceCapability 11 73 7.9 Resource firmware 12 74 7.10 Resource software . 13 75 7.11 Resource reboot . 15 76 7.12 Resource c

26、mdhPolicy 15 77 7.12.1 Resource activeCmdhPolicy . 16 78 7.12.2 Resource cmdhDefaults 16 79 7.12.3 Resource cmdhDefEcValues 17 80 7.12.4 Resource cmdhEcDefParamValues 17 81 7.12.5 Resource cmdhLimits. 18 82 7.12.6 Resource cmdhNetworkAccessRules 18 83 7.12.7 Resource cmdhNwAccessRule . 19 84 7.12.8

27、Resource cmdhBuffer . 19 85 7.13 Resource Type . 20 86 7.14 Resource Type 20 87 8 Mapping of procedures for management 21 88 8.1 Resource Type primitive mappings 21 89 8.1.1 Alias-Based Addressing Mechanism 21 90 8.1.2 Create primitive mapping . 21 91 8.1.2.1 M2M Service Layer Resource Instance Iden

28、tifier mapping 21 92 8.1.3 Delete primitive mapping . 22 93 8.1.3.1 Delete primitive mapping for deletion of Object Instances . 22 94 8.1.3.2 Delete primitive mapping for software un-install operation . 22 95 8.1.4 Update primitive mapping 24 96 8.1.4.1 Update primitive mapping for Parameter modific

29、ations . 24 97 8.1.4.2 Update primitive mapping for upload file transfer operations 24 98 8.1.4.3 Update primitive mapping for download file transfer operations 26 99 8.1.4.4 Update primitive mapping for reboot operation . 27 100 oneM2M Partners Type 1 (ARIB, ATIS, CCSA, ETSI, TIA, TTA, TTC) Page 4

30、of 42 This is a draft oneM2M document and should not be relied upon; the final version, if any, will be made available by oneM2M Partners Type 1. 8.1.4.5 Update primitive mapping for factory reset operation 28 101 8.1.4.6 Update primitive mapping for software install operation . 28 102 8.1.5 Retriev

31、e primitive mapping 30 103 8.1.6 Notify primitive mapping . 30 104 8.1.6.1 Procedure for subscribed Resource attributes. 30 105 8.1.6.2 Notification primitive mapping . 31 106 8.2 and resource primitive mappings . 32 107 8.2.1 Update (Execute) primitive for the resource 32 108 8.2.1.1 Execute File D

32、ownload . 32 109 8.2.1.2 Execute File Upload Operations 33 110 8.2.1.3 Report Results using TransferComplete RPC 34 111 8.2.1.4 Execute Software Operations with ChangeDUState RPC 35 112 8.2.1.5 Report Results with ChangeDUStateComplete RPC 35 113 8.2.1.6 Execute Reboot operation 37 114 8.2.1.7 Execu

33、te Factory Reset operation . 37 115 8.2.2 Delete resource primitive mapping 38 116 8.2.3 Update (Cancel) primitive mapping . 38 117 8.2.4 Delete primitive mapping 39 118 9 Server Interactions . 40 119 9.1 Communication Session Establishment 40 120 9.1.1 IN-CSE to ACS Communication Session Establishm

34、ent 40 121 9.1.2 ACS to IN-CSE Communication Session Establishment 40 122 9.2.3 ACS and IN-CSE Communication Session Requirements . 40 123 9.2 Processing of Requests and Responses . 41 124 9.2.1 Request and Notification Formatting 41 125 9.2.2 ACS Request Processing Requirements 41 126 9.2.3 ACS Not

35、ification Processing Requirements 41 127 9.3 Discovery and Synchronization of Resources . 41 128 9.4 Access Management 41 129 9.4.1 Access Management Requirements 42 130 10 New Management Technology Specific Resources 42 131 History 42 132 133 134 oneM2M Partners Type 1 (ARIB, ATIS, CCSA, ETSI, TIA,

36、 TTA, TTC) Page 5 of 42 This is a draft oneM2M document and should not be relied upon; the final version, if any, will be made available by oneM2M Partners Type 1. 1. Scope 135 The present document describes the protocol mappings between the management Resources for oneM2M and the BBF 136 TR-181i2 D

37、ata Model 6. 137 2 References 138 2.1 Normative references 139 The following referenced documents are necessary, partially or totally, for the application of the present document. 140 Their use in the context of this TS is specified by the normative statements that are referring back to this clause.

38、 141 1 oneM2M TS-0001: “Functional Architecture”. 142 2 oneM2M TS-0004: “Service Layer Core Protocol Specification”. 143 3 oneM2M TS-0011: “Definitions and Acronyms”. 144 4 BBF: “TR-069 CPE WAN Management Protocol” Issue: 1 Amendment 5, November 2013. 145 5 BBF: “TR-106 Data Model Template for TR-06

39、9-Enabled Devices”, Issue 1, Amendment 7, 146 September 2013. 147 6 BBF: “TR-181 Device Data Model for TR-069, Issue 2 Amendment 8”, September 2014. 148 7 BBF: “TR-131 ACS Northbound Interface Requirements, Issue:1”, November 2009. 149 2.2 Informative references 150 i.1 oneM2M Drafting Rules 151 (ht

40、tp:/member.onem2m.org/Static_pages/Others/Rules_Pages/oneM2M-Drafting-Rules-152 V1_0.doc) 153 3 Definitions, symbols, abbreviations and acronyms 154 3.1 Definitions 155 For the purposes of the present document, the terms and definitions given in TS-0011 3 apply. 156 CPE Proxier A CPE that is capable

41、 of proxying the communication between an ACS and a Proxied Device as 157 defined in TR-069 4. 158 3.2 Abbreviations 159 For the purposes of the present document, the abbreviations given in TS-0011 3 apply. 160 ACS Auto-Configuration Server 161 ADN Application Dedicated Node 162 AE Application Entit

42、y 163 ASN Application Service Node 164 CMDH Communication Management and Delivery Handling 165 CPE Customer Premise Equipment 166 CSE Common Services Entity 167 CWMP CPE WAN Management Protocol 168 DU Deployment Unit 169 oneM2M Partners Type 1 (ARIB, ATIS, CCSA, ETSI, TIA, TTA, TTC) Page 6 of 42 Thi

43、s is a draft oneM2M document and should not be relied upon; the final version, if any, will be made available by oneM2M Partners Type 1. IN-CSE CSE which resides in the Infrastructure Node 170 LAN Local Area Network 171 MN Middle Node 172 OUI Organizationally Unique Identifier 173 PC Product Class 1

44、74 RPC Remote Procedure Call 175 SN Serial Number 176 URI Uniform Resource Identifier 177 URL Uniform Resource Locator 178 USB Universal Serial Bus 179 UUID Universal Unique Identifier 180 XML Extensible Markup Language 181 3.4 Acronyms 182 For the purposes of the present document, the acronyms give

45、n in TR-0004 3 apply. 183 4 Conventions 184 The key words “Shall”, ”Shall not”, “May”, ”Need not”, “Should”, ”Should not” in this document are to be interpreted 185 as described in the oneM2M Drafting Rules i.1 186 5 Mapping of basic data types 187 TR-106 5 specifies the object structure supported b

46、y TR-069 enabled devices and specifies the structural requirements 188 for the data hierarchy. This clause includes the mapping attribute data types to TR-181 6 parameters which follows the 189 conventions of section 3 of TR-106 5 and data types described in Table 4 of TR-106 5. 190 Table 5-1: Data

47、Type Mapping 191 oneM2M Data Types Mapping to data types in TR-106 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 size of the long data type. X

48、s: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 structure is represented by comma

49、 separated list as described in section 3.2.3 of TR-106 5. 192 In some instances the conversion of the contents between data types will cause an error to occur (e.g., xs:integer to 193 long). When an error occurs in the conversion of a data type, the STATUS_BAD_REQUEST response status code. 194 6 Mapping of identifiers 195 The TR-069 4 specification defines three (3) types of devices, known as CPEs, that are capable of being managed 196 from the perspective of the TR-069 agent: 197 CPE that hosts