Presentation is loading. Please wait.

Presentation is loading. Please wait.

Abc Architectural Support for Activity- Based and Ubiquitous Computing Jonathan Bunde-Pedersen Ph.D. student Centre for Pervasive Healthcare Aarhus University.

Similar presentations


Presentation on theme: "Abc Architectural Support for Activity- Based and Ubiquitous Computing Jonathan Bunde-Pedersen Ph.D. student Centre for Pervasive Healthcare Aarhus University."— Presentation transcript:

1 abc Architectural Support for Activity- Based and Ubiquitous Computing Jonathan Bunde-Pedersen Ph.D. student Centre for Pervasive Healthcare Aarhus University

2 abc Jonathan Bunde-Pedersen Doctoral Colloquium 2 Activity-Based Computing – Objects Activities –Carrying out a task, unit of work Services –Application or service, partial runtime-state Data –File, portions of a file, simple values … participants, resources etc. http://www.dr.dk/“

3 abc Jonathan Bunde-Pedersen Doctoral Colloquium 3 Activity-Based Computing – Operations Suspend –Gathering runtime state –“Exiting” all services Resume –Fetching runtime state –Starting each service –Re-establishing state Share –Duplicating state (via server) –Events –Collaboration widgets

4 abc Jonathan Bunde-Pedersen Doctoral Colloquium 4 Related projects Project Aura –Garlan et. al., CMU Gaia OS –Román et. al., Univ. of Illinois at Urbana-Champaign Microsoft Groupbar –Microsoft Research one.world –Grimm et. al., NYU iRoom –Johanson et. al., Stanford Univ. MobileSpaces –Satoh, National Institute of Informatics, Tokyo

5 abc Jonathan Bunde-Pedersen Doctoral Colloquium 5 Current State – Generally Migration of applications, data Applications and devices –Many-to-one (window systems, threads) –One-to-many (teaching-tools) –Many-to-many (agents, mobile code) People and devices –Many-to-one (public displays (?)) –One-to-many (remote desktop, chat, etc.) –Many-to-many (public displays)

6 abc Jonathan Bunde-Pedersen Doctoral Colloquium 6 Current State – v4 implementation Client-server –Server is required for collaboration –Server scales nicely (for our purposes) –Cache works locally Front-ends –UIs for different needs –Wearable –Wall –Desktop

7 abc Jonathan Bunde-Pedersen Doctoral Colloquium 7 Current State - v4 user interface

8 abc Jonathan Bunde-Pedersen Doctoral Colloquium 8 Current State - v4 user interface

9 abc Jonathan Bunde-Pedersen Doctoral Colloquium 9 Architecture – Overview Activity Manager Components –Agent-like components –System –Functionality Connectors

10 abc Jonathan Bunde-Pedersen Doctoral Colloquium 10 Architecture – “Rubberbands” Migration policy “Self-organizing” Elasticity, stretch (distance) and weight

11 abc Jonathan Bunde-Pedersen Doctoral Colloquium 11 Architecture – Programming model Annotations Migration is provided Intra-activity communication is provided –E.g. patient switcher –Templates for activities [StatefulField(“my_scrollbar”)] public ScrollBar MyScrollBar; [StatefulField(“my_string”)] public string MyString;

12 abc Jonathan Bunde-Pedersen Doctoral Colloquium 12 Architecture – Visibility AMAP –Hierarchical map showing off inner workings of architecture “Global” variables Event-handlers … –as communication tool –as monitoring tool

13 abc Jonathan Bunde-Pedersen Doctoral Colloquium 13 Architecture – Visibility / dev1 / device_root / activities / 1 / services / A  / dev2 / device_root / remote_components / A Operations on the tree is reflected in the system at run-time

14 abc Jonathan Bunde-Pedersen Doctoral Colloquium 14 Contributions – Collaboration Exploring … –one application  many devices –one person  many devices –many people  one device

15 abc Jonathan Bunde-Pedersen Doctoral Colloquium 15 Contributions – Collaboration

16 abc Jonathan Bunde-Pedersen Doctoral Colloquium 16 Contributions – Migration Data and applications –Different types of data –Applications likewise Exploring … –many people  many devices –many-applications  many devices

17 abc Jonathan Bunde-Pedersen Doctoral Colloquium 17 Contributions – Serverlessness Electable server-role (super-peer system) Obvious advantage: Single point of failure Configuration(less) –Writing a Jini or uPnP system component Challenges –Migration of data –Consistency, synchronization issues

18 abc Jonathan Bunde-Pedersen Doctoral Colloquium 18 Approach – Project scope Centre for Pervasive Healthcare –Scandinavian tradition of participatory design ABC project (4 years) ElderTech project (6 months) Ph.D.s –Sensor networks –Novel user interfaces –Architecture (me)

19 abc Jonathan Bunde-Pedersen Doctoral Colloquium 19 Approach – User involvement Original concepts based on user input Architecture ideas + requirements from experiences with v4 ElderTech (senior citizens, nurses, care- staff) Falck (emergency rescue personnel) Horsens Hospital (doctors, nurses)

20 abc Jonathan Bunde-Pedersen Doctoral Colloquium 20 Approach – Prototyping Architectural prototype Services –Picture/Video Album (ET) –Hospitals (aware) X-Ray viewer Journal –Emergency medicine (palcom) Injury-charts ER organizer Merge concurrent projects into ABC

21 abc Jonathan Bunde-Pedersen Doctoral Colloquium 21 Evaluation – Technical Performance Reliability (improvement over single point of failure) Scalability (How many peers, services and how much data can we sustain?) Complexity (How hard is it writing services?)

22 abc Jonathan Bunde-Pedersen Doctoral Colloquium 22 Evaluation – ElderTech Co-operation w. kommune, IBM, “nursing home” Utility (Have we enabled others to be successful?) –Architecture as a framework for building services –Sensor network Completeness (Can we build useful services?)

23 abc Jonathan Bunde-Pedersen Doctoral Colloquium 23 Open issues Current status –Related research –Implementation Approach Evaluation –Activity as concept? –Activity operations? –Privacy concerns (shared activities)


Download ppt "Abc Architectural Support for Activity- Based and Ubiquitous Computing Jonathan Bunde-Pedersen Ph.D. student Centre for Pervasive Healthcare Aarhus University."

Similar presentations


Ads by Google