What are the IoT protocols that are at the base of the Internet of things? Before answering this question, it is useful to have an overview about IoT.
IoT is gaining appeal, and the most important players are investing in IoT. IoT promises to be a technological revolution that will touch every area: industrial, transportation, energy, everyday life, and so on. As we have seen in previous posts, there are several IoT definitions highlighting different aspects, and there are many solutions to implement IoT projects.
IoT promises to connect all the devices together, like wearables, home devices, and smart objects, and enable them to exchange information. All this information is gathered and analyzed to improve our life.
But how these devices send and receive data? We all know HTTP protocol that makes possible to browse the net, opens web pages and so on. Is this protocol still useful for IoT?
Well, the answer is yes but there are other IoT protocols that can be more efficient and suitable for low power devices.
Below, you will find a list of the most “important” IoT protocols used in IoT ecosystem:
MQTT stands for Message Queuing Telemetry Trasport . It is a publish/subscribe message lightweight protocol. It is an M2M (Machine-to-Machine)-oriented protocol. Now, it is an open standard maintained by the OASIS group. The reference architecture is very simple, and it is based on client/server. The client is generally a sensor that “publishes” the information to the server (broker), which receives the information and dispatches it to the subscribers. The underlying communication is based on TCP.
Generally speaking, the MQTT protocol uses a many-to-many paradigm, and the broker decouples the publisher to the subscriber and acts as a message router. This protocol implements QoS, secure communication, persistence, and so on. There is another version of this protocol called MQTT-SN (or MQTT-S), which stands for Sensor Network. Eclipse has released an open source implementation of MQTT called Mosquitto.
COAP stands for Constrained Application Protocol. This protocol was designed by IETF, and it is an M2M protocol. This protocol is defined by RFC7252 and is web transfer protocol. This protocol is very similar to HTTP and is based on the document transfer paradigm. It uses the request/response model and supports built-in service discovery. Respective to HTTP protocol, COAP is lightweight with smaller packets.
COAP uses UDP as underlying network protocol. It is basically a client-server protocol where the client makes a request and the server sends back a response as it happens in HTTP. The methods used by COAP are the same used by HTTP.
AMQP stands for Advanced Message Queue Protocol. It is maintained by OASIS, like MQTT. AMQP is an open standard to exchange messages between applications (M2M). In other words, it is a message-oriented protocol that provides features like routing and queuing. The key factors of AMQP are:
- It is open.
- It is interoperable.
- It is secure.
- It is reliable.
We al know REST. It stands for REpresentational State Transfer. It is used to exchange data between applications and to integrate applications belonging to different domains. It uses HTTP as the base protocol. REST uses the client/server paradigm, and it is widely used, not just in the IoT ecosystem. We discussed how to use REST to integrate Arduino with Android.
XMPP (Extensible Messaging and Presence Protocol) is an open standard for presence and messaging. This protocol uses XML messages. XMPP-IoT is designed specifically for the IoT environment, and, basically, this protocol enables users to send real-time messages and handles the user presence (Online, Offline, Busy). The IoT version enables users to send and receive messages from machines. Moreover, it is eXtensbile easily. The key factors are:
- Open standard.
Stomp is a text oriented messaging protocol. It is very easy to use. Clients connect to a message broker to exchange messages.
That's it! Now you know a bit of the various protocols that are seeing heavy utilization in the world of IoT.