Web of Domotics (WoD): Towards a web of Smart EnvironmentsFaisal Razzak {faisal.razzak@polito.it}Elite Research Group (htt...
Upcoming SlideShare
Loading in …5
×

Web of Domotics Poster

1,056 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,056
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
17
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Web of Domotics Poster

  1. 1. Web of Domotics (WoD): Towards a web of Smart EnvironmentsFaisal Razzak {faisal.razzak@polito.it}Elite Research Group (http://elite.polito.it), Politecnicodi Torino, Italy<br />What is WoD? <br />Abstract<br />Issues <br /><ul><li>WoD combines the concepts of Internet of Things and Domotics.
  2. 2. Enables mobile users to access and to control devices in a ubiquitous manner, without any a priori knowledge of device controllers from any network or location.</li></ul>Domotic Device Identification<br /><ul><li>A domotic device must be identified uniquely.
  3. 3. It should have a visual identifier (Optional). </li></ul>Domotic Device Control<br /><ul><li>A domotic device should have a controller. The controller should store characteristic information about devices and should have the ability to control devices.
  4. 4. The information should have formal semantics so that it can be interpreted. </li></ul>Access to Controller<br /><ul><li>A mobile terminal should be able to determine the correct controller controlling the domotic device, without any a priori knowledge.</li></ul>Universal Authentication<br /><ul><li>Every mobile user accessing information about a device or sending request to perform operation on a device must be authenticated.
  5. 5. Authentication should be universal and independent of any network constraints.
  6. 6. Allow mobile users to approach and operate physical devices in any smart environment empowered by a compatible environment gateway (Controller).
  7. 7. It exploits several Internet and Web standard technologies to provide following features:
  8. 8. Proximity-based device identification.
  9. 9. Network-based detection of service access points (through DNS based device</li></ul> dereferencing). <br /><ul><li>User identification through Open ID.
  10. 10. Open data exchange, service/device description through Linked Open Data formats .
  11. 11. Device operation through REST-based interaction.</li></ul>Faisal Razzak<br />faisal.razzak@polito.it<br />Reference<br /><ul><li>Mobile Interaction with Smart Environments through Linked DataF Razzak, D. Bonino, and F. CornoAccepted for publication on SMC 2010, 2010 IEEE International Conference on Systems, Man, and Cybernetics, October 10-13, 2010, Istanbul, Turkey</li></ul>WoD Solution<br />Assumptions<br />Conceptual Model<br /><ul><li>The user has a mobile phone equipped with a camera and an enabled Internet connectionand a mobile application.
  12. 12. The mobile application decodes the visual tag, provides interface to authenticate users and to control domotic devices.
  13. 13. Every device is identified uniquely through a Universal Access ID (UAID). The UAID of a domotic device is encoded using visual tags like 2D Bar Codes.
  14. 14. There exists a reference DNS domain assigned to all visual tags. For example, viztag.com.</li></ul>The mobile application contacts the Controller and sends the user’s identity credentials .<br />The Controller forwards the authentication credentials to an external authentication service. <br />The authentication service informs the Controller about the validity of the user credentials.<br />If the user is authorized, the Controller returns<br /><ul><li>the type, location and control information about the device
  15. 15. list of operations associated with the device.</li></ul>The user opens the mobile application to perform operations.<br />The mobile application takes a snap shot of the visual tag associated to the device and located nearby.<br />The mobile application decodes the visual tag to extract the UAID of the device.<br />After getting the UAID, the mobile application determines the URL of the correct Controller through a DNS query on a special domain.<br />Features<br /><ul><li> The Controller adhere to theLinked Data vision by exposing device information through RDF or RDFa.
  16. 16. The user can request pure RDF description of a device or RDFa (XHTML) as a response user interface.
  17. 17. Devices are described by reporting semantics-rich information including their name, type, functionalities, current location and by showing current state and available operations.
  18. 18. The Controller offer information about devices by exploiting theincreasingly popularLinked Open Data format.
  19. 19. The Controller is built by introducing 3 new units inside Dog to enhance its functionality.
  20. 20. Dog is an ontology-powered DomoticOSGi Gateway that is able to expose different domotic networks as a single, technology neutral, home automation system.
  21. 21. The three new units are: HTTP-Access, Authentication and Authorization Unit and UAID Mapping Unit..
  22. 22. The mobile application provides a user with an interface to interact with the devices present in the environment. It communicates with the controller responsible for the devices on behalf of the user.
  23. 23. User authentication is provided through Open ID. Open ID is a decentralized standard based on Single Sign-On (SSO) paradigm to authenticate the users.
  24. 24. UAID is encoded through QR Code because the decoding process is quick and many modern mobile phones are by default equipped with software to decode QR Code
  25. 25. During setup phase, MAP (Mobile Access Provider) registers the UAID associated with the device with the domain address of the Controller that controls the device. </li>

×