[go: up one dir, main page]

0% found this document useful (0 votes)
76 views22 pages

IoT: Definitions, Goals, and Characteristics

Uploaded by

satheesh
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
76 views22 pages

IoT: Definitions, Goals, and Characteristics

Uploaded by

satheesh
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 22

lOMoARcPSD|157 970 14

UNIT - I

 Definition of IoT (Internet of Things):

The IoT can be defined in two ways based on


 existing Technology
 Infrastructure

Definition of IoT based on existing technology:


IoT is a new revolution to the internet due to the advancement in sensor networks, mobile
devices, wireless communication, networking and cloud technologies.

Definition of IoT based on infrastructure:


IoT is a dynamic global network infrastructure of physical and virtual objects having unique
identities, which are embedded with software, sensors, actuators, electronic and network
connectivity to facilitate intelligent applications by collecting and exchanging data.

Goal of IoT:
The main goal of IoT is to configure, control and network the devices or things, to internet,
which are traditionally not associated with the internet i.e thermostats, utility meters, a Bluetooth
connected headset, irrigation pumps and sensors or control circuits for an electric car’s engine that
make energy, logistics, industrial control, retail, agriculture and many other domain smarter.
 Characteristics of IoT:
Various characteristics of IoT are:
 Dynamic and self-adapting
 Self-configuring
 Interoperable Communication protocols
 Unique identity
 Integrated into information network
Dynamic and self-adapting:
The IoT devices can dynamically adapt with sensed environment, their operating
conditions, and user’s context and take actions accordingly. For ex: Surveillance System.
Self-configuring:

I. IoT devices can be able to upgrade the software with minimal intervention of user,
whenever they are connected to the internet.
II. They can also setup the network i.e. a new device can be easily added to the existing
network. For ex: Whenever there will be free wifi access one device can be connected easily.
Interoperable Communication:

IoT allows different devices (different in architecture) to communicate with each other as well as
with different network. For ex: MI Phone is able to control the smart AC and smart TV of different
manufacturer.

RCR Institute of Management & Technology Page 1


Prepared By Mrs.P.Lalitha, Dept.of MCA Internet of Things
lOMoARcPSD|157 970 14

Unique identities:
I. The devices which are connected to the internet have unique identities i.e IP address through
which they can be identified throughout the network.
II. The IoT devices have intelligent interfaces which allow communicating with users. It adapts
to the environmental contexts.
III. It also allows the user to query the devices, monitor their status, and control them remotely,
in association with the control, configuration and management infrastructure.
Integrated into information network:
I. The IoT devices are connected to the network to share some information with other
connected devices. The devices can be discovered dynamically in the network by other
devices. For ex. If a device has wifi connectivity then that will be shown to other nearby
devices having wifi connectivity.
II. The devices ssid will be visible though out the network. Due to these things the network is
also called as information network.
III. The IoT devices become smarter due to the collective intelligence of the individual devices
in collaboration with the information network. For Ex: weather monitoring system. Here the
information collected from different monitoring nodes (sensors, arduino devices) can be
aggregated and analysed to predict the weather.
 Physical Design of IoT:
Things in IoT:
I. IoT i.e Internet of things, where things refer to the IoT devices which have unique identities
and can perform remote sensing, actuating and monitoring capabilities (ex: combination of
sensors, actuators, Arduino, relay, non IoT devices).
II. The IoT devices can share information with as well as collect information from other
connected devices and applications (directly and indirectly).
III. They can process the data locally or in the cloud to find greater insights and put them into
action based on temporal and space constraints (i.e space memory, processing capabilities,
communication latencies and speeds and deadlines).
IV. IoT devices can be of varied types. For ex: wearable sensors, smart watches, LED lights,
automobiles and industrial machines.
 Logical design of IoT:
Logical design of IoT refers to an abstract representation of entities and the processes
without going into the details of the implementations. The logical design includes functional block
of IoT and the communication APIs.
IoT functional Block: (Refer book for the diagram):
The functional block of the system provides the capabilities for identification, sensing,
actuation, communication and management. Various components of IoT functional block are as
follows.
 Device
 Communications
 Services
 Management
 Security
 Application
RCR Institute of Management & Technology Page 2
Prepared By Mrs.P.Lalitha, Dept.of MCA Internet of Things
lOMoARcPSD|157 970 14

Device:
I. IoT i.e. Internet of things, where things refer to the IoT devices which have unique
identities and can perform remote sensing, actuating and monitoring capabilities (ex:
combination of sensors, actuators, Arduino, relay, non IoT devices).
II. The IoT devices can share information with as well as collect information from other
connected devices and applications (directly and indirectly).
III. They can process the data locally or in the cloud to find greater insights and put them into
action based on temporal and space constraints (i.e space memory, processing capabilities,
communication latencies and speeds and deadlines).
IV. IoT devices can be of varied types. For ex: wearable sensors, smart watches, LED lights,
automobiles and industrial machines.
Communications:
It refers to various communication protocols which allows different devices to communicate
with each other by sharing some information. It also allows interoperability among different
devices.
Services:
IoT system provides various services such as device monitoring, device control services,
data publishing services, device discovery services.
Management:
Various management functions to govern the IoT system.
Security:
It secures the IoT system by providing authentication, authorization, message and content
integrity and data security.
Application:
I. IoT applications provide an interface that the users can use to control and monitor various
aspects of the IoT system.
II. It also allows viewing the system status and view or analyzing the processed data.
IoT communication model:
To provide communication to various IoT devices, there are various communication models.
Such as

Request-Response communication model


Publisher-subscriber communication model
Push-pull communication model
Exclusive-pair communication model
Request-response communication model: (Refer book for the diagram)
I. In this communication model client will send request to server. Server will receive the
request then decides how to respond, fetches the data according to client’s request, retrieves
resource representations, prepares the response and then sends the response to client.
II. Request-response model is a stateless communication model i.e each request-response pair is
independent of others. Ex: HTTPs requests to log in some secure sites like IRCTC.
III. Here only client can request to the server. i.e request is unidirectional but data transfer is bi-
directional.
IV. It follows client server architecture. IoT devices act as client. Cloud act as server or local
server serves as server.
RCR Institute of Management & Technology Page 3
Prepared By Mrs.P.Lalitha, Dept.of MCA Internet of Things
lOMoARcPSD|157 970 14

Publish-Subscribe communication model:


I. This communication model comprises of publisher, broker, and consumer.
II. Publishers are the source of data i.e the devices or applications which generate data.
Publisher publishes the data to the requested topic by the client or consumer into the server.
III. Broker manages the topics in server. Broker receives the data from the client or publisher
and forwards the message to topics on the topics subscribed by the clients.
IV. Consumer or clients (applications that process the data) subscribe to various topics present
inside server. When the publisher publishes the data to the requested topics they will receive
it from the broker.
V. The publisher doesn’t know about the client, but knows about the broker. Likewise client
does not know about the publisher but knows about the broker.
VI. It also follows client-server architecture.
VII. Ex1-when one user subscribe to any channel in you-tube. Here let I am a client and I
subscribe to Remo’s dance channel. Remo may directly create his own channel in You-tube
and sends the recorded video to the channel. Here Remo act as publisher, you tube as server
and broker. Channel as topic and me as subscriber.
Ex2- sometimes what happened the publisher doesn’t create its own channel rather they
send the data to an intermediate then they send the data to the server and from that to the
subscribed user. That intermediate can be called as broker. There you -tube is called as
server. Ex. Cheers is a broker which manages some of the web series. Here the web
series are topic. You-tube is the server.
Push-Pull communication model:
Push-pull is a communication model in which the data producers push the data to the queues and the
consumers pull the data from the queues.
I. Producers do not need to be aware of the consumers.
II. Queues act as buffer which helps in situations when there is a mismatch between the rate at
which the producers push the data and the rate at which the consumers pull the data.
Exclusive pair communication model:
I. Exclusive pair is a bi-directional, full duplex communication model.
II. It uses state-full protocols i.e we don’t need to log in again and again.
III. It uses a single http connection i.e persistent connection between the client and the server i.e
once the connection is set up it remains until the client sends the request to close the
connection.
IV. It also supports client-server architecture.
V. It is a stateful communication model and the server is aware about all the open connection.
IoT communication APIs:
What is an API: Application programming interface is a set of requirements that govern how one
application can talk to another. API’s do all these things by exposing some of program’s internal
functions to the outside world in a limited fashion.
Mainly two types of communication APIs are used in IoT. Those are as follows
 REST based communication API
 WebSocket based communication API REST
based communication API:

RCR Institute of Management & Technology Page 4


Prepared By Mrs.P.Lalitha, Dept.of MCA Internet of Things
lOMoARcPSD|157 970 14

I. REST: Representational State Transfer.


II. It helps to design web services and web APIs that focus on a system’s resource and how
resource states are addressed and transferred.
III. It follows Request-response communication model and unidirectional communication for
request. The clients send request to URIs using methods defined by the HTTP protocols
(GET, PUT, POST, DELETE).
IV. RESTful web service is a “web API” implemented using HTTP and REST principle.
RESTful web service is a collection of resources which are represented by URIs.
V. RESTful Web services can support various internet media types (JSON, XML).
JSON: Java script object notation (most popular web service).
XML: Extensible mark up language
VI. This communication API follows various constraints such as
 Client-server
 Stateless
 Cache-able
 Layered System
 Uniform interface
 Code on demand
 Scalability
Client-Server: The principle behind the client-server constraint is the separation of concern. Ex:
The server is concerned about the storage part i.e storage of data and the client will not bother
about it. The client should concern about the user interface and the server will not bother about it.
Due to this type of separation client and server can be independently developed and updated.
Stateless: Each time the request from client to server must contain all the information necessary
for understanding the request.
Cache-able: It requires that data within a response to request be implicitly or explicitly labelled as
cach-able or non-cache-able. The data can be cached in client side so that it can be reused when
requested for the next time in order to minimise the time. It will increase the efficiency and
scalability.
Layered System: This constraint limits the behaviour of components i.e each component
cannot see beyond the immediate layer with which they are interacting. Ex: client cannot say
whether it is connected directly to the end server or to an intermediary. It improves scalability by
allowing intermediaries to respond to requests instead of the end server without the client having to
do anything different.
Uniform interface: The method of communication between a client and a server must be uniform
Code on demand: Servers can provide executable codes or scripts for clients to execute in their
context.
Scalability: it supports both horizontal and vertical scalability. As it is stateless so scalability is
easier to implement.
Web Socket-based Communication APIs:
1. WebSocket API helps to design web services and web APIs.
2. It allows bi-directional, full-duplex communication between clients and servers.
3. It follows the exclusive pair communication model.
4. It supports stateful protocols. It does not require a new connection to be set up for each
message to be sent. There is no overload for connection set up and termination request

RCR Institute of Management & Technology Page 5


Prepared By Mrs.P.Lalitha, Dept.of MCA Internet of Things
lOMoARcPSD|157 970 14

for each message. So Web socket API reduces the network traffic and latency.
5. It is suitable for IoT applications that have low latency or high throughput requirements.
Description of the Diagram:
In web socket communication first the client sets up connection with the server. This request
is sent over the HTTP and the server interprets as an upgrade request (called Websocket
handshake). If the server supports websocket protocol then only it will respond to this handshake. If
the server supports then client and server can send message to each other in full-duplex mode.
Difference between REST and Websocket:
REST WebSocket
1. It supports Request-response 1. It supports Exclusive-pair
communication model. communication model.
2. It supports stateless protocol. 2. It supports stateful protocol.
3. It supports unidirectional 3. It supports bidirectional
communication between client and communication between client and
server as only client can send server i.e client and server both can
request to server and server only request to each other.
respond to the request. 4. It is full duplex.
4. It is half duplex. 5. It uses single TCP connection for
5. It uses multiple TCP connection for search over HTTP.
each search over HTTP. 6. Header overhead is less.
6. Since it does not store the request 7. Vertical scaling is easier than
information so each time it needs to horizontal scaling.
provide all the information while
creating communication with
server. For this reason header
overhead increases.
7. It supports both horizontal and
vertical scalability.
 Architecture of Internet of Things (IoT)
Internet of Things (IoT) technology has a wide variety of applications and use of Internet of
Things is growing so faster. Depending upon different application areas of Internet of Things, it
works accordingly as per it has been designed/developed. But it has not a standard defined
architecture of working which is strictly followed universally. The architecture of IoT depends upon
its functionality and implementation in different sectors. Still, there is a basic process flow based on
which IoT is built.
So. here in this article we will discuss basic fundamental architecture of IoT i.e., 4 Stage IoT
architecture.

RCR Institute of Management & Technology Page 6


Prepared By Mrs.P.Lalitha, Dept.of MCA Internet of Things
lOMoARcPSD|157 970 14

So, from the above image it is clear that there is 4 layers are present that can be divided as follows:
Sensing Layer, Network Layer, Data processing Layer, and Application Layer.
These are explained as following below.
1. Sensing Layer –
Sensors, actuators, devices are present in this Sensing layer. These Sensors or Actuators accepts
data (physical/environmental parameters), processes data and emits data over network.
2. Network Layer
Internet/Network gateways, Data Acquisition System (DAS) are present in this layer. DAS
performs data aggregation and conversion function (Collecting data and aggregating data then
converting analog data of sensors to digital data etc). Advanced gateways which mainly opens up
connection between Sensor networks and Internet also performs many basic gateway functionalities
like malware protection, and filtering also some times decision making based on inputted data and
data management services, etc.
3. Data processing Layer –
This is processing unit of IoT ecosystem. Here data is analyzed and pre-processed before sending it
to data center from where data is accessed by software applications often termed as business
applications where data is monitored and managed and further actions are also prepared. So here
Edge IT or edge analytics comes into picture.
4. Application Layer –
This is last layer of 4 stages of IoT architecture. Data centers or cloud is management stage of data
where data is managed and is used by end-user applications like agriculture, health care, aerospace,
farming, defense, etc
 IoT enabling technologies:
The technologies which are cooperative with IoT those are as follows.
There are many technologies that enable the IoT. Crucial to the field is the network used to
communicate between devices of an IoT installation, a role that several wireless or wired technologies
may fulfill .

RCR Institute of Management & Technology Page 7


Prepared By Mrs.P.Lalitha, Dept.of MCA Internet of Things
lOMoARcPSD|157 970 14

Addressability
The original idea of the Auto-ID Center is based on RFID-tags and distinct identification through
the Electronic Product Code. This has evolved into objects having an IP address or URI.[169] An
alternative view, from the world of the Semantic Web[170] focuses instead on making all things (not just
those electronic, smart, or RFID-enabled) addressable by the existing naming protocols, such as URI.
The objects themselves do not converse, but they may now be referred to by other agents, such as
powerful centralized servers acting for their human owners. [171] Integration with the Internet implies
that devices will use an IP address as a distinct identifier. Due to the limited address
space of IPv4 (which allows for 4.3 billion different addresses), objects in the IoT will have to use the
next generation of the Internet protocol (IPv6) to scale to the extremely large address space
required.[172][173][174] Internet-of-things devices additionally will benefit from the stateless address auto-
configuration present in IPv6,[175] as it reduces the configuration overhead on the hosts, [173] and
the IETF 6LoWPAN header compression. To a large extent, the future of the Internet of things will not
be possible without the support of IPv6; and consequently, the global adoption of IPv6 in the coming
years will be critical for the successful development of the IoT in the future.
Application Layer
 ADRC defines an application layer protocol and supporting framework for implementing IoT
applications.
Short-range wireless
 Bluetooth mesh networking – Specification providing a mesh networking variant to Bluetooth low
energy (BLE) with an increased number of nodes and standardized application layer (Models).
 Light-Fidelity (Li-Fi) – Wireless communication technology similar to the Wi-Fi standard, but
using visible light communication for increased bandwidth.
 Near-field communication (NFC) – Communication protocols enabling two electronic devices to
communicate within a 4 cm range.
 Radio-frequency identification (RFID) – Technology using electromagnetic fields to read data
stored in tags embedded in other items.
 Wi-Fi – Technology for local area networking based on the IEEE 802.11 standard, where devices
may communicate through a shared access point or directly between individual devices.
 ZigBee – Communication protocols for personal area networking based on the IEEE 802.15.4
standard, providing low power consumption, low data rate, low cost, and high throughput.
 Z-Wave – Wireless communications protocol used primarily for home automation and security
applications
Medium-range wireless
 LTE-Advanced – High-speed communication specification for mobile networks. Provides
enhancements to the LTE standard with extended coverage, higher throughput, and lower latency.
 5G - 5G wireless networks can be used to achieve the high communication requirements of the IoT
and connect a large number of IoT devices, even when they are on the move. There are three
features of 5G that are each considered to be useful for supporting particular elements of IoT:
enhanced mobile broadband (eMBB), massive machine type communications (mMTC) and ultra-
reliable low latency communications (URLLC).
Long-range wireless
 Low-power wide-area networking (LPWAN) – Wireless networks designed to allow long-range
communication at a low data rate, reducing power and cost for transmission. Available LPWAN
technologies and protocols: LoRaWan, Sigfox, NB-IoT, Weightless, RPMA.

RCR Institute of Management & Technology Page 8


Prepared By Mrs.P.Lalitha, Dept.of MCA Internet of Things
lOMoARcPSD|157 970 14

 Very small aperture terminal (VSAT) – Satellite communication technology using small dish
antennas for narrowband and broadband data.
Wired
 Ethernet – General purpose networking standard using twisted pair and fiber optic links in
conjunction with hubs or switches.
 Power-line communication (PLC) – Communication technology using electrical wiring to carry
power and data. Specifications such as Home Plug or G.hn utilize PLC for networking IoT devices.
Standards and standards organizations
This is a list of technical standards for the IoT, most of which are open standards, and the standards
organizations that aspire to successfully setting them .

Short Long name Standards under Other notes


name development

Auto-ID Auto Networked RFID (radiofreque


Labs Identification ncy identification) and
Center emerging sensing technologies

Connected Project Connected Home over IP (or The Connected Home over IP project
Home Connected Project Connected Home over group was launched and introduced
over IP Home over IP) is an open-sourced, by Amazon, Apple, Google,[181] Comcast
IP royalty-free home automation and the Zigbee Alliance on December
connectivity standard project 18, 2019.[182] The project is backed by
which features compatibility big companies and by being based on
among different smart home proven Internet design principles and
and Internet of things (IoT) protocols it aims to unify the currently
products and software fragmented systems.[183]

EPCglobal Electronic Standards for adoption


Product code of EPC (Electronic Product
Technology Code) technology

FDA U.S. Food UDI (Unique Device


and Drug Identification) system for
Administrati distinct identifiers for medical
on devices

Parent organization comprises member


GS1 Global Standards for UIDs ("unique" organizations such as GS1 US
Standards identifiers) and RFID of fast-
One moving consumer
goods (consumer packaged
goods), health care supplies,

RCR Institute of Management & Technology Page 9


Prepared By Mrs.P.Lalitha, Dept.of MCA Internet of Things
lOMoARcPSD|157 970 14

and other things

The GS1 digital link


[184]
standard, first released in
August 2018, allows the use
QR Codes, GS1 Datamatrix,
RFID and NFC to enable
various types of business-to-
business, as well as business-
to-consumers interactions.
IEEE Institute ofUnderlying communication
Electrical and
technology standards such
Electronics as IEEE 802.15.4, IEEE
[185]
Engineers P1451-99 (IoT
Harmonization), and IEEE
P1931.1 (ROOF Computing).
IETF Internet Standards that
Engineering comprise TCP/IP (the Internet
Task Force protocol suite)
MTConne — MTConnect is a
ct Institute manufacturing industry
standard for data exchange
with machine tools and related
industrial equipment. It is
important to the IIoT subset of
the IoT.
O-DF Open Data O-DF is a standard published
Format by the Internet of Things
Work Group of The Open
Group in 2014, which
specifies a generic information
model structure that is meant
to be applicable for describing
any "Thing", as well as for
publishing, updating and
querying information when
used together with O-
MI (Open Messaging
Interface).
O-MI Open O-MI is a standard published
Messaging by the Internet of Things
Interface Work Group of The Open
Group in 2014, which
specifies a limited set of key
operations needed in IoT
systems, notably different
kinds of subscription
mechanisms based on
RCR Institute of Management & Technology Page 10
Prepared By Mrs.P.Lalitha, Dept.of MCA Internet of Things
lOMoARcPSD|157 970 14

the Observer pattern.


OCF Open Standards for simple devices OCF (Open Connectivity Foundation)
Connectivity
using CoAP (Constrained supersedes OIC (Open Interconnect
Foundation Application Protocol) Consortium)
OMA Open MobileOMA DM and OMA
Alliance LWM2M for IoT device
management, as well as
GotAPI, which provides a
secure framework for IoT
applications
XSF XMPP Protocol extensions
Standards of XMPP (Extensible
Foundation Messaging and Presence
Protocol), the open standard
of instant messaging
W3C World Wide Standards for bringing
Web interoperability between
Consortium different IoT protocols and
platforms such as Thing
Description, Discovery, Script
ing API and Architecture that
explains how they work
together.

Cloud Computing:
1. It is an emerging technology which enables on-demand network access to computing
resources like network servers, storage, applications and services that can be rapidly
provisioned and released.
2. On demand: we invoke cloud services only when we need them, they are not permanent part
of IT infrastructure.
3. Pay as you go model: You pay for the cloud services when you use them, either for the
short period of time or longer duration (for cloud based storage).
4. Cloud provides various services such as
i. IAAS: Infrastructure as a service
ii. PAAS: Platform as a service
iii. SAAS: Software as a service
IAAS:
Instead of creating a server room we will hire it from a cloud service provider. Here user
will not use its local computer, storage and processing resources rather it will use virtual machine
and virtual storage, servers, networking of third party. Here the client can deploy the OS (operating
system), application of his own choice. User can start, stop, configure and manage the virtual
machine instances and virtual storage.
PAAS:
User can develop and deploy applications. For ex. We are using various online editors to
write codes like online arduino IDE, C IDE, APIs, software libraries. Here we don’t need to install
anything. The cloud service provider will manage servers, network, OS and storage. The users will
develop, deploy, configure and manage applications on the cloud infrastructure.
RCR Institute of Management & Technology Page 11
Prepared By Mrs.P.Lalitha, Dept.of MCA Internet of Things
lOMoARcPSD|157 970 14

SAAS:
It provides complete software application or the user interface to the application itself. The
user is not concerned about the underlying architecture of cloud only service provider is responsible
for this. It is platform independent and can be accessed from various client devices such as
workstation, laptop, tablet and smart phone, running different OS. Ex: The online software we use
like online image converter, doc converter etc.
Big data analytics:
Big data refers to large amount of data which cannot be stored, processed and analysed
using traditional database like (oracle, mysql) and traditional processing tools. In big data analytics
BIG refers to 5 Vs.
 Volume
 Velocity
 Variety
 Veracity
 Value
Volume: volume refers to the massive amount of data generated from the IoT systems. There
is no threshold value for generated data. It is difficult to store, process and analyse using traditional
database and processing tools. Ex: The volume of data generated by modern IT, industrial and
healthcare system.
Velocity: The rate at which the data is generated from the IoT system. This is the primary
reason for the exponential growth of data. Velocity refers to how fast the data is generated and
how frequently it varies. Ex: Modern IT, industrial and other systems like social networking sites
are generating data at increasingly higher speed.
Variety: Variety refers to different forms of data. Since there are various domain of IoT so
various type of data are generated from different IoT domain. Those data is called as sparse data.
Those data include text, audio, video etc.. The variety of data is mainly divided into 3 types i.e.
 structured
 semi structured
 unstructured
Structured data: The data which has a fixed format to be stored is known as structured data.
The data stored in database like oracle, mySQL is an example of structured data. With a simple
query data can be retrieved from the database.
Semi-structured data: The data which has not a fixed format to be stored but uses some elements
and components through which they can be analysed easily is known as semi- structured data. Ex:
HTML, XML, JSON data
Unstructured data: The data which has not any fixed format. It is difficult to store and analyse. It
can be analysed after converting into structured data. Ex: Audio, video (gif, audio with lyrics),
Text (containing special symbols).
Veracity: The data in doubt is known as veracity. Sometimes what happen it is very difficult accept
the data stored in database. This happens due to typical error, corrupted storage ordata.
Value: It is efficient to access big data if we can turn it into values i.e we can find greater insights
from it so that we can perform some action to get the desired output. This will be beneficial for the
organization. Otherwise it has no use.
Embedded Systems:
1. An embedded system is a computer system that has hardware and software embedded to
perform specific task.
RCR Institute of Management & Technology Page 12
Prepared By Mrs.P.Lalitha, Dept.of MCA Internet of Things
lOMoARcPSD|157 970 14

2. The key components of an embedded system include microprocessor or micro controller,


memory (RAM, ROM, and Cache), networking units (Ethernet, Wi-Fi adapter), input/output
units (display, keyboard, etc) and storage (flash memory). They use some special types of
processor such as digital signal processor, graphics processor and application specific
processor). Embedded system uses embedded OS like RTOS.
3. Ex. Of embedded systems: digital watch, digital camera, vending machines.
Communication protocols:
1. Protocol is nothing but rules and regulations. Communication protocol is the backbone of
the IoT system.
 History of IoT
A world of omnipresent connected devices and sensors is one of the oldest tropes of science fiction. IoT
lore has dubbed a vending machine at Carnegie Mellon that was connected to APRANET in 1970 as
the first Internet of Things device, and many technologies have been touted as enabling "smart" IoT-
style characteristics to give them a futuristic sheen. But the term Internet of Things was coined in 1999
by British technologist Kevin Ashton.
At first, the technology lagged behind the vision. Every internet-connected thing needed a
processor and a means to communicate with other things, preferably wirelessly, and those factors
imposed costs and power requirements that made widespread IoT rollouts impractical, at least until
Moore's Law caught up in the mid '00s.
One important milestone was widespread adoption of RFID tags, cheap minimalist transponders
that could be stuck on any object to connect it to the larger internet world. Omnipresent Wi-Fi and 4G
made it possible to for designers to simply assume wireless connectivity anywhere. And the rollout of
IPv6 means that connecting billions of gadgets to the internet won't exhaust the store of IP addresses,
which was a real concern. (Related story: Can IoT networking drive adoption of IPv6?).
The main concept of a network of smart devices was discussed as early as 1982, with a
modified Coca-Cola vending machine at Carnegie Mellon University becoming the first ARPANET-
connected appliance, able to report its inventory and whether newly loaded drinks were cold or
not. Mark Weiser's 1991 paper on ubiquitous computing, "The Computer of the 21st Century", as well
as academic venues such as UbiComp and PerCom produced the contemporary vision of the IOT. In
1994, Reza Raji described the concept in IEEE Spectrum as "[moving] small packets of data to a large
set of nodes, so as to integrate and automate everything from home appliances to entire
factories". Between 1993 and 1997, several companies proposed solutions like Microsoft's at
Work or Novell's NEST. The field gained momentum when Bill Joy envisioned device-to-
device communication as a part of his "Six Webs" framework, presented at the World Economic Forum
at Davos in 1999.
The concept of the "Internet of things" and the term itself, first appeared in a speech by Peter T.
Lewis, to the Congressional Black Caucus Foundation 15th Annual Legislative Weekend in
Washington, D.C, published in September 1985. According to Lewis, "The Internet of Things, or IoT,
is the integration of people, processes and technology with connectable devices and sensors to enable
remote monitoring, status, manipulation and evaluation of trends of such devices."
The term "Internet of things" was coined independently by Kevin Ashton of Procter & Gamble,
later MIT's Auto-ID Center, in 1999, though he prefers the phrase "Internet for things". At that point, he
viewed radio-frequency identification (RFID) as essential to the Internet of things, which would allow
computers to manage all individual things. The main theme of the Internet of things is to embed short-
range mobile transceivers in various gadgets and daily necessities to enable new forms of
communication between people and things, and between things themselves.

RCR Institute of Management & Technology Page 13


Prepared By Mrs.P.Lalitha, Dept.of MCA Internet of Things
lOMoARcPSD|157 970 14

In 2004 Cornelius "Pete" Peterson, CEO of NetSilicon, predicted that, "The next era of
information technology will be dominated by [IoT] devices, and networked devices will ultimately gain
in popularity and significance to the extent that they will far exceed the number of networked
computers and workstations." Peterson believed that medical devices and industrial controls would
become dominant applications of the technology.
Defining the Internet of things as "simply the point in time when more 'things or objects' were
connected to the Internet than people", Cisco Systems estimated that the IoT was "born" between 2008
and 2009, with the things/people ratio growing from 0.08 in 2003 to 1.84 in 2010.
 About the Internet in IoT
What is the internet of things?
The IoT brings the power of the internet, data processing and analytics to the real world of
physical objects. For consumers, this means interacting with the global information network without
the intermediary of a keyboard and screen; many of their everyday objects and appliances can take
instructions from that network with minimal human intervention.
In enterprise settings, IoT can bring the same efficiencies to physical manufacturing and
distribution that the internet has long delivered for knowledge work. Millions if not billions of
embedded internet-enabled sensors worldwide are providing an incredibly rich set of data that
companies can use to gather data about their safety of their operations, track assets and reduce manual
processes. Researchers can also use the IoT to gather data about people's preferences and behavior,
though that can have serious implications for privacy and security.

How does the IoT work?


The basic elements of the IoT are devices that gather data. Broadly speaking, they are internet-
connected devices, so they each have an IP address. They range in complexity from autonomous
vehicles that haul products around factory floors to simple sensors that monitor the temperature in
buildings. They also include personal devices like fitness trackers that monitor the number of steps
individuals take each day. To make that data useful it needs to be collected, processed, filtered and
analyzed, each of which can be handled in a variety of ways.

Collecting the data is done by transmitting it from the devices to a gathering point. Moving the data can
be done wirelessly using a range of technologies or on wired networks. The data can be sent over the
internet to a data center or a cloud that has storage and compute power or the transfer can be staged,
with intermediary devices aggregating the data before sending it along.

Processing the data can take place in data centers or cloud, but sometimes that’s not an option. In the
case of critical devices such as shutoffs in industrial settings, the delay of sending data from the device
to a remote data center is too great. The round-trip time for sending data, processing it, analyzing it and
returning instructions (close that valve before the pipes burst) can take too long. In such cases edge-
computing can come into play, where a smart edge device can aggregate data, analyze it and fashion
responses if necessary, all within relatively close physical distance, thereby reducing delay. Edge
devices also have upstream connectivity for sending data to be further processed and stored.
The Identifiers in IoT
Identification plays an important role for the Internet of Things (IoT). First discussions in AIOTI
focused around the use of communication identifiers like IP addresses and mobile phone numbers in
IoT. This was triggered by similar discussions in the Body of European Regulators for Electronic
Communications (BEREC) [1]. However identification has a much wider scope and is relevant for
many applications and entities in IoT. Beside identification for communication means this includes

RCR Institute of Management & Technology Page 14


Prepared By Mrs.P.Lalitha, Dept.of MCA Internet of Things
lOMoARcPSD|157 970 14

identification of the things, but also for example of services, users, data and locations. Various
identification schemes already exist, have been standardized, and are deployed in the market.
To address the wider scope of identifiers in IoT, the AIOTI Working Group 03 (WG03) IoT Identifier
task force was set up. The task force objectives are to provide a thorough analysis of the identification
needs and related standardization for IoT, specifically:
- to evaluate identification needs for IoT and related requirements;
- and to describe existing identification standards and ongoing standardization work and
elabo- rate their applicability for IoT.
This public deliverable is the first outcome of the work of the task force.
 Identifiers in IoT
In any system of interacting components, identification of these components is needed in order to en-
sure the correct composition and operation of the system. This applies to all lifecycle phases of a sys-
tem from development to assembly, commissioning, operations, maintenance and even end of life. Es-
pecially in case of flexible and dynamic interactions between system components identification plays
an important role.
Identifiers are used to provide identification. In general an identifier is a pattern to uniquely identify a
single entity (instance identifier) or a class of entities (i.e. type identifier) within a specific context.
Definition: An identifier is a pattern to uniquely identify a single entity (instance identifier) or a
class of entities (i.e. type identifier) within a specific context.
Depending on the application and user need various types of identifiers are used.
IoT is about interaction between things and users by electronic means. Both things and user have to be
identified in order to establish such interaction. Various other entities are involved in the interaction
and are part of an IoT system and identification is also relevant for them. Figure 1 shows the different
entities with the related identifiers in the IoT Domain Model of the AIOTI WG03 High Level
Architecture.
Various identification schemes already exist, are standardized and deployed. This document
- evaluates IoT identification needs;
- classifies the different identification schemes;
- evaluates and categorises related requirements;
- provides examples of identifier standards and elaborates their applicability for IoT;
- discusses allocation, registration resolution of identifiers;
- considers security and privacy issues;
- and discusses interoperability of identifiers.
This is done from a high level viewpoint. The document does not define or recommend specific
solutions and standards, but provides examples and summaries in order to indicate what has to be
taken into ac- count for identifiers in IoT.
It should be noted that the document does not cover identity and identity management issues. An
identifier is usually part of the identity of an entity, but many other topics are relevant for identities and
are not discussed in the document. Specific coding technologies for identifiers like printed numbers,
bar codes or Radio Frequency Identification (RFID) are also not evaluated in the document.

RCR Institute of Management & Technology Page 15


Prepared By Mrs.P.Lalitha, Dept.of MCA Internet of Things
lOMoARcPSD|157 970 14

 The IoT Framework


Introduction
Today, the Internet has become a major part of the world. It finds application in every corner of the
globe. With the increasing use of the Internet, more appliances and devices are now being connected to
the web, forming the ‘Internet of Things,’ commonly known by its acronym ‘IoT’. The IoT is not just a
simple technology. It is a complex framework that includes several different technologies, designed to
work together in tandem. In this article, you will learn what the IoT framework is in detail, as well as
the Open-source IoT frameworks

What is IoT Framework?


Normally, when large data is being generated and transmitted across a number of devices, there
has to be a specific point where everything is collected and combined.
This specific point is very essential in a network, as it combines all data, making it possible to
understand the data being generated.
However, the smooth transmission and generation of data don’t just happen. Rather, it is usually
made possible by the Internet of Things Framework, (IoT framework). So, just what is IoT framework?
The Internet of Things (IoT) Framework can be described as being an ecosystem, comprising of
several connected devices that communicate with each other, over the Internet. These connected
devices usually work to transfer and sense data over the Internet, while requiring very little human
intervention.
The IoT framework is what makes it possible for the connected devices to have smooth communication
over the Internet. It is no wonder, then, that it is referred to as the ‘Internet of Things’ framework, or in
other words, the framework that facilitates the interaction of ‘Things’ (devices) over the Internet.

RCR Institute of Management & Technology Page 16


Prepared By Mrs.P.Lalitha, Dept.of MCA Internet of Things
lOMoARcPSD|157 970 14

IoT Framework Overview


The IoT framework is a very important element of technology in the modern world, finding application
in almost every sector. For instance, one of the major applications of the IoT is in the designing of
smart homes.
The IoT framework concept is also applied in the designing of different physical objects, such as
thermostats, electrical devices, security and alarm systems, as well as vending machines, among many
other objects.
Main Components of the Internet of Things Framework

major components of IoT Framework


The IoT Framework is comprised of four major components, as discussed below;
1) Device Hardware
The device hardware component of the IoT framework requires some basic knowledge on architecture.
The user is also required to have an idea on the working of the different micro-controllers, as well the
sensors.
Examples of hardware devices that form part of this IoT framework component are sensors, micro-
controllers and controllers.
2) Device Software
In order for the device software of the IoT framework to function properly, the included writing
applications are required to configure the controller, then operate them remotely. The user is required to
have a basic understanding of how an API works inside the micro-controllers, as well how libraries are
usually made for programming.
3) Communication and Cloud Platform
The cloud platform is one of the most crucial parts of the IoT framework. It calls for the basic
knowledge of all communication, whether wireless or wired. The user is also required to have a good
understanding of IoT integration, as well as the working of the cloud technology.
In summary, we can say the communication and Cloud Platform of the IoT Framework is where all
communications happen.

RCR Institute of Management & Technology Page 17


Prepared By Mrs.P.Lalitha, Dept.of MCA Internet of Things
lOMoARcPSD|157 970 14

4) Cloud Application
The cloud application is a type of software program, which mainly consists of components that
can be accessed quite easier and faster. These components can be either local or even cloud-based. The
cloud application works to improve the system, such that its maximum potential is realized.
In other words, the cloud application can be defined as the written application of an IoT frame work
that binds all the local hardware devices, as well as the cloud-based devices.
Open Source IoT Frameworks
In order to understand what an IoT framework open source is, consider these three facts;
1) Every consumer wishes that they can use any technology device of their choice, without being
limited or forced to use devices from just one particular vendor (for instance, some smart-watches
require that they are paired with only smart phones from the same vendor).
2) All dealers of IoT devices wish that the integration of their devices can be made much easier, and
even possible with a large number of different technology ecosystems.
3) Those who develop applications wish that they could support many different devices, which do not
require any developed vendor-specific codes.
The Open source framework is a solution to all the above challenges. It allows for such levels of scale
to be achieved, and also high flexibility levels. Most of the IoT framework open sources are free to
download and can be installed and launched quite easily.
The Internet world offers a large variety of open sources for the IoT Framework. So, just which open
source should you go for?
Top 10 Open Source IoT Frameworks
The following are the most recommended top 10 open source IoT frameworks;
1) KAA IoT
This particular IoT framework open source is most popular for its efficiency and the ‘rich’ services it
offers. The KAA IoT is a cloud platform that allows the users to materialize and implement all the
smart product concepts that they may be having.

While on the KAA IoT framework, the user has the ability to manage as many connected devices as
they prefer. This ability to manage the unlimited number of devices is made possible by the cross-
device interoperability of this platform. Also, the KAA IoT framework makes it possible to monitor the
connected devices, and even configure them from a remote location.
The KAA IoT cloud platform is not just known for being an efficient IoT framework open source, but it
is also one of the most flexible open-source solutions available. It is what allows for information to be
exchanged between the connected devices and other elements of the IoT framework.
2) MACCHINA.io
The MACCHINA.io open source can support a large number of different sensors, as well as
connection technologies. It also facilitates a JavaScript and C++ environment that is not only web-
enabled, but that is also extensible. Such an environment makes it easier to develop different IoT
gateway applications.
A good example of the application of the MACCHINA.io IoT framework open source is in the building
of smart homes and home automation systems. In the construction of smart homes, this open-source is
used for the development and deployment of device software for smart sensors and other automotive
telematics.
3) ZETTA
The ZETTA open source is more of a server-oriented platform. This means that its construction is
mainly developed around the REST, NodeJS, as well as the reactive programming philosophy that is
usually based on flow. This philosophy tends to be linked with the Siren hypermedia APIs, which are
later on abstracted as REST API

RCR Institute of Management & Technology Page 18


Prepared By Mrs.P.Lalitha, Dept.of MCA Internet of Things
lOMoARcPSD|157 970 14

The REST APIs of the ZETTA open source are then linked with the cloud services, such as
visualization tools. Being an API-oriented open-source, ZETTA mainly deals with the unlimited
streaming loads of data.
4) GE PREDIX
The GE PREDIX open-source framework is mainly built around the concept of cloud foundry. Despite
the fact that this IoT framework open source was developed for the internal operations of the GE, it has
now become one of the most popular and successful IoT platforms available.
The GE PREDIX open source allows for a user to efficiently manage assets, ensure the security
and real-time of connected devices, as well as facilitate the acquisition, storage and access of large
chunks of data.
5) ThingSpeak
ThingSpeak framework makes it possible for the users to not only analyze but also visualize data in
MATLAB. The fact that this particular open source IoT framework does this eliminates any need for
the user to buy a license for performing such services.
With the ThingSpeak open source, the collection and storage of sensor data is made possible, even in
private channels. Furthermore, this open-source allows for the sharing of sensor data in public
channels.
The most common uses for ThingSpeak open-source framework are providing alerts, tracking specific
locations and sensor logging.
6) DeviceHive
The DeviceHive is a free open source IoT framework. The package includes two deployment options;
Docker and Kubernetes. After downloading this open-source framework, the user can use it with either
a private or a public cloud. It can be changed very easily and is designed with its main focus being the
analysis of big data.
DeviceHive open source makes it possible for the user to run batch analysis, as well as machine
learning that exceeds the device’s information and data. It supports a variety of libraries, with the most
common libraries supported being Android and iOS. Some client libraries are also supported by open-
source, such as Python and Java.
7) Distributed Services Architecture
Like the name implies, the Distributed Services Architecture open-source functions to bring together all
the separate devices, applications and services, which are distributed in the given data model. This
open-source can be described as being a community library, which links the translation of protocols and
integration of data to the data sources of third parties
The main advantage of the Distributed Services Architecture is that it is lightweight, which
makes it more flexible and easier to use. It also includes a hardware integration support built into the
system.
8) Arduino
Arduino is one of the most recommended IoT framework open source, especially if you intend to own a
computer that perceives and has strong control over the world.
The Arduino open source is a combination of both the hardware and software systems of IoT, which
makes it very simple and easy to use.

The operation of the Arduino open-source is facilitated by several hardware specifications, that are
usually applied by the interactive electronics.
9) Node-RED
The Node-Red open source works as a visual tool that functions to wire together all the connected
hardware devices, services, as well as APIs. This open-source IoT framework usually does the wiring

RCR Institute of Management & Technology Page 19


Prepared By Mrs.P.Lalitha, Dept.of MCA Internet of Things
lOMoARcPSD|157 970 14

in new and unique ways than other open-source framework. Node-Red open source is developed
around Node.js. it can work on Raspberry Pi, as well as on other 60,000 different modules.
10) Flutter
The Flutter open-source framework is a processor core, that can be easily programmed for different
electronic projects. The fact that this IoT framework open source is programmable makes it very
popular among students and engineers .
The board of the Flutter open source is based on Arduino and is designed with a very powerful wireless
transmitter. Since flutter boards make fast interactions with each other, this eliminates the need for a
router. This open-source is also very simple and easy to use, which makes it very convenient.
 IoT and M2M
Machine to machine (M2M) refers to networking of Machines for the purpose of remote
monitoring and control and data exchange. The end-to-end architecture for M2M systems comprising of
M2M area networks, Communications Network and application domain.

An M2M area network comprises of machines which have embedded hardware module for
sensing actuation and communication. Various Communication protocols can be used for M2M local
area network such as Zigbee, Bluetooth, Modbus M –bus, wireless, power LINE Communication,
6LoWPAN.

These Communications protocols provide connectivity between M2M nodes within and M2M
area network. The Communications Network provides connectivity to remote m2m area network.
Communication network can use wired or wireless network. The M2M area network use either
proprietary or non IP based protocol.

The communication between the M2M nodes and the M2M Gateway is based on the
communication protocol. M2M Gateway protocol translation to enable IP connectivity for M2M. M2M
Gateway act as a proxy performing translation from / to native protocol to M2M area network.

M2M data is gathered into point solution such as enterprise applications, service management
application for remote monitoring applications. M2M has various application domain such as smart
metering, Home Automation, industrial Automation, smart grid.
DIFFERENCE BETWEEN IOT AND M2M
The difference between m2m and IoT are described as follows:Communication protocols:
M2m and IoT can differ in how the communication between the machines is device happens. M2M
uses other proprietary or not IP based communication protocol for communication with in the M2M
area networks. Commonly uses M2m protocol include zigbee, Bluetooth, ModBus, wireless M-Bus,
power line communication.
The focus of communication in M2M is usually on the protocols below the network layer. Focus
of communication in IoT is usually a protocol in network layer such as http web sockets, MQTT,
XMPP, DDS, and AMQP.
Machines in M2M vs Things in IoT:
The “things “IoT refers to Physical objects that have unique identifier and can sense and communicate
with the external environment or their internal physical status. The unique identifiers the things in IoT
are the IP addresses. Things have software component for accessing processing and storing sensor
information on controlling actuator connector. IoT system can include IoT devices of various types such
as fire alarms, door alarms, lighting control devices.
Hardware versus software emphasis:
RCR Institute of Management & Technology Page 20
Prepared By Mrs.P.Lalitha, Dept.of MCA Internet of Things
lOMoARcPSD|157 970 14

while the emphasis of M2M is more on hardware with embedded modules, the emphasis
modules, the emphasis of IoT is more on software . IoT devices run specialist software sensor Data
Collection, data analysis and interfacing with cloud through IP based communication.
Data collection and analysis:
M2M data is collected in point solutions and often in on premises storage infrastructure. In
contrast to M2M, the data in IoT is connected in the cloud. The analytical component analysis the data
and stores the result in the cloud database. Data and analysis results are visualized with the cloud based
applications. The centralized controller is aware of the status of all the nodes and sends Control
Commands to the nodes.
Applications:
M2m data is collected in point solutions and can be accessed by on premises application diagnosis
applications, service management applications, and on-premises enterprise application.
SDN and NFV for IoT :
Software defined networking (SDN) and the network function virtualization (NFV) and their
applications for IoT.
Software Defined Networking:
Software defined networking (SDN) is the networking architecture that separates the control plan from
the data plan and centralizes race the network controller. Conventional network architecture build with
specialized hardware (switches, router etc).
Network device in conventional architectures are getting exceedingly Complex with the increasing
number of distributed product has been implemented and the use of proprietary hardware and interfaces.
Control plan is the part of the network that carries the signal and routing message traffic while the data
plan is a part of network that carries the payloaddata traffic.
The limitations of the conventional network architecture as follows:Complex network devices:
Interoperability is limited due to the lack of standard and open interfaces. Network devices use
proprietary hardware and software and have slow product lifecycle limiting innovations . The
convention networks were well suited for static traffic pattern and had a large number of product was
decided for specific applications .which are applied in cloud computing environment traffic patterns
are more dynamic. Due to complexity of conventional network devices making changes in the networks
to meet the dynamic trafficpattern has become increasingly difficult.
Management overhead:
Conventional networks involve significant manager overhead. Network managers find it increasingly
difficult to manage multiple network devices and interfaces from multiple vendors. Up gradation of
network configuration changes in multiple devices.
Limited scalability:
The Virtualization technologies used in cloud computing environment has increased the number of its
host repairing network access IoT applications hosted in the cloud are distributed across multiple
virtual machines that require exchange of traffic.
Components of IoT applications run distributed algorithms on a large number of virtual machine that
require huge amounts of data exchange between virtual machines.
Such computing environment require highly scalable and easy to manage network architectures with
minimal manual configuration which is becoming raising a difficult with a conventional networks.
key Elements of SDN and follow:
Centralized network controller:
with Decoupled control and the data plan and centralized network controller, the network administrator

RCR Institute of Management & Technology Page 21


Prepared By Mrs.P.Lalitha, Dept.of MCA Internet of Things
lOMoARcPSD|157 970 14

can rapidly configure the network. SDN applications can be deployed Programmable open API. These
speeds have innovation as the network status no longer need to wait for other device vendors to embed
features in their proprietary hardware.
Programmable open APIs:
SDN architecture propose Programmable open API for interface between the SDN application and
control layers with these open API is various network services can be implemented such as routing
quality of services access.
Standard communication interface (Open Flow)
SDN architecture uses a standard communication interface between the control and infrastructure
layers. Open flow, which is defined by the open networking Foundation is the broadly accepted SDN
protocol for the southbound interface. Open flow, the forwarding plan of the network devices can be
directly accessed and manipulated.
Open floor uses the concept of close try different network traffic based on three different rules.
Floor can be programmed statically and dynamically by the SDN control software. Components of and
open flow switch comprising one or more tables and their group table which perform packet lookup and
forwarding, and open flow channels to an external Controller System open flow protocol is
implemented at both sides of the interface betweenthe controller and the network devices.
network function virtualization:
Network function virtualization is a technology that leverages virtualization to consolidate the
heterogeneous network devices on to industry standard high-volume service switches and storage.
NFV is complementary to SDN as NFV can provide at the infrastructure on which SDN can run. NFV
and SDN mutually beneficial to each other but not dependent. Network functions can be virtualized
without SDN which very beneficialto each other but not dependent
Elements of architecture as follows:
Virtualize to network function VNF:
VNF is software implementations of a network function which is capable of running over the enough
Infrastructures
NVF Infrastructure NFVI:
It into Computer Network and storage resources that are visualized.
NFV management and orchestrations: Orchestrations focuses on all visualization specific management
task and the covers the orchestrations and lifecycle management of physical and / or software resources
that support the infrastructure utilization and the lifecycle management of VNF.
NFV comprises of network functions implemented in software that run on Virtualized resources in the
cloud. NFC enabled separations of network function which are implemented in software from the
underlying hardware.

RCR Institute of Management & Technology Page 22


Prepared By Mrs.P.Lalitha, Dept.of MCA Internet of Things

You might also like