MQTT 3.1.1

Presentation about MQTT as an OASIS TC member - KuppingerCole EIC conference in Munich, Germany on 14 May 2014 .

Transcript

1. Alex Kritikos Senior Director R&D Universal Messaging Software AG Member of OASIS MQTT TC, MQTT Security TC, AMQP MS, AMQP TC, AMQP Bindings & Mappings TC Email: Alex.Kritikos@softwareag.com Twitter: @krital www.oasis-open.org
2. History Overview What about wireless? Why not HTTP? Standardization status Conclusion www.oasis-open.org
3. MQTT was initially developed by IBM and Eurotech as a proprietary protocol which was open sourced in Nov 2012 Software AG implemented support for the protocol in Universal Messaging in January 2013 IBM, Eurotech and Software AG began the standardization process by creating the OASIS MQTT TC in March 2013 They were soon joined by ClearBlade, Sierra Wireless, HiveMQ, WS02, Xively, 2lemetry, RedHat and others. www.oasis-open.org 3
4. MQTT is an open, simple, lightweight publish- subscribe binary messaging protocol The protocol is designed to be easy to implement (15 protocol commands) and has a fixed 2 byte over-the-wire overhead header MQTT offers 3 quality of service levels: MQTT QOS 0: At most once (Fire and forget) MQTT QOS 1: At least once (ACKed delivery) MQTT QOS 2: Exactly once (ACKed /No duplicates) www.oasis-open.org
5. MQTT allows a maximum message of 256MB The protocol runs on top of TCP/TLS stacks Various (non standard) efforts for WS/WSS support in progress: http://ow.ly/wHi7R Information on software/hardware that uses MQTT: http://ow.ly/wHm2e The Eclipse Paho project offers some great MQTT clients in minimal C, regular C, C++, Java, Javascript, Python, Lua, Go and Objective-C: http://ow.ly/wHl8c www.oasis-open.org
6. Meet MQTT-SN : MQTT for Sensor Networks The (non standard) protocol is designed to offer what MQTT offers, without relying on network services with ordered/lossless connection characteristics: http://ow.ly/wHiUi MQTT-SN aims to be as close as possible to MQTT but adapted for very constrained, unpredictable wireless communication environments. These environments typically have low bandwidth, high latency, high link failure frequencies / are subject to radio interference. Devices are low cost, battery-powered / have limited processing and storage capabilities. www.oasis-open.org
7. Tests indicate that HTTP has > 5 times over- the-wire footprint Asynchronous HTTP typically requires polling to discover data availability = network cost increase & battery life reduction With MQTT, data is transmitted to the device: In real time if the device is connected As soon as the device connects Power profiling of MQTT on Android shows 0.78% battery / hour over 3G and 0.01% over WiFi to maintain a connection: For more information see: http://ow.ly/wHsWg www.oasis-open.org
8. The OASIS standardization process is scheduled to reach CS by June 2014 The first public interoperability test was hosted by Eclipse IoT working group in March 2014 during EclipseCon San Francisco 15 commercial and OSS products participated. The results can be found on http://ow.ly/wHeIf Other complementary(?) standards: AMQP (ISO 19464), CoAP Other related standards: NFC, ZigBee, RFID, 6LowPAN, Sub-Gig, BTLE, GSM 2G/3G/LTE, OMA-DM, TR-069, LWM2M www.oasis-open.org
9. MQTT offers a standardized mechanism for for MPU level data exchange The protocol’s broker based architecture is very well suited to WAN/LAN/PAN devices with eventual connectivity MQTT relies on ordered / lossless connection based network services These are inapplicable in MCU level wireless communication environments such as sensor networks We are left with an Internet of Gateways (IoG) that relies on hardware / software innovation to make the Internet of Things (IoT) a reality www.oasis-open.org