Lec 3

IOT ARCHITECTURES
Lect. 3
2
COMMUNICATION CHANNELS
• IoT systems enable Things to communicate with servers as well as other
Things, internet technology provides the foundation for this
communication.
• An IoT system communicates by combining IoT specific internet protocols
and a method for connectivity
• Internet Protocols
• Existing internet protocols, such as Transmission Control Protocol/Internet
Protocol (TCP/IP), are often too inefficient and power hungry to apply to
emerging IoT applications.
• we will discuss some alternative internet protocols developed for use by
IoT systems.
• Message Queuing Telemetry Transport (MQTT) and Constrained
Application Protocol (CoAP) are two alternative internet protocols.
3
MESSAGE QUEUING TELEMETRY

• TRANSPORT
MQTT is a lightweight, publish subscribe network protocol that transports
messages between devices. It is widely used due to its efficiency and
minimal resource usage.
• Characteristics of MQTT include:
• Publish/subscribe Architecture: devices can publish messages on specific
topics and others subscribe to those topics to receive the messages.
• Small Footprint: it works efficiently in low-bandwidth, high-latency or
unreliable networks, making it ideal for IoT devices with limited
processing power.
• Quality of Service :MQTT provides three levels of QoS allowing the user to
choose how message delivery should guaranteed.
MESSAGE QUEUING TELEMETRY 4
TRANSPORT
• QoS 0: best effort delivery at most once.
• QoS 1: messages may be delivered multiple times Q at least once.
• QoS 2: ensures only one delivery exactly once.
• Persistent sessions: MQTT supports persistent sessions, allowing clients to
reconnect without losing the context of previous session.
• Retained messages: publishers can retain the last message on a topic so that new
subscribers immediately receive the latest message upon subscription.
• It is commonly used in industries such as automotive, healthcare, smart homes
and telecommunications, where real-time, efficient communication between
connected devices is essential.

IoT things presentation - Davis M Onsakia
5

6
CONSTRAINED APPLICATION PROTOCOL

• CoAP is a specialized web transfer protocol designed for use in constrained
devices and networks, It is designed to be lightweight and to operate
efficiently in environments with low bandwidth, limited power, and
constrained processing capabilities
• CoAP characteristics include:
• Client/Server Model: it uses a client server architecture similar to HTTP,
where clients make requests to servers, and servers respond to those
requests. However it is optimized for constrained environments, unlike HTTP.
• RESTful Protocol: CoAP follows the REST (representational State Transfer)
model meaning that it supports the standard HTTP methods like GET, POST,
PUT and DELETE these allow CoAP to interact with web resources in
standardized way.
• Efficient with low Overhead: CoAP operates over UDP (User Datagram
Protocol) which is less resource intensive than TCP which reduces overhead,
making CoAP more efficient in constrained environments.
CONSTRAINED APPLICATION PROTOCOL
• Asynchronous Communication: CoAP supports asynchronous message
exchange, meaning that clients do not have to wait for a response
immediately after sending a request which is ideal for IoT devices that
may experience variable response times.
• Built in reliability: CoAP provides a simple message retransmission
mechanism to ensure message delivery even though it uses UDP which is
unreliable by default CoAP message can be sent as confirmable( requiring
acknowledgment) or non-confirmable (no-acknowledgment required).
• Resource Discovery: CoAP includes a mechanism for discovering
resources an a device, this helps in dynamically finding services and
devices on a network.
• Proxy caching support: which improves the performance in larger,
distributed IoT systems.
• Security: CoAP can use Datagram Transport Layer Security to provide
encryption, integrity, and authentication for secure communication. It is
well suited for applications like smart home devices, industrial
automation and other IoT applications where bandwidth and power are
8
TCP/IP REVIEW
• Before going further, it is helpful to review existing
internet layers and protocols.
• The internet is based on TCP/IP communications and operates
using the 7 layer
OSI (open system
interconnection)model
or 4 layers model
shown in
the following chart

9
WHY INTERNET PROTOCOLS ARE NOT ENOUGH?

• There are a few reasons that the traditional internet design is not sufficient.
For starters, it cannot accommodate the major power constraints of some IoT
devices. The connection may not always be stable or may have limited
memory.
• Finally, not all IoT applications require guaranteed data delivery, data
protection, or message acknowledgment. These capabilities may be
beneficial, but the data overhead and power cost may not be worth it.
• For example, take the overhead ratio of a standard TCP/IP datagram
(Overhead Ratio% = Overhead/Total Bytes). If considering an IP Datagram
(over IPv6) of 1280 bytes. TCP overhead is 20 bytes. The overhead ratio
would be 1.6% (20/1280). For CoAP, overhead is at least 4 bytes, resulting in
an overhead ratio of 0.3% (4/1280). Not much of an improvement!
• Now consider an IoT application. The data could include device temperature
(4 bytes), GPS position (16 bytes), and time (10 bytes). Byte consumption
amount totals 30 bytes, plus overhead. In this case, the TCP overhead ratio
would be 40% (20/50) and the CoAP overhead ratio would be 11.8% (4/34).
Use of this data format is almost 4 times more efficient, resulting in power
saving
10
PROTOCOL SUMMARY
• MQTT and CoAP are becoming the leading, lightweight messaging
protocols for the IoT market.
• Each protocol offers unique benefits with some fundamental differences.
Both protocols are used for mesh-networking applications, in which
lightweight end nodes are a necessary aspect of almost every network.
• Both also act as a gateway for bridging logic to allow inter-standard
communication.
• MQTT is most commonly run in Asynchronous only
• For higher-level security, other protocols such as Data Distribution Service
(DDS) or extensible Messaging and Presence Protocol (XMPP) should be
considered
11
PROTOCOL SUMMARY

LINK LAYER IMPROVEMENTS
12
• MQTT and CoAP make improvements primarily in the Application layer.

• However, efforts are being made to offer improvements for IoT at the link layer.
• IPv6 over Low-Power Wireless Personal Area Networks” – 6LoWPAN is a
networking technology or adaptation layer that allows IPv6 packets to move
within small link layer frames.
• 6LoWPAN is a link layer protocol that defines encapsulation and header
compression mechanisms, as well as fragmentation and reassembly mechanisms
that provide for adaptation between standard IP data packets (1280 bytes) and
the IoT optimized packets of IEEE 802.15.4 (127 bytes). This
• allows packets sent from the Internet to be seamlessly transmitted across an
802.15.4 link and vice versa. The standard has the freedom of frequency band
and physical layer, and is usable across multiple communication platforms.
13
CONNECTIVITY SOLUTIONS
• An internet protocol relies on connectivity to transport data
between nodes. Connectivity can be thing-to-thing, thing-to-
server, or server-to-server. There are sever-all node architecture
options. They can range from simple, point-to-point solutions, to
complex, sophisticated solutions.
Connectivity options for IoT systems include:
1. Wired Direct: The IoT device is physically wired into the internet (e.g.
Ethernet)
2. Wireless Direct: The IoT device wirelessly communicates with the
internet (e.g. a Wi-Fi or cellular connection).
3. Wireless Local Connection, Wired Internet Connection: The IoT
device communicates wirelessly with a local system using a short
range, local connectivity solution. The local system, itself, is physically
wired into the internet (e.g. via ethernet)
14
CONNECTIVITY SOLUTIONS
• Wireless Local Connection, Wireless Internet Connection: The IoT
device communicates wirelessly with a local system using a short range,
local connectivity solution. The local system, itself, connects wirelessly to
the internet.
• Star Network
• A star network has a central node managing connections with many other
nodes. The central node is the hub, or access point (AP). The AP connects to
the internet, providing the connection for all other nodes. Nodes do not talk
to each other unless the AP forwards the message.
• Mesh Network
• A mesh network allows nodes within a specified range to talk to one another.
Using multiple paths from the source node to the destination node, creates a
robust network. However, the routing can get complicated depending on the
requirements of the system. Typically, the internet connects to only one
node in this network type.
15
WIRELESS RADIO TECHNOLOGY
16
• What is the best wireless technology for IoT applications? The answer
is, there isn’t one. There are numerous candidates for wireless
technology. Which candidate is best is dependent on the design
constraints of the IoT system. Below is a helpful chart to organize
your constraints as you read through the IoT wireless solutions
17
18
END
Thanks for listening

Lec 3

Uploaded by

Copyright:

Available Formats

Lec 3

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Lec 3

Uploaded by

Copyright:

Available Formats

IOT ARCHITECTURES

MESSAGE QUEUING TELEMETRY

• QoS 1: messages may be delivered multiple times Q at least once.

• QoS 2: ensures only one delivery exactly once.

• Persistent sessions: MQTT supports persistent sessions, allowing clients to

reconnect without losing the context of previous session.

subscribers immediately receive the latest message upon subscription.

• It is commonly used in industries such as automotive, healthcare, smart homes

and telecommunications, where real-time, efficient communication between

connected devices is essential.

IoT things presentation - Davis M Onsakia

CONSTRAINED APPLICATION PROTOCOL

IoT things presentation - Davis M Onsakia

WHY INTERNET PROTOCOLS ARE NOT ENOUGH?

IoT things presentation - Davis M Onsakia

• MQTT and CoAP make improvements primarily in the Application layer.

Thanks for listening

You might also like