mobicom1

Slide1: 

Pervasive Computing: What is it good for? Andrew C. Huang et all Stanford University Presented by Kalpana Banerjee

“Buy drinks by Friday”: 

“Buy drinks by Friday”

“Buy drinks by Friday”: 

“Buy drinks by Friday”

“Buy drinks by Friday”: 

“Buy drinks by Friday”

Screen Fridge: 

Screen Fridge Screen Fridge provides: Email, video messages, web surfing, food management, TV, radio, virtual key board, digital cook book, surveillance camera

Auto PC: 

Auto PC Provides driver with navigation and traffic information (GPS) Voice interface Audio system, voice memo recorder,

What do we do with all this information?: 

What do we do with all this information? We are constantly receiving information The problem: Information is only received once or twice It is not received when and where we need it A possible solution: Place information into the context in which it will be most useful Devices accept and/or deliver information

Rome manages the information: 

Rome manages the information The devices are available What is missing is the software framework Rome is an architecture that addresses the information management problem Incorporates pervasive computing devices into the system as information managers Introduces an abstraction to describe context-sensitive information

Incorporating devices into the network: 

Incorporating devices into the network Enables communication among devices Gives devices access to Internet services Unwieldy datasets (e.g., UPC database) Rapidly-changing data (e.g., traffic reports) Computationally intensive (e.g., mapping) Must deal with device heterogeneity Limitations: connectivity, computation, UI, etc. Devices have a permanent representative

Describing context-sensitive information: 

Describing context-sensitive information A trigger is a piece of data bundled with contextual information Conceptually, it is an action that is taken when a certain condition is satisfied Condition: (location  R)  (t  T1)  (t  T2) Data: “You are passing a grocery store at R. You might want to buy drinks for Friday.” Note: similar to database triggers Difference: trigger management is decentralized

Rome Architecture: 

Rome Architecture Frontend: handles the entering of triggers into the system Unit Manager: acts as a permanent representative of a device Trigger Manager: accepts, stores, and forwards triggers

Rome Architecture: 

Rome Architecture Trigger Acceptor: accepts triggers from the Unit Manager Trigger Handler: evaluates trigger conditions and executes appropriate data handlers

Rome Architecture: 

Rome Architecture GPS- enbaled AutoPC Bar-code scanner

Open Questions: 

Open Questions Trigger consistency Deleting triggers once a high-level task is accomplished User interface and semantic translation Translating high-level requests into triggers Multiple users Sharing the system in the public infrastructure Adding a trigger to be seen by another user

Summary: 

Summary Information management applications are a natural target for pervasive computing Rome provides an extensible framework and some basic building blocks Communication Leveraging Internet services Triggers abstraction

My Conclusions: 

My Conclusions Information management/ triggers – simple concept, utilized well Rome infrastructure deployment is unclear – service?, personalized setup? Drawback – other applications? Problem is there is no problem