1 / 11

Requirement Specification for IoT API layer

This document outlines the comprehensive requirements for an IoT API layer to enhance sensor data collection, analytics, and actuation in deployments. It covers API, backend, and edge interface needs for seamless IoT operations.

brantley
Download Presentation

Requirement Specification for IoT API layer

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Requirement Specification for IoT API layer Company: Tata Consultancy Services Author(s): Avik Ghose Contact information: avik.ghose@tcs.com +91-33-6636-7415 Purpose: Discussion and Approval GISFI # 05, June 20 – 22, 2011, Hyderabad, India

  2. Outline • The following sections are present in this presentation: • Abstract • Introduction • Requirements GISFI # 05, June 20 – 22, 2011, Hyderabad, India

  3. 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. GISFI # 05, June 20 – 22, 2011, Hyderabad, India

  4. Introduction • The Requirements are divided into the following categories: • API Requirements • Interface requirements from back-end platform • Interface requirements from the edge platform GISFI # 05, June 20 – 22, 2011, Hyderabad, India

  5. 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 GISFI # 05, June 20 – 22, 2011, Hyderabad, India

  6. 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 GISFI # 05, June 20 – 22, 2011, Hyderabad, India

  7. 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. GISFI # 05, June 20 – 22, 2011, Hyderabad, India

  8. 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 GISFI # 05, June 20 – 22, 2011, Hyderabad, India

  9. Edge – Device access and Gateway Requirements • Device Access • Access to individual devices • Device profiling • Gateway Intelligence • Context extraction • Periodic posting of data GISFI # 05, June 20 – 22, 2011, Hyderabad, India

  10. 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 GISFI # 05, June 20 – 22, 2011, Hyderabad, India

  11. Edge – Security and Privacy Requirements • Secure temporary storage • Secure communication to backend • Secure communication to app • User authentication • Anonymous posting GISFI # 05, June 20 – 22, 2011, Hyderabad, India

More Related