See discussions, stats, and author profiles for this publication at: https://www.researchgate.

net/publication/366407648

IoT Protocols

Presentation · December 2022

CITATIONS READS

0 2,370

1 author:

Nitin Shivsharan
Sinhgad Technical Education Society
24 PUBLICATIONS 70 CITATIONS

SEE PROFILE

All content following this page was uploaded by Nitin Shivsharan on 19 December 2022.

The user has requested enhancement of the downloaded file.

 IoT Protocols

Dr. Nitin Shivsharan

nmshivsharan@sspmcoe.ac.in

Department of Computer Engineering,

SSPM’s College of Engineering, Kankavli.
University of Mumbai.

December 14, 2022

1 / 44
Outline

1 Introduction to Protocol

2 Can we use TCP/IP for IoT?

3 IoT Protocols

4 Some Future challenges in IoT

5 Conclusion

2 / 44
Minimum Pre-requisite

Computer Networking: Basic concepts, OSI model, Layers in the

OSI model, TCP/IP Protocol Suite, Physical and Logical
Addressing.
IEEE Standards, Ethernet, IPv4 addressing, IPv6 addressing,
Router, Switch, Gateway, Unicast routing, and Multicast routing
Sensors and Sensor Network
C,JavaScript and Python
Machine Learning and Artificial Intelligence

3 / 44
Protocol

Figure: Source:Coursera

Sequence of communication used to conduct some activity in the

distributed system.
4 / 44
Protocol (contd.)

Protocols are widely used in networks for

How fast to send data?
Discover paths to destinations.
Replicate data.
Encode data into transmitable
format.
Protocols often organized into “stack or ”‘suite‘”
Handles collection of activities associated wit particular
environment
Examples: TCP/IP Internet, Bluetooth(IoT)

5 / 44
Can We Use TCP/IP for IoT?

Yes
But IoT introduces additional challenges
Very tight power and compute constraints
Need to work closely with wireless
Need to address applications not just interfaces

6 / 44
Can We Use TCP/IP for IoT?

Yes
But IoT introduces additional challenges
Very tight power and compute constraints
Need to work closely with wireless
Need to address applications not just interfaces

6 / 44
Can We Use TCP/IP for IoT?

Yes
But IoT introduces additional challenges
Very tight power and compute constraints
Need to work closely with wireless
Need to address applications not just interfaces

6 / 44
Can We Use TCP/IP for IoT?

Yes
But IoT introduces additional challenges
Very tight power and compute constraints
Need to work closely with wireless
Need to address applications not just interfaces

6 / 44
Can We Use TCP/IP for IoT?

Yes
But IoT introduces additional challenges
Very tight power and compute constraints
Need to work closely with wireless
Need to address applications not just interfaces

6 / 44
Can We Use TCP/IP for IoT?

Yes
But IoT introduces additional challenges
Very tight power and compute constraints
Need to work closely with wireless
Need to address applications not just interfaces

6 / 44
Some Common IoT Protocols

Figure: Some Common IoT Protocols Source:coursera

7 / 44
Different IoT Protocols for different Environment

Figure: Different IoT Protocols for different Environment

Source:coursera

8 / 44
 Some Types of IoT Protocols

Figure: Application-based IoT protocols [1].

Figure: OSI Model-based IoT Protocols [1].

9 / 44
Physical Layer: Bluetooth Low Energy (BLE)

It dramatically reduces power consumption and cost.

Maintains a similar connectivity range as classic Bluetooth.
BLE works across all mobile operating systems
It is becoming a favorite for consumer electronics due to its low
cost and long battery life

Figure: Bluetooth IoT Protocols Source:coursera

10 / 44
Physical Layer: Long-term Evolution (LTE)

Is a ”Low Power Wide Area Networks” (LPWAN) developed for IoT.

IT is used for wireless broadband communication standard for
mobile devices and data terminals.
LTE increases the capacity and speed of wireless networks and
It supports multicast and broadcast streams.

11 / 44
Physical Layer: Near Field Communication (NFC)

A set of communication protocols using electromagnetic fields that

allow two devices to communicate from within four centimeters
4cm of each other.
NFC-enabled devices function as identity keycards and are
commonly used for contactless mobile payments, ticketing, and
smart cards.
NFC allows you to share small payloads of data between an NFC
tag and an Android-powered device, or
NFC connects two Android-powered devices.

12 / 44
Physical Layer: Power Line Communication (PLC)

A communication technology that enables the sending and

receiving of data over existing power cables.
This allows you to both powers and control an IoT device through
the same cable.

13 / 44
Physical Layer: Ethernet, RFID, and Wi-Fi/802.11

Ethernet
This wired connection is a the less expensive option that provides
fast data connection and low latency.

Radio frequency identification (RFID)

RFID uses electromagnetic fields to track otherwise unpowered
electronic tags.
Compatible hardware supplies power and communicates with these
tags, reading their information for identification and authentication.

Wi-Fi/802.11
Wi-Fi/802.11 is a standard in homes and offices.
Although it’s an inexpensive option, it may not suit all scenarios due
to its limited range and energy consumption.

14 / 44
Physical Layer: Z-Wave

A mesh network, low-energy radio waves.

Frequency band =900 MHz. Data rates= 100 kbps
Can communicate within the range of 120 feet to 40 meters.
Applications:lightings, thermostats, security sensors, locks etc.
No of devices configured within Z-Wave network 232.

Figure: Z-Wave Technology

Source:Z-Wave Technology
15 / 44
Physical Layer: Zigbee

An IEEE 802.15.4-based specification for a suite of high-level

communication protocols used to create personal area networks
with small, low-power digital radios.

Figure: Zeegbee / IEEE802.15.4 IoT Protocols Source:coursera

16 / 44
Data Link Layer:IEEE 802.15.4

A radio standard for low-powered wireless connection.

It’s used with Zigbee, 6LoWPAN, and other standards to build
wireless embedded networks

Figure: Zeegbee / IEEE802.15.4 IoT Protocols Source:coursera

17 / 44
Data Link Layer: LPWAN

Low-power wide-area networks (LPWAN)

networks enable communication across distances of 500 meters to
over 10km in some places.
LoRaWAN is an example of LPWAN that’s optimized for low power
consumption

18 / 44
Network Layer: Internet Protocol (IPv4 and IPv6)

Many IoT protocols utilize IPv4, while more recent executions use
IPv6.
IP routes traffic across the Internet and identifies and locates
devices on the network.
IPv6
It provides a unique identification.
It utilizes 128-bit Internet alphanumeric addresses.
Can support 2128 Internet addresses.
IPSEC being an in-built feature in IPv6 adds to its security.
It also supports Quality of Service (QoS).

19 / 44
Network Layer: 6LoWPAN

Figure: 6LOWPAN- An IP Based Wireless Protocol

Source:6LOWPAN- An IP Based Wireless Protocol

IPv6 over Low power Wireless Personal Area Networks

(6LoWPAN).
20 / 44
Network Layer: 6LoWPAN (contd.)

Low-power devices that have limited processing capabilities.

The smallest devices were unable to participate in the IoT.
Allows for the smallest devices with limited processing ability to
transmit information wirelessly using an internet protocol IPV6.
low cost, short-range, low memory usage, low bit rate.

THE MAXIMUM TRANSMISSION PACKET SIZE IN A STANDARD

IPV6 IS 1024 BYTES WHEREAS IT IS REDUCED TO 127 BYTES IN
6LOWPAN

21 / 44
Transport Layer: Transmission Control Protocol (TCP)

The dominant protocol for a majority of internet connectivity.

It offers host-to-host communication, breaking large sets of data
into individual packets and resending and reassembling packets
as needed.

22 / 44
Transport Layer: User Datagram Protocol (UDP)

A communications protocol that enables process-to-process

communication and runs on top of IP.
UDP improves data transfer rates over TCP and best suits
applications that require lossless data transmissions.

23 / 44
Application Layer: HTTP

Hypertext Transfer Protocol (HTTP)

For transmitting hypermedia documents, such as HTML.
It was designed for communication between web browsers and
web servers
HTTP follows a classical client-server model
HTTP is a stateless protocol.
Stateless:meaning that the server does not keep any data (state)
between two requests.
Multiple Header: Multipurpose Internet Mail Extensions (MIME)
image/jpeg
24 / 44
Application Layer:MQTT

Message Queuing Telemetry Transport Protocol (MQTT)

It designed for lightweight machine-to-machine communication
Primarily used for low-bandwidth connections to remote locations.
It was introduced by IBM in 1999.
Example: MQTT based vehicle accident detection and alert system.

Figure: MQTT Architecture

25 / 44
Application Layer:MQTT (contd.)

It uses a publisher-subscriber architecture.

It consists of three main components:
1 Publishers: The lightweight sensors that connect to the broker to
send their data and go back to sleep whenever possible.,
2 Subscribers: applications that are interested in a certain topic, or
sensory data, so they connect to brokers to be informed whenever
new data are received [1].
3 Broker: classify sensory data in topics and send them to subscribers
interested in the topics.

26 / 44
Application Layer: XMPP

Extensible Messaging and Presence Protocol (XMPP)

Real time communication and streaming xml data between nodes.
Suitable for voice video chat, gaming multiparty chat
Support Client-Server and Server-Server Architecture

27 / 44
Application Layer: CoAP

Constrained Application Protocol (CoAP)

Figure: CoAP features

28 / 44
Application Layer: CoAP (contd.)

A constrained-bandwidth and constrained-network protocol

designed for devices with limited capacity to connect in
machine-to-machine communication.
Request Response Model
GET, PUT, DELETE, etc.
It is also a document-transfer protocol that runs over UDP.
Representational State Transfer (REST) is the standard interface
between HTTP client and servers.
It is designed by IETF Constrained RESTful Environment (Core)
working group to provide lightweight RESTful (HTTP) interface.

29 / 44
Application Layer: CoAP (contd.)

Figure: HTTP and CoAP

CoAP architecture is divided into two main sublayers:messaging and

request/response.
The messaging sublayer is responsible for reliability and duplication
of messages
request/response sublayer is responsible for communication.
CoAP has four messaging modes:
confirmable,

30 / 44
Application Layer: CoAP (contd.)

non- confirmable,
piggyback and
separate
Confirmable and nonconfirmable modes represent the reliable and
unreliable transmissions others used for request/response.

Figure: CoAP Messages

31 / 44
Application Layer: Web Sockets

Figure: Working of Web Sockets Protocol

Full duplex communication over single socket connection

It is based on TCP

Client can be

Browser, IoT Device, Mobile Application, etc.

32 / 44
Application Layer: AMQP

Figure: AMQP architecture

Advanced Message Queuing Protocol (AMQP)

33 / 44
Application Layer: AMQP (contd.)

A software layer that creates interoperability between messaging

middleware.

It helps a range of systems and applications work together, creating

standardized messaging on an industrial scale.

The Advanced Message Queuing Protocol (AMQP) is another session

layer protocol that was designed for financial industry

It runs over TCP and provides a publish/ subscribe architecture which is

similar to that of MQTT.

34 / 44
Application Layer: DDS

Figure: Illustration of DDS Protocol

Data Distribution Service (DDS) is another publish/subscribe protocol

that is designed by the Object Management Group (OMG) for M2M
communications.

Publisher layer is responsible for sensory data distribution.

35 / 44
Application Layer: DDS (contd.)

Data writer interacts with the publishers to agree about the data and
changes to be sent to the subscribers.

Subscribers are the receivers of sensory data to be delivered to the

IoT application.

Data readers basically read the published data and deliver it to the
subscribers and the topics are basically the data that are being
published.

In others words, data writers and data reader take the

responsibilities of the broker in the broker-based architectures.

36 / 44
Application Layer: DDS (contd.)

The basic benefit of this protocol is the excellent QoS levels and
reliability guarantees as it relies on a broker-less architecture, which
suits IoT and M2M communication.

It offers 23 QoS levels

Variety of QoS criteria including: security, urgency, priority, durability,

reliability, etc.

It defines two sublayers:

data-centric publish- subscribe and

data-local reconstruction sublayers [2].

37 / 44
Comparison of IoT Data Protocols

Figure: Source:Introduction to Industrial Internet of Things

38 / 44
State of the Art of IoT

Figure: Source:MIT: The Internet of Things A RoadMap to a

Connected World

39 / 44
Some Future challenges in IoT

The main challenge could be big data analytics arise from the large,
diverse, and time-evolving high-resolution data generated by IoT
devices and sensors.

The technological advancement has led to an drastic increase in the

number of connected IoT devices, which has resulted in big data
generation and transfer

Using open and standardized architectures that have independent

hardware technologies and logic mechanisms is a major challenge in
IoT implementation in residential and commercial settings.

40 / 44
Some Future challenges in IoT (contd.)

Storing and processing data from multiple heterogeneous connected

devices is also a critical IoT-related issue

Integrating new devices and applications in an existing IoT system

architecture without reducing the performance quality is a major
challenge for future development in building environments [3].

41 / 44
Conclusion

We have discussed in brief about the What is

Protocol? and Can we use TCP/IP for IoT?

Also, we have discussed layered architecture and

corresponding IoT protocols used in the particular
layer in detail.
And, lastly the list of some future challenges in the
field of IoT have been presented.

42 / 44
Thank You
??

43 / 44
References

[1] Sudip Misra, Anandarup Mukherjee, and Arijit Roy.

Introduction to Industrial Internet of Things and Industry 4.0.

Routldge Taylaor and Francis, 2021.

[2] Sudip Misra, Anandarup Mukherjee, and Arijit Roy.

Introduction to IoT.

Cambridge University Press, 2021.

[3] Kehinde Lawal and Hamed Nabizadeh Rafsanjani.

Trends, benefits, risks, and challenges of iot implementation in

residential and commercial buildings.

Energy and Built Environment, 3(3):251–266, 2022.

View publication stats
44 / 44