1 / 14

Challenges : An Application Model for Pervasive Computing

Guruduth Banavar, James Beck, Eugene Gluzberg, Jonathan Munson, Jeremy Sussman, DeborraZukowski. Proc. 6th ACM MOBICOM , Boston, Mass., August 2000. Presenter : Youn Do, Lee (ydlee@mmlab.snu.ac.kr). Challenges : An Application Model for Pervasive Computing. Why this presentation?.

etenia
Télécharger la présentation

Challenges : An Application Model for Pervasive Computing

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. Guruduth Banavar, James Beck, Eugene Gluzberg, Jonathan Munson, Jeremy Sussman, DeborraZukowski. Proc. 6th ACM MOBICOM , Boston, Mass., August 2000. Presenter : Youn Do, Lee (ydlee@mmlab.snu.ac.kr) Challenges : An Application Model for Pervasive Computing

  2. Why this presentation? To recognizechallenges for Pervasive Computing especially from the perspective of application. Pervasive Computing!

  3. Outline • Pervasive Computing • Today’s problem • New Vision • New Application Model • A Glimpse of tomorrow • Related Work • Conclude

  4. Pervasive Computing • Anytime – Anywhere – Anydevice – Anydata- Anyservice • Smart or Active Space • Context Awareness

  5. Today’s Problem • The program has to be different on the different devices. • The program doesn’t live in the environment. • Some of devices cannot speak to one another. • The program requires the specific services.

  6. New Vision • Vision can be summarized in three precepts. A device is a repository of custom software managed by user A device is a portal into an application/data space An application is a piece of software that is written to exploit a device’s capabilities An application is a means by Which a user performs a task The computing environment is a virtual space that exists to store and run software The computing environment is the user’s information-enha nced physical surroundings.

  7. New Application Model(1) The life cycle of an application The developer creates, maintains and enhances the application Design Time The system loads the application components into an application instance on particular devices Load Time The end-user invokes the applica tion and uses its functionality Run Time

  8. New Application Model(2) • Design Time • Identifying abstract interaction elements that capture user intent, not device mechanism. • Specifying an abstract service description language. • Creating a task-based model for program structure. • Specifying what causes a task to begin and end, and what tasks precede and follow it. An ideal development methodology for building an application is to focus on the user task, rather than the user's interaction with an interface on a specific device in a specific environment.

  9. New Application Model(3) • Load Time • Dynamic Discovery – Mobile device can dynamically identify and enumerate the applications and services in its local vicinity. • Requirements and capability negotiation - A device needs to negotiate with a server that hosts applications and services. • Presentation Selection – The system needs to support dynamic selection of an appropriate application interface from a set of available interfaces based on the device’s resources and form-factor. • Adaptation and Composition – The system needs to seamlessly integrate the applications and services found in the environment.

  10. New Application Model(4) • Run Time • Monitoring and Redistribution – The system needs to detect changes in the resources of any device or environment . • Handoff of task – The system must allow a user to initiate and perform a task in an uninterrupted manner, despite changes in the environment and devices. • Disconnection – If the network connection between client and server is detected to degrade, code might be migrated from the server to the client. • Failure Detection and Recovery – Many existing failure detection and recovery techniques may need to be modified. (e. g., Understanding disconnection.)

  11. A Glimpse of Tomorrow • The application is built to be run on any device. • The application is no longer thought of as a selling tool for a device. • The concept of “upgrading” software may become anachronistic. • Etc.

  12. Related Work • Existing technologies • User-Interface Management Systems (UIMS) • Client-server Computing Model • Java Computing Model • Web Technologies • Service Technologies (e. g., Bluetooth, MOCA) • On-going pervasive efforts • Portolano, University of Washington • Oxygen, MIT

  13. Conclude • PIMA, IBM T.J. Watson Research Center • Project Leader’s tomorrow • Having the same vision while lying in the different beds. • This paper challenges you, not others.

  14. Thank you, Any Question?

More Related