1 requirement specification for iot api layer company:tata consultancy services author(s):avik ghose...
DESCRIPTION
Abstract IoT deployments involve sensor data collection, analytics and optional actuation. Unified API for access to IoT deployments is missing. Much like CE, Apps can revolutionize IoT deployments. We recommend a web API based approach. Requirements for API, backend and edge interfaces. 3 GISFI # 05, June 20 – 22, 2011, Hyderabad, India IOT5_TRANSCRIPT
1
Requirement Specification for IoT API layer
Company: Tata Consultancy ServicesAuthor(s): Avik GhoseContact information: [email protected] +91-33-6636-7415Purpose: Discussion and Approval
GISFI # 05, June 20 – 22, 2011, Hyderabad, India
IOT5_20110012
2
Outline
• The following sections are present in this presentation:1. Abstract2. Introduction3. Requirements
GISFI # 05, June 20 – 22, 2011, Hyderabad, India
IOT5_20110012
Abstract• IoT deployments involve sensor data collection, analytics and
optional actuation.• Unified API for access to IoT deployments is missing.• Much like CE, Apps can revolutionize IoT deployments.• We recommend a web API based approach.• Requirements for API, backend and edge interfaces.
3GISFI # 05, June 20 – 22, 2011, Hyderabad, India
IOT5_20110012
Introduction
• The Requirements are divided into the following categories:– API Requirements– Interface requirements from back-end platform– Interface requirements from the edge platform
4GISFI # 05, June 20 – 22, 2011, Hyderabad, India
IOT5_20110012
API – Access Requirements
• Backend Access• Access for historic sensor readings• Access for data and context analytics• Access for edge discovery
• Edge Access• Access for extracted context• Access for device discovery
• Device Access• Access for real-time sensing• Access for actuation
5GISFI # 05, June 20 – 22, 2011, Hyderabad, India
IOT5_20110012
API – I/O Requirements• Web Service Based I/O – XML format• Base64 encoding for binary data like
images within XML• RESTful access to devices• RSS like feed support• HTTP Live Streaming• Complex I/O like Events, Subscriptions
and Complex query formulation
6GISFI # 05, June 20 – 22, 2011, Hyderabad, India
IOT5_20110012
API – Collaborative, Security and Privacy Requirements• Collaboration
– SIP/H.323 based IP calls– 3G/4G based voice/video calls
• Security– Secure connected to back-end.– User Authentication.
• Privacy– Anonymous data to app.
7GISFI # 05, June 20 – 22, 2011, Hyderabad, India
IOT5_20110012
Backend Requirements• Addressability of edge.• Analytics on sensor data.• Direct access to sensor data.• Storage/Retrieval of historic sensor data.• Secure storage of sensor data• Secure connectivity• User Authentication• Anonymous analytics
8GISFI # 05, June 20 – 22, 2011, Hyderabad, India
IOT5_20110012
Edge – Device access and Gateway Requirements• Device Access
– Access to individual devices– Device profiling
• Gateway Intelligence– Context extraction– Periodic posting of data
9GISFI # 05, June 20 – 22, 2011, Hyderabad, India
IOT5_20110012
Edge – Aggregation and Asynchronous I/O Requirements• Aggregation and Compression
– Aggregation of sensor data– Compression of aggregated data before
uploading• Asynchronous access
– On demand access from applications– On demand access by the back-end
10GISFI # 05, June 20 – 22, 2011, Hyderabad, India
IOT5_20110012
Edge – Security and Privacy Requirements• Secure temporary storage• Secure communication to backend• Secure communication to app• User authentication• Anonymous posting
11GISFI # 05, June 20 – 22, 2011, Hyderabad, India
IOT5_20110012