Internet of Things (IoTE 540)

L-T-P-[C] 4-0-0-[4]

Outline of the course

Introduction to IoT, need, technologies used in IoT,

benefits of IoTs, IoT Implementation Challenges,
Applications, IoT structure, IoT Components, Working
process of IoT, IoT Networking – IoT Architecture,
OneM2M Model, Reference model, IoT Service Oriented
Architecture, challenges, Components of internet of
things, - Sensor, Actuator…

IoT Protocols – IEEE 804.14.5, ZigBee, Connectivity

(6LowPAN, RPL), Communication / Transport (Wi-Fi,
Bluetooth, LPWAN), Discovery Protocols (Physical Web,
mDNS, DNS-SD), Data Protocol (MQTT, CoAP, AMQP,
Web Socket, Node), Device Management (TR-069,
OMA-DM), Semantic (JSON-LD, Web Thing Model)

1
Courseware and Reference Books
Text Books:
 Mayur Ramgir, Internet of Things- Architecture, Implementation, and Security, Pearson Education India,
2019.
Reference Books:
1. Raj Kamal, INTERNET OF THINGS Architecture and Design Principles, McGraw Hill Education
(India) Private Limited, 2017.
2. S. Misra, A. Mukherjee, and A. Roy, Introduction to IoT, Cambridge University Press, 2020.
3. S. Misra, C. Roy, and A. Mukerjee, 2020, Introduction to Industrial Internet of Things and Industry 4.0,
CRC Press, 2020
4. Research Papers.

2
 Lecture No 8

Two of the best-known architecture are those

supported by oneM2M and the IoT World Forum
(IoTWF).
Modified OSI Model for the IoT/M2M Systems

Architectural layers in a modified OSI model for Internet

of smart streetlights application

3
 Gather + Enrich + Stream + (Manage + Acquire +
Organise + Analyse)
= IoT Applications and Services

Modifications are also at the data-link layer 2 (L2) and

physical layer 1 (L1). The new layers are data-adaptation
(new L2) and physical cum data-link (new L1).

The data-adaptation layer includes a gateway.

The gateway enables communication between the
devices network and the web.

 L1: It consists of smart sensing and data-link circuits

with each streetlight transferring the sensed data to
L2.

 L2: It consists of a group-controller which receives

data of each group through Bluetooth or ZigBee,
aggregates and compacts the data for
communication to the Internet, and controls the
group streetlights as per the program commands
from a central station.
4
 L3: It communicates a network stream on the Internet
to the next layer.

 L4: The transport layer does device identity

management, identity registry and data routing to the
next layer

 L5: The application-support layer does data

managing, acquiring, organising and analysing, and
functionalities of standard protocols such as CoAP,
UDP and IP.
Constrained Application Protocol (CoAP) is a specialized Internet Application
Protocol for constrained devices, as defined in RFC 7252.

 L6: The application layer enables remote

programming and issue of central station directions
to switch on-off and commands of services to the
controllers along with monitoring each group of
streetlights in the whole city.

5
The oneM2M IoT Standardized Architecture

In effort 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.

The goal of this committee was to create a common

architecture that would help accelerate the adoption of
M2M applications and devices.

Over the time, the scope has expanded to include the

Internet of Things.

6
 Recognizing this need, in 2012 ETSI and 13 other founding members launched one
M2M as a global initiative designed to promote efficient M2M communication
systems and IoT.

One of the greatest challenges in designing an IoT

architecture is dealing with the heterogeneity of devices,
software, and access methods.

By developing a horizontal platform architecture,

oneM2M is developing standards that allow
interoperability at all levels of the IoT stack.

The one M2M architecture divides IoT functions into three

major domains: the application layer, the services layer
and the network layer.

7
 Applications Layer
The one M2M architecture gives major attention to
connectivity between devices and their applications.
This domain includes the application layer protocols
and attempts to standardize northbound API
definitions for interaction with Business Intelligence
(BI) Systems.

Applications tend to be industry specific and have

their own sets of data models and thus they are
shown as vertical entities.

 Services Layer
This layer is shown as a horizontal framework across
the vertical industry applications.

At this layer, horizontal modules include the physical

network that the IoT applications run on, the
underlying management protocols, and the
hardware.

8
Examples include backhaul communications via
cellular, MPLS (Multiprotocol label switching)
networks, VPNs and so on.

The term backhaul is often used in telecommunications and

refers to transmitting a signal from a remote site or network
to another site, usually a central one.

Backhaul usually implies a high-capacity line, meaning

high-speed lines capable of transmitting
high bandwidth at very fast speeds.

Riding on top is the common services layer.

This conceptual layer adds APIs and middleware

supporting third party services and applications.

9
 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.

Examples include wireless mesh technologies, such as

IEEE 802.15.4, and wireless point-to-multipoint systems,
such as IEEE 801.11ah

IEEE 802.15.4 is a technical standard which defines the operation of

low-rate wireless personal area networks (LR-WPANs).

IEEE 802.11ah is a wireless networking protocol published in 2017 called Wi-Fi

HaLow (pronounced "HEY-Low") as an amendment of the

IEEE 802.11-2007 wireless networking standard. It uses 900 MHz license-exempt bands to
provide extended-range Wi-Fi networks, compared to conventional Wi-Fi networks
operating in the 2.4 GHz and 5 GHz bands.

10
 In many cases, the smart (and sometimes not so smart) devices
communicate with each other.

 In other cases, machine-to-machine communication is not

necessary, and the devices communicate through a field area
network (FAN) to use case specific apps in the IoT application
domain.

 Therefore, the device domain also includes the gateway device,

which provides communications up into the core network and acts
as a demarcation point between the device and network domains.

11
The IoT World Forum (IoTWF) Standardized
Architecture

 IoTWF architectural committee published 7- layer

IoT architectural reference model in 2014.

 This committee was led by Cisco, IBM, Rockwell

Automation, and others

Rockwell Automation covers control systems, industrial control components,

information software, motor control devices, sensing devices, network
technology, safety technology, and industrial security.

 While various IoT reference models exist, the one put

forth by the IoT World Forum offers clean, simplified
perspective on IoT

 Includes edge computing, data storage, and access.

12
 Defines set of levels with control flowing from the
center (cloud service or dedicated data center), to
the edge

 May includes sensors, devices, machines, and other

types of intelligent end nodes

 In general, data travels up stack, originating from

edge, and goes northbound to the center

13
Using this model, we are able to achieve:

 Decompose the IoT problem into smaller parts

 Identify different technologies at each layer and how

they relate to one another

 Define a system in which different parts can be

provided by different vendors

 Have a process of defining interfaces that leads to

interoperability

 Define a tiered security model that is enforced at the

transition points between levels

14
Layer -1 (Physical devices)
 The first layer is concerned with the controllers and
physical equipment which is used to control devices.

 These are popularly known as “Things” in the

Internet of Things terminology (jargon).

 This layer is home to the “things” in the IoT, including

various endpoint devices & sensors

 Size of these “things” can range from almost tiny

sensors to huge machines in factory

 Their primary function is generating data and being

capable of being controlled over network
These devices send and receive data.

 This data can include a description of the device

status or information from the sensor.

15
 This information might be then processed by a local
controller and transmitted with the help of near field
communications (NFC).

 When IoT devices are concerned via a network, they

convert analog data to digital data.

16
Layer -2 (Connectivity)
(Connectivity – Communication and Processing Units)

 This second layer is concerned with the relay of data

which is communicated between devices via multiple
different networks.

This layer is used to execute the following tasks.

 It is used to set up a connection with the first layer

devices.

 It is used for trustable delivery throughout the

network.

17
 It is used to implement different device compatible
protocol.

 It is used for routing and switching.

 It is used to translate for protocol.

 It serves as an added protection measure for the

network.

 It is used for networking analytics.

18
Layer -3 (Edge computing)
(Edge computing – Data Element Analysis and
Transformation)

 In order to ensure that the fourth layer understands

all the datasets, the third layer, edge computing layer
is responsible for data formatting.

This layer can perform the following tasks.

 It can filter data.

 It can cleanup data.
 It can aggregate data.
 It can provide evaluation for validation so data can
be processed by the fourth layer.
19
 It is used to reform data so it can help in more
complex and higher-level computations.

 It is used for expanding and decoding.

 It is used to compress data so its impact on data and

traffic is reduced for the network.

 It is used to generate events for any alerts.

20
Layer -4 (Data Accumulation)

Capture data and stores it so it is usable by applications

when necessary.
Converts event-based data to query-based processing.

 The data from the sensor is constantly changing.

Therefore, the fourth layer is tasked to convert it.

 This layer maintains the data in a format that is

extremely accessible.

After data is filtered through this layer, a lot of data is

decreased.

21
Layer -5 (Data Abstraction)

The fifth layer uses all the important data is used to follow
certain properties of the stored data.

It then provides the data to the application layer so it can

process further.

 Reconciles multiple data formats and ensures

consistent semantics from various sources.

 Confirms that the data set is complete and

consolidates data intone place or multiple data
stores using virtualization.

 The objective of this layer to render data along with

its such a strategy that can help developers to write
easier applications.

22
Layer -6 (Application)

The sixth layer is responsible to process data in order to

ensure that it accessible for everyone.

 It is associated with both the physical and software

layer.

 It is used for data interpretation to create reports.

Business intelligence tools are also used in this layer.

 The objective, applications may monitor, control, and

provide reports based on the analysis of data.

 Interprets data using software applications.

23
Layer -7 (Collaboration and Processes)

The seventh layer offers action or response that can help

against the provided data.

For example, this action can be electromechanical

device’s actuation after a trigger from the controller.

 Consumes and shares the applications information.

 Collaborating on and communicating IoT information

often requires multiple steps, and it is what makes
IoT useful.

 This layer can change business processes and

delivers the benefits of IoT.

24
Summary

We learnt

(i) IoT Architecture - oneM2M and

(ii) IoT World Forum (IoTWF)

25