IoT
StandardMQTT Version 5.0
A Client Server publish/subscribe messaging transport protocol. It is light weight, open, simple, and designed to be easy to implement. These characteristics make it ideal for use in many situations, including constrained environments such as for communication in Machine to Machine (M2M) and Internet of Things (IoT) contexts where a small code footprint is required and/or network bandwidth is at a premium.
The protocol runs over TCP/IP, or over other network protocols that provide ordered, lossless, bi-directional connections. Its features include:
· Use of the publish/subscribe message pattern which provides one-to-many message distribution and decoupling of applications.
· A messaging transport that is agnostic to the content of the payload.
· Three qualities of service for message delivery:
o “At most once”, where messages are delivered according to the best efforts of the operating environment. Message loss can occur. This level could be used, for example, with ambient sensor data where it does not matter if an individual reading is lost as the next one will be published soon after.
o “At least once”, where messages are assured to arrive but duplicates can occur.
o “Exactly once”, where messages are assured to arrive exactly once. This level could be used, for example, with billing systems where duplicate or lost messages could lead to incorrect charges being applied.
· A small transport overhead and protocol exchanges minimized to reduce network traffic.
· A mechanism to notify interested parties when an abnormal disconnection occurs.
MQTT Version 5.0
A Client Server publish/subscribe messaging transport protocol. It is light weight, open, simple, and designed to be easy to implement. These characteristics make it ideal for use in many situations, including constrained environments such as for communication in Machine to Machine (M2M) and Internet of Things (IoT) contexts where a small code footprint is required and/or network bandwidth is at a premium.
The protocol runs over TCP/IP, or over other network protocols that provide ordered, lossless, bi-directional connections. Its features include:
· Use of the publish/subscribe message pattern which provides one-to-many message distribution and decoupling of applications.
· A messaging transport that is agnostic to the content of the payload.
· Three qualities of service for message delivery:
o “At most once”, where messages are delivered according to the best efforts of the operating environment. Message loss can occur. This level could be used, for example, with ambient sensor data where it does not matter if an individual reading is lost as the next one will be published soon after.
o “At least once”, where messages are assured to arrive but duplicates can occur.
o “Exactly once”, where messages are assured to arrive exactly once. This level could be used, for example, with billing systems where duplicate or lost messages could lead to incorrect charges being applied.
· A small transport overhead and protocol exchanges minimized to reduce network traffic.
· A mechanism to notify interested parties when an abnormal disconnection occurs.
Produced by:
OASIS Message Queuing Telemetry Transport (MQTT) TCVoting history:
May 2018
OASIS Standard:
Cite as:
Cite as:
[mqtt-v5.0]
MQTT Version 5.0. Edited by Andrew Banks, Ed Briggs, Ken Borgendale, and Rahul Gupta. 15 May 2018.
OASIS Committee Specification 02. http://docs.oasis-open.org/mqtt/mqtt/v5.0/cs02/mqtt-v5.0-cs02.html.
Latest version: http://docs.oasis-open.org/mqtt/mqtt/v5.0/mqtt-v5.0.html.
StandardClassification of Everyday Living Version 1.0
Defines the Classification of Everyday Living (COEL) version 1.0 specification for the complete implementation of a compliant system. Examples and non-normative material are also offered as guidance.
Classification of Everyday Living Version 1.0
Defines the Classification of Everyday Living (COEL) version 1.0 specification for the complete implementation of a compliant system. Examples and non-normative material are also offered as guidance.
Produced by:
OASIS Classification of Everyday Living (COEL) TCVoting history:
February 2018
OASIS Standard:
Cite as:
Cite as:
[COEL-COEL-v1.0] Classification of Everyday Living Version 1.0.
Edited by Paul Bruton, Joss Langford, Matthew Reed, and David Snelling. 25 February 2018. OASIS Committee Specification 01.
http://docs.oasis-open.org/coel/COEL/v1.0/cs01/COEL-v1.0-cs01.html. Latest version: http://docs.oasis-open.org/coel/COEL/v1.0/COEL-v1.0.html.
StandardMQTT Version 5.0
A Client Server publish/subscribe messaging transport protocol. It is light weight, open, simple, and designed to be easy to implement. These characteristics make it ideal for use in many situations, including constrained environments such as for communication in Machine to Machine (M2M) and Internet of Things (IoT) contexts where a small code footprint is required and/or network bandwidth is at a premium.
The protocol runs over TCP/IP, or over other network protocols that provide ordered, lossless, bi-directional connections. Its features include:
· Use of the publish/subscribe message pattern which provides one-to-many message distribution and decoupling of applications.
· A messaging transport that is agnostic to the content of the payload.
· Three qualities of service for message delivery:
o “At most once”, where messages are delivered according to the best efforts of the operating environment. Message loss can occur. This level could be used, for example, with ambient sensor data where it does not matter if an individual reading is lost as the next one will be published soon after.
o “At least once”, where messages are assured to arrive but duplicates can occur.
o “Exactly once”, where messages are assured to arrive exactly once. This level could be used, for example, with billing systems where duplicate or lost messages could lead to incorrect charges being applied.
· A small transport overhead and protocol exchanges minimized to reduce network traffic.
· A mechanism to notify interested parties when an abnormal disconnection occurs.
MQTT Version 5.0
A Client Server publish/subscribe messaging transport protocol. It is light weight, open, simple, and designed to be easy to implement. These characteristics make it ideal for use in many situations, including constrained environments such as for communication in Machine to Machine (M2M) and Internet of Things (IoT) contexts where a small code footprint is required and/or network bandwidth is at a premium.
The protocol runs over TCP/IP, or over other network protocols that provide ordered, lossless, bi-directional connections. Its features include:
· Use of the publish/subscribe message pattern which provides one-to-many message distribution and decoupling of applications.
· A messaging transport that is agnostic to the content of the payload.
· Three qualities of service for message delivery:
o “At most once”, where messages are delivered according to the best efforts of the operating environment. Message loss can occur. This level could be used, for example, with ambient sensor data where it does not matter if an individual reading is lost as the next one will be published soon after.
o “At least once”, where messages are assured to arrive but duplicates can occur.
o “Exactly once”, where messages are assured to arrive exactly once. This level could be used, for example, with billing systems where duplicate or lost messages could lead to incorrect charges being applied.
· A small transport overhead and protocol exchanges minimized to reduce network traffic.
· A mechanism to notify interested parties when an abnormal disconnection occurs.
Produced by:
OASIS Message Queuing Telemetry Transport (MQTT) TCVoting history:
December 2017
OASIS Standard:
Cite as:
Cite as:
[mqtt-v5.0]
MQTT Version 5.0. Edited by Andrew Banks, Ed Briggs, Ken Borgendale, and Rahul Gupta. 25 December 2017.
OASIS Committee Specification 01. http://docs.oasis-open.org/mqtt/mqtt/v5.0/cs01/mqtt-v5.0-cs01.html.
Latest version: http://docs.oasis-open.org/mqtt/mqtt/v5.0/mqtt-v5.0.html.
StandardVirtual I/O Device (VIRTIO) Version 1.0
Describes the specifications of the “virtio” family of devices. These devices are found in virtual environments, yet by design they look like physical devices to the guest within the virtual machine – and this document treats them as such. This similarity allows the guest to use standard drivers and discovery mechanisms.
The purpose of virtio and this specification is that virtual environments and guests should have a straightforward, efficient, standard and extensible mechanism for virtual devices, rather than boutique per-environment or per-OS mechanisms.
Virtual I/O Device (VIRTIO) Version 1.0
Describes the specifications of the “virtio” family of devices. These devices are found in virtual environments, yet by design they look like physical devices to the guest within the virtual machine – and this document treats them as such. This similarity allows the guest to use standard drivers and discovery mechanisms.
The purpose of virtio and this specification is that virtual environments and guests should have a straightforward, efficient, standard and extensible mechanism for virtual devices, rather than boutique per-environment or per-OS mechanisms.
Produced by:
OASIS Virtual I/O Device (VIRTIO) TCVoting history:
August 2015
OASIS Standard:
Cite as:
Cite as:
[VIRTIO-v1.0]
Virtual I/O Device (VIRTIO) Version 1.0. Edited by Rusty Russell, Michael S. Tsirkin, Cornelia Huck, and Pawel Moll. 03 March 2016. OASIS Committee Specification 04. http://docs.oasis-open.org/virtio/virtio/v1.0/cs03/virtio-v1.0-cs03.html. Latest version: http://docs.oasis-open.org/virtio/virtio/v1.0/virtio-v1.0.html.
StandardBindings for OBIX: REST Bindings Version 1.0
Specifies REST bindings for OBIX. OBIX provides the core information model and interaction pattern for communication with building control systems. Specific implementations of OBIX must choose how to bind OBIX interactions. This document describes the REST Binding, an interaction pattern that can be used in conjunction with XML, EXI, CoAP, and JSON encodings, as well as other encodings that may be specified elsewhere.
Bindings for OBIX: REST Bindings Version 1.0
Specifies REST bindings for OBIX. OBIX provides the core information model and interaction pattern for communication with building control systems. Specific implementations of OBIX must choose how to bind OBIX interactions. This document describes the REST Binding, an interaction pattern that can be used in conjunction with XML, EXI, CoAP, and JSON encodings, as well as other encodings that may be specified elsewhere.
Produced by:
OASIS Open Building Information Exchange (oBIX) TCVoting history:
September 2015
OASIS Standard:
Cite as:
Cite as:
[OBIX-REST-v1.0] Bindings for OBIX: REST Bindings Version 1.0. Edited by Craig Gemmill and Markus Jung. 14 September 2015. OASIS Committee Specification 01. http://docs.oasis-open.org/obix/obix-rest/v1.0/cs01/obix-rest-v1.0-cs01.html. Latest version: http://docs.oasis-open.org/obix/obix-rest/v1.0/obix-rest-v1.0.html.
StandardBindings for OBIX: SOAP Bindings Version 1.0
OBIX provides the core information model and interaction pattern for communication with building control systems. Specific implementations of OBIX must choose how to bind OBIX interactions. Specifies SOAP protocol bindings for OBIX.
Bindings for OBIX: SOAP Bindings Version 1.0
OBIX provides the core information model and interaction pattern for communication with building control systems. Specific implementations of OBIX must choose how to bind OBIX interactions. Specifies SOAP protocol bindings for OBIX.
Produced by:
OASIS Open Building Information Exchange (oBIX) TCVoting history:
September 2015
OASIS Standard:
Cite as:
Cite as:
[OBIX-SOAP-v1.0] Bindings for OBIX: SOAP Bindings Version 1.0. Edited by Markus Jung. 14 September 2015. OASIS Committee Specification 01. http://docs.oasis-open.org/obix/obix-soap/v1.0/cs01/obix-soap-v1.0-cs01.html. Latest version: http://docs.oasis-open.org/obix/obix-soap/v1.0/obix-soap-v1.0.html.
StandardBindings for OBIX: WebSocket Bindings Version 1.0
OBIX provides the core information model and interaction pattern for communication with building control systems. Specific implementations of OBIX must choose how to bind OBIX interactions. This document specifies WebSocket binding for OBIX.
Bindings for OBIX: WebSocket Bindings Version 1.0
OBIX provides the core information model and interaction pattern for communication with building control systems. Specific implementations of OBIX must choose how to bind OBIX interactions. This document specifies WebSocket binding for OBIX.
Produced by:
OASIS Open Building Information Exchange (oBIX) TCVoting history:
September 2015
OASIS Standard:
Cite as:
Cite as:
[OBIX-WebSocket-v1.0] Bindings for OBIX: WebSocket Bindings Version 1.0. Edited by Matthias Hub. 14 September 2015. OASIS Committee Specification 01. http://docs.oasis-open.org/obix/obix-websocket/v1.0/cs01/obix-websocket-v1.0-cs01.html. Latest version: http://docs.oasis-open.org/obix/obix-websocket/v1.0/obix-websocket-v1.0.html.
StandardEncodings for OBIX: Common Encodings Version 1.0
Specifies different encodings for OBIX objects adhering to the OBIX object model. OBIX provides the core information model and interaction pattern for communication with building control systems.
Encodings for OBIX: Common Encodings Version 1.0
Specifies different encodings for OBIX objects adhering to the OBIX object model. OBIX provides the core information model and interaction pattern for communication with building control systems.
Produced by:
OASIS Open Building Information Exchange (oBIX) TCVoting history:
September 2015
OASIS Standard:
Cite as:
Cite as:
[OBIX-Encodings] Encodings for OBIX: Common Encodings Version 1.0.. Edited by Markus Jung. 14 September 2015. OASIS Committee Specification 01. http://docs.oasis-open.org/obix/obix-encodings/v1.0/cs01/obix-encodings-v1.0-cs01.html. Latest version: http://docs.oasis-open.org/obix/obix-encodings/v1.0/obix-encodings-v1.0.html.
StandardOBIX Version 1.1
Specifies an object model used for machine-to-machine (M2M) communication. Companion documents will specify the protocol bindings and encodings for specific cases.
OBIX Version 1.1
Specifies an object model used for machine-to-machine (M2M) communication. Companion documents will specify the protocol bindings and encodings for specific cases.
Produced by:
OASIS Open Building Information Exchange (oBIX) TCVoting history:
September 2015
OASIS Standard:
Cite as:
Cite as:
[OBIX-v1.1] OBIX Version 1.1. Edited by Craig Gemmill. 14 September 2015. OASIS Committee Specification 01. http://docs.oasis-open.org/obix/obix/v1.1/cs01/obix-v1.1-cs01.html. Latest version: http://docs.oasis-open.org/obix/obix/v1.1/obix-v1.1.html.
StandardMQTT v3.1.1
A Client Server publish/subscribe messaging transport protocol. It is light weight, open, simple, and designed so as to be easy to implement. These characteristics make it ideal for use in many situations, including constrained environments such as for communication in Machine to Machine (M2M) and Internet of Things (IoT) contexts where a small code footprint is required and/or network bandwidth is at a premium.
The protocol runs over TCP/IP, or over other network protocols that provide ordered, lossless, bi-directional connections. Its features include:
· Use of the publish/subscribe message pattern which provides one-to-many message distribution and decoupling of applications.
· A messaging transport that is agnostic to the content of the payload.
· Three qualities of service for message delivery:
· “At most once”, where messages are delivered according to the best efforts of the operating environment. Message loss can occur. This level could be used, for example, with ambient sensor data where it does not matter if an individual reading is lost as the next one will be published soon after.
· “At least once”, where messages are assured to arrive but duplicates can occur.
· “Exactly once”, where message are assured to arrive exactly once. This level could be used, for example, with billing systems where duplicate or lost messages could lead to incorrect charges being applied.
· A small transport overhead and protocol exchanges minimized to reduce network traffic.
· A mechanism to notify interested parties when an abnormal disconnection occurs.
MQTT v3.1.1
A Client Server publish/subscribe messaging transport protocol. It is light weight, open, simple, and designed so as to be easy to implement. These characteristics make it ideal for use in many situations, including constrained environments such as for communication in Machine to Machine (M2M) and Internet of Things (IoT) contexts where a small code footprint is required and/or network bandwidth is at a premium.
The protocol runs over TCP/IP, or over other network protocols that provide ordered, lossless, bi-directional connections. Its features include:
· Use of the publish/subscribe message pattern which provides one-to-many message distribution and decoupling of applications.
· A messaging transport that is agnostic to the content of the payload.
· Three qualities of service for message delivery:
· “At most once”, where messages are delivered according to the best efforts of the operating environment. Message loss can occur. This level could be used, for example, with ambient sensor data where it does not matter if an individual reading is lost as the next one will be published soon after.
· “At least once”, where messages are assured to arrive but duplicates can occur.
· “Exactly once”, where message are assured to arrive exactly once. This level could be used, for example, with billing systems where duplicate or lost messages could lead to incorrect charges being applied.
· A small transport overhead and protocol exchanges minimized to reduce network traffic.
· A mechanism to notify interested parties when an abnormal disconnection occurs.
Produced by:
OASIS Message Queuing Telemetry Transport (MQTT) TCVoting history:
Voting History for OASIS Standard, October 2014
Voting History for Approved Errata 01, December 2015
Additional approvals
OASIS Standard:
OASIS Standard:
HTML
Approved Errata 01:
HTML
PDF
DOC
Cite as:
Cite as:
[mqtt-v3.1.1]MQTT Version 3.1.1. Edited by Andrew Banks and Rahul Gupta. 29 October 2014. OASIS Standard. http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/os/mqtt-v3.1.1-os.html. Latest version: http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/mqtt-v3.1.1.html.
[mqtt-v3.1.1-errata01]MQTT Version 3.1.1 Errata 01. Edited by Andrew Banks and Rahul Gupta. 10 December 2015. OASIS Approved Errata. http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/errata01/os/mqtt-v3.1.1-errata01-os.html. Latest version: http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/errata01/mqtt-v3.1.1-errata01.html.
[mqtt-v3.1.1-plus-errata01]MQTT Version 3.1.1 Plus Errata 01. Edited by Andrew Banks and Rahul Gupta. 10 December 2015. OASIS Standard Incorporating Approved Errata 01. http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/errata01/os/mqtt-v3.1.1-errata01-os-complete.html. Latest version: http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/mqtt-v3.1.1.html.
No results with the selected filters