Module 1

IOT ARCHITECHTURE

Badharudheen P
Assistant Professor,
Dept. of CSE, MESCE, Kuttippuram
What is IoT?

 IoT is a technology transition in which devices will

allow us to sense and control the physical world by
making objects smarter and connecting them through an
intelligent network.
TRACE KTU
 Objects and machines can be sensed and controlled
remotely across a network.

 The basic goal of IoT is to “connect the unconnected”.

What is IoT?

TRACE KTU
Genesis of IoT

TRACE KTU
Genesis of IoT

 The age of IoT is often said to have started between the

years 2008 and 2009.
 With more “things” connected to the Internet than
people in the world, a new age was upon us, and
the Internet of Things was born.
TRACE KTU
 The person credited with the creation of the term
“Internet of Things” is Kevin Ashton (Father of IoT)
TRACE KTU
Evolution of IoT

TRACE KTU
IoT and Digitization

 IoT focuses on connecting “things”, such as objects and

machines, to a computer network, such as the Internet.

 Digitization is the conversion of information into a


TRACE KTU
digital format.
Digitization happening all fields including video and
photography, transportation, etc.

 In the context of IoT, digitization brings together things,

data, and business process to make networked
connections more relevant and valuable.
IoT Impact

TRACE KTU

The rapid growth in the number of devices connected to the Internet

Convergence of IT and OT
 IT (Information Technology) supports connections to the
Internet along with related data and technology systems
and is focused on the secure flow of data across an
organization.
 email, file and print services, databases, and so on


TRACE KTU
OT (Operational Technology) monitors and controls
devices and processes on physical operational
systems.
 industrial equipment, such as factory
machines, meters, actuators, electrical distribution
automation devices, etc.
Features of IoT
 Dynamic and Self Adapting:
 Capability to dynamically adapt with the changing
contexts and take actions based on their operating
condition. Ex: Surveillance cameras can adapt their
modes based on whether it is day or night.


TRACE
Self – Configuring:
KTU
 IoT devices may have self configuring capability
allowing a large number of devices to work
together to provide certain functionality.
Features of IoT
 Interoperable Communication Protocols:
 IoT Devices may support a number of
interoperable communication protocols and can
communicate with other devices and also with the
infrastructure.


TRACE
Unique Identity:
KTU
 Each IoT devices has a unique identity and a
unique identifier. IP address, URI, etc.
IoT Challenges

 Scale: While the scale of IT networks can be large, the

scale of IoT can be several orders of magnitude larger.

 Security: With more “things” becoming connected with

TRACE KTU
other “things” and people, security is an increasingly
complex issue for IoT.

 Privacy: Much of the data sensors gather will be specific

to individuals and their activities.
IoT Challenges

 Big data and data analytics: IoT and its large number of
sensors deals with huge amount of data. It should be
properly managed.


TRACE KTU
Interoperability: There are various protocols and
implementations available for IoT networks today. Some
of these protocols and architectures are based on
proprietary elements, and others are open.
IoT Network Architecture and Design
 The key difference between IT and IoT is the data.
 IT systems are mostly concerned with reliable and
continuous support of business applications such as
email, web, databases, and so on.
 IoT is all about the data generated by sensors
TRACE KTU
and how that data is used.

 The essence of IoT architectures involves how the data is

transported, collected, analyzed, and ultimately acted
upon.
IoT Architectural Drivers
 Scale: The massive scale of IoT end-points (sensors).
 Scale can be met only by using IPv6.

 Security: IoT devices, especially wireless sensor

networks (WSNs), are often physically exposed to the
world. TRACE KTU
 Must support device-level authentication and link
encryption.
IoT Architectural Drivers
 Power, CPU, Memory and Speed: Due to the massive
scale and longer distances, the networks are often
constrained, lossy, and capable of supporting only
minimal data rates.
 New last-mile wireless technologies are needed to
TRACE KTU
support constrained IoT devices over long distances.

 Massive Volume of Data: The sensors generate a

massive amount of data on a daily basis.
 Data analytics capabilities need to be distributed
throughout the IoT network, from the edge to the cloud.
IoT Architectural Drivers

 The need for data to be analyzed in real time: Traditional

IT networks perform scheduled batch processing of data,
IoT data needs to be analyzed and responded to in real-
time.
 Analytics software needs to be positioned closer to
TRACE KTU
the edge and should support real-time streaming
analytics.
Comparing IoT Architectures

 Two of the best-known architectures are

 oneM2M

 IoT World Forum (IoTWF)

TRACE KTU
OneM2M IoT Architecture

 To standardize the rapidly growing field of machine-to-

machine (M2M) communications, the European
Telecommunications Standards Institute (ETSI) created
the M2M Technical Committee in 2008.


TRACE KTU
One of the greatest challenges in designing an IoT
architecture is dealing with the heterogeneity of devices,
software, and access methods.
OneM2M IoT Architecture

TRACE KTU
OneM2M IoT Architecture

 This architecture divides IoT functions into three

domains:
 Applications Layer

 Services Layer

TRACE KTU
 Network Layer.

 Applications Layer ensures connectivity between

devices and their applications.
 Services Layer include the physical network that the IoT
applications run on, the underlying management
protocols, and the hardware.
OneM2M IoT Architecture

 Network Layer: This is the communication domain for

the IoT devices and endpoints. It includes the devices
themselves and the communication network that links
them.

TRACE KTU
IoT World Forum (IoTWF) Architecture

 In 2014 the IoTWF architectural committee (led by

Cisco, IBM, Rockwell Automation, and others)
published a seven-layer IoT architectural reference
model.

functions
TRACE KTU
Each of the seven layers is broken down into specific
IoT World Forum (IoTWF) Architecture

TRACE KTU
IoT World Forum (IoTWF) Architecture

 Layer 1: Physical Devices and Controllers - “things” in

the Internet of Things, including the various
endpoint devices and sensors that send and receive
information. Their primary function is generating data

 TRACE KTU
Layer 2: Connectivity Layer - For reliable and timely
transmission of data. Transmission between Layer 1 and
Layer 3.
IoT World Forum (IoTWF) Architecture

TRACE KTU
IoT World Forum (IoTWF) Architecture

 Layer 3: Edge Computing Layer - Edge computing is

often referred to as the “fog” layer. The function is on
data reduction and converting network data that is ready
for storage and processing by higher layers.

 TRACE KTU
Layer 4: Data Accumulation Layer - Captures data and
stores it so it is usable by applications when necessary.
Converts event-based data to query-based processing.
IoT World Forum (IoTWF) Architecture

 Layer 5: Data abstraction layer - Reconciles multiple

data formats and ensures consistent semantics from
various sources. Confirms that the data set is complete
and consolidates data into one place or multiple data
stores using virtualization.
TRACE KTU
 Layer 6: Application Layer - Interprets data using
software applications. Applications may monitor,
control, and provide reports based on the
analysis of the data.
IoT World Forum (IoTWF) Architecture

 Layer 7: Collaboration and processes layer - Consumes

and shares the application information. This layer can
change business processes and delivers the
benefits of IoT.

TRACE KTU
A Simplified IoT Architecture

TRACE KTU
A Simplified IoT Architecture

 This framework is presented as two parallel stacks:

1. The Core IoT Functional Stack.
2. The IoT Data Management and Compute Stack

TRACE KTU
1. The Core IoT Functional Stack

 Layer 1: Things: Sensors and Actuators Layer:

 They can be

 Battery-powered or power-connected

 Mobile or static

TRACE KTU
 Low or high reporting frequency

 Simple or rich data: Quantity of data exchanged

 Report range: Distance to gateway

 Object density per cell: number of smart objects

(with a similar need to communicate) over a
given area
1. The Core IoT Functional Stack

 Layer 2: Communications Network Layer: This layer has

4 sub layers
a. Access Network Sublayer
b. Gateways and Backhaul Network Sublayer

TRACE KTU
c. Network Transport Sublayer
d. IoT Network Management Sublayer
1. The Core IoT Functional Stack

a. Access Network Sublayer:

 This is typically made up of wireless (802.11ah,
802.15.4g, and LoRa) or Wired technologies.
 Parameter determining the choice of access

TRACE KTU
technology:
 Range between the smart object and the
information collector.
 Topology: Point-to-Point or Point-to-Multipoint
(Mesh or Star Topology is used)
1. The Core IoT Functional Stack

TRACE KTU

Access Technologies and Distances

1. The Core IoT Functional Stack

b. Gateways and Backhaul Sublayer:

 Data received from the sensor through an access
technology needs to be forwarded to another
medium (the backhaul) and transported to the
central station called gateway.
TRACE KTU
 Smart objects or gateways can be static or mobile.

 It can use Wi-Fi (802.11ah) or WiMAX (802.16)

technology or Ethernet or Cellular technology for
communication.
1. The Core IoT Functional Stack

c. Network Transport Sublayer:

 Transport layer protocols built above IP (TCP and
UDP) must be implemented.


TRACE KTU
It should be
 Open and standard-based to accommodate
multiple industries and multiple media.
 Scalable

 Secure (TCP uses TLS/SSL, UDP uses DTLS)

1. The Core IoT Functional Stack

d. IoT Network Management Sublayer:

 Protocols responsible for data transmission
between the smart objects and other systems.
 Networks may use Push model (sensor reports

TRACE KTU
data) or Pull model (Application queries sensors)
or Hybrid model.
 Protocols in this layer include: HTTP, WebSocket
with MQTT (Message Queuing Telemetry
Transport), XMPP (Extensible Messaging and
Presence Protocol), CoAP (Constrained
Application Protocol).
1. The Core IoT Functional Stack
 Layer 3: Applications and Analytics Layer:
 An application needs to process the collected data,
and make intelligent decision and, in turn, instruct
the “things” to adapt to the analyzed conditions and
change their behaviors or parameters.
TRACE KTU
 Applications types include:
 Analytics Applications (collect, process and
display).
 Control Applications (controls the behavior of
the smart object).
2. IoT Data Management and Compute Stack
 The data generated by IoT sensors is one of the biggest
challenges.
 This stack deals with how and where data is filtered,
aggregated, stored, and analyzed.
 In most cases, the data processing location is outside the


TRACE KTU
smart object (Mostly cloud).
One advantage of this model is simplicity.
 Limitations of this model:
 Network bandwidth, Cloud overhead, Latency, Local
efficiency
2. IoT Data Management and Compute Stack

TRACE KTU

Traditional IT Cloud Computing Model

2. IoT Data Management and Compute Stack
 IoT systems function differently. Several data-related
problems need to be addressed.
 Bandwidth is very limited: Many devices are connected
(<10 Kbps per device)
 Latency very high: 100-1000 ms
 TRACE KTU
Backhaul network from gateway can be unreliable and
also expensive: 3G/LTE or even satellite links
 The volume of data transmitted over the backhaul can be
high, and much of the data may not be important.
 Big data is getting biger: Storing and analyzing all
sensor data in the cloud is impractical.
Fog Computing
 The solution to these challenges is to distribute data
management throughout the IoT system, as close to the
edge of the IP network as possible.
 One of the best solutions is fog computing.
 Any device with computing, storage, and network


TRACE KTU
connectivity can be a fog node.
Examples: switches, routers, embedded servers,
industrial controllers, and IoT gateways.
 The fog layer provides a distributed edge control loop
capability, where devices can be monitored, con-
trolled, and analyzed in real time without the need to
wait for servers in the cloud.
Fog Computing

TRACE KTU
Fog Computing - Properties

 Contextual location awareness and low latency

 Geographic distribution
 Deployment near IoT endpoints
 Wireless communication between the fog and the IoT
endpoint TRACE KTU
 Use for real-time interactions
Edge Computing
 Edge computing is also called “mist” computing.
 If clouds exist in the sky, and fog sits near the ground,
then mist is what actually sits on the ground.


TRACE KTU
Some IoT endpoints have enough compute capabilities
to perform at least low-level analytics and filtering to
make basic decisions.
The Hierarchy of Edge, Fog, and Cloud
 Network, compute, and data storage resources are
organized in hierarchical manner.
 At each stage, data is collected, analyzed, and responded
to when necessary, according to the capabilities of the
resources at each layer.
 TRACE KTU
As data needs to be sent to the cloud, the latency
becomes higher.
 In many cases both edge and fog resources will use
different operating systems, have different CPU and data
storage capabilities, and have different energy
consumption profiles.
The Hierarchy of Edge, Fog, and Cloud

TRACE KTU

Distributed Compute and Data Management Across an IoT System