Please read this disclaimer before proceeding:

This document is confidential and intended solely for the educational purpose of
RMK Group of Educational Institutions. If you have received this document
through email in error, please notify the system manager. This document
contains proprietary information and is intended only to the respective group /
learning community as intended. If you are not the addressee you should not
disseminate, distribute or copy through e-mail. Please notify the sender
immediately by e-mail if you have received this document by mistake and delete
this document from your system. If you are not the intended recipient you are
notified that disclosing, copying, distributing or taking any action in reliance on
the contents of this information is strictly prohibited.
20EC004 Industrial IoT
Applications
Department: CSE, CSD & IT
Batch/Year: 2023 -2024/ IVYear

Created by: Dr. T Ramesh(CSE),

Dr.Jeno Jasmine J(CSE),

Date: 23.03.2023
 CONTENTS

1 Course Objectives

2 Pre Requisites

3 Syllabus

4 Course outcomes

5 CO- PO/PSO Mapping

6 Lecture Plan

7 Lecture Notes

8 Assignments

9 Part A Q & A

10 Part B Questions

11 Activity based learning

12 Supportive online Certification courses

13 Real time Applications in day to day life and to Industry

14 Contents beyond the Syllabus

15 Assessment Schedule

16 Prescribed Text Books & Reference Books

17 Mini Project suggestions

5
1. Course Objectives

6
 1. Course Objectives

OBJECTIVES:

OUTCOMES: On successful completion of this course, the student will be able to

CO1: Describe IOT, IIOT

CO2: Understand various IoT Layers and their relative importance
CO3: Interpret the requirements of IIOT sensors and understand the role of
actuators.
CO4: Study various IoT platforms and Security
CO5: Realize the importance of Data Analytics in IoT
CO6: Design various applications using IIoT in manufacturing sector

7
2. Pre Requisites

8
 3. PRE REQUISITES

Pre-requisite Chart

20IT909 Advanced Java- JEE

20IT501 Web Development Frameworks

9
3. Syllabus

10
 3. Syllabus
20EC004:Industrial IoT Applications LTPC:3003
UNIT I INTRODUCTION
Introduction to IOT, What is IIOT? IOT Vs. IIOT, History of IIOT, Components of IIOT –
Sensors,Interface, Networks, People Process, Hype cycle, IOT Market, Trends; future Real life
examples,Key terms IOT Platform, Interfaces, API, clouds, Data Management Analytics,
Mining Manipulation;Role of IIOT in Manufacturing Processes, Use of IIOT in plant
maintenance practices, Sustainability through Business excellence tools Challenges, Benefits
in implementing IIOT
UNIT II ARCHITECTURE AND PROTOCOLS
Overview of IOT components; Various Architectures of IOT and IIOT, Advantages
&disadvantages,Industrial Internet - Reference Architecture; IIOT System components:
Sensors, Gateways, Routers,Modem, Cloud brokers, servers and its integration, WSN, WSN
network design for IOT; Need for protocols, Wi-Fi, Zigbee, Bacnet, IIOT protocols COAP,
MQTT, 6LoWPAN, LWM2M, AMPQ.
UNIT III SENSORS AND INTERFACING
Introduction to sensors, Transducers, Classification, Roles of sensors in IIOT , Various types
of sensors ,Design of sensors, sensor architecture, special requirements for IIOT sensors,
Role of actuators, types of actuators. Hardwire the sensors with different protocols such as
HART, MODBUS-Serial,Parallel,Ethernet, BACNet , Current, M2M
UNIT IV CLOUD, SECURITY AND GOVERNANCE
IIOT cloud platforms: Overview of cots cloud platforms, predix, thingworks, azure,. Data
analytics, cloud services, Business models: Saas, Paas, Iaas; Introduction to web security,
Conventional web technology and relationship with IIOT, Vulnerabilities of IoT, IoT security
tomography and layered attacker model,Identity establishment, Access control, Message
integrity; Management aspects of cyber security
UNIT V IOT ANALYTICS AND APPLICATIONS
IOT Analytics : Role of Analytics in IOT, Data visualization Techniques, Statistical Methods;
IOT Applications : Smart Metering, e-Health Body Area Networks, City Automation,
Automotive Applications, Plant Automation, Real life examples of IIOT in Manufacturing
Sector

11
4. Course outcomes

12
 5. COURSE OUTCOME

At the end of the course, the student should be able to:

COURSE OUTCOMES HKL

CO1: Describe IOT, IIOT K2

CO2: Understand various IoT Layers and their relative importance K3

CO3: Understand various IoT Layers and their relative importance K3

CO4: Understand various IoT Layers and their relative importance K3

CO5: Realize the importance of Data Analytics in IoT K4

CO6: Realize the importance of Data Analytics in IoT K5

HKL = Highest Knowledge Level

7
13
5. CO- PO/PSO Mapping

14
 5. CO- PO/PSO Mapping

PO PO PO PO PO PO PO PO PO PO1 PO1 PO1 POS POS POS

CO #
1 2 3 4 5 6 7 8 9 0 1 2 1 2 3
CO1 3 2 2 3 2 _ _ 3 2 3 _ 3 3 3 _
CO2 3 2 2 2 2 _ _ 3 2 2 _ 3 3 3 _
CO3 3 2 2 3 3 _ _ 3 2 2 _ 3 3 3 _
CO4 3 2 2 3 2 _ _ 3 2 2 _ 3 3 3 _
CO5 3 2 2 1 1 _ _ 3 2 2 _ 3 3 3 _
CO6 3 2 1 1 2 _ _ 2 2 2 _ 2 2 2 _
6. Lecture Plan

16
 6. Lecture Plan

Duration Course Delivery Plan

S.
Planned Delivery
No From To Topics
Date Data

Overview of IOT components; Various

1 Architectures of IOT and IIOT, 19.08.2023 19.08.2023

Advantages &disadvantages, Industrial

2 Internet - 22.08.2023 22.08.2023

3 Reference Architecture; 23.08.2023 23.08.2023

IIOT System components: Sensors,

4 Gateways, Routers, Modem, 24.08.2023 24.08.2023
Cloud brokers, servers and its
integration, WSN, WSN network design
5 for IOT; 25.08.2023 25.08.2023
18.08.2023 29.08.2023

6 Need for protocols, 26.08.2023 26.08.2023

7 Wi-Fi, Zigbee, Bacnet, IIOT protocols 28.08.2023 28.08.2023

8 –COAP, MQTT, 29.08.2023 29.08.2023

30.08.2023 30.08.2023
9 6LoWPAN, LWM2M, AMPQ.

31.08.2023 31.08.2023
10 Revision

17
7. Lecture Notes

18
 UNIT II

ARCHITECTURE AND PROTOCOLS

 UNIT-II- ARCHITECTURE AND PROTOCOLS

UNIT-II- ARCHITECTURE AND PROTOCOLS

Overview of IOT components:

IoT refers to the network of interconnected devices and objects that can

communicate and exchange data over the internet. These devices are equipped with

sensors, actuators, and communication technologies, allowing them to gather and

transmit data for various purposes. Here are the key components of IoT:

1. Devices/Things: These are the physical objects or devices that are equipped with

sensors, actuators, and communication interfaces to interact with the environment.

They can range from simple sensors to complex devices like smartphones,

wearables, home appliances, industrial machinery, and vehicles.

2. Sensors: Sensors are devices that detect and measure physical attributes such as

temperature, humidity, light, motion, pressure, and more. They collect real-world

data and convert it into a digital format for processing and transmission.

3. Actuators: Actuators are devices that perform actions based on the data received

from sensors or through remote commands. Examples include motors, servos,

solenoids, and relays. Actuators enable devices to have an impact on the physical
 UNIT-II- ARCHITECTURE AND PROTOCOLS

world.

4. Connectivity: IoT devices rely on various connectivity technologies to

communicate with each other and the central systems. Common connectivity options

include Wi-Fi, cellular networks (3G, 4G, 5G), Bluetooth, Zigbee, LoRaWAN, and NFC

(Near Field Communication).

5. Data Processing: The data collected by sensors is often raw and needs processing

to become useful. This is done using microcontrollers, microprocessors, or dedicated

IoT platforms. Processing can involve data filtering, aggregation, transformation,

and even basic analysis at the edge (on the device itself) or in the cloud.

6. IoT Platforms: IoT platforms provide a set of tools and services for managing,

connecting, and analyzing IoT devices and data. They often include features like

device management, data storage, analytics, security, and remote monitoring.

Examples of IoT platforms are AWS IoT, Google Cloud IoT, and Microsoft Azure IoT.

7. Cloud Services: Cloud services play a crucial role in IoT by providing scalable

storage and computational resources. They enable data storage, processing, and

analysis on a larger scale. Cloud platforms can also host applications that interact
 UNIT-II- ARCHITECTURE AND PROTOCOLS

with IoT devices and users.

8. Communication Protocols: IoT devices use various communication protocols to

exchange data. Some common protocols include MQTT (Message Queuing

Telemetry Transport), CoAP (Constrained Application Protocol), HTTP/HTTPS, and

WebSocket. These protocols ensure efficient and secure data transmission.

9. Security Mechanisms: IoT devices are vulnerable to security threats due to their

connectivity and data sharing capabilities. Security mechanisms include encryption,

authentication, authorization, and secure bootstrapping. Ensuring the security of IoT

systems is essential to prevent unauthorized access and data breaches.

10. User Interface: IoT devices often have user interfaces that allow users to interact

with them. This can be through mobile apps, web dashboards, voice commands, or

physical interfaces on the device itself.

11. Data Analytics and Machine Learning: IoT data is valuable for gaining insights

and making predictions. Data analytics and machine learning techniques can be

applied to extract meaningful patterns, optimize processes, and enable predictive

maintenance.
 UNIT-II- ARCHITECTURE AND PROTOCOLS

12. Edge Computing: Edge computing involves processing data closer to the source

(on the device or at a local server) rather than sending all data to the cloud. This

reduces latency and bandwidth usage while enabling real-time or near-real-time

responses.

These components work together to create a network of interconnected devices that

can collect, transmit, and act on data, enabling a wide range of applications across

industries such as healthcare, agriculture, smart cities, industrial automation, and

more.

Various Architectures of IOT and IIOT:

The reference architecture consists of a set of components. Layers can be realized

by means of specific technologies, and we will discuss options for realizing each

component.

There are also some cross-cutting/vertical layers such as access/identity

management.

The layers are

• Client/external communications - Web/Portal, Dashboard, APIs

 UNIT-II- ARCHITECTURE AND PROTOCOLS

• Event processing and analytics (including data storage)

• Aggregation/bus layer – ESB and message broker

• Relevant transports - MQTT/HTTP/XMPP/CoAP/AMQP, etc.

• Devices

The cross-cutting layers are

• Device manager

• Identity and access managements

 UNIT-II- ARCHITECTURE AND PROTOCOLS

THE DEVICE LAYER:

The bottom layer of the architecture is the device layer. Devices can be of various

types, butin order to be considered as IoT devices, they must have some

communications that eitherindirectly or directly attaches to the Internet. Examples

of direct connections are

• Arduino with Arduino Ethernet connection

• Arduino Yun with a Wi-Fi connection

• Raspberry Pi connected via Ethernet or Wi-Fi

• Intel Galileo connected via Ethernet or

Wi-Fi Examples of indirectly connected devices include

• ZigBee devices connected via a ZigBee gateway

• Bluetooth or Bluetooth Low Energy devices connecting via a mobile phone

• Devices communicating via low power radios to a

Raspberry Pi There are many more such examples of each type.

Each device typically needs an identity.

The identity may be one of the following:

• A unique identifier (UUID) burnt into the device (typically part of the System-on

Chip, orprovided by a secondary chip)

•A UUID provided by the radio subsystem (e.g. Bluetooth identifier, Wi-Fi MAC
 UNIT-II- ARCHITECTURE AND PROTOCOLS

address)

• An OAuth2 Refresh/Bearer Token (this may be in addition to one of the above)

• An identifier stored in nonvolatile memory such as EEPROM.

For the reference architecture we recommend that every device has a UUID

(preferably anunchangeable ID provided by the core hardware) as well as an OAuth2

Refresh and Bearertoken stored in EEPROM. The specification is based on HTTP;

however, (as we will discussin the communications section) the reference

architecture also supports these flows overMQTT.

COMMUNICATIONS LAYER

The communication layer supports the connectivity of the devices. There are

multiple potential protocols for communication between the devices and the cloud.

The most well-known three potential protocols are

• HTTP/HTTPS (and RESTful approaches on those)

• MQTT 3.1/3.1.1(Message Queuing Telemetry Transport)

• Constrained application protocol (CoAP)

HTTP is well known, and there are many libraries that support it. Because it

is a simple textbased protocol, many small devices such as 8-bit controllers can only
 UNIT-II- ARCHITECTURE AND PROTOCOLS

partially support theprotocol – for example enough code to POST or GET a resource.

The larger 32-bit baseddevices can utilize full HTTP client libraries that properly

implement the whole protocol.

There are several protocols optimized for IoT use. The two best known are

MQTT6 and CoAP7. MQTT was invented in 1999 to solve issues in embedded

systems and SCADA. It

has been through some iterations and the current version (3.1.1) is undergoing

standardizationin the OASIS MQTT Technical Committee8. MQTT is a publish-

subscribe messaging systembased on a broker model. The protocol has a very small

overhead (as little as 2 bytes permessage), and was designed to support lossy and

intermittently connected networks.

MQTTwas designed to flow over TCP. In addition, there is an associated

specification designed forZigBee-style networks called MQTT-SN (Sensor Networks).

CoAP is a protocol from theIETF that is designed to provide a RESTful application

protocol modeled on HTTPsemantics, but with a much smaller footprint and a binary

rather than a text- based approach.

CoAP is a more traditional client-server approach rather than a brokered

 UNIT-II- ARCHITECTURE AND PROTOCOLS

approach. CoAP isdesigned to be used over UDP. For the reference architecture we

have opted to select MQTTas the preferred device communication protocol, with

HTTP as an alternative option.

The reasons to select MQTT and not CoAP at this stage are

• Better adoption and wider library support for MQTT;

• Simplified bridging into existing event collection and event processing systems;

and

• Simpler connectivity over firewalls and NAT networks

However, both protocols have specific strengths (and weaknesses) and so there will

be somesituations where CoAP may be preferable and could be swapped in. In order

to supportMQTT we need to have an MQTT broker in the architecture as well as

device libraries.

In the case where the main communication is based on HTTP, thetraditional

approach for sending data to the device would be to use HTTP Polling. This isvery

inefficient and costly, both in terms of network traffic as well as power requirements.

The modern replacement for this is the WebSocket protocol9 that allows an HTTP

connection to be upgraded into a full two-way connection. This then acts as a socket
 UNIT-II- ARCHITECTURE AND PROTOCOLS

channel(similar to a pure TCP channel) between the server and client. Once that has

been established,it is up to the system to choose an ongoing protocol to tunnel over

the connection.

For thereference architecture we once again recommend using MQTT as a protocol

with WebSockets. In some cases, MQTT over Web Sockets will be the only protocol.

This is because itis even more firewall-friendly than the base MQTT specification as

well as supporting purebrowser/JavaScript clients using the same protocol.

Note that while there is some support forWeb Sockets on small controllers, such as

Arduino, the combination of network code, HTTPand Web Sockets would utilize most

of the available code space on a typical Arduino 8-bitdevice. Therefore, we only

recommend the use of Web Sockets on the larger 32-bit devices.

AGGREGATION/BUS LAYER:

An important layer of the architecture is the layer that aggregates and brokers

communications. This is an important layer for three reasons:

 UNIT-II- ARCHITECTURE AND PROTOCOLS

1. The ability to support an HTTP server and/or an MQTT broker to talk to the

devices

2. The ability to aggregate and combine communications from different devices

and to route communications to a specific device (possibly via a gateway).

3. The ability to bridge and transform between different protocols, e.g. to offer

HTTP basedAPIs that are mediated into an MQTT message going to the

device. The aggregation/buslayer provides these capabilities as well as

adapting into legacy protocols.

The bus layer may also provide some simple correlation and mapping from different

correlation models (e.g.mapping a device ID into an owner‘s ID or vice-versa).

Finally, the aggregation/bus layer needs to perform two key security roles. It must

be able to act as an OAuth2 Resource Server(validating Bearer Tokens and

associated resource access scopes). It must also be able to act as a policy

enforcement point (PEP) for policy-based access. In this model, the bus makes

requests to the identity and access management layer to validate access requests.

The identity and access management layer acts as a policy decision point (PDP) in

this process. The bus layer then implements the results of these calls to the PDP to
 UNIT-II- ARCHITECTURE AND PROTOCOLS

either allow or disallow resource access.

EVENT PROCESSING AND ANALYTICS LAYER:

This layer takes the events from the bus and provides the ability to process and act

upon these events. A core capability here is the requirement to store the data into

a database. This may happen in three forms. The traditional model here would be

to write a server-side application, e.g. this could be a JAX-RS application backed by

a database. However, there are many approaches where we can support more agile

approaches. The first of these is to use a big data analytics platform.

This is a cloud calable platform that supports technologies such as Apache Hadoop

to provide highly scalable map reduce analytics on the data coming from then

devices. The second approach is to support complex event processing to initiate

near real time activities and actions based on data from the devices and from the

rest of the system.

Our recommended approach in this space is to use the following approaches:

• Highly scalable, column-based data storage for storing events

 UNIT-II- ARCHITECTURE AND PROTOCOLS

• Map-reduce for long-running batch-oriented processing of data

• Complex event processing for fast in-memory processing and near real-time

reaction and autonomic actions based on the data and activity of devices and other

systems

• In addition, this layer may support traditional application processing platforms,

such as JavaBeans, JAX-RS logic, message-driven beans, or alternatives, such as

node.js, PHP, Ruby or Python.

CLIENT/EXTERNAL COMMUNICATIONS LAYER:

The reference architecture needs to provide a way for these devices to communicate

outside of the device-oriented system. This includes three main approaches. Firstly,

we need thea bility to create web-based front-ends and portals that interact with

devices and with the event-processing layer. Secondly, we need the ability to create

dashboards that offer views into analytics and event processing. Finally, we need to
 UNIT-II- ARCHITECTURE AND PROTOCOLS

be able to interact with systems outside this network using machine-to-machine

communications (APIs). These APIs need to be managed and controlled and this

happens in an API management system. There recommended approach to building

the web front end is to utilize a modular front-end architecture, such as a portal,

which allows simple fast composition of useful UIs.

Of course, the architecture also supports existing Web server-side technology, such

as Java Servlets/JSP, PHP, Python, Ruby, etc. Our recommended approach is based

on the Java framework and the most popular Java-based web server, Apache

Tomcat. The dashboard is a re-usable system focused on creating graphs and other

visualizations of data coming from the devices and the event processing layer.

The API management layer provides three main functions:

• The first is that it provides a developer-focused portal (as opposed to the user

focused portal previously mentioned), where developers can find, explore, and

subscribe to APIs from the system. There is also support for publishers to create,

version, and manage the available and published APIs;

• The second is a gateway that manages access to the APIs, performing access

control checks(for external requests) as well as throttling usage based on policies.

It also performs routing and load- balancing;

 UNIT-II- ARCHITECTURE AND PROTOCOLS

• The final aspect is that the gateway publishes data into the analytics layer where

it is stored as well as processed to provide insights into how the APIs are used.

DEVICE MANAGEMENT:

Device management (DM) is handled by two components. A server-side system (the

device manager) communicates with devices via various protocols and provides both

individual and bulk control of devices. It also remotely manages software and

applications deployed on the device. It can lock and/or wipe the device if necessary.

The device manager works in conjunction with the device management agents.

There are multiple different agents for different platforms and device types. The

device manager also needs to maintain the list of device identities and map these

into owners. It must also work with the identity and access management layer to

manage access controls over devices (e.g. who else can manage the device apart

from the owner, how much control does the owner have vs. the administrator, etc.)

There are three levels of device: non-managed, semi-managed and fully managed

(NM,SM, FM). Fully managed devices are those that run a full DM agent.

A full DM agent supports:

 UNIT-II- ARCHITECTURE AND PROTOCOLS

• Managing the software on the device

• Enabling/disabling features of the device (e.g. camera, hardware, etc.)

• Management of security controls and identifiers

• Monitoring the availability of the device • Maintaining a record of the device

location if

available

• Locking or wiping the device remotely if the device is compromised, etc.

Non-managed devices can communicate with the rest of the network, but have no

agent

involved. These may include 8-bit devices where the constraints are too small to

support the agent. The device manager may still maintain information on the

availability and location of the device if this is available. Semi-managed devices are

those that implement some parts of the DM (e.g. feature control, but not software

management).

IDENTITY AND ACCESS MANAGEMENT

The final layer is the identity and access management layer. This layer needs to

provide the following services:

 UNIT-II- ARCHITECTURE AND PROTOCOLS

• OAuth2 token issuing and validation

• Other identity services including SAML2 SSO and OpenID Connect support for

identifying

inbound requests from the Web layer

• XACML PDP

• Directory of users (e.g. LDAP)

• Policy management for access control (policy control point).

The identity layer may of course have other requirements specific to the other

identity and access management for a given instantiation of the reference

architecture. In this section we have outlined the major components of the reference

architecture as well as specific decisions we have taken around technologies. These

decisions are motivated by the specific requirements of IoT architectures as well as

best practices for building agile, evolvable, scalable Internet architectures.

IIOT THREE-TIER ARCHITECTURE PATTERN:

The three-tier architecture pattern comprises edge, platform and enterprise tiers.
 UNIT-II- ARCHITECTURE AND PROTOCOLS

These tier splay specific roles in processing the data flows and control flows involved

in usage

activities. They are connected by three networks, as shown in Figure

The edge tier collects data from the edge nodes, using the proximity network. The

architectural characteristics of this tier, including the breadth of distribution,

location, governance scope and the nature of the proximity network, vary depending

on the specific use cases.

The edge tier collects data from the edge nodes, using the proximity network. The
 UNIT-II- ARCHITECTURE AND PROTOCOLS

architectural characteristics of this tier, including the breadth of distribution,

location, governance scope and the nature of the proximity network, vary depending

on the specific use cases.

The platform tier receives, processes and forwards control commands from the

enterprise tier to the edge tier. It consolidates processes and analyzes data flows

from the edge tier and other tiers. It provides management functions for devices

and assets. It also offers non-domain specific services such as data query and

analytics.

The enterprise tier implements domain-specific applications, decision-support

systems and provides interfaces to end-users including operation specialists. It

receives data flows from the edge and platform tier. It also issues control commands

to the platform and edge tiers.

In the above figure, functional blocks are shown in each tier. These functional blocks

are indicative of the primary functional location of the tier yet are not exclusively

assigned to that tier. For example, the 'data transform' function in the platform tier

could also be found in the edge tier (e.g. performed by a gateway) although it would

be implemented in a different way and for a different purpose. For example, 'data
 UNIT-II- ARCHITECTURE AND PROTOCOLS

transform' at the edge is typically done in a device-specific manner through device

specific configuration and interfaces, unlike the platform tier where it is usually

supported as a higher-level service that operates on data that has been abstracted

from any device source or type.

Different networks connect the tiers:

The proximity network connects the sensors, actuators, devices, control systems

and assets, collectively called edge nodes. It typically connects these edge nodes,

as one or more clusters related to a gateway that bridges to other networks.

The access network enables connectivity for data and control flows between the

edge and the platform tiers. For example, it could be a corporate network, an overlay

private network over the public internet or a 4G/5G network.

Service network enables connectivity between the services in the platform tier and

the enterprise tier, and the services within each tier. It may be an overlay private

network over the public Internet or the Internet itself, allowing the enterprise grade

of security between end-users and various services.

 UNIT-II- ARCHITECTURE AND PROTOCOLS

Fig.Mapping between a three-tier architecture to the functional domains

The three-tier architecture pattern combines major components (e.g. platforms,

management services, applications) that generally map to the functional domains

as shown in the above Figure.

From the tier and domain perspective, the edge tier implements most of the control

domain; the platform tier most of the information and operations domains; the

enterprise tier most of the application and business domains. This mapping

demonstrates a simple functional partitioning across tiers. In a real system, the

 UNIT-II- ARCHITECTURE AND PROTOCOLS

functional mapping of IIoT system tiers depends greatly on the specifics of the

system use cases and requirements.

For example, some functions of the information domain may be implemented in or

close to the edge tier, along with some application logic and rules to enable

intelligent edge computing.

The asset management flows is an expression of the operations domain component

of the platform tier to manage the assets in the edge tier. The operations domain

component of the platform tier itself provides services (asset management service

flows) to other components, either in the same tier or in another.

The data services (information domain) component of the platform tier may request

services from the operations domain component for the verification of asset

credentials it receives in the data flows from the edge tier, and query of asset

metadata so it can augment the data received from the assets before the data are

persisted or fed into analytics in the next stage of processing.

Similar operations domain services can be provided to the application domain

components in the enterprise tier as well. Conversely, the operations domain

 UNIT-II- ARCHITECTURE AND PROTOCOLS

components may use data services from the information domain component in order

to get better intelligence from asset data, e.g. for diagnostics, prognostics and

optimization on the assets.

As a result, components from all functional domains may leverage the same data

and use analytic platforms and services to transform data into information for their

specific purposes.

Advantages:

The advantages of IoT are as follows

Cost Reduction − IOT devices catch any problem very fast as compared to traditional

troubleshooting. It not only saves time but also saves costs of large repairs.

Efficiency and Productivity − An automated PDF conversion and creation tool will

remove the hustle of PDF editing and archiving. Hence, increase in Efficiency and

Productivity.
 UNIT-II- ARCHITECTURE AND PROTOCOLS

Business Opportunities − IOT provides advanced analytics, smart utility grids which

help Small Management Businesses to provide more valuable content and things to

their customers.

Customer Experience − Nowadays customer's experience is the most valuable thing

in running a business. IoT has drastically increased the customer's experience. An

example of customer experience is Home Automation. Since everything is

connected, customers need not have to worry about appliances. One can turn off

the appliance through mobile.

Mobility and Agility − With the help of IoT, employees can do their work from any

geographical location, anytime without any restrictions.

Disadvantages

The disadvantages of IoT are as follows −

Security − The data is travelling all over the Internet. So maintaining its privacy is

still a Big Challenge. End-to-end Encryption is a must in IoT.

Compatibility − There is no International Standard for the monitoring of the

 UNIT-II- ARCHITECTURE AND PROTOCOLS

equipment.

Complexity − Most of the devices still contain some software bugs. Each device must

be able to seamlessly interact with other devices in the network.

Safety − Suppose a patient is left unattended by a doctor. And some notorious guy

changes the prescription or Health monitoring devices malfunctioned. Then it can

result in the death of the patient.

Policies − Government authorities must take some steps to make policies and

standards related to IoT to stop the Black marketing of IoT devices.

The technologies supported by IoT are as follows −

1.Big Data Analytics

2.Cloud

3.Wireless Sensor Networks

4.Embedded Systems
 UNIT-II- ARCHITECTURE AND PROTOCOLS

Industrial Internet System

The digital industrial company, General Electric (GE), coined the term Industrial

Internet.

Industrial Internet is not exactly the same as Industrial Internet of Things (IIoTs),

but they are often used interchangeably.

GE is also a founding member of Industrial Internet Consortium (IIC), which is also

a huge contributor in shaping IIoTs.

According to GE, there are three waves in industrial level

1.The First Wave or The Industrial Revolution

2. The Second Wave or The Internet Revolution

3. The Third Wave or The Industrial Internet

 UNIT-II- ARCHITECTURE AND PROTOCOLS

The Industrial Revolution lasted for around 150 years which began in 1750 and

ended in 1900

It had two stages

Commercialization and the mass production of steam engines marked the beginning

of the First Stage. It was started in the middle of eighteenth century.

The Second Stage started in 1870 with the invention of internal combustion engines

and electricity

1. The Second Stage is more powerful

2. Electricity brings new types of communications

3. Combustion Engines brings new forms of transportation systems

 UNIT-II- ARCHITECTURE AND PROTOCOLS

Drawbacks of Industrial Revolution:

Even though Industrial Revolution brought significant leap in the economy and

society, it had some negative effects

1.The waste products harmed the environment

2. Bad working environment

3. Inefficient

The Internet Revolution

The Internet Revolution started around 1950 and lasted for around 50 years

It was started with a government sponsored experimentation on computer networks

It became more eminent with the emergence World Wide Web

Computing capacity had also increased

Rapid information exchange over large geographical distance was made possible.

The Industrial Internet

Integration of Internet-based technologies to industries

Currently we are under Third Wave or The Industrial Internet

Third Wave has not reached its peak

According to GE, Industrial Internet can be defined as “the association of the global

industrial system with low-cost sensing, interconnectivity through internet, high-

level computing and analytics”.

 UNIT-II- ARCHITECTURE AND PROTOCOLS

It has three key elements

a) Intelligent machines

b) Advanced analytics

c) People at work

Intelligent machines

Different kinds of machines located at different locations can be interconnected

These machines can be monitored using advanced sensors and actuators using

related software.

Advanced analytics:

The huge data generated from different kinds of machines and sensors, advance

analytic and prediction techniques make possible in shaping a whole new era of

automation and intelligent machines.

 UNIT-II- ARCHITECTURE AND PROTOCOLS

People at work:

 Through web and mobile interfaces, everybody can connect with one another

regardless of their location.

 A doctor can interact with his patient virtually, a worker can control a machine

from anywhere etc.

 This makes the system more intelligent, maintenance and operations become

easier, safety and the quality of services also enhances at the same time.

APPLICATIONS:

 Commercial Aviation

 Rail Transportation

 Power Production

 Oil and Gas Sectors

 Healthcare
 UNIT-II- ARCHITECTURE AND PROTOCOLS

Commercial Aviation:

 The Industrial Internet can benefit commercial aviation industries by

improving both airline operations and asset management

 Airline operation

 Reducing fuel consumption

 Effective management of crews, flight scheduling, minimizing delays and

cancellations of flight

 Asset Management

 Proper maintenance of engines and other parts

 Timely repairing

Rail Transportation:
 UNIT-II- ARCHITECTURE AND PROTOCOLS

 Real-time analysis and application of predictive algorithms will help

 in reducing the maintenance cost

 in preventing engine breakdown

 Availability of software will help in providing a real-time overview of the entire

system to operators. Therefore,

 the rail operator can monitor the trains and make optimal decisions

 optimal train scheduling

Power Production:

 In power industries, outage is a huge problem because locating a broken

power line or equipment is not an easy task

 With the help of industrial internet, everything will be connected to internet.

Therefore

 status updates and performance related data will be easily available

 analysis of the incoming data will provide new insights relating to potential

problems which may occur in future

 cost of field inspection before repairing will be reduced

Oil and Gas Sectors:

 UNIT-II- ARCHITECTURE AND PROTOCOLS

 Industrial Internet

 reduces fuel consumption

 enhances production

 tracking events inside well, simulation of inside well, improve production

flow

 reduces costs

 real-time monitoring and alert system for safety and optimization

 Predictive analysis of the incoming data from different devices helps in

understanding the behavior of the underground reservoir.

Healthcare:

 Industrial Internet enables safe and efficient operations.

 availability of the information and reputations of doctors helps the patients to

choose the right doctor

 connectivity of healthcare devices to the internet helps in location each

devices and also know the status of the connected devices and the patients

monitor by them

 availability of healthcare data helps in advance healthcare researches.

 UNIT-II- ARCHITECTURE AND PROTOCOLS

Advantages of Industrial Internet:

 One percent fuel savings (in 15 years)

 Commercial Aviation Industries will save $30 billion

 Gas and Power segment of Power plants will save $66 billion

 One percent reduction in system inefficiency in

 Healthcare sector will save $63 billion

 Freight transportation through world rail network will save $27 billion

 One percent reduction in capital expenditure during exploration and

development in Oil and Gas industries will save $90 billion

 The emergence of cloud-based system will replace the isolated systems.

 UNIT-II- ARCHITECTURE AND PROTOCOLS

IoT Reference Architecture:

The IIRA viewpoints are defined by analyzing the various IIoT use cases developed

by the IIC and elsewhere, identifying the relevant stakeholders of IIoT systems and

determining the proper framing of concerns. These four viewpoints are:

 Business Viewpoint

 Usage Viewpoint

 Functional Viewpoint

 Implementation Viewpoint
 UNIT-II- ARCHITECTURE AND PROTOCOLS

As shown in Figure, these four viewpoints form the basis for the four views that

address the IIoT system concerns. Architects can then use these industrial internet

views as the basis of their architecture and may extend them by defining additional

views and viewpoints as needed to organize system concerns based on their specific

system requirements.

BUSINESS VIEWPOINT

The business viewpoint frames the concerns of the business stakeholders and their

business vision, values and objectives in establishing an IIoT system in its business

and regulatory context.

It further identifies the objectives of the IIoT system.

The concerns for the business viewpoint are business-oriented and are of interest
 UNIT-II- ARCHITECTURE AND PROTOCOLS

to business decision-makers, product managers and system engineers.

USAGE VIEWPOINT:

The usage viewpoint frames the concerns of expected system usage. It is typically

represented as sequences of activities involving human or logical (e.g. system or

system components) users that deliver its intended functionality in achieving its

fundamental system capabilities.

The stakeholders of these concerns typically consist of system engineers, product

managers and others, including those involved in the specification of the IIoT system

under consideration and those who use it.

The usage view contains models of context model kind. A context model depicts a

system of interest, or other entity, in the context of its environment to identify

external entities with which the system interacts.

FUNCTIONAL VIEWPOINT:

The functional viewpoint focuses on the functional components in an IIoT system,

their structure and interrelations, the interfaces and interactions between them, and

the relation and interactions of the system with external elements in the

environment, to support the usages and activities of the overall system.

 UNIT-II- ARCHITECTURE AND PROTOCOLS

These concerns are of particular interest to system and component architects,

developers and integrators. The functional view contains two models, a functional

domain model of concepts model kind, and a functional requirements model of

narrative statement model kind. A concepts model depicts a set of concepts and

their relationships for a domain of problem under consideration.

Itincludes both diagrams and narrative descriptions. A narrative statement model

provides text tobe used as a part of one or more architecture views to address

concerns

IMPLEMENTATION VIEWPOINT:

The implementation viewpoint frames concerns with the technologies needed to

implement functional components (functional view), their communication schemes

and their life cycle procedures. These elements are coordinated by activities (usage

view) and support the system capabilities (business view).

These concerns are of interest to system and component architects, developers and

integrators and system operators.

 UNIT-II- ARCHITECTURE AND PROTOCOLS

The patterns in the implementation view are of architecture pattern model kind. An

architecture pattern model kind describes the structure of a system and are used in

the construction of new systems. Architecture patterns are described using both

common architecture frameworks and specific domain languages.

IIOT System components:

The Industrial Internet of Things (IIoT) refers to the application of IoT technologies

in industrial settings, such as manufacturing, energy, transportation, and more. IIoT

system components are tailored to the unique requirements of these environments.

Sensors:

Sensors in IIoT environments are designed to monitor various parameters, such as

temperature, pressure, vibration, humidity, and more. These sensors collect real-

time data from machines, equipment, and processes. The collected data forms the

foundation for analysis and decision-making.

Gateways:

Gateways act as intermediaries between sensors and the central infrastructure. They
 UNIT-II- ARCHITECTURE AND PROTOCOLS

aggregate data from multiple sensors, preprocess and filter the data, and then

transmit it to higher-level systems. Gateways often handle tasks like protocol

translation, data compression, and local data processing to reduce latency.

Routers:

Routers facilitate communication between different network segments within an

IIoT environment. They ensure that data flows efficiently and securely between

sensors, gateways, and other components while maintaining network integrity.

Modems:

Modems are communication devices that modulate and demodulate digital signals

to enable data transmission over different types of communication networks, such

as cellular networks or satellite connections

Cloud Brokers:

Cloud brokers facilitate communication and data exchange between IIoT devices

and cloud platforms. They ensure secure and reliable data transfer, often utilizing

standard protocols like MQTT or CoAP to transmit data to cloud services.

 UNIT-II- ARCHITECTURE AND PROTOCOLS

Servers and Cloud Infrastructure:

IIoT data is often sent to cloud-based servers for storage, processing, and analysis.

Cloud infrastructure provides the scalability and computational power needed to

handle large volumes of data and run complex analytics. This enables organizations

to derive insights, make predictions, and optimize operations.

Integration:

Integration involves the seamless connection and interaction of various components

within an IIoT system. This can be achieved through standardized communication

protocols, APIs (Application Programming Interfaces), and middleware that enable

interoperability between different hardware and software components.

Wireless Sensor Network (WSN)

Wireless Sensor Network (WSN) is an infrastructure-less wireless network that is

deployed in a large number of wireless sensors in an ad-hoc manner that is used to

monitor the system, physical or environmental conditions. Sensor nodes are used in

WSN with the onboard processor that manages and monitors the environment in a

particular area. They are connected to the Base Station which acts as a processing

unit in the WSN System. Base Station in a WSN System is connected through the

Internet to share data. WSN can be used for processing, analysis, storage, and
 UNIT-II- ARCHITECTURE AND PROTOCOLS

mining of the data.

Applications of WSN:

1. Internet of Things (IoT)

2. Surveillance and Monitoring for security, threat detection

3. Environmental temperature, humidity, and air pressure

4. Noise Level of the surrounding

5. Medical applications like patient monitoring

6. Agriculture

7. Landslide Detection

Challenges of WSN:
 UNIT-II- ARCHITECTURE AND PROTOCOLS

1. Quality of Service

2. Security Issue

3. Energy Efficiency

4. Network Throughput

5. Performance

6. Ability to cope with node failure

7. Cross layer optimisation

8. Scalability to large scale of deployment

A modern Wireless Sensor Network (WSN) faces several challenges,

including:

Limited power and energy: WSNs are typically composed of battery-powered

sensors that have limited energy resources. This makes it challenging to ensure

that the network can function for long periods of time without the need for frequent

battery replacements.

Limited processing and storage capabilities: Sensor nodes in a WSN are

typically small and have limited processing and storage capabilities. This makes it

difficult to perform complex tasks or store large amounts of data.

Heterogeneity: WSNs often consist of a variety of different sensor types and

nodes with different capabilities. This makes it challenging to ensure that the
 UNIT-II- ARCHITECTURE AND PROTOCOLS

network can function effectively and efficiently.

Security: WSNs are vulnerable to various types of attacks, such as eavesdropping,

jamming, and spoofing. Ensuring the security of the network and the data it

collects is a major challenge.

Scalability: WSNs often need to be able to support a large number of sensor

nodes and handle large amounts of data. Ensuring that the network can scale to

meet these demands is a significant challenge.

Interference: WSNs are often deployed in environments where there is a lot of

interference from other wireless devices. This can make it difficult to ensure

reliable communication between sensor nodes.

Reliability: WSNs are often used in critical applications, such as monitoring the

environment or controlling industrial processes. Ensuring that the network is

reliable and able to function correctly in all conditions is a major challenge.

Components of WSN:

Sensors:

Sensors in WSN are used to capture the environmental variables and which is used

for data acquisition. Sensor signals are converted into electrical signals.

Radio Nodes:

It is used to receive the data produced by the Sensors and sends it to the WLAN
 UNIT-II- ARCHITECTURE AND PROTOCOLS

access point. It consists of a microcontroller, transceiver, external memory, and

power source.

WLAN Access Point:

It receives the data which is sent by the Radio nodes wirelessly, generally through

the internet.

Evaluation Software:

The data received by the WLAN Access Point is processed by a software called as

Evaluation Software for presenting the report to the users for further processing

of the data which can be used for processing, analysis, storage, and mining of

the data.

Advantages of Wireless Sensor Networks (WSN):

Low cost: WSNs consist of small, low-cost sensors that are easy to deploy, making

them a cost-effective solution for many applications.

Wireless communication: WSNs eliminate the need for wired connections,

which can be costly and difficult to install. Wireless communication also enables

flexible deployment and reconfiguration of the network.

Energy efficiency: WSNs use low-power devices and protocols to conserve

energy, enabling long-term operation without the need for frequent battery

replacements.
 UNIT-II- ARCHITECTURE AND PROTOCOLS

Scalability: WSNs can be scaled up or down easily by adding or removing

sensors, making them suitable for a range of applications and environments.

Real-time monitoring: WSNs enable real-time monitoring of physical

phenomena in the environment, providing timely information for decision making

and control.

Disadvantages of Wireless Sensor Networks (WSN):

Limited range: The range of wireless communication in WSNs is limited, which

can be a challenge for large-scale deployments or in environments with obstacles

that obstruct radio signals.

Limited processing power: WSNs use low-power devices, which may have

limited processing power and memory, making it difficult to perform complex

computations or support advanced applications.

Data security: WSNs are vulnerable to security threats, such as eavesdropping,

tampering, and denial of service attacks, which can compromise the confidentiality,

integrity, and availability of data.

Interference: Wireless communication in WSNs can be susceptible to

interference from other wireless devices or radio signals, which can degrade the

quality of data transmission.

 UNIT-II- ARCHITECTURE AND PROTOCOLS

Deployment challenges: Deploying WSNs can be challenging due to the need

for proper sensor placement, power management, and network configuration,

which can require significant time and resources.

while WSNs offer many benefits, they also have limitations and challenges that

must be considered when deploying and using them in real-world applications.

WIRELESS SENSOR NETWORK IN IOT

Wireless Sensor Network in IoT is an infrastructure-less wireless network that is

used for deploying a large number of wireless sensors that monitor the system,

physical and environmental conditions. Our extremely motivated and professional

engineers are very well equipped to provide you with an all round solution if you are

looking to incorporate WSN in your business.

NETWORKS CONNECTING WIRELESS SENSORS

To connect Sensors embedded in IoT devices, a communication protocol is used.

A low-power wide-area network ,LPWAN, is a type of wireless network designed to

allow long-range communications between these IoT devices.Lora based Wireless

Sensor network is widely used. Sub-1 GHz, Zigbee,Thread etc are also used to
 UNIT-II- ARCHITECTURE AND PROTOCOLS

connect sensor networks and gateway and data collected from this sensor network

can be sent to cloud using cellular networks such as NBIoT, LTE-M or wifi etc.
 UNIT-II- ARCHITECTURE AND PROTOCOLS

COMPONENTS OF WSN IN IOT

Sensor Nodes- Sensors play the vital role of capturing environmental variables.

Radio Nodes- Radio nodes or master nodes in a Wireless sensor network receive

data from the sensors and forward it to the gateway.

Access Point or Gateway-It is used to receive the data sent by the radio nodes

wirelessly typically through the internet and send it over the cloud.

Edge Computing and Data Analysis-The data received by the gateway

is analysed. This data is further analyzed on the cloud and displayed on IoT mobile

application or IoT dashboard.

 UNIT-II- ARCHITECTURE AND PROTOCOLS

IOT AND WIRELESS SENSOR NETWORKS

WSN protocols in IoT are used to provide a connectivity medium between IoT sensor

nodes and a central gateway. IoT consists of different tech stacks, WSN is just one

and is a subset of IoT. It is a part where data is transmitted among several IoT

devices mostly without internet.

WIRELESS SENSOR NETWORK APPLICATIONS

Patient monitoring in hospitals , Home security, Military applications, Livestock

monitoring , Server Room monitoring

Wireless sensor network for smart agriculture

Wireless sensor network for forest fire detection

Wireless sensor network for water quality monitoring

Wireless sensor network for office monitoring

Wireless sensor network for environmental monitoring

Wireless sensor network for landslide detection

Wireless sensor network for IoT security

WIRELESS SENSOR NETWORKS ARCHITECTURE

 UNIT-II- ARCHITECTURE AND PROTOCOLS

Fault Tolerance – Fault tolerance is the ability of the network to work even when

there is a break due to sensor node failures.

Mobility of Nodes – Nodes can be moved anywhere within the sensor field in order

to increase the efficiency of the network.

Scalability – WSN is designed in such a way that it can have thousands of nodes

in a network.

Feedback in case of Communication Failure – If a particular node fails to

exchange data over the network, it informs the base station immediately without

any delay.
 UNIT-II- ARCHITECTURE AND PROTOCOLS

Protocols of IIOT

Wi-Fi(Wireless Fidelity)

Wireless Fidelity Is One Of The Most Hassle-Free And Fast Wireless Communication

Technology. It Is The Choice Of Many Developers Due To Its Various Advantages.

It Allows Access To The Internet As Well As To Connect Devices In A Specific Range.

Personal Computers, Smartphones, Laptops, Printers, And Cars Use This Protocol.
 UNIT-II- ARCHITECTURE AND PROTOCOLS

An Automatic IP Address Is Allocated To Wireless Devices Using DHCD(Dynamic

Host Configuration )Protocol.

Features-

 Network Type – LAN(Local Area Network )

 Technology- Traditional Radio Transmission.

 Standards- IEEE 802.11.

 Communication Direction-Bidirectional.

 Frequency-2.4 GHz Or 5GHz.

 Power Usage – Medium.

 Range – Up To 50 M.

 Data Rate- 0.1 To 54 Mbps.

 Topology – Star, Tree, P2P.

 Connecting Devices – 4 To 8 Devices At A Time.

Advantages-

 Cost-Effective

 Convenient

 Explanadibility

 Easy To Use And Hassle-Free

Disadvantages-

 More Power Consumption

 UNIT-II- ARCHITECTURE AND PROTOCOLS

 Inconsistent And Instable

 Low-Level Security

 Low Range

ZigBee

Zigbee Is One Of The Wireless Technology That Has A Vast User Base And It

Addresses The Needs Of Low-Power, Low-Cost Requirements. It Is A High-Level

Communication Protocol. It Consists Of A Lower Power Digital Radio System And Is

Widely Used In Home Automation Systems, Medical Data Collection, Or Any Small

Scale Project With Low Bandwidth Requirement. In Our Day To Day Life, The

Applications Of ZigBee Is In The Traffic Management System, Light Switches, Etc.

It Is Secured With AES-128 Technology And Has Minimal Power Consumption.

Features-

 Network Type – WPAN(Wireless Personal Area Network).

 Standards- IEEE 802.15.4.

 Communication Direction -Bidirectional.

 Frequency -2.4 GHz.

 Power Usage-Low Power Usage.

 Range-10-100m.

 Data Rate-250 Kbps.

 UNIT-II- ARCHITECTURE AND PROTOCOLS

 Topology – Star,Tree, Mesh.

Advantages-

 Low Power Requirement.

 Low Cost.

 Flexible Network Structure.

 Easy To Implement And Install.

Disadvantages-

 Low Data Transmission Rate.

 Risky For The Use Of Personal Information.

 Low Bandwidth.

BACnet

BACnet Modbus

Developed By: ASHRAE

Use Communication across devices

Industrial, Transportation, Energy Management, Building

Markets
Automation, Regulatory and health and safety
 UNIT-II- ARCHITECTURE AND PROTOCOLS

Examples Boiler Control, Tank Level Measurements

Proprietary No

Transmission
Ethernet, IP, MS/TP, Zigbee
Modes

Standards ANSI/ASHRAE Standard 185 ;ISO-16484-5; ISO-16484-6

Costs Low; No charge for usage or licensing fees

Network Interfaces Existing LANs and LANs infrastructure

Testing BACnet Testing Labs

 Scalability between cost, performance and system size

 Endorsement and adoption by nearly every major vendor in

North America and many other countries

Advantages  Robust internetworking including multiple LAN types and

dial-up

 Unrestricted growth and the ability to add new innovations

and new features anytime

 UNIT-II- ARCHITECTURE AND PROTOCOLS

 Limited the number of field devices that can connect to a

master station except Ethernet TCP/IP

 MT/TP-Wire Length

Disadvantages  Ethernet-Infrastructure

 New standard has security standard but not implemented

in all devices

6LoWPAN

IPv6 Over Low Power Personal Area Network Or 6LoWPAN Is An IP-Also Based

Protocol That Ensures Connectivity Of Even Low Data Rate Networks. It Ensures

That Even The Smallest Or Low Power Device Should Be A Part Of IoT. It Helps

Provide End-To-End IP And Is Widely Used In Home Automation Systems.

Features-

 Network Type-WPAN(Wireless Personal Area Network).

 Technology – IP(Internet Protocol)Also Based Technology.

 Standards-IEEE 802.15.4 (RFC 6282).

 Frequency -Sub GHz Frequency Range.

 Range-25-50m.
 UNIT-II- ARCHITECTURE AND PROTOCOLS

 Data Rate-0-250 Kbps.

 Topology-Mesh.

Advantages-

 Low Power Consumption.

 Low Cost.

 The Protocol Can Be Directly Routed To The Cloud Platform.

 Vast Network For Many Devices.

Disadvantages-

 Less Secure.

 Problem Of Interference.

 Without Mesh Topology The Network May Be Small.

MQTT

MQTT Protocol is an IoT communication protocol based on publish/subscribe mode,

which occupies half of the IoT Protocol because of its simplicity, supporting QoS,

and small packet size.

MQTT Protocol is widely used in the fields of IoT, Mobile Internet, Intelligent

Hardware, IoV, Energy&Utilities, etc., which can not only be used as a gateway to

access communication on the device side, but also as a Device-Cloud

 UNIT-II- ARCHITECTURE AND PROTOCOLS

Communication Protocol. Most gateway protocols such as ZigBee and LoRa are

finally converted into MQTT Protocol to access Cloud.

Characteristics of the Protocol

 Light-weight and reliable: The MQTT message is compact, which can realize

stable transmission on severely limited hardware equipment and network with low

bandwidth and high delay.

 Publish/subscribe mode: Based on the publish/subscribe mode, the

advantage of publishing and subscribing mode is that the publisher and subscriber

are decoupled: Subscribers and publishers do not need to establish a direct

connection or be online at the same time.

 Created for the IoT: It provides comprehensive IoT application features such

as heartbeat mechanism, testament message, QoS quality level+offline message,

and theme and security management.

 Better ecosystem: It covers all-language platform's clients and SDKs, and it

has mature Broker server software, which can support massive Topic and ten-

million-level device access and provide rich enterprise integration capabilities.

Communication Mode

MQTT uses the publish-subscribe mode, which is different from the traditional client-

server mode. It separates the client who sends the message (publisher) from the
 UNIT-II- ARCHITECTURE AND PROTOCOLS

client who receives the message (subscriber), and the publisher does not need to

establish direct contact with the subscriber. We can let multiple publishers publish

messages to a subscriber, or multiple subscribers can receive a publisher's message

at the same time.

Market Conditions

MQTT is one of the most important standard protocols in the IoT field, which is

widely used in industries such as IoV, Industrial Internet of Things (IIoT), Smart

Home, Smart City, Electric Petroleum Energy, etc.

MQTT is the standard communication protocol of IoT platform of top Cloud

manufacturers such as AWS IoT Core, Azure IoT Hub, and Alibaba Cloud IoT

platform, and it is the preferred protocol for Cloud in various industries (such as

industrial Internet, car networking, and smart home) and many gateway protocols.

As one of the most popular MQTT brokers in the world, EMQX provides the cloud-

native distributed IoT messaging platform of "run anywhere, connect once, integrate

everything", with an all-in-one distributed MQTT broker and SQL-based IoT rule

engine, powering high-performance, reliable data movement, processing, and

integration for business-critical IoT solutions.

CoAP
 UNIT-II- ARCHITECTURE AND PROTOCOLS

CoAP is an HTTP-like Protocol in the IoT world, used on resource-constrained IoT

devices. Its detailed specification is defined in RFC 7252.

Most IoT devices are resource-constrained, such as CPU, RAM, Flash, network

broadband, etc. For this kind of device, it is unrealistic to realize the information

exchange directly by using TCP and HTTP of the existing network. CoAP Protocol

emerges as the times require, in order to make this part of devices connect to the

network smoothly.

Characteristics of the Protocol

CoAP refers to many design ideas of HTTP, and it also improves many design details

and adds many practical functions according to the specific situation of limited

resource-limited devices.

 It is based on message model

 Based on UDP Protocol, transport layer supports restricted devices

 It uses request/response model similar to HTTP request, and HTTP is text

format, while CoAP is binary format, which is more compact than HTTP

 It supports two-way communication

 It has the characteristics of light-weight and low power consumption

 It supports reliable transmission, data re-transmission, and block

transmission to ensure reliable arrival of data

 It supports IP multicast
 UNIT-II- ARCHITECTURE AND PROTOCOLS

 It supports observation mode

 It supports asynchronous communication

Market Conditions

Compared with MQTT, CoAP is lighter with lower overhead, and it is more suitable

for certain device and network environments. EMQX and some public cloud IoT

platforms provide CoAP access capability.

LwM2M

LwM2M is a lightweight IoT protocol suitable for resource-limited terminal

equipment management. LwM2M Protocol was born at the end of 2013, which was

proposed and defined by OMA (Open Mobile Alliance). At present, the mature

version number is still 1.0, and OMA experts are working on version 1.1.

Characteristics of the Protocol

• The most important entities of LwM2M Protocol include LwM2M Server and

LwM2M Client.

• As a server, the LwM2M Server is deployed at the M2M service provider or the

network service provider.

• As a client, the LwM2M Client is deployed on each LwM2M device.

In addition, LwM2M Bootstrap Server or SmartCard can be added as needed to

complete the initial boot for the client.

 UNIT-II- ARCHITECTURE AND PROTOCOLS

LwM2M Protocol has the following outstanding features:

 The Protocol is based on REST architecture.

 Protocol messaging is achieved through CoAP Protocol.

 The Protocol defines a compact, efficient and scalable data model.

LwM2M Protocol adopts REST to keep pace with the times and realize a simple and

easy-to-understand style.

However, because the protocol’s service object is the terminal equipment with

limited resources, the traditional HTTP data transmission mode is too cumbersome

to support the limited resources, so the REST-style CoAP is chosen to complete the

message and data transfer. On the one hand, compared with TCP, CoAP is based

on UDP. It is more flexible in environments where network resources are limited and

devices cannot be always on-line (for security reasons, UDP-based DTLS secure

transport protocol is used). On the other hand, the message structure of CoAP itself

is very simple, the message is compressed, and the main part of CoAP can be made

very compact without occupying too much resources.

For similar reasons, the protocol’s data structure must be simple enough. The

LwM2M Protocol defines a resource-based model, each resource may not only carry

a numerical value, but also point to an address to represent each item of information

available in the LwM2M client. All resources exist in an object instance, that is, the
 UNIT-II- ARCHITECTURE AND PROTOCOLS

instantiation of an object. The LwM2M Protocol pre-defines eight types of objects to

meet the basic requirements:

For scalability, the Protocol also allows more objects to be customized according to

actual needs. In such a data model, resources, object instances, and objects are

represented by ID corresponding to numbers to achieve maximum compression, so

that any resource can be represented in a concise manner of at most 3 levels, e.g.,

/1/0/1 represents the server short ID resource in the first instance of the Server

Object. At the registration stage, the LwM2M client transmits the object instance

carrying the resource information to the LwM2M server, so as to notify the server of

the capability of its own device.

EMQ also realizes LwM2M access capability on the EMQX server and most functions

of the LwM2M Protocol. LwM2M device can register to EMQX-LWM2M to access and

manage equipment through EMQX-LWM2M. Device can also report information to

EMQX-LWM2M and collect data by using EMQ back-end service.

AMQP

While one plans to bring AMQP into action, getting to know some of its key

terminologies is imperative. In this post part, we have explained the widely used

ones.
 UNIT-II- ARCHITECTURE AND PROTOCOLS

 Broker (or server) plays a crucial role in AMQP protocol enablement. It is

responsible for connection building that ensure better data routing and queuing at

the client-side.

 The job of queues generation and message acknowledgement is taken care

of by consumer.

 Redirection of data taken from exchanges and its placement in queues is

taken care of by producer.

Components Of AMQP

Other than the above AMQP terminologies, developers must be aware of certain

components used for AMQP model deployment.

 Exchanges (and their classification)

Exchange handles the responsibility of fetching messages and placing them carefully

in the right queue. Its 4 categories are: Fanout, Headers, Topic, and Direct. To detail

you on it further, it is an indispensable component of the broker.

Channel

Channel refers to a multiplexed virtual connection among AMQP peers, which is built

inside an existing connection.

Message Queue
 UNIT-II- ARCHITECTURE AND PROTOCOLS

It is an identified entity that helps link messages with their resources or point of

origin.

Binding

Bindings denote a set of predefined instructions related to queues as well as

exchanges. It administers the sending of message and their delivery.

Virtual Hosts

vhost is a platform offering the segregation facility inside the broker. Based upon

users and their access rights, there could be multiple vhost functional at a time.

How AMQP Exchanges Work?

The functional mechanism that AMQP follows is simple; however, only after

everything is set and system is ready for communication.

The exchanges play a crucial role in trading messages as they start with delivering

the messages to client, perform processing as per the rules, and direct the output

of previous stage to 1 or multiple queues. Its type in use decides which routing

method will be followed.

For instance, in the case of ‘direct’ type, the newly-added data contains final

message destination. Alternatively, Fanout exchange do not use any information

routing method. Instead, It broadcasts the same piece of information to all queues

attached.
 UNIT-II- ARCHITECTURE AND PROTOCOLS

API Development With AMQP

Now that you are well-aware of what is AMQP and how it works, let us explain how

it can help in API development. Using AMQP, APIs can:

 Direct send messages

 Cache messages them in queue for trigger-based sending;

 Can route information or bind exchanges to the designated queues;

 Establishes connection among exchanges in order to ensure efficient

communication;

 Can send automated or manual acknowledgement.

You may consider a few scenarios where AMQP can be used in APIs, for example:

 Adding money to your digital wallets

 Credit or debit card transaction in retail stores

 In messengers or communication systems

Let us take the first example and elaborate it now:

1. Adding money to your digital wallet, such as Paytm will require selecting a

method for adding money. It will initiate the create service.

2. Now comes the authentication step. If verified the details, the next service

will fetch money and add it to the wallet.

 UNIT-II- ARCHITECTURE AND PROTOCOLS

3. To give your user a chance to prevent transactions if he wants, you must

have a cancel service.

4. Messages exchange entertained by AMQP is asynchronous. As transactions

are crucial events and you won’t want inconsistency in them, there can be an extra

service events that will keep track of the outcome of each message so that the next

event could be triggered on time.

So, you see, asynchronous nature of AMQP will cause the need for callbacks in

comparison to HTTP. Also, it is more complex to design ‘fetch’ endpoints using this

protocol.

To conclude, if you could develop its API functionality well, AMQP can work well with

HTTP too. As it is lightweight, it will improve your application’s performance

significantly. If you cannot bear the complexity of the development process, HTTP

can be used alone and it will be sufficient for the job.

8. Assignments

1
 8. Assignments

Collect the IOT devices used in Smart TV and explain

the working principle of Smart TV
9. Part A Q & A

3
1. What is IIoT, and what are some of its key benefits?
IIoT stands for Industrial Internet of Things, which refers to the use of
connected sensors, devices, and machines to collect and analyze data in industrial
settings. Some key benefits of IIoT include increased efficiency and productivity,
improved quality control, predictive maintenance, and reduced downtime and
costs.

2. What are some of the challenges associated with implementing an

IIoT system, and how can they be addressed?
Some challenges of implementing an IIoT system include data security and
privacy concerns, integration with existing systems, and ensuring reliable
communication and data processing. These challenges can be addressed by
implementing security protocols, using standard communication protocols, and
selecting a scalable and flexible IIoT architecture.

3. What are some common types of sensors used in IIoT systems, and
how are they deployed in industrial settings?
Common types of sensors used in IIoT systems include temperature sensors,
pressure sensors, and vibration sensors. These sensors can be deployed in
industrial settings in various ways, such as using wireless sensor networks or
attaching sensors directly to machines and equipment.
4. What are some data processing and analysis methods used in IIoT
systems, and what are some of their applications?
Some data processing and analysis methods used in IIoT systems include
machine learning algorithms, data visualization tools, and statistical analysis
techniques. These methods can be used for applications such as predictive
maintenance, supply chain optimization, and quality control.

5. What are some common communication protocols used in IIoT systems,

and what are their advantages and disadvantages?
Common communication protocols used in IIoT systems include MQTT, CoAP,
and HTTP. Each protocol has its own advantages and disadvantages, such as
MQTT's low bandwidth requirements and CoAP's low overhead.

6. What is edge computing, and how is it used in IIoT systems?

Edge computing refers to the use of computing resources at or near the source of
data, rather than relying on cloud-based processing. In IIoT systems, edge
computing can be used to process and analyze data in real-time, reducing latency
and increasing efficiency.

7. What is the difference between IIoT and IoT, and how does IIoT benefit
industrial settings specifically?
IoT (Internet of Things) refers to the use of connected devices and sensors in
various settings, while IIoT (Industrial Internet of Things) specifically refers to the
use of such technology in industrial settings. IIoT benefits industrial settings by
improving efficiency, reducing downtime, and enabling predictive maintenance and
quality control.
8. What is the role of IIoT in smart factories, and how can it be used to
improve production processes?
IIoT can play a key role in smart factories by providing real-time data on machine
performance, energy usage, and quality control. This data can be used to optimize
production processes, reduce downtime, and improve overall efficiency.

9. Define actuators.
Actuators are devices that perform actions based on the data received from
sensors or through remote commands. Examples include motors, servos, solenoids,
and relays. Actuators enable devices to have an impact on the physical world.

10. Compare and contrast the features of AWS IoT, Google Cloud IoT, and
Microsoft Azure IoT platforms.
IoT platforms provide a set of tools and services for managing, connecting, and
analyzing IoT devices and data. They often include features like device
management, data storage, analytics, security, and remote monitoring. Examples of
IoT platforms are AWS IoT, Google Cloud IoT, and Microsoft Azure IoT.

11. Define edge computing.

Edge computing involves processing data closer to the source (on the device or at
a local server) rather than sending all data to the cloud. This reduces latency and
bandwidth usage while enabling real-time or near-real-time responses.

12. Show the structure of IOT reference architecture.

13. What are the main differences between MQTT and COAP?
MQTT CoAP

Retained messages Yes No

Synchronous (or
Asynchronous, event-
Messaging Mode asynchronous with
based
observe extension)

The broker can queue

Message queuing messages for None
disconnected subscribers

Message overhead 2 bytes minimum 4 bytes minimum

14. What is the Zigbee Alliance?

The Zigbee Alliance was created to develop a set of standards for IoT devices, or
wireless home automation devices, that use the Zigbee communication protocol. Its
mission is to help simplify, harmonize and build global open standards for the
Internet of Things (IoT).

15. What are some use cases for IoT data analytics?
• Predictive maintenance.
• Smart metering.
• Improving customer experience.
• Supply chain management.
• Smart parking.
• Smart building monitoring.
• Smart grids.
• Agriculture.

16. What role does a gateway play in IoT?

Simply put, an IoT gateway is a physical device or virtual platform that connects
sensors, IoT modules, and smart devices to the cloud. Gateways serve as a wireless
access portal to give IoT devices access to the Internet. On the surface, it may
sound like a simple router, enabling communication between different protocols and
devices. But IoT Gateways are sophisticated technology that does so much more,
like edge-computing in particular.
17. Mention some advantages of COAP.
1. Reduced power requirements
2. Grass-root-level usage
3. Security
4. Promp

18.Define industrial internet system.

The industry has widely accepted the four-layer model that describes the typical
architecture of an IIoT system. The four layers in this model are perception, network,
processing, and application,

19. Define Sensor.

1.A sensor is a device that monitors and responds to physical input. For instance, the
presence of visible light, infrared transmission (IR), and ultraviolet (UV) radiation are
detected using a photosensor.
2.It detects or analyzes a physical attribute as well as records, displays, or responds to it
in some particular way.
Types of sensor
1.Temperature sensor
2.Radio sensor
3.Humidity sensor
4.Magnetic switch sensor
5.Chemical sensor
6.Environment sensor
7.Proximity sensor
8.Optimal sensor
Uses of sensor
1.Doctors utilize the signals generated by sensors in medical equipment, surgical tools,
and gadgets for diagnosis, and, treatment.
2.It is used to measure voltage, capacitance, inductance, and ohmic resistance.
3.Sensors are used to measure gauge distance, temperature, detect smoke, regulate
pressure, etc.
20. Define WSN.
A Wireless Sensor Network (WSN) is a set of spatially distributed sensors that can
monitor environmental phenomenons and exchange that information with each other
over wireless channels.

21. Mention Some advantages of WSN.

➨It is scalable and hence can accommodate any new nodes or devices at any time.
➨It is flexible and hence open to physical partitions.
➨All the WSN nodes can be accessed through centralized montoring system.
➨As it is wireless in nature, it does not require wires or cables. Refer difference
between wired network vs wireless network.
➨WSNs can be applied on large scale and in various domains such as mines,
healthcare, surveillance, agriculture etc.
➨It uses different security algorithms as per underlying wireless technologies and
hence provide reliable network for consumers or users.

22. Mention the Drawbacks or disadvantages of WSN

➨As it is wireless in nature, it is prone to hacking by hackers.
➨It can not be used for high speed communication as it is designed for low speed
applications.
➨It is expensive to build such network and hence can not be affordable by all.
➨There are various challenges to be considered in WSN such as energy efficiency,
limited bandwidth, node costs, deployment model, Software/hardware design
constraints and so on.
➨In star topology based WSN, failure of central node leads to whole network shutdown.
10. Part B Questions

10
 10. Part B Questions

1 Measure the extent of benefits that can be provided by IOT for K5 CO2 A
Home Automation, Health monitoring system, Smart
Transportation and Smart Shopping.

2 Develop a narration on IoT Access technologies that plays a K6 C02 A

major role in market. Give suitable examples explaining the
technologies.

3 Explain the meaning of the term “Integrating Cloud Computing K5 CO2 A

and IOT” with suitable examples.

4 Discuss and Design IOT Based Environment Monitoring using K3 CO2 A

Wireless Sensor Network.

5 To implement and Designing the Smart Agricultural System K4 C02 A

with LoRa-based WSNs using different IOT technologies and
Protocols.

6 To Design and Discuss Briefly about WSN based Monitoring of K3 CO2 S

Temperature and Humidity of Soil using Arduino

7 Discuss about Protocols in IIOT? Explain with its advantages K2 CO2

and disadvantages?

8 Explain and Discuss in details? about Short Range K2 CO2

communications and Long Range communications

9 How IoT Protocols and Standards Support Secure Data K3 CO2 S

Exchange in the IoT Ecosystem ?

10 Explain the following protocols in IIOT? K3 CO2 S

(i)WIFI (4)

(ii)Zigbee (4)

(iii)BACnet (5)

11 (i) Why are IoT protocols important? (6) K1 CO2 A

(ii) How many protocols are there in IoT? How to choose the
right IoT protocol (7)
11. Activity based learning

12
 11. Activity based learning

Activity – Group discussion

Case study Automated Health care system
•Discuss architecture of Automated Health care system
•Discuss challenges to implement automated healthcare system
•Discuss advantages of automated health care system
12. Supportive online Certification courses

14
 12. Supportive online Certification courses

1.Introduction To Internet of Thongs

https://onlinecourses.nptel.ac.in/noc23_cs83

2. Introduction to Industrial IoT for IT Professionals

https://www.udemy.com/course/introduction-to-industrial-iot-for-it-professionals/
13. Real time Applications in day to day life
and to Industry

16
13. Real time Applications in day to day life and to Industry

• Manage building automation data from multiple locations- all Star hotels
• IIoT can be used to monitor and control the heating, lighting, energy consumption, fire
protection, employee safety and many other systems for multiple buildings from a
central location. The real-time machine data can be transferred to a central cloud
application, using industrial communication networks.
14. Contents beyond the Syllabus

18
 14. Contents beyond the Syllabus
What is edge computing?
•Edge computing is an emerging computing paradigm which refers to a
range of networks and devices at or near the user. Edge is about
processing data closer to where it’s being generated, enabling processing
at greater speeds and volumes, leading to greater action-led results in real
time.
•It offers some unique advantages over traditional models, where computing power
is centralized at an on-premise data center. Putting compute at the edge allows
companies to improve how they manage and use physical assets and create new
interactive, human experiences. Some examples of edge use cases include self-
driving cars, autonomous robots, smart equipment data and automated retail.
•Possible components of edge include:
•Edge devices: We already use devices that do edge computing every day—like
smart speakers, watches and phones – devices which are locally collecting and
processing data while touching the physical world. Internet of Things (IoT) devices,
point of sales (POS) systems, robots, vehicles and sensors can all be edge devices—
if they compute locally and talk to the cloud.
•Network edge: Edge computing doesn’t require a separate “edge network” to
exist (it could be located on individual edge devices or a router, for example). When
a separate network is involved, this is just another location in the continuum
between users and the cloud and this is where 5G can come into play. 5G brings
extremely powerful wireless connectivity to edge computing with low latency and
high cellular speed, which brings exciting opportunities like autonomous drones,
remote telesurgery, smart city projects and much more. The network edge can be
particularly useful in cases where it is too costly and complicated to put compute on
premises and yet high responsiveness is required (meaning the cloud is too distant).
•On-premises infrastructure: These are for managing local systems and
connecting to the network and could be servers, routers, containers, hubs or
bridges.
15. Assessment Schedule

20
 15. Assessment Schedule

•FIRST INTERNAL ASSESSMENT TEST

SCHEDULED ON 24/09/23

•SECOND INTERNAL ASSESSMENT TEST

SCHEDULED ON 28/10/23
16. Prescribed Text Books &
Reference Books

22
Prescribed Text Books & Reference Books

TEXT BOOKS:
•1. Daniel Minoli, Building the Internet of Things with IPv6 and MIPv6: The Evolving World
of M2M Communications,First Edition, Wiley Publications, 2013
•2. Dieter Uckelmann , Mark Harrison, Florian Michahelles, Architecting the Internet of
Things, Springer-Verlag Berlin Heidelberg 2011 Industry 4.0: The Industrial Internet of Things
REFERENCES:
•1. Hakima Chaouchi,The Internet of Things Connecting Objects to the Web Willy
Publications.
•2. Olivier Hersent, David Boswarthick, Omar Elloumi, The Internet of Things: Key
Applications and Protocols, Second Edition,Wiley Publications
• 3. Internet of Things - From Research and Innovation to Market Deployment; by
OvidiuVermesan & Peter Friess; 2014, River Publishers Series
•4. How Protocol Conversion Addresses IIoT Challenges:White Paper By RedLion.
•5. Alasdair Gilchrist, Industry 4.0: The Industrial Internet of Things,First Edition,Kindle
Edition
17. Mini Project suggestions

24
 17. Mini Project suggestions

Create a table for literature review with following

entrees
• Paper title, journal name , published year
• Methodology used ( Algoritham )
• Parameters considered
• Output
• Advantages
• Disadvantage
 Thank you

Disclaimer:

This document is confidential and intended solely for the educational purpose of RMK
Group of Educational Institutions. If you have received this document through email in
error, please notify the system manager. This document contains proprietary
information and is intended only to the respective group / learning community as
intended. If you are not the addressee you should not disseminate, distribute or copy
through e-mail. Please notify the sender immediately by e-mail if you have received this
document by mistake and delete this document from your system. If you are not the
intended recipient you are notified that disclosing, copying, distributing or taking any
action in reliance on the contents of this information is strictly prohibited.