IoT Fundamentals

IoT Fundamentals
V 1.0 (Sep-2017)
TABLE OF CONTENTS
1. Introduction
2. Exploring IoT Universe
3. Understanding a typical IoT Device
4. IoT Architecture
5. IoT Sensors
6. IoT Gateways
7. IoT Platform
8. Iot Northbound Protocols
9. Iot Southbound Protocols
10. IoT Applications
11. Basic IoT Use Cases
IOT FUNDAMENTALS
Introduction
Copyright 2017 Aricent. All rights reserved.

3
IOT FUNDAMENTALS
Internet of Things
Courtesy : Postscapesy

4
IOT FUNDAMENTALS
Basic Components of IoT
Sensors
Connectivity
People and
Processes

5
IOT FUNDAMENTALS
Sensors
6
IOT FUNDAMENTALS
Connectivity

7
IOT FUNDAMENTALS
People and Processes

8
IOT FUNDAMENTALS
IoT Applications

9
IOT FUNDAMENTALS
IoT Applications (Contd..)
10
IOT FUNDAMENTALS
IoT Use Cases
11
IOT FUNDAMENTALS
IoT Buzz !!
12
IOT FUNDAMENTALS
Exploring IoT Universe

13
IOT FUNDAMENTALS
Define Things

14
IOT FUNDAMENTALS
Exploring Things
Purpose of Things
Thing Makers
Categorizing Things
Connecting Input and Outputs
Connecting to the Network

15
IOT FUNDAMENTALS
Purpose of Things
Protection
Health
Omniscience
Human Connection
Mobility

16
IOT FUNDAMENTALS
Thing Makers
Artists
Engineers / Hacker / Developers
Designers
Crafters

17
IOT FUNDAMENTALS
Categorizing Things
Monitor: Babies, Elderly, Biometrics, Environment
Quantify: Activity, Compliance
Optimize: Energy, Water, Fuel
Protect: Security, Quality, Consistency

18
IOT FUNDAMENTALS
People Connecting to Things
ECG sensor
Motion sensor
Internet
Motion sensor
Motion sensor

19
IOT FUNDAMENTALS
Understanding a typical IoT

Device

20
IOT FUNDAMENTALS
IoT Devices

21
IOT FUNDAMENTALS
Iot Device Market Estimation
Courtesy : BI Informaticsy

22
IOT FUNDAMENTALS
Understanding a Typical IoT Device
Creating Command and Control
Connecting Inputs
Connecting Outputs
Connecting via TCP/IP
Connecting via Bluetooth

23
IOT FUNDAMENTALS
Creating Command and Control
CPU
Low Power
10% of Desktop CPU or less
ARM (or similar) low power instruction set
Programmed in C or Assembly language
Memory
From 128 KiloBytes to 8/16 MegaBytes
Much slower than Desktop systems
Read Only, Read Mostly, Flash, Static Courtesy : Ciscoy
Timer(s)
Typically Multiple timers
Time-of-Day
High Resolution
Programmable (one-shot)

24
IOT FUNDAMENTALS
Connecting Inputs
Analog Inputs
Static Digital Inputs
Advanced Digital Inuts

25
IOT FUNDAMENTALS
Connecting Outputs
Analog Outputs
Static Digital Outputs
Pulse-width Modulated (PWM) Digital Outputs
Electrically Isolated Digital Outputs (Relay)

26
IOT FUNDAMENTALS
Connecting to the Network
Wired Ethernet
Wifi
Bluetooth
Custom RF (ZigBee, 6LoWPAN etc)
Courtesy : Ciscoy

27
IOT FUNDAMENTALS
Connecting Via TCP/IP
Highest Speed
IP and/or DNS
Any Supported Protocol (HTTP, FTP, Telnet, SSH, etc)

28
IOT FUNDAMENTALS
Connecting via Bluetooth
Bluetooth Low Energy (aka Bluetooth Smart)
Slow Data rate
IoT Devices maintain and proffer state/status

29
IOT FUNDAMENTALS
IoT Architecture

30
IOT FUNDAMENTALS
Typical Architecture of IoT Network
REST
HTTP / MQTT
ZigBee, BLE, 6LoWPAN

31
IOT FUNDAMENTALS
Field Deployment Example
Cloud
Servers
The
Internet
The Internet
Network
level
Gateway
Network
Device Communications
level
Thing
Sensors &
Actuators
User/Environment 2 sensors
IEEE 802.15.4
2.4GHz RF System

32
IOT FUNDAMENTALS
Things
We can turn almost every object into a thing.

A thing still looks much like an embedded system currently.
A thing generally consists of four main parts:
Sensors & actuators
Microcontroller
Communication unit
Power supply
A thing has the following properties:
Its usually powered by battery. This implies limited source of energy.
Its generally small in size and low in cost. This limits their computing capability.
It doesnt usually perform complicated tasks.

33
IOT FUNDAMENTALS
Communications
A thing always feature communications for team working

The Role of Communications
Providing a data link between two nodes
Communication type:
Wireline (e.g. copper wires, optical fibers)
Wireless (e.g. RF, IR). RF-based communication is the most popular choice
Popular RF-based communication solutions:
IEEE 802.15.4
IEEE 802.11 (or Wifi)
Bluetooth
Near Field Communication (NFC), e.g. RFID

34
IOT FUNDAMENTALS
Networks
The Roles of Networks

Managing nodes (discovery, join, leave, etc).
Relaying data packets from the source to the destination node in the network.
Networks are a distributed system. All nodes need to perform networking related tasks.
RF-based Network in IoT is usually a Wireless Multi-hop Network. Some examples:
Wireless Sensor Networks (WSNs)
Mobile Wireless Ad hoc Networks (MANETs)
Wireless Mesh Networks (WMNs)
Vehicular Ad Hoc Networks (VANETs)
and others...

35
IOT FUNDAMENTALS
Gateway
For a practical deployment, a gateway is often needed in a network.

It offers relaying packets between the network and the Internet.
The Internet
Data link Gateway
Network

36
IOT FUNDAMENTALS
End To End Message Flow
Thing Thing
Application Application
TCP/UDP TCP/UDP
Network (IP) Network (IP)

IEEE 802.15.4 IEEE 802.15.4 Wireless
PHY/MAC PHY/MAC Medium
Server
Application Gateway
TCP/UDP
Network (IP) Network (IP)
IEEE 802.3 IEEE 802.3 IEEE 802.15.4

(Ethernet) The (Ethernet) PHY/MAC
Internet

37
IOT FUNDAMENTALS
IoT Sensors

38
IOT FUNDAMENTALS
Connecting Inputs - Sensors
They are mainly input components

They sense and collect surrounding information
Programmable devices
Off-the-shelf gadgets/tools
Type of Sensors:
Environmental: Temperature, Humidity, Pressure, Flame, Smoke
Motion: IR, Ultrasound, Shock, GPS
Light: Intensity, Presence (Photo Resistor), Image
Physical: Switches, Pressure, Proximity, Accelerometer, Gyroscope, Tilt
Electrical: Resistance, Magnetic

39
IOT FUNDAMENTALS
Sensors

40
IOT FUNDAMENTALS
Sensors (Contd..)

41
IOT FUNDAMENTALS
Sensors (Contd..)

42
IOT FUNDAMENTALS
IoT Gateways

43
IOT FUNDAMENTALS
IoT Gateway
Not all devices connect directly via Wi-Fi

as they may use different kinds of radio
technology to transmit data.
Essentially a gateway acts as a bridge between
the IoT devices and the Internet beyond.
Gateways can connect to the IoT devices that
communicate via specific protocols, store and
parse the information and then send them
over to cloud servers for processing and
analytics.
IoT gateways not only abstract the medium
of communication but also provide the secure
channel required for the transmission of this
data.
Connect the things such as Home appliances,
clocks, cars, robots etc. with the cloud.
Helps in quickly converting data to be cloud
enabled which can be downloaded and
analyzed.
Publish the data to cloud services such as text
messages or email etc.
Can use analytics data applications e.g. SLAM
Data
Can support Edge computing

44
IOT FUNDAMENTALS
IoT Gateway Market

45
IOT FUNDAMENTALS
Aricent IoT Gateway

Northbound Interfaces
OneM2M AWS-IoT CIoT OpenADR OPC-UA
Remote Management OneM2M Service Layer Edge Computing
Security
Application Data Local Application Hosting
OMA DM
Enablement Containers Framework
Database
AWS-IoT Subscription Notification Services Rule Execution & CEP Framework
Southbound Interfaces
Zigbee Zwave BT/BLE Wifi Modbus DNP3 DLMS-COSEM
SW Platform
Protocol
Database Java OSGi Drivers
Stacks
Linux
HW Platform: Aricent Designed IoT Gateway Hardware based on Qseven Modules or Partner Gateway Reference Design
Q7 Cellular Ethernet
ZigBee ZWave CAN Bluetooth Wi-Fi USB ports
Processor (3G/LTE) Switch
Aricent SW / HW
Third Party / Open Source SW

46
IOT FUNDAMENTALS
Aricent IoT Gateway features
Southbound Protocols and Device Integration: Supports various southbound interfaces and protocols towards devices:
such as ZigBee, Wi-Fi, Bluetooth, DLMS-COSEM, LWM2M, etc.
Northbound Interfaces: Supports various northbound interfaces towards IoT Cloud platforms such as Aricent Converged
IoT, OneM2M, AWS IoT, IBM Bluemix, MS Azure, etc.
Edge Computing: Provides a User Deployable Local Application Hosting Environment, Rule Engine and Event Processing
Framework which enables analyses of IoT data close to where it is collected, and thereby, minimizes latency, offloads gigabytes of
network traffic from the core network, and it keep sensitive data inside the network.
OneM2M Service Layer: OneM2M Standards based Service layer which exposes the Gateway Services to M2M Applications
and Devices via standard reference points based on RESTful interfaces. Implemented using Java OSGi Framework.
Security: TLS Certificate based northbound interface authentication and encryption, Secure Southbound interface as per the
respective standards, User Authentication and Access Control, SW Signing and Authentication, Secure key store.
Monitoring and Diagnostics: Health Monitoring of IoT GW SW components, auto-recovery in case of failures. Alarms,
Statistics, Logs and Traces for Diagnostics.
Licensing Framework: Supports Node Locked, Time-based, Feature-based Licenses.
Remote Management: Remote Management of the GW (including Configuration Management, Software Management) via
OMA-DM standard interface with support for DevInfo Management Object, Software Component Management Object (SCOMO),
Gateway Management Object (GwMO), etc.
Local Management: Web & Command Line based user interface for local management & monitoring of the gateway.
HW Platforms: Integrated with various HW Platforms such as Aricent IoT HW, Intel IoT GW, Marvel IoT GW, Freescale iMx6
based boards, etc.

47
IOT FUNDAMENTALS
IoT Platform

48
IOT FUNDAMENTALS
AWS IoT
Courtesy : Amazon

49
IOT FUNDAMENTALS
AWS IoT
AWS IoT is a managed cloud platform that lets connected devices easily and securely interact with cloud
applications and other devices.
AWS IoT can support billions of devices and trillions of messages, and can process and route those messages
to AWS endpoints and to other devices reliably and securely.
With AWS IoT, applications can keep track of and communicate with all your devices, all the time, even
when they arent connected.
AWS IoT makes it easy to use AWS services like AWS Lambda, Amazon Kinesis, Amazon S3, Amazon
Machine Learning, Amazon DynamoDB, Amazon CloudWatch, AWS CloudTrail, and Amazon Elasticsearch
Service with built-in Kibana integration, to build IoT applications that gather, process, analyze and act on
data generated by connected devices, without having to manage any infrastructure.

50
IOT FUNDAMENTALS
Microsoft Azure IoT
Courtesy : Microsofty

51
IOT FUNDAMENTALS
Microsoft Azure Services
Devices Device Connectivity Storage Analytics Presentation & Action
Machine
Event Hubs SQL Database App Service
Learning
Table/Blob Stream
Service Bus Power BI
Storage Analytics
External Data Notification

DocumentDB HDInsight
Sources Hubs
External Data
Data Factory Mobile Services
Sources
BizTalk
Services
Courtesy : Microsofty

52
IOT FUNDAMENTALS
IBM Bluemix
Cloud based platform for building, managing and running applications of all types.
Offers Platform as a Service (PaaS)
Build Web apps, Mobile Apps, IoT apps quickly
Provides large collection of services, a service can be open source, 3rd party.
Examples of services - Runtime servers, Analytics, Database, Logging, monitoring
Enables integration of all services to create Apps quickly.
Focus on core app building logic, rest all reuse the existing services available through Bluemix.
IBM Bluemix offers various set of services:
Databases
Web Applications and Devops
Mobile
Security
Cloud Integration
Big Data
Internet of Things (IoT)
Cognitive Analytics (through IBM Watson)

53
IOT FUNDAMENTALS
Aricent Converged IoT Platform
Delivers a Complete Device Management Solution

Connect devices with MQTT, AMQP, Stomp, and other protocols
Add devices through self registration, REST services, or in batches
Control large numbers of devices using batch command operations
Provides massively scalable device event management solution
Offers highly tuned MongoDB and HBase implementations
Embeds Siddhi for Complex Event Processing (CEP)
Provides libraries for platforms such as Android and Arduino
Offers Asset Management Features
Deploy to any provider that supports Docker
Deploy to public clouds such as Microsoft Azure or Amazon EC2
Supports Advanced Multitenancy
Run any number of IoT applications on a single CIoT instance
Offers separate data storage per tenant with no intermingling

54
IOT FUNDAMENTALS
Aricent Converged IOT Platform Solution Overview
1. Chips & Devices

Converged IoT Solution
4. Customer Applications
Parking 3. Cloud IoT Infrastructure Asset Tracking
sensors Wearable application
Converged IoT Platform Smart Metering application
Street Lighting application
Lighting 2. Connectivity Infrastructure Device Management Smart Parking application
controllers
Device-Asset mapping
LTE IoT REST, HTTP,
Solutions & MQTT
Gateway Enterprise Integration
Smart
meters
Big Data & Analytics
Multi Tenancy
Wearables
What is the Converged IoT Platform?

Aricent defined and developed Horizontal platform comprising hardware and/or software elements across the IoT solution
Asset architecture that supports vertical applications across different segments
Tracking Converged because Converges multiple elements into an EtE IoT use case, Converges multiple applications across
(In-house developed or different segments on a single platform, Converges multiple technologies into a solution, Converges multiple disciplines
through partnership)
CIS: Smart Wearable CIS: Smart Infrastructure CIS: Smart Energy

Core IoT Platform Core IoT Platform Core IoT Platform
ADAPT Middleware for Devices IoT Gateway IoT Gateway
Cloud applications Smart parking, lighting & metering application Energy management application
Sensors through partners Meters from Partners

55
IOT FUNDAMENTALS
Key Features
Device Events/ Storage Reporting

Connectivity Commands
Multiple time series data storage Reporting framework integration
support Web based reports
Multiple protocols support like High speed event ingestion Hadoop integration Pre-configured, Adhoc reporting
MQTT, AMQP, REST, CoAP, Support for Measurements, Alerts, Search engine Report to PDF, CSV conversion
WebSockets etc. Location events Structured & unstructured data Support of charts/graphs
Direct devices & devices behind Commands to devices/gateway Short term and long term storages Scheduled reports
gateway connectivity Optional ACK for events and BI tools integration support Reports via email
SSL/TLS support commands
Message Priority & QoS support
Optional Compression
Device Stream Processing Analytics Integration

Management Configurable event & command
Services Services
processing chain
Configurable CEP engine
Device types & attributes R & Spark integration Enterprise integration such as SAP,
Stateful event detection
Device groups Machine learning Oracle, Salesforce etc.
Push notifications via different
Device auto registration Timeseries models SMS and Email
channels
Device status & SW version Predictive models Android Push Notifications
Machine learning integration
Remote software deployment & Image recognition iOS Push Notifications
upgrades for individual device or Number plate recognition Social Network integration
batch of devices Spark Integration support
Schedule upgrades & Throttling Flexible publish/subscribe
Upgrade status & retries

56
IOT FUNDAMENTALS
Key Features
Location Services Security Services System Configuration UI

Configuration
GeoFences/Zones Encrypted data and storage Responsive UI
Access control for GeoFence areas SSO Support Site management
OAUTH2 REST API support Users & Roles
Time based GeoFences User management
SSL/TLS Support Integration with external IAM
GeoFence violation Device & Asset management
HIPAA compliant storage /directory
GeoFence proximity detection System configuration
Audit logs Multiple sites support
Navigation support Contextual help
Hierarchical support like buildings,
Indoor positioning UI Internationalization
floors etc.
Processing chains for each site
Video Services Asset Platform Features Monitoring UI

Management
IP camera integration Multi-Tenancy Support System health monitoring
Live A/V stream ingestion Highly Scalable Statistics & Log viewer
Transcoding Asset categories Customizable for different Real time device status
Video storage Flexible asset attributes applications Map view
FF/RW of video Device to Asset / Person / Location On-Premise & Cloud deployable Job Scheduler
VoD & DVR services Assignment status SDK for different devices HTML/PDF System reports
Live streaming to multiple devices Dynamic associations SDK for application development Responsive UI
Different codecs support Asset association history UI Internationalization

57
IOT FUNDAMENTALS
IoT Northbound Protocols

58
IOT FUNDAMENTALS
MQ Telemetry Transport (MQTT)
MQTT is a Lightweight message queueing and

transport protocol
MQTT, as its name implies, is suited for the
transport of telemetry data (sensor and actor data)
MQTT is very lightweight and thus suited for M2M,
WSN and IoT Scenarios where sensor and actor nodes
communicate with applications through the MQTT
message broker.
Example:
Light sensor continuously sends sensor data to
the broker.
Building control application receives sensor data
from the broker decides to activate the blinds.
Application sends a blind activation message to
the blind actor node through the broker

59
IOT FUNDAMENTALS
MQTT Key Features
Lightweight message queueing and transport protocol

Asynchronous communication model with
messages(events)
Low overhead (2 Bytes header) for low network bandwidth
applications
Publish / Subscribe (PubSub) Model
Decoupling of data producer (Publisher) and data
consumer (Subscriber) through topics (Message Queues)
Simple Protocol, aimed at low complexity, low power and
low footprint implementations (e.g Wireless Sensor
Networks)
Runs on connection oriented transport (TCP).
MQTT caters for (wireless) network disruptions

60
IOT FUNDAMENTALS
Constrained Application Protocol (CoAP)
It is a specialized web transfer protocol for use with

constrained nodes and constrained (e.g., low-power,
Client Server lossy) networks
Client-Server based architecture
REST architecture for CRUD operations on resources
Very small footprint, RAM, ROM

61
IOT FUNDAMENTALS
CoAP Key Features
Constrained web protocol fulfilling M2M Requirements

Security binding to Datagram Transport Layer Security (DTLS)
Asynchronous Message Exchanges
Low overhead header and parsing complexity
URI and Content-type support
Simple proxy and caching capabilities
UDP binding with optional reliability supporting unicast and multicast requests
A stateless HTTP mapping, allowing proxies to be built providing access to CoAP resources via HTTP
in a uniform way or for HTTP simple interfaces to be realized alternatively over CoAP.

62
IOT FUNDAMENTALS
OneM2M
It is a software layer
Automotive Home Energy Health It sits between M2M applications and
Application Application Application Application communication HW/SW that provides data
transport
It normally rides on top of IP
Common Service Layer It provides functions that IoT applications
Common functions applicable to different application domains across different industry segments
commonly need. Those functions are
Communication Devices & Hardware exposed to Applications via developer
friendly APIs.
It allows for distributed intelligence (device,
Communication Technologies & Protocols gateway, cloud apps)
Automotive Communication
Home Networks
Energy Health
Automotive Home Energy Health

63
IOT FUNDAMENTALS
OneM2M Common Service Functions
Registration
Discovery
Security
Group Management
Data Management & Repository
Subscription & Notification
Device Management
Application & Service Management
Communication Management
Network Service Exposure
Location
Service Charging & Accounting

64
IOT FUNDAMENTALS
OMA LWM2M
LwM2M Enabler defines the application layer communication protocol between a Server and a Client
ClientServer Protocol is based on an open IETF standards
CoAP is an alternative to HTTP for RESTfull APIs in resourceconstrained area
CoAP and DTLS are bound to UDP or SMS bearers
Typically :
In LwM2M, the Server resides in a Data Center and the Client resides in the Device
LwM2M separates Protocol Commands and Data Object (as in OMA DM 1.x and 2.0 )
LwM2M Enabler is focused on constrained M2M devices (lowpower C, low amount of Flash &
RAM)
Applicable to Cellular, 6LoWPAN, WiFi or any other IP based constrained devices or networks
Public registry of Objects from OMA, other SDOs or enterprises
ClientServer Protocol based on CoAP
(HTTPlike protocol adapted to constrained context)
Extensible Object and Resource model for application semantics
A Client has one or more Object Instances
An Object is a collection of Resources
A resource may be Read, Written or Executed and Observed
A Resource may contain :
a piece of information (value)
a reference to an other Object Instance
Resources can have multiple instances

65
IOT FUNDAMENTALS
OMA LWM2M (Contd..)
Categories of LwM2M Operations

Bootstrap operations
Discovery/Registration operations
Device Mgt & Serv. Enablement Operations
Observe & Notify operations (Information reporting)
LwM2M Operations are mapped on :
GET, PUT, POST and DELETE CoAP Operations

66
IOT FUNDAMENTALS
OpenADR

67
IOT FUNDAMENTALS
OpenADR Features and Benefits

68
IOT FUNDAMENTALS
IoT Southbound Protocols

69
IOT FUNDAMENTALS
ZigBee
Technological Standard created for control and

sensor networks
Based on the IEEE 802.15.4 standard
Wireless personal area networks (WPANs)
High Level communication
Frequency Band up to 2.4 GHz

70
IOT FUNDAMENTALS
General Characteristics
Star Network: Data rates of 20 kbps and upto 250 kbps

Support for low latency devices
CSMA-CA Channel Access
Low Power usage consumption
3 Frequency bands with 27 channels
Extremely low duty cycle (< 0.1 %)
Supports large number of nodes
Very long battery life
Supported Data Transfer models
Star
Mesh Network: Mesh
Peer to Peer

71
IOT FUNDAMENTALS
ZWave
Z-wave technology based devices operates in

ISM band
Developed for low bandwidth data
communication applications such as security
sensors, home automation, alarms etc
Architecture based on master and slave in
mesh mode
Distance supported is 30 meter in indoors, 100
meters in outdoors

72
IOT FUNDAMENTALS
Low Powered RF communications technology

that supports full mesh networks without the
SLAVE - 1 SLAVE - 2 SLAVE - 3 need for a coordinator node
Operates in the sub-1GHz band
Impervious to interference from Wi-Fi and
other wireless technologies in the 2.4-GHz range
PRIMARY (Bluetooth, ZigBee, etc.)
CONTROLLER The Z-Wave PHY and MAC layers are
defined by ITU-T Recommendation G.9959.
SLAVE - 4 SLAVE - 5
Designed specifically for control and status apps,
supports data rates of up to 100kbps, with
AES128 encryption, IPV6, and multi-channel
SECONDARY
CONTROLLER operation
Full interoperability through layer 6 with
backwards compatibility to all versions.
ZWAVE NETWORK
The Z-Wave Network is of the mesh
architecture.
More than one Z-Wave Network can co-exist.
A Z-Wave network can consist of 232 nodes to
the max.

73
IOT FUNDAMENTALS
Modbus
Modbus Client (Master)

SCADA HMI Client/Server communications protocol designed by
Modicon in 1979 for use with its PLCs
Openly published and free of royalties or licensing fees
The most common industrial communications protocol in
the US
RS-232/485 Internet
Used widely for Building Management Systems
Passes raw words of bits without processing them
Modbus Device (Slave) Modbus Device (Slave)
Originally a serial protocol very similar to RS-485, it now
has a TCP variant
Basic Modbus protocol does not support floating point or
Modbus network ASCII
A MODBUS Request is the message sent on the network by
the Client to initiate a transaction
A MODBUS Indication is the Request message received on
the Server side
Query A MODBUS Response is the Response message sent by the
Station Number Server
Function Code A MODBUS Confirmation is the Response Message
Station Number
Data Bytes
Function Code
received on the Client side
(Flexible)
Data Bytes
Error Check (Flexible)
Error Check
Response
Query Response Cycle

74
IOT FUNDAMENTALS
It is scalable in complexity. A device, which has only a simple purpose, need only implement one or two
message types to be compliant.
It is highly scalable in scope. A collection of devices using MODBUS/TCP to communicate can range up to
10,000 or more on a single switched Ethernet network.
It is simple to administer and enhance. There is no need to use complex configuration tools when adding a
new station to a Modbus/TCP network.
There is no vendor-proprietary equipment or software needed. Any computer system or microprocessor with
Internet style (TCP/IP) networking can use MODBUS/TCP.
It is very high performance, limited typically by the ability of the computer operating systems to
communicate. Transaction rates of 1000 per second or more are easy to achieve on a single station, and
networks can be easily constructed to achieve guaranteed response times in the millisecond range.
It can be used to communicate with the large installed base of MODBUS devices, using conversion products,
which require no configuration.

75
IOT FUNDAMENTALS
Bluetooth Low Energy (BLE)
Bluetooth low energy is a NEW, open, short range

radio technology
Also known as Bluetooth SMART
Target Applications:
Wireless battery-powered sensors e.g. heart
rate, thermometer
Location tracking and information serving e.g.
Beacons
Requirements for target applications
Low Power
Low Cost
Low bandwidth
Low latency
Bluetooth Low Energy Architecture

76
IOT FUNDAMENTALS
Optimized for ultra low power

Enable coin cell battery use cases
< 20mA peak current
< 5 uA average current
Everything is optimized for lowest power consumption
Short packets reduce TX peak current
Short packets reduce RX time
Less RF channels to improve discovery and connection time
Simple state machine
Single protocol
It does not support streaming.
It has a data rate of 1Mbps, but is not optimized for file transfer.
It is designed for sending small chunks of data (exposing state)
Its good at small, discrete data transfers.
Data can triggered by local events.
Data can be read at any time by a client.
Interface model is very simple (GATT)

77
IOT FUNDAMENTALS
IoT Applications

78
IOT FUNDAMENTALS
Intelligent Home

79
IOT FUNDAMENTALS
Smart Egg Tray

80
IOT FUNDAMENTALS
Smart Washing Machine

81
IOT FUNDAMENTALS
Smart Lighting

82
IOT FUNDAMENTALS
Smart A/C

83
IOT FUNDAMENTALS
Smart Sleep System

84
IOT FUNDAMENTALS
Smart Weather Station

85
IOT FUNDAMENTALS
Smart Slow Cooker

86
IOT FUNDAMENTALS
Smart Garbage Cans

87
IOT FUNDAMENTALS
Smart Gardening

88
IOT FUNDAMENTALS
Basic IoT Use Cases

89
Voice based Home Automation
ALEXA HOME AUTOMATION
Alexa Home Automation Demo High level message flow

Customer: The person interacting
Alexa , Turn with the Alexa-enabled device and
Alexa Service
On The
Kitchen Light owner of cloud-enabled devices
Smart Home
Skill
The Smart Home Skill API: A
service that understands the voice
commands and converts them
Amazon Echo
to directives (JSON messages) that
Directive: Turn are sent to smart home skills
On Request
Kitchen Light
AWS Lambda: A compute service
offered by Amazon Web
Services (AWS) that hosts the smart
home skill code, which is called a skill
BLe AWS Lambda adapter
Photo Frame Smart home skill: Code and

configuration that interpret directives
and send messages to a device cloud
ZigBee
Aricent CIoT
Device cloud: The cloud
Aricent GW environment provided by a device
Kitchen Light Device cloud
vendor that controls and manages the
customers cloud-enabled devices
Home/ Office Network Internet

91
ARICENT IOT GATEWAY FRAMEWORK
Message Flow - Discovery of Devices
Amazon Cloud Service
User Amazon Alexa Skill AWS Lambda

Echo Service CIoT
Skill Adaptor
User Speaks to
Alexa
Echo Sends Audio to
Alexa service
Alexa Service send Json based Command to discover
message to AWS skill Adapter devices in account of
user
Json Message
Response contains
Amazon Echo details of devices
Speaks Sends audio response to List of devices
response to echo
user

92
ARICENT IOT GATEWAY FRAMEWORK
Message Flow Voice Command Invocation
Amazon Cloud Service IoT Gateway

CIoT Zigbe
Amazon AWS Lambda ZigBee
User Alexa Service CIoT e/BLE
Echo Skill Adaptor Adapter /BLE
IPE
User Speaks to
Alexa
Echo Sends Audio
to Alexa service CIoT sends data
Alexa Service send Json based
to CIOT adapter CIoT Adapter
message to AWS skill Adapter
JSON message to invoke Invoke
inSendscluding Device command based command
ID and Action on device intended for
mapping IPE sends
device in IoT
data to
Gateway
intended
device over
the air
Response
Response
over the air
Response Successful/
Successful/ unsuccessful
unsuccessful
Json
to CIoT
Message
Amazon Echo Response
Speaks Sends audio response to Json Message Response
response to echo
user

93
HOME AUTOMATION DEMO
LIVE Demo from lab
94
Smart Parking
SMART PARKING DEMO
Smart Parking Demo - Setup
Smart Parking Application UI
ARICENT Converged IoT Platform

96
SMART PARKING DEMO
Smart Parking Demo High Level Message Flow
Smart Parking WSO2 API

IOT GW CIOT Platform Microservice Manager Smart Parking UI

97
SMART PARKING DEMO
LIVE Demo from lab
98
Headquarters
303 Twin Dolphin Drive
Redwood City, CA 94065
USA
Tel: +1 650 632 4310
Thank You.
www.aricent.com

IoT Fundamentals

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

IoT Fundamentals

Uploaded by

Copyright:

Available Formats

IoT Fundamentals

Copyright 2017 Aricent. All rights reserved.

Copyright 2017 Aricent. All rights reserved.

Basic Components of IoT

Copyright 2017 Aricent. All rights reserved.

Copyright 2017 Aricent. All rights reserved.

People and Processes

Copyright 2017 Aricent. All rights reserved.

Copyright 2017 Aricent. All rights reserved.

IoT Applications (Contd..)

IoT Use Cases

Exploring IoT Universe

Copyright 2017 Aricent. All rights reserved.

Copyright 2017 Aricent. All rights reserved.

Connecting Input and Outputs

Connecting to the Network

Copyright 2017 Aricent. All rights reserved.

Copyright 2017 Aricent. All rights reserved.

Engineers / Hacker / Developers

Copyright 2017 Aricent. All rights reserved.

Monitor: Babies, Elderly, Biometrics, Environment

Quantify: Activity, Compliance

Optimize: Energy, Water, Fuel

Protect: Security, Quality, Consistency

Copyright 2017 Aricent. All rights reserved.

People Connecting to Things

Copyright 2017 Aricent. All rights reserved.

Understanding a typical IoT

Copyright 2017 Aricent. All rights reserved.

Copyright 2017 Aricent. All rights reserved.

Iot Device Market Estimation

Copyright 2017 Aricent. All rights reserved.

Understanding a Typical IoT Device

Creating Command and Control

Connecting via TCP/IP

Connecting via Bluetooth

Copyright 2017 Aricent. All rights reserved.

Creating Command and Control

Copyright 2017 Aricent. All rights reserved.

Static Digital Inputs

Advanced Digital Inuts

Copyright 2017 Aricent. All rights reserved.

Static Digital Outputs

Pulse-width Modulated (PWM) Digital Outputs

Electrically Isolated Digital Outputs (Relay)

Copyright 2017 Aricent. All rights reserved.

Connecting to the Network

Custom RF (ZigBee, 6LoWPAN etc)

Copyright 2017 Aricent. All rights reserved.

Connecting Via TCP/IP

Any Supported Protocol (HTTP, FTP, Telnet, SSH, etc)

Copyright 2017 Aricent. All rights reserved.

Connecting via Bluetooth

Bluetooth Low Energy (aka Bluetooth Smart)

Slow Data rate

IoT Devices maintain and proffer state/status

Copyright 2017 Aricent. All rights reserved.

Copyright 2017 Aricent. All rights reserved.

Typical Architecture of IoT Network

ZigBee, BLE, 6LoWPAN

Copyright 2017 Aricent. All rights reserved.

Field Deployment Example

Copyright 2017 Aricent. All rights reserved.

We can turn almost every object into a thing.