ITU-T Y 4500 6-2018 oneM2M management enablement (BBF) (Study Group 20).pdf

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.6 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 (BBF) Recommendation ITU-T Y.4500.6 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.6 (03/2018) i Recommendation ITU-T Y.4500.6 oneM2M management enablement (BBF) Summary Recommendation ITU-T Y.4500.6 specifies the usage of the BBF TR-069 protocol and the corresponding message flows including normal as well as error cases to fulfil o

10、neM2M management requirements. Protocol mapping between the oneM2M service layer and BBF TR-069 protocol. The Mca reference point, ms interface and la interface are possibly involved in this protocol mapping. Mapping between oneM2M management-related resources and the BBF TR-069 protocol remote proc

11、edure calls (RPCs) and BBF TR-181i2 data model. Specification of new BBF TR-181 data model elements to fulfil oneM2M specific management requirements that cannot be currently translated. History Edition Recommendation Approval Study Group Unique ID* 1.0 ITU-T Y.4500.6 2018-03-01 20 11.1002/1000/1350

12、2 Keywords Broadband Forum, oneM2M, device management. * To access the Recommendation, 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.6 (03/2018) FOR

13、EWORD The International Telecommunication Union (ITU) is the United Nations 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 studyin

14、g technical, operating and tariff questions and issuing Recommendations on them 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

15、which, in turn, produce Recommendations on these topics. The approval of ITU-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

16、and IEC. NOTE In this Recommendation, the expression “Administration“ is used 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

17、(to ensure, e.g., interoperability or applicability) and compliance with the 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 wo

18、rds does not suggest that compliance with the Recommendation is required of 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 con

19、cerning 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 intellectual property, protected by

20、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/. NOTE This Recommendation departs slightly from

21、the usual editorial style of ITU-T Recommendations to preserve existing cross-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.6 (03/2018) iii Tabl

22、e 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 . 2 4 Abbreviations and acronyms 2 5 Conventions 2 6 Mapping of basic data types . 3 7 Mapping of identifiers 4 7.0 Introduction 4 7.1 Mapping of device identifiers

23、to the node resource . 4 7.2 Identifier of an object instance . 4 8 Mapping of resources . 5 8.0 Introduction 5 8.1 General mapping assumptions 5 8.2 Resource deviceInfo 5 8.3 Resource memory 6 8.4 Resource battery 6 8.5 Resource areaNwkInfo 7 8.6 Resource areaNwkDeviceInfo . 7 8.7 Resource eventLog

24、 8 8.8 Resource deviceCapability 8 8.9 Resource firmware . 9 8.10 Resource software 10 8.11 Resource reboot . 12 8.12 Resource cmdhPolicy 12 8.13 Resource type . 17 8.14 Resource type . 18 9 Mapping of procedures for management 18 9.0 Introduction 18 9.1 Resource type primitive mappings 18 9.2 and r

25、esource primitive mappings . 28 10 Server interactions 36 10.0 Introduction 36 10.1 Communication session establishment . 36 10.2 Processing of requests and responses . 37 10.3 Discovery and synchronization of resources 38 iv Rec. ITU-T Y.4500.6 (03/2018) Page 10.4 Access management . 38 11 New mana

26、gement technology specific resources . 39 Annex A oneM2M specification update and maintenance control procedure 40 Bibliography. 41 Rec. ITU-T Y.4500.6 (03/2018) 1 Recommendation ITU-T Y.4500.6 oneM2M management enablement (BBF) 1 Scope This Recommendation describes the protocol mappings between man

27、agement resources for oneM2M and the BBF TR-181i2 data model. This Recommendation contains oneM2M Release 2 specification oneM2M Management Enablement (BBF) V2.0.1 and is equivalent to standards of oneM2M partners including ARIB, ATIS b-ATIS.oneM2M.TS0006V201, CCSA b-CCSA M2M-TS-0006-V2.0.1, ETSI b-

28、ETSI TS 118 106, TIA, TSDSI b-TSDSI STD T1.oneM2M TS-0006-2.0.1 V1.0.0, TTA b-TTAT.MM-TS.0006 v2.0.1 and TTC b-TTC TS-M2M-0006v2.0.1. 2 References The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommen

29、dation. 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 to investigate the possibility of applying the most recent edition of the Recommendations and other reference

30、s 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, the status of a Recommendation. ITU-T Y.4500.1 Recommendation ITU-T Y.4500.1 (2018), oneM2M Functional archi

31、tecture. ITU-T Y.4500.4 Recommendation ITU-T Y.4500.4 (2018), Service layer core protocol specification. ITU-T Y.4500.11 Recommendation ITU-T Y.4500.11 (2018), Common terminology. BBF TR-069 TR-069, Issue 1, Amendment 6 (2018), CPE WAN management protocol. BBF TR-106 TR-106, Issue 1, Amendment 7 (20

32、13), Data model template for TR-069-enabled devices. BBF TR-131 TR-131, Issue 1, Amendment 1 (2015), ACS northbound interface requirements. BBF TR-181 TR-181, Issue 2, Amendment 11 (2016), Device data model for TR-069. 3 Definitions 3.1 Terms defined elsewhere This Recommendation uses the following

33、terms defined elsewhere: For the purposes of this Recommendation, the terms and definitions given in oneM2M TS-0011 ITU-T Y.4500.11 and the following apply. 3.1.1 application entity ITU-T Y.4500.11: represents an instantiation of application logic for end-to-end M2M solutions. 2 Rec. ITU-T Y.4500.6

34、(03/2018) 3.1.2 common services entity (CSE) ITU-T Y. 4500.11: Represents an instantiation of a set of common service functions of the M2M environments. Such service functions are exposed to other entities through reference points. 3.1.3 CPE proxier BBF TR-069: A CPE that is capable of proxying the

35、communication between an ACS and a proxied device. 3.2 Terms defined in this Recommendation None. 4 Abbreviations and acronyms For the purposes of this Recommendation, the abbreviations given in oneM2M TS-0011 ITU-T Y.4500.11 and the following apply: ACS Auto-Configuration Server ADN Application-Ded

36、icated Node AE Application Entity ASN Application Service Node CMDH Communication Management and Delivery Handling CPE Customer Premises Equipment CWMP Common premises equipment Wide area network Management Protocol DM Device Management DU Deployment Unit IN-CSE Infrastructure Node-Common Services E

37、ntity LAN Local Area Network MN Middle Node MoCA Multimedia over Coax Alliance OUI Organizationally Unique Identifier 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

38、UUID Universal Unique Identifier XML Extensible Markup Language Wi-Fi Wireless Fidelity 5 Conventions The keywords “shall“, “shall not“, “should“, “should not“, “may“, “need not“ in this Recommendation are to be interpreted as follows. Rec. ITU-T Y.4500.6 (03/2018) 3 Shall/shall not: Requirements 1)

39、 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 with this Recommendation) must support it; 3) effect on deployments: every depl

40、oyment (M2M service based on this Recommendation) must use the standardized feature where applicable otherwise interoperability problems with other services could arise, for example. Should/should not Recommendation 1) effect on this Recommendation: This Recommendation needs to describe a solution t

41、hat 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 recommended. May/need not: Permission/Option 1) effect on this

42、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 may not use it. 6 Mapping of basic data types BBF TR-10

43、6 specifies the object structure supported by BBF 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 parameters that follow the conventions of section 3 of BBF TR-106 and data types described in

44、 Table 4 of BBF TR-106. See Table 6-1. Table 6-1 Data type mapping oneM2M data types Mapping to data types in BBF 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 Mappi

45、ng is constrained to the size 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-sep

46、arated Lists Data structure is represented by comma-separated list as described in section 3.2.3 of BBF TR-106 4 Rec. ITU-T Y.4500.6 (03/2018) In some instances, the conversion of the contents between data types will cause an error to occur (e.g., xs:integer is too long). When an error occurs in the

47、 conversion of a data type, the response status code is STATUS_BAD_REQUEST. 7 Mapping of identifiers 7.0 Introduction BBF TR-069 specifies three types of device, known as customer premises equipment (CPE), that are capable of being managed from the perspective of the BBF TR-069 agent as follows. CPE

48、 that hosts the BBF TR-069 agent: section A.3.3.1 of BBF TR-069 defines the required fields for a CPE to be identified. These fields include the organizationally unique identifier (OUI) and serial number (SN) of the CPE assigned by the CPE manufacturer. The manufacturer may assign a product class (P

49、C) to the CPE. The format of the identifier 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 common premises equipment wide area network management protocol (CWMP) agent for each virtual device. Embedded device: This type of device is addressed as one or more objects within the data