Internet of Things (IoT):

IoT Protocols

Mohammad Alharbi, PhD

[email protected]
Office 0120
Contents
● Generic Block Diagram of an IoT Device
● IoT Protocols
● Communication Model
Generic Block Diagram of an IoT Device
An IoT device may consist of several
interfaces for connections to other
devices, both wired and wireless.

● I/O interfaces for sensors

● Interfaces for internet
connectivity
● Memory and storage interfaces
● Audio/video interfaces
IoT Protocols
Data Link Layer Communication Protocols
Several Communication Protocols are used in Internet of Things (IoT) to provide service to the
network layer.
● Ethernet (802.3, 802.3.i, 802.3.j, 802.3.ae)
● Bluetooth
● BLE (Bluetooth Low Energy)
● LR-WPAN (ZigBee, 6LoWPAN)
● Wi-Fi (802.11a, 802.11b, 802.11g, 802.11n, 802.11ac, 802.11ad)
● WiMax (802.16m)
● Z-Wave
● RFID (Radio-Frequency Identification)
● Cellular (GSM/3G/4G/5G etc)
Network/Internet Layer Protocols
● Responsible for sending of IP datagrams from source to destination network
● Performs the host addressing and packet routing
● Host identification is done using hierarchical IP addressing schemes such as IPV4
or IPV6
○ IPV4 is used to identify the devices on a network using hierarchical addressing scheme. It uses 32-bit
address scheme
○ IPV6 uses 128-bit address scheme
Transport Layer Protocols
● Provide end-to-end message transfer capability independent of the underlying
network
TCP UDP
● Transmission Control Protocol ● User Datagram Protocol

● Connection Oriented ● Connectionless

● Ensures Reliable transmission ● Does not ensures Reliable transmission

● Provides Error Detection Capability to ensure no duplicacy of ● Does not provide proper ordering of messages
packets and retransmit lost packets

● Flow Control capability to ensure the sending data rate is not too ● Transaction oriented and stateless
high for the receiver process

● Congestion control capability helps in avoiding congestion which

leads to degradation of network performance
Application Layer Protocols
The application layer is responsible for enabling communication between applications
and end-users. In simple terms, itʼs where the actual services and apps we interact with
on the internet operate.
Application Layer Protocols
1. MQTT (Message Queuing Telemetry Transport):
○ Purpose: Often used for sending messages between devices in real-time.
○ How It Works: Uses a publish-subscribe model, where devices can "publish" messages on topics and others "subscribe" to them.
○ Use Cases: Smart homes, connected cars, and remote sensors.
2. CoAP (Constrained Application Protocol):
○ Purpose: Designed for low-power devices with limited processing power.
○ How It Works: Uses a request-response model similar to HTTP, but it's optimized for small, constrained devices.
○ Use Cases: Smart meters, environmental monitoring.
3. HTTP/HTTPS (Hypertext Transfer Protocol / Secure):
○ Purpose: Common protocol for accessing and transferring web data.
○ How It Works: Uses a request-response model where clients request data and servers respond.
○ Use Cases: Web-based IoT applications, like smart appliances and wearables with internet access.
4. AMQP (Advanced Message Queuing Protocol):
○ Purpose: Reliable communication for business applications.
○ How It Works: Uses message queues and offers more control and security for message delivery.
○ Use Cases: Industrial IoT systems and business applications that require secure, ordered message delivery.
5. DDS (Data Distribution Service):
○ Purpose: Real-time communication in distributed systems.
○ How It Works: Uses a publish-subscribe model for high-performance, real-time applications.
○ Use Cases: Robotics, autonomous vehicles, and industrial automation.
Communication Models
Request-Response Model

Publish-Subscribe Model

Push–Pull Communication Model

Exclusive Pair Communication Model

REST-based Communication APIs

Communication Models: Request-Response
How It Works: In this simple model, a
device (the “client”) sends a request to
another device (the “server”), and the
server responds with the requested
information or service. Itʼs like asking a
question and getting an answer.
Use Case: Common in web browsing.
When you type a URL, your browser (client)
requests the webpage from a server, and
the server responds by loading the page.
Communication Models: Publish-Subscribe
How It Works: In this model, a central system
(called a “broker”) helps distribute messages.
Devices or users that want to share information
are called "publishers," and those interested in
receiving certain types of information are
"subscribers." The broker makes sure each
subscriber gets the messages they want.

Use Case: Used in smart home setups. For

example, a smart thermostat (publisher) sends
temperature updates to a broker, which then
forwards them to apps on your phone
(subscribers).
Communication Models: Push–Pull
How It Works: In this model, data is
“pushed” from devices to a central storage
or buffer, and then “pulled” by other
devices or applications when theyʼre ready
to use it. This model provides flexibility in
when data is processed.
Use Case: Common in social media
platforms, where users push posts to the
platform, and followers pull (see) the
updates in their feeds whenever they log
in.
Communication Models: Exclusive Pair
How It Works: It creates a private, direct
connection between just two devices. Think of
it as a private conversation where only these
two devices can "talk" and "listen" to each
other, with no other devices allowed in.
Use Case:
1. Personal device pairing such as connecting a
smartwatch to a phone.
2. Security-Critical applications: Useful in
applications, where private, encrypted
connections between two devices (like a smart
lock and a smartphone) are essential for safety.
Communication Models: REST-based API
Representational State Transfer (REST) is a
set of architectural principles by which you
can design web services and web APIs that
focus on a systemʼs resources and how
resource states are addressed and
transferred.

REST APIs follow the request–response

communication model.
Communication Models: REST-based API
Simple Example:

● You Want to Check the Weather:

○ You open a weather app (the client).
○ The app sends a GET request to the server at a URL for the
current weather.
○ The server gets the current weather data and sends it back to
the app.
○ The app displays the weather on your screen.
References
● Hanes, David, et al. IoT fundamentals: Networking technologies, protocols, and use

cases for the internet of things. Cisco Press, 2017.