1、 Recomm 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.4115 TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (04/2017) SERIES Y: GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS, NEXT-GENERATION NETWORKS, INTERNET OF THINGS AND SMART CITIES Internet of thing
2、s and smart cities and communities Requirements and use cases Reference architecture for IoT device capability exposure Recommendation ITU-T Y.4115 ITU-T Y-SERIES RECOMMENDATIONS GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS, NEXT-GENERATION NETWORKS, INTERNET OF THINGS AND SMART CITI
3、ES 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 Security Y.700Y.799 Performances Y.
4、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 Y.1500Y.1599 Signalling Y.1600Y.1
5、699 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 capabilities and service architectu
6、re 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.2700Y.2799 Generalized mobility Y.280
7、0Y.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 Infrastructure, connectivity and n
8、etworks 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 Evaluation and assessment Y.4900Y.4999 For further details, please
9、refer to the list of ITU-T Recommendations. Rec. ITU-T Y.4115 (04/2017) i Recommendation ITU-T Y.4115 Reference architecture for IoT device capability exposure Summary Recommendation ITU-T Y.4115 specifies the reference architecture of IoT device capability exposure (IoT DCE) which supports IoT appl
10、ications in DCE devices (e.g., smart phones, tablets and home gateways) to access device capabilities exposed by IoT devices connected to the DCE device. This Recommendation clarifies the concept of the IoT DCE, identifies its general characteristics and common requirements and provides the referenc
11、e architecture for the IoT DCE and relevant high-level common procedures. History Edition Recommendation Approval Study Group Unique ID* 1.0 ITU-T Y.4115 2017-04-29 20 11.1002/1000/13266 Keywords Device capability, device capability exposure, Internet of things. * To access the Recommendation, type
12、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.4115 (04/2017) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency
13、 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 studying technical, operating and tariff questions and issuing Recommendations on them with a view to
14、 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 which, in turn, produce Recommendations on these topics. The approval of ITU-T Recommendations
15、 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 and IEC. NOTE In this Recommendation, the expression “Administration“ is used for conciseness
16、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 (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is
17、 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 words does not suggest that compliance with the Recommendation is required of any party. INTELLE
18、CTUAL 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 concerning the evidence, validity or applicability of claimed Intellectual Property Rights, wheth
19、er asserted by ITU members or others outside of the Recommendation development process. As of the date of approval of this Recommendation, ITU had received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are caution
20、ed 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 2017 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU
21、. Rec. ITU-T Y.4115 (04/2017) iii Table 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 Introduction . 2 7 General characteristics of IoT DCE 3 7.1 Provision of s
22、tandardized uniform interfaces . 3 7.2 Discovery and exposure of IoT devices . 4 7.3 Collection and exposure of data to IoT applications 4 7.4 Collection and exposure capabilities of the connected IoT devices . 4 7.5 Access to the capabilities of the connected IoT devices 4 7.6 Security and privacy
23、protection 4 8 Common requirements of IoT DCE . 4 8.1 Communication with the IoT devices . 4 8.2 Publication of the IoT device capabilities 4 8.3 Subscription to the exposed IoT device capabilities 5 8.4 Access to the exposed IoT device capabilities . 5 8.5 Security protection and privacy preservati
24、on . 5 9 Reference architecture of IoT DCE 5 9.1 Profile management functional component (PM-FC) 6 9.2 Auth agent management functional component (AAM-FC) 8 9.3 Application management functional component (AM-FC) . 8 9.4 Device proxy management functional component (DPM-FC) 8 9.5 Device proxy 9 9.6
25、Auth agent 9 9.7 Interface DCE-1 9 9.8 DCE device and external entities . 10 10 Common reference procedures of IoT DCE . 10 10.1 Registration of the IoT devices . 10 10.2 Publication of the exposed IoT device capabilities 10 10.3 Subscription to the exposed IoT device capabilities 11 10.4 Access to
26、the exposed IoT device capabilities . 13 11 Security considerations . 13 iv Rec. ITU-T Y.4115 (04/2017) Page Appendix I Use cases of IoT DCE 14 I.1 Leveraging personal data integration for wearable devices . 14 I.2 Leveraging centralized controlling for home devices 15 Appendix II Implementation exa
27、mple of IoT DCE 17 Bibliography. 18 Rec. ITU-T Y.4115 (04/2017) 1 Recommendation ITU-T Y.4115 Reference architecture for IoT device capability exposure 1 Scope This Recommendation specifies the reference architecture for IoT device capability exposure. The scope of this Recommendation includes: the
28、concept, general characteristics and requirements of IoT device capability exposure, the reference architecture for IoT device capability exposure including common procedures. 2 References The following ITU-T Recommendations and other references contain provisions which, through reference in this te
29、xt, constitute provisions of this Recommendation. 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
30、of the Recommendations and other references 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.2091 Recommendation ITU-T
31、Y.2091 (2011), Terms and definitions for next generation networks. ITU-T Y.4000 Recommendation ITU-T Y.4000/Y.2060 (2012), Overview of the Internet of things. 3 Definitions 3.1 Terms defined elsewhere This Recommendation uses the following terms defined elsewhere: 3.1.1 application ITU-T Y.2091: A s
32、tructured set of capabilities, which provide value-added functionality supported by one or more services, which may be supported by an API interface. 3.1.2 capability b-ITU-R M.1224-1: The ability of an item to meet a service demand of given quantitative characteristics under given internal conditio
33、ns. 3.1.3 device ITU-T Y.4000: 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, date capture, data storage and data processing. 3.1.4 internet of things (IoT) ITU-T Y.4000: A glob
34、al infrastructure for the information society, enabling advanced services by interconnecting (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 communic
35、ation capabilities, the IoT makes full use of things to offer services to all kinds 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. 2 Rec. ITU-
36、T Y.4115 (04/2017) 3.2 Terms defined in this Recommendation This Recommendation defines the following terms: 3.2.1 device capability exposure (DCE): A functional entity to manage the connected Internet of things (IoT) devices in an IoT area network, to expose the capabilities of the connected IoT de
37、vices to IoT applications and to support the IoT applications to access the exposed device capabilities. NOTE Through device capability exposure, IoT applications can dynamically discover the connected IoT devices. 3.2.2 DCE device: A device (e.g., smart phone, tablet, home gateway) that hosts the d
38、evice capability exposure (DCE) and connects to external IoT devices, and provides underlying hardware/software support for implementing the functionalities of DCE. 4 Abbreviations and acronyms This Recommendation uses the following abbreviations and acronyms: AAM-FC Auth Agent Management Functional
39、 Component of the IoT DCE AM-FC Application Management Functional Component of the IoT DCE API Application Programming Interface DCE Device Capability Exposure DPM-FC Device Proxy Management Functional Component of the IoT DCE FC Functional Component IoT Internet of Things NFC Near Field Communicati
40、on OS Operating System PC Personal Computer PM-FC Profile Management Functional Component of the IoT DCE UPnP Universal Plug and Play USB Universal Serial Bus Wi-Fi Wireless Fidelity 5 Conventions The following conventions are used in this Recommendation: The keywords “is required to“ indicate a req
41、uirement which must be strictly followed and from which no deviation is permitted, if conformance to this Recommendation is to be claimed. The keywords “is recommended“ indicate a requirement which is recommended but which is not absolutely required. Thus, this requirement need not be present to cla
42、im conformance. 6 Introduction IoT devices for individual consumers, especially wearable devices (e.g., watches, glasses, headbands and belts), are accepted in the market and are becoming more and more popular. Usually, consumers use their device capability exposure (DCE) devices (e.g., smart phones
43、, tablets and home gateways) to manage IoT devices. There are two kinds of solutions for using DCE devices to manage IoT devices, vertical solutions and horizontal solutions. Rec. ITU-T Y.4115 (04/2017) 3 In vertical solutions, a device manufacturer is usually also an application vendor. When a devi
44、ce manufacturer launches a new IoT device (e.g., a smart watch) onto the market, it has to provide its own applications (for each of the target operating system (OS) platforms) that will allow consumers to access and manage devices through their DCE devices. In addition, in vertical solutions there
45、are many obstacles to one IoT application integrating the capabilities of different types of IoT devices at the same time. In horizontal solutions, IoT devices and relevant applications are separated. Device manufacturers launch IoT devices and provide relevant software proxies supporting open unifo
46、rm interfaces for the DCE devices. Based on the open standard interfaces, other application vendors can develop applications to access those of the IoT devices via the proxies. Therefore, horizontal solutions can overcome the disadvantages of the vertical solutions mentioned above. The IoT device ca
47、pability exposure (IoT DCE), a common integration middleware in DCE devices, uses one type of horizontal solution. The IoT DCE dynamically discovers, connects and accesses the IoT devices in an IoT area network, and exposes capabilities of the connected external IoT devices to upper IoT applications
48、 with standardized uniform interfaces. Using the uniform interfaces provided by the IoT DCE, the upper IoT applications in a DCE device can dynamically discover, subscribe and access the exposed capabilities of the IoT devices as published on the IoT DCE. Figure 6-1 Overview for IoT DCE The IoT DCE
49、in a DCE device (e.g., a smart phone) as shown in Figure 6-1, integrates the underlying device proxies through interfaces (e.g., I1 to Iy) provided by the manufacturers to interact with relevant IoT devices (e.g., the hairpin, belt, watches, glasses and shoes) respectively and provides uniform interfaces to upper IoT applications, with which the upper IoT applications can access the device capabilities of those IoT devices. 7 General characteristics of IoT DCE This clause describes the gene
