EAC3016

EAC3017FUNDAMENTALS OF SENSORS
FUNDAMENTALS OF SENSORSAND
ANDIoT
IoT
MODULE 3
Fundamentals of IoT

Dr J P Shritharanyaa
shritharanyaa@vitbhopal.ac.in
Assistant Professor Grade I
School of Electrical and Electronics Enigineering – Embedded Systems
VIT Bhopal University, Kothri Kalan, Madhya Pradesh
 Syllabus
Fundamentals of IoT:

Introduction, Definitions & Characteristics of IoT, Evolution IoT, IoT Architectures,

Physical & Logical Design of IoT, IoT frameworks.

Design Principles for Connected Devices:

Machine-to-Machine(M2M) Communications, Architectural components of M2M,

IoT versus M2M, M2M systems layers, and design standardization.
 IoT Definition
∙ A dynamic global network infrastructure with self-configuring capabilities based
on standard and interoperable communication protocols where physical and
virtual “things” have identities, physical attributes, and virtual personalities and
use intelligent interfaces, and are seamlessly integrated into the information
network, often communicate data associated with users and their environment.
 IoT Structure

COLLECT COMMUNICATE ANALYZE ACT

Characteristics of IoT
 Characteristics of IoT
∙ Dynamic and self-adapting
∙ Self-configuring
∙ Interoperable Communication protocols
∙ Unique identity
∙ Integrated into information network.
 Characteristics of IoT
∙ Dynamic and self-adapting: The IoT devices can dynamically adapt with sensed
environment, their operating conditions, and user’s context and take actions
accordingly. 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.

ex: Whenever there will be free wifi access one device can be connected easily.
 Characteristics of IoT
∙ Interoperable Communication: IoT allows different devices (different in architecture) to
communicate with each other as well as with different network.

ex: MI Phone is able to control the smart AC and smart TV of different manufacturer.

∙ 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.
 Characteristics of IoT
∙ 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.

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 through 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.

Ex: weather monitoring system. Here the information collected from different monitoring nodes
(sensors, arduino devices) can be aggregated and analysed to predict the weather.
IoT Architecture
 IoT Architecture
∙ The main stages in the IoT architecture diagram
consists of :

1. Sensors and actuators

2. Internet getaways and Data Acquisition Systems

3. Edge IT

4. Data center and cloud.

 Stage 1– Sensors & Actuators

∙ The process starts with sensors and actuators, the connected devices that monitor (in the case of
sensors) or control (in the case of actuators) some “thing” or physical process.

∙ Sensors capture data regarding the status of a process or an environmental condition.

∙ In some cases, a sensor might detect a condition or event that requires an almost immediate response
so that an actuator can perform remediation actions in real time, for example, adjusting the flow rate
of a fluid, or the movements of an industrial robot.

∙ To avoid the delay of a round-trip of data to the server, analysis of data to determine failure and
sending of control to the “thing”, this critical processing is performed in close proximity to the process
being monitored or controlled.
 Stage 2– Internet Gateways and Data Acquisition
Systems
∙ A data acquisition system (DAS) collects raw data from the sensors and converts it from analog into
digital format.

∙ The DAS then aggregates and formats the data before sending it through an Internet gateway via
wireless WANs (such as Wi-Fi or Cellular) or wired WANs for the next stage of processing.

∙ At this point, the volume of data is at its maximum.

∙ The quantities can be huge, especially, for example, in a factory setting where hundreds of sensors
may be gathering data simultaneously.

∙ For that reason, the data is also filtered and compressed to an optimum size for transmission.
 Stage 3– Pre-processing: Analytics at the Edge
∙ Once the IoT data has been digitized and aggregated, it will need processing to further reduce the
data volume before it goes to the data center or cloud.

∙ The edge device may perform some analytics as part of the pre-processing.

∙ Machine learning can be very helpful at this stage to provide feedback into the system and improve
the process on an ongoing basis, without waiting for instructions to come back from the corporate
data center or cloud.

∙ Processing of this type will generally take place on a device in a location close to where the sensors
reside, such as in an on-site wiring closet.
 Stage 4– In-depth Analysis in the Cloud or Data Center
∙ At Stage 4, systems can be brought to bear to analyze, manage, and securely store the data.

∙ This usually takes place in the corporate data center or in the cloud, where data from multiple field
sites/sensors can be combined to provide a broader picture of the overall IoT system and deliver actionable
insights to both IT and business managers.

∙ A company may have operations in different geographies and IoT data can be analyzed to identify key
trends and patterns, or to spot anomalies.

∙ At this level, industry-specific and/or company-specific applications can be used to perform in-depth
analysis and apply business rules to determine whether action needs to be taken.

∙ The incoming data may indicate desirable changes to device settings or other ways to optimize the process,
forming a loop that facilitates constant improvement.

∙ Stage 4 also includes storage in a data warehouse, both for record keeping and for further analysis.
Physical Design of IoT
 Things in IoT
∙ Things refers to the devices which have unique identities and can
perform remote sensing, actuating & monitoring capabilities.

∙ IoT devices can

o Exchange data with other connected devices

o Collect data from other devices

o Process the data locally or send the data to centralized servers

o Cloud based application back-ends for processing data

∙ IoT devices consists of several interfaces for connections to other

devices like:

o I/O interfaces for sensors

o Interface for internet connectivity

o Memory & storage interfaces

o Audio/video interfaces
 IoT Protocols

∙ Link layer
∙ Network/Internet layer
∙ Transport Layer
∙ Application Layer
 Link Layer Protocol
∙ It determines how the data is physically sent over the network’s physical layer.
∙ Hosts on the same link exchange data packets over the link layer protocols.
∙ This layer determines how the packets are coded and signalled by the hardware
device over the medium to which the host is attached.

LINK LAYER SPEED PURPOSE

PROTOCOLS
802.3 10Mbps to 40Gbps Ethernet
802.11 1Mbps to 6.75Gbps Wi-Fi
802.16 1.5Mbps to 1Gbps Wi-Max
802.15.4 40Kbps to 250Kbps LR-WPAN
2G/3G/4G 9.6Kbps to 100Mbps Mobile
Communication
 Network Layer Protocol
∙ Responsible for sending of IP datagrams from the source network to destination network.

∙ Performs host addressing and packet routing.

∙ The datagrams contain the source & destination addresses which are used to route them from source to
destination across multiple network.

∙ Host identification: IPv4, IPv6 & 6LoWPAN

∙ IP protocols establish connections on packet networks, but do not guarantee delivery of packets.

IPv4 32 bit address = 2^32 devices

IPv6 128 bit address = 2^128 devices
6LoWPAN Used to address low power device.
Operates in 2.4 Ghz with data rate of
250kbps
Works with 802.15.4 in link layer
 Transport Layer Protocol
∙ Provide end to end message transfer capability independent of the network.
∙ This capability can be setup on connections, either using handshakes(TCP) or
without handshakes (UDP)

∙ It provides functions as
o Error control

o Segmentation

o Flow control

o Congestion control
 Transport Layer Protocol - TCP
∙ Transmission Congestion Protocol

∙ Used for
o Web browser (HTTP)
o Email programs (SMTP)
o File transfer (FTP)

∙ Connection oriented and stateful protocol

∙ Ensures reliable transmission of packets in order

∙ Error detection capability: discard duplicate packets & retransmit lost packets

∙ Flow control capability: rate at which the sender sends data is not too high for the receiver to
process.

∙ Congestion control capability: avoid network congestion and collapse that leads to degradation of
network performance
 Transport Layer Protocol - UDP
∙ User Datagram Protocol
∙ Connectionless, transaction oriented and stateless protocol
∙ Useful for time sensitive applications that have very small data units to exchange
and do not want the overhead of connection setup.

∙ Does not provide

o Guaranteed delivery

o Ordering of message

o Duplicate elimination
 Application Layer Protocol - HTTP
Define how the applications interface with lower layer protocols to send the data
over the network.

∙ Hypertext Transfer Protocol

Base for WWW

Includes commands like: GET, POST, PUT, DELETE, HEAD, TRACE, etc

Follows request-response model

Stateless protocol

Each HTTP request is independent of other

HTTP client: web browser, application

 Application Layer Protocol - CoAP

∙ Constrained Application Protocol

∙ For M2M application under constrained environment
∙ Follows request-response model – run on top of UDP
∙ Client server architecture where clients communicate with server using
connectionless datagrams.
 Application Layer Protocol - WebSocket

∙ Full duplex communication over a single socket connection for sending messages
between client and server.

∙ Based on TCP
∙ Allows stream of messages to be sent back or forth between the client and server
while keeping the TCP connection open

∙ Client: browser, mobile application

 Application Layer Protocol - MQTT

∙ Message Queue Telemetry Transport

∙ Light weight messaging protocol based on publish subscribe model
∙ Use client server architecture
∙ The client connects to the server and publishes messages to topics on the server.
∙ The broker forwards the messages to the clients subscribed to topics.
∙ Suited for constrained environments where the devices have limited processing
and memory resources and network bandwidth is low.
 Application Layer Protocol - XMPP

∙ Extensible Messaging and Presence Protocol

∙ Used for real time communication and streaming XML data between network
entities

∙ Decentralized protocol-uses client server architecture

∙ Allow server to server communication as well
 Application Layer Protocol - DDS

∙ Data Distribution Service

∙ Data centric meant for M2M communication
∙ Use publish subscribe model
∙ Publisher – responsible to data distribution and Subscriber – responsible to
receive published data
 Application Layer Protocol - AMQP

∙ Advanced Message Queuing Protocol

∙ Publish Subscribe model
Logical Design of IoT
 LOGICAL DESIGN
∙ Logical design of an IoT system refers to an abstract representation of the entities
and processes without going into the low-level specifics of the implementation.

∙ IoT functional blocks:

Devices
Communication
Services
Management
Security
Application
 IoT COMMUNICATION MODELS
∙ Request – Response model
∙ Publish – Subscribe model
∙ Push-Pull model
∙ Exclusive Pair
 REQUEST RESPONSE MODEL
∙ Client send request to the server and server responds to the
request.

∙ It is a stateless communication model & each request-response

pair is independent of others.

∙ When server receives a request:

Decides how to respond

Fetches the data

Retrieves resource representation

Prepares the response

Sends the response to the client

 PUBLISH SUBSCRIBE MODEL
∙ Publishers- source of data.

It sends the data to the topics which are managed by

the brokers.

They are not aware of consumers

∙ Consumers – subscribe to the topics managed by

broker.

∙ When broker receives data from publisher, it sends

the data to all subscribe consumers.

 PUSH-PULL MODEL
∙ The data producers push the data to queues and

consumers pull data from the queues.

∙ Producers not aware of consumers.

∙ Queues:

Helps in decoupling the messaging between

producer & consumer.

Act as a buffer.

Helps in situation when there is a mismatch

between the rate at which the producers push

data and rate at which consumers pull data.

 EXCLUSIVE PAIR
∙ Bi-directional, full duplex model.

∙ Once the connection is setup it remains open until

client sends request to close the connection.

∙ Client – server can send messages to each other

after connection setup.

∙ It is a statefull connection.

∙ Server is aware of all open connection.

 IoT COMMUNICATION APIs
REST- based Communication APIs

∙ Representation State Transfer

∙ It is set of architectural principles used to design web services and web APIs
focuses on system’s resource and how resource states can be addressed and
transferred.

∙ Follow request-response model.

 REST- BASED COMMUNICATION APIs

REQUEST RESPONSE
COMMUNICATION WITH REST APIs MODEL USED BY REST
 REST ARHITECTURAL CONSTRIANTS
∙ Client-Server:

Separation of concerns.

Client – should not concern about the data storage.

Server – should not concern about user interface.

∙ Stateless:

Each request from client to server must contain all information necessary to understand the request.

It cannot take advantage of any stored context on the server.

∙ Cache-able:

Response to a request must labelled as cache-able or non-cache-able.

Cache-able: the client is given a right to reuse the response later for the same request.
 REST ARHITECTURAL CONSTRIANTS
∙ Layered system:

It constrains the behaviour of components such that each component cannot see beyond the
immediate layer with which they are interacting.

∙ Uniform interface:

It emphasis that the method of communication between client and server must be uniform.

Resources identified in the request & are themselves separate from the representation of the
resources that are returned to the client.

∙ Code on demand:

Server can provide executable code or scripts for clients to execute in their context.
 WEBSOCKET BASED COMMUNICATION APIs
∙ It allows bi-directional, full duplex communication
between client and server.

∙ It follow exclusive pair communication.

∙ It do not require any new connection to setup for each

messages to be sent.

∙ WebSocket APIs reduce network traffic & latency.

∙ It can used for IoT applications that have low latency

or high throughput requirements.
IoT Framework
 IoT Framework
∙ IoT (Internet of Things) is a network of devices which are connected to the internet
for transferring and sensing the data without much human intervention and the
frame work is used to achieve this.

∙ The framework has required capabilities for the cloud support and other needs
which is needed to satisfy the IoT technology.

∙ It allows device management, handles communication protocols on software and

hardware, collects / analyses information, improves information flow and intelligent
apps functionality.
 IoT Framework - KAA IoT
∙ KAA IoT is one of the most effective and rich Open Source Internet of Things Cloud
Platforms, where anyone can freely implement their smart product concepts.

∙ It can manage an N number of devices connected to each other with cross-device

interoperability on this platform.

∙ It can monitor the machine in actual time by providing and configuring remote
devices.

∙ KAA enables information exchange between linked devices, the IoT Cloud,
information and visualization systems, as well as other elements of IoT Ecosystems.
 IoT Framework - Cisco IoT Cloud Connect
∙ Cisco IoT Cloud Connect provides robust, automated, and highly secure connectivity
for the enterprise.

∙ IoT data management is done by the Cisco Kinetic IoT platform to extract, move and
compute the data.

∙ As Cisco is very famous for its security services, it protects IoT deployment against
threats with a secure IoT architecture.
 IoT Framework - ZETTA IoT
∙ Zetta is nothing but a server-oriented platform developed based on the REST,
NodeJS, and the Siren hypermedia-API-strip flow-based reactive programming
philosophy.

∙ After being abstracted as REST APIs they are connected with cloud services.
∙ These internet services include tools for visualizing machine analytics and support
such as Splunk.

∙ It builds a gero-distributed network through connectivity with systems like Heroku

to endpoints like Arduino and Linux hackers.
 IoT Framework - Salesforce IoT
∙ Salesforce is power by thunder.
∙ Thunder allows companies to unlock earlier unseen ideas and allows anyone to take
proactive, personalized activities from any device to bring their clients closer than ever.

∙ More than 150,000 clients worldwide were held by Salesforce.

∙ Salesforce has a 19.7% market share in the globe of CRM. SAP (12.%1), Microsoft (6.2%),
Oracle (9.1%) are far behind its nearest rivals.

∙ Many businesses now develop their apps or migrate to Salesforce on the Salesforce platform.
∙ This has raised demand for developers and administrators from Salesforce.
 IoT Framework - DeviceHive IoT
∙ DeviceHive is another rich IoT open-source platform that is distributed under the
Apache 2.0 license and can be used and changed free of charge.

∙ It provides deployment options for Docker and Kubernetes and can be downloaded
and used both by public and personal cloud.

∙ You can run batch analysis and machine learning above and beyond your device
information.

∙ DeviceHive supports several libraries, including Android and iOS.

 IoT Framework - Oracle IoT
∙ Oracle offers its flexible environment outstanding company possibilities to create
company applications.

∙ Oracle supports the processing and builds large-scale IoT networks with very wide
data.

∙ The use of advanced security systems to protect IoT systems against external
threats is another worth mentioning.

∙ Since these systems usually have different devices, some of which have no security
tool, it is not sufficiently justifiable to implement centralized security measures.
 IoT Framework - SAP IoT
∙ The SAP Internet of Things cloud platform has everything you need to build and
handle an IoT application.

∙ The SAP platform provides a convenient environment to remotely manage and

monitor all connected devices of your IoT system.

∙ In the SAP Platform a remote-devices we can connect directly or through cloud

service.

∙ Obviously, SAP can use IoT information to create machine learning and artificial
intelligence applications while maintaining recent technological trends.
 IoT Framework - Microsoft Azure IoT
∙ Without the Microsoft Azure solution, a cloud service giant with AWS and Google
Cloud platform, the comparison of our IoT platform will be not complete.

∙ The Microsoft Azure IoT Suite provides preconfigured solutions and the ability to
personalize and develop new solutions to meet the project requirements.

∙ The strongest safety mechanisms, superb scalability and simple integration with
your current or future systems are achieved through Microsoft Azure Internet of
thing Suite.
 IoT Framework - Google Cloud Platform
∙ Google Cloud is one of the best IoT systems available today with its end-to-end
platform.

∙ Google stands out from the others because it can process the large quantity of
information using Cloud IoT Core.

∙ Due to Google’s Cloud Data Studio and Big Query you get advanced analysis.
 IoT Framework - IBM Watson
∙ IBM Watson is very popular among the internet of thing platform among developers.
∙ The Bluemix hybrid cloud-supported Watson IoT platform allows developers to use
IoT-applications easily.

∙ IBM Watson manages the secure communication and also data storage.
∙ Real-time data exchange also is done by IBM Watson.
 IoT Framework - Hewlett Packard Enterprise
∙ Hewlett Packard Enterprise’s universal business platform offers scalability for its customers
by offering solutions to most of their problems.

∙ The platform provides cloud-based assistance or local support.

∙ In smart cities and the automobile industry, HPE universal of things platform was used
properly.

∙ The data monetization of several businesses has been carried out by HPE.
∙ Hewlett Packard Enterprise Collects analyzes information in order to grow the company.
∙ In the Hewlett Packard Enterprise M2M device management in Single point, Single seller.
 IoT Framework - DataV by Bsquare
∙ Bsquare takes its services seriously and has introduced the DataV application, the
hybrid framework for managing IoT services.

∙ It offers a variety of services that predict and analyze all of your ecosystem
problems.

∙ It Improves the condition maintenances.

 IoT Framework - Mindsphere by Siemens
∙ Mindsphere from Siemens provides a cost-effective platform as a service that is
ideal for application development.

∙ The cost-efficient platform allows you to connect all your appliances to a cloud
solution.

∙ In accordance with the DIn ISO / IEC 27001 standard, Siemens claims every stored
information is strictly confidential.

∙ It allows to regulate machine information in order to open fresh opportunities.

 IoT Framework - Ayla Network
∙ Ayla networks have developed their platform as a solution for enterprises.
∙ Agile Ayla networks have been established to support customers with the smooth
establishment of services, not only to develop the product.

∙ In addition to the Ayla agile platform, AMAP is an agile mobile app platform from
Ayla that develops and guides consumers through app development.
 IoT Framework - MBED
∙ The open-source service is available on the Apache 2.0 Arm MBED computer
platform.

∙ It involves cloud services, developer tools, and operating systems, that facilitate the
creation and operation of business goods.

∙ The service is designed to simplify users’ processes.

∙ MBED OS was designed to connect all your devices as an open-source platform.
∙ The platform provides services from over 60 partners and free access to a
community of 200,000 designers.
 IoT Framework - Amazon Web Services (AWS)
∙ Amazon Web Services (AWS) is an IoT platform provided by Amazon.
∙ This IoT platform provides cloud computing, database, and security services through the
AWS Console.

∙ There are so many other services such as Regions, Availability Zones, and Virtual Private
Clouds (VPCs).

∙ It helps to ease out the improving durability, distribution, availability of the application.
∙ It provides Registry for recognizing devices, Secure Device Gateway, Compatible Software
Development Kit for devices which AWS partnered with HW manufacturers like Intel,
Texas Instruments, Broadcom and Qualcomm.
 IoT Framework - RTI
∙ RTI is one of the IoT platforms that is the oldest and most pioneering provider and
also it is the most influent industrial of the internet of thing firm.

∙ Connext DDS is built especially for smart computers and their corresponding cyber-
physical systems.

∙ Connext DDS does not require response brokers, directory services, servers, as well
as administration, unlike messaging middleware designed mainly for IT systems.
Machine to Machine Communication
 M2M Communication

∙ Machine-to-machine (M2M) communication is the exchange of information

between machines.

∙ M2M is a network of physical objects capable of capturing information about their

state, communicating that information over a network without requiring human
interference, and using that information to control their operational behavior.
M2M Architecture and Components
 M2M Architecture
∙ M2M Device: Device capable of replying to request for
data contained within those devices or capable of
transmitting data autonomously.

∙ Sensors and communication devices are the endpoints of

M2M applications.

∙ Generally, devices can connect directly to an operator’s

network, or they will probably interconnect using WPAN
technologies such as ZigBee or Bluetooth.

∙ Backhaul to an operator’s network is than achieved via

gateways that encapsulate and manage all devices.

∙ Consequently, addressing and identifying, e.g., routing, of

the devices relies heavily on the gateways.
 M2M Architecture
∙ Devices that connect via gateways are normally outside
the operator’s responsibility but belong to M2M
applications that are provided by service or application
providers.

∙ Sensors and devices that connect directly into an

operator’s network (via embedded SIM, TPM and radio
stack or fixed line access) are endpoints of the network.

∙ Thus, the responsibility in terms of accountability, SLAs

etc., lies within the network operator (or virtual network
operator).
 M2M Architecture

∙ M2M Area Network (Device Domain):

Provide connectivity between M2M
Devices and M2M Gateways, e.g. personal
area network.
 M2M Architecture
∙ M2M Gateway: Equipment that uses M2M capabilities to
ensure M2M Devices inter-working and interconnection
to the communication network.

∙ Gateways and routers are the endpoints of the operator’s

network in scenarios where sensors and M2M devices do
not connect directly to the network.

∙ It ensures the devices of the capillary network may be

reached from outside and vice versa.

∙ These functions are addressed by the access enablers,

such as identification, addressing, accounting etc., from
the operator’s platform and have to be supported at the
gateway’s side as well.
 M2M Architecture
∙ M2M Applications: It contains the middleware layer
where data goes through various application services
and is used by the specific business-processing engines.

∙ M2M applications will be based on the infrastructural

assets that are provided by the operator.

∙ Applications may either target at end users, or at other

application providers to offer more refined building
blocks by which they can build more sophisticated M2M
solutions and services. e.g. customer care functionality,
elaborate billing functions, etc.

∙ Those services, or service enablers, may be designed and

offered by an application provider, but they might be
offered by the operator via the operator platform itself.
M2M System Layers and Standardization
 System Standardization
Internet Engineering Task Force (IETF)

∙ Initiated actions for addressing and working on the recommendations for the
engineering specifications for IoT.

∙ IETF suggests the specifications for the layers, and the engineering aspects for the
IoT communication, networks and applications.
 System Standardization
International Telecommunication Union for Telecommunication (ITU-T)

∙ Suggested a reference model for IoT domain, network, and transport capabilities for
IoT services and the applications.

European Telecommunication Standards Institute (ETSI)

∙ Initiated the development of a set of standards for the network, and devices and
gateway domains for the communication between machines (M2M).

∙ Proposed high-level architecture for applications and service capabilities.

 System Standardization
Open Geospatial Consortium (OGC)

∙ An International Industry Consortium, has also suggested open standards for sensor
discovery, capabilities, quality and other aspects with support to geographical
information web support.
System Layers
Thank You