INTERNET OF THINGS

INTRODUCTION TO IOT

1
 OUTLINES

 Introduction to IOT
 Definition and Characteristics of IoT
 Architecture of IoT
 IoT Layers

I5IT422E Dr.Suresh Sankaranarayanan 05/01/2018 2

 INTERNET OF THINGS (IOT)

The Internet of Things (IoT) is the network of physical

objects—devices, vehicles, buildings and other items
embedded with electronics, software, sensors, and
network connectivity—that enables these objects to
collect and exchange data

I5IT422E Dr.Suresh Sankaranarayanan 05/01/2018 3

 COMPONENTS OF IOT

I5IT422E Dr.Suresh Sankaranarayanan 05/01/2018 4

 Where is IoT

Wearable Tech

Healthcare

Smart Appliances
I5IT422E Dr.Suresh Sankaranarayanan 05/01/2018 5
 IoT- NoT New Technology
 NO!!!
 IoT integrates leading technologies such as:
 Advanced M2M communication
 Autonomic networking
 Data mining
 Security and privacy
 Cloud computing
 Advanced sensing and actuation

I5IT422E Dr.Suresh Sankaranarayanan 05/01/2018 6

 Definition of IoT

I5IT422E Dr.Suresh Sankaranarayanan 05/01/2018 7

 IoT Data Flow

I5IT422E Dr.Suresh Sankaranarayanan 05/01/2018 8

 IoT characteristics
Dynamic and self adapting
e.g:-Surveillance cameras
Self- Configuring
-allowing a large number of devices to work
e.g:-Weather monitoring
Interoperable Communication Protocols
-for communicate with other devices and infrastructure
Unique Identity
- IP address and URI
Integrated into Information Network
- allows to communicate and exchange data with other devices and systems

I5IT422E Dr.Suresh Sankaranarayanan 05/01/2018 9

 IoT Reference Architecture
 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
 Layers are :
 Client/external communications - Web/Portal, Dashboard, APIs
 Event processing and analytics (including data storage)
 Aggregation/bus layer – ESB and message broker
 Relevant transports - MQTT/HTTP/XMPP/CoAP/AMQP, etc
 Devices
 Cross Cutting layers are Device Management and Identity Access
Management

I5IT422E Dr.Suresh Sankaranarayanan 05/01/2018 10

I5IT422E Dr.Suresh Sankaranarayanan 05/01/2018 11
  Device Layer : Bottom layer of architecture. Devices can be of
various types, but in order to be considered as IoT devices,
they must have some communications that either indirectly 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 device 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

I5IT422E Dr.Suresh Sankaranarayanan 05/01/2018 12

 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,or provided by a secondary chip)
• A UUID provided by the radio subsystem (e.g. Bluetooth
identifier, Wi-Fi MAC 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 an unchangeable ID provided
by the core hardware) as well as an OAuth2 Refresh and
Bearer token stored in EEPROM

I5IT422E Dr.Suresh Sankaranarayanan 05/01/2018 13

  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
• Constrained application protocol (CoAP)
MQTT is a publish-subscribe messaging system based on a
broker model. The protocol has a very small overhead (as little
as 2 bytes per message), and was designed to support lossy
and intermittently connected networks. MQTT was designed to
flow over TCP. In addition there is an associated specification
designed for ZigBee-style networks called MQTT-SN (Sensor
Networks).

I5IT422E Dr.Suresh Sankaranarayanan 05/01/2018 14

 CoAP is a protocol from the IETF that is designed to provide a
RESTful application protocol
modeled on HTTP semantics, 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 approach. CoAP is designed to be used over UDP
 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:
The ability to support an HTTP server and/or an MQTT broker to talk to the
devices;
The ability to aggregate and combine communications from different
devices and to route communications to a specific device (possibly via a
gateway)
The ability to bridge and transform between different protocols, e.g. to
offer HTTP based APIs that are mediated into an MQTT message going to
the device
I5IT422E Dr.Suresh Sankaranarayanan 05/01/2018 15
  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. The first of
these is to use a big data analytics platform. This is a cloud-
scalable platform that supports
technologies such as Apache Hadoop to provide highly
scalable Mapreduce analytics
on the data coming from the 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.

I5IT422E Dr.Suresh Sankaranarayanan 05/01/2018 16

 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 the ability 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 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.

I5IT422E Dr.Suresh Sankaranarayanan 05/01/2018 17

  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 like
Fully Managed, Semi Managed and Non-Managed.
 Identity and Access Management: This layer provides following
services like:
Token Issuing and Validation
XACML PDP
Directory of user’s (LDAP)
Policy Management for access Control (Policy control Point)

I5IT422E Dr.Suresh Sankaranarayanan 05/01/2018 18

 IoT Protocols

I5IT422E Dr.Suresh Sankaranarayanan 05/01/2018 19

IoT Communication Models
IoT Communication Models
IoT Communication Models
IoT Communication Models
 IoT Communication APIs

 Two communication APIs

 REST-Based Communication APIs
 Web Socket Based Communication APIs
 REST-Based Communication APIs

Principles (constrains):
 Client-Server
 Stateless: request contains all information needed to
understand it
 Cache-able: Response can be marked as cache-able. If
so, client can reuse response later on.
 Layered system: a component cannot see beyond its
scope
 Uniform system: communication method between
client and server is uniform
 Code on demand: servers can provide executable
code or scripts for clients (optional)
 REST-Based Communication APIs

 Request- Response Model used by REST

 HTTP request methods and Actions
 Web Based Communication APIs

 Bi directional
 Full duplex communication b/w client and server
 Do not require a new connection to be setup for each
message to be sent
 Suitable for IoT Applications with low latency or high
throughput requirements
IoT Enabling Technologies
 IoT Levels & Deployment Template

 An IoT system comprises of the following components:

 Device
 Resourse
 Controller service
 Database
 Web service
 Analysis component
 Application
Level 1 :Monitoring node performs analysis, stores data, No cloud
Level 2: Monitoring node performs analysis, Cloud for storage
Level3: Node Monitors, Cloud for storage and analysis
Level4: Monitoring nodes perform local analysis, Cloud storage
Endpoints/Routers, coordinator, Cloud for storage and analysis
multiple monitoring nodes, centralized controller
Cloud for storage and analysis
 Domain Specific IoTs

 IoT Applications
 Home
 Smart Lighting
 Smart Appliances
 Intrusion Detection
 Smoke and Gas detectors
 Environment
 Weather Monitoring
 Air Pollution Monitoring
 Noise Pollution Monitoring
 Forest Fire Detection
 Domain Specific IoTs

 Cities
 Smart Parking
 Smart Roads
 Structural Health Monitoring
 Emergency Response
 
 Domain Specific IoTs

 IoT Applications
 Home
 Smart Lighting
 Smart Appliances
 Intrusion Detection
 Smoke and Gas detectors
 Environment
 Weather Monitoring
 Air Pollution Monitoring
 Noise Pollution Monitoring
 Forest Fire Detection
 Domain Specific IoTs

 Cities
 Smart Parking
 Smart Roads
 Structural Health Monitoring
 Emergency Response
Domain Specific IoTs
 Domain Specific IoTs

 IoT Applications:
 Retail
 Inventory Management
 Smart Payments
 Smart Vending Machines
 Agriculture
 Smart Irrigation
 Green House Control
 Health anf Life Style
 Health and Fitness Monitoring
 Wearable Electronics
 
 Domain Specific IoTs

 Energy
 Smart Grids
 Renewable Energy Systems
 Prognostics
 Logistics
 Route Generation and Scheduling
 Fleet Tracking
 Shipment Monitoring
 Remote Vehicle Diagnosis
 Industry
 Machine Diagnostics
 Indoor Air Quality Monitoring
