MTIN 101

IoT ARCHITECTURE AND PROTOCOLS

======================================================================

Unit III
IoT Data Link Layer & Network Layer Protocols: PHY/MAC Layer(3GPP MTC, IEEE 802.11, IEEE
802.15), Wireless HART,ZWave,Bluetooth Low Energy, Zigbee Smart Energy, DASH7 - Network
Layer-IPv4,IPv6, 6LoWPAN, 6TiSCH,ND, DHCP, ICMP, RPL, CORPL, CARP

IoT Data Link Layer & Network Layer Protocols:

IoT Data Link Layer :

Several Communication Protocols are used in Internet of Things (IoT) to provide service to the network
layer.
As we know IoT is based on networking of things where smart devices communicate with each other by
sending and receiving data. So for that several network protocols (Communication protocols) are used to
connect the IoT enabled devices and to establish the communication.

Bluetooth
Bluetooth is a short-range wireless communication network over a radio frequency. Bluetooth is mostly
integrated into smartphones and mobile devices. The Bluetooth communication network works within 2.4
ISM band frequencies with data rate up to 3Mbps.

There are three categories of Bluetooth technology:

1. Bluetooth Classic
2. Bluetooth Low Energy
3. Bluetooth SmartReady

The features of Bluetooth 5.0 version is introduced as Bluetooth 5 which have been developed entirely for
the Internet of Things.

Properties of Bluetooth network

o Standard: Bluetooth 4.2
o Frequency: 2.4GHz
o Range: 50-150m
o Data transfer rates: 3Mbps

Advantages of Bluetooth network

o It is wireless.
o It is cheap.
o It is easy to install.
o It is free to use if the device is installed with it.

Disadvantages of Bluetooth network

o It is a short-range communication network.
o It connects only two devices at a time.
Bluetooth Low Energy

Bluetooth low energy (BLE) is a short

short-range
range communication network protocol with PHY (physical layer)
and MAC (Medium Access Control) llayer. It is designed for low-power
power devices which uses less data. BLE
always remain in sleep mode except when the connection between devices is initiated and data
transmission occurs, due to this it conserves power of the device. Bluetooth low energy follows
follow the
master/slave architecture and offers two types of frames that are adverting and data frames. Slave node
sent the advertising frame to discover one or more dedicated advertisement channels. Master nodes
sense this advertisement channels to find slaves and connect them.

Z-Wave

Z-Wave
Wave is a wireless communication protocol with the frequency of 900MHz. The ranges of Z-Wave
Z lies
between 30 meters to 100 meters with the data transfer rate of 100kbps so that it is suitable for small
messages in IoT applications
ions for home automation. This communication protocol operates on mesh
network architecture with one and several secondary controllers.

Properties of Z-Wave protocol

• Standard: Z-Wave
Wave Alliance ZAD12837 / ITU
ITU-T G.9959
• Frequency: 908.42GHz
• Range: 30-100m
• Data transfer rate: 100kbps

Advantages of Z-Wave protocol

• Low power consumption

 • Remote or local control
• Simple installation
• Interoperability

Application of Z-Wave protocol

• Smart product and IoT based application

• Energy saving
• Home security

ZigBee Smart Energy

ZigBee is a low power, low data rate wireless personal area network communication protocol. It is mostly
used in home automation and industrial settings. Since ZigBee is a low power communication protocol,
the IoT power devices used with ZigBee technol
technology.
ogy. The ZigBee communication protocol is based on the
IEEE 802.15.4 standard operating at the 2.4GHz frequency. The ZigBee protocol supports star, cluster or
wireless mesh technology topology.

ZigBee uses the following devices in its network:

o Zigbee Coordinator
o Zigbee End Device
o Zigbee Router

Properties of ZigBee protocol

o Standard: ZigBee 3.0 based on IEEE802.15.4
o Frequency: 2.4GHz
o Range: 10-100m
o Data transfer rate: 250kbps

Advantages of ZigBee protocol

o Wireless
o Mesh networking
o Direct communication
o Low power consumption

Disadvantages of ZigBee protocol

o Costly
o Works with low speed within a small distance

Application of ZigBee protocol

o Commercial and residential control
 o Personal and healthcare
o Home networking
o Industrial control and management
o Consumer electronics

DASH7

DASH7 is an “instant-on,” long-range, low power wireless communications standard for applications
requiring modest bandwidth like text messages, sensor readings, or location-based advertising
coordinates.
DASH7 is an open source RFID-standard for wireless sensor networking, which operates in the 433 MHz
unlicensed ISM band/SRD band. DASH7 provides multi-year battery life, range of up to 2 km, indoor
location with 1 meter accuracy, low latency for connecting with moving things, a very small open source
protocol stack, AES 128-bit shared key encryption support, and data transfer of up to 200 kbit/s.

Wireless HART

https://instrumentationtools.com/wireless-hart-communication-protocol-overview/

https://www.pepperl-fuchs.com/india/hi/10028.htm

WirelessHart is a subset of the HART industrial instrument communication standard as of version 7,

communicating process data over 2.4 GHz radio waves. Individual instruments communicate with a
common “gateway” device serving as an interface between the wireless network and a wired network or a
host control system. In addition to this, though, individual WirelessHART devices also form links with one
another, so that the network data routes look like a “mesh” with all nearby nodes interconnected in
addition to connecting with the gateway.
In a mesh network, devices (nodes) perform double-duty as repeaters to relay data from other
instruments to the gateway as needed. In other words, data transmitted from one WirelessHART
instrument may not be directly received by the gateway device if that path is blocked or too far away.
Instead, the data may “hop” from one device to another nearby, which then re-broadcasts that information
to the gateway via a clearer path.
Network Layer Protocols:
IoT Network Layer Protocols

The network layer is divided into two sublayers: routing layer which handles the transfer of packets from
source to destination, and an encapsulation layer that forms the packets.

RPL Protocol

RPL stands for Routing Protocol for Low-Power and Lossy Network. It is a distance-vector protocol that
supports a varity of Data Link Protocols. RPL builds a Destination Oriented Directed Acyclic Graph
(DODAG) which has only one route from each leaf node to the root. All the traffic in this DODAG is routed
through the root. Initially, each node sends a DODAG Information Object (DIO) announcing them self as a
root. This information travels in the network, and complete DODAG is gradually built. When a new node
wants to join the network, it sends a DODAG Information Solicitation (DIS) request and root responds
back with a DAO Acknowledgment (DAO-ACK) confirming the join.

CORPL

CORPL protocol is the extension of the RPL protocol, which is termed as cognitive RPL. This network
protocol is designed for cognitive networks and uses DODAG topology. CORPL protocol makes two new
modifications in the RPL protocol. It uses opportunistic forwarding to forward a packet between the
nodes. Each node of CORPL protocol keeps the information of forwarding set rather than parents only
maintaining it. Each node updates its changes to its neighbor using DIO messages. On the basis of this
updated message, each node frequently updates its neighbor for constant forwarder set.

CARP Protocol

CARP (Channel-Aware Routing Protocol) is a distributed routing protocol. It is designed for underwater
communication. It has lightweight packets so that it can be used for Internet of Things (IoT). It performs
two different functionalities: network initialization and data forwarding. CARP protocol does not support
previously collected data. Hence, it is not beneficial for those IoT or other application where data is
changed frequently. The upgradation of CARP is done in E-CARP which overcomes the limitation of
CARP. The E-CARP allows the sink node to save previously received sensory data.

6LoWPAN

The 6LoWPAN protocol refers to IPv6 Low Power Personal Area Network which uses a lightweight
IP-based communication to travel over low data rate networks. It has limited processing ability to transfer
information wirelessly using an internet protocol. So, it is mainly used for home and building automation.
The 6LoWPAN protocol operates only within the 2.4 GHz frequency range with 250 kbps transfer rate. It
has a maximum length of 128-bit header packets.
 6LowPAN Security Measure

Security is a major issue for 6LowPAN communication Protocol. There are several attacks issues at the
security level of 6LoWPAN which aim is to direct destruction of the network. Since it is the combination of
two systems, so, there is a possibility of attack from two sides that targets all the layer of the 6LoWPAN
stack (Physical layer, Data link layer, Adaptation layer, Network layer, Transport layer, Application layer).

Properties of 6LowPAN protocol

• Standard: RFC6282
• Frequency: Used over a variety of other networking media including Bluetooth Smart (2.4GHz)
or ZigBee or low-power RF (sub-1GHz)
• Range: NA
• Data Rates: NA

IP version 4 (IPv4) –

IPv4 is still the widely used network layer protocol used for networking computers. IPv4 addresses are
expressed as dotted decimal numbers. The address consist of four octets (32-bit number) divided into two
parts – network address to uniquely identify a TCP-IP or IOT network and host address to identify host
within the identified network. A subnet mask is used along with the 32-bit IP address to uniquely identify a
host (computer or IOT device). The subnet mask is also a 32-bit number. The subnet mask helps in
identifying the exact location of the host device. The routers extract the network address from the IPv4
address and compare it with a route table to identify the network and the data packet is first delivered to
the target network. Then, the subnet mask is used to uniquely identify the host and deliver the data
packet to the host device.
In the standard, there are five IPv4 classes – A, B, C, D and E. The class of an IPv4 address is identified
by the first octet of the IP address. The classes A, B and C are most commonly used. The class D is
reserved for multi-casting and Class E for experimental purposes.

In class A IPv4 address, first octet is used to identify network and remaining three octet are used to
identify the host. This addressing class is generally used in networks having large number of host
devices. The first bit of the first octet is always set to 0, so, the first octet can have a decimal value in
range from 1 to 127. The value of 127 for first octet in class A address remains reserved for loopback IP
address or localhost, so values only from 1 to 126 remains available. The default subnet mask for class A
is 255.0.0.0. With this addressing scheme, maximum 126 networks and maximum 16777214 host devices
in each network can be uniquely identified.

In class B IPv4 address, first two octet are used to identify network and last two octet are used to identify
host device. The first two bits in first octet of Class B address is always set to 10, so the network address
can range from 128.0.X.X to 191.255.X.X. The default subnet mask for class B address is 255.255.0.0.
With this addressing scheme, maximum 16384 networks and maximum 65534 host devices in each
network can be uniquely identified.
In class C IPv4 address, first three octet are used to identify network and last octet is used to identify host
device. The first three bits in first octet of Class C address is always set to 110, so its value can range
from 192 to 223. The network address can range from 192.0.0.X to 223.255.255.X. The default subnet
mask for class B address is 255.255.255.0. With this addressing scheme, maximum 2097152 networks
and maximum 254 host devices in each network can be uniquely identified.

Suppose, a class C IPv4 address be 192.168.8.1 and a subnet mask be 255.255.255.0. The subnet mask
in binary converts to 11111111.11111111.11111111.00000000, which implies that first three octet are the
network address and the last octet is the host address. So, in the IP address 192.168.8.1, 192.168.8.0
will be the network address and 000.000.000.1 will be the host address.

There is only address space for 4,294,967,296 addresses in IPv4 standard. This address space has
already exhausted and is not scalable to accommodate the billions of IOT devices. So, IPv6 has been
introduced to expand address space for the IOT.

IP version 6 (IPv6) –

IP Version 6 is an interoperable successor of IPv4. The address space in IPv4 is limited to roughly 4.3
billion devices. There will be 20 billion IOT devices alone by the year 2020. So, an IP addressing standard
that would be scalable to cater to the future IOT infrastructure was the need of the time.
Compared to 32-bit addresses in IPv4, there are 128-bit addresses in IPv6. The address is divided into
eight 16-bit blocks where each block can be represented by a 4-digit hexadecimal number. each block in
the IPv6 address is separated by a semi-colon. So, a typical IPv6 address would look like
77AD:45DF:A23D:8:2D:76DF:245:AF. There are eight blocks in the address – 77AD, 45DF, A23D, 8, 2D,
76DF, 245 and AF.

Each block is separated by a semicolon in the address.

There can be three types of addresses in IPv6 standard –

1) Unicast address – address to identify a single interface
2) Multicast address – address to identify multiple interfaces grouped into different nodes
3) Anycast address – address to identify single interface in a set of interfaces belonging to different
nodes
With 128-bit addresses, IPv6 can be used to identify 340 trillion trillion trillion (38X1038) devices which is
roughly 667 sextillion (667X1021) devices per square meter on earth. This is more than enough for the
farthest future of the IOT.

6TiSCH –

Developed by IETF, 6TiSCH is a IPv6 standard for 802.15.4 MAC layer protocols. The standard allows
IPv6 addresses to pass through Time-Slotted Channel Hopping (TSCH) mode of IEEE 802.15.4e MAC
layer, so that the IPv6 adaption layer can be used for industrial automation and Low Power Lossy
Networks (LLN).
What is DHCP?

Dynamic Host Configuration Protocol (DHCP)

Dynamic Host Configuration Protocol (DHCP) is a network management protocol used to automate the
process of configuring devices on IP networks, thus allowing them to use network services such as DNS,
NTP, and any communication protocol based on UDP or TCP. A DHCP server dynamically assigns an IP
address and other network configuration parameters to each device on a network so they can
communicate with other IP networks. DHCP is an enhancement of an older protocol called BOOTP.
DHCP is an important part of the DDI solution (DNS-DHCP-IPAM).

What is the Internet Control Message Protocol (ICMP)?

The Internet Control Message Protocol (ICMP) is a network layer protocol used by network devices to
diagnose network communication issues. ICMP is mainly used to determine whether or not data is
reaching its intended destination in a timely manner. Commonly, the ICMP protocol is used on network
devices, such as routers. ICMP is crucial for error reporting and testing, but it can also be used
in distributed denial-of-service (DDoS) attacks.

What is ICMP used for?

The primary purpose of ICMP is for error reporting. When two devices connect over the Internet, the
ICMP generates errors to share with the sending device in the event that any of the data did not get to its
intended destination. For example, if a packet of data is too large for a router, the router will drop the
packet and send an ICMP message back to the original source for the data.

The medium access control (MAC)

The medium access control (MAC) is a sublayer of the data link layer of the open system interconnections
(OSI) reference model for data transmission. It is responsible for flow control and multiplexing for
transmission medium. It controls the transmission of data packets via remotely shared channels. It sends
data over the network interface card.

MAC Layer in the OSI Model

The Open System Interconnections (OSI) model is a layered networking framework that conceptualizes
how communications should be done between heterogeneous systems. The data link layer is the second
lowest layer. It is divided into two sublayers −

• The logical link control (LLC) sublayer

• The medium access control (MAC) sublayer

The following diagram depicts the position of the MAC layer −

MAC Addresses

MAC address or media access control address is a unique identifier allotted to a network interface
controller (NIC) of a device. It is used as a network address for data transmission within a network
segment like Ethernet, Wi-Fi, and Bluetooth.
MAC address is assigned to a network adapter at the time of manufacturing. It is hardwired or hard-coded
in the network interface card (NIC). A MAC address comprises of six groups of two hexadecimal digits,
separated by hyphens, colons, or no separators. An example of a MAC address is 00:0A:89:5B:F0:11.

The MAC and PHY layers

Most network protocols use the concept of layers to separate different components and functions into
independent modules that developers can assemble in different ways.
The PHY layer defines the physical and electrical characteristics of the network. It is responsible for
managing the hardware that modulates and demodulates the RF bits.
The MAC layer is responsible for sending and receiving RF frames. As part of each packet, there is a
MAC layer data header that has addressing information as well as packet options. This layer implements
packet acknowledgments (ACKs), packet tracking to eliminate duplicates, and so forth.

• When a device is transmitting, it cannot receive packets.

• When a device is not sleeping, it is either receiving or transmitting.
• There are no beacons or master/slave requirements in the design of the MAC/PHY.

The XBee/XBee-PRO SX RF Module uses a patented method for scanning and finding a transmission.
When a device transmits, it sends out a repeated preamble pattern, a MAC header, optionally a network
header, followed by packet data. A receiving device is able to scan all the channels to find a transmission
during the preamble, then once it has locked into that channel it attempts to receive the whole packet.

The following table shows the AT commands related to the MAC/PHY layers.
 AT
command Function

CM The Channel Mask is a user-defined list of channels that the device operates on.
For additional information, see CM (Channel Mask).
HP Change HP (Preamble ID) to make it so a group of devices will not interfere with another
group of devices in the same vicinity. The advantage of changing this parameter is that a
receiving device will not lock into a transmission of a transmitting device that does not have
the same Preamble ID.
ID Change ID (Network ID) to further keep devices from interfering with each other. The device
matches this ID after it matches the preamble pattern and after it receives the MAC header.
A unique network identifier distinguishes each network. For devices to communicate, they
must be configured with the same network identifier. The ID parameter allows multiple
networks to co-exist on the same physical channel.
PL Sets the transmit (TX) power level. You can reduce the power level from the maximum to
reduce current consumption or for testing. This comes at the expense of reduced radio range.
RR Specifies the number of times a sending device attempts to get an ACK from a destination
device when it sends a unicast packet.

MT Specifies the number of times that a device repeatedly transmits a broadcast packet. This
adds redundancy, which improves reliability.

3GPP MTC

A MTC Device might also communicate locally (wirelessly, possibly through a PAN, or hardwired)
with other entities which provide the MTC Device “raw data” for processing and communication to the
MTC Server(s) and/or other MTC Device(s). Local communication between MTC Device(s) and other
entities is out of scope of this technical specification.
Machine-type communication (MTC) is a form of data communication which involves one or more
entities that do not necessarily need human interaction.
MTC Device: A MTC Device is a User Equipped (UE) for Machine Type Communication, which
communicates through a PLMN with MTC Server(s) and/or other MTC Device(s).
MTC Feature: MTC Features are network functions to optimise the network for use by M2M applications.
MTC Group: A MTC Group is a group of MTC Devices that share one or more MTC Features and that
belong to the same MTC Subscriber.
MTC Server: A MTC Server is a server, which communicates to the PLMN itself, and to MTC Devices
through the PLMN. The MTC Server can also have an interface which can be accessed by the MTC User.
The MTC Server can:

• Provides services for other servers (e.g. The MTC Server is a Services Capability Server for an
Application Server), and/or

• Provides services for applications and can host the application (e.g. The MTC Server is an
Application Server).
MTC User: A MTC User uses the service provided by the MTC Server.

MTC Subscriber: A MTC Subscriber is a legal entity having a contractual relationship with the network
operator to provide service to one or more MTC Devices.
 What does IEEE 802.11 mean?

IEEE 802.11 refers to the set of standards that define communication for wireless LANs (wireless local
area networks, or WLANs). The technology behind 802.11 is branded to consumers as Wi-Fi.

As the name implies, IEEE 802.11 is overseen by the IEEE, specifically the IEEE LAN/MAN Standards
Committee (IEEE 802). The current version of the standard is IEEE 802.11-2007.

IEEE 802.15

IEEE 802.15 is the IEEE working group for Wireless Personal Area Networks (WPANs). The working
group is developing standards for short- range communicatons of devices within a personal operating
space. A personal wireless network consists of mobile devices such as a handheld or pocket computer,
PDA, mobile phone and wireless microphone.

IEEE 802.15 consists of a number of working groups:

• 802.15.1(Standardization Task Group)

o Standardization of Bluetooth
• 802.15.2 (Recommended practice)
o Coexistence of WPAN and WLAN devices
• 802.15.3 (High Rate WPAN)
o High-rate (>20 Mbit/s) WPANs
o IEEE 802.15.3a is a standard for UWB devices
o IEEE 802.15.3c is a standard for gigabit wireless (> 2 Gbit/s) in the 60 GHz band
• 802.15.4 (Low Rate WPAN)
o Low-rate WPANs (up to 200 kbit/s)
o Standardization of ZigBee

NarrowBand-Internet of Things (NB-IoT)

NarrowBand-Internet of Things (NB-IoT) is a standards-based low power wide area (LPWA)
technology developed to enable a wide range of new IoT devices and services. NB-IoT
significantly improves the power consumption of user devices, system capacity and spectrum
efficiency, especially in deep coverage. Battery life of more than 10 years can be supported for a
wide range of use cases.
 MTIN 101

IoT ARCHITECTURE AND PROTOCOLS

======================================================================

Unit IV
IoT Transport & Session Layer Protocols: Transport Layer (TCP, MPTCP, UDP, DCCP, SCTP)-(TLS, DTLS) – Session
Layer-HTTP, CoAP, CoAP message types, CoAP Request-Response model, XMPP, AMQP, MQTT, MQTT methods
and components, MQTT communication, topics and applications, SMQTT.
-----------------------------------------------------------------
Transport layer which is also known as routing layer is responsible for routing of data packets over a network. At
this layer, ordering of packets, error detection and correction in delivery of data packets is performed. The
commonly used transport layer protocols include the following –

TCP – Transmission Control Protocol (TCP) is connection oriented and heavyweight protocol. It is suitable for
reliable communication because in this protocol acknowledgment is received when the client sends the packet to
the server via TCP protocol. The data must be guaranteed sent at the other end if the packet is sent via TCP
protocol.
The protocol operates in three phases – Connection establishment, data transfer and connection close. A TCP
connection is managed by an internet socket which lying at the end point (physical) undergoes various state
changes.
The packet overhead is very large in this protocol. TCP consumes more power from the devices and has large
overhead so it is not suitable for low power devices with constrained environment. Therefore, UDP is preferred as
a connection less protocol for low overhead.
UDP – User Datagram Protocol is a connection less protocol and is not reliable for guaranteed transmission of
data. However, the UDP protocol is a best protocol to send data to the server when packet loss during
transmission of the data can be afforded. UDP protocol is a lightweight protocol and is suitable for wireless sensor
network communication. UDP is often used in applications specially tuned for real-time performance.
DCCP – Datagram Congestion Control Protocol (DCCP) is a message-oriented transport layer protocol. This
protocol is more secure than TCP protocol. Compared to TCP which has a single byte long ID for each packet, the
packet ID is 48-bit long (6-bytes) in DCCP. This makes it hard for any attacker to hack data packets. This protocol is
generally used for time critical data transfers like media streaming and VoIP.
SCTP – Stream Control Transmission Protocol (SCTP) protocol is a message oriented transport layer protocol and it
uses congestion control to reliably transfer data over a network. The data transferred along with a 12-byte header
is secured using 4-way handshake. Due to multi-homing, data is reliably sent to the destination.

The Session Layer

The Session Layer manages connection between two endpoints of a network by controlling data between sender
and receiver where session layer protocols are responsible for actual transmission of data in IoT ecosystem. That’s
why these Session Layer protocols are called as IoT Messaging Protocols or sometimes referred as IoT Data
Protocols. Most of IoT applications use TCP and UDP for transport and these messaging protocols can operate
over TCP or UDP.
There are different types of messaging protocols that are present by different standardization organizations and
depending upon their implementations they are used. Below are some of popular IoT Messaging protocols used in
IoT eco-system.

MQTT (Message Queue Telemetry Transport)

MQTT (Message Queue Telemetry Transport) is a messaging protocol which was introduced by IBM in 1999. It
was initially built for monitoring sensor node and faraway tracking in IoT. Its suits are small, cheap, low-memory
and low-power devices. MQTT provides embedded connectivity between applications and middleware in one side
and another side it connects networks and communicators.

MQTT protocol is based on publish/subscribe architecture. The publish/subscribe architecture consists of three
major components: publishers, subscribers, and a broker. According to IoT point of view, publishers are lightweight
sensor devices that send their data to connected broker and goes back to sleep whenever possible. Subscribers are
applications, which are interested in a certain topic or sensory data, so they are connected to brokers to be
informed whenever new data are received. The broker receives the sensory data and filters them in different
topics and sends them to subscribers according to interest in the topics.

CoAP (Constrained Application Protocol) is a session layer protocol that provides the RESTful (HTTP) interface
between HTTP client and server. It is designed by IETF Constrained RESTful Environment (CoRE) working group. It is
designed to use devices on the same constrained network between devices and general nodes on the Internet.
CoAP enables low-power sensors to use RESTful services while meeting their low power constraints. This protocol
is specially built for IoT systems primarily based on HTTP protocols.

This network is used within the limited network or in a constrained environment. The whole architecture of CoAP
consists of CoAP client, CoAP server, REST CoAP proxy, and REST internet.
The data is sent from CoAP clients (such as smartphones, RFID sensors, etc.) to the CoAP server and the same
message is routed to REST CoAP proxy. The REST CoAP proxy interacts outside the CoAP environment and uploads
the data over REST internet.

DDS (Data Distribution Service) is a middleware (sometimes called machine-to-machine (M2M)) communication
protocol. It is implemented by the Object Management Group (OMG) standard for the real-time system with high
speed and high-performance, scalable, dependable, and interoperable data exchange. This communication
protocol is based on a publish-subscribe pattern for sending and receiving data, events, and commands among the
nodes.

The DDS protocol has two main layers:

Data-Centric Publish-Subscribe (DCPS): This layer delivers the information to subscribers.

Data-Local Reconstruction Layer (DLRL): This layer provides an interface to DCPS functionalities, permitting the
sharing of distributed data amongst IoT enabled objects.

Advanced Message Queuing Protocol (AMQP) :

AMQP is an open standard session layer protocol useful for sending transnational messages that’s why mainly
used in financial industry. It runs over TCP (Transmission Control Protocol) or UDP (User Datagram Protocol)
which is nearly similar to that of MQTT. But only difference is that Broker(Dealer) contains Exchange and
Queues as a result it is focused on not losing messages. The exchange receives messages from publishers and
distributes them to respective queues. Different subscribers collect topic wise sensory data from respective
topic queues.

Secure Message Queue Telemetry Transport (SMQTT) :

SMQTT works as an extension to MQTT protocol. It is based on an encryption messaging mechanism that’s why
it provides a secure messaging standard. In this protocol, subscriber sends encrypted messages to all nodes and
nodes receive encrypted message and use message after decryption. The encryption and decryption activities
are carried out by using master key.

This protocol follows four main stages i.e., Setup, Encryption, Publish, Decryption.
1. In Setup, both publisher and subscriber register themselves near broker and get master keys.
2. In the Encryption stage, broker encrypts published message.
3. In the Published stage, broker gives encrypted data to subscribers.
4. In the Decryption stage which is last stage, data /message is decrypted by subscriber using that master
key.

HTTP

HTTP stands for Hyper Text Transfer Protocol

WWW is about communication between web clients and servers

Communication between client computers and web servers is done by sending HTTP Requests and receiving HTTP
Responses
The World Wide Web is about communication between web clients and web servers.

Clients are often browsers (Chrome, Edge, Safari), but they can be any type of program or device.

Servers are most often computers in the cloud.

HTTP Request / Response

Communication between clients and servers is done by requests and responses:

1. A client (a browser) sends an HTTP request to the web

2. A web server receives the request
3. The server runs an application to process the request
4. The server returns an HTTP response (output) to the browser
5. The client (the browser) receives the response

The HTTP Request Circle

A typical HTTP request / response circle:

1. The browser requests an HTML page. The server returns an HTML file.
2. The browser requests a style sheet. The server returns a CSS file.
3. The browser requests an JPG image. The server returns a JPG file.
4. The browser requests JavaScript code. The server returns a JS file
5. The browser requests data. The server returns data (in XML or JSON).
 Unit 5 MTIN 101 IoT ARCHITECTURE AND PROTOCOLS

IoT Service Layer Protocols & Security Protocols: Service Layer –one M2M, ETSI M2M, OMA, BBF –
Security in IoT Protocols – MAC802.15.4 , 6LoWPAN, RPL, Application Layer ,IoT Platforms, Arduino,
Raspberry Pi Board, Other IoT Platforms; Data Analytics for IoT, Cloud for IoT, Cloud storage models
& communication APIs, IoT case studies
IoT Service Layer Protocols & Security Protocols: IoT service layer protocols and security protocols
can be categorized based on their functionality and purpose.
IoT Service Layer Protocols: IoT (Internet of Things) Service Layer Protocols refer to a set of
communication protocols and standards designed to facilitate interaction and data exchange between
various IoT devices, applications, and services. These protocols operate at the service layer of the IoT
architecture and play a crucial role in enabling seamless communication, interoperability, and
management of IoT devices and data. Here's an overview of key aspects related to IoT Service Layer
Protocols:
Purpose and Functions:
1. Interoperability: Service layer protocols aim to ensure interoperability among diverse IoT
devices and applications. They provide a standardized way for different devices, often from
various manufacturers, to communicate and work together.
2. Abstraction of Complexity: These protocols abstract the underlying complexity of the IoT
network and device communication, providing a common interface and set of functionalities that
developers can leverage.
3. Common Service Abstractions: Service layer protocols define common service abstractions,
such as data management, device discovery, security mechanisms, and application enablement.
This allows developers to create applications without needing to understand the intricacies of
each device's communication protocol.
Common IoT Service Layer Protocols:
1. MQTT (Message Queuing Telemetry Transport):
• Purpose: Lightweight and efficient messaging protocol suitable for low-bandwidth, high-latency,
or unreliable networks.
• Usage: Commonly used for real-time communication between IoT devices and applications,
especially in scenarios where low power and low data overhead are crucial.
2. CoAP (Constrained Application Protocol):
• Purpose: Designed for resource-constrained devices and networks, providing a lightweight
alternative to traditional HTTP for communication in IoT.
• Usage: Well-suited for applications where devices may have limited resources, such as in
industrial IoT or sensor networks.
3. oneM2M (One Machine-to-Machine):
• Purpose: A global standard that aims to provide a common service layer for M2M and IoT
applications, ensuring interoperability across diverse platforms.
 Unit 5 MTIN 101 IoT ARCHITECTURE AND PROTOCOLS

• Usage: Enables seamless communication and data exchange between devices and applications,
promoting a standardized approach to IoT deployments.
4. OMA (Open Mobile Alliance) Standards:
• Purpose: OMA develops various standards for mobile services, including those relevant to IoT.
Examples include Lightweight M2M (LwM2M) for device management and Smart Objects for
defining data models.
• Usage: Addresses specific needs in IoT ecosystems, offering solutions for device management,
data representation, and service enablement.
Key Characteristics:
1. Scalability: The protocols are designed to scale efficiently, supporting communication between a
large number of devices and applications within the IoT ecosystem.
2. Security: Security features are often embedded in these protocols, addressing authentication,
encryption, and secure data transfer to protect IoT devices and data from unauthorized access or
tampering.
3. Flexibility: Protocols are flexible to accommodate different types of IoT devices, communication
patterns, and application requirements.
4. Standards Compliance: Adherence to industry standards ensures that devices and applications
from different vendors can work together seamlessly, fostering interoperability.
IoT Service Layer Protocols form the foundation for effective communication and collaboration in
IoT ecosystems, providing a standardized and efficient means for devices and applications to interact
while addressing challenges related to interoperability and resource constraints.

The Broadband Forum (BBF): The Broadband Forum (BBF) is a consortium of approximately 200
member companies that work collaboratively to define broadband network specifications, management
systems, and various related technologies. Initially, the focus of BBF was on broadband access
technologies, but its scope has expanded to encompass multiple areas including home networking,
Internet of Things (IoT), cloud services, and more.
BBF and IoT:
Within the realm of the Internet of Things (IoT), the Broadband Forum has contributed in several ways:
1. TR-069 Protocol:
• BBF developed the TR-069 protocol, also known as the CPE WAN Management Protocol
(CWMP). While initially designed for remote management of Customer Premises Equipment
(CPE) by Internet Service Providers (ISPs), it has extended its functionality to manage IoT
devices as well.
• TR-069 offers a standardized and secure approach for remote management, provisioning, and
configuration of IoT devices, ensuring interoperability across various devices and networks.
 Unit 5 MTIN 101 IoT ARCHITECTURE AND PROTOCOLS

2. Interoperability and Standards:

• BBF has been involved in establishing standards and specifications that promote interoperability
among different IoT devices and platforms.
• It aims to create a standardized framework for IoT deployments, enabling seamless
communication and compatibility between devices from various manufacturers.
3. Home Automation and IoT Security:
• With a focus on home networking and connected devices, BBF works on defining standards for
home automation and IoT security within broadband environments.
• This includes developing best practices and protocols to ensure secure communication and data
protection in IoT devices connected via broadband networks.
4. Collaboration and Industry Engagement:
• BBF collaborates with other standardization bodies and industry groups to ensure alignment and
convergence of IoT-related standards and practices.
• By engaging with various stakeholders, BBF aims to drive innovation and development of IoT
technologies while emphasizing security and interoperability.
In summary, while BBF traditionally concentrated on broadband technologies, its involvement in
defining protocols like TR-069 and efforts in establishing interoperability standards for IoT devices
reflect its commitment to shaping the IoT landscape within broadband networks, addressing management,
security, and connectivity challenges.

IoT Security Protocols: IoT (Internet of Things) Security Protocols are a set of protocols and standards
designed to secure the communication, data, and interactions within IoT ecosystems. Given the
proliferation of IoT devices and the potential vulnerabilities associated with their deployment, ensuring
robust security is essential to protect against unauthorized access, data breaches, and various cyber
threats. Here's an overview of key aspects related to IoT Security Protocols:
Common IoT Security Protocols:

1. TLS (Transport Layer Security) and DTLS (Datagram Transport Layer Security):
• Purpose: Provide secure communication channels by encrypting data exchanged between IoT
devices and servers.
• Usage: Ensures confidentiality and integrity of data, preventing eavesdropping and tampering
during transmission.
2. OAuth (Open Authorization):
• Purpose: Enables secure authorization between IoT devices and services without sharing
sensitive credentials.
• Usage: Allows devices to access resources or services on behalf of a user with proper
authentication, enhancing security and user privacy.
 Unit 5 MTIN 101 IoT ARCHITECTURE AND PROTOCOLS

3. X.509 Certificates:
• Purpose: Defines a standard format for public key certificates, supporting authentication in IoT
environments.
• Usage: Certificates are used to verify the identity of devices and establish secure communication
channels, often employed in conjunction with TLS.
4. CoAP (Constrained Application Protocol) with DTLS/TLS:
• Purpose: Extends the CoAP protocol with DTLS/TLS for secure communication in resource-
constrained IoT devices.
• Usage: Ensures secure data exchange in environments where devices have limited processing
power and memory.
5. JWT (JSON Web Tokens):
• Purpose: Provides a compact, URL-safe means of representing claims to be transferred between
parties.
• Usage: Often used for secure authentication and authorization, especially in scenarios where
lightweight token-based authentication is preferred.
6. LwM2M (Lightweight M2M) Security:
• Purpose: LwM2M includes security mechanisms for device management in IoT, addressing
issues like authentication and secure firmware updates.
• Usage: Ensures the secure management of IoT devices, protecting against unauthorized access
and malicious activities.

Key Security Characteristics:

1. Authentication: Ensures that devices and users are who they claim to be, preventing
unauthorized access.
2. Authorization: Controls access to resources, ensuring that only authorized entities can perform
specific actions or access certain data.
3. Encryption: Protects data in transit by encrypting it, preventing eavesdropping and unauthorized
interception.
4. Integrity: Ensures the integrity of data, preventing unauthorized tampering or modification.
5. Secure Bootstrapping and Provisioning: Establishes a secure initial setup for devices, ensuring
they are configured and authenticated securely from the start.
6. Secure Device Lifecycle Management: Addresses security considerations throughout the entire
lifecycle of an IoT device, including provisioning, operation, and decommissioning.
7. Security Standards Compliance: Adherence to established security standards and best practices,
ensuring a consistent and well-understood security posture for IoT implementations.

Challenges and Considerations:

 Unit 5 MTIN 101 IoT ARCHITECTURE AND PROTOCOLS

1. Resource Constraints: Many IoT devices have limited resources (processing power, memory,
etc.), making it challenging to implement complex security measures.
2. Diversity of Devices: The vast diversity in IoT devices, ranging from sensors to actuators,
presents challenges in standardizing security protocols that can be universally applied.
3. Long Lifecycle: Some IoT devices may have long lifecycles, requiring robust security
mechanisms to remain effective over an extended period.

IoT Security Protocols are crucial for safeguarding IoT ecosystems against various cybersecurity
threats. They provide a foundation for secure communication, authentication, and data protection,
addressing the unique challenges posed by the diverse and interconnected nature of IoT devices.

Security in IoT Protocols – MAC 802.15.4 : The IEEE 802.15.4 standard is a set of specifications for
low-rate wireless personal area networks (LR-WPANs). This standard is commonly used in the Internet
of Things (IoT) for communication between low-power, low-cost devices. While IEEE 802.15.4 provides
a foundation for wireless communication in IoT, it does not explicitly define security mechanisms.
Instead, it leaves security considerations to be addressed by higher-layer protocols or additional
specifications.

Here are key aspects related to security in IoT protocols, particularly in the context of IEEE
802.15.4:

IEEE 802.15.4 Security Considerations:

1. MAC (Medium Access Control) Layer Security:

• Frame-Level Security: IEEE 802.15.4 allows for frame-level security through the use of frame
types that support encryption and integrity protection.
• Secure Communication: Devices using IEEE 802.15.4 can employ secure communication by
encrypting the payload and appending a frame integrity check sequence (FCS) to ensure data
integrity.
2. Link-Layer Security:
• Authentication: IEEE 802.15.4 provides the capability for devices to authenticate each other
using shared secrets.
• Key Management: Devices can employ key management mechanisms to establish and update
cryptographic keys used for encryption and integrity protection.
3. Use of Higher-Layer Protocols:
• Zigbee Security: Zigbee, a popular communication protocol built on IEEE 802.15.4, includes
additional security features. It defines how devices can securely join a network, handle key
establishment, and manage secure communication.
 Unit 5 MTIN 101 IoT ARCHITECTURE AND PROTOCOLS

• Thread Security: Thread, another IoT communication protocol, builds on IEEE 802.15.4 and
includes its security mechanisms for device authentication, secure communication, and network
key management.
4. Network Layer Security:
• IP Security (IPsec): In cases where IEEE 802.15.4 is used as the link layer for IPv6
communication, IPsec can be employed at the network layer for end-to-end security.

Challenges and Considerations:

1. Resource Constraints: Many IoT devices using IEEE 802.15.4 have limited resources, making it
challenging to implement complex security mechanisms. Efficient algorithms and lightweight
cryptographic protocols are crucial.
2. Key Management: Managing cryptographic keys for secure communication is critical.
Establishing a secure key management system for IoT devices, especially those with constrained
resources, is a challenge.
3. Interoperability: The lack of a standardized security approach in the base IEEE 802.15.4
standard can lead to interoperability challenges. Devices from different manufacturers might
implement security differently.
4. Adaptability to Application Needs: Security requirements vary across IoT applications. Some
applications might need strong encryption, while others may prioritize low-latency
communication. Security mechanisms should be adaptable to diverse application needs.

while IEEE 802.15.4 provides a foundation for low-rate wireless communication in IoT, security
is typically addressed by higher-layer protocols or additional specifications like Zigbee or Thread.
Implementing effective security in IoT devices using IEEE 802.15.4 involves considering resource
constraints, key management, and interoperability challenges.

Security in IoT Protocols – 6LoWPAN: 6LoWPAN (IPv6 over Low-Power Wireless Personal Area
Networks) is a protocol designed to enable the use of IPv6 communication over low-power, low-rate
wireless networks, such as those used in the Internet of Things (IoT). Security considerations in
6LoWPAN are crucial to protect the communication between devices, ensure data integrity, and prevent
unauthorized access.

Here are key aspects related to security in 6LoWPAN protocols:

6LoWPAN Security Features:

1. IPsec (Internet Protocol Security):

• Purpose: IPsec is a suite of protocols used to secure communication at the IP layer. It provides
mechanisms for authentication, integrity, and confidentiality.
 Unit 5 MTIN 101 IoT ARCHITECTURE AND PROTOCOLS

• Usage: In 6LoWPAN, IPsec can be employed to secure end-to-end communication between

devices, ensuring that data remains confidential and has not been tampered with during
transmission.
2. DTLS (Datagram Transport Layer Security):
• Purpose: DTLS is a lightweight version of TLS designed for datagram protocols. It provides
security for UDP-based communication, which is commonly used in IoT.
• Usage: DTLS can be applied in 6LoWPAN to secure communication between devices, providing
encryption and integrity protection for data exchanged over UDP.
3. Security Headers in 6LoWPAN:
• Header Compression Security: 6LoWPAN uses header compression techniques to reduce
overhead. Security headers may be added to protect compressed headers during transmission.
• Fragmentation and Reassembly Security: Security mechanisms must consider the potential
fragmentation of IPv6 packets in low-power networks, ensuring that fragments are appropriately
secured and reassembled.
4. Link-Layer Security:
• IEEE 802.15.4 Security: 6LoWPAN often operates over IEEE 802.15.4 wireless networks. IEEE
802.15.4 provides its security mechanisms, including encryption and authentication. 6LoWPAN
implementations can leverage these link-layer security features.
5. Key Management:
• Pre-Shared Keys (PSK): Devices in a 6LoWPAN network may use pre-shared keys for
authentication and key establishment. Ensuring secure key management is essential for
preventing unauthorized access.
6. Secure Neighbor Discovery (SEND):
• Purpose: SEND is an extension to IPv6 Neighbor Discovery that enhances the security of
neighbor discovery processes.
• Usage: In 6LoWPAN, SEND can be employed to secure neighbor discovery, preventing various
attacks related to address resolution and neighbor interactions.

Challenges and Considerations:

1. Resource Constraints:
• 6LoWPAN devices often have limited resources in terms of processing power, memory, and
energy. Implementing robust security mechanisms while considering these constraints is a
challenge.
2. Interoperability:
 Unit 5 MTIN 101 IoT ARCHITECTURE AND PROTOCOLS

• Ensuring interoperability between different 6LoWPAN implementations, especially when

security features are involved, is essential. Standardizing security protocols and practices aids in
achieving interoperability.
3. Application-Specific Security Requirements:
• Security requirements may vary across different IoT applications. Some applications might
prioritize confidentiality, while others may focus on integrity or authentication. Security
mechanisms in 6LoWPAN should be adaptable to diverse application needs.
4. Firmware Updates and Secure Bootstrapping:
• Securing the process of firmware updates and the initial bootstrapping of devices is crucial for
maintaining a secure IoT deployment.

6LoWPAN security involves the implementation of established security protocols such as IPsec
and DTLS, leveraging link-layer security features, and addressing challenges related to resource
constraints and interoperability. Security considerations are integral to the successful deployment of
6LoWPAN in IoT applications.

Security in IoT Protocols – RPL: RPL (Routing Protocol for Low-Power and Lossy Networks) is a
routing protocol designed for Low-Power and Lossy Networks (LLNs), which are common in the Internet
of Things (IoT). RPL plays a crucial role in enabling efficient and reliable communication between
devices with limited resources. Ensuring security in RPL is essential to protect the routing infrastructure,
prevent attacks, and maintain the integrity of data transmission.

Here are key aspects related to security in RPL:

RPL Security Features:

1. Authentication:
• Message Authentication Code (MAC): RPL supports the use of MAC for message
authentication. This helps ensure that the messages exchanged between nodes are from legitimate
sources and have not been tampered with during transit.
2. Link-Layer Security:
• IEEE 802.15.4 Security: RPL often operates over low-power wireless networks, and devices
may use the IEEE 802.15.4 link-layer security features, such as encryption and authentication, to
secure communication between nodes.
3. Secure Bootstrapping:
• Purpose: Secure bootstrapping ensures that a device joining the RPL network is authentic and
trustworthy.
• Usage: Devices may use secure bootstrapping mechanisms to authenticate themselves to the
network, preventing unauthorized nodes from participating in the routing infrastructure.
 Unit 5 MTIN 101 IoT ARCHITECTURE AND PROTOCOLS

4. Message Integrity:
• Hash Functions: RPL can use hash functions to ensure the integrity of routing messages. This
prevents malicious nodes from altering routing information and disrupting the network.
5. Key Management:
• Pre-Shared Keys (PSK): RPL networks may use pre-shared keys for authentication and key
establishment. Ensuring secure key management is essential for preventing unauthorized access
to the network.
6. Trust Models:
• Trusted Authorities: RPL can utilize trusted authorities to establish and distribute keys securely.
This involves entities that nodes in the network trust for key management and authentication.
7. Secure Neighbor Discovery:
• Purpose: Secure Neighbor Discovery (SEND) extensions can enhance the security of neighbor
discovery processes in RPL.
• Usage: SEND ensures that nodes can securely discover and authenticate their neighbors,
preventing various attacks related to address resolution and neighbor interactions.

Challenges and Considerations:

1. Resource Constraints:
• RPL operates in resource-constrained environments, and devices may have limited processing
power and memory. Implementing robust security measures while considering these constraints is
challenging.
2. Scalability:
• RPL networks can scale to include a large number of nodes. Ensuring that security mechanisms
scale efficiently is crucial for maintaining the security of the entire network.
3. Adaptability to Network Changes:
• RPL networks are dynamic, and the network topology may change frequently. Security
mechanisms should be adaptable to these changes and continue to provide protection against
attacks.
4. Interoperability:
• Ensuring interoperability between different implementations of RPL and across heterogeneous
IoT devices is essential for a secure and seamless deployment.
5. Secure Firmware Updates:
• Ensuring the security of firmware updates is crucial for preventing the injection of malicious code
into the network.

Security in RPL involves the implementation of authentication, message integrity, secure

bootstrapping, and other mechanisms to protect the routing infrastructure and maintain the integrity of
 Unit 5 MTIN 101 IoT ARCHITECTURE AND PROTOCOLS

communication in low-power and lossy networks typical in IoT deployments. Addressing resource
constraints and ensuring scalability and adaptability to network changes are key considerations in
securing RPL-based IoT networks.

Application Layer : The Application Layer in the context of IoT (Internet of Things) refers to the top
layer of the IoT architecture, where applications and services interact with the data generated by
connected devices. This layer plays a crucial role in extracting meaningful insights from the vast amount
of data produced by IoT devices and enabling various use cases.

Here are key aspects of the Application Layer in IoT:

Key Characteristics:

1. Data Processing and Analytics:

• The Application Layer is responsible for processing and analyzing the data collected from IoT
devices. This involves extracting valuable information, identifying patterns, and gaining insights
that can be used for decision-making.
2. Use Case-Specific Functionality:
• Different IoT applications have unique requirements. The Application Layer accommodates use
case-specific functionalities, allowing developers to create applications tailored to specific
industries or scenarios, such as smart homes, industrial automation, healthcare, and more.
3. Interoperability:
• Ensures interoperability between various devices, protocols, and platforms. The Application
Layer often uses standardized protocols and APIs (Application Programming Interfaces) to
enable seamless communication and integration between different IoT components.
4. User Interface and Experience:
• Provides a user interface that allows end-users or administrators to interact with and control IoT
devices. This may include web applications, mobile apps, dashboards, or other interfaces that
facilitate user engagement.
5. Security and Access Control:
• Implements security measures to protect the confidentiality, integrity, and availability of data.
This includes authentication mechanisms, encryption, access control, and secure communication
between devices and the application layer.
6. Device Management:
• Manages the lifecycle of IoT devices, including provisioning, configuration, firmware updates,
and decommissioning. This ensures that devices are properly maintained and remain secure over
time.
 Unit 5 MTIN 101 IoT ARCHITECTURE AND PROTOCOLS

7. Integration with Cloud Services:

• Many IoT applications leverage cloud services for data storage, analytics, and scalability. The
Application Layer facilitates the integration of IoT data with cloud-based services, enabling
efficient data management and processing.

Components:

1. Applications: Custom software applications developed for specific IoT use cases, ranging from
smart home automation to industrial control systems.
2. APIs (Application Programming Interfaces): APIs enable communication and data exchange
between different components within the Application Layer and may also allow integration with
external services.
3. Data Storage and Databases: Systems for storing and managing the vast amounts of data
generated by IoT devices. Databases are crucial for efficient data retrieval, analysis, and historical
tracking.
4. User Interfaces: Interfaces that allow end-users, administrators, or other applications to interact
with IoT devices and access data. This can include web-based dashboards, mobile applications, or
command-line interfaces.
5. Security Modules: Components responsible for implementing security measures, including
authentication, authorization, encryption, and secure communication protocols.
6. Device Management Systems: Systems that handle device provisioning, configuration,
monitoring, and maintenance. This ensures the proper functioning and security of IoT devices
throughout their lifecycle.

Examples of IoT Applications:

1. Smart Home Automation: Applications that allow users to control and monitor smart home
devices such as thermostats, lights, security cameras, and appliances.
2. Industrial IoT (IIoT): Applications for monitoring and controlling industrial processes,
optimizing operations, and ensuring the efficiency and safety of manufacturing facilities.
3. Healthcare Solutions: Applications for remote patient monitoring, health data analytics, and the
management of medical devices.
4. Smart Cities: Applications for urban planning, traffic management, waste management, and
other city services to enhance efficiency and sustainability.
5. Retail and Inventory Management: Applications that utilize IoT data for inventory tracking,
supply chain management, and improving the customer shopping experience.
 Unit 5 MTIN 101 IoT ARCHITECTURE AND PROTOCOLS

The Application Layer acts as the interface between the raw data generated by IoT devices and the
end-users or other systems that can benefit from that data. It enables the creation of diverse and
customized IoT applications to address a wide range of needs across different industries.

IoT Platforms, Arduino, Raspberry Pi Board, Other IoT Platforms; IoT platforms, Arduino, Raspberry
Pi, and other IoT development boards are essential components in building and prototyping Internet of
Things (IoT) applications. Each serves a specific purpose, and their choice depends on factors such as
project requirements, complexity, and the desired level of customization.

Here's an explanation of IoT platforms, Arduino, Raspberry Pi, and a mention of other IoT
platforms:
IoT Platforms: IoT platforms are software frameworks that provide a set of tools and services to
facilitate the development, deployment, and management of IoT applications. These platforms typically
include features like device management, data analytics, connectivity, security, and application
enablement. Some popular IoT platforms include:
1. AWS IoT: Amazon Web Services (AWS) IoT platform offers a comprehensive set of services for
IoT applications, including device management, security, and data analytics.
2. Microsoft Azure IoT: Microsoft Azure provides a robust IoT suite with services for device
management, data storage, and integration with other Azure services.
3. Google Cloud IoT: Google Cloud Platform (GCP) offers IoT services that include device
registry, data storage, and integration with other Google Cloud services.
4. IBM Watson IoT Platform: IBM's Watson IoT Platform provides tools for device management,
data analytics, and integration with IBM's AI and analytics services.

Arduino: Arduino is an open-source electronics platform that includes both hardware and software
components. Arduino boards are widely used for prototyping IoT projects, especially those with simpler
requirements.
Key features of Arduino include:
• Hardware: Arduino boards come in various models, each with specific capabilities. They are
equipped with input/output pins, analog-to-digital converters, and can connect to various sensors
and actuators.
• Programming Language: Arduino uses a simplified version of C++ for programming. The
Arduino IDE (Integrated Development Environment) provides an easy-to-use interface for
writing and uploading code to the Arduino board.
• Community Support: Arduino has a large and active community of users, making it easy to find
tutorials, libraries, and support for a wide range of projects.
 Unit 5 MTIN 101 IoT ARCHITECTURE AND PROTOCOLS

Raspberry Pi: Raspberry Pi is a series of small, affordable, single-board computers designed for
educational purposes and prototyping. While Arduino is more focused on hardware interaction, Raspberry
Pi is a full-fledged computer with an emphasis on software development.
Key features of Raspberry Pi include:
• Processor: Raspberry Pi boards are equipped with ARM-based processors, allowing them to run
a variety of operating systems, including Linux.
• Connectivity: Raspberry Pi boards have built-in Ethernet ports and support for Wi-Fi and
Bluetooth, providing versatile connectivity options.
• GPIO Pins: Like Arduino, Raspberry Pi has General-Purpose Input/Output (GPIO) pins for
connecting to sensors, actuators, and other electronic components.
• Programming Languages: Raspberry Pi supports a variety of programming languages,
including Python, Java, and C++, making it suitable for a wide range of applications.
Other IoT Platforms: Apart from Arduino and Raspberry Pi, there are various other IoT development
platforms catering to specific needs and use cases.
Some examples include:
1. ESP8266 and ESP32: These are popular low-cost Wi-Fi modules with embedded processors,
often used in IoT projects. They can be programmed using the Arduino IDE and provide built-in
Wi-Fi connectivity.
2. Particle IoT Platform: Particle offers a range of development boards and an IoT cloud platform,
making it easier to build and scale IoT solutions.
3. BeagleBone: BeagleBone is a single-board computer with more features than Raspberry Pi,
including multiple USB ports, HDMI output, and more. It's suitable for more complex projects.
4. NVIDIA Jetson: Designed for AI and machine learning applications, NVIDIA Jetson boards are
powerful single-board computers with GPU capabilities, ideal for edge computing in IoT.
Choosing the right IoT platform or development board depends on the specific requirements of the
project, including computing power, connectivity, and scalability needs. Each platform has its strengths,
and the choice often comes down to the specific use case and development preferences.
Data Analytics for IoT: Data analytics for IoT (Internet of Things) involves the use of advanced
techniques and tools to analyze the vast amount of data generated by IoT devices. The goal is to extract
valuable insights, detect patterns, and make informed decisions to optimize processes, enhance efficiency,
and improve overall system performance.

Here's an overview of data analytics for IoT:

 Unit 5 MTIN 101 IoT ARCHITECTURE AND PROTOCOLS

Key Components of Data Analytics for IoT:

1. Data Collection:
• Sensor Data: IoT devices generate data from various sensors. This can include environmental
data, health metrics, industrial sensor readings, and more.
• Device Logs: Information about device status, errors, and activities are collected to monitor
device performance.
2. Data Storage:
• Databases: Storing IoT data efficiently is crucial. Time-series databases are often used to handle
data points collected over time, allowing for easy retrieval and analysis.
• Data Warehouses: For more complex analytics and historical analysis, data warehouses may be
used to store and manage large volumes of IoT data.
3. Data Processing:
• Stream Processing: Real-time processing of streaming data is essential for immediate decision-
making. Technologies like Apache Kafka and Apache Flink are commonly used for stream
processing in IoT.
• Batch Processing: Historical data can be analyzed using batch processing frameworks like
Apache Spark or Hadoop.
4. Data Analysis Techniques:
• Descriptive Analytics: Describes what has happened, providing insights into historical data
patterns and trends.
• Predictive Analytics: Uses statistical models and machine learning algorithms to predict future
trends and events based on historical data.
• Prescriptive Analytics: Recommends actions to optimize processes and improve outcomes based
on analytical insights.

Challenges in Data Analytics for IoT:

1. Data Volume: IoT devices generate massive amounts of data. Handling and analyzing this
volume of data in real-time or near-real-time can be challenging.
2. Data Variety: IoT data comes in various formats and structures. Integrating and processing
heterogeneous data from different devices requires flexible data handling techniques.
3. Data Velocity: The speed at which IoT data is generated is often high, especially in real-time
applications. Analyzing data quickly to make timely decisions is a critical requirement.
4. Data Security: Security and privacy concerns are paramount. Ensuring the confidentiality
and integrity of IoT data throughout the analytics pipeline is essential.
5. Data Quality: Inaccuracies or inconsistencies in IoT data can lead to incorrect insights. Data
cleaning and quality assurance processes are necessary to ensure accurate analysis.
 Unit 5 MTIN 101 IoT ARCHITECTURE AND PROTOCOLS

Use Cases for Data Analytics in IoT:

1. Predictive Maintenance: Analyzing sensor data to predict when equipment or machinery is

likely to fail, allowing for proactive maintenance and minimizing downtime.
2. Supply Chain Optimization:Analyzing data from RFID tags, GPS trackers, and sensors to
optimize supply chain logistics, reduce delays, and enhance overall efficiency.
3. Healthcare Monitoring:Continuous monitoring of patient health through wearable devices,
analyzing data to detect anomalies and provide early warnings for potential health issues.
4. Smart Grid Management:Analyzing data from smart meters and grid sensors to optimize
energy distribution, reduce losses, and improve the overall reliability of the electrical grid.
5. Environmental Monitoring:Analyzing sensor data from environmental monitoring devices to
assess air quality, detect pollution sources, and support urban planning initiatives.

Tools and Technologies:

1. Machine Learning Libraries: Libraries like scikit-learn, TensorFlow, and PyTorch are used for
building machine learning models for predictive analytics.
2. Big Data Processing Frameworks: Apache Spark, Apache Flink, and Hadoop are commonly
used for processing and analyzing large volumes of IoT data.
3. Visualization Tools: Tools like Tableau, Power BI, and Grafana are used for creating dashboards
and visualizing analytical insights.
4. Time-Series Databases: InfluxDB, TimescaleDB, and OpenTSDB are examples of databases
specifically designed for handling time-series data in IoT applications.
5. Edge Analytics: Some analytics are performed directly on IoT devices or at the edge to reduce
latency. Edge computing platforms like AWS Greengrass or Azure IoT Edge facilitate edge
analytics.

Data analytics for IoT is a critical aspect of extracting value from the massive amounts of data
generated by interconnected devices. By leveraging advanced analytics techniques, organizations can gain
actionable insights, improve decision-making, and optimize processes in various domains.

Cloud for IoT : Cloud computing plays a pivotal role in the Internet of Things (IoT) ecosystem by
providing scalable and flexible infrastructure, storage, and services to handle the vast amount of data
generated by IoT devices. Cloud services for IoT enable data storage, processing, analysis, and
application development, facilitating the implementation and management of IoT solutions.

Here's an explanation of the role of the cloud in IoT:

Key Components of Cloud for IoT:

 Unit 5 MTIN 101 IoT ARCHITECTURE AND PROTOCOLS

1. Data Storage: Cloud platforms offer scalable and durable storage solutions to handle the large
volumes of data generated by IoT devices. Data can be stored in databases, object storage, or
specialized time-series databases tailored for IoT use cases.
2. Data Processing and Analytics: Cloud services provide robust tools and frameworks for
processing and analyzing IoT data. Batch processing and real-time stream processing capabilities
are available, allowing organizations to gain insights from the data in near real-time.
3. Edge Computing: Cloud platforms often extend their services to the edge of the network,
allowing some processing and analytics tasks to be performed closer to the IoT devices. This
reduces latency and bandwidth usage, making edge computing crucial for time-sensitive
applications.
4. Device Management: Cloud services enable centralized device management, allowing
organizations to provision, configure, monitor, and update IoT devices remotely. This includes
managing device identities, security credentials, and firmware updates.
5. Security Services: Cloud platforms provide a range of security services to protect IoT
deployments. This includes identity and access management, encryption, threat detection, and
monitoring to ensure the security and integrity of IoT data and communication.
6. Scalable Computing Resources: Cloud platforms offer scalable computing resources through
Infrastructure as a Service (IaaS) and Platform as a Service (PaaS) models. This allows
organizations to scale their IoT applications based on demand without the need for extensive
upfront infrastructure investments.
7. IoT Application Development: Cloud services often include tools and services for developing,
deploying, and managing IoT applications. This may involve using serverless computing,
containerization, or other application deployment models.
8. Integration with Other Services: Cloud platforms provide integration with various other
services, such as machine learning, artificial intelligence, data visualization, and business
intelligence tools. This enables organizations to derive more value from IoT data.

Benefits of Cloud for IoT:

1. Scalability: Cloud platforms provide the ability to scale resources up or down based on demand,
accommodating the varying workloads of IoT applications.
2. Cost-Efficiency: Organizations can leverage pay-as-you-go models, minimizing upfront
infrastructure costs and paying only for the resources they consume.
3. Global Reach: Cloud services are available in multiple geographic regions, allowing
organizations to deploy and manage IoT applications globally.
4. Rapid Deployment: Cloud services enable quick deployment of IoT solutions without the need
for extensive infrastructure setup, reducing time-to-market for new applications.
 Unit 5 MTIN 101 IoT ARCHITECTURE AND PROTOCOLS

5. Flexibility and Customization: Cloud platforms provide a wide range of services and tools,
allowing organizations to customize and tailor their IoT solutions to specific requirements.
6. Reliability and Redundancy: Cloud providers offer high levels of reliability and redundancy,
ensuring that IoT applications are available and resilient even in the face of hardware failures or
other disruptions.
7. Security and Compliance: Cloud platforms invest heavily in security measures, including
encryption, access controls, and compliance certifications, enhancing the overall security of IoT
deployments.

Popular Cloud Providers for IoT:

1. Amazon Web Services (AWS): AWS IoT Core, AWS IoT Analytics, and other related services.
2. Microsoft Azure: Azure IoT Hub, Azure IoT Central, and Azure IoT Edge.
3. Google Cloud Platform (GCP): Cloud IoT Core and related services.
4. IBM Cloud: IBM Watson IoT Platform and related services.
5. Oracle Cloud: Oracle IoT and Oracle IoT Cloud Service.

Choosing a cloud provider depends on factors such as specific service offerings, integration
capabilities, pricing models, and the existing technology stack of the organization.

the cloud is a fundamental enabler for IoT applications, providing a robust infrastructure and a
suite of services to handle data storage, processing, analytics, and application development. It allows
organizations to harness the power of IoT data efficiently and cost-effectively, driving innovation and
digital transformation across various industries.

Cloud storage models & communication APIs: Cloud storage models and communication APIs are
fundamental components of cloud computing, providing organizations with scalable and flexible
solutions for data storage and communication.

Here's an explanation of cloud storage models and communication APIs:

Cloud Storage Models:

Cloud storage models refer to the different approaches or services offered by cloud providers for
storing and managing data. The three primary cloud storage models are:
1. Object Storage:
• Description: Object storage is a scalable and flexible storage model that stores data as objects.
Each object consists of data, metadata, and a unique identifier. It is commonly used for
unstructured data such as images, videos, and documents.
• Key Characteristics:
 Objects are stored in a flat structure, organized in containers or buckets.
 Unit 5 MTIN 101 IoT ARCHITECTURE AND PROTOCOLS

 Suitable for large-scale data storage and retrieval.

 Offers high scalability, durability, and availability.
 Commonly used in scenarios requiring distributed and highly available storage.
2. File Storage:
• Description: File storage provides a hierarchical file system in the cloud, allowing users to organize
data into directories and files. It mimics traditional file systems and is suitable for structured and
semi-structured data.
• Key Characteristics:
 Offers a familiar file system structure with directories and files.
 Suitable for applications that require shared access to files among multiple users or systems.
 Often used in enterprise applications, content management systems, and collaborative environments.
3. Block Storage:
• Description: Block storage involves dividing data into fixed-sized blocks, each with its own address.
It is typically used for structured data and provides raw storage volumes that can be attached to virtual
machines.
• Key Characteristics:
 Provides raw storage volumes that can be mounted to a server or virtual machine.
 Offers high-performance storage suitable for database applications and transactional workloads.
 Enables more granular control over storage and allows users to manage data at the block level.

Communication APIs:

Communication APIs (Application Programming Interfaces) are interfaces that allow different software
applications to communicate and interact with each other. In the context of cloud computing and IoT,
communication APIs play a crucial role in facilitating data exchange, integration, and interaction between
applications, services, and devices. Some common types of communication APIs include:

1. RESTful APIs (Representational State Transfer):

• Description: RESTful APIs use HTTP methods (GET, POST, PUT, DELETE) to perform operations
on resources. They follow REST principles and are widely used for web services and cloud-based
applications.
• Key Characteristics:
 Stateless communication.
 Use of standard HTTP methods.
 Lightweight and scalable.
 Commonly used for web and mobile applications.
2. WebSocket API:
 Unit 5 MTIN 101 IoT ARCHITECTURE AND PROTOCOLS

• Description: WebSocket is a communication protocol that provides full-duplex communication

channels over a single, long-lived connection. It is suitable for real-time applications where low
latency is crucial.
• Key Characteristics:
 Bi-directional communication.
 Persistent connection for real-time updates.
 Reduced overhead compared to traditional HTTP polling.
 Ideal for applications requiring low-latency communication, such as chat applications and real-time
analytics.
3. MQTT (Message Queuing Telemetry Transport):
• Description: MQTT is a lightweight and efficient messaging protocol designed for low-bandwidth,
high-latency, or unreliable networks. It is commonly used in IoT for device-to-device and device-to-
cloud communication.
• Key Characteristics:
 Publish/subscribe model.
 Low bandwidth usage and overhead.
 Quality of Service (QoS) levels for message delivery assurance.
 Well-suited for IoT scenarios with resource-constrained devices.
• GraphQL API:
• Description: GraphQL is a query language and runtime for APIs that enables clients to request only
the data they need. It provides a flexible and efficient alternative to traditional REST APIs.
• Key Characteristics:
 Clients can specify the shape and structure of the data they need.
 Reduces over-fetching and under-fetching of data.
 Enables efficient data retrieval for clients.
 Suitable for applications with complex data requirements.

These storage models and communication APIs are integral to the architecture of modern cloud-
based applications, enabling efficient data storage, retrieval, and communication between various
components in the cloud and IoT ecosystems.

IoT case studies : IoT case studies provide real-world examples of how organizations leverage Internet
of Things (IoT) technologies to solve specific challenges, improve operations, and create new
opportunities. Here are a few IoT case studies across various industries:

1. Smart Agriculture: John Deere's Precision Farming

Challenge: Optimizing agricultural processes for increased efficiency and reduced resource usage.
 Unit 5 MTIN 101 IoT ARCHITECTURE AND PROTOCOLS

Solution: John Deere implemented precision farming using IoT technologies. Tractors and equipment are
equipped with sensors that collect data on soil conditions, weather, and crop health. This data is sent to
the cloud for analysis. Farmers receive insights and recommendations on optimal planting times,
irrigation schedules, and fertilizer application.

Impact: Increased crop yield, reduced resource usage, and improved overall farm productivity.

2. Smart Cities: Barcelona's Smart City Initiative

Challenge: Enhancing urban living by addressing challenges such as traffic congestion, waste
management, and energy consumption.

Solution: Barcelona implemented an extensive IoT network with sensors and smart infrastructure. Smart
parking meters provide real-time parking availability information, optimizing traffic flow. Waste bins
equipped with sensors alert authorities when they need emptying. Smart streetlights adjust brightness
based on foot traffic, and environmental sensors monitor air quality.

Impact: Reduced traffic congestion, efficient waste management, energy savings, and improved quality
of life for residents.

3. Healthcare: Philips Healthcare's Remote Patient Monitoring

Challenge: Providing better healthcare outcomes through continuous monitoring of patients with chronic
conditions.

Solution: Philips developed a remote patient monitoring system using IoT devices. Patients with chronic
conditions wear connected devices that monitor vital signs, such as heart rate and blood pressure, in real-
time. The data is transmitted to healthcare providers, allowing for early detection of potential issues and
timely interventions.

Impact: Improved patient outcomes, reduced hospital readmissions, and more proactive healthcare
management.

4. Manufacturing: General Electric's Brilliant Manufacturing

Challenge: Enhancing manufacturing processes for increased efficiency, reduced downtime, and
improved product quality.

Solution: General Electric implemented a Brilliant Manufacturing initiative leveraging IoT. Sensors are
placed on machines and equipment to collect data on performance and health. This data is analyzed in
real-time, allowing for predictive maintenance to prevent equipment failures. Machine learning
algorithms optimize production schedules, and data analytics improve overall efficiency.
 Unit 5 MTIN 101 IoT ARCHITECTURE AND PROTOCOLS

Impact: Reduced downtime, increased production efficiency, and improved product quality.

5. Retail: Amazon Go's Cashierless Stores

Challenge: Streamlining the retail shopping experience by eliminating checkout lines and improving
customer convenience.

Solution: Amazon Go stores use IoT technologies, including computer vision, sensors, and machine
learning. Customers enter the store, pick up items, and simply walk out. Cameras and sensors track the
items taken, and the customer's account is automatically charged.

Impact: Improved customer experience, reduced friction in the shopping process, and increased
efficiency in retail operations.

6. Energy: Enel's Smart Grids

Challenge: Enhancing the efficiency and reliability of energy distribution and consumption.

Solution: Enel implemented smart grids equipped with sensors and IoT devices to monitor energy
consumption, detect faults, and optimize distribution. IoT-enabled smart meters provide real-time data,
and automation helps balance the grid by adjusting energy distribution based on demand.

Impact: Improved energy efficiency, reduced power outages, and better integration of renewable energy
sources.

These IoT case studies illustrate how organizations across various industries are leveraging IoT
technologies to address specific challenges, drive innovation, and improve overall performance. Each
case study highlights the versatility and transformative potential of IoT in diverse contexts.