1 / 21

A Pervasive Reminder System for Smart Homes

A Pervasive Reminder System for Smart Homes. Sylvain GIROUX and Simon GUERTIN Département d’informatique, Université de Sherbrooke 2500 boul. Université, Sherbrooke, Canada J1K 2R1 {Sylvain.Giroux, Simon.Guertin,}@USherbrooke.ca http://www.dmi.usherb.ca/~sgiroux/domus/. Plan. Context

zeheb
Download Presentation

A Pervasive Reminder System for Smart Homes

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. A Pervasive Reminder Systemfor Smart Homes Sylvain GIROUX and Simon GUERTIN Département d’informatique, Université de Sherbrooke 2500 boul. Université, Sherbrooke, Canada J1K 2R1 {Sylvain.Giroux, Simon.Guertin,}@USherbrooke.ca http://www.dmi.usherb.ca/~sgiroux/domus/

  2. Plan • Context • Issues and Goals • Architecture • Scenario 1: • Localization and identification of the user • Towards personalization of the home according to the user • Scenario 2: • Pervasiveness • Moving applications seamlessly across devices • Scenario 3: • Sending information specific to the user that is in the room • Preserving the integrity of the distributed system • Conclusion • Future works

  3. Context The DOMUS laboratory investigates pervasive and mobile computing • In a smart home environment, • Technology must be: • Seamlessly incorporated, distributed and available in the environment • Inter operate with other technological system (hardware, networks, software) • Personalized according to the user

  4. Goals of the prototype • Identification of a user • Localization of a user • Transitory coalition of devices • Pervasiveness: • Integration in a real living environment • Fluid usage • Transparent user friendly migration of sessions • Zero-configuration • Spontaneous networking and service discovery • To cope with heterogeneity of devices and hardware, networks • Keeping the system in a clean state

  5. Hardware Architecture

  6. Software Architecture • Operating systems • Windows • Linux • Software • Java { J2ME, RMI, JINI} • Networks • Bluetooth • X10 • WiFi • LAN

  7. Architecture • Jini Federation are used to structure services and communication • Rooms • for instance, to support location-awareness • living room, kitchen, etc. • Logically related services and devices • Identification services ( user log, sécurity, etc.) • Lighting control system • Heating, Ventilation and Air Conditioning systems (HVAC) • Example • A lamp using X10 could be part of the federations “Kitchen”, “X10 Devices” and “Electrical Devices” • Federations are used to: • locate and use other services • search for and select relevant services • discard or use a service

  8. General Description • Pervasive messaging system • First steps towards a more sophisticated pervasive cognitive assistance system

  9. Initial configuration • Basic Jini setup • HTTP Server for file distribution • Reggie • lookup service to allow registration to service discovery • Domus Server • Provide basic Domus architecture info and services • Provides a shared HTTP server to distribute source files • Security Server • Provide a database of user names and passwords

  10. Scenario 1 • Goals • Enable user detection and localization • Integration of heterogeneous networks • X10 and LAN • When someone enters the room, • Motion detectors gets triggered • The login screen is displayed (pervasive)

  11. Scenario 1: Motion detector User goes through the door in a normal motion X10 X10 Motion detectors gets triggered X10 messages are received by the X10 Server X10 Server

  12. Domus Room A Agenda Server The agenda client prepares the login screen Domus Server Agenda Client Someone is in the room Motion Detector The user enters his password Authentication of the user Security Server The session begins Sensor A X10 Server Sensor B Motion Detector establish that someone has entered the room X10 Server transform codes from electrical to computer format And notify the interested applications X10 server feeds new X10 codes to motion detector application

  13. Scenario 2: Pervasiveness • Goals • Seamlessly changing device • Use a device with more appropriate capabilities • display • wireless • Location • Continue working in the application • The session is restored where it was left off • Case A - User switches directly to another device • Case B – User transfers his session to the server for later use

  14. Scenario 2 A Domus Room A Agenda Server Domus Server Agenda Client Security Server Kitchen Agenda Client The user choose the appropriate device The session is restored The session is transferred Session The user logs on The server authenticates

  15. Scenario 2B Same as scenario 2A Domus Federation But session moves through the server Room A Federation Agenda Server Domus Server Agenda Client Security Server Agenda Client Session

  16. Scenario 3 • Goals • Spontaneous networking and service discovery • Keeping the distributed system in a “clean” state • No messages are delivered twice • Towards transitory coalition of devices • The agenda tries to notify a user of an upcoming appointment

  17. Scenario 3: Feedback Domus An appointment is soon Room A Server needs to notify the user Agenda Server And Send message to feedback server Agenda Client Appointment A Locate and send message to clients Domus Server The appointment has been acknowledged by the user Message Client The user is authenticated Feedback Server Security Server Confirmation sent back to the feedback server Kitchen Agenda Client A Message Client Remaining messages are removed Confirmation is sent back to agenda server

  18. Decentralized No main computer No need for a super fast or powerful computer Robust Some services still remain available in case of partial crash or failure Spontaneous networking Integration of heterogeneous networks Service discovery Flexible Properties of the distributed architecture

  19. Conclusion • This system has been used to: • Integrate sensing and information devices • Deliver information to the user • Dynamic cooperation of • heterogeneous devices • heterogeneous networks (WiFi Bluetooth LAN X10) • Pervasiveness • Localization of the user • Session migration • Keeping the distributed system in a clean state • Low cost of hardware and software development

  20. Future Works • Physical Identification of a user • Automatic login • Smart tags • Networks • Integrating Bluetooth • Choosing the right network protocol to deliver a message (Luc Bergevin) • Enhancing security (software and Java) • Improving and adding features to the messaging system

  21. Scenario 2B Domus Federation Room A Federation Agenda Server Domus Server Agenda Client Security Server Agenda Client A client becomes available No clients are available to switch to Session The session is restored The user logs in The session is sent to the server The server authenticates

More Related