Project AURA

1
Project AURA

• ? ? ?
• 2005. 10. 31
• ????? ???

2
CONTENTS
?
Project AURA
?
AURA Architecture
?
Simple Scenario
?
Conclusion
3
PROJECT AURA

• Distraction-free Ubiquitous Computing !!
• Computer Science, CMU
• David Garlan and 5 others, Professor of CMU
• The most precious resource in a computer system?
• Goal of Project AURA
• To provide each user with an invisible halo of
  computing and information regardless of location
• Will require effort at every level
• H/W, network, OS, M/W, UI and applications

• Process, memory, disk or network?

• No! Rather, User Attention

4
PROJECT AURA (cont)

• AURA Consortium
• Collection of companies that partner with CMU
• Companies fund the research and development
• Royalty-free rights to commercialize AURA tech.

5
INTRODUCTION

• Ideally, Ubiquitous Computing infra.
• Allow users to move their tasks easily from one
  environment to another
• Current approaches
• 1. To Support as possible as on a mobile machine
• 2. Via remote access
• 3. To provide standard applications installed in
  all env.
• 4. To provide standard virtual platforms that
  enable mobile code
• Limitation of current approaches
• Heterogeneous environments
• Dynamic variations of capabilities and resources
• Propose new architectural framework
• User tasks become first class entities
• User tasks are represented as coalitions of
  abstract services
• Environments are equipped to self-monitor and
  renegotiate task in run time

6
AURAs ARCHITECTURE

• Needs of mobile users
• Maximize the use of available resources
• Minimize user distraction and drains on user
  attention
• ? Manage their computing resources in each new
  env.
• Aura in a new environment
• Marshals the appropriate resources to support the
  users task
• Captures constraints of physical context

7
AURAs ARCHITECTURE (cont)

• Architecture
• Task Manager (Prism)
• Context Observer
• Environment Manager
• Suppliers

8
Task Manager (Prism)

• Embodies the concept of a personal Aura
• Minimize the user distractions
• User moves to another env.
• Migration of info. related to the task
  negotiates the task
• Env. Changes
• Monitors QoS information provided by the
  Suppliers
• Queries the Environment Manager to find an
  alternative conf.
• Task Changes
• Saving the state of interrupted task
  instantiates intended new task

9
Service Suppliers

• Provide the abstract services
• e.g. Emacs, Word, Notepad can be wrapped ? Text
  editing
• Guarantee platform-independent
• XML-based service description for their different
  capabilities

10
Context Observer / Environment Manager

• Context Observer
• Provide information about the physical context
• User location, recognition, activity, other
  people in the vicinity
• Environment Manager
• Aware of
• Which Suppliers are available to supply which
  services
• Where they can be deployed
• Registry
• Keeps track of the available capacity

11
Connection b/w components

• Four types of connectors
• Prism ? Suppliers
• Prism ? Environment Manager
• Context Observer ? Prism
• Context Observer ? Environment Manager
• Independent implementation
• Each connector type has its own implementations
• Independent from each other

12
Simple Scenario

• Migration from home to his office

13
Simple Scenario (cont)

• Context Observer lets Prism know that he is
  leaving
• Suspend the task ongoing at home
• EM de-allocates all services and stores all files
  back into a globally accessible file server
• Prism infers that he is likely to head to the
  office conveys description
• Given description, Prism at the office requests
  EM
• Context Observer recognizes Fred coming into his
  office

14
Simple Scenario (cont)

• Example of description

15
Conclusion

• Easy migration of a task from one env. To another