CS578: Internet of Things Traditional Data Flow in IoT

IoT Architecture

Dr. Manas Khatua IoT Network Core Network

Assistant Professor, Dept. of CSE, IIT Guwahati
E-mail: [email protected] Image Source: http://events17.linuxfoundation.org/sites/events/files/slides/Intelligence%20at%20the%20Edge.pdf

“We must have life-building, man-making, character-making assimilation of ideas.” – Swami Vivekananda 03-08-2023 Dr. Manas Khatua 2

What is Architectural Plan? Basic 3-Layer architecture

Smart
• Perception layer is the physical layer,
 In present days, networks Home which has sensors for sensing and
run the modern business gathering information about the
environment.
 So, it should never be built
without careful planning • Network layer is responsible for
connecting to other smart things,
network devices, and servers. Its
features are also used for
 Architecture is how you design (i.e. graphical transmitting and processing sensor
Driving forces: data.
structure) your application or solution.  Scale
 Security • Application layer is responsible for
 Essence of IoT architecture:  Constrained devices delivering application specific
 how the data is  Massive data services to the user.
 transported,
 collected,  Data analysis – For example, smart homes, smart
cities, smart health, etc.
 analyzed, and  Support to legacy
 ultimately acted upon. devices
Source: https://www.pinterest.com/pin/641129696942354756/

03-08-2023 Dr. Manas Khatua 3 03-08-2023 Dr. Manas Khatua 4

 Emergence of Standard IoT Architecture oneM2M Architecture
• However, the basic 3-layer architecture did not address many issues. Goal of oneM2M architecture:
– e.g. Compatibility, Safety & Security, Reusability, Heterogeneity, etc.
• to create a common services layer, which can be readily embedded in field
• In fact, the IoT did not have any standard defined architecture of working which is strictly followed universally. devices to allow communication with application servers.

Few Issues:

 Highly fragmented marked with limited vendor-

specific applications

 Each silo contains its own technologies without

interoperability

 Incompatibility for seamless integration between

heterogeneous applications and devices
Challenges in IoT Architecture: • Using the smart building use case, a
• heterogeneity of devices, security application can detect when
• So, in the past several years, architectural standards and frameworks have emerged • heterogeneity of software, nobody is in the building.
• Heterogeneity of access methods • It could then trigger lights to be switched
• Two best-known architectures:
– oneM2M architecture
off and for the HVAC system to operate
– IoT World Forum architecture on a reduced setting.
Source: https://onem2m.org/using-onem2m/developers/basics Image Source: https://onem2m.org/using-onem2m/developers/basics

03-08-2023 Dr. Manas Khatua 5 03-08-2023 Dr. Manas Khatua 6

oneM2M Architecture oneM2M Architecture

• Proposed by Européen Télécommunications Standards Institute (ETSI) • Proposed by Européen Télécommunications Standards Institute (ETSI)
• oneM2M architecture divides IoT functions into three major domains. • oneM2M architecture divides IoT functions into three major domains.
First First Second
• horizontal framework
• Defines application-layer protocols across the vertical
industry applications.
• Attempts to standardize northbound API
• API stands for Application Programming Interface.
• Include:
Note: Interface can be thought of as a contract of • the physical
service between two applications or parties. This network that the
contract defines how the two communicate with each
other using requests and responses.
IoT applications
run on. (e.g.
backhaul network)
• A northbound interface allows a particular • the underlying
component of a network to communicate with a management
higher-level component. protocols
• the hardware
• Applications have their own sets of data models
cont…
03-08-2023 Dr. Manas Khatua 7 03-08-2023 Dr. Manas Khatua 8
 oneM2M Architecture oneM2M Architecture
• Proposed by European Telecommunications Standards Institute (ETSI) • Proposed by European Telecommunications Standards Institute (ETSI)
• oneM2M architecture divides IoT functions into three major domains. • oneM2M architecture divides IoT functions into three major domains.
First Second First Second Third
• top is the common
services layer
IoT devices, &
• This layer adds APIs and communication
middleware supporting network
third-party services and (802.15.4, LoRa,
WiFi)
applications.

• Service layer can be

readily embedded within
various hardware and
software nodes

• A RESTful API uses HTTP

requests to GET, PUT,
POST and DELETE data.
03-08-2023 Dr. Manas Khatua 9 03-08-2023 Dr. Manas Khatua 10

IoTWF Architecture – 7 Layer Stack Layers 1 & 2

• IoTWF architectural committee (led by Cisco, • Control flowing from the
IBM, Rockwell Automation, and others) center to the edge Layer 1: Physical Devices Layer 2: Connectivity Layer
and Controllers Layer • focus is on connectivity
• Decompose the IoT
problem into smaller parts
• home of the “things” in IoT
• Identify different
technologies at each layer • “things” can be from a
microscopic sensors to giant
• Different parts of a system machines in a factory
can be provided by
different vendors • primary function is
generating data
• Tiered security model
enforced at the transition
points between levels • capable of being queried
• offers a clean, simplified perspective on IoT and/or controlled over a
• includes edge computing, data storage, and access • Define interfaces that network.
• succinct way of visualizing IoT from a technical perspective leads to interoperability

03-08-2023 Dr. Manas Khatua 11 03-08-2023 Dr. Manas Khatua 12

 Layer 3 : Fog Layer Upper Layers: Layers 4–7
Basic principle:

Layer 3: Edge Computing Layer information processing is initiated as

early and as close to the edge of the
• often referred to as the “fog” layer network as possible.
• emphasis is on
– Data reduction by filtering and Layers Functions
cleaning up
Layer 4: Data Accumulation • Captures data and stores it for applications
– Reformatting and compressing data • Convert event-based data to query-based processing
Layer 5: Data Abstraction • Reconciles multiple data formats
– Initial processing of data (e.g. alert
generation, data validation, etc) • Ensures consistent semantics for various data sources
• Confirmation about dataset completeness
Layer 6: Application • Interpret data using software applications
• Applications may monitor, control, and provide report
based on analysing the data
Layer 7: Collaboration and • Consumes and shares the application information
processes • Collaborating and communicating IoT information
03-08-2023 Dr. Manas Khatua 13 03-08-2023 Dr. Manas Khatua 14

Simplified IoT Architecture Lessons Learned

• It highlights the fundamental building blocks that are common to most IoT
systems and which is intended to help in designing an IoT network.

• IoT architectural framework is presented as two parallel stacks  What is the need of IoT architecture?
• Core IoT Functional Stack
• IoT Data Management and Compute Stack  Different type of IoT Architectures

 About oneM2M architecture

 About IoT WF architecture

 About Simplified IoT Architecture

03-08-2023 Dr. Manas Khatua 15 03-08-2023 Dr. Manas Khatua 16

 Figures and slide materials are taken from the following sources:

1. David Hanes et al., “IoT Fundamentals: Networking Technologies, Protocols,

and Use Cases for the Internet of Things”, 1st Edition, 2018, Pearson India.

03-08-2023 Dr. Manas Khatua 17