0% found this document useful (0 votes)
14 views

IoT Protocols

The document discusses the physical and logical design of IoT, outlining the components, protocols, and communication models involved. It details various IoT devices, their interfaces, and the protocols across different layers including link, network, transport, and application layers. Additionally, it covers IoT functional blocks, communication models like request-response and publish-subscribe, and communication APIs such as REST and WebSocket.
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
14 views

IoT Protocols

The document discusses the physical and logical design of IoT, outlining the components, protocols, and communication models involved. It details various IoT devices, their interfaces, and the protocols across different layers including link, network, transport, and application layers. Additionally, it covers IoT functional blocks, communication models like request-response and publish-subscribe, and communication APIs such as REST and WebSocket.
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 8

Physical Design of IoT:

1) Things in IoT:

The things in IoT refers to IoT devices which have unique identities and
perform remote sensing, actuating and monitoring capabilities. IoT devices
can exchange data with other connected devices applications. It collects
data from other devices and process data either locally or remotely.

An IoT device may consist of several interfaces for communication to other


devices both wired and wireless. These includes
(i) I/O interfaces for sensors,
(ii) Interfaces for internet connectivity,
(iii) Memory and storage interfaces and(iv)audio/video interfaces.

2) IoT Protocols:

a) Link Layer: Protocols determine how data is physically sent over


the network’s physical layer or medium. Local network connect to
which host is attached. Hosts on the same link exchange data
packets over the link layer using link layer protocols.
Link layer determines how packets are coded and signaled by the
h/w device over the medium to which the host is attached.
Protocols:

• 802.3-Ethernet: IEEE802.3 is collection of wired Ethernet


standards for the link layer. Eg: 802.3 uses co-axial cable;
802.3i uses copper twisted pair connection; 802.3j uses fiber
optic connection; 802.3ae uses Ethernet over fiber.
• 802.11-WiFi: IEEE802.11 is a collection of wireless
LAN(WLAN) communication standards including extensive
description of link layer. Eg: 802.11a operates in 5GHz band,
802.11b and 802.11g operates in 2.4GHz band, 802.11n
operates in 2.4/5GHzband, 802.11ac operates in 5GHz band,
802.11ad operates in 60Ghzband.
• 802.16 - WiMax: IEEE802.16 is a collection of wireless
broadband standards including exclusive description of link
layer. WiMax provide data rates from 1.5 Mb/s to 1Gb/s.

• 802.15.4-LR-WPAN: IEEE802.15.4 is a collection of standards


for low rate wireless personal area network(LR-WPAN).Basis
for high level communication protocols such as ZigBee.
Provides data rate from 40kb/s to250kb/s.
b) Network/Internet Layer: Responsible for sending IP
datagrams from source n/w to destination n/w, performs the host
addressing and packet routing. Datagrams contains source and
destination address.

Protocols:

• IPv4: Internet Protocol version4 is used to identify the devices on a


network using a hierarchical addressing scheme. 32-bit address and
allows total of 2**32 addresses.
• IPv6: Internet Protocol version6 uses 128-bit address scheme and
allows2**128 addresses.
• 6LOWPAN: (IPv6 over Low power Wireless Personal Area Network)
operates in 2.4GHz frequency range and data transfer 250kb/s.

B) Transport Layer: Provides end-to-end message transfer capability


independent of the underlying n/w. Set up on connection with ACK as in
TCP and without ACK as in UDP. Provides functions such as error control,
segmentation, flow control and congestion control.

Protocols:
• TCP: Transmission Control Protocol used by web browsers (along
with HTTP and HTTPS), email(along with SMTP, FTP). Connection
oriented and stateless protocol. IP Protocol deals with sending
packets, TCP ensures reliable transmission of protocols in order.
Avoids n/w congestion and congestion collapse.
• UDP: User Datagram Protocol is connectionless protocol. Useful in
time sensitive applications, very small data units to exchange.
Transaction oriented and stateless protocol. Does not provide
guaranteed delivery.

C) Application Layer: Defines how the applications interface with lower


layer protocols to send data over the n/w. Enables process-to-process
communication using ports.
Protocols:

• HTTP: Hyper Text Transfer Protocol that forms foundation of WWW.


Follow request- response model Stateless protocol.
• CoAP: Constrained Application Protocol for machine-to-machine
(M2M) applications with constrained devices, constrained
environment and constrained n/w. Uses client- server architecture.
• Web Socket: allows full duplex communication over a single socket
connection.
• MQTT: Message Queue Telemetry Transport is light weight
messaging protocol based on publish-subscribe model. Uses client
server architecture. Well suited for constrained environment.
• XMPP: Extensible Message and Presence Protocol for real time
communication and streaming XML data between network entities.
Support client-server and server-server communication.
• DDS: Data Distribution Service is data centric middle ware standards
for device-to-device or machine-to-machine communication. Uses
publish-subscribe model.
• AMQP: Advanced Message Queuing Protocol is open application layer
protocol for business messaging. Supports both point-to-point and
publish-subscribe model.

Logical Design of IoT:

Refers to an abstract represent of entities and processes without going into


the low level specifies of implementation.

1) IoT Functional Blocks


2) IoT Communication Models
3) IoT Communication APIs

1) IoT Functional Blocks: 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 system.
• Services: for device monitoring, device control services,
data publishing services and services for device discovery.
• Management: Provides various functions to govern the IoT system.
• Security: Secures IoT system and priority functions such as
authentication, authorization, message and context integrity and data
security.
• Application: IoT application provide an interface that the users can
use to control and monitor various aspects of IoT system.

2) IoT Communication Models:

1) Request-Response 2) Publish-Subscribe 3) Push-Pull 4) Exclusive


Pair
1) Request-Response Model:

In which the client sends request to the server and the server replies to
requests. Is a stateless communication model and each request-response
pair is independent of others.

2) Publish-Subscribe Model:
Involves publishers, brokers and consumers. Publishers are source of data.
Publishers send 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 Model: in which data producers push data to queues and


consumers pull data from the queues. Producers do not need to aware of
the consumers. Queues help in decoupling the message between the
producers and consumers.

4) Exclusive Pair: is bi-directional, fully duplex communication model that


uses a persistent connection between the client and server. Once
connection is set up it remains open until the client send a request to close
the connection. Is a stateful communication model and server is aware of
all the open connections.
3) IoT Communication APIs:

a) REST based communication APIs(Request-Response


Based Model)
b) WebSocket based Communication APIs(Exclusive
PairBased Model)

a) REST based communication APIs: Representational State


Transfer(REST) is a set of architectural principles by which we can design
web services and web APIs that focus on a system‗s resources and have
resource states are addressed and transferred.

The REST architectural constraints: Fig. shows communication between


client server with REST APIs.

You might also like