[email protected] Software Architecture and Technology for AAL Martin Becker Dagstuhl...

[email protected]

Software Architecture and Technology for AAL

Martin Becker

Dagstuhl Seminar AAL16.11.2007

2/56

© Fraunhofer IESE 2007

Dagstuhl Seminar AALDagstuhl

Software Technology: Challenges and Opportunities

16.11.2007

Fraunhofer Institute for Experimental Software Engineering

•Kaiserslautern, Germany•180 Employees•Applied Research & TT in Systems & Software Engineering•International Positioning

•USA, Hungary, India, Japan, and Korea

• Innovative Cooperation Model•“Research Labs”

• High International Reputation in “Systems & Software Engineering”

•No. 1 in Europe (JSS, 2005)

3/56




16.11.2007

Content

• Ambient Assisted Living (AAL)

• Architectural Considerations

• Promising Technology

• Remarks, Questions & Wrap Up

4/56




16.11.2007

Ambient Assisted Living (AAL)

5/56




16.11.2007

Ambient Assisted Living (AAL)

Equipment and services for the independent living of people, via the seamless integration of info-communication technologies within homes and extended homes, thus increasing their quality of life and autonomy and reducing the need for being institutionalised [source: www.aal169.org]

Goals:

• Increase quality of life

• Reduce need for external assistance

• Reduce health and care costs for the individual and the society

• Avoid stigmatisation

• Ease human care

Goals:

• Increase quality of life

• Reduce need for external assistance

• Reduce health and care costs for the individual and the society

• Avoid stigmatisation

• Ease human care

6/56




16.11.2007

AAL Landscape

Home

ExtendedHome

Health & Care

Safety, Security &

PrivacyServices & Goods

Social Environment

8/56




16.11.2007

AAL Landscape

Home

ExtendedHome

Health & Care

Safety, Security &

PrivacyServices & Goods

Social Environment

Hospital

EmergencyService

Med. PractitionerHomeCare

Reha

DomoticHousehold

Goods Delivery

Mobility Wellness

Social Interaction

Services

SecurityService

Poor integration in overlapping areas

this time

Poor integration in overlapping areas

this time

Big Bang will failBig Bang will fail

Where to start first?Where to start first?

9/56




16.11.2007

Projects: BelAmI

Bilaterial German-Hungarian Collaboration on Ambient Intelligence Systems

Research Activities in- Microelectronics and Sensors: Low power systems,

dynamic sensors networks

- Mobile Communication: Adaptive QoS

- Software Engineering: Dynamic reconfigurable architectures, context awareness, resource optimized programming

- Human Computer Interaction: Usability engineering for flexible and adaptive systems, adaptive HCI

- Safety&Security: Analysis and engineering techniques for safe, secure and dependable AmI applications

- System and Software Integration: Position, activity and vital data tracking technology, integration into AAL system architecture and application

Application domain: Assisted living

- Home care assistance in daily routine + health monitoring

Application domain: Assisted living

- Home care assistance in daily routine + health monitoring

Funding: BMBF, RLP, FhG

Duration: 10.2004 – 09.2008

Partners: Fh IESE, TU-KL, BayAmI, TU Budapest, Uni Szeged

Funding: BMBF, RLP, FhG

Duration: 10.2004 – 09.2008

Partners: Fh IESE, TU-KL, BayAmI, TU Budapest, Uni Szeged

10/56




16.11.2007

Assisted Living Lab

• "Demonstrator-driven" research closely related to application

• Integration of partial solutions together with research and industrial partners

• Realistic simulation of the environment

- Requirements elicitation

- Testing of individual technologies (prototypes)

• Pre-studies for field tests

• Evaluation of safety and security, reliability, accuracy, usability, speed, acceptance (before operation)

Partners:• Partners from Industry and Research• Hospital (Westpfalz-Klinkum): Medical

Expertise, User Representative• Nursing Home (Westpfalz-Klinikum):

Users, Real Life• Emergency Medical Service

(Rettungsleitstelle Kaiserslautern): Acute Medical Competence Centre

Partners:• Partners from Industry and Research• Hospital (Westpfalz-Klinkum): Medical

Expertise, User Representative• Nursing Home (Westpfalz-Klinikum):

Users, Real Life• Emergency Medical Service

(Rettungsleitstelle Kaiserslautern): Acute Medical Competence Centre

11/56




16.11.2007

AAL Service Classification

predictiondetection

prevention

drinking eating

cleaning cooking dressing

medication

logistic servicesservices for finding things

infotainment services

predictiondetection

prevention

shopping traveling banking

transportation servicesnavigation services

EmergencyTreatment

AutonomyEnhancement

Comfort

Indoor

Outdoor

• Dependance decreases to the right

• Relevance of a function can change over time (e.g., communication service)

12/56




16.11.2007

Assisted Living Lab

13/56




16.11.2007

Projects: EMERGE

Funding: EU IST-045056

Duration: 02.2007 – 10.2009

Partners: FhG IESE, Siemens, Westpfalz-Klinikum, NCSR Demokritos, EMIC, e-ISOTIS, AoT, Bay Zoltan, Med. Uni. Graz

Funding: EU IST-045056

Duration: 02.2007 – 10.2009

Partners: FhG IESE, Siemens, Westpfalz-Klinikum, NCSR Demokritos, EMIC, e-ISOTIS, AoT, Bay Zoltan, Med. Uni. Graz

Application domain: Emergency assistance in the home environment

Application domain: Emergency assistance in the home environment

14/56




16.11.2007

Projects: AmbiComp

Objective:

Streamline Development of AmI/AAL Solutions

Low cost / high quality solutions

•Development of „AmI Construction Set“:

•Software Engineering Method (Dynamic Integration, Adaptivity, …)

•Software: Development Platform

•Reusable Components

•Development Environment

•Hardware: wireless Nodes with BT/Zigbeeand Infrared Communication

Objective:

Streamline Development of AmI/AAL Solutions

Low cost / high quality solutions

•Development of „AmI Construction Set“:

•Software Engineering Method (Dynamic Integration, Adaptivity, …)

•Software: Development Platform

•Reusable Components

•Development Environment

•Hardware: wireless Nodes with BT/Zigbeeand Infrared Communication

Funding: BMBF-SE2006

Duration: 05.2006 – 12.2008

Partners: Universität Karlsruhe, Beecon GmbH, Alcatel SEL AG, Fraunhofer IESE, Hochschule der Medien Stuttgart

Funding: BMBF-SE2006

Duration: 05.2006 – 12.2008

Partners: Universität Karlsruhe, Beecon GmbH, Alcatel SEL AG, Fraunhofer IESE, Hochschule der Medien Stuttgart

Application domain: Safety and Security (intelligent fire alarm)

Application domain: Safety and Security (intelligent fire alarm)

16/56




16.11.2007

Architectural Considerations

17/56




16.11.2007

Required QualitiesUsability

Dependability & Privacy

Controlability

Affordability

Extensibility

PersonalizationAnticipatory

Integratability

Changability

Accessability

User Experienc

eSuitability

Relevance to achievement of

user goals?

Relevance to achievement of

user goals?

Quality tradeoffs!Quality tradeoffs!

Quality model required!Quality model required!

Performance

20/56




16.11.2007

HumanCapabilities

perfect

existingdisabilities

normal

critical

time

ht = ft (p1, p2, . . . . , pn)

a

b

c

emergency

Human Capability Model

22/56




16.11.2007

Closed Loop Controller

Sensing

Perception

Identification Assisting

Acting

Controlling

Knowledge

Information

Data

Feedback enableslearning!

Feedback enableslearning!

• Information: Activities, Position, Vital Data

23/56




16.11.2007

AAL System – an intelligent environment

AmiNode

User

Interaction

24/56




16.11.2007

Service Oriented Architecture (SOA)

• Separate the contract from the implementation Loose-coupling

• Allows alternate implementations

• Dynamically discover and bind available implementations

• Based on contract (interface)

• Components are reusable

• Static vs. dynamic binding

Service Contract

Componentprovides

uses

Virtualization!Virtualization! Events?Events? QoS?End-to-End?

QoS?End-to-End?

25/56




16.11.2007

World is changing

watchTV watchTVcontrolhome

monitoractivity

Cost sharing?Cost sharing?

Revenue sharing?Revenue sharing?

1:n

1:1

n:m

n:m

Money is made with services!

Money is made with services!

26/56




16.11.2007

Peer-To-Peer

• peer-to-peer computer network exploits diverse connectivity

• cumulative bandwidth of network participants

• equal peer nodes

• ad hoc networking

• interesting qualities: robustness, performance

27/56




16.11.2007

Other Relevant Styles

• Event Driven Architecture

• Multi Agent Systems

• Enterprise Service Bus

• Service Area Networks

• Service Oriented Device Architecture (SODA)

QoS managementwill be central

QoS managementwill be central

Some of these styles will converge

Some of these styles will converge

28/56




16.11.2007

Conceptual Organisation

AssistedPerson

1..*

1..*

3 provide assistance

1..*

1..*


Doctor

EMS

1..* 1..*


1..*1..*provide assistance4

1..*1..*provide assistance4

AssistedPersonAssistant

DoctorAssistant

EMSAssistant

Structure systemlike real world!

Structure systemlike real world!

Easy to understand!

Easy to understand!

AAL System

29/56




16.11.2007

Context-Awareness

• “…Context is any information that can be used to characterize the situation of an entity. An entity is a person, place, or object that is considered relevant to the interaction between a user and an application, including the user and application themselves.”

• “…Context-awareness is a property of a system that uses context to provide relevant information and/or services to the user, where relevancy depends on the user’s task.” [Anind Dey]

• Types: Device, User, Physical Context is key!Context is key!

30/56




16.11.2007

Context-Awareness

ContextManager

ContextProvider

ContextListener

ContextAggregator

-provider

*

-listener

*

ContextAdmin

ContextAccess

Component

registeraccess

Contextmanages

«meta»ContextModel

1

*

defines

• All components can provide/use context• Context can be exchanged between Nodes information distribution• Processed information can be considered as context• Context Manager Information broker

Some kind of blackboardcan be realized!

Some kind of blackboardcan be realized!

Meta-model required!AAL concept model?

Meta-model required!AAL concept model?

31/56




16.11.2007

Context-Awareness

• Any data flow can be realized

• Access of data can be controlled by context management

• Context will become very important

• Quality of context has to be considered: precision, reliability, cost

P

A

L

P P

A L

Standard formats?Standard formats?

What is context?What is context?

32/56




16.11.2007

Adaptation Support

• Support external and self-adaptation (adaptivity)

• Treat adaptation / adaptivity as an aspect (orthogonal)

Component AdaptationModel

0..1

AdaptationManagerConfigurator

0..*

AdaptationAdmin

register

ApplicationReconfiguration

configures

ContextListenerGlobal optimization!Global optimization! Consistentoptimization!

Consistentoptimization!

33/56




16.11.2007

Promising Technology

34/56




16.11.2007

Middleware

• provide complete decentralized communication among components

• provide extensibility and exchangeability

• provide conflict resolution

• Technologies: RMI, Corba, HAVi, Jini, JXTA, UPnP, OSGi, …

Hardware

OS

Middleware

Application

Node

Hardware

Device

Platform := Hardware + OS

35/56




16.11.2007

JXTA

• open source, peer-to-peer protocol

• by Sun Microsystems in 2001

• set of XML messages

• any device connected to a network can exchange messages and collaborate independently of the underlying network topology

• most mature general purpose P2P framework

Conflict Management?Conflict Management?

36/56




16.11.2007

UPnP – Universal Plug and Play

• a set of computer network protocols

• offers an easy way to connect electronic devices on a local network

• without any user configuration

• simple control possibilities for the services of the networked devices by a Control Point

• an ISO standard

37/56




16.11.2007

UPnP features

• Service discovery

• Media and device independence

• Operating system and programming language independence

• Internet-based technologies (IP, TCP, UDP, HTTP, and SOAP, XML)

• Extensibility Conflict Management?Conflict Management?

38/56




16.11.2007

• Problems of nowadays:

- Increased functionality, software complexity

- Shortened product cycles

- Different manufacturers, interoperability problems

• The solution:

- OSGi technology is the dynamic module system for Java™ universal middleware

provides the standardized primitives for the collaborative components

change the composition dynamically without requiring restarts

provides a service-oriented architecture

enables these components to dynamically discover each other for collaboration

OSGi

39/56




16.11.2007

The buildup of the OSGi system

• System services

• OSGi Framework

• Bundels

40/56




16.11.2007

OSGI framework

• provides a standardized environment to applications (called bundles)

• The layers:

- L0: Execution Environment

- L1: Modules: defines the class loading policies

- L2: Life Cycle Management

- L3: Service Registry

• Founds the basis of Eclipse IDE

- no model break

- enables continuous, holistic engineering

41/56




16.11.2007

OSGI Framework

• Allows applications to share a single Java VM

• Classloading

• Isolation/Security

• Communication & Collaborations between applications

• Life cycle management

• Policy freeHardware

BundleBundleBundleBundle

BundleBundle

Operating System

OSGi

Java VM

Bundle (Application)Bundle (Application)

Driver Driver Driver

42/56




16.11.2007

BELAMI OSGI Platform/Overview

• dynamic reconfiguration

• model based adaptation

TCP/IPOSGi

R-OSGi

BELAMI Platform

43/56




16.11.2007

AMIGO

• usability of a networked home system

• developing open, standardized, interoperable middleware

• service discovery and service composition strategies

• each component is responsible for the application of such strategies

• strategies are not public or transparent to the application developers

• semantic description of services

• some components will be publicly availableNice documentation!Nice documentation!

44/56




16.11.2007

AMIGO

45/56




16.11.2007

DynaMITE

• component topologies, which are determined by a data flow model

• components: multimodal input and output, dialogue, strategy components, actuators. The different

• semantic channels:

- define specific strategies for distributing messages

- enable the cooperation of components and the fragmentation of messages into sub-messages

• strategies can be implemented in a distributed way across the software infrastructure

Output

OutputEvents

Input

InputEvents

Dialoge Strategy Actuator

Goals Actions

QoS?QoS?

46/56




16.11.2007

Other Middleware Approaches

• AlarmNet, EASY-LINE+, I2Home, I-LIVING, INHOME, INTERPLAY, LARES, MONAMI, MPOWER, NETCARITY, OASIS, OLDES, Oxygene, PERSONA, SENSACTION-AAL, SOPPRANO …

• Specific qualities

• No One-Size-Fits-All

• Middleware should be an open standard

Cope with several middlewares!

Cope with several middlewares!

Be prepared for change!Be prepared for change!

47/56




16.11.2007

Sementic Web Models

• Resource Description Framework (RDF)

• data interchange formats

• RDF Schema (RDFS)

• Web Ontology Language (OWL)

- formal description of concepts, terms, and relationships within a given knowledge domain

If not applicable, at least some concepts can be used!

If not applicable, at least some concepts can be used!

48/56




16.11.2007

Context Models

• Standard Ontology for Ubiquitous and Pervasive Applications (SOUPA)

- Person, Policies, Agent & Belief-Desire-Intentions, Time, Space, Events

• Context Ontology (CONON)

- RDF based

- computational entity, location, person, and activity

• …[conon]

49/56




16.11.2007

Context Management Systems

• u2m.org [PhD Heckmann]

- manages information about users, about their contexts and the, situation in general

• SOCAM

- rapid prototyping of context-aware services based on CONON

• AMIGO

- well defined interfaces

• …

[Amigo]

quality is oftenunclear

quality is oftenunclear

50/56




16.11.2007

Remarks, Questions& Wrap Up

51/56




16.11.2007

Some remarks

• Clearly separate architecture and technology

- it should be possible

• Separate function (service) and data (context)

- they evolve differently

• Separate between devices and services

- greater flexibility

- ease integration, better interoperability

• Providing technology is not enough

- specifications (function, quality), proof of value are required

• Go for standardized interfaces and information exchange

52/56




16.11.2007

Some Questions

• How to get a sound domain/feature model of AAL?

• Who architects the holistic AAL system?

- we will provide only components to it

- we would profit from standardized interfaces

• Who manages the architecture?

• Who assesses the suitability of technology

We could as a Community do some!

We could as a Community do some!

53/56




16.11.2007

Wrap up

• Promising technology is available

- its applicability is unclear (context dependence, quality)

• Integration of solutions is possible

- but at what quality (effort)?

• Personalized infomation will be key

- how to keep in control of it

• From devices to services

- new business models required

• Proposal: set up a interdisciplinary AAL network with a clear shaped mission

54/56




16.11.2007

AAL Innovation Model

[ www.aal169.org]

We can to matchboth worlds

We can to matchboth worlds

55/56




16.11.2007

56/56




16.11.2007

Stand der Dinge

57/56




16.11.2007

Thank you for your attention

Any Questions

or Comments

[email protected] Software Architecture and Technology for AAL Martin Becker Dagstuhl...

Documents

Transcript of [email protected] Software Architecture and Technology for AAL Martin Becker Dagstuhl...