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.9 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 HTTP protocol binding Recommendation ITU-T Y.4500.9 ITU-T Y-SERIES RECOMMENDATIONS GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS, NEXT-GENERATION NETWORKS, INTERNET OF THINGS AND SMART CITIES GLOBAL INFORMATI
3、ON 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 INTERNET P
4、ROTOCOL 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, admi
5、nistration 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.2249 Ser
6、vice 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 Carrier gra
7、de 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.4250Y.439
8、9 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 list o
9、f ITU-T Recommendations. Rec. ITU-T Y.4500.9 (03/2018) i Recommendation ITU-T Y.4500.9 oneM2M HTTP protocol binding Summary Recommendation ITU-T Y.4500.9 specifies the protocol specific part of the communication protocol used by oneM2M compliant systems as RESTful HTTP binding. The scope of the pres
10、ent Recommendation is (not limited to as shown below): Binding oneM2M Protocol primitive types to HTTP method. Binding oneM2M response status codes (successful/unsuccessful) to HTTP response codes. Binding oneM2M RESTful resources to HTTP resources. History Edition Recommendation Approval Study Grou
11、p Unique ID* 1.0 ITU-T Y.4500.9 2018-03-01 20 11.1002/1000/13504 Keywords oneM2M, HTTP. * 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
12、Rec. ITU-T Y.4500.9 (03/2018) 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.
13、 ITU-T is responsible 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
14、 study by the ITU-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 o
15、n a collaborative 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 cont
16、ain certain mandatory 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
17、 requirements. The 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
18、 Right. ITU takes 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 int
19、ellectual property, 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/. NOTE This Reco
20、mmendation departs slightly from 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.
21、ITU-T Y.4500.9 (03/2018) 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 Abbreviations and acronyms 2 5 Conventions 2 6 Overview on HTTP binding . 3 6.0 Overview 3 6.1 Introduction 3 6.2 Request-Line
22、 . 4 6.3 Status-Line 4 7 HTTP message mapping . 5 7.1 Introduction 5 7.2 Parameter mappings on Request-Line 5 7.3 Status-Line 10 7.4 Header fields . 11 7.5 Message-body . 15 7.6 Message routing 15 8 Security consideration 15 8.1 Authentication on HTTP Request message 15 8.2 Transport layer security
23、15 Annex A oneM2M specification update and maintenance control procedure 16 Appendix I Example procedures . 17 I.1 resource creation 17 Appendix II WebSocket 18 II.1 Notification using WebSocket 18 Bibliography. 19 Rec. ITU-T Y.4500.9 (03/2018) 1 Recommendation ITU-T Y.4500.9 oneM2M HTTP protocol bi
24、nding 1 Scope This Recommendation specifies the protocol specific part of the communication protocol used by oneM2M compliant systems as RESTful HTTP binding. The scope of this Recommendation is (not limited to as shown below): Binding oneM2M Protocol primitive types to HTTP method. Binding oneM2M r
25、esponse status codes (successful/unsuccessful) to HTTP response codes. Binding oneM2M RESTful resources to HTTP resources. The Recommendation contains oneM2M Release 2 specification oneM2M HTTP Protocol Binding V2.6.1 and is equivalent to standards of oneM2M partners including Association of Radio I
26、ndustries and Businesses (ARIB), Alliance for Telecommunications Industry Solutions (ATIS) b-ATIS.oneM2M.TS009, China Communications Standards Association (CCSA) b-CCSA M2M-TS-0009-V2.6.1, European Telecommunications Standards Institute (ETSI) b-ETSI TS 118 109 V2.6.1, Telecommunications Industry As
27、sociation (TIA), Telecommunications Standards Development Society India (TSDSI) b-TSDSI STD TS-0009, Telecommunications Technology Association (TTA) b-TTA MM-TS.0009 and Telecommunication Technology Committee (TTC) b-TTC TS-M2M-0009. 2 References The following ITU-T Recommendations and other referen
28、ces 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 other references are subject to revision; users of this Recommendation are therefore encouraged to invest
29、igate 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 reference to a document within this Recommendation does not give it, as a stand-alone document, the stat
30、us of a Recommendation. ITU-T Y.4500.1 Recommendation ITU-T Y.4500.1 (2018), Functional architecture. ITU-T Y.4500.4 Recommendation ITU-T Y.4500.4 (2018), Service layer core protocol. ETSI TS 118 103 ETSI TS 118 103 (2016), oneM2M; Security solutions. IETF RFC 3986 IETF RFC 3986 (2005), Uniform Reso
31、urce Identifier (URI): Generic Syntax. IETF RFC 6750 IETF RFC 6750 (2012), The OAuth 2.0 Authorization Framework: Bearer Token Usage. IETF RFC 7230 IETF RFC 7230 (2014), Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing. IETF RFC 7232 IETF RFC 7232 (2014), Hypertext Transfer Protoco
32、l (HTTP/1.1): Conditional Requests. IETF RFC 7235 IETF RFC 7235 (2014), Hypertext Transfer Protocol (HTTP/1.1): Authentication. 2 Rec. ITU-T Y.4500.9 (03/2018) 3 Definitions 3.1 Terms defined elsewhere This Recommendation uses the following terms defined elsewhere: 3.1.1 application entity (AE) b-IT
33、U-T Y.4500.11: Represents an instantiation of application logic for end-to-end M2M solutions. 3.1.2 common services entity (CSE) b-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 r
34、eference points. 3.2 Terms defined in this Recommendation None. 4 Abbreviations and acronyms This Recommendation uses the following abbreviations and acronyms: AE Application Entity CSE Common Services Entity HTTP Hyper Text Transfer Protocol RESTful Representational state transfer TLS Transport Lay
35、er Security URI Uniform Resource Identifier 5 Conventions The key words “Shall“, “Shall not“, “May“, “Need not“, “Should“, “Should not“ in the present document are to be interpreted as described: Shall/Shall not: Requirements 1) effect on this Recommendation: This Recommendation needs to describe th
36、e required feature (i.e., specify a technical solution for the Requirement); 2) effect on products: every implementation (M2M Solution that complies to this Standard) must support it; 3) effect on deployments: every deployment (M2M Service based on this Standard) must use the Standardized feature wh
37、ere applicable otherwise e.g., interoperability problems with other services could arise. Should/Should not: Recommendation 1) effect on this Recommendation: This Recommendation needs to describe a solution that allows the presence and the absence of the feature; 2) effect on products: an implementa
38、tion 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: Rec. ITU-T Y.4500.9 (03/2018) 3 Permission/Option 1) effect on this Recommendation: This Recommendation needs to describe a soluti
39、on 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 Overview on HTTP binding 6.0 Overview HTTP binding specifies the equivalence between oneM2M request
40、 and response primitives and HTTP request and response messages, respectively. This clause provides a brief overview on the mapping relationship between oneM2M and HTTP message parameters. This clause describes how oneM2M request/response primitives can be mapped to HTTP request/response messages an
41、d vice versa. 6.1 Introduction Figure 6.1-1 illustrates an example oneM2M system configuration and its correspondence to an HTTP-based information system if HTTP binding as defined in this Recommendation is applied. The upper diagram in Figure 6.1-1 shows with solid line arrows the flow of a request
42、 primitive originating from an AE which is registered to an MN-CSE (Registrar of AE). The request primitive is assumed to address a resource which is hosted by another MN-CSE (Host of Resource). Both MN-CSEs are registered to the same IN-CSE. When applying HTTP binding, the oneM2M entities of the up
43、per diagram take the roles outlined in the lower diagram of a corresponding HTTP information system as defined in IETF RFC 7230. The AE takes the role of an HTTP client, the MN-CSE (Registrar of AE) takes the role of a HTTP Proxy Server, and both the IN-CSE and MN-CSE (Host of Resource) take the rol
44、e of a HTTP server for this particular request message. CSEs may also issue unsolicited request messages, shown with dashed line arrows in Figure 6.1-1, and receive associated response messages. Therefore, for HTTP protocol binding, CSEs generally provides capability of both HTTP Server and HTTP Cli
45、ent. AEs may provide HTTP Server capability optionally in order to be able to serve Notification request messages (see TS-0004 ITU-T Y.4500.4 and TS-0001 ITU-T Y.4500.1). See Appendix II for information on notification using WebSocket. 4 Rec. ITU-T Y.4500.9 (03/2018) Figure 6.1-1 Correspondence betw
46、een oneM2M entities and HTTP client and server Each individual request primitive will be mapped to single HTTP request message, and each individual response primitive will be mapped to a single HTTP response message, and vice-versa. An HTTP request message consists of Request-Line, headers and messa
47、ge-body. An HTTP response message consists of Status-Line, headers and message-body IETF RFC 7230. HTTP header names are case-insensitive and a receiver shall accept headers that are either lower or upper or any mixture thereof. This clause describes how oneM2M request/response primitives are mapped
48、 to HTTP messages at a high level. Corresponding details are specified in clause 7. See Appendix I for example procedures. 6.2 Request-Line The HTTP method of a request message is mapped to the Operation parameter, and vice-versa. At the message originator side the HTTP Request-Target is derived fro
49、m the To parameter of the request primitive, including a query string which carries other specific primitive parameters. HTTP-Version is specified in clause 7. 6.3 Status-Line HTTP Version is specified in clause 7. The Status-Code of HTTP response messages is derived from the Response Status Code parameter of the response primitive. The Reason-Phrase is not applicable to oneM2M systems and is omitted. Rec. ITU-T Y.4500.9 (03/2018) 5 7 HTTP message mapping
