Introducing MQTT- Connectivity protocol for M2M & IoT

604
MQTT

Last Updated on

Introduction :

MQTT is designed as a machine-to-machine (M2M) & IoT connectivity protocol.

MQTT stands for Message Queuing telemetry Transport .

This protocol is thus light-weight that it are often supported by some of the littlest measure and monitoring devices, and it can transmit information over way reaching, sometimes intermittent networks.

It is a publish/subscribe messaging transport protocol that’s optimized to connect physical world devices and events with enterprise servers and different customers.
This protocol is designed to overcome the challenges of connecting the rapidly increasing physical world of sensors, actuators, phones, and tablets with established code process technologies.

These principles additionally prove to make this protocol ideal for the rising M2M or IoT world of connected devices where information measure and battery power are at a premium.
• Fast transaction rates
• Consistent lower latency
• Extensive scaling within the range of co-occurring devices that may be connected
• Suitable for deployment in a demilitarized zone (DMZ)

The IBM Redbooks publication Building Realtime Mobile Solutions with MQ Telemetry Transport protocol  and IBM Message Sight covers the theory and real world scenarios for using this light weighted protocol along with IBM Message Sight for mobile and other Internet Of Things applications.

Key features:

  • light-weight message queueing and transport protocol
  • Asynchronous communication model with messages (events)
  •  Low overhead (2 bytes header) for low network bandwidth applications
  • Publish / Subscribe (PubSub) model
  •  Decoupling {of data|of knowledge|of information} producer (publisher) and data client (subscriber) through topics (message queues)
  •  simple protocol, aimed at low quality, low power and low footprint implementations (e.g. WSN – Wireless sensor Networks)
  •  Runs on connection-oriented transport (TCP). To be used in conjunction with 6LoWPAN (TCP header compression)
  •  MQTT caters for (wireless) network disruptions

A little bit of history :

  • It was at first developed by IBM and Eurotech.
  • The previous protocol version 3.1 was made available under mqtt.org
  • In 2014, This protocol was adopted and published as an official standard by OASIS (published V3.1.1). As such, OASIS has become the new home for the development of MQTT.

Applications :

  1. MQTT used by Facebook Messenger

This one has come slightly out of the blue.  We’ve always known around here that MQTT is ideal for mobile messaging; the small-footprint, low bandwidth nature of the protocol helps to minimise both battery use and network traffic. Just what you want to stay connected.

This protocol is specifically designed for applications like sending telemetry data to and from space              probes, so it is designed to use bandwidth and batteries sparingly.

By maintaining an MQTT connection and routing messages through our chat pipeline, we were able to often achieve phone-to-phone delivery in the hundreds of milliseconds, rather than multiple seconds.

You can read full post Building Facebook messenger

 

       2. MQTT based android application.

This application is used to initiate/receive alerts on certain scenarios.

The alerts are received in the mobile application using MQTT clients, which then influences the received MQTT message and presents it to the user in desired formats.

The same  message is delivered to other hardware devices which has subscribed to the same topic i.e. the same  message can be received in the mobile application as well as in the hardware device.

Either of them can influence the received data and present them to the client in a desired format .
       3. Home Automation – using this protocol we can control home lighting
MQTT has many more application , you can get more about this protocol  at mqtt.org

 

Reference : http://mqtt.org, rapidvalue .

LEAVE A REPLY

Please enter your comment!
Please enter your name here