A Pervasive Reminder SystemA Pervasive Reminder Systemfor Smart Homesfor Smart Homes

Sylvain GIROUX and Simon GUERTINSylvain GIROUX and Simon GUERTIN

Département d’informatique,Département d’informatique,Université de SherbrookeUniversité de Sherbrooke

2500 boul. Université, Sherbrooke, Canada J1K 2R12500 boul. Université, Sherbrooke, Canada J1K 2R1{Sylvain.Giroux, Simon.Guertin,}@USherbrooke.ca{Sylvain.Giroux, Simon.Guertin,}@USherbrooke.ca

http://www.dmi.usherb.ca/~sgiroux/domus/http://www.dmi.usherb.ca/~sgiroux/domus/

PlanPlan ContextContext Issues and GoalsIssues and Goals

ArchitectureArchitecture

Scenario 1: Scenario 1: – Localization and identification of the userLocalization and identification of the user– Towards personalization of the home according to the userTowards personalization of the home according to the user

Scenario 2: Scenario 2: – PervasivenessPervasiveness– Moving applications seamlessly across devicesMoving applications seamlessly across devices

Scenario 3: Scenario 3: – Sending information specific to the user that is in the roomSending information specific to the user that is in the room– Preserving the integrity of the distributed systemPreserving the integrity of the distributed system

ConclusionConclusion Future worksFuture works

ContextContext

The DOMUS laboratory investigates pervasive and mobile computingThe DOMUS laboratory investigates pervasive and mobile computing

In a smart home environment, In a smart home environment,

– Technology must be:Technology must be:

Seamlessly incorporated, distributed and available in the environmentSeamlessly incorporated, distributed and available in the environment

Inter operate with other technological system (hardware, networks, software)Inter operate with other technological system (hardware, networks, software)

Personalized according to the user Personalized according to the user

Goals of the prototypeGoals of the prototype

Identification of a user Identification of a user Localization of a user Localization of a user Transitory coalition of devices Transitory coalition of devices Pervasiveness: Pervasiveness:

– Integration in a real living environmentIntegration in a real living environment– Fluid usage Fluid usage – Transparent user friendly migration of sessions Transparent user friendly migration of sessions – Zero-configurationZero-configuration

Spontaneous networking and service discoverySpontaneous networking and service discovery To cope with heterogeneity of devices and hardware, networksTo cope with heterogeneity of devices and hardware, networks Keeping the system in a clean state Keeping the system in a clean state

Hardware ArchitectureHardware Architecture

Software ArchitectureSoftware Architecture

Operating systemsOperating systems– WindowsWindows– LinuxLinux

SoftwareSoftware– Java { J2ME, RMI, JINI}Java { J2ME, RMI, JINI}

NetworksNetworks– BluetoothBluetooth– X10X10– WiFiWiFi– LANLAN

ArchitectureArchitecture Jini Federation are used to structure services and communicationJini Federation are used to structure services and communication

– Rooms Rooms for instance, to support location-awarenessfor instance, to support location-awareness living room, kitchen, etc.living room, kitchen, etc.

– Logically related services and devicesLogically related services and devices Identification services ( user log, sécurity, etc.)Identification services ( user log, sécurity, etc.) Lighting control systemLighting control system Heating, Ventilation and Air Conditioning systems (HVAC)Heating, Ventilation and Air Conditioning systems (HVAC)

– ExampleExample A lamp using X10 could be part of the federations “Kitchen”, “X10 Devices” and A lamp using X10 could be part of the federations “Kitchen”, “X10 Devices” and

“Electrical Devices”“Electrical Devices”

Federations are used to:Federations are used to:– locate and use other serviceslocate and use other services– search for and select relevant servicessearch for and select relevant services– discard or use a servicediscard or use a service

General DescriptionGeneral Description

Pervasive messaging systemPervasive messaging system

First steps towards a more sophisticated First steps towards a more sophisticated pervasive cognitive assistance system pervasive cognitive assistance system

Initial configuration Initial configuration

Basic Jini setupBasic Jini setup– HTTP Server for file distributionHTTP Server for file distribution– Reggie Reggie

lookup service to allow registration to service discoverylookup service to allow registration to service discovery

Domus ServerDomus Server– Provide basic Domus architecture info and servicesProvide basic Domus architecture info and services– Provides a shared HTTP server to distribute source filesProvides a shared HTTP server to distribute source files

Security ServerSecurity Server– Provide a database of user names and passwordsProvide a database of user names and passwords

Scenario 1Scenario 1

GoalsGoals– Enable user detection and localizationEnable user detection and localization– Integration of heterogeneous networks Integration of heterogeneous networks

X10 and LANX10 and LAN

When someone enters the room,When someone enters the room,– Motion detectors gets triggeredMotion detectors gets triggered– The login screen is displayed (pervasive)The login screen is displayed (pervasive)

Scenario 1: Motion detectorScenario 1: Motion detector

User goes through the door in a normal motion

Motion detectors gets triggered

X10 messages are received by the X10 Server

X10 Server

X10 X10

Domus

Room A Agenda ServerDomus

Server

Security Server

X10 Server

Agenda Client

Motion Detector

Sensor ASensor B

Someone is in the room

The agenda client prepares the login screen

The user enters his password

Authentication of the user

X10 Server transform codes from electrical to computer format

X10 server feeds new X10 codes to motion detector application

Motion Detector establish that someone has entered the room

And notify the interested applications

The session begins

Scenario 2: PervasivenessScenario 2: Pervasiveness

GoalsGoals

– Seamlessly changing device Seamlessly changing device

– Use a device with more appropriate capabilitiesUse a device with more appropriate capabilities displaydisplay wirelesswireless LocationLocation

– Continue working in the applicationContinue working in the application The session is restored where it was left offThe session is restored where it was left off

Case A - Case A - User switches directly to another deviceUser switches directly to another device Case B – Case B – User transfers his session to the server for later useUser transfers his session to the server for later use

ScenarioScenario 2 A 2 ADomus

Kitchen

Room AAgenda ServerDomus

Server

Security Server

Agenda Client

Agenda Client

Session

The user choose the appropriate device

The user logs on

The session is transferred

The server authenticates

The session is restored

Scenario 2BScenario 2B

Domus FederationRoom A

FederationAgenda ServerDomus

Server

Security Server

Agenda Client

Agenda Client

Session

Same as scenario 2A

But session moves through the server

Scenario 3Scenario 3

GoalsGoals– Spontaneous networking and service discoverySpontaneous networking and service discovery– Keeping the distributed system in a “clean” stateKeeping the distributed system in a “clean” state– No messages are delivered twiceNo messages are delivered twice– Towards transitory coalition of devicesTowards transitory coalition of devices

The agenda tries to notify a user of an The agenda tries to notify a user of an upcoming appointmentupcoming appointment

Scenario 3: FeedbackScenario 3: FeedbackDomus

Kitchen

Agenda Server

Domus Server

SecurityServer

FeedbackServer

Room A

Agenda Client

Message Client

Agenda Client

Message Client

Appointment

An appointment is soon

Server needs to notify the user

A

And Send message to feedback server

Locate and send message to clients

A

The user is authenticated

Confirmation sent back to the feedback server

Remaining messages are removed

Confirmation is sent back to agenda server

The appointment has been acknowledged by the user

Properties of the distributed architectureProperties of the distributed architecture

DecentralizedDecentralized No main computerNo main computer No need for a super fast or powerful computerNo need for a super fast or powerful computer

RobustRobust Some services still remain available in case of partial Some services still remain available in case of partial

crash or failurecrash or failure

Spontaneous networkingSpontaneous networking Integration of heterogeneous networksIntegration of heterogeneous networks Service discoveryService discovery

FlexibleFlexible

ConclusionConclusion This system has been used to:This system has been used to:

– Integrate sensing and information devicesIntegrate sensing and information devices– Deliver information to the userDeliver information to the user

Dynamic cooperation of Dynamic cooperation of – heterogeneous devicesheterogeneous devices– heterogeneous networks (WiFi Bluetooth LAN X10)heterogeneous networks (WiFi Bluetooth LAN X10)

PervasivenessPervasiveness– Localization of the userLocalization of the user– Session migrationSession migration– Keeping the distributed system in a clean stateKeeping the distributed system in a clean state

Low cost of hardware and software developmentLow cost of hardware and software development

Future WorksFuture Works

Physical Identification of a user Physical Identification of a user – Automatic loginAutomatic login– Smart tagsSmart tags

NetworksNetworks– Integrating Bluetooth Integrating Bluetooth – Choosing the right network protocol to deliver a message Choosing the right network protocol to deliver a message

(Luc Bergevin)(Luc Bergevin)

Enhancing security (software and Java)Enhancing security (software and Java)

Improving and adding features to the messaging systemImproving and adding features to the messaging system

Scenario 2BScenario 2B

Domus FederationRoom A

FederationAgenda ServerDomus

Server

Security Server

Agenda Client

Agenda Client

SessionNo clients are available to switch to

The session is sent to the server

A client becomes availableThe user logs in

The server authenticates

The session is restored