MQTT Protocol Binding (one M2M TS- 0010-v1.0.1)

1 Scope
The present document specifies the binding of Mca and Mcc primitives (message flows) onto the MQTT protocol. It specifies
1) How a CSE or AE connects to MQTT.
2) How an Originator (CSE or AE) formulates a Request as an MQTT message, and transmits it to its intended Receiver.
3) How a Receiver listens for incoming Requests.
4) How that Receiver can formulate and transmit a Response.
2 References
2.1 Normative references
References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies.
The following referenced documents are necessary for the application of the present document.
[1] OASIS MQTT Version 3.1.1 (29 October 2014). OASIS Standard. Edited by Andrew Banks and Rahul Gupta.
NOTE: Available at http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/os/mqtt-v3.1.1-os.html.
[2] oneM2M TS-0001: “Functional Architecture”.
[3] oneM2M TS-0004: “Service Layer Core Protocol Specification”.
[4] IETF RFC 793 (September 1981): “Transmission Control Protocol – DARPA Ineternet Program – Protocol Specification”, J. Postel.
NOTE: Available at http://www.ietf.org/rfc/rfc793.txt.
[5] IETF RFC 5246 (August 2008): “The Transport Layer Security (TLS) Protocol Version 1.2”,
T. Dierks.
NOTE: Available at http://tools.ietf.org/html/rfc5246.
[6] IETF RFC 6455 (December 2011): “The WebSocket Protocol”, I. Fette.
NOTE: Available at http://tools.ietf.org/html/rfc6455.
[7] oneM2M TS-0003: ” Security Solutions “.
2.2 Informative references
References are either specific (identified by date of publication and/or edition number or version number) or on-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies.
The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area.
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply:
originator [2]: actor that initiates a Request
NOTE: An Originator can either be an Application or a CSE.
receiver [2]: actor that receives the Request
NOTE: A Receiver can be a CSE or an Application.
resource [2]: uniquely addressable entity in oneM2M System such as by the use of a Universal Resource Identifier (URI)
NOTE: A resource can be accessed and manipulated by using the specified procedures.