UNIT-2

IOT Protocols
IoT Messaging Protocols
• MQTT stands for Message Queuing Telemetry Transport. MQTT is a
machine to machine internet of things connectivity protocol. It is an
extremely lightweight and publish-subscribe messaging transport protocol.
• This protocol is useful for the connection with the remote location where
the bandwidth is a premium. These characteristics make it useful in various
situations, including constant environment such as for communication
machine to machine and internet of things contexts.
• It is a publish and subscribe system where we can publish and receive the
messages as a client. It makes it easy for communication between multiple
devices.
• It is a simple messaging protocol designed for the constrained devices and
with low bandwidth, so it's a perfect solution for the internet of things
applications.
Characteristics of MQTT
The MQTT has some unique features which are hardly found in other protocols. Some of
the features of an MQTT are given below:
•It is a machine to machine protocol, i.e., it provides communication between the
devices.
•It is designed as a simple and lightweight messaging protocol that uses a
publish/subscribe system to exchange the information between the client and the server.
•It does not require that both the client and the server establish a connection at the
same time.
•It provides faster data transmission, like how WhatsApp/messenger provides a faster
delivery.
•It's a real-time messaging protocol.
•It allows the clients to subscribe to the narrow selection of topics so that they can
receive the information they are looking for.
MQTT Architecture
To understand the MQTT architecture, we first look at the components of the
MQTT.
• Message
• Client
• Server or Broker
• TOPIC
Message
• The message is the data that is carried out by the protocol across the network for
the application. When the message is transmitted over the network, then the
message contains the following parameters:
1.Payload data
2.Quality of Service (QoS)
3.Collection of Properties
4.Topic Name
Client
• In MQTT, the subscriber and publisher are the two roles of a client.
The clients subscribe to the topics to publish and receive messages.
That is if any program or device uses an MQTT, then that device is
referred to as a client. A device is a client if it opens the network
connection to the server, publishes messages that other clients want
to see, subscribes to the messages that it is interested in receiving,
unsubscribes to the messages that it is not interested in receiving,
and closes the network connection to the server.
In MQTT, the client performs two operations:
• Publish: When the client sends the data to the server, then we call
this operation as a publish.
• Subscribe: When the client receives the data from the server, then we
call this operation a subscription.
Server
• The device or a program that allows the client to publish the
messages and subscribe to the messages. A server accepts the
network connection from the client, accepts the messages from the
client, processes the subscribe and unsubscribe requests, forwards
the application messages to the client, and closes the network
connection from the client.
TOPIC
• The label provided to the message is checked against the subscription
known by the server is known as TOPIC.
 Architecture of MQTT
To understand it more clearly, we will look at the example. Suppose a device has a temperature
sensor and wants to send the rating to the server or the broker. If the phone or desktop application
wishes to receive this temperature value on the other side, then there will be two things that
happened.
The publisher first defines the topic; for example, the temperature then publishes the message, i.e.,
the temperature's value. After publishing the message, the phone or the desktop application on the
other side will subscribe to the topic, i.e., temperature and then receive the published message, i.e.,
the value of the temperature.
The server or the broker's role is to deliver the published message to the phone or the desktop
application.
MQTT Message Format
• The MQTT uses the command and the command acknowledgment
format, which means that each command has an associated
acknowledgment. As shown in the figure that the connect command
has connect acknowledgment, subscribe command has subscribe
acknowledgment, and publish command has publish
acknowledgment. This mechanism is similar to the handshaking
mechanism as in TCP protocol.
IOT Messaging Protocol: CoAP
• CoAP, the Constrained Application Protocol, is a
specialized protocol designed to facilitate
communication between constrained devices in low-
power, low-bandwidth networks.
• Unlike traditional protocols like HTTP, CoAP is
tailored to meet the unique demands of IoT devices.
By minimizing overhead and utilizing efficient
messaging, CoAP enables reliable communication in
resource-constrained scenarios.
CoAP Architecture
• This protocol follows a client-server architecture, mirroring the
structure of HTTP but optimized for IoT. Devices in a CoAP
network can act as clients, servers, or both. Clients initiate
communication by sending requests to servers, which in turn
respond with relevant data or actions. This architectural model
simplifies communication between devices and applications while
considering the limitations of constrained environments.
The architecture is centered around the client-server model, which
is a fundamental approach in CoAP, similar to HTTP. This protocol
has optimized this architecture for the unique requirements of IoT
environments.
• CoAP Clients: These are devices or applications that initiate
communication by sending CoAP requests to CoAP servers.
Clients can be sensors, actuators, or any other IoT devices that
require data or actions from the network.
• CoAP Servers: These are devices that respond to CoAP requests
from clients. Servers can also serve as resources that clients
interact with. Servers process incoming requests, perform
relevant actions, and generate responses containing the
requested data or indicating the status of the operation.
• CoAP Requests: Clients send CoAP requests to servers to initiate
actions or retrieve data. CoAP supports various request methods,
such as GET (retrieve data), POST (create new resource), PUT
(update resource), and DELETE (remove resource).
• CoAP Responses: Servers generate CoAP responses
containing the requested data or the outcome of the
requested action. Responses can be confirmable (CON) or
non-confirmable (NON), depending on the desired level of
reliability. Confirmable responses include an
acknowledgment (ACK) from the client.
• CoAP Network and Communication: The communication
between clients and servers happens over the CoAP
network. CoAP is designed to operate over constrained
networks, which might have limited bandwidth and
resources. The protocol’s lightweight nature ensures efficient
communication in such environments.
CoAP Message Types

• This IoT messaging protocol defines four primary message types, each
serving a specific purpose:
• CON (Confirmable): This type ensures reliable communication by
requiring acknowledgment and retransmission of messages until
acknowledged. It suits scenarios where data integrity is crucial.
• NON (Non-Confirmable): NON messages prioritize efficiency over
reliability, making them suitable for scenarios where occasional data
loss is acceptable.
• ACK (Acknowledgment): The recipient of a CON message sends an ACK
message to confirm receipt. It forms a vital part of CoAP’s reliability
mechanism.
• RST (Reset): When a server or client receives a message that cannot be
processed, it sends an RST message to indicate this situation.
CoAP Resources and URIs

• CoAP resources are fundamental entities in the protocol.

They are identified using Uniform Resource Identifiers (URIs),
similar to URLs in HTTP. Resources can represent data,
services, or actions that a device exposes to the network.
This design facilitates interoperability and makes it possible
to apply web paradigms to IoT applications.
CoAP Methods

• CoAP supports a set of methods that clients can use to interact with
resources:
1. GET Method
• The GET method is one of the fundamental methods supported by
CoAP. It allows clients to retrieve a representation of a resource from a
server. A “representation” can be thought of as the current state or
content of the requested resource. When a client sends a GET request,
it is asking the server to provide information about the resource’s
current status.
• For example, in a smart home scenario, a CoAP client (such as a
smartphone app) might send a GET request to a CoAP server that
controls a smart thermostat. The server would respond with a
representation of the thermostat’s current temperature setting,
humidity level, and other relevant data.
2. POST Method
• The POST method enables clients to send data to a server. This
method is typically used for creating new resources on the server
or submitting data for processing. When a client sends a POST
request, it’s asking the server to handle the enclosed data and
perform an action accordingly.
• In the context of IoT, a CoAP client might send a POST request to
a server that manages a home security system. The request could
include data about a detected motion event or a door opening.
The server would process this data and potentially take actions
like sending alerts or logging the event.
3.PUT Method
• The PUT method allows clients to update or create a
resource’s state on the server. Clients use PUT when they
want to modify the content or properties of a resource. If the
resource doesn’t exist, PUT can also be used to create a new
resource.
• For instance, consider a CoAP-enabled environmental
sensor. The sensor might send a PUT request to update its
current temperature reading on the server. If the sensor
detects a change in temperature, it could use PUT to ensure
that the server’s record of the temperature is accurate.
4.DELETE Method
• As the name suggests, the DELETE method is used to request
the removal or deletion of a resource on the server. When a
client sends a DELETE request, it’s asking the server to
eliminate the specified resource.
• In an industrial setting, a CoAP client representing a
maintenance robot could send a DELETE request to a server
managing a broken machine. This request could prompt the
server to remove the machine’s resource representation
from its records, indicating that the machine is no longer
operational
TRANSPORT LAYER PROTOCOL:BLE and Li-Fi
Bluetooth Low Energy
• Bluetooth is a wireless communication protocol designed for short-
range communication between devices. It's commonly used for
connecting devices like smartphones, headphones, keyboards, and
IoT (Internet of Things) devices. Bluetooth Low Energy (BLE) is a
specific version of the Bluetooth protocol that is particularly well-
suited for IoT applications due to its low power consumption.
Technical overview of BLE
• 1. Physical Layer:
• Frequency Bands: BLE operates in the 2.4 GHz ISM (Industrial, Scientific, and
Medical) band.
• Channels: It uses 40 channels spaced 2 MHz apart to minimize interference.
• Frequency Hopping: BLE uses frequency hopping spread spectrum (FHSS) to
avoid interference and fading. This means that the signal hops between different
channels rapidly, providing resilience against interference
• 2. Link Layer:
• Advertising and Scanning: BLE devices can operate in two modes: Advertising
and scanning. Advertising devices broadcast packets at regular intervals, while
scanning devices listen for these packets. This is how devices discover and
connect to each other.
• Connection Types: BLE supports two types of connections - connection-oriented
(for continuous data streaming) and connectionless (for intermittent data
transfer).
• 3. Physical Channel Access:
• BLE uses a Time Division Multiple Access (TDMA) approach, where time is
divided into time slots, and devices take turns transmitting data.
• The device can be in an active or low-power mode, depending on the
specific requirements.
• 4. Protocol Stack:
• Layers: BLE protocol stack consists of several layers - Physical Layer, Link
Layer, Attribute Protocol (ATT), Generic Attribute Profile (GATT), Security
Manager, and Generic Access Profile (GAP).
• ATT and GATT: These are used for organizing and exchanging data between
devices. GATT defines how BLE devices exchange data with Services,
Characteristics, and Descriptors.
5. Host Controller Interface (HCI):
• HCI provides a standardized interface between the Bluetooth
controller (hardware) and the host (software). This allows for easier
integration of BLE into various platforms and operating systems.
6. Security and Privacy:
• BLE provides various security features to ensure data confidentiality,
integrity, and authenticity.
• Pairing and Bonding: Devices can establish a secure connection
through pairing, where they exchange security keys. Bonding allows
devices to remember each other for future connections without re-
pairing.
• Encryption: Once paired, data exchanged between devices can be
encrypted to prevent eavesdropping and tampering.
7. Profiles and Services:
• BLE defines profiles that specify how devices communicate for
specific applications. Examples include:
• Heart Rate Profile: Defines how heart rate monitors communicate
heart rate data.
• Battery Service: Provides information about the battery level of a
device.
• Environmental Sensing Profile: Allows environmental sensors (e.g.,
temperature, humidity) to communicate data.
8. Application Layer:
• At the application layer, developers can create custom applications
using the BLE stack. This layer interacts with the GATT layer to
read/write characteristics, handle notifications, and implement
specific IoT functionalities.
• 9. Power Consumption:
• BLE is designed to be power-efficient, making it suitable for IoT
devices with limited power resources.
• Devices can operate in low-power modes and wake up periodically for
data exchange.

Conclusion:
• Bluetooth Low Energy (BLE) in IoT applications offers a robust
architecture optimized for low-power, short-range communication. By
understanding its physical, link, and application layers, along with
profiles and security features, developers can design efficient and
secure IoT solutions using BLE technology.
IoT Specifics:
1. IoT Protocols:
• BLE can be used as a standalone protocol for IoT or in conjunction
with other protocols like MQTT or CoAP for higher-level
communication.
2. Device Profiles:
• BLE defines specific profiles for various IoT applications, such as the
Generic Attribute Profile (GATT) for defining services and
characteristics.
3. Interoperability:
• BLE ensures interoperability between different devices by defining
standardized profiles that manufacturers can implement.
2. Li-Fi(Light Fidelity
• A technology that is 100 times faster than current average wifi speeds!
Yes, this technology exists, and this is known as Light Fidelity(LiFi).
• LiFi, also known as LIGHT FIDELITY, is a both-sided wireless
communication system that releases information via LED (Light Emitting
Device) or Infrared Light.
• LiFi technology was the first time it came into use in the year 2011. LiFi is
an extension of WIFI Communication which requires a light source for
data sending and communication on the internet.
• The most significant feature of LiFi is that it’s most faster than WIFI
communication.
• LiFi increases the speed and bandwidth of wifi, 3G, and 4G. LiFi
transmission speeds can go over 100 Gbps, 14 times faster than WIFI
Communication, also known as the world’s fastest wifi.
• The interference or the obstacles are less during the communication
process, so in seawater, it is preferable to use LiFi as WIFI communication
can have numerous interference while communicating. The founder of the
father of this technology is Professor Harald Hass.
• The Li-Fi circuit is used consists of mainly three sub-
assemblies
1.RF Driver – RF Driver is used for controlling or handling the
circuit for digital and analog lighting controls.
2.Emitter – An emitter device is used to emit or generate
charged particles.
3.Power Supply: Power Supply is an electrical device used to
supply electrical power to an electrical load for operation.
Working
1.The working or the implementation of LiFi is not very complex like
WIFI communication. It is straightforward to send information
through the LED light bulb, which emits pulsed light to receivers.
After that, the receiver collects the sent data or information and
understands the transmitted data.
2.The LED bulb can be toggled on and off instantly for more reliable
communication and for saving power. So only the things we require
for this communication are some LEDs Bulbs and a controller that
codes into those LEDs Bulbs.
3.In some cases, we need to alter or modify the rate of transmission
in which the lED bulb flash depending upon the information we
want to encode.
4.As we stated above, the Light source is the main component in this
communication, so that light source will serve as the central hub for
data transmission from one point to another destination point.
Advantages of LiFi :
1.Every User wants the communication and data transfer should be fast, so
LiFi does this for us; its main advantage is the Speed of Transmission.
LIFEIrDA-compliant standard-compliant is 10000 times or even faster
than the Spectrum used by RADIO waves in WIFI communication or data
transfer.
2.The structure of LiFi is not very complex as WIFI, as Lightboxes are
already present in LiFi, so the design is already available and pre-
installed.
3.As the Speed is high, indirectly data transfer rate increases. So the data
transfer rate of LiFi is approximately 10 Gbps or sometimes more.
4.Light is the primary source required in LiFi structure for communication,
and luckily Light is already available in natural or artificial ways.
Everywhere there is Light, so the Data is present where Light exists.
5.We all know LEDs use a very minimal amount of energy for
their usage or operation. So the energy and cost required for
Data Transfer in LiFi are also minimal.
6.The interference or obstacles in WIFI are more than the LiFi, so
LiFi is more secure than the WIFI communication, and this is
also an essential advantage regarding LiFi.
Disadvantages of LiFi :
• No Thing is perfect! Every aspect has its advantages and
disadvantages. So LiFi also has some disadvantages.
1.LIFI has a minimal area of scope or range also connectivity.
2.There is an Unavailability of Compatible Technologies.
3.LIFI can give rise to Light Interference and Light Pollution.
4.LiFI has Possible cost Implications.
5.Cannot penetrate through walls.
6.Interference from external sources i.e. sun, normal bulbs,
candles, etc.
NETWORK PROTOCOL:6LoWPAN
6LoWPAN
• What is 6LoWPAN?
6LoWPAN stands for IPv6 over Low-Power Wireless Personal Area
Networks. It’s a communication protocol designed to enable small,
low-power devices to connect over wireless networks.
6LoWPAN is an IPv6 protocol, and It’s extended from IPv6 over
Low Power Personal Area Network.
WPAN is a Personal Area Network (PAN) where the
interconnected devices are centered around a person’s
workspace and connected through a wireless medium.
6LoWPAN allows communication using the IPv6 protocol. IPv6
is Internet Protocol Version 6 is a network layer protocol that
allows communication to take place over the network. It is faster
and more reliable and provides a large number of addresses.
• It has very low cost, short-range, low memory usage, and low
bit rate. It comprises an Edge Router and Sensor Nodes. Even
the smallest of the IoT devices can now be part of the network,
and the information can be transmitted to the outside world as
well. For example, LED Streetlights.
• It is a technology that makes the individual nodes IP-enabled.
6LoWPAN can interact with 802.15.4 devices and also other
types of devices on an IP Network.
Basic Requirements of 6LoWPAN
• The device should be having sleep mode in order to support
the battery saving.
• Minimal memory requirement.
• Routing overhead should be lowered.
Functioning of the 6LoWPAN Network

• The magic of 6LoWPAN lies in its ability to seamlessly

integrate resource-constrained devices with the internet.
Here’s a breakdown of the key processes:
1.Data Flow:
1. A sensor (host) within the 6LoWPAN network
collects data.
2. It transmits the data packet to a router in the
network.
3. The router, based on the destination address,
determines if the data needs to be forwarded
outside the 6LoWPAN network.
4. If the destination is an external device (internet or
another network), the router forwards the data
packet to the edge router.
5. The edge router acts as a translator, adapting the
6LoWPAN packet format to the standard IPv6
format for transmission across the internet
backbone.
6. Conversely, data packets received from the
internet destined for a device within the 6LoWPAN
follow the reverse path, with the edge router
translating them for the 6LoWPAN format and the
router finally delivering them to the intended
device (host).
2.Local Communication:
1. Data exchange between devices solely within the 6LoWPAN
network bypasses the edge router.
2. Routers within the 6LoWPAN efficiently route the data packets to
their destination based on the local routing tables.
3.Power Efficiency:
1. Hosts within the network operate in a sleep mode, minimizing
power consumption.
2. They periodically wake up to check for data from the router.
3. This sleep-wake cycle significantly reduces energy usage compared
to constantly active devices.
Features of 6LoWPAN
• It is used with IEEE 802.15,.4 in the 2.4 GHz band.
• Outdoor range: ~200 m (maximum)
• Data rate: 200kbps (maximum)
• Maximum number of nodes: ~100
Applications of 6LoWPAN
• It is a wireless sensor network.
• It is used in home-automation,
• It is used in smart agricultural techniques, and industrial
monitoring.
• It is utilised to make IPv6 packet transmission on networks
with constrained power and reliability resources possible.
• Advantages of 6LoWPAN
• 6LoWPAN is a mesh network that is robust, scalable, and can heal
on its own.
• It delivers low-cost and secure communication in IoT devices.
• It uses IPv6 protocol and so it can be directly routed to cloud
platforms.
• It offers one-to-many and many-to-one routing.
• In the network, leaf nodes can be in sleep mode for a longer
duration of time.
• Disadvantages of 6LoWPAN
• It is comparatively less secure than Zigbee.
• It has lesser immunity to interference than that Wi-Fi
and Bluetooth.
• Without the mesh topology, it supports a short range.
IoT Functional Blocks

• IoT systems are composed of a number of building blocks,

including sensors/actuators, connectivity, security, services,
etc. The functional blocks are responsible for sensing,
verification, actuation, management, and communication.
• These functional blocks are made up of devices that handle
1.interactions between a web server and the client,
2. enable controls and monitoring functions,
3.manage data transfer, secure the IoT system through
authentication and various purposes,
4.And offer an interface for monitoring and managing various
concepts.
1.Sensor/Actuator block
• The sensor/actuator block serves as the data entry point in
an IoT system. Sensors collect data from their
surroundings, whereas actuators drive physical processes.
Sensors gather data on temperature, humidity, light,
motion, and other variables, whereas actuators turn on
lights, open doors, and control machines. These gadgets
work together to collect data and operate in the physical
world.
2.Connectivity Block
• Once the sensor/actuator block has collected data, it must
be sent to the remainder of the system. This is when the
connection block enters the picture. The connectivity block
is in charge of creating and managing communication
channels amongst IoT system devices. This can be
accomplished with the use of several technologies such as
Wi-Fi, Bluetooth, ZigBee, and cellular networks.
3.Data Processing Block
• The obtained data is examined and processed in the
data processing block. This block is in charge of filtering
out noise and irrelevant data, converting the data into
an easily studied format, and recognizing patterns and
anomalies in the data. This block can also execute real-
time analysis, enabling speedy data-driven decisions.
4.Application Block
• The application block is the component of the IoT
system that gives value to the end user. This block is in
charge of utilizing the processed data to provide a
specified function or service. An application block, for
example, could be used to provide insights into energy
usage in a building or to adjust the temperature in a
greenhouse.
5.Security Block
• The security block is in charge of assuring the IoT system's
security and protection against illegal access. This block is
in charge of authentication and authorization, as well as
data encryption during transmission and storage. It also
handles intrusion detection and response, assisting in the
prevention and mitigation of threats.
6.Management Block
• The management block is in charge of overseeing the
overall operation of the IoT system. This block is capable of
handling device configuration, firmware updates, and
system monitoring. It can also give analytics and reporting,
allowing system administrators to understand how the
system is operating and find areas for improvement.
Advantages of IoT Functional Blocks
• IoT Functional Blocks provide various advantages to
enterprises and people interested in implementing IoT
solutions.
• These advantages include −
• Scalability
• IoT Scalability is built into Functional Blocks, allowing
enterprises to add new devices and services to their IoT
system as needed. The capacity to scale assures that an IoT
system can grow and react to changing business needs and
future technology.
• Interoperability
• IoT Functional Blocks is a standardized architecture for
developing IoT solutions. This standardization means that
devices and services from various suppliers may function
seamlessly together, enhancing interoperability and lowering
integration costs.
• Modularity
• Because IoT Functional Blocks are modular, they may
be swapped, modified, or added as needed. Because of
this versatility, enterprises can select the optimal
components for their IoT system and easily swap out
components as needed.
• Flexibility
• IoT Functional Blocks offer a variety of deployment
choices. Depending on their needs, businesses can
implement an IoT system on-premises, in the cloud, or
in a hybrid approach.
Cloud Storage Models
• Internet of Things (IoT) storage involves managing and processing
immense volumes of data generated by connected devices.
• These devices, ranging from simple sensors to complex industrial
machinery, produce diverse, continuous streams of data that need
to be stored for further analysis and real-time decision making.
• IoT storage demands differ from traditional data storage, requiring
highly scalable, durable, and accessible storage systems that can
handle large volumes of high-velocity, unstructured data.
• This necessitates advanced storage architectures and technologies
designed to meet the performance and scalability needs of IoT
applications.
Storage Architectures
• Over the past decade, we’ve seen four such architectures emerge:
• Serverless storage: The use of infrastructure-as-a-service (IaaS)
has grown in popularity in recent years, especially for companies
developing IoT systems. In this model, the complexity of cloud
storage systems are hidden from the data owner, who uses a
software interface to manage data.
• Hybrid storage: This is a term used to describe a storage
infrastructure that mixes private cloud storage with storage
provided by public cloud services.
• Multi-Cloud: This is a similar model to hybrid storage, but with
more emphasis on replicating data across multiple clouds in order
to improve security, and to enhance resiliency.
• Hybrid Cloud: Hybrid cloud environments combine private and
public clouds, which allows for easier customization and lower
costs.
 IoT Data Storage Approaches
• Edge Storage
Edge storage involves storing data on local devices or near the data source, rather than
transmitting it to a centralized data center. This mitigates latency issues by processing data
close to where it is generated, reducing bandwidth usage on networks. Examples of use cases
include manufacturing plants and autonomous vehicles.
• Cloud Storage
Cloud storage is scalable and flexible, leveraging the cloud’s resources to store data remotely.
This allows IoT deployments to expand storage capacity as needed without investing in
physical infrastructure. However, relying solely on cloud storage can introduce latency issues
due to data having to travel from the IoT devices to the cloud. Data caching and choosing
cloud data centers located nearer to the data sources can help mitigate these latency
problems.
• Hybrid Storage
Hybrid storage combines the advantages of edge and cloud storage, allowing data to be
stored and processed both locally and in the cloud. This enables a balance between reducing
latency and leveraging the scalable storage and advanced analytics capabilities of the cloud.
It is useful for local decision-making, but where long-term data analysis can be offloaded to
the cloud.
Covered in PPT for UNIT1
• Communication Models,
• Communication APIs: REST based, Web Socket
Based.