Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

WoT framework and use cases


Published on

Web of Things framework and use cases

Published in: Technology
  • Be the first to comment

WoT framework and use cases

  1. 1. Web of Things Architecture and Use Cases Soumya Kanti Datta, Christian Bonnet Mobile Communications Department Email:
  2. 2. Connecting Things in IoT 07-Apr-15 Source: Source: Roberto Minerva, “From M2M to Virtual Continuum”, ICCE 2015, Las Vegas 2
  3. 3. Volume of Connected Things 07-Apr-15 A Lightw eight Framew ork for Efficient M2M Device Management in oneM2M Architecture 3
  4. 4. IoT Challenges  Incompatible platforms and silos  Wide range of technologies  Missing consumer centric approach  Processing of sensor data  No uniform nomenclature for sensors, domains, measurements, units  Hard task for application developers  Learn the technologies  Making interoperable solutions  Address the fragmentation in the market  Create cross domain applications 20/04/2015 Web of Things Architecture and Use Cases - p 4
  5. 5. Web of Things - Motivation  Today we have devices that can access the web  Directly  Via a smart gateway  Web of Things (WoT) concept is becoming more popular  Leverage web standards and technologies to interconnect all types of devices.  Expose functionalities using RESTful APIs making them easier to access and use.  Provide truly open, flexible, scalable and interoperable services. 20/04/2015 Web of Things Architecture and Use Cases - p 5 Source:
  6. 6. Requirements  Uniform description of devices/things  Uniform nomenclature for devices, units, measurements and domains  Discovery  Local – from a smart gateway  Remote – remotely discovering devices in a smart city  P2P – to explore the social aspect of WoT  Management of devices  Automatic management  Provisioning, maintenance, configuration update  End user access control  Binding to HTTP, CoAP, MQTT … 20/04/2015 Web of Things Architecture and Use Cases - p 6
  7. 7. Requirements  Security, Privacy, Trust  Data Management and Repository (DMR)  Data Processing  Utilization of semantic web technologies  Results in high level abstraction and actionable intelligence  Uniform treatment of data coming from heterogeneous sources  End user service creation  Domain specific scenarios  Cross domain scenarios 20/04/2015 Web of Things Architecture and Use Cases - p 7
  8. 8. WoT Architecture 20/04/2015 Web of Things Architecture and Use Cases - p 8
  9. 9. Proxy-in and Proxy-out  Enables creation of virtual instances of physical devices.  Proxy-in manages sensors and Proxy-out is for actuators.  Each proxy can be accessed using URIs and facilitates discovery of the associated devices.  Distinct advantage  Proxies can support both smart and legacy devices  Essentially hides the intelligence of the devices from higher level applications  Allows seamless integration of legacy devices into WoT platforms 20/04/2015 Web of Things Architecture and Use Cases - p 9 Source: Datta, S.K.; Bonnet, C.; Nikaein, N., "An IoT gateway centric architecture to provide novel M2M services," Internet of Things (WF-IoT), 2014 IEEE World Forum on , vol., no., pp.514,519, 6-8 March 2014.
  10. 10. Description of Devices  Current Solutions  Describing devices using CoRE Link Specifications [1]  Software implementation in JSON  Proposed uniform nomenclature [2]  Ultra lightweight description (each description file size < 1KB)  Work on progress  Integrate JSON-LD for things description 20/04/2015 Web of Things Architecture and Use Cases - p 10 [1] Datta, S.K.; Bonnet, C., "Smart M2M Gateway Based Architecture for M2M Device and Endpoint Management," Internet of Things(iThings), 2014 IEEE International Conference on, IEEE , vol., no., pp.61,68, 1-3 Sept. 2014 [2] Gyrard, A.; Bonnet, C., “A unified language to describe M2M/IoT Data”, OneM2M 2015, MAS Working Group 5, 22-27 March 2015, Sophia Antipolis, France.
  11. 11. Device Management  Based on OMA Lightweight M2M Technical Specifications [3]  Defines a framework for connected device management using a lightweight M2M server.  Can be integrated into a WoT server, cloud system, smart gateway [4].  Enables [4]  Automatic registration, un-registration, provisioning of devices.  Configuration update from end users. 20/04/2015 Web of Things Architecture and Use Cases - p 11 [3] v1-0 [4] Datta, S.K.; Bonnet, C., "A lightweight framework for efficient M2M device management in oneM2M architecture," First International Conference on Recent Advances in Internet of Things (RIoT 2015), 7-9 April 2015.
  12. 12. Data Processing  Goals  How to get meaning out of raw data  Understand the context  Derive actionable intelligence  Solution: reasoning with semantic web technologies  First step – add side information to sensor measurement using SenML (results into metadata)  Second step – decorate the “metadata” with additional semantic reasoning (results into high level abstraction)  Third step – Further processing to derive actionable intelligence 20/04/2015 Web of Things Architecture and Use Cases - p 12
  13. 13. M3 Approach  The M3 (Machine to Machine Measurement) approach  Enrich M2M data with semantic web technologies [5]  The M3 ontology: A hub for cross-domain ontologies and datasets – e-Health: weather, recipe, health – Smart city: weather, home automation, transport, vacation – STAC (security): sensor, cellular, web, mobile phone  LOR (Linked Open Rules): share and reuse domain rules  M3 integrated in a semantic-based (Machine-to- Machine) M2M architecture  Prototype: - p 13 [5] Gyrard, A.; Bonnet, C.; Boudaoud, K., "Enrich machine-to-machine data with semantic web technologies for cross-domain applications," Internet of Things (WF-IoT), 2014 IEEE World Forum on, pp.559,564, 6-8 March 2014
  14. 14. End User Service Creation  Accomplished through a mobile application  Connect and Control Things  Trigger an action if a pre-defined event occurs  Switch on light switch (actuation) when someone enter a room (presence detector sensor)  Interacts with WoT server over RESTful interfaces  We intend to provide open source APIs to add and improve offered functionalities 20/04/2015 Web of Things Architecture and Use Cases - p 14
  15. 15. Work on progress  Discovery  Remote and P2P  Local discovery is supported by the smart gateway itself.  Data Management and Repository  Access control and end-to-end security 20/04/2015 Web of Things Architecture and Use Cases - p 15
  16. 16. Use Case – Smart Home  Smart gateway is at the heart  WoT server is deployed inside it  Physical devices are connected to the gateway and are accessed from a mobile app.  Implements access control for visiting friends/relatives  Advantage  Local processing of data  Privacy 20/04/2015 Web of Things Architecture and Use Cases - p 16
  17. 17. Use Case – Cross Domain  Combine Smart Home, eHealth, Weather  Get information about weather, body temperature of a person and suggest food accordingly  Example: – Weather – hot – Body Temp – normal – Smart Home contains ingredients for iced tea – Suggest – Iced Tea  Another example – Smart vehicle detects outside is foggy from weather domain sensor and the OBU suggest to switch on fog lamp. – It combines knowledge from weather and transportation domains. 20/04/2015 Web of Things Architecture and Use Cases - p 17
  18. 18. Conclusion  Motivation and requirements of WoT  Overview on a WoT architecture  Its components  Use cases  Expressing interest to lead WoT Framework task force  And contribute to rest of the TFs. 20/04/2015 Web of Things Architecture and Use Cases - p 18
  19. 19. Thank you! - p 19  Email:  Webpage: soumya-kanti/publications  Twitter: @skdatta2010