1. Mobile and Pervasive Computing - 5 Case Study – Oxygen Project
Hari Balakrishnan
Mobile and Pervasive Computing - 5 Case Study – Oxygen Project
Presented by: Dr. Adeel Akram
University of Engineering and Technology, Taxila,Pakistan

2. Vision & Goals Pervasive, human-centered computing
Computation embedded into human life, like the Oxygen we breathe
Improve human productivity and comfort
Move computation into the mainstream of our lives
Improve ease-of-use and accessibility
Develop a deep understanding of how to develop, deploy, and manage systems of systems in dynamic settings
Situated computing: An actual research area that gathers the knowledge and investigation in mobile, wearable, ubiquitous and augmented computing. The aim is to sustain systems that collect information about contexts and user actions over a period of time and supply it to applications that dynamically adapt to context changes. 2

3. The Oxygen Environment
Camera array
“Situated”
computing
Speech &
vision
Projector
Phone
Microphone array
Situated computing is a new paradigm for mobile computer users based on their physical context and activities carried out as a part of their working business.
- Natural, peceptual interfaces (speech, vision)
- Handheld, mobile computers (e.g. Handy21)
- Situated computing resources & sensors (e.g, Enviro21)
- Numerous other networked devices (e.g. Network21)
. . .
- And tons of software making all this work together! 3

4. What Oxygen is… and isn’t
A system of systems
Several diverse component systems designed by different minds
A computing environment
A philosophy for developing and deploying future computing environments
It is not:
Designed by committee
Solution for all computing problems 4

5. This talk
Cross-cutting systems design and implementation issues for Oxygen
Design considerations and goals
Six considerations to keep in mind
Annotated using specific examples
Context-aware networking walk-through
Distributed systems and networking
We don’t have all the answers (yet!) 5

6. Configuration and management
C1. Take the human out of the configuration and maintenance loop
Cause of much frustration today
Setting up a network, device support, software versions
Deploying distributed network services
Examples
Self-configuring networks
Self-updating software
Run-time introspection 6

7. Software adaptation
C2. Expose resource availability and constraints to software & applications
Energy: compiler techniques; application-specific, low- energy routing
Network bandwidth, latency: monitor network conditions and export via API
Gates (computation)
Configure gates using smart compilers
Application-partitioning in situated computing 7

8. Mobility and nomadicity
C3. Design software for mobility and nomadicity
Services will join, move, fail, recover, disappear: dynamic resource discovery
Data will move: access to files from anywhere
Users will move across multiple networks: vertical mobility based on performance
Software will move: updates/upgrades
Running programs will move: on-the-fly application- partitioning 8

9. Context-awareness
C4. Develop infrastructure to expose environmental context to applications
Understand user and application intent
Location-awareness
Information management for individuals and communities: context-sensitive query handling
Speech interfaces across domains
Semantic web of information in documents and service descriptions (“synonyms”) 9

10. Security and privacy
C5. Address user privacy and security from the beginning
Context-awareness raises many privacy concerns
Location-tracking is problematic; a private location- support system is better
Security concerns
File system access
Resource discovery system
Anonymous, personalizable devices 10

11. User-empowerment C6. Empower users to “program” Oxygen
Allow users to compose functionality and express requirements
Gentle-slope language
Scale from novices to over-eager high-school kids and undergraduates
Robustness via introspective operation 11

12. Device Technologies E21 Intelligent Spaces
Space centered computation, embedded in ordinary environment
Populated by cameras, microphones, displays, sound output
Controls for physical entities like curtains, lighting, door- locks
People interact in Intelligent Spaces naturally, using speech, gestures

13. Device Technologies H21 Mobile Devices
Person centered devices also the Universal Personal Appliances
Equipped with perpetual transducers such as microphone, speakers
Auto reconfigurable, light weight, inexpensive
Anonymous generic devices

14. Device Technologies N21 Network Devices
Networks make it easy to establish ad-hoc collaborating communities of computer devices

15. E21- Intelligent Spaces
Connected to sensors, suitably encapsulated into physical objects
Communicate with each other and nearby handheld devices (H21) through Dynamically Configured Networks (N21)
E21 provide computational power throughout the system to
Communicate with people
Support Oxygen User Technologies
Monitor and control their environment
E21 software is robust, and configurable among themselves

16. H21 – Mobile Devices
Generic devices also called Universal Personal Appliances
Do not carry large amount of permanent local state
They configure themselves according to the person using them
Being small and lightweight, they have few transducers
They have less computational power than E21
Can be configured to be used as radio, cellphone or even TV
Power efficient, the software controls the power consumption

17. Intelligent Rooms sensors Capable of Detection motion
Recognize voice patterns
Identify a person by face
sensors 18

18. H21 - Prototype

19. N21 – Network Technologies
Networks make it easy to establish ad-hoc collaborating communities of
computer devices
Through algorithms, protocols and middleware, they
Configure collaborative regions automatically
Create topologies and adapt them to change
Provide automatic resource and location discovery
Provide secure, authenticated and private access
N21 networks use intentional names rather than conventional static names
They support location discovery through proximity

20. Software Technologies
Software systems adapt - to user, to environment, to change, to failure
Project Oxygen's software architecture provides mechanisms for
Building applications using distributed components
Customizing, adapting and altering component behavior
Person-centric rather than device-centric security
Disconnected operation and nomadic code
Eternal Computation: The system must never shut down or reboot though components are upgraded, removed and reinstalled

21. Perceptual Techniques
Two types of Perceptual Techniques are used
Spoken Interaction
Users and Machines engage in interactive conversations
Highly efficient
Visual Interaction
Users interact with perceptual modalities
Use of body language and gestures

22. Spoken Interaction

23. Visual Interaction It consists of Visual perception Subsystem
It recognizes and classify objects and actions
Complements spoken language subsystem
Visual rendering Subsystem
Creates 3D scenes from 2D data
Provide macroscopic view of application supplied data

24. User Technologies Knowledge Access Automation Collaboration
Access any time, anywhere, almost anything
Automation
Automate control of physical environment
Collaboration
Connecting people

25. Oxygen in action: Context-aware networking
“Spontaneous” networking
Context-aware speech-driven active maps (location-specific)
Resource discovery and secure information access 26

26. Self-configuring networks
Software physical layer allows flexible (de)modulation, parameter adaptation
Self-updating software to overcome compatibility problems
Topology creation using decentralized protocols in ad hoc networks
Network monitoring across multiple networks for better routing decisions 27

27. Location-awareness
Goal: System that provides information about physical location; must work indoors too
Several goals must be met
User privacy
Decentralized administration
Cost-effectiveness
Portion-of-a-room granularity
Network heterogeneity
GPS-oriented solutions do not provide required accuracy, reliability, or cost-effectiveness 28

28. Traditional approach Location DB ID = u? Networked sensor grid ID = u
Responder
Problems: privacy; administration; granularity; cost 29

29. Cricket space = “a2” Beacon space = “a1” Pick nearest to infer space
Listener
No central beacon control or location database
Passive listeners + active beacons preserves privacy
Straightforward deployment and programmability 30

30. Problems Location granularity Interference Energy consumption
Lack of explicit beacon coordination
Energy consumption
Listener inference algorithms 31

31. Resource discovery Services advertise/register resources
Consumers make queries for services
System matches services and consumers
This is really a naming problem
Name services and treat queries are resolution requests
Problem: most of today’s naming system name by (network) locations
Names should refer to what, not where 32

32. Intentional Naming System (INS)
Names are intentional; apps know what, not where
Expressiveness
Late binding of name to location to handle failover, mobility
Responsiveness
Decentralized, cooperating resolvers
Robustness
Name resolvers self-configure into overlay network
Easy configuration
Aggressive partitioning of namespace and delegation
Scalability 33

33. form an overlay network
INS architecture
camera510.lcs.mit.edu
[service = camera]
[building = NE43
[room = 510]]
Intentional name
Lookup
image
Resolver
self-configuration
Intentional name resolvers
form an overlay network
Late binding: integrate resolution and message routing 34

34. Oxygen is a system of systems
Pervasive, human-centered, dynamic environment
Perceptual, intentional interfaces using speech, vision, and writing
Programmable and composable architecture
General approaches to handling a variety of contexts (e.g., location, information, speech)
Networking software and services
Novel hardware (and associated software)
RAW-based configurable, energy-efficient handhelds
Situated computing architectures 39

35. Summary: How might we cope?
C1. Eliminate human involvement in configuration
C2. Expose resources to software
C3. Design for mobility and nomadicity
C4. Expose and exploit environmental context
C5. Pay close attention to privacy and security
C6. Enable user programmability 40

36. Questions???

37. References
for Oxygen vision, technologies, and research agenda

38. Assignment # 4
Write Note on Project Oxygen, Cricket, N21, H21 and E21