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.4702 TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (03/2016) SERIES Y: GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS AND NEXT-GENERATION NETWORKS, INTERNET OF THINGS AND SMART CITIES Internet of things an
2、d smart cities and communities Management, control and performance Common requirements and capabilities of device management in the Internet of things Recommendation ITU-T Y.4702 ITU-T Y-SERIES RECOMMENDATIONS GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS AND NEXT-GENERATION NETWORKS,
3、 INTERNET OF THINGS AND SMART CITIES GLOBAL INFORMATION 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 S
4、ecurity Y.700Y.799 Performances Y.800Y.899 INTERNET 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
5、 Y.1500Y.1599 Signalling Y.1600Y.1699 Operation, 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 c
6、apabilities and service architecture Y.2200Y.2249 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.270
7、0Y.2799 Generalized mobility Y.2800Y.2899 Carrier 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
8、Infrastructure, connectivity and networks Y.4250Y.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 For further details, please refer
9、 to the list of ITU-T Recommendations. Rec. ITU-T Y.4702 (03/2016) i Recommendation ITU-T Y.4702 Common requirements and capabilities of device management in the Internet of things Summary Recommendation ITU-T Y.4702 provides the common requirements and capabilities of device management (DM) in the
10、Internet of things (IoT). The provided common requirements and capabilities are intended to be generally applicable in device management application scenarios. History Edition Recommendation Approval Study Group Unique ID* 1.0 ITU-T Y.4702 2016-03-15 20 11.1002/1000/12780 Keywords Common requirement
11、s, common capabilities, device management, DM, Internet of things (IoT). * 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. Rec. ITU-T Y.4702
12、(03/2016) ii FOREWORD 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 respons
13、ible for studying 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
14、-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 WTSA Resolution 1. In some areas of information technology which fall within ITU-Ts purview, the necessary standards are prepared on a collaborative
15、 basis with ISO 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 manda
16、tory provisions (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. Th
17、e use of such words 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
18、 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 intellectual propert
19、y, 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 2016 All rights reserved. N
20、o part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. Rec. ITU-T Y.4702 (03/2016) iii Table of Contents Page 1 Scope . 1 2 References . 1 3 Definitions 2 3.1 Terms defined elsewhere 2 3.2 Terms defined in this Recommendation . 2 4 Abbrevi
21、ations and acronyms 2 5 Conventions 3 6 Introduction . 3 7 Requirements of device management in the IoT 5 7.1 Characteristics specific to device management in the IoT . 5 7.2 Common requirements of device management in the IoT . 6 8 Common capabilities of device management in the IoT 9 8.1 Configura
22、tion management capability . 9 8.2 Performance management capability . 10 8.3 Fault management capability 10 8.4 Security management capability . 11 8.5 Connectivity management capability . 11 8.6 DM protocol engine capability . 12 8.7 Accounting management capability . 12 8.8 Service exposure web p
23、ortal capability . 12 8.9 Service exposure API capability . 12 Bibliography. 13 Rec. ITU-T Y.4702 (03/2016) 1 Recommendation ITU-T Y.4072 Common requirements and capabilities of device management in the Internet of things 1 Scope This Recommendation provides the common requirements and capabilities
24、of device management (DM) in the Internet of things (IoT). The provided common requirements and capabilities are intended to be generally applicable in device management application scenarios. The scope of this Recommendation includes: 1) Common requirements of device management in the IoT. 2) Commo
25、n capabilities of device management in the IoT. NOTE This Recommendation focuses on the requirements of DM for the interaction between devices and the various DM functional components. The DM client, a functional component optionally present in some IoT applications, and its specific requirements ar
26、e outside of the scope of this Recommendation. 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 Recommendati
27、ons 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 references listed below. A list of the currently valid ITU-T Recommendations is regularly publis
28、hed. 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.4000 Recommendation ITU-T Y.4000/Y.2060 (2012), Overview of Internet of things. ITU-T Y.2061 Recommendation ITU-T Y.2061 (2012), Requirements for the suppo
29、rt of machine-oriented communication applications in the next generation network environment. ITU-T Y.2066 Recommendation ITU-T Y.4100/Y.2066 (2014), Common requirements of the Internet of things. ITU-T Y.2067 Recommendation ITU-T Y.4101/Y.2067 (2014), Common requirements and capabilities of a gatew
30、ay for Internet of things applications. OMA-RD-LightweightM2M OMA-RD-LightweightM2M (2013), Lightweight Machine to Machine Requirements. 2 Rec. ITU-T Y.4702 (03/2016) 3 Definitions 3.1 Terms defined elsewhere This Recommendation uses the following terms defined elsewhere: 3.1.1 device ITU-T Y.4000:
31、With regard to the Internet of things, this is a piece of equipment with the mandatory capabilities of communication and the optional capabilities of sensing, actuation, data capture, data storage and data processing. 3.1.2 gateway ITU-T Y.2067: A unit in the Internet of things which interconnects t
32、he devices with the communication networks. It performs the necessary translation between the protocols used in the communication networks and those used by devices. 3.1.3 Internet of things (IoT) ITU-T Y.4000: A global infrastructure for the information society, enabling advanced services by interc
33、onnecting (physical and virtual) things based on existing and evolving interoperable information and communication technologies. NOTE 1 Through the exploitation of identification, data capture, processing and communication capabilities, the IoT makes full use of things to offer services to all kinds
34、 of applications, whilst ensuring that security and privacy requirements are fulfilled. NOTE 2 From a broader perspective, the IoT can be perceived as a vision with technological and societal implications. 3.2 Terms defined in this Recommendation This Recommendation defines or uses the following ter
35、ms: 3.2.1 Device management (DM) agent: The DM functional component responsible for collecting DM-related information from devices and gateways, reporting device related information to the DM manager or DM GW manager and analysing the commands from the DM manager or DM GW manager in order to execute
36、 DM-related tasks. 3.2.2 Device management (DM) client: The DM functional component optionally present in some IoT applications and interacting with the DM manager implemented by specific capabilities of the IoT SSAS capability set ITU-T Y.4000. It provides access to DM capabilities in order to enab
37、le device management functionalities in IoT applications. 3.2.3 Device management (DM) gateway (GW) manager: The DM functional component responsible for managing devices connected to a given gateway (GW). 3.2.4 Device management (DM) manager: With regard to device management in IoT, the DM functiona
38、l component, responsible for managing devices and gateways. NOTE The device management manager interacts with other DM functional components to get DM-related information of devices and gateways and to send commands for execution of DM-related tasks. According to the IoT application deployment scena
39、rios, it may be implemented by DM capabilities of the IoT service support and application support (SSAS) capability set ITU-T Y.4000 or by the IoT applications themselves. 4 Abbreviations and acronyms 3G Third Generation 4G Fourth Generation ADSL Asymmetric Digital Subscriber Line API Application Pr
40、ogramming Interface Rec. ITU-T Y.4702 (03/2016) 3 CPU Central Processing Unit DM Device Management GPRS General Packet Radio Service GW Gateway ID Identifier IoT Internet of Things IP Internet Protocol LAN Local Area Network OS Operating System OSS Operation Support System QoS Quality of Service SMS
41、 Short Message Service SSAS Service Support and Application Support WiFi Wireless Fidelity 5 Conventions In this Recommendation: The keywords “is required to“ indicate a requirement which must be strictly followed and from which no deviation is permitted if conformance to this document is to be clai
42、med. The keywords “is recommended“ indicate a requirement which is recommended but which is not absolutely required. Thus this requirement need not be present to claim conformance. The keywords “can optionally“ and “may“ indicate an optional requirement which is permissible, without implying any sen
43、se of being recommended. These terms are not intended to imply that the vendors implementation must provide the option and the feature can be optionally enabled by the network operator/service provider. Rather, it means the vendor may optionally provide the feature and still claim conformance with t
44、he specification. The term “IoT applications“ is used to identify applications which are operated over the IoT infrastructure. 6 Introduction Device management (DM) is an essential set of management capabilities in the Internet of things (IoT), providing support for, but not being limited to, device
45、s remote activation and de-activation, diagnostics, firmware/software updating and sensor node working status management ITU-T Y.4000. DM provides a set of capabilities through which the users of these capabilities can exercise various management tasks for devices, locally and remotely. Via DM, the
46、devices in IoT can be correctly configured and can correctly and efficiently operate through standardized interfaces and procedures. In addition, the users of these capabilities can know the current status of devices and get notification if there is something wrong with the devices. The ultimate aim
47、 of DM is to make sure that the applications running on a given device operate well. 4 Rec. ITU-T Y.4702 (03/2016) Traditionally, IoT applications interact directly with devices (and gateways) to realize DM functionalities. Nowadays, with the advent of service support and application support (SSAS)
48、capabilities ITU-T Y.4000 in the IoT infrastructure, the DM functionalities can be provided as a common service to IoT applications. IoT applications may directly use the DM service provided by DM capabilities of the SSAS capability set in order to realize DM functionalities without interacting with
49、 devices (and gateways) directly. This is a simpler and more efficient way to realize DM functionalities for IoT applications. In the IoT, the DM functional components can be deployed in devices, gateways, components which provide SSAS capabilities and IoT applications. Four DM functional components are identified: DM manager, DM agent, DM gateway (GW) manager and DM client. Figure 1 shows the positioning of these components in the IoT from the layering perspective of the IoT reference mo
