INTERNET OF THINGS – A PERSPECTIVE

Download ✓Supporting a set of protocols for exchanging the data and control commands. ✓ Supporting a set of configuration attributes. ✓Supporting dat...

0 downloads 673 Views 778KB Size
Internet of Things – A perspective Soma Bandyopadhyay Innovation Lab TATA Consultancy Services

Copyright © 2011 Tata Consultancy Services Limited

0

Agenda

Agenda Introduction Functional Components IoT System Architecture Interfaces IoT Use cases GISFI IoT WG Plan & Status - Summary Contribution of various standard bodies on IoT Architecture Standardization Components Way Forward & Conclusion 1

Introduction Internet of Things Demands a complex distributed architecture communicating over Internet Uses numerous diverse components Includes the diverse end devices (sensors) and applications and made association with their context. [1]

Functional Properties Interoperation among diverse sensor.  Context detection & Analysis.  Device discovery and management.  Security and privacy.  Managing data volume. Providing unique application plug-in interface [1] http://www.scribd.com/doc/64235401/Role-Of-Middleware-For-Internet-Of-Things-A-Study

2

Functional Components

Sensor domain Mainly consists with diverse sensors serving diverse functions and access mechanism communicating over diverse communication protocols like WiFi, Zigbee, Bluetooth, etc. Has own sensor aggregator. Addressable Access gateway with middleware Provides access to sensor domain to the Internet. Has middleware supporting device interoperation , device context detection etc. Supports device discovery and registration , device capability negotiation, device management . Defines unique interfaces Application middleware/controller Provides access to applications to the access gateway over the Internet. Provides unique application plug-in interface Defines unique interfaces Service /Application domain 3

Interfaces

Common properties of the interfaces Handling of sensor data stream Handling of Event reporting Handling of Alerts/Notifications Handling of management messages Handling of control messages Supporting a set of protocols for exchanging the data and control commands Supporting a set of configuration attributes Supporting data and control types  Data type of interface – supports only the data exchange across the different components of IoT architecture. Control type of interface – supports the exchange of control messages which includes registration, configuration, management and interacting with security provisioning servers. Supporting communication among sensor access gateways. Supporting communication among application controller/ gateways. 4

IoT Use Cases

Some important use cases defined in GISFI IOT WG mHealth Non-availability of adequate or any health services in large part of the country One room hospital Provision basic diagnosis One per village 1 healthcare person (doctor or 1 nurse) who performs checkup Need to reduce the number of healthcare people because number of hospital will be more Number of healthcare people are already very few Each one room hospital is connected to central or district hospital. Central hospital with: Continuous observation facilities has all facilities Body area network – A solution approach

Farming Crop Modeling, Planning Water Conservation Measures Pest and Disease Prediction/Prevention Water Management for Deficit Irrigation Insurance & Finance Provisioning

5

Use Cases Contd. Food supply chain management To provide price support to producers. To distribute food grains through the public distribution system (PDS) at reasonable and uniform prices especially to the weaker sections of the society. To have better price controls on the food items sold in private markets. To ensure food security through better management of food stocks for PDS and disasters like drought. To facilitate better cultivation by addressing problems in cultivation, to ensure supply vs. demand is met.

User is in Outdoor with Smartphone

User may be inside a moving vehicle or a pedestrian/cyclist. Use cases such as: (a) Share a ride, (b) Road condition monitoring, (c) Traffic congestion detection, (d) Driving pattern analysis (e) Un-manned railway crossing, etc., are under consideration.

User is Indoor

 Health monitoring, (b) Indoor positioning via ultrasound based detection, (c) Smart metering and control, etc., are under consideration.

6

IoT WG Plan in GISFI - Summary IoT WG Contributors: NEC, ERRICSON, TCS Sl. No.

Milestones

Deliverables

Schedule (Months)

1

Use Case presentation

Study report

Done

2

IoT definition and architecture for identifying interfaces as standardization candidates

Study report (including Gap Analysis)

Done – under review

4

Interface requirements for individual use cases

Requirements document to be presented

Done – need more detailing

1

TCS will IoT System Architecture

propose enhancementModified in IoTproposal Architecture will be & presented Interface in coming GISFI meeting

GISFI #8

9

Proposals for IoT interface specifications (based on requirements)

Specification document to be presented

GISFI #8

10

Final document for interface specification – draft for approval

Specification document to be presented

6 months GISFI # 9

11

Final consolidated specification document ready for submission

Final specification document to be presented

9 months GISFI # 10 7

IoT System Architecture in GISFI

Architecture is still under discussion

8

Standard bodies on IoT Architecture

GISFI-TIA Interfaces

9

Standard bodies on IoT Architecture Contd. GISFI-ETSI Interfaces

10 10

10

IoT System Architecture - A refined view from TCS Proposing in Coming GISFI meeting

Interfaces : I1- The sensors to access gateway

I1a – Data I1b – Control

I2 - Access gateway to Application middleware/ controller

I2a - Data I2b - Control I2C - Among access gateways

I3 I3a – Data I3b –Control I3C - Among application middleware 11

Standardization Candidates

Deriving the optimized protocols set for I2 both for data and control. Optimized bandwidth usage Optimized energy usage Standardize the Interface for communicating with the diverse applications from the application controller – I3

12

Way Forward & Conclusion

Working on the standardization aspects of IoT system Validating the proposed system across the requirements of diverse domains of use-cases /applications India has requirements in M2M/IoT space which are valid for other countries. Synchronizing with various standard bodies across the globe. GISFI immensely interested in working on IOT

with TTC and ARIB. First step would be to identify common grounds. 13

Thank You