FutureSkills PRIME: IoT

Training the Trainer program

Module 1: Fundamentals of IoT

Vaibhav Pratap Singh

CDAC Bangalore

Not for further circulation

 Seven layers of the OSI model By ISO

ISO-
International
Organization for
Standardization
Layering principle-
OSI- Open System
• Decompose Interconnection
communication into layers
of abstraction Topology: Star,
Mesh, Bus, Ring
• Separation of concerns
Switching: Circuit,
• Each layer can evolve Packet
independently
Type of networks:
LAN, MAN, WAN,
Internet

Not for further circulation

The Interaction between Layers in the OSI model

Not for further circulation

An exchange using the OSI model

Not for further circulation

 Internet of Things(IoT)
• Sensors and actuators gets connected to the
Internet through low power embedded
communication modules either through wired
or wireless medium for automated monitoring
and control

Not for further circulation

 IoT- A Brief History
• Actual idea of connected devices had been around since
the 70s- “embedded internet” or “pervasive computing”.
• Actual term “Internet of Things” was coined by Kevin
Ashton in 1999 during his work at Procter & Gamble
-working in supply chain optimization, wanted to attract
senior management’s attention to a new technology
called RFID.
• Because the internet was the hottest new trend in 1999 -
he called his presentation “Internet of Things”.
• IoT did not get widespread attention for the next 10 years.

Not for further circulation

The IoT Goal: Complete Ubiquity

Not for further circulation

 Characteristics of IoT
• Addressability
• Event driven architecture
• Ambient intelligence
• Complex system
• Semantic sharing
• Size, time and space considerations

Not for further circulation

 The Challenge of IoT
• Structural Aspects of IoT
– Environmental Characteristics
– Traffic Characteristics – huge data and communication reliability
– Volume & Scalability
– Durability & Interoperability
• Power system and Energy harvesting
• Security and privacy: physical, connectivity, data storage
• Managing and fostering rapid innovation is a challenge for
governments
• Testing of Multi-Discipline Systems
• Absence of governance and standardization

9
Not for further circulation
Convergence of Multiple Technologies

Networking

Embedded
Systems Automation
Wireless
Control Sensor
Systems Networks
MEMS

Big Data Robotics Microcontrollers

RFID Wireless
Communication
Cloud
Computing

10
Not for further circulation
HourGlass Architecture of IoT

Not for further circulation

 Data Flow Across Layers of IoT

Integrated
Application

Information
Processing

Network /
Communication
(Data Transmission)

Devices
(Information gathering)

12
Not for further circulation
 IoT in CDAC
Smart Building
U-Sehat ZLED
Integrated
Application

Information
Processing

Network /
Communication
(Data Transmission)

Devices
(Information gathering) INDUS-IoT
Ubi-DAC
Ubi-Sense
BLE-Mote
13
Not for further circulation
 Data Flow: Sensing/ Actuation
• Radio Frequency Identifier (RFID)
Tag
Integrated Application • Wireless Sensor Node
• Mobiles/ Tablets/ PCs
• Home Appliances
Information Processing

Network / Communication
(Data Transmission)
• GPS
• Robots
Devices
(Information
gathering)
• Alarms/Displays/Printers/Scanners
• … etc
14
Not for further circulation
 Data Flow: Network/Communication
• Internet
• Wired Networks
Integrated
Application • Wireless Personal Area Network
Information
(WPAN)
Processing • Wireless Local Area Network
Network / (WLAN)
Communication
• Cellular Data Networks
Devices
(Information • … etc.
gathering)

15
Not for further circulation
 Data Flow: Information Processing
• Data Centers
• Servers
Integrated
Application • Big Data
Information
• Cloud Computing
Processing
• Search Engines
Network /
Communication
• Information Security
Devices
• Artificial Intelligence
(Information
gathering)
• Intelligent Decision making
• … etc.
16
Not for further circulation
 Data Flow: Integrated Applications
• Smart Building
• Smart Grid
Integrated
Application • Smart City
Information
• Smart Healthcare
Processing
• Smart Transport
Network /
Communication
• Smart Logistics
Devices
• Environmental Monitoring
(Information
gathering)
• Big Data
• Cloud Computing
17
Not for further circulation
IoT from an Embedded Engineer Perspective

http://micrium.com/iot/devices/ Not for further circulation

IOT STANDARDS

Not for further circulation 14th September 2017

 Need & Urgency of IOT Standards

• IOT aims to connect various things around us to the Internet with

the use of smart sensors and actuators
• IOT devices have limited resources in terms of power, processing
capabilities, bandwidth etc.
• Existing set of protocols were not designed for such constraints
• Gartner Inc. forecasts that the total number of connected things
will reach 20.4 billion by 2020
• Need of a standards based layered architecture and protocol suite
considering the huge scale of implementation and influence on
public life

Not for further circulation

 Challenges

• Customers would be bound to one vendor for the entire end

to end solution
• Operational quality may not be uniform
• Systems might not work as expected
• Interoperability issues- incompatible with other solutions
• Scalability is a challenge
• Development of entire end to end solution- lesser
competition, monopolization of market and higher cost of the
product

Not for further circulation

 IOT Standards: International Scenario
Organizations
AllSeen Alliance
Open Interconnect Consortium
OneM2M
Thread Group
IEEE (Institute of Electrical and
Electronics Engineers)
ISO/IEC (International Organization for
Standardization/ International
Electrotechnical Commission)
ITU (International Telecommunication
Union)
Industrial Internet Consortium
Committees/Working Group
>170 members - Qualcomm, Cisco
Systems, Panasonic
>300 members - Intel, Samsung
Electronics, Dell, HP, Lenovo
8 standardization organizations,
industry consortia
>170 members - ARM Holdings,
Samsung, and Google’s Nest Labs
IEEE P2413
ISO/IEC JTC 1 (Joint Technical
Committee)
SG20 (Study Group)
>250 members - General Electric, Cisco
Systems, IBM, Intel and AT&T
Not for further circulation
Efforts
An open-source framework for service &
connectivity layer- build around AllJoyn
protocol
framework which enable interoperability of
IOT devices- IOTivity project
AllSeen merged into it
6 Defines an IoT service layer - middleware
Promoting a mesh networking protocol
standard for low-power devices around
homes
Liaison agreement with ZigBee
To turn the information from different IoT
platforms into commonly understood data
objects
Develop standards for IoT & facilitate
coordination between JTC 1 and other
organizations like IEEE, ITU etc.
For development of technical standards
enabling the Internet of Things on a global
scale
foster coordination among industries where
IOT and older M2M technologies
 IOT STANDARDS: NATIONAL SCENARIO

• Ministry of Electronics and Information Technology (MeitY),

GoI released its draft IoT policy in 2014.

• Focuses on creating an IoT industry in India worth of USD 15

billion by 2020 with a share of 5-6% of global IoT industry.

• Signifies the need of IoT standards meeting specific Indian

requirements.

Not for further circulation

 INDIAN EFFORTS
Organizations
Telecommunications Standards Development
Society, India (TSDSI)
Bureau of Indian Standards
Telecommunication Engineering Centre, DoT,
GoI
Seconded European Standardization Expert in
India
IOT for Smart Cities Task Force (IOT4SCTF)
Not for further circulation
Committees/Working Group
Working group 8 (WG8) on M2M to
study Indian requirements of M2M
and IoT Services
Setup two panels namely, Internet of
Things and Smart Infrastructure.
In 2014, five working groups (WGs)
formed - M2M gateway &
architecture, power, automotive,
health, safety and surveillance.
In June 2015, 6 new WGs formed -
security, smart cities, smart homes,
smart villages, agriculture, smart
environment and smart governance.
Focus areas - electrical and electronic
household products, ITS, smart cities,
ICT domains like M2M/IOT, Security,
5G, NFV/SDN etc.
Divided into three working groups on
usage scenarios, architecture and RFP
framework.
Efforts
Technical reports mentioning the study of
Indian use cases has been released by
TSDSI.
2015 – TSDSI joined the one M2M
consortium
Tasked to examine the progress of
International standards and identify the
gap and need of standards for India.
BIS works in close association with the
ISO/IEC initiatives.
WGs have released different technical
reports.
Have identified the need of a standardized
M2M service layer similar to the one
being promoted by the oneM2M
consortium.
It is playing a major role in converging the
various standardization efforts going on in
India with that at the International level.
It aims to develop standards, guidelines
and procedures for application of IoT to
various smart city solutions.
Released a draft IoT reference architecture
for smart cities.
 Conclusion - IoT Standards

• IoT is a diversified domain with plenty of organizations/consortia are working

towards standardizations at different layers of a layered architecture
• Sensor interface standardization is getting addressed by IEEE1451-99 at global
level
• Communication networks - plenty of possible standardized technologies with
Thread also picking up
• Service and connectivity layers - can be based on the new merged IoTivity
• oneM2M also defines the service layer/IoT platform and manages the
semantic interoperability as well.
• It will require a concerted effort of the major National and International
standards bodies to arrive at global standards for IoT.
• Pitch India’s interest at such global standardization organizations and
consortia and come up with guidelines/standards to fill in the gap, wherever
necessary.
• Important to address Security standards in IOT including Identity and Privacy.

Not for further circulation

 Need for a Reference Model & Reference
Architecture
• Fragmented architectures, no coherent unifying
concepts, solutions exist only for specific application
silos.
• No coherent approaches to implement IoT have been
finalized, yet.
• Little cross-sectorial re-use of technology and
exchange of knowledge.

Not for further circulation

 IoT-A: Reference Model &
Reference Architecture
• proposed by European Commission (Framework
Program 7)
• 17 Partners from 8 EU countries

• The mission of the IoT-A project is to develop an

architectural reference model for the interoperability
of Internet-of-Things systems, outlining principles
and guidelines for the technical design of its
protocols, interfaces and algorithms

Not for further circulation

 IoT-A: Aims & Objectives
• Providing guidelines for the technical design of
protocols, interfaces and algorithms
• Building the enabling architectural framework
for the IoT
• Federating heterogeneous IoT technologies
into a homogeneous IoT fabric and enabling
interoperability

Not for further circulation

 IoT Reference Model
• Reference model is a division of functionality
into elements together with the data flow
among those elements
• A Reference Model is an abstract framework
for understanding significant relationships
among the entities of some IoT environment
• The IoT Reference Model provides the highest
abstraction level for the definition of the IoT
Architectural Reference Model.

Not for further circulation

 IoT Reference Architecture
• Reference Architecture describes essential
building blocks as well as design choices to
deal with conflicting requirements regarding
functionality, performance, deployment and
security.
• Interfaces should be standardized, best
practices in terms of functionality and
information usage need to be provided.

Not for further circulation

 IoT-A Reference Model (ARM)
• A Generic Reference Model derived from
– Business considerations
– Application-based requirements
– Current technologies

• Able to generate different Reference

architectures depending on domain-specific
requirements to be used as a blueprint for
concrete architecture design
Not for further circulation
IoT ARM &Reference-Architecture
dependencies and Influences

Not for further circulation

IoT ARM &Reference-Architecture
dependencies and Influences

Not for further circulation

 IoT ARM
•A general discourse on the IoT domain
•An IoT Domain Model - top-level description – the sensors, services
and the users
•An IoT Information Model explaining how IoT information is going to
be modelled
•An IoT Communication Model in order to understand specifics about
communication between many heterogeneous IoT devices and the
Internet as a whole.

Not for further circulation

IoT-A RA's Views and Perspectives
• The recommended reference architecture provided high-level
architectural views and perspectives for constructing IoT
systems
• Views: different angles for viewing an architecture that can be
used when designing and implementing it.

Not for further circulation

IoT-A RA's Views and Perspectives
• Functional view: It consists nine functionality groups, each one with one
or more functional components.
• Information view: it describes the components that handle information,
the static and dynamic information flows through the system.
• Deployment and operation view: this view investigates how the IoT
component communicate with each other.

Not for further circulation

IoT-A RA's Views and Perspectives
• Functional view: It consists nine functionality groups, each one with one
or more functional components.

Not for further circulation

 IoT-A RA's Views and Perspectives
• Perspectives: set of tasks, tactics, directives and architectural decisions for
ensuring that a given concrete system accomplishes one or more quality attributes.
• Each perspective encompasses:
• a desired quality level
• relevant IoT requirements
• applicability to (types of) IoT systems
• activities to achieve the desired qualities
• architectural tactics to be used by architects

Not for further circulation

 The THING Architecture
• Sensing:
– Sensor/Transducer
– Actuators
– Analog Signal Conditioning
– Digitization
• Computing:
– Microprocessor
– Microcontroller
– Digital Signal Processor
– FPGA
– Memory/Storage
• Communication: Microcontroller
– Transceiver System on Chip
– BALUN
– RF Amplifier
– Matching Circuit
– Antenna
Not for further circulation
 Sensor Module
• Provides interface to sensors/ actuators
• Interface can be
– Simple analog
– Simple digital
– Conditioning circuit
– Filter design for the corresponding signal
– Any other interfacing required for the transducer

Not for further circulation

 Why Energy Harvesting?
• Mostly, IoT devices are powered by the batteries.
• Continuous communication of data, need of replaceable
batteries
• This solution of replacing battery may be effective for
small IoT system but for large IoT systems, this solution is
not effective – cost and management
• A promising solution to this problem is energy harvesting.
The different energy harvester architectures are
• (i) Harvest and Use: Just-in time energy is harvested and directly used. If
harvested energy is not enough, the system will remain in idle state.
• (ii) Harvest-Store-Use: Whenever available, energy is harvested and
stored which can be used in future at the time of requirement. Harvested
energy directly powers the system and is also stored for future use.
Not for further circulation
Energy Harvesting for The Things

Not for further circulation

 Processor Module
• Basic Requirements for selection of the
processor- ARM Cortex M series, MSP430, Atmel
– Low active power consumption
– Very low sleep mode current
– Quick wake up from sleep mode
– Memory availability as per the application
requirements
– IO capability for connecting various transducers
– Compatibility with the radio communication protocol

Not for further circulation

 Target Devices
• INDUS-IoT kit
• Raspberry pi
• Arduino

44
Not for further circulation
 INDUS-IoT Kit
• Microcontroller: ARM Cortex-M4F based Microcontroller clocked up to 170
MHz
• Inbuilt MCU Memory: 32 KB SRAM, 128 KB Flash
• External onboard Memory: 32Kbit EEPROM (SPI)
• Dedicated on board SWD hardware debugger (USB-SWD)
• Communication Ports: USB (Device),SPI, USART/UART, I2C, CAN
• Analog Ports: ADCs, DACs, Comparators
• Two headers with pin-outs of : SPI, USART/UART, I2C, CAN, GPIO, ADC,
Comparator
• On board Wireless RF Connectivity: WLAN (Wi-Fi) and Bluetooth/Bluetooth
Low Energy
• On board Optical Connectivity: Modulated IR Transmitter and Receiver for
remote control

Not for further circulation

 INDUS-IoT Kit
• On-board Sensors:
– 3Axis Digital Accelerometer
– Digital Temperature Sensor
– Digital Relative Humidity Sensor
– Digital Light Intensity Sensor
– MEMS based quasi-digital Microphone (PDM)
– Analog Temperature Sensor with Voltage output
– Potentiometer for analog ADC input
– Piezoelectric Buzzer
– 2 LED indicators
– 2 Push button switches

46
Not for further circulation
IoT Network Architecture

Not for further circulation

Multiple protocols for IoT

48
Not for further circulation
 Wireless Protocols for IoT
Zigbee 6LowPAN

LoRa

Bluetooth/BLE Wi-Fi

Not for further circulation Online reference

 Wireless Protocols for IoT
Protocol Name Zigbee 6LowPAN Bluetooth Wi-Fi LoRa

PHY and MAC IEEE 802.15.4 IEEE 802.15.4 IEEE 802.15.1 IEEE 802.11 LoRa MAC class
Layers Standards a,b,g,n A,B and C

Network Mesh, Tree, Mesh Piconet, Infrastructure, Star on Star

Topologies Star Scatternet Ad-hoc
Bandwidth 20 to 250 kbps 20 to 250 kbps 25 to 50 54 to 600 0.3 to 50kbps
Mbits/s Mbits/s
Network size 65,535 2^128 7 2007 62,500
Per Coordinator Per Edge Per Master Per Access Point Per Gateway
router
Security AES AES , IPSec AES AES , SHA AES

Success metrics Reliability, Inter- Cost, Speed, Flexibility Long range,

Power, Cost operability Convenience Power
with IP
backbone
Applications Home Smart Beacons, Data streaming Pollution
automation, Metering Indoor monitoring
Industrial localizations
automation
 The Gateway General Architecture

http://micrium.com/iot/devices/ Not for further circulation

C-DAC’s Gateway Architecture

Not for further circulation

IOT PLATFORMS & CLOUD FOR IOT

Not for further circulation

 IoT Platforms Evolution
• IoT platforms originated in the form of IoT middleware, which
purpose was to function as a mediator between the hardware
and application layers.
• Its primary tasks included data collection from the devices
over different protocols and network topologies, remote
device configuration and control, device management and
over-the-air firmware updates.

• To be used in real-life heterogeneous IoT ecosystems, IoT

middleware is expected to support integration with almost
any connected device and blend in with third-party
applications used by the device.

Not for further circulation

 IoT Platforms
• An IoT platform is a multi-layer technology that enables
straightforward provisioning, management, and automation
of connected devices within the Internet of Things universe.
• It basically connects your hardware, however diverse, to the
cloud by using flexible connectivity options, enterprise-grade
security mechanisms, and broad data processing powers.
• For developers, an IoT platform provides a set of ready-to-use
features that greatly speed up development of applications
for connected devices as well as take care of scalability and
cross-device compatibility.

Not for further circulation

 APIs
• The application program (or programming) interface, or API, is arguably
what really ties together the connected “things” of the “internet of things.”
• IoT APIs are the points of interaction between an IoT device and the
internet and/or other elements within the network.
• APIs are sets of requirements that govern how one application can
communicate and interact with another.
• An open API (public API) is publicly available that provides developers with
programmatic access to a proprietary software application or web service.
• In the simplest terms, an API allows one piece of software to interact with
another piece of software, whether within a single computer via a
mechanism provided by the operating system or over an internal or
external TCP/IP-based or non-TCP/IP-based network.
• A private API is an interface that opens parts of an organisation’s backend
data and application functionality for use by developers working within (or
contractors working for) that organization.

Not for further circulation

Cloud in IoT

Not for further circulation

IoT Platforms

Not for further circulation

IoT Platforms

Not for further circulation

 Prominent IoT Platforms
• Amazon Web Services
• Google Cloud IoT
• Microsoft Azure IoT Suite
• SAP IoT Platform
• Salesforce IoT
• Oracle IoT
• Cisco IoT Cloud Connect
• Bosch IoT Suite
• IBM Watson IoT

Not for further circulation

 Data Analytics in
IoT

PGDIoT-CDACB_Internal Use Only Not for further circulation

Data Analytics in IoT

Not for further circulation

Data Analytics in IoT

Not for further circulation

 References
• Data Communication and Networking by Forouzan
• Computer Networks by Andrew S. Tanenbaum
• https://startupsutras.org/the-iot-stack-the-need-for-an-hourglass-architecture-605326b3c0d9
• https://iotforum.org/wp-content/uploads/2014/09/120613-IoT-A-ARM-Book-Introduction-v7.pdf
• https://iotforum.files.wordpress.com/2013/07/iot-a.pdf
• http://ijcsse.org/published/volume5/issue8/p1-V5I8.pdf
• https://www.kaaproject.org/what-is-iot-platform
• https://www.rcrwireless.com/20161018/internet-of-things/what-is-an-iot-api-tag6-tag99
• https://en.wikipedia.org/wiki/Open_API
• https://iotforum.org/wp-content/uploads/2014/09/120613-IoT-A-ARM-Book-Introduction-v7.pdf
• https://iotforum.files.wordpress.com/2013/07/iot-a.pdf
• http://ijcsse.org/published/volume5/issue8/p1-V5I8.pdf
• Internet of Things – A Hands-ON Approach – Arshdeep Bahga, Vijay madisetti
• M. Marjani et al., "Big IoT Data Analytics: Architecture, Opportunities, and Open Research Challenges,"
in IEEE Access, vol. 5, pp. 5247-5261, 2017.
doi: 10.1109/ACCESS.2017.2689040
• da Silva, A.F., Ohta, R.L., dos Santos, M.N., Binotto, A.P., 2016. A cloudbased architecture for the internet of
things targeting industrial devices remote monitoring and control. IFAC-PapersOnLine 49, 108–113.

Not for further circulation

Thank You