The document discusses the need for standardization in the Internet-of-Things (IoT). It notes that IoT involves a highly heterogeneous set of sensors, devices, and data that needs interoperability standards. It describes some existing standards for different IoT layers including networking, data formats, protocols, and interfaces. The document advocates for both syntactic and semantic interoperability standards and outlines Tata Consultancy Services' contributions to various standards bodies.

1. 1Copyright © 2014 Tata Consultancy Services Limited
Dr. Arpan Pal
Principal Scientist and Head of Research
Innovation Lab, Kolkata
Tata Consultancy Services
Standardization in Internet-of-Things
BIS 9 July 2016

2. 2
Click to edit Master title styleNeed for Standardization in IoT

3. 3
Internet-of-Things Horizon
Extract
http://www.internet-of-things-research.eu/pdf/IERC_Position_Paper_IoT_Standardization_Final.pdf

4. 4
Internet-of-Things – at the peak of the Hype?
Revenue Potential - $300+ Billion for Technology and Services
Economic Value - $1.9 Trillion
50 Billion Connected Devices by 2030
Gartner, 2014

5. 5
Pervading all aspects of our life – Internet-of-Everything
Humans
Physical
Objects and
Infrastructure
Computing
Infrastructure
Physical
Context
Discovery
INTERNET OF EVERYTHING
Physical Context
Discovery
What is happening,
where and when
People Context
Discovery
Who is doing what,
where and when, who is
thinking what
Internet
of
Digital
Internet
of
Things
Internet
of
Humans
ABI Research. May 7, 2014

6. 6
Internet-of-Things – what does it really mean?
M2M Communication
Sensing the human – quantified self
Embedded software
and Hardware
Cloud, Mobile, Big Data
and Analytics
Wireless Sensor Networks,
Pervasive Computing
Sensors
and Actuators

7. 7
Too much diversity – Interoperation is the Key
• Highly heterogeneous set of sensors and devices
• Huge scale
• Pervasively distributed sensors, fixed and mobile
• Mobile phones as sensors
• Continuous evolution of devices, apps and domain specfic
interface standards
• Third party / crowd-sourced apps
Sensor Network characteristics
• Application level - RESTful Sensor Web with Resource Catalog
and Discovery
• Data level - Semantic meta-models for sensors and
observations
• Network level - Network Proxies and Syntax Transcoders
How interoperability can be achieved
Ref : Defined by IEEE P2413

8. 8
An example of Mobile-Health as use case
Health Center/Home
TCUP
Web Request
Patient
Records
Social
Network
Healthcare
Portal
Expert Doctor
 Elderly People Monitoring
 Chronic Patient Monitoring
Networking:
ReST web service
Secure HTTP
GPRS / 2G, Bluetooth
Sensing:
Android Sensor APIs
Wearable
Data:
XML schema Storage
Application:
Programming Interfaces
Data:
Time-series of
HeartRate, Blood
Pressure, PPG, ECG,
Activity…
Sensor
Gateway
Cloud

9. 9
Click to edit Master title styleNetwork Layer Standardization
Have to allow all communication
standards to co-exist

10. 10
Sensor to Gateway - Wi-Fi / Zigbee / Bluetooth Trends
WiFi Direct
• P2P WiFi
• No need for an access point
802.11ac
• The fifth generation WiFi
• Up to 6.9 Gbps
802.11ac: The Fifth Generation of Wi-Fi Technical White Paper,, CISCO, August, 2012
• Long battery life (periodic or intermittent transfer with Sleep
modes)
• Verticalized Profiles
• Popular in Healthcare, Factory Automation, Apps that
need mobile phone as a gateway
• BLE – low power profile, but yet to proliferate

11. 11
Gateway to Cloud – TV White Space Spectrum
• http://gigaom.com/2010/09/23/get-ready-to-innovate-fcc-approves-white-spaces-rules/
The Federal Communications Commission unanimously approved new rules
for the unlicensed use white spaces, the empty or under utilized TV spectrum
that many are hoping could lead to a new form of super Wi-Fi.
The release of such spectrum could make White Spaces bigger than Wi-Fi.

12. 12
Need for Lightweight Protocols at Application Layer
Presentation / Application HTTP / ??
Transport TCP /
IP/routing IPv6, IETF RPL
Adaptation IETF 6LoWPAN
Medium-access / Physical WiFi, Bluetooth, Zigbee
Source : http://openwsn.berkeley.edu
Is HTTP too heavy for Sensor Data Upload?
CoAP / MQTT / ZeroMQ
UDP

13. 13
Lightweight Protocols
CoAP
Specialized web transfer protocol for use with constrained
nodes and constrained networks
 proposed by IETF CoRE Working Group
 Over UDP
MQTT
Lightweight broker-based publish/subscribe messaging protocol
for constrained devices. open, simple, lightweight and easy to
implement.
 Developed by IBM , Eurotech
 Under OASIS - an open standards organization:
 Over TCP
ZeroMQ
Socket-like API with provision to Enque if receiver is not ready
 Open Source
 Over TCP
 High-speed asynchronous I/O engines, in a tiny library
IPSO Alliance | Enabling the
Internet of Things
MQTT.ORG
Code Connected - zeromq

14. 14
TCS Contribution to IETF
NON_NORESPONSE
CoAP-Auth-lite
 Useful trade-off
between reliability and
system throughput.
Improves resource
utilization further.
 Address scalability
issue, network clogging
 Lightweight Key
management protocol)
 Adapted on CoAP
 Integration with
pre-shared key mode of
DTLS
Submitted total 3 drafts – 2 on CoAP NON-NORESPONSE, 1 on CoAP-Authlite
The No-Response draft is in most promising state - Received good traction
• Now has a formal number assigned by IANA
• Promising candidate to become an RFC

15. 15
Data Layer Standardization
Need not only syntactic but also semantic
interoperability

16. 16
Syntactic Interoperability
• XML based standardization of all sensor meta
data
• JSON objects for web services
• SQL and no-SQL database schemas
• Binary time series representation of sensor
observations
But is Syntactic Interoperation enough?
No – Need Semantic Interop

17. 17
Actuators Sensors
Drivers
A new way to look at IoT – Knowledge-driven Semantic Sensor Web
Entity of Interest
(building)
Phenomenon
(catches fire)
observation
Drivers
Sensor
measurement
Deduce Fire,
activate fire
control
measures
actuation
Physical
World
Cyber
World

18. 18
Horizontal operators
(semantic integration) operates on data from heterogeneous sources to created integrated data streams.
Semantic Sensor Web - From Data to Wisdom
temperature
humidity
odor
image
high temperature
gaseous odor
light
concentrated light
high temperature
indicates fire
gaseous odor indicates
gas discharge
Fire from
Gas Leak,
evacuate
immediately,
send fire fighting team
equipped with gas leakage
data
information
knowledge
wisdom
Vertical operators
(semantic abstraction) operates on
artifacts at each level and
transcends them to the next level
F PCS(Data, KB*) → Information
F PCS(Knowledge, KB) → Wisdom
F PCS(Information, KB) → Knowledge
KB: Knowledge base
Adopted from: Physical-Cyber-Social Computing: An early 21st Century Approach, Amit Sheth et. al.

19. 19
OGC - Web Enablement of Sensor
Ref : http://www.opengeospatial.org/domain/swe

20. 20
IoT Standardization Landscape
Challenge is to stich and accommodate
so many existing standards

21. 21
Different SDOs and Industrial Organizations Working on IoT
Extract
TCS Involvement – ETSI, GISFI, TSDSI, IIC

22. 22
Relevant Standards
Networking – Sensors and Gateways
• Sensor to Gateway
• IEEE 802.11 a/b/g/n
• IEEE 802.15.4 and Zigbee
• Bluetooth 4.x
• Gateway to Cloud
• 2g / 3g / LTE Cellular
Data and Control
• Service Methods - OGC SWE
• Data Formats - XML, JSON or EXI
• Protocols - RESTful and/or Pub-sub messaging protocols - CoAP and MQTT
Interfaces
• Device Management - BBF TR-069 or IETF SNMP v3 for fixed gateways/devices
• Device Management - OMA DM 2.0 (HTTP) for mobile gateways/devices
• Device Management - OMA LWM2M(CoAP) for constrained gateways/devices
Industry-specific Interfaces
• Interfaces to IT infrastructure - IETF SNMP v3
• Interfaces to physical security subsystems - ONVIF or PSIA
• Interfaces to environment subsystems - OPC UA (IEC 62541)

23. 23
IoT Reference Architecture - ETSI
Ref : ETSI TS 102 690 v1.1.1

24. 24
IoT Reference Architecture – OMA for M2M
Ref: http://community.arm.com/docs/DOC-8693

25. 25
OGC - Web Enablement of Sensor
http://www.mdpi.com/1424-8220/14/6/10725/htm

26. 26
Are there more things to Standardize?
What about Privacy?

27. 27
The Holy Grail of Privacy
Data that is both contextually useful as well as forever privacy preserving
• Privacy agreements are ok for legalities sake – but does the average user
understand it?
https://www.privacyrights.org/fs/fs2b-cellprivacy.htm
• Main issue – Is the data I am giving out is worth the Utility I am getting?
PrivacyUtility

28. 28
 Could indicate your pattern of living and what you are doing in your own home
 Bad guy knows when you're not at home and burgles your house, or worse, he
knows when only one old woman is at home and breaks in
Source:
www.winlab.rutgers.edu/~gruteser/papers/fp02
3-roufPS.pdf
Privacy Issues with IoT applications - examples
Even Sleeping Smartphones Could Soon Hear Spoken Commands
Nuance is working with chipmakers on technology that would enable
“persistent listening” apps.
http://www.technologyreview.com/news/429316/even-sleeping-smartphones-could-soon-hear-spoken-commands/
MIT Technology Review, Sept. 2012
Smartphone Malware Designed to Steal Your Life
The US Naval Surface Warfare Center has created an Android app that secretly records your
environment and reconstructs it as a 3D virtual model for a malicious user to browse
http://www.technologyreview.com/view/429394/placeraider-the-military-smartphone-malware-designed-to-steal-your-life/
MIT Technology Review, Sept. 2012

29. 29
Implications
Behavioral privacy is under unprecedented threat
Original picture from: http://thedailydose.com, Aug 16, 2011
WITH IOT
Privacy: a major hurdle for the realization of IoT potential
Does Privacy also needs to be Standardized?
Will it be Global or National or Regional or Individual?

30. 30
References
1. Philip B. Gibbons, et.al, IrisNet: An Architecture for a Worldwide Sensor Web, October 2003 IEEE
Pervasive Computing , Volume 2 Issue 4
2. Open Geospatial Consortium, OGC Sensor Web Enablement Architecture,, December 2008
3. Charles Severance, Using Google App Engine, O Reilly | Google Press, May 2009
4. W3C Incubator Group, Semantic Sensor Network XG Final Report, Report 28, June 2011
5. Dennis Pfisterer et.al, SPITFIRE: Towards a Semantic Web of Things, November 2011, IEEE
Communication Magazine
6. S Bandyopadhyay, P Balamuralidhar, A Pal, Interoperation among IoT Standards, Journal of ICT
Standardization, 2013
7. P Balamuralidhara, P Misra, A Pal, Software Platforms for Internet of Things and M2M, Journal of the
Indian Institute of Science, 2013
8. CoAP implementation from Californium - http://people.inf.ethz.ch/mkovatsc/californium.php
9. S. Bandyopadhyay, A. Bhattacharyya, and A. Pal, Adapting protocol characteristics of CoAP using
sensed indication for vehicular analytics SenSys, 2013
10. A. Ukil, S. Bandyopadhyay, A. Bhattacharyya, A. Pal and T. Pal, Auth-Lite: Lightweight
M2MAuthentication reinforcing DTLS for CoAP, IEEE Percom, 2014.
11. No-Response Draft to IETF: http://tools.ietf.org/html/draft-tcs-coap-no-response-option-06
12. Secure-session Draft to IETF: http://tools.ietf.org/html/draft-bhattacharyya-core-coap-lite-auth-00
13. Arpan Pal, Arijit Mukherjee, Balamuralidhar P, Model-driven Development for Internet of Things:
Towards easing the concerns of Application Developers, IoTaaS, IoT 360, 2014

31. 31
Thank You
arpan.pal@tcs.com