HIGHER NATIONAL SCHOOL OF

RENEWABLE ENERGY, ENVIRONMENT &

SUSTAINABLE DEVELOPMENT

MQTT
PROTOCOLE IN IOT

BOUREK KHALIL

12 - 03 - 2024
 01 02 03 04
What is MQTT HISTORY MQTT Key Features
Architecture of MQTT

05 06 07 08
Use Cases of Comparison SECURITY
CONCLUSION
MQTT in IoT with Other OF MQTT
Protocols
WHAT IS MQTT ?

MQTT (Message Queuing Telemetry

Transport) is indeed a lightweight,
publish-subscribe network protocol that
is designed for transporting messages
between devices

It's particularly well-suited for use in

situations where bandwidth or
resources may be limited, such as in IoT
(Internet of Things) environments. MQTT
operates on top of the TCP/IP protocol
suite and is known for its efficiency,
simplicity, and reliability in delivering
messages between clients.
LIGHTWEIGHT ?

Lightweight: Refers to efficiency in

resource usage, including bandwidth
and processing power. Lightweight
protocols like MQTT minimize network
overhead and computational
requirements, making them ideal for
resource-constrained environments such
as IoT.
PUBLISH-SUBSCRIBE

Publish-Subscribe Messaging Protocol:

Publishers send messages to topics
without knowing who the subscribers
are, and subscribers receive messages
based on their interest in those topics.
This decoupling enables scalable and
flexible communication.
HISTORY
Invented in 1999 , Prompted by the need to design a protocol that
could handle a very limited operating environment that can afford
only minimal battery loss and minimal bandwidth to connect devices
with satellite
MQTT ARCHITECTURE

MQTT COMPONENTS :

MESSAGE
CLIENT
SERVER OR BROKER
TOPIC
 KEY FEATURES OF MQTT :
PUBLISH/SUBSCRIBE MODEL

The diagram explain the communication

01 between a mobile device and a
temperature sensor via an MQTT broker
server

Elements and Interactions:

02 Mobile Device: Acts as the subscriber
interested in temperature data.
MQTT Broker (Server): Facilitates
communication, receiving messages
from the temperature sensor and
delivering them to the mobile
device.
Temperature Sensor: Serves as the
publisher, generating and publishing
temperature data to the broker.
 KEY FEATURES OF MQTT :
PUBLISH/SUBSCRIBE MODEL
MQTT MESSAGE FORMAT
Communication Steps:
1. Connect: Devices establish
connections with the MQTT broker.
2. Subscribe: Mobile device subscribes
to a temperature-related topic.
3. Publish: Temperature sensor
publishes temperature data to the
topic.
4. Publish & Subscribe ACK: Broker
acknowledges both the published
message and the subscription
request.
5. Delivery: Broker identifies the
subscribed device and delivers the
temperature message.
 QOS
MQTT offers different levels of QoS to ensure message delivery reliability. This includes:

QoS 0 (At most once) QoS 1 (At least once) QoS 2 (Exactly once)

Messages are Messages are Messages are

delivered at most guaranteed to be guaranteed to be
once, without any delivered at least delivered exactly
confirmation. once, but may be once, ensuring no
delivered multiple duplication or loss.
times in case of
network issues or
failures.
USE CASES OF MQTT IN IOT

MQTT (Message Queuing Telemetry Transport) is widely used in various IoT (Internet
of Things) applications due to its lightweight nature, efficiency, and support for
Pub/Sub messaging. Here are some common use cases of MQTT in IoT:

1. Remote Monitoring and Control

2. Asset Tracking and Management
3. Industrial Automation and Control
4. Smart Agriculture
5. Energy Management
6. Healthcare Monitoring
7. Smart Cities : Integral to smart city initiatives for optimizing urban
infrastructure, transportation, and public services through data-driven insights
and decision-making.
MQTT VS HTTP

MQTT: Lightweight, optimized for low-bandwidth,

high-latency networks, ideal for IoT with
constrained resources.

Lorem ipsum dolor sit amet, consectetur

HTTP: Heavier overhead, less efficient for devices
adipiscing elit. Duis vulputate nulla at
ante rhoncus, vel efficitur felis
with limited processing power and battery life.
condimentum. Proin odio odio.

MQTT supports bidirectional communication and

push notifications, making it preferable for real-
time data streaming and event-driven
applications.
 MQTT VS COAP
(CONSTRAINED APPLICATION PROTOCOL)

MQTT: Offers more advanced features like

retained messages, QoS levels, and persistent
sessions, suitable for IoT scenarios demanding
reliable messaging.
Lorem ipsum dolor sit amet, consectetur
adipiscing elit. Duis vulputate nulla at
ante rhoncus, vel efficitur felis
CoAP: Designed for constrained devices and
condimentum. Proin odio odio.
networks, lighter in terms of message size and
resource usage, and easier to integrate with
existing web infrastructure due to its alignment
with REST architectural style.
SECURITY CONSIDERATIONS

In MQTT protocol, security considerations include

authentication, encryption, and authorization
mechanisms. These ensure that only authorized
clients can connect to the broker, data exchanged is
encrypted to prevent eavesdropping, and clients
have restricted access based on their roles or
permissions.
 CONCLUSION

In conclusion, the future of MQTT appears

promising, with advancements focusing on
enhanced security, scalability, and interoperability
to accommodate the growing demands of IoT
Lorem ipsum dolor sit amet, consectetur
ecosystems. As MQTT continues to elit.
adipiscing evolve, its nulla at
Duis vulputate
ante rhoncus, vel efficitur felis
widespread adoption is expected to drive
condimentum. Proin odio odio.
innovation across industries, fostering efficient
communication and seamless integration within
interconnected systems.
 Thank you
for listening!