06/02/25 IoT and Cloud Computing 1

Faculty Name : Dr. K. Kishore Kumar – TTS2045

(AP-SG / CSE / VEL TECH)
Slot No. : S1+L14
Year : Winter Semester : 2023-2024

Department of Computer Science & Engineering

School of Computing
Vel Tech Rangarajan Dr. Sagunthala R&D Institute of Science and Technology

06/02/25 IoT and Cloud Computing 2

 PEO1 : Will formulate, solve and analyze Computer Science and
Engineering problems using necessary mathematical, Scientific and
engineering fundamentals.

PEO2 : Will demonstrate the impact of cutting-edge technologies to

accomplish social and professional responsibilities.

PEO3 : Will demonstrate critical thinking, communication,

teamwork, leadership skills and ethical behavior necessary to
function productively and professionally.

PEO4 : Will pursue higher education at reputed institution in India

and abroad, work in product development companies and engage in
lifelong learning.

06/02/25 IoT and Cloud Computing 3

Engineering Graduates will be able to:
1. Engineering knowledge: Apply the knowledge of mathematics, science,
engineering fundamentals, and an engineering specialization to the
solution of complex engineering problems.
2. Problem analysis: Identify, formulate, review research literature, and
analyze complex engineering problems reaching substantiated conclusions
using first principles of mathematics, natural sciences, and engineering
sciences.
3. Design/development of solutions: Design solutions for complex
engineering problems and design system components or processes that
meet the specified needs with appropriate consideration for the public
health and safety, and the cultural, societal and environmental
considerations.
4. Conduct investigations of complex problems: Use research-based
knowledge and research methods including design of experiments,
analysis and interpretation of data, and synthesis of the information to
provide valid conclusions.

06/02/25 IoT and Cloud Computing 4

5. Modern tool usage: Create, select, and apply appropriate techniques,
resources, and modern engineering and IT tools including prediction and
modeling to complex engineering activities with an understanding of the
limitations.
6. The engineer and society: Apply reasoning informed by the contextual
knowledge to assess societal, health, safety, legal and cultural issues and
the consequent responsibilities relevant to the professional engineering
practice.
7. Environment and sustainability: Understand the impact of the
professional engineering solutions in societal and environmental contexts,
and demonstrate the knowledge of, and need for sustainable development.
8. Ethics: Apply ethical principles and commit to professional ethics and
responsibilities and norms of the engineering practice.

06/02/25 IoT and Cloud Computing 5

09. Individual and team work: Function effectively as an individual, and
as a member or leader in diverse teams, and in multidisciplinary settings.

10. Communication: Communicate effectively on complex engineering

activities with the engineering community and with society at large, such
as, being able to comprehend and write effective reports and design
documentation, make effective presentations, and give and receive clear
instructions.
11. Project management and finance: Demonstrate knowledge and
understanding of the engineering and management principles and apply
these to one’s own work, as a member and leader in a team, to manage
projects and in multidisciplinary environments.
12. Life-long learning: Recognize the need for, and have the preparation
and ability to engage in independent and life-long learning in the broadest
context of technological change.

06/02/25 IoT and Cloud Computing 6

On successful completion of the program, the graduates will be able to,

PSO1: Mathematical Concepts: Equipped with the knowledge to

infer the mathematical models for problem solving using data
structures, design and analysis of algorithms.

PSO2: Software Development: Exhibit proficiency to analyze,

design and develop applications in various domains to provide
solutions using innovative ideas.

PSO3: Transferring Skills: Demonstrate the ability to provide

solutions for real world problems through acquaintance and hands-
on training

06/02/25 IoT and Cloud Computing 7

COURSE CODE COURSE TITLE L T P C

10212CS229 IoT and Cloud Computing 3 0 2 4

Description:

• The core modules of this elective course include

•introduction to IoT,
•Elements of IoT,
•Data Analytics and IoT Platform.

• This course aims to teach the student to understand the concepts of Internet of
Things(IoT) and can able to practice the same with practical kits to build IoT
applications.

06/02/25 IoT and Cloud Computing 8

 Prerequisite Courses

S.NO COURSE CODE COURSE NAME

1 10211CS129 Modern Computer Architecture

06/02/25 IoT and Cloud Computing 9

 Course Outcomes
Upon the successful completion of the course, students will be able to:
Knowledge Level
CO
Course Outcomes (Based on revised
Nos.
Bloom’s Taxonomy)
Understand the various concepts of IoT and their
CO1 K2
technologies
Choose appropriate physical devices to develop IoT
CO2 K3
applications.
CO3 Use various protocols in IoT applications K3
Demonstrate the use of cloud technology in IoT
CO4 K3
applications.
CO5 Develop a smart application using IoT and Cloud. K3

K1-Remember; K2-Understand; K3- Apply; K4-Analyze; K5 – Evaluate; K6 Create.

06/02/25 IoT and Cloud Computing 10

 Correlation of COs with POs :

PO1. Engineering knowledge PO9. Individual and team work

PO2. Problem analysis PO10. Communication
PO3. Design/development of solutions PO11. Project management and finance
PO4. Conduct investigations of complex problems PO12. Life-long learning
PO5. Modern tool usage PSO1: Mathematical Concepts
PO6. The engineer and society PSO2: Software Development
PO7. Environment and sustainability PSO3: Transferring Skills
PO8. Ethics
06/02/25 IoT and Cloud Computing 11
 Chalk And Talk Demonstration Learning By Doing

Simulation Peer Learning ICT Tools

06/02/25 IoT and Cloud Computing 12

U

nit I – Introduction to IoT

Duration : 45 Hours
Introduction to IoT – IoT – Characteristics – IoT Complete Architectural Stack – IoT
enabling Technologies – IoT Challenges.
Case studies: Architectural analysis for IoT applications 01
Unit II – Data Management and Smart Objects in IoT

Sensors and Hardware for IoT – Hardware Platforms – Arduino, Raspberry Pi, Node MCU.
Case studies: Data acquisition from sensors with hardware platforms
02
Unit III – Access Technologies and Application Protocols for IoT

Protocols for IoT – Infrastructure protocol, Identification, Transport Layer Protocolos,

Discovery, Data Protocols, Device Management Protocols.
Case Study: MQTT/CoAP usage in IoT applications.
03
Unit IV – Analytics Concepts and Securing IoT

Introduction to Cloud Computing - Service Model – Deployment Model- Cloud Platforms –

Amazon AWS – Microsoft Azure – Google APIs.
Case Studies: Risk Issues, and Legal Aspects of Cloud Computing 04
Unit V – Cloud for IoT

Role of Cloud Computing in IoT - Cloud Components - S3 – Lambda - IoT Core - 05

Connecting a IoT applications to cloud
Case Study: Cloud Data Security

06/02/25 IoT and Cloud Computing 13

Lab Experiments: (Duration : 30 Hours)
Part-1
Task 1 : Familiarization with Arduino/Raspberry Pi/Node MCU and perform necessary software
installation.
Task 2 : Familiarization with Fritzing and Thnikercad for design and fabrication of circuits.
Task 3 : To interface LED/Buzzer with Arduino/ Raspberry Pi and write a program to implement
traffic light system.
Task 4 : To interface Digital sensor (IR/LDR) with Arduino/Raspberry Pi and write a program for
object detection and find the distance between sensor and object.
Task 5 : To interface DHT11 sensor with Arduino/Raspberry Pi and write a program to find the
weather conditions and control the air conditioner.
Task 6 : To interface motor using relay with Arduino/Raspberry Pi and write a program to control
the direction and speed of the motor.
Task 7 : To interface Bluetooth/WiFi with Arduino/Raspberry Pi and write a program to send
sensor data to smartphone using Bluetooth.
Task 8 : Write a program on Arduino/Raspberry Pi to push the data to cloud for detecting the fire
event using temperature, light and smoke sensors.
Task 9 : Write a program on Arduino/Raspberry Pi to upload/retrieve/visualize the sensor data to
thingspeak/thingsio cloud for predicting the future data.
Task 10 :Write a program on Arduino/Raspberry Pi to stream the sensor data with IoT core and
use Bigquery to store data being streamed from IoT devices. Create Pub/Sub model for event
driven systems.
Task 11 :Use Cloud IoT Core for IoT based environmental monitoring application.
Task 12 :Use Cloud IoT Core for IoT based Smart Light Controlling& Monitoring System.
Part-2
Task 13: Implement a smart dust bin to detect level of Garbage, Temperature, Humidity, Gases
like Ammonia, Carbon Monoxide and send a message with GPS coordinates to garbage
collector using GSM module.
Task 14: Implement a person centric health care management system to detect the medical events
using IoT components and cloud Task
15:Implement a Smart home with IoT components and cloud for occupant monitoring.

06/02/25 IoT and Cloud Computing 14

 Books
Books
Reference Books
Text Book1

David Hanes, Gonzalo Salgueiro,

Patrick Grossetete, Rob Barton and 1. Arshdeep Bahga, Vijay
Jerome Henry, “IoT Fundamentals: Madisetti, “Internet of
Networking Technologies, Protocols Things (A Hands-On-
and Use Cases for Internet of Things”, Approach)”, VPT,
Cisco Press, 2017. 2014.

1. Olivier Hersent, David

Text Book2 Boswarthick, Omar
Elloumi, “The Internet
Honbo Zhou, The Internet of Things of Things – Key
in the Cloud: A Middleware applications and
Perspective,CRC Press, 2012 Protocols”, Wiley,
2012.

1. Michael Margolis,
“Arduino Cookbook”
OReilly, Second
Edition, 2011.

06/02/25 IoT and Cloud Computing 15

Outcome :

Explain the IEEE standards and basic protocols of

IoT–K2

06/02/25 IoT and Cloud Computing 16

•Wireless Access Technology
oIEEE 802.15.4
oIEEE 1901.2a
oIEEE 802.11ah
oLoRaWAN
•The Transport Layer
•IoT Application Transport Methods : Application Layer Protocol Not Present,
•SCADA,
•Background on SCADA,
•Adapting SCADA for IP,
•Tunneling Legacy SCADA over IP Networks,
•SCADA Protocol Translation,
•SCADA Transport over LLNs with MAP-T,
• Generic Web-Based Protocols,
•IoT Application Layer Protocols,
•CoAP, Message Queuing Telemetry Transport (MQTT).

06/02/25 IoT and Cloud Computing 17

The following topics are addressed for each IoT access technology:
• Standardization and alliances: The standards bodies that maintain the
protocols for a technology

• Physical layer: The wired or wireless methods and relevant frequencies

• MAC layer: Considerations at the Media Access Control (MAC) layer,

which bridges the physical layer with data link control

• Topology: The topologies supported by the technology

• Security: Security aspects of the technology Competitive technologies:
Other technologies that are similar and may be suitable alternatives to the
given technology

06/02/25 IoT and Cloud Computing 18

• IEEE 802.15.4 is a wireless access technology for low-cost and low-data-
rate devices that are powered or run on batteries.
• In addition to being low cost and offering a reasonable battery life, this
access technology enables easy installation using a compact protocol stack
while remaining both simple and flexible.
• IEEE 802.15.4 is commonly found in the following types of deployments:
– Home and building automation
– Automotive networks
– Industrial wireless sensor networks
– Interactive toys and remote controls

06/02/25 IoT and Cloud Computing 19

• The 802.15.4 standard supports an extensive number of PHY options that
range from 2.4 GHz to sub-GHz frequencies in ISM bands.

• The original physical layer transmission options were as follows:

– 2.4GHz, 16 channels, with a data rate of 250 kbps
– 915 MHz, 10 channels, with a data rate of 40 kbps
– 868 MHz, 1 channel, with a data rate of 20 kbps

802.15.4 Physical Layer Format

06/02/25 IoT and Cloud Computing 20

06/02/25 IoT and Cloud Computing 21
 • IEEE 802.15.4–based networks
can be built as star, peer-to-
peer, or mesh topologies.

• one FFD acting as a PAN

coordinator is required to
deliver services that allow
• other devices to associate and
form a cell or PAN.

06/02/25 IoT and Cloud Computing 22

• The IEEE 802.15.4 specification uses Advanced Encryption Standard
(AES) with a 128-bit key length as the base encryption algorithm for
securing its data.

06/02/25 IoT and Cloud Computing 23

• The IEEE 802.15.4 PHY and MAC layers are the foundations for several
networking profiles that compete against each other in various IoT access
environments.

• A competitive radio technology that is different in its PHY and MAC

layers is DASH7.

06/02/25 IoT and Cloud Computing 24

 • After the release of the IEEE 802.15.4
specification the previous year.

• While not released as a typical standard, like

an RFC, ZigBee still had industry support
from more than 100 companies upon its
initial publication.

• This industry support has grown to more than

400 companies that are members of the
ZigBee Alliance.

• Similar to the Wi-Fi Alliance, the Zigbee

Alliance is an industry group formed to
certify interoperability between vendors and
it is committed to driving and

• evolving ZigBee as an IoT solution for

interconnecting smart objects.

06/02/25 IoT and Cloud Computing 25

06/02/25 IoT and Cloud Computing 26
 • IP and TCP/UDP protocols and
various other open standards are
now supported at the network
and transport layers.

• ZigBee IP was created to

embrace the open standards
coming from the IETF’s work
on LLNs, such as IPv6,
6LoWPAN, and RPL.

• They provide for low-

bandwidth, low-power, and
cost-effective communications
when connecting smart objects.

06/02/25 IoT and Cloud Computing 27

• IEEE 1901.2a-2013 is a wired technology that is an update to the original
IEEE 1901.2 specification.
• This is a standard for Narrowband Power Line Communication (NB-PLC).
NB-PLC is often found in use cases such as the following:
– Smart metering:
– Distribution automation
– Public lighting
– Electric vehicle charging stations
– Microgrids
– Renewable energy

06/02/25 IoT and Cloud Computing 28

• The first generations of NB-PLC implementations have generated a lot of
interest from utilities in Europe but have often suffered from poor reliability,
low throughput (in the range of a few hundred bits per second to a maximum of
2 kbps), lack of manageability, and poor interoperability.

• This has led several organizations to develop their own specifications for new
generations of NB-PLC technologies.

• NB-PLC standards are based on orthogonal frequency-division multiplexing

(OFDM).

• OFDM encodes digital data on multiple carrier frequencies. This provides

several parallel streams that suffer less from high frequency attenuation in
copper wire and narrowband interference.

• The IEEE 1901.2 working group published the IEEE 1901.2a

06/02/25 IoT and Cloud Computing 29

• US FCC-Low and FCC-above- CENELEC, and Japan ARIB bands.

• The FCC is the Federal Communications Commission, a US

government organization that regulates interstate and international
communications by radio, television, wire, satellite, and cable.

06/02/25 IoT and Cloud Computing 30

• The MAC frame format of IEEE 1901.2a is based on the IEEE 802.15.4
MAC frame but integrates the latest IEEE 802.15.4e-2012 amendment,
which enables key features to be supported.
• One of the key components brought from 802.15.4e to IEEE 1901.2a is
information elements. With IE support, additional capabilities, such as
IEEE 802.15.9 Key Management Protocol and SSID, are supported.

06/02/25 IoT and Cloud Computing 31

06/02/25 IoT and Cloud Computing 32
• Encryption and authentication are performed using AES.
• support the IEEE 802.15.9 Key Management Protocol.
• PHY layer fragmentation capabilities of IEEE 1901.2a and include the following:
• The Security Enabled bit in the Frame Control field should be set in all MAC frames carrying
segments of an encrypted frame.
• If data encryption is required, it should be done before packet segmentation. During packet
encryption, the Segment Control field should not be included in the input to the encryption
algorithm.
• On the receiver side, the data decryption is done after packet reassembly.
• When security is enabled, the MAC payload is composed of the ciphered payload and the
message integrity code (MIC) authentication tag for non-segmented payloads. If the payload is
segmented, the MIC is part of the last packet (segment) only. The MIC authentication is
computed using only information from the MHR of the frame carrying the first segment.

06/02/25 IoT and Cloud Computing 33

• In the domain of NB-PLC, two technologies compete against IEEE
1901.2a: G3-PLC (now ITU G.9903) and PRIME (now ITU G.9904).

• Both of these technologies were initially developed to address a single use

case: smart metering deployment in Europe over the CENELEC A band.

06/02/25 IoT and Cloud Computing 34

• IEEE 802.11 Wi-Fi is certainly the most successfully deployed wireless
technology. This standard is a key IoT wireless access technology, either
for connecting endpoints such as fog computing nodes, high-data-rate
sensors, and audio or video analytics devices or for deploying Wi-Fi
backhaul infrastructures, such as outdoor Wi-Fi mesh in smart cities, oil
and mining, or other environments. Three main use cases are identified for
IEEE 802.11ah:
• Sensors and meters covering a smart grid: Meter to pole,
environmental/agricultural monitoring, industrial process sensors, indoor
healthcare system and fitness sensors, home and building automation
sensors
• Backhaul aggregation of industrial sensors and meter data: Potentially
connecting IEEE 802.15.4g subnetworks
• Extended range Wi-Fi: For outdoor extended-range hotspot or cellular
traffic offloading when distances already covered by IEEE
802.11a/b/g/n/ac are not good enough

06/02/25 IoT and Cloud Computing 35

• IEEE 802.11 working group decided to work on an “industrial Wi-Fi” and
created the IEEE 802.11ah group. The 802.11ah specification would
operate in unlicensed sub-GHz frequency bands, similar to IEEE 802.15.4
and other LPWA technologies.

• The industry organization that promotes Wi-Fi certifications and

interoperability for 2.4 GHz and 5 GHz products is the Wi-Fi Alliance. The
Wi-Fi Alliance is a similar body to the Wi-SUN Alliance.

• For the 802.11ah standard, the Wi-Fi Alliance defined a new brand called
Wi- Fi HaLow. This marketing name is based on a play on words between
“11ah” in reverse and “low power.

06/02/25 IoT and Cloud Computing 36

• IEEE 802.11ah essentially provides an additional 802.11 physical layer operating in
unlicensed sub-GHz bands. For example, various countries and regions use the
following bands for IEEE 802.11ah:

• 868–868.6 MHz for EMEAR,

• 902–928 MHz and associated subsets for North America and Asia- Pacific regions,
and
• 314–316 MHz, 430–434 MHz, 470–510 MHz, and 779– 787 MHz for China.
• Based on OFDM modulation, IEEE 802.11ah uses channels of 2, 4, 8, or 16 MHz
(and also 1 MHz for low-bandwidth transmission).
• This is one-tenth of the IEEE 802.11ac channels, resulting in one-tenth of the
corresponding data rates of IEEE 802.11ac.
• The IEEE 802.11ac standard is a high-speed wireless LAN protocol at the 5 GHz
band that is capable of speeds up to 1 Gbps.
• While 802.11ah does not approach this transmission speed (as it uses one-tenth of
802.11ac channel width, it reaches one-tenth of 802.11ac speed), it does provide an
extended range for its lower speed data. For example, at a data rate of 100 kbps, the
outdoor transmission range for IEEE 802.11ah is expected to be 0.62 mile.

06/02/25 IoT and Cloud Computing 37

• The IEEE 802.11ah MAC layer is optimized to support the new sub-GHz Wi- Fi
PHY while providing low power consumption and the ability to support a larger
number of endpoints. Enhancements and features specified by IEEE 802.11ah for the
MAC layer include the following:
• Number of devices: Has been scaled up to 8192 per access point.
• MAC header: Has been shortened to allow more efficient communication.
• Null data packet (NDP) support: Is extended to cover several control and
management frames. Relevant information is concentrated in the PHY header and the
additional overhead associated with decoding the MAC header and data payload is
avoided. This change makes the control frame exchanges efficient and less power-
consuming for the receiving stations.
• Grouping and sectorization: Enables an AP to use sector antennas and also group
stations (distributing a group ID). In combination with RAW and TWT, this
mechanism reduces contention in large cells with many clients by restricting which
group, in which sector, can contend during which time window. (Sectors are
described in more detail in the following section.)

06/02/25 IoT and Cloud Computing 38

• Restricted access window (RAW): Is a control algorithm that avoids
simultaneous transmissions when many devices are present and provides
fair access to the wireless network. By providing more efficient access to
the medium, additional power savings for battery-powered devices can be
achieved, and collisions are reduced.
• Target wake time (TWT): Reduces energy consumption by permitting an
access point to define times when a device can access the network. This
allows devices to enter a low-power state until their TWT time arrives. It
also reduces the probability of collisions in large cells with many clients.
• Speed frame exchange: Enables an AP and endpoint to exchange frames
during a reserved transmit opportunity (TXOP). This reduces contention
on the medium, minimizes the number of frame exchanges to improve
channel efficiency, and extends battery life by keeping awake times short.

06/02/25 IoT and Cloud Computing 39

06/02/25 IoT and Cloud Computing 40
• No additional security has been identified for IEEE 802.11ah compared to
other IEEE 802.11 specifications. (The other IEEE protocols are discussed
earlier in this chapter.) These protocols include IEEE 802.15.4, IEEE
802.15.4e, and IEEE 1901.2a, and the security information for them is also
applicable to IEEE 802.11ah.

06/02/25 IoT and Cloud Computing 41

• Competitive technologies to IEEE 802.11ah are
– IEEE 802.15.4 and
– IEEE 802.15.4e, along with the competitive technologies highlighted in each of their
sections.

06/02/25 IoT and Cloud Computing 42

• In recent years, a new set of wireless technologies known as Low-Power
Wide-Area (LPWA) has received a lot of attention from the industry and
press.
• Standardization and Alliances
• Initially, LoRa was a physical layer, or Layer 1, modulation that was
developed by a French company named Cycleo. Later, Cycleo was
acquired by Semtech. Optimized for long-range, two-way
communications and low power consumption,
• the technology evolved from Layer 1 to a broader scope through the
creation of the LoRa Alliance. For more information on the LoRa Alliance

06/02/25 IoT and Cloud Computing 43

06/02/25 IoT and Cloud Computing 44
• Semtech LoRa modulation is based on chirp spread spectrum modulation,
which trades a lower data rate for receiver sensitivity to significantly
increase the communication distance. In addition,
• It allows demodulation below the noise floor, offers robustness to noise and
interference, and manages a single channel occupation by different spreading
factors.
• This enables LoRa devices to receive on multiple channels in parallel.
• LoRaWAN 1.0.2 regional specifications describe the use of the main
unlicensed sub-GHz frequency bands of
– 433 MHz,
– 779–787 MHz,
– 863–870 MHz, and
– 902–928 MHz,
• as well as regional profiles for a subset of the 902– 928 MHz bandwidth.
• For example, Australia utilizes 915–928 MHz frequency bands,
• while South Korea uses 920–923 MHz and
• Japan uses 920–928 MHz.

06/02/25 IoT and Cloud Computing 45

06/02/25 IoT and Cloud Computing 46
• Class A: This class is the default implementation. Optimized for
batterypowered nodes, it allows bidirectional communications, where a
given node is able to receive downstream traffic after transmitting. Two
receive windows are available after each transmission.
• Class B: This class was designated “experimental” in LoRaWAN 1.0.1
until it can be better defined. A Class B node or endpoint should get
additional receive windows compared to Class A, but gateways must be
synchronized through a beaconing process.
• Class C: This class is particularly adapted for powered nodes. This
classification enables a node to be continuously listening by keeping its
receive window open when not transmitting.

06/02/25 IoT and Cloud Computing 47

• LoRaWAN topology is often described as a “star of stars” topology.
• the infrastructure consists of endpoints exchanging packets through
gateways acting as bridges, with a central LoRaWAN network server
Gateways connect to the backend network using standard IP connections,
and endpoints communicate directly with one or more gateways

06/02/25 IoT and Cloud Computing 48

• Security in a LoRaWAN
deployment applies to
different components of the
architecture,
• LoRaWAN endpoints must
implement two layers of
security, protecting
communications and data
privacy across the network.

06/02/25 IoT and Cloud Computing 49

• LPWA solutions and technologies are split between unlicensed and
licensed bands.
• The licensed-band technologies are dedicated to mobile service providers
that have acquired spectrum licenses; they are discussed in the next
section. In addition, several technologies are targeting the unlicensed-band
LPWA market to compete against LoRaWAN.
• The LPWA market is quickly evolving. Table 4-5 evaluates two of the best-
established vendors known to provide LPWA options.

06/02/25 IoT and Cloud Computing 50

06/02/25 IoT and Cloud Computing 51
• This chapter focuses on how higher-layer IoT
protocols are transported. Specifically, this chapter
includes the following sections:
• The Transport Layer: IP-based networks use either
TCP or UDP. However, the constrained nature of IoT
networks requires a closer look at the use of these
traditional transport mechanisms.
• IoT Application Transport Methods: This section
explores the various types of IoT application data and
the ways this data can be carried across a network.
•

06/02/25 IoT and Cloud Computing 52

• This section reviews the selection of a protocol for the transport layer as
supported by the TCP/IP architecture in the context of IoT networks. With
the TCP/IP protocol, two main protocols are specified for the transport
layer:
• Transmission Control Protocol (TCP): This connection-oriented
protocol requires a session to get established between the source and
destination before exchanging data.
• User Datagram Protocol (UDP): With this connectionless protocol, data
can be quickly sent between source and destination—but with n guarantee
of delivery.

06/02/25 IoT and Cloud Computing 53

• IoT Application Transport Methods
• Because of the diverse types of IoT application protocols, there are
various means for transporting these protocols across a network.
• Sometimes you may be dealing with legacy utility and industrial IoT
protocols that have certain requirements, while other times you
might need to consider the transport requirements of more modern
application layer protocols. To make these decisions easier, it makes
sense to categorize the common IoT application protocols and then
focus on the transport methods available for each category.
• The following categories of IoT application protocols and their
transport methods are explored in the following sections:

06/02/25 IoT and Cloud Computing 54

• Application layer protocol not present: In this case, the data payload is
directly transported on top of the lower layers. No application layer
protocol is used.
• Supervisory control and data acquisition (SCADA): SCADA is one of
the most common industrial protocols in the world, but it was developed
long before the days of IP, and it has been adapted for IP networks.
• Generic web-based protocols: Generic protocols, such as Ethernet, Wi-Fi,
and 4G/LTE, are found on many consumer- and enterprise-class IoT
devices that communicate over non-constrained networks.
• IoT application layer protocols: IoT application layer protocols are
devised to run on constrained nodes with a small compute footprint and are
well adapted to the network bandwidth constraints on cellular or satellite
links or constrained 6LoWPAN networks. Message Queuing Telemetry
Transport (MQTT) and Constrained Application Protocol (CoAP), covered
later in this chapter, are two well-known examples of IoT application layer
protocols.

06/02/25 IoT and Cloud Computing 55

06/02/25 IoT and Cloud Computing 56
• Supervisory control and data acquisition(SCADA).
• Designed decades ago, SCADA is an automation control system that was
initially implemented without IP over serial links, before being adapted to
Ethernet and IPv4.

06/02/25 IoT and Cloud Computing 57

• In the 1990s, the rapid adoption of Ethernet networks in the industrial world drove
the evolution of SCADA application layer protocols.
• For example, the IEC adopted the Open System Interconnection (OSI) layer model
to define its protocol framework.
• To further facilitate the support of legacy industrial protocols over IP networks,
protocol specifications were updated and published, documenting the use of IP for
each protocol. This included assigning TCP/UDP port numbers to the protocols,
such as the following:
• DNP3 (adopted by IEEE 1815-2012) - use of TCP or UDP on port 20000 for
transporting DNP3 messages over IP.
• The Modbus messaging service utilizes TCP port 502.
• IEC 60870-5-104 is the evolution of IEC 60870-5-101 serial for running over
Ethernet and IPv4 using port 2404.
• DLMS User Association specified a communication profile based on TCP/IP in the
DLMS/COSEM Green Book (Edition 5 or higher), or in the IEC 62056-53 and IEC
62056-47 standards, allowing data exchange via IP and port 4059.

06/02/25 IoT and Cloud Computing 58

06/02/25 IoT and Cloud Computing 59
06/02/25 IoT and Cloud Computing 60
06/02/25 IoT and Cloud Computing 61
06/02/25 IoT and Cloud Computing 62
06/02/25 IoT and Cloud Computing 63
• Constrained Application Protocol (CoAP) resulted from the IETF
Constrained RESTful Environments (CoRE) working group’s efforts to
develop a generic framework for resource-oriented applications targeting
constrained nodes and networks.
• The CoAP framework defines simple and flexible ways to manipulate
sensors and actuators for data or device management. The IETF CoRE
working group has published multiple standards-track specifications for
CoAP, including the following:
• RFC 6690: Constrained RESTful Environments (CoRE) Link Format
• RFC 7252: The Constrained Application Protocol (CoAP)
• RFC 7641: Observing Resources in the Constrained Application Protocol
(CoAP)
• RFC 7959: Block-Wise Transfers in the Constrained Application Protocol
(CoAP)
• RFC 8075: Guidelines for Mapping Implementations: HTTP to the
Constrained Application Protocol (CoAP)

06/02/25 IoT and Cloud Computing 64

06/02/25 IoT and Cloud Computing 65
06/02/25 IoT and Cloud Computing 66
06/02/25 IoT and Cloud Computing 67
06/02/25 IoT and Cloud Computing 68
 At the end of the 1990s,
engineers from IBM and Arcom
(acquired in 2006 by Eurotech)
were looking for a reliable,
lightweight, and cost-effective
protocol to monitor and control
a large number of sensors and
their data from a central server
location, as typically used by
the oil and gas industries. Their
research resulted in the
development and
implementation of the Message
Queuing Telemetry Transport
(MQTT) protocol that is now
standardized by the
Organization for the
Advancement of Structured
Information Standards

06/02/25 IoT and Cloud Computing 69

06/02/25 IoT and Cloud Computing 70
06/02/25 IoT and Cloud Computing 71
06/02/25 IoT and Cloud Computing 72
06/02/25 IoT and Cloud Computing 73