S.K.D.A.V. Govt.

Polytechnic, Rourkela Internet of Things (IoT)

Introduction to
IoT Networking

Made by Stella Kujur

 Key Terminologies
As the number of IoT-connected devices grows exponentially,
integrating existing devices, smart devices, and constrained
nodes into a unified framework becomes critical. To
understand IoT networking better, let’s explore essential
connectivity terminologies.
1. IoT LAN (Local Area Network)
Definition: A short to medium-range network (up to
hundreds of meters), often organization-wide, which may or
may not be connected to the Internet.
Purpose: To enable communication among devices within
a limited geographical area.
Example: Sensors in a factory production line
communicating via Wi-Fi to a central gateway.
Key Characteristics:
Connectivity can be achieved using technologies like Wi-Fi,
Zigbee, or Bluetooth.
Operates within a building or campus.
Architecture:
Nodes (L) represent connected devices in the IoT LAN.
Page 2
 Key Terminologies
2. IoT Node
Definition: Machines, things, or computers connected to other nodes within a Local Area Network (LAN). Some IoT nodes
may connect to the Internet via a Wide Area Network (WAN).
Example: A smart thermostat in a smart home setup is an IoT node communicating with other devices like a smart speaker.

3. IoT WAN (Wide Area Network)

Definition: A larger network connecting multiple LANs across geographical or organizational boundaries, often with
Internet access.
Purpose: Facilitates long-distance communication between IoT devices and cloud servers or centralized systems.
Example: Smart meters in different cities reporting to a centralized energy management system.
Key Characteristics:
Each LAN within the WAN has a unique identifier.
Supports technologies like LTE, LoRaWAN, or 5G for extended connectivity.
Architecture:
Includes gateways (connecting LANs to WAN) and devices with locally unique (LU) addresses.

4. IoT WAN Gateway

Definition: A router connecting IoT LANs to WANs or directly to the Internet.
Purpose: Facilitates packet forwarding between LAN and WAN layers using the Internet Protocol (IP).
Example: A home Wi-Fi router that allows smart devices to access cloud-based services.
Nodes communicate via proxies, which handle locally unique (LU) addresses to ensure smooth operations.

Page 3
 Key Terminologies
5. IoT Proxy
Definition: A network entity that performs active
application-layer functions, bridging communication
between IoT nodes and other entities (e.g., servers or
cloud systems).
Purpose: Enhances security, data aggregation, and
protocol translation.
Example: Proxy server that manages communication
between smart cameras and the cloud for data
storage.
Architecture:
Nodes communicate via proxies, which handle
locally unique (LU) addresses to ensure smooth
operations.

Conclusion
Understanding these core connectivity terminologies
is vital for IoT network design and implementation.
They form the foundation for selecting appropriate
communication technologies and ensuring seamless
integration across different IoT devices and systems.
Page 4
 Key Terminologies

Page 5
 Gateway Prefix Allotment
In IoT addressing, conserving the address space is crucial due to the massive number of connected devices. Each IoT device
requires a unique IP address to communicate effectively. Gateway prefix allotment provides a strategy for efficient address
allocation while ensuring scalability and minimizing wastage.
Key Concepts:
1. Locally Unique Addresses:
Nodes within the jurisdiction of a gateway are assigned addresses that are valid only within that gateway's domain.
Example: Consider a smart home setup. Devices like smart lights, thermostats, and security cameras connected to a home
gateway are assigned local addresses such as 192.168.1.X. These addresses are valid only within the home network.
2. Global Identification via Prefix: Gateways are assigned a unique network prefix to differentiate them globally.
Example: A home gateway might have the global prefix 2001:db8:abcd::/64 assigned to it by an Internet Service Provider
(ISP). All devices within that home network will have IP addresses starting with this prefix, e.g., 2001:db8:abcd::1.
3. Address Conservation:
Using local addresses that are unique only within the gateway's domain allows the same address ranges to be reused across
different domains.
Example: Two separate factories might use the same local address range (e.g., 10.0.0.X) for devices within their respective
networks. The gateways connecting these factories to the internet ensure no conflict occurs globally.
4. Communication via Gateways:
Devices in an IoT network communicate with the broader internet through gateways, which translate local addresses into
globally routable addresses.

Page 6
 Gateway Prefix Allotment
Key Concepts:
4. Communication via Gateways:
Example: In a smart city, streetlights in different neighborhoods might use local addresses within their respective domains.
Gateways in each neighborhood route data from the streetlights to a central monitoring system over the internet.
Advantages of Gateway Prefix Allotment:
Efficient Use of Address Space: By reusing local addresses within different domains, unnecessary wastage of unique IPs is
avoided.
Scalability: This approach supports the rapid growth of IoT networks without requiring a massive number of global IP
addresses.
Simplified Management: Gateways handle address translation and routing, making the system manageable and reducing
the complexity for individual devices.
Example to Reinforce Understanding:
Imagine an IoT network in a smart agricultural system:
Farm 1: Local devices (e.g., moisture sensors, weather stations) are assigned addresses like 10.1.0.X.
Farm 2: Devices in another farm also use local addresses like 10.1.0.X.
Gateways: Each farm has a gateway that assigns its devices a prefix (e.g., 2001:db8:farm1::/64 for Farm 1 and
2001:db8:farm2::/64 for Farm 2) for global communication.
This allows the central monitoring system to uniquely identify devices from each farm, even though their local addresses
are the same.

Page 7
 Gateway Prefix Allotment

Working of IoT Gateway :

1. Receives data from sensor network.
2. Performs Pre processing, filtering and cleaning on unfiltered data.
3. Transports into standard protocols for communication.
4. Sends data to cloud.

Page 8
 Gateway Prefix Allotment

Page 9
 Impact of Mobility on Addressing
The movement of IoT devices within a network has significant implications for addressing, especially when it comes to
maintaining stable and secure connections. Here's a summary of the key concepts and protocols mentioned:
IoT Addressing and Mobility: When IoT devices move, they might change their network prefix, which could disrupt
communication. To address this, IoT LANs use Unique Local Addresses (ULA) that remain stable even when the network
prefix of the IoT gateway changes. This ensures that the LAN’s internal addressing is not affected by the mobility of devices.
Gateway Prefix Changes: As IoT devices move, the IoT gateway's WAN address may change, but the IoT LAN’s addressing
stays the same. This is facilitated by the use of ULAs, which provide locally unique addresses that are independent of the
gateway's network prefix.
Remote Anchor Points: For IoT devices to remain connected despite changing prefixes, remote anchor points are used.
These anchor points help maintain consistent addresses by keeping the gateway's prefix stable. Protocols like Mobile IPv6
are used to anchor these prefixes, ensuring the devices' addresses remain unchanged.
Tunneling: When IoT nodes need to communicate directly with the Internet, tunneling is used. In this setup, nodes send
packets to a remote anchor point rather than routing them through the standard network. Protocols like IKEv2 are used for
tunneling, providing secure communication pathways.
Internet Connectivity and IoT LAN Intra-Connectivity: IoT gateways, with or without proxies, handle both Internet
connectivity and intra-LAN communication for IoT devices. These gateways receive upstream address prefixes using
protocols like DHCPv6.
Dynamic Host Configuration Protocol Version 6 (DHCPv6): This protocol is used to configure IPv6 addresses for devices in
the network. It is the IPv6 equivalent of DHCP for IPv4. DHCPv6 assigns IP addresses, prefixes, and other network
configuration data to IoT devices.

Page 10
 Impact of Mobility on Addressing
Stateless Address Autoconfiguration (SLAAC):
Once the upstream address prefixes are
obtained via DHCPv6, they are used by IoT
devices to self-configure their IPv6 addresses
using SLAAC. SLAAC allows devices to generate
their own IP addresses based on router
advertisements.
Dynamic Host Configuration Protocol for
Unique Local Addresses (ULA): In cases where
internal address stability is critical, ULAs are
used, ensuring that devices within the network
can maintain stable addresses. However, ULAs
cannot be used for communication with the
wider Internet, as they are not globally routable.
In summary, mobility in IoT networks is managed
by a combination of techniques like ULA
addressing, remote anchor points, tunneling, and
DHCPv6, ensuring stable connectivity for IoT
devices while accommodating changes in network
prefixes due to device movement.

Page 11
 Multihoming
Multihoming is the practice of connecting a host or network to multiple networks to enhance reliability, performance, or
reduce costs. Below are the different types of multihoming and how they are applied:

1. Host Multihoming: 2. Multihoming with Multiple Addresses:

Definition: A single host (device) is connected to Definition: A network connects to multiple providers
multiple networks. For instance, a mobile phone may and is assigned multiple address ranges—one for each
connect to both a Wi-Fi network and a 3G network provider. Hosts within the network are assigned
simultaneously, or a desktop computer may be addresses corresponding to each provider.
connected to both a home network and a VPN. Key Features:
Key Feature: The host is assigned multiple addresses, This approach is cheaper than classical
one for each network it's connected to. multihoming and does not require coordination
Example: A mobile device that switches between Wi- with the service providers.
Fi and cellular networks based on availability, ensuring Additional technology (like policy-based routing) is
continuous connectivity. needed for managing routing.
Example: A small office connecting to two ISPs, with
each host within the network receiving an address
from each provider to ensure redundancy and
performance.

Page 12
 Multihoming
3. Classical Multihoming:
Definition: A network connects to multiple service providers and uses a Provider Independent (PI) address range. The
network's edge routers communicate with the providers using a dynamic routing protocol like BGP (Border Gateway
Protocol), which announces the network's address range to all connected providers.
Key Features:
BGP is used to handle routing between the network and providers.
The routing tables are automatically updated if a link fails, with reconfiguration occurring transparently.
Challenges:
High costs due to the need for a public Autonomous System (AS) number and address space that is globally recognized.
Growth of global routing tables due to non-aggregated address space.
Example: A large enterprise network that connects to multiple ISPs to ensure uninterrupted service and load balancing.

Page 13
 Multihoming
Multihoming in IoT:
Challenges:
For small IoT LANs, multihoming can be difficult if address prefixes cannot be allocated to the network, and routing
between multiple addresses is needed.
In such cases, proxy-based approaches and gateway-based approaches are used.
Proxy-Based Approach:
In this approach, a proxy is used to manage multiple IP addresses, which are mapped to link-local addresses. This allows
the network to appear as a single entity to the outside world despite having multiple internal addresses.
Gateway-Based Approach:
A gateway is used to assign link-local addresses to IoT nodes. The gateway manages the IP addressing and routing,
ensuring communication between multihomed nodes.
Key Challenges in IoT Multihoming:
Properly handling source and destination addresses in multihomed environments.
Routing information must be dynamically updated to reflect changes in network topology.
Multihoming in IoT and general networking is a technique to improve network reliability and performance by connecting to
multiple providers or networks. Depending on the complexity of the network, different approaches (host multihoming, classical
multihoming, multihoming with multiple addresses) are applied. In IoT networks, proxy and gateway-based approaches help
manage the complexity of addressing and routing in multihomed scenarios. The main challenge is providing proper
addressing and routing for multihomed nodes, ensuring seamless communication across multiple networks.

Page 14
 Deviations from Regular Web
The comparison between communication networks in the Web and IoT highlights the differences and similarities across the
layers of the OSI reference model and the IoT stack. Here's a breakdown of the key points:
1. Sensing Layer (IoT) vs. Physical and Data Link Layers (OSI):
Sensing Layer in IoT: This layer is responsible for the physical sensing of the environment and gathering data through
sensors and devices.
Protocols in IoT:
IEEE 802.15.4 MAC (Medium Access Control): Defines how devices communicate in a network, including how to share
communication channels.
IEEE 802.15.4 PHY (Physical Layer): Specifies the physical medium (e.g., radio frequency) for communication.
Protocols in OSI: In the OSI model, the Physical Layer and Data Link Layer handle physical transmission of data, using
protocols like Ethernet, DSL, ISDN, Wireless LAN, and Wi-Fi.
2. Network Layer in IoT vs. Network Layer in OSI:
Network Layer in IoT: This layer is responsible for routing data across networks and ensuring reliable communication
between devices in the IoT ecosystem.
Protocols in IoT:
IPv6: The latest version of the Internet Protocol used to route data packets.
6LoWPAN (Low Power Wide Area Network): An adaptation layer that allows IPv6 to be used in low-power, low-
bandwidth IoT networks.
Protocols in OSI: The OSI Network Layer uses IPv4, IPv6, and IPSec for data transmission and security.

Page 15
 Deviations from Regular Web
3. Service Layer in IoT vs. Transport Layer in OSI:
Service Layer in IoT: Provides necessary services such as data transmission, security, and encryption between devices.
Protocols in IoT:
UDP (User Datagram Protocol): A connectionless, lightweight protocol often used for IoT applications.
DTLS (Datagram Transport Layer Security): Provides security for datagram-based communications, often used for
securing IoT data exchanges.
Protocols in OSI: The Transport Layer in the OSI model uses TCP (Transmission Control Protocol) and UDP for end-to-end
communication between hosts.

4. Interface Layer in IoT vs. Application Layer in OSI:

Interface Layer in IoT: Similar to the Application Layer in the OSI model, this layer handles application-specific tasks,
allowing IoT devices to interact with users and other systems.
Protocols in IoT and Web: The protocols used in this layer vary based on the specific IoT application, such as HTTP for web
applications or MQTT for lightweight messaging in IoT.

5. Key Differences in Protocols:

IoT Protocols: Designed for specific IoT use cases, including low power, low bandwidth, and real-time communication.
Protocols like 6LoWPAN, DTLS, and UDP are commonly used in IoT because they are lightweight and efficient for
constrained environments.
Web Protocols: In contrast, the Web stack typically uses TCP, HTTP, and IP protocols, which are designed for higher
bandwidth and more stable, large-scale communications.
Page 16
 Deviations from Regular Web
6. Management Component in IoT:
IoT Stack Management: Unlike the Web stack,
IoT networks require a management component
due to the large number of devices, networks,
and resources that need to be efficiently
managed.
Management Tasks: This includes tasks such as
device configuration, monitoring, and network
management to ensure proper operation,
security, and scalability of the IoT ecosystem.

Summary
While the IoT stack and the Web stack share many similarities in terms of layered structure (e.g., sensing layer vs. physical
and data link layers), they use different protocols suited for their respective environments. IoT networks, with their
emphasis on low power, low bandwidth, and real-time constraints, utilize specific protocols like 6LoWPAN, DTLS, and UDP.
Additionally, IoT systems incorporate a management layer to handle the complexity of large-scale deployments, which is
not as prominent in traditional Web networks.

Page 17
 loT Identification and Data Protocols
The Internet of Things (IoT) ecosystem consists of a wide range of communication protocols, each serving specific roles in the
infrastructure, identification, communication, discovery, and data management within IoT systems. These protocols enable
devices to connect, interact, and share information across networks. Here's a breakdown of key protocols in various IoT layers:
1. Infrastructure Layer:
6LoWPAN: A protocol designed to enable IPv6 communication over low-power and low-bandwidth networks (e.g., sensor
networks). It allows IPv6 packets to be transmitted efficiently over networks with small devices that have limited processing
and memory capabilities.
IPv4/IPv6: These are the fundamental Internet protocols for addressing and routing data across the Internet. IPv6 is
becoming more prevalent in IoT due to its larger address space, essential for the vast number of connected devices.
RPL (Routing Protocol for Low Power and Lossy Networks): A protocol designed for low-power IoT networks that have
intermittent or unreliable connections. It focuses on efficient routing and energy management.
2. Identification Layer:
EPC (Electronic Product Code): A system for identifying individual physical objects using unique identifiers, often applied
in asset tracking and supply chain management.
uCode: A unique identifier for objects, often used in radio-frequency identification (RFID) systems. It is typically used for
tracking items or devices.
IPv6: In IoT, IPv6 not only serves as the addressing protocol but also as a way to uniquely identify each device.
URIs (Uniform Resource Identifiers): A way to identify resources (e.g., devices, services) on the network.

Page 18
 loT Identification and Data Protocols
3. Communication/Transport Layer:
Wi-Fi: A widely used wireless networking technology for local area networks (LANs), enabling high-speed communication.
Bluetooth: A short-range wireless technology used for device-to-device communication in proximity. Bluetooth Low Energy
(BLE) is commonly used in IoT applications due to its low power consumption.
IPWAN (Internet Protocol Wide Area Network): A communication network that uses Internet Protocol (IP) to connect
devices over long distances, allowing IoT devices to communicate with servers and other devices over large geographic
areas.
4. Discovery Layer:
Physical Web: A protocol for enabling devices to discover nearby services via Bluetooth Low Energy (BLE) and URLs. It
allows users to interact with physical objects and services based on their location.
mDNS (Multicast DNS): A method of resolving domain names to IP addresses in local networks without requiring a
traditional DNS server. Often used in IoT to simplify device discovery on local networks.
DNS-SD (DNS Service Discovery): A method that allows devices to discover services (e.g., printers, file servers) on a network
using DNS.
5. Data Protocols Layer:
MQTT (Message Queuing Telemetry Transport): A lightweight messaging protocol designed for low-bandwidth, high-
latency networks. It is widely used in IoT for transmitting data between devices and servers.
CoAP (Constrained Application Protocol): A protocol designed for simple devices that need to communicate over the
Internet. It is especially suitable for low-power, resource-constrained environments.

Page 19
 loT Identification and Data Protocols
5. Data Protocols Layer:
AMQP (Advanced Message Queuing Protocol): A protocol for message-oriented middleware that supports reliable and
secure messaging, commonly used in IoT applications.
WebSocket: A communication protocol that enables full-duplex communication between devices and servers over a single,
long-lived connection. It's often used for real-time data exchanges.
Node: Refers to a device or object in an IoT network. Protocols for node communication like MQTT and CoAP help these
devices share information and perform actions.
6. Device Management Layer:
TR-069 (Technical Report 069): A protocol for remote management of networked devices, especially useful in IoT for
managing devices like routers, sensors, and other connected devices.
OMA-DM (Open Mobile Alliance Device Management): A protocol used to manage mobile and IoT devices remotely,
providing capabilities for configuration, monitoring, and software updates.
7. Semantic Layer:
JSON-LD (JSON for Linked Data): A lightweight data format used to represent linked data in JSON format. It's particularly
useful in IoT for representing and exchanging structured data that can be easily linked to other data sources.
Web Thing Model: A model for representing IoT devices and services on the web. It provides a standard way to describe
and interact with devices using RESTful APIs and the Web.
8. Multi-layer Frameworks:
Alljoyn: An open-source IoT platform that enables device-to-device communication and interoperability across different
manufacturers and platforms.
Page 20
 loT Identification and Data Protocols
8. Multi-layer Frameworks:
IoTivity: An open-source framework for enabling seamless IoT device communication. It supports multiple IoT protocols and
allows devices from different vendors to work together.
Weave: A communication protocol developed by Google for IoT devices to communicate directly with each other and the
cloud, with built-in security and encryption.
HomeKit: Apple’s IoT framework for connecting home devices, enabling secure and easy control of devices via the iPhone,
iPad, or Siri.
Protocols in IoT:
IPv6 vs. IPv4: IPv6 offers a much larger address space than IPv4, which is essential for the exponential growth of IoT
devices. IPv6 also enables more direct addressing of devices, which is beneficial for scalability in IoT networks.
MQTT, CoAP, and AMQP: These are the primary messaging protocols in IoT that provide communication between devices
and the cloud, each suited to different use cases (e.g., MQTT for low-latency, CoAP for constrained environments, AMQP for
more robust messaging systems).
Summary:
IoT ecosystems rely on a variety of communication protocols tailored to specific needs such as low-power, low-
bandwidth communication, security, device discovery, and management. Protocols like MQTT, CoAP, IPv6, and AMQP
are central to ensuring efficient communication in these environments. The IoT stack involves multiple layers, each using
specific protocols to address the different challenges posed by IoT deployments, from data transmission to device
management and semantic interoperability.

Page 21
Internet Protocol Version 4 (IPv4)

Overview
IPv4: Fourth revision of the Internet Protocol, widely used for data communication across networks.
Connectionless protocol for packet-switched networks like Ethernet.
Identifies devices via 32-bit addressing.
Configurable manually or automatically, based on the network type.

Page 22
Internet Protocol Version 4 (IPv4)
Key Features IPv4 Header Format
Best-Effort Delivery Model: Key fields in the IPv4 header:
No guarantee for delivery or duplicate avoidance Version: Specifies the Internet Protocol version (IPv4).
(handled by transport layers). IHL (Internet Header Length): Specifies header
Address Classes: length.
Class A: Subnet mask 255.0.0.0 or /8. DSCP (Differentiated Services Code Point): Indicates
Class B: Subnet mask 255.255.0.0 or /16. type of service.
Class C: Subnet mask 255.255.255.0 or /24. ECN (Explicit Congestion Notification): Reflects
Class D: Reserved for multicasting. network congestion status.
Class E: Reserved for future use.
Total Length: Total size of the IP packet (header +
Address Limitations: payload).
IPv4 can support 2³² (4.29 billion) addresses. Identification: Identifies fragments of the same packet.
IPv6 resolves this limitation with 2¹²⁸ addresses. Flags:
Current Usage: Indicates if fragmentation is allowed.
Internet is largely IPv4-based with limited IPv6 3 bits, where MSB is always 0.
adoption. Fragment Offset: Position of the fragment in the
IoT relies on workarounds like IPv4-to-IPv6 original packet.
translation, tunneling, and data relaying. Time to Live (TTL): Limits packet lifespan to avoid
looping; decremented at every hop.

Page 23
Internet Protocol Version 4 (IPv4)
Protocol: Specifies the next-layer protocol (e.g., ICMP = 1, TCP = 6, UDP = 17).
Header Checksum: Ensures error-free packet delivery.
Source Address: 32-bit IP address of the sender.
Destination Address: 32-bit IP address of the receiver.
Reliability Mechanisms
IPv4 emphasizes reliable transmission with fields for service type, length, identification, fragment offset, TTL, and checksum.
Comparison with IPv6
IPv6 overcomes IPv4 limitations with 128-bit addressing and enhanced scalability for modern applications, including IoT.

Page 24
Internet Protocol Version 6 (IPv6)

Overview
IPv6: Advanced version of IPv4, introduced by the Internet Engineering Task Force (IETF).
Major enhancement: IP addresses expanded from 32 bits (IPv4) to 128 bits, supporting extensive future Internet growth.
Compatible tools: Similar functionality as IPv4 (e.g., Ping) with improvements in efficiency, security, and mobility.

Page 25
Internet Protocol Version 6 (IPv6)
Key Features IPv6 Header Format
Massive Address Space: IPv6 header fields (simpler and more efficient than
IPv4 supports 2³² addresses (~4.29 billion). IPv4):
IPv6 supports 2¹²⁸ addresses (~340 undecillion), Version (4 bits): Indicates Internet Protocol version
addressing the exhaustion of IPv4 addresses. (IPv6 = 0110).
Auto-Configuration: Traffic Class (8 bits):
Facilitates automated device configuration, 6 MSBs: Type of service (QoS).
addressing IPv4 shortcomings. 2 LSBs: Explicit Congestion Notification (ECN).
Integrated Security & Mobility: Flow Label (20 bits):
IPv6 embeds security features (IPSec) and supports Identifies a flow of packets for real-time/streaming
better mobility for devices. data to ensure proper sequencing.
Simpler Header Structure: Payload Length (16 bits):
Focuses on addressing rather than reliability, Specifies size of the payload (up to 65,535 bytes).
reducing header processing overhead. Can exceed this limit if Hop-by-Hop Extension
No Backward Compatibility: Header is included.
IPv4 and IPv6 are not directly compatible, Next Header (8 bits):
necessitating dual-stack solutions or transition Indicates the type of Extension Header or Upper
technologies like tunneling. Layer Protocol Data Unit (PDU) (e.g., TCP, UDP).

Page 26
Internet Protocol Version 6 (IPv6)
Hop Limit (8 bits):
Prevents infinite looping (similar to TTL in IPv4).
Decrements by 1 at each hop; discarded when it reaches 0.
Source Address (128 bits): Address of the packet's originator.
Destination Address (128 bits): Address of the intended recipient.
Advantages of IPv6 Over IPv4
Larger Address Space: Virtually eliminates the risk of IP address exhaustion.
Improved Routing Efficiency: Simplified header improves router processing speed.
Better Support for IoT: Scalability supports billions of interconnected devices.
Built-in Security: IPSec mandatory in IPv6 ensures encrypted communication.
Enhanced Mobility: Seamless handoffs between networks for mobile devices.
Challenges in IPv6 Adoption
Incompatibility with IPv4: Requires transition technologies (e.g., dual stack, tunneling).
Slow Transition: Businesses and ISPs are hesitant to migrate due to infrastructure costs.
Interoperability Issues: Ensuring seamless IPv4/IPv6 coexistence without disrupting users.
Key Takeaways
IPv6 provides a long-term solution to address the growing demand for IP addresses.
Its enhancements in efficiency, scalability, and security are critical for supporting IoT and future Internet growth.
Despite its benefits, global adoption remains slow, primarily due to the challenges of transitioning from IPv4.

Page 27
MQTT (Message Queuing Telemetry Transport)

Overview
MQTT is an ISO standard (ISO/IEC PRF 20922) lightweight messaging protocol.
Operates on a publish-subscribe architecture, suitable for low-bandwidth, high-latency, or unreliable networks.
Works on top of the TCP/IP protocol stack for reliable communication.
Introduced by IBM in 1999, standardized by OASIS in 2013.
Applications include IoT devices, embedded systems, and machine-to-machine (M2M) communication.

Page 28
MQTT (Message Queuing Telemetry Transport)
Core Components Methods in MQTT (Verbs)
Publishers: Connect: Establishes a connection between the MQTT
Lightweight devices (e.g., sensors) that generate client and broker.
data and publish it to a topic. Disconnect: Terminates the TCP/IP session after
Subscribers: completing pending work.
Applications or devices that subscribe to specific Subscribe: Requests the broker to allow the client to
topics to receive relevant data. subscribe to one or more topics.

Broker: Unsubscribe: Requests the broker to remove the

The central communication point responsible for: client’s subscription to one or more topics.
Receiving messages from publishers. Publish: Sends messages from publishers to the
Filtering messages based on topics. broker to be distributed to subscribers.
Dispatching messages to appropriate
subscribers.
Handles message buffering if clients are
temporarily offline.

Page 29
MQTT (Message Queuing Telemetry Transport)
Working of MQTT Applications of MQTT
1. Publish-Subscribe Model: IoT (Internet of Things):
MQTT operates on an event-driven architecture. Smart homes, industrial automation,
Publishers send data to the broker with a topic (e.g., wearables, etc.
home/living-room/temperature).
M2M Communication:
Subscribers register for topics, and the broker ensures Machine communication for real-time
messages are delivered to them. data processing.
2. Topic Hierarchy:
Home Automation:
Topics are structured as simple strings with hierarchical levels
MQTT plugins for platforms like Raspberry
separated by a slash (/). Pi (e.g., Node.js-based frameworks).
Example topic: home/kitchen/humidity.
Cybersecurity Solutions:
Wildcards (+, #) can be used for flexible subscription:
Platforms like McAfee Open DXL use
home/+/temperature: Matches all rooms' temperature data.
MQTT for advanced features like
home/#: Matches all data under home. request/response messaging.
3. Message Delivery:
The broker pushes messages to subscribers, unlike HTTP’s pull-
based model.
Maintains an open TCP connection between the client and
broker.
If a connection is interrupted, the broker buffers messages until
the client reconnects.
Page 30
MQTT (Message Queuing Telemetry Transport)
Advantages of MQTT
Lightweight Protocol: Ideal for resource-constrained devices
and low-bandwidth networks.
Scalable: Decouples data producers (publishers) and
consumers (subscribers).
Reliable Delivery:
Supports three levels of Quality of Service (QoS):
i. QoS 0: At most once delivery.
ii. QoS 1: At least once delivery.
iii. QoS 2: Exactly once delivery.
Flexibility: Wide adoption across programming languages (C,
Java, Python, JavaScript, etc.).
Offline Support: Message buffering ensures reliable
communication even during client disconnections.

Key Takeaways
MQTT provides a robust, scalable, and efficient messaging protocol for IoT and embedded systems.
Its lightweight nature, combined with the publish-subscribe model, makes it highly suitable for modern applications
requiring real-time communication over constrained networks.
The ability to integrate with a variety of programming languages and frameworks ensures broad usability in diverse
scenarios.
Page 31
CoAP Architecture (Constrained Application Protocol)
Overview
CoAP is a lightweight protocol designed for resource-constrained devices,
typically used in IoT (Internet of Things) applications. Its architecture is built to
support reliable communication and efficient resource utilization over the
UDP protocol.
Layers in CoAP Architecture
Application Layer:
Interacts with user applications and provides methods (GET, PUT,
POST, DELETE) for resource management.
Request/Response Layer:
Handles communication between the client and server.
Defines messaging patterns like piggyback and separate messaging.
Messaging Layer:
Ensures reliability and detects duplicate messages.
Implements message types like Confirmable (CON) and Non-
confirmable (NON).
UDP Layer:
Serves as the transport protocol for CoAP.
Ensures lightweight communication suitable for constrained devices.

Page 32
CoAP Architecture (Constrained Application Protocol)

Messaging Modes in CoAP

CoAP supports four messaging modes to ensure communication between clients and servers:
Confirmable (CON):
Reliable transmission.
The client resends the message until it receives an acknowledgment (ACK) with the same message ID.
If the recipient cannot process the message, it responds with a Reset (RST) message.

Page 33
CoAP Architecture (Constrained Application Protocol)
Messaging Modes in CoAP
Non-confirmable (NON):
Unreliable transmission.
The client sends a message without waiting for an acknowledgment.
A message ID is included for tracking and supervising retransmissions.
If the server fails to process the message, it replies with an RST.
Piggyback Messaging:
Used for direct client-server communication.
The client sends a request, and the server responds immediately with an acknowledgment (ACK) that contains the
response message.
Successful Response: ACK contains the response message identified by a token.
Failure Response: ACK contains a failure response code.
Separate Messaging:
Used when the server cannot respond immediately to the client’s request.
Workflow:
The client sends a request using a CON message.
The server sends an empty ACK to confirm receipt of the request.
The server waits for a specified interval to process the request and then sends the response as a new CON message.
The client replies with a confirmable acknowledgment.

Page 34
CoAP Architecture (Constrained Application Protocol)
Key Features of CoAP Messaging
Reliability:
Confirmable messages ensure reliability with acknowledgment and retransmission mechanisms.
Lightweight Communication:
CoAP is optimized for devices with limited computational power and bandwidth, relying on UDP rather than TCP.
Token Identification:
Each request and response pair is identified by a token, enabling stateful communication.
CoAP Methods
Similar to HTTP, CoAP defines four methods for resource management:
→GET: Retrieves the resource representation. →PUT: Updates an existing resource.
→POST: Creates or updates a resource. →DELETE: Removes a resource.
Applications of CoAP
IoT Systems: Communication between constrained devices like sensors and actuators.
Smart Homes: Managing appliances, security systems, and environmental monitoring.
Industrial Automation: Lightweight, reliable communication in resource-constrained environments.
Conclusion
CoAP is an efficient and lightweight protocol tailored for IoT applications. By leveraging its four-layer architecture and versatile
messaging modes, it ensures reliable communication with minimal resource overhead. Its design principles, derived from
HTTP, allow seamless integration with existing web protocols while optimizing for constrained devices.

Page 35
Secure MQTT (SMQTT)
Overview
SMQTT (Secure Message Queue Telemetry Transport) is an extension of the standard MQTT protocol. It introduces lightweight
attribute-based encryption to enhance the security of MQTT. SMQTT operates at the session layer of the OSI model and is
designed for secure communication in IoT and other resource-constrained environments.
Key Features of SMQTT
Lightweight Encryption:
Uses lightweight encryption to secure messages.
Ensures low computational overhead, making it ideal for constrained devices.
Broadcast Encryption:
A single message can be encrypted and securely delivered to multiple nodes simultaneously.
Reduces redundancy in encryption and decryption processes.
Broker-Based Architecture:
Similar to MQTT, SMQTT follows a publish-subscribe architecture with a central broker responsible for message delivery.
Enhanced Security:
Provides an additional layer of security by encrypting data before publishing.
Focuses on mitigating vulnerabilities present in the standard MQTT protocol.

Page 36
Secure MQTT (SMQTT)
Phases of the SMQTT Algorithm
1. Setup Phase:
Subscribers and publishers register themselves with the central broker.
The broker provides each participant with a master secret key to be used for encryption and decryption.
2. Encryption Phase:
Before publishing, data is encrypted by the publisher using an encryption algorithm.
The encryption algorithm and key generation process are customizable and depend on the developers.
3. Publish Phase:
The encrypted data is sent to the broker.
The broker broadcasts the encrypted message to all subscribed clients.
4. Decryption Phase:
Subscribers receive the encrypted message.
They use the master secret key to decrypt and decode the message.
Customization in SMQTT
Key Generation:
The process of generating the master secret key is not standardized in SMQTT.
Developers have the flexibility to design their own key generation algorithms based on specific use cases.
Encryption Algorithms:
SMQTT does not prescribe a specific encryption algorithm.
Developers can choose algorithms such as AES, RSA, or other lightweight encryption techniques depending on the
application's security and performance requirements.
Page 37
Secure MQTT (SMQTT)
Benefits of SMQTT
1. Enhanced Security:
Encrypting messages ensures secure communication, even in untrusted networks.
2. Efficient Data Sharing:
The broadcast encryption feature allows a single encrypted message to be securely delivered to multiple clients,
improving efficiency.
3. Flexibility:
Developers can customize encryption and key generation methods to suit specific needs.
4. Compatibility:
Retains the publish-subscribe architecture of MQTT, allowing seamless integration with existing MQTT systems.
Applications of SMQTT
IoT Security: Protects sensitive data in smart home devices, industrial IoT systems, and healthcare IoT applications.
Resource-Constrained Environments: Lightweight encryption ensures efficient performance on devices with limited
computational power.
Secure Communication: Ideal for environments requiring high levels of data confidentiality and integrity.
Conclusion
SMQTT enhances the security features of MQTT by introducing encryption mechanisms that are lightweight and efficient. Its
broadcast encryption capability makes it particularly suited for IoT applications, where secure and scalable communication is
critical. By enabling customizable encryption and key management, SMQTT provides a flexible yet robust framework for secure
message exchange.

Page 38
Extensible Messaging and Presence Protocol (XMPP)
Overview
XMPP (Extensible Messaging and Presence Protocol) is a real-
time communication protocol built on XML (Extensible Markup
Language). It supports the exchange of structured, extensible
data between network entities, enabling applications like instant
messaging, VoIP signaling, file transfer, gaming, IoT
communication, and social networking.
XMPP is an open standard that allows anyone to implement and
interoperate across various platforms. Its decentralized and
extensible nature makes it suitable for cloud computing, IoT, and
machine-to-machine (M2M) communications.

Architecture
Client-Server Model:
Communication happens through XMPP servers that facilitate message routing and service discovery.
The architecture is decentralized, allowing individuals and organizations to host their own servers, similar to email
systems.
Core Components:
Clients: End-user devices or applications using XMPP libraries for communication.
Servers: Intermediaries that route messages between clients and manage service discovery.
Extensions: Custom protocols or features added to the core XMPP standards for specific use cases.

Page 39
Extensible Messaging and Presence Protocol (XMPP)
Key Features of XMPP
1. Proven Technology:
XMPP was first developed by Jeremie Miller in 1998 (as Jabber) and has matured over time.
Widely adopted globally, with millions of users leveraging XMPP for real-time communication.
2. Decentralization:
No central server is required, enabling individuals and organizations to control their communication infrastructure.
Similar to email, it allows a fully decentralized communication network.
3. Open Standards:
XMPP protocols are free, public, and open for anyone to implement.
Core specifications have been formalized by the IETF in RFC 6120, RFC 6121, and RFC 7622.
4. Security:
Supports robust authentication and encryption mechanisms such as SASL and TLS for secure communication.
XMPP servers can be isolated on private networks for added security.
Developers are actively working on end-to-end encryption solutions.
5. Flexibility:
Beyond instant messaging, XMPP can be used for network management, content syndication, file sharing, gaming,
remote monitoring, and more.
Facilitates seamless interoperability across diverse networks and devices
6. Extensibility:
XMPP leverages XML to allow custom functionality while maintaining compatibility.
a. Extensions are documented in the XEP (XMPP Extension Protocol) series, though private extensions are also supported.
7. Diversity:
Widely used by companies and open-source projects for building real-time applications.
Avoids vendor lock-in, ensuring flexibility in deployments.
Page 40
Extensible Messaging and Presence Protocol (XMPP)
Core XMPP Technologies
1. Core XML Streaming: Enables real-time communication through XML data streams.
2. Jingle: A protocol for multimedia signaling, supporting voice, video, and file transfer applications.
3. Multi-User Chat (MUC): Provides flexible communication for group chats.
4. Publish-Subscribe (PubSub): Enables alerts, notifications, and rich presence data for syndication.
5. BOSH: HTTP binding for XMPP, allowing real-time communication over web protocols.

Applications of XMPP
1. Instant Messaging: Used in public services like Google Talk and private organizational deployments.
2. IoT and Smart Grid: Supports machine-to-machine communication and smart grid applications.
3. VoIP and Video: Facilitates signaling for voice and video communication through protocols like Jingle.
4. Gaming: Provides real-time communication for multiplayer gaming platforms.
5. File Sharing: Enables secure and efficient file transfer between clients.
6. Cloud Computing: Facilitates service discovery and presence information in cloud environments.
Advantages of XMPP
1. Interoperability: Ensures seamless communication between different devices and platforms.
2. Security: Built-in authentication and encryption mechanisms enhance security.
3. Scalability: Supports millions of users and can be scaled for large deployments.
4. Cost-Effective: Being open-source, it eliminates licensing costs and royalty fees.
5. Customizable: Extensible protocol allows for the creation of tailored solutions for specific applications.
XMPP is a versatile, secure, and extensible protocol for real-time communication across diverse applications. Its open-standard
nature and decentralized architecture make it a popular choice for IoT, cloud computing, and instant messaging services. By
leveraging its extensibility, organizations can build custom solutions while ensuring interoperability and scalability.
Page 41
AMQP Architecture and Applications
Overview of AMQP (Advanced Message Queuing Protocol)
AMQP is a protocol designed for reliable message-oriented
communication. It connects systems, feeds business processes with the
information they require, and reliably transmits instructions to achieve
organizational goals. AMQP is widely used for message queuing, routing,
and task delegation, enabling seamless communication across
technologies, time zones, and organizations.
Architecture of AMQP
The AMQP architecture consists of producers, exchanges, brokers,
queues, and consumers, as shown in Figure 2.16 (hypothetical). Below are
the primary components:
Producers (P):
Clients that create and publish messages to the exchange.
Exchanges (X):
Responsible for processing and routing incoming messages to appropriate queues based on routing mechanisms.
Types of exchanges include Direct, Fan-out, Topic, and Headers (explained below).
Brokers:
Intermediary systems that manage exchanges and queues. They receive messages, process them, and forward them to
designated queues.

Page 42
AMQP Architecture and Applications
Queues:
Message storage units where messages are held until they are consumed by client applications.
Separate queues are created for different business processes.
Consumers (C):
Applications or clients that retrieve messages from queues for processing.
Bindings:
Rules that govern message routing and distribution. These determine who can access messages and their destinations.
Types of Exchanges in AMQP
Direct Exchange:
Routes messages to queues based on routing keys.
Example: Distributing tasks in a round-robin fashion among workers.
Use case: Load balancing tasks.
Fan-out Exchange:
Ignores routing keys and delivers messages to all bound queues.
Use case: Sending notifications, updates, or broadcasting chat messages.
Topic Exchange:
Uses routing keys and patterns for publish-subscribe (pub/sub) systems.
Allows specialized consumer involvement, distributing messages based on keys and patterns.
Use case: Event-driven systems, such as triggering specific actions based on message content.

Page 43
AMQP Architecture and Applications
Offline Data Fetching: Enables clients to retrieve data asynchronously when they are back online.
Asynchronous Functionality: Provides fully asynchronous communication for distributed systems.
Reliability and Uptime: Ensures reliable message delivery and improves the uptime of application deployments.

Conclusion
AMQP is a powerful, reliable, and flexible messaging protocol that supports various message-routing patterns and
asynchronous communication. With its advanced queuing mechanisms and exchange types, AMQP is ideal for
distributed systems requiring seamless communication and high reliability. Its applications span across IoT, cloud
computing, task automation, and real-time monitoring systems.

Page 44
 Thank You.
Thank You.
Thank You.

Page 45