ITU-T Q 3052-2016 Overview of application programming interfaces and protocols for the machine-to-machine service layer (Study Group 11)《机器到机器服务层的应用程序编程接口和协议概述(研究组11)》.pdf

《ITU-T Q 3052-2016 Overview of application programming interfaces and protocols for the machine-to-machine service layer (Study Group 11)《机器到机器服务层的应用程序编程接口和协议概述(研究组11)》.pdf》由会员分享，可在线阅读，更多相关《ITU-T Q 3052-2016 Overview of application programming interfaces and protocols for the machine-to-machine service layer (Study Group 11)《机器到机器服务层的应用程序编程接口和协议概述(研究组11)》.pdf（24页珍藏版）》请在麦多课文档分享上搜索。

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.4411/Q.3052 TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (02/2016) SERIES Y: GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS AND NEXT-GENERATION NETWORKS, INTERNET OF THINGS AND SMART CITIES Internet of th

2、ings and smart cities and communities Frameworks, architectures and protocols SERIES Q: SWITCHING AND SIGNALLING Signalling requirements and protocols for the NGN Network signalling and control functional architecture Overview of application programming interfaces and protocols for the machine-to-ma

3、chine service layer Recommendation ITU-T Y.4411/Q.3052 ITU-T Y-SERIES RECOMMENDATIONS GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS AND NEXT-GENERATION NETWORKS, INTERNET OF THINGS AND SMART CITIES GLOBAL INFORMATION INFRASTRUCTURE General Y.100Y.199 Services, applications and middlew

4、are 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 INTERNET PROTOCOL ASPECTS General Y.1000Y.1099 Services and applications Y.1100Y.

5、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, administration and maintenance Y.1700Y.1799 Charging Y.1800Y.1899 IPTV over

6、 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.2249 Service aspects: Interoperability of services and networks in NGN Y.2250Y.

7、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 Carrier grade open environment Y.2900Y.2999 FUTURE NETWORKS Y.3000Y.3499 CLOUD COM

8、PUTING 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.4250Y.4399 Frameworks, architectures and protocols Y.4400Y.4549 Services, applic

9、ations, 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 to the list of ITU-T Recommendations. Rec. ITU-T Y.4411/Q.3052 (02/2016) i Recommendation ITU-T Y.4411/Q.3052 Overview of a

10、pplication programming interfaces and protocols for the machine-to-machine service layer Summary Recommendation ITU-T Y.4411/Q.3052 describes an overview of application programming interfaces (APIs) and protocols for the machine-to-machine (M2M) service layer and the related API and protocol require

11、ments. It describes the component-based M2M reference model, including the reference points of the M2M service layer. APIs and protocols for M2M are introduced, including existing APIs and protocols for M2M service layer and M2M protocol structure and stacks. Finally, general requirements of APIs an

12、d protocols with respect to the M2M service layer are described. History Edition Recommendation Approval Study Group Unique ID* 1.0 ITU-T Y.4411/Q.3052 2016-02-13 11 11.1002/1000/12698 Keywords API, application programming interface, M2M, machine-to-machine, protocol. * To access the Recommendation,

13、 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.4411/Q.3052 (02/2016) FOREWORD The International Telecommunication Union (ITU) is the United Nations speci

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

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

16、commendations 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

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

18、mmendation 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 words does not suggest that compliance with the Recommendation is required of any p

19、arty. 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 concerning the evidence, validity or applicability of claimed Intellectual Property

20、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 patents, which may be required to implement this Recommendation. However, impleme

21、nters 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. No part of this publication may be reproduced, by any means whatsoever, without the prior written

22、permission of ITU. Rec. ITU-T Y.4411/Q.3052 (02/2016) 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 3 6 General introduction . 3 7 Component-based M2M ref

23、erence model and its relationship with M2M service layer 3 7.1 Component based M2M reference model 3 7.2 M2M platforms . 4 7.3 Types of M2M platforms 4 7.4 Reference points of the M2M service layer in the component-based M2M reference model 5 8 APIs and protocols for M2M 7 8.1 API overview 7 8.2 Des

24、ign approach for M2M service layer APIs . 8 8.3 Existing APIs and protocols for M2M service layer 8 8.4 M2M protocol structure and stacks 9 9 General requirements of APIs and protocols with respect to the M2M service layer 12 9.1 Extensibility 12 9.2 Scalability . 12 9.3 Fault tolerance and robustne

25、ss 12 9.4 Efficiency . 12 9.5 Interoperability . 12 9.6 Self-operation and self-management 13 Appendix I Examples of attributes for APIs and protocols 14 Appendix II Reference of other existing APIs and protocols for M2M service layer 15 Bibliography. 16 Rec. ITU-T Y.4411/Q.3052 (02/2016) 1 Recommen

26、dation ITU-T Y.4411/Q.3052 Overview of application programming interfaces and protocols for the machine-to-machine service layer 1 Scope This Recommendation provides an overview of APIs and protocols for the M2M service layer and the related API and protocol requirements. First, it describes the com

27、ponent-based M2M reference model, including the reference points of the M2M service layer. Then, APIs and protocols for M2M are introduced, including existing APIs and protocols for M2M service layer and M2M protocol structure and stacks. Finally, API and protocol general requirements with respect t

28、o the M2M service layer are described. 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 Recommendations and

29、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 published. The

30、 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 the Internet of things. IETF RFC 2045 IETF RFC 2045 (1996), Multipurpose Internet Mail Extensions (MIME

31、) Part One: Format of Internet Message Bodies. IETF RFC 2616 IETF RFC 2616 (1999), Hypertext Transfer Protocol HTTP/1.1. IETF RFC 6455 IETF RFC 6455 (2011), The WebSocket Protocol. IETF RFC 6749 IETF RFC 6749 (2010), The OAuth 2.0 Authorization Framework. IETF RFC 6886 IETF RFC 6886 (2013), NAT Port

32、 Mapping Protocol (NAT-PMP). IEEE 11073-20601 Health informatics Personal health device communication Part 20601 (2010), Application profile Optimized exchange protocol. DPWS OASIS standard (2009), Devices Profile for Web Services (DPWS). SOAP W3C Recommendation SOAP V.1.2 (2007), Simple Object Acce

33、ss Protocol. XML 1.1 W3C Recommendation XML 1.1 (2006), Extensible Markup Language (XML) 1.1 (Second Edition). 3 Definitions 3.1 Terms defined elsewhere None. 2 Rec. ITU-T Y.4411/Q.3052 (02/2016) 3.2 Terms defined in this Recommendation This Recommendation defines the following term: 3.2.1 applicati

34、on programming interface (API): A particular set of rules and specifications that a software program can follow to access and make use of the services and resources provided by another software program or set of resources. 4 Abbreviations and acronyms This Recommendation uses the following abbreviat

35、ions and acronyms: API Application Programming Interface CSP Community Service Provider CoAP Constrained Application Protocol DA Device Application DPWS Devices Profile for Web Services GA Gateway Application HTML Hyper Text Markup Language HTTP Hypertext Transfer Protocol HVAC Heating, Ventilation,

36、 and Air Conditioning IGD Internet Gateway Device IoT Internet of Things LAN Local Area Network M2M Machine-to-Machine M2M SL Machine-to-Machine Service Layer MIME Multipurpose Internet Mail Extensions MTU Master Terminal Unit NA Network Application NAT Network Address Translation NAT-PMP NAT Port M

37、apping Protocol PKI Public Key Infrastructure RDF Resource Description Framework REST Representational State Transfer RFID Radio Frequency Identification ROA Resource-Oriented Architecture RTU Remote Terminal Unit SAO Service-Oriented Architecture SCADA Supervisory Control and Data Acquisition SLA S

38、ervice Level Agreement SOAP Simple Object Access Protocol TCP Transmission Control Protocol Rec. ITU-T Y.4411/Q.3052 (02/2016) 3 UDP User Datagram Protocol UPnP Universal Plug and Play URI Uniform Resource Identifier WAN Wide Area Network WSDL Web Services Description Language XML Extensible Markup

39、Language 6LoWPAN IPv6 over Low power Wireless Personal Area Networks 5 Conventions None. 6 General introduction This decade is widely predicted to see the rise of machine-to-machine (M2M) communications over various networks. The M2M opportunity is diverse, dynamic and is rapidly expanding. It provi

40、des connectivity for a huge variety of different devices and machines including utility meters, vehicles, sensors point of sale terminals, security devices, healthcare devices and many more. Every day, objects are becoming machines that can be addressed, recognized, localized and controlled via comm

41、unication networks and platforms. An application programming interface (API) is a set of rules (code) and specifications that software programs can follow to communicate with each other. It serves as an interface between different software programs and facilitates their interaction, similar to the w

42、ay a user interface facilitates interaction between humans and computers. In the M2M world, APIs provide the level of abstraction necessary to implement interactions uniformly. The data exchanged are inherently related to the protocol stack used in the communication. A protocol is the special set of

43、 rules that end points in a communication network use when they communicate with each other. It is expected that M2M applications utilize standardized protocols in order to be widely deployable. Depending on the needs of the M2M application, different protocols may be utilized. 7 Component-based M2M

44、 reference model and its relationship with M2M service layer 7.1 Component based M2M reference model The component-based M2M reference model is shown in Figure 1. It can be decomposed in five main components and one super-component: device: The component that hosts the device applications. It can co

45、nnect directly, or via the gateway, to the network. It may host M2M service layer (M2M SL) capabilities. When it does not contain the M2M SL capabilities, it is considered as a legacy device. gateway: A component that may host M2M SL capabilities and gateway applications (GA) and acts as an intermed

46、iary between the network and a legacy device. network: A component, which does not host M2M SL capabilities, and that connects device, gateway and network application server with each other. M2M platform: A component that hosts the M2M SL capabilities, and that can be used by one or more application

47、 servers. The M2M platform is part of the network application server. NOTE 1 Clauses 7.2 and 7.3 provide some details about M2M platforms, as they play a relevant role from a protocol/API point of view. 4 Rec. ITU-T Y.4411/Q.3052 (02/2016) application server: A component that hosts the network appli

48、cations. The application server is also part of the network application server. network application server: A super-component including both the application server and the M2M platform. Figure 1 Component based M2M reference model The different elements of the component-based M2M reference model can

49、 communicate among themselves using capabilities of multiple layers. NOTE 2 ITU-T Y.4000 defines the Internet of things (IoT) reference model as having four layers (application layer, service support and application support layer, network layer, and device layer). 7.2 M2M platforms Traditionally, M2M solutions have been conceived and deployed as stovepipe (or standalone) solutions with the aim of improving (or enabling) a specific proc