PROTOCOLS

11.5.1
MQTT 11.5
IOT
Definition:
messaging MÌTT

sands
protocol
for
Message
for
use
in
Queuing
cases

where
Telemetry
clients
Transport.
need
a
small II
is
code a
lightweight
footprint
Machine-To-Machine(M2M) 11.29

and are connected to unreliable neworks or nehworks with limited bundwdih

resources.

. MØTT is primarily used for machine-to-machine (M2M) communication or

Internet of Things types of connections.

Client

Publish Mesage PublishMessage

Suscriber

Publish Message MQTT

Client BROKER
Publi
M shessage

Publish Message Suscriber

Client

Fig 11.19 MQTT architecture

defining the clients and
* MQTT implements the publish/subscribe model by
brokers as below:

(i) MQTT client

microcontroller that runs on
An MØTT client is any device froma server to a
publisher, and
an MQTT library. If the client is sending messages, it acts as a
if it is receiving messages, it acts as a receiver.
can be
Basically, any device that communicates using MQTT over a network
called an MØTT client device.

(i) MQTT broker

The MQTT broker is the backend system which coordinates messages

between the different clients. Responsibilities of the broker include receiving
and filtering messages, identifying clients subscribed to each message, and
Sending them the messages. It is also responsible for other tasks such as:
|11.30|
Embedded Systems and loT Desivn
Authorizing and authenticating MQTT clients.
Passing messages to other systems for further analysis.
Handling missed messages and client sessions.
(ii) MQTT connection

Clients and brokers begin communicating by using an

MQTT
Clients initiate the connection by sending a CONNECT message toconnection
the MOTT
broker. The broker confirms that a conncction has been
established hy
responding with aCONNACK message. Clients never connect with each
other, they connects only with the broker.
Ø Advantages
The advantages of MQTT are,
(i) Lightweight and efficient
MQTT implementation on the loT device requires minimal resources, so that it
can even be used on small microcontrollers. MQTT message headers are also
small so that network bandwidth can be optimized.
(i) Scalable
MQTT implementation requires a minimal amount of code that consumes very
little power in operations.
(iii) Secure
MQTT makes it easy for developers to encrypt messages and authenticate
devices and users using modern authentication protocols.
(iv) Well-supported
Several languages like Python have extensive support for MQTT protocol
implementation. Hence, developers can quickly implement it with a minimal
coding on any type of application.

11.5.2 XMPP

o XMPP is a short form for Extensible Messaging Presence Protocol. I's

protocol for streaming XML elements over a network in order to exchange
Machine-To-Machine (M2M) 11.31

messages and presence information in close to real time. This protocol is

mostly used by instant messaging applications like WhatsApp.
s Requirements: Functions
The following are the basic requirements of any Instant Messenger which are
fulfilled by XMPP:
(i) Send and receive messages with other users.
(ii) Check and share presence status.
(i) Manage subscriptions to and from other users.
(iv) Manage contact list
(v) Block communications (receive message, sharing presence statusS, etc) to
specific users.
Decentralized:
communicate
XMPP is based on client-server architecture, i.e. clients don't
decentralized
directly, they do it with the help of server as intermediary. It is
can run
means there is no centralized XMPP server just like an email, anyone
their own XMPP server.

Addresses in XMPP
couple of
Addresses in XMPP are similar to standard e-mail addresses with a
optional
notable differences. JIDs include an optional node, a domain, and an
resource in the form:
[node " @"]domain |" / " resource]
Direct Client - Client Communication

Client Client
stanza
stanza

Client Plug-ins Client

XMPP Server XMPP Server

Client Client
XMPP Component
11.32 Embedded Systems and loT
In XMPP architecture, a client communicates with another client
Design
in same domain. The servers can also communicate for the purpose
when both are
of
between domains. routing
Each client implements the client fom of the protocol, where the server provides
routing capability. Gateways can exist for purposes of translating
foreign messaging domains and protocols. between
11.5.3 MODBUS

Modbus or MODBUS is aclient/server data communications protocol in the

application layer of the OSl model. It was originally published by Modicon in
1979 for use with its Programmable Logic Controllers (PLCS).
Modbus is a request-response protocol implemented using a master-slave
relationship. In the communication always occurs in pairs, one device must
initiate a request and then wait fora response. The initiating device (he master)
isresponsible for initiating every interaction.
Modbus client Modbus client

Computer HMI

Read /Write Read /Write

Response request Response request
Ethernet Modbus TPC

Response Read /Write

request

PLC PLC

Modbus server Modbus server

Fig I1.21 Modbus protocol

The PDU consists of aone-byte function code followed by up to 252 bytes o1
function-specific data. The function code is the first item to be validated. If the
Machine-To-Machine (M2M) 11.33
function code is not recognized by the device receiving the request, it responds
with an exception.
Function
Code Function - Specific Data
1 253 max

Fig l1.22 Modbus PDU

The packet size is limited to 253 bytes, the most common function codes can
transfer between 240 and 250 bytes of actual data from the slave data model,
depending on the code.
Modbus uses the Transmission Control Protocol (TCP), which provides
connection-oriented communication, error detection, and flow control.
Advantages
The advantages of Modbus are,
(i) Simple but efficient technical architecture.
(iüi) Very easy integration with installations.
(iii) High reliability.

11.5.4 CANBUS with BACNet

The Controller Area Network (CAN bus) is a message-based protocol designed

to allow the Electronic Control Units (ECUs) found in today's automobiles, as
well as other devices, to communicate with each other in a reliable, priority
driven fashion.

BAChet is a network protocol used in Building Automation Systems (BAS) to

control the data exchange between diferent devices and components. BAChet
stands for Building Automation and Control Network.
Ihe CAN to BACNet gateway(PG-103-194) give a solution as a powerful and
outstanding processor that is completely flexible and productive as a building &
industrial automation gateway, allowing integrators to easily connect devices to
networks in a commercial buildings and industrial facilities.
1134 ) Embedded Systems and loT Design

A
CAN Network BACNet Network

W
A
Y
Node Node Node Node

Fig I1.23 CANbus with BacNet

The gateway reads the data from the CAN channel and converts it to BAChet [P
format. The messages can be filtered by their CAN message IDs, and the
incoming bytesof data can be received.
The BACnet IP can be set up as a client, and data from the CAN interface can be
written to the BACnet server.

BACnet client devices can read data from the gateway which we received from
CAN end if it's configured as a BACnet IP server.

Features:

() Up to 1000 points can be interconnected.

(ii) Integrated Serial Port (one wire)
(iüi) Faster datatransmission while decreasing the network
traffic.