Things in IoT

Physical Design

IoT Protocols

Design of IOT
IoT Functional Blocks

Logical Design IoT Communication Model

IoT Communication APIs

Things in IOT

• Refers to IOT devices which have unique

identities that can perform sensing,
actuating and monitoring capabilities.

• An IOT device may consist of several

interfaces for connections to other
devices, both wired and wireless.
a) I/O interfaces for sensors
b) Interfaces for internet connectivity
c) Memory and storage interfaces
d) Audio/video interfaces

• IOT devices can exchange data with other connected devices or collect data from other devices and process the
data either locally or send the data to centralized servers or cloud – based application back-ends for processing
the data.
IOT Protocols
1. Link Layer
(Ethernet)
Sl.No. Standard Shared medium
• Ethernet is a type of computer network
1 802.3 Coaxial Cable…10BASE5
technology that are use to connect devices to
2 802.3.i Copper Twisted pair …..10BASE-T
form a local area network.
3 802.3.j Fibre Optic……10BASE-F
• Data Rates are provided from 10Gbit/s to 40Gb/s
4 802.3.ae Fibre Optic…..10Gbits/s
and higher
(WiFi)
Sl.No. Standard Shared medium
• A WiFi connection transmits data via wireless
1 802.11a 5 GHz band
signals providing greater mobility for users who
2 802.11b & 802.11g 2.4GHz band
can connect to a network.
3 802.11.n 2.4/5 GHz bands
• It’s a collection of Wireless LAN and provides
4 802.11.ac 5GHz band
Data Rates from 1Mb/s to 6.75 Gb/s
5 802.11.ad 60Hz band
(WiMax)
• WiMax stands for Worldwide Interoperability for Sr.No Standard Shared medium
Microwave Access. 1 802.16m 100Mb/s for mobile stations 1Gb/s for
• It’s a collection of Wireless Broadband standards fixed stations
that provides Data Rates from 1.5Mb/s to 1
Gb/s.
(LR-WPAN)
• Collection of standards for low-rate wireless personal area
networks.
• Basis for high level communication protocols such as Zigbee.
• Data Rates from 40Kb/s to 250Kb/s
• Provide low-cost and low-speed communication for power
constrained devices.

(2G/3G/4G/5G)
• These are Mobile Communication technologies which can Sl.No. Standard Shared medium
provide Data Rates from 9.6Kb/s (for 2G) to up to 100Mb/s 1 2G GSM-CDMA
(for 4G). 2 3G UMTS and CDMA 2000
• 5G has a theoretical peak data rate of 20 gigabits per 3 4G LTE
second (Gbps). However, real-world speeds are usually
between 100 Mbps and 3 Gbps. GSM - Global System for Mobile Communications
CDMA - Code-Division Multiple Access
UMTS - Universal Mobile Telecommunications System
LTE - Long Term Evolution
2. Network/Internet Layer
• Responsible for sending of IP datagram's from source to destination network
• Performs the host addressing and packet routing
• Host identification is done using hierarchical IP addressing schemes such as IPV4 or IPV6

(IPv4) (IPv6)
• 32-bit, leads to address exhaustion. • 128-bit, solves address exhaustion.
• Relies on external measures for security and Less • Integrates IPsec for enhanced security and More
scalable due to address limitations. scalable, accommodating IoT growth.

• Widely used in IoT for existing infrastructure but • Allows more direct connections without NAT as it
dependent on NAT due to limited address space. removes need for NAT, simplifies configuration.
• May require complex designs for IoT. • Simplifies designs with more addresses.

(6LoWPAN)
• IPV6 over Low power Wireless Personal Area Network, Operates in 2.4 Ghz with a Data Rates of 250Kb/s .
• allows small, low-power devices to communicate with wireless networks via the IPv6 protocol.
• It provides a low-cost, scalable, and secure solution for IoT applications by enabling mesh networking and
interoperability with multiple devices.
3. Transport Layer
• Provide end-to-end message transfer capability independent of the underlying network.
• It provides functions such as error control, segmentation, flow control and congestion control.

Transmission Control Protocol

• Connection Oriented and Ensures Reliable transmission.
• Provides Error Detection Capability to ensure no duplicacy of packets and retransmit lost packets .
• Flow Control capability to ensure the sending data rate is not too high for the receiver process .
• Congestion control capability helps in avoiding congestion which leads to degradation of n/w performance.

User Datagram Protocol

• Connectionless and Does not ensures Reliable transmission.
• Does not do connection before transmitting .
• Does not provide proper ordering of messages .
• Transaction oriented and stateless .
4. Application Layer
HTTP – (Hypertext Transfer Protocol) MQTT – (Message Queuing Telemetry Transport)
• Uses Universal Resource Identifiers(URIs) to identify HTTP • For Real time communication and streaming XML data
resources. between n/w entities
• Follows a request-response model. • Decentralized protocol and uses client server architecture.
• Includes commands such as GET,PUT, POST, HEAD, Used for Applications such as Multi-party chat and
OPTIONS, TRACE..etc. voice/video calls.
CoAP – (Constrained Application Protocol)
DDS – (Data Distribution service)
• Used for Machine to machine (M2M) applications meant
for constrained devices and h/w’s. • It is a data-centric middleware standard for device-to-
• Web transfer protocol for IoT and uses request-response device communication.
model/ client –server architecture . • Publish subscribe model where publishers create topics to
• Supports methods such as GET,POST, PUT and DELETE. which subscribers can use.
• Provides Quality-of-service control and configurable
AMQP - (Advanced Messaging Queuing Protocol) reliability.
• Supports both point-to-point and publisher/subscriber
WebSocket
models, routing and queuing.
• Allows full-duplex communication over single socket .
• This Protocol is used for business messaging where Broker
• Based on TCP.
here receives messages from publishers and route them
• Client can be a browser, IoT device or mobile application.
over connections to consumers through messaging
queues.
 Logical Design of IoT

IoT Functional Blocks IoT Communication Model IoT Communication APIs

1. Device 1. Request-Response 1. REST based communication APIs

2. Communication 2. Publish-Subscribe (Request-Response Based Model)
3. Management 3. Push-Pull
2. WebSocket based Communication
4. Services 4. Exclusive Pair
APIs(Exclusive Pair Based Model)
5. Security
6. Application
IoT Functional Blocks
• Logical design of an IoT system refers to an abstract
representation of the entities and processes without
going into the low-level specifics of the implementation.

• An IoT system comprises a number of functional blocks

that provide the system the capabilities for identification,
sensing, actuation, communication and management.

• Device: An IoT system comprises of devices that provide

sensing, actuation, monitoring and control functions.

• Communication: handles the communication for IoT

• Security: Secures IoT system and priority functions such as
system.
authentication, authorization, message and context integrity
• Management: Provides various functions to govern the and data security.
IoT system.
• Application: IoT application provide an interface that the
• Services: Services like device monitoring, device control
users can use to control and monitor various aspects of IoT
services, data publishing services and device discovery. system.
IoT Communication Model
1. Request–Response Communication Model
• Request–Response is a communication model in which the client sends requests to the server and the server
responds to the requests.
• When the server receives a request, it decides how to respond, fetches the data, retrieves resource representations,
prepares the response and then sends the response to the client.
• Stateless communication model
2. Publish–Subscribe Communication Model
• Publish–Subscribe is a communication model that involves publishers, brokers and consumers.
• Publishers are the source of data. Publishers send the data to the topics which are managed by the broker. Publishers
are not aware of the consumers.
• Consumers subscribe to the topics which are managed by the broker.
• When the broker receives data for a topic from the publisher, it sends the data to all the subscribed consumers.
3. Push–Pull Communication Model

• Push–Pull is a communication model in which the data producers push the data to queues and the consumers pull
the data from the queues. Producers do not need to be aware of the consumers.

• Queues help in decoupling the messaging between the producers and consumers.

• Queues also act as a buffer which helps in situations when there is a mismatch between the rate at which the
producers push data and the rate at which the consumers pull data.
4. Exclusive Pair Communication Model
• Exclusive Pair is a bidirectional, fully duplex communication model that uses a persistent connection between the client
and the server.
• Once the connection is set up it, remains open until the client sends a request to close the connection.
• Client and server can send messages to each other after connection setup.
Communication APIs
1. REST-based Communication APIs
• Representational State Transfer (REST) is a set of architectural principles by which you can design web services
and web APIs that focus on a system’s resources and how resource states are addressed and transferred.
• REST APIs follow the request–response communication model.
• REST architectural constraints apply to the components, connectors and data elements within a distributed
hypermedia system.

REST-based Communication APIs Constraints

• Client – Server
• Stateless
• Cacheable
• Layered System
• Uniform Interface
• Code on demand
2. WebSocket-based Communication APIs
• WebSocket APIs allow bidirectional, full duplex communication between clients and servers.
• WebSocket APIs follow the exclusive pair communication model.
 Difference between REST and WebSocket-based Communication APIs
S.NO. REST API WEB SOCKET API
1. It is Stateless protocol. It will not store the data. It is Stateful protocol. It will store the data.

It is Uni-directional. Only either server or client It is Bi-directional. Messages can be received or sent
2.
will communicate. by both server or client.

3. It is Request-response model. It is Full duplex model.

HTTP request contains headers like head section, It is suitable for real-time applications. It does not
4.
title section. have any overhead.

New TCP connection will be set up for each HTTP

5. Only Single TCP connection.
request.

It depends upon the HTTP methods to retrieve the It depends upon the IP address and port number to
6.
data.. retrieve the data

It is slower than web socket regarding the web socket transmits messages very fastly than REST
7.
transmission of messages. API.

It does not need memory or buffers to store the

8. It requires memory and buffers to store the data.
data.