context-driven adaptation of mobile services. leuven, 14 oktober 2004 agenda inleiding en stand van...

Context-Driven Adaptation

of Mobile Services

Leuven, 14 oktober 2004

agenda

Inleiding en stand van zaken WP1

Context: definition and specification Building Scenarios

WP5: Designing Context-Sensitive User Interfaces WP6: Strong Code Mobility Plannen voor komend jaar Napraten, netwerking, drink … in faculty club

Context-Driven Adaptation of

Mobile Services

Inleiding en stand van zaken


Overzicht project: vertrouwde slides

Projectplanning

Inzoomen op werk uit afgelopen jaar dat verder

niet aan bod komt in de presentaties WP2, WP3, WP4, WP8


Motivatie en probleemstellingtoekomstvisie van personal devices in AMI omgeving

zeer dynamisch platform voor gepersonaliseerde diensten in functie van context

toekomstvisie van personal devices in AMI omgeving zeer dynamisch platform voor gepersonaliseerde diensten in functie van context

nood aan een resourcebewust dienstenplatform met ondersteuning voor adaptiviteit

statische en dynamische met ondersteuning voor mobiliteit in functie van de context

persoonlijke context locatie device resources


Service DeploymentInfrastructure (SDI)

Service Provider

Service Users

CoDAMoS Service Platform


Service Provider SDI


Context Specification

Comp. Library Compositions

Service Provider

Service Users







Service Provider

Service Users


WP 1context

specification






Rh, User profile, Location, …

Rs Rh

Service Provider

Service Users

Rh

Rs





Context Specification Generated Implementation

Service S1



Rs Rh

Service Provider

Service Users

Rh

Rs


Service S1’’




Context Specification Generated Implementations

Service S



Rs Rh

Service Provider

Service Users

Rh

Rs


WP 2:contextdriven

implementationgeneration

WP 3:performance

modelling



Service-User SDI Service-User SDI Service-User SDI



Service S



Rs Rh

Service Provider

Service S1’

Service S2’

Service S3Service S1’’

Service S2’’

Users

Service Users

Device resources

Rh

Rs


Service S4






Service S



Rs Rh

Service Provider

Service S1’

Service S2’


Service S2’’

Users

Service Users

Device resources

Rh

Rs


Service S4

UI: speech UI: graphical, speech






Service S



Rs Rh

Service Provider

Service S1’

Service S2’


Service S2’’

Users

Service Users

Device resources

Rh

Rs


Service S4

UI: speech UI: graphical, speech

WP 5:contextawareuser

interface






Service S



Rs Rh

Service Provider

Service S1’

Service S2’


Service S2’’

Service S4

Users

Service Users

Device resources

Cooperation

Context awareness/discoveryUI: speech

Rh

Rs

UI: graphical, speech

Service S4







Service S



Rs Rh

Service Provider

Service S1’

Service S2’


Service S2’’

Service S4

Users

Service Users

Device resources

Cooperation


Rh

Rs


Service S4


WP 4:service

integration






Service S



Rs Rh

Service Provider

Service S1’

Service S2’


Service S2’’

Service S4

Mobility

Users

Service Users

Device resources

Rh

Rs







Service S



Rs Rh

Service Provider

Service S1’

Service S2’


Service S2’’

Service S4

Mobility

Users

Service Users

Device resources

Rh

Rs


Service S4






Service S



Rs Rh

Service Provider

Service S1’

Service S2’


Service S2’’

Service S4

Mobility

Users

Service Users

Device resources

Rh

Rs


Service S4

WP 6:code

mobility






Service S



Rs Rh

Service Provider

Service S1’

Service S2’


Service S2’’

Service S4

Mobility

Users

Service Users

Device resources

Cooperation


Rh

Rs


Service S4



Doelstellingen

1 contextspecificatie2 contextgedreven

implementatiegeneratie 3 modelleren van prestatie4 integratie van diensten5 contextbewuste User Interfaces6 codemobiliteit

1 uittekenen van scenario’s

2 tools en omgevingen die de resultaten in de verschillende werkpakketten demonstreren

3 integratie van resultaten van telkens 2 of 3 werkpakkettenin demonstrators

CoDAMoS beoogt strategisch, generisch basisonderzoek.Alle ontwikkelde software dient louter als proof-of-concept.CoDAMoS beoogt strategisch, generisch basisonderzoek.Alle ontwikkelde software dient louter als proof-of-concept.

Wetenschappelijke doelstellingen Technologische doelstellingen

Economische doelstellingen1 transfer van innovatieve oplossingen naar industriële partners

zal leiden tot creatie van nieuwe producten, diensten, en markten en productiviteitsverhoging in Vlaamse industrie

2 opzetten van specifieke follow-up projecten


Projectstructuur

WP 8 WP 8

WP 1 WP1

WP 7WP 7

0 12 24 24 36 48

fase 1 fase 2

WP9

WP 2 - 6 WP 2 - 6

mijlpalen M m M m M


Projectplanning

WP2: Context-DrivenImplementation Generation


WP2: Tasks for Year 1

T2.1: Component-Based Frameworks – status study Assess applicability of existing CB approaches Assess possible approaches for describing alternative

implementations T2.2a: High-level composition language

Develop initial language model for composing alternative software components, based on context

T2.4a: Tool support


Task 2.1: Component-Based Frameworks

Study of Component-Based Design Approaches Model-Driven Software Development/MDA

Model-Driven Architecture standard researched in detail Synthesis-Based Design

Design Algebra and CoCompose approaches researched in detail

Study of Component Configuration Management Component Repositories

Component Libraries approach has been researched in detail Component Composition

Composition Patterns/Adapters approach researched in detail


Task 2.2: Model Transformation Composition Language – Context-Aware Modelling

Software models expressed in UML Standard language for OO modelling Meta-model defined with Meta Object Framework (MOF)

Context models expressed in OWL Standard language for ontologies OWL Description Logic allows for automatic reasoning

Model transformations expressed in QVT “Query-Views-Transformations” Standard-under-construction for model transformations

based on MOF and UML


Task 2.2: Model Transformation Composition Language – Context-Driven Refinement Based on Synthesis-Based Design

Select/eliminate alternative model transformations Uses context constraints to eliminate all non-feasible

alternatives Automatic reasoner (e.g. RACER) can do this

Sorts remaining alternatives using selection criteria: Constraint predicate composition:

more predicates in a constraint = more context-specific Subsumption distance:

actual value lies closer to the constraint = more context-specific


Task 2.4: Tool support

Software model repositories – Meta Object Framework (MOF) Standardised Java Implementation: JMI

Model Transformation Engines – QVT (MOF/JMI-based) INRIA/Triskell BasicMTL ModFact QVT Engine

Ontology Modelling and Reasoning Protégé Ontology Editor RACER Automatic Reasoner for Description Logic

Integration test-bed: Eclipse-based CoCompose2 Integrates with BasicMTL/Modfact engine

WP3: Performance Modeling


WP3: Performance modeling

Cycle budget Power budget Memory Bandwidth

program

?

Proof-of-concept tool uses statistical simulation to get very accurate results

IPC, EPC, memory usagerequired bandwidth


Statistical simulation (1)

Program trace

μ-arch independent

μ -arch dependent

Statisticalprofile of the

program

Assemblesynthetic trace

simulate

Synthetic trace(much smaller)

IPC estimate

EPC estimate


Statistical simulation (2)

Improved statistical simulation framework Statistical control-flow graph

Modeling delayed updates for branch behavior Detailed model of the hardware is required

Component sizes, latencies, …

A

B

C

A (33%)

B (66%)

C(45%)

B (55%)B(100%)1st order statistical

flow graph for 3 basic blocks A, B, and C


Other important resources What about memory?

Usually very input-dependent: determine allocation behavior via DIOTA (instrumentation tool)

Trace malloc/free library calls (evolution of allocations in time) Trace mmap/munmap system calls (yields upper bounds)

What about bandwidth? Network usage in the program Network usage for moving a (part of a) program Input dependent

Other requirements, such as display requirements are very program-specific and can not automatically be modeled.


Conclusion

Very accurate performance model 6.6% error on average for IPC 4% error on average for EPC

Still some work to do for memory consumption and bandwidth requirements: Measuring both through instrumentation? Measuring bandwidth requirements through input-replay

concept? Modeling memory and bandwidth in terms of input to the

program?

WP4: Service Integration


Services formalism and resourcecontract monitoring Requirements for an AmI service architecture:

Service specification Component-based service specification

Based on SEESCOA-methodology Service platform

Supporting service co-operation Resource aware Supporting user in a mobile environment Deployment on high-end embedded devices

Service discovery Personalized through user profiles Network transparent


Component-based service specification


Component-based service specification

Properties of a service

Functional aspects Components - Ports Connectors Service Ports: proxies for internal component ports Service Control Interface: managing the service

Non-functional aspects Contracts Service Information Interface: static information for service discovery Context Interface: dynamic context information gateway Context Control Block: context managing component

Services as composite components


Resource contract monitoring

Resource contracts Negotiating and specifying service resource requirements at runtime

Goal Flexible service support in a distributed environment

Limited availability of environmental resources Guaranteeing Quality of Service aspects Guidelines for application adaptation mechanisms and component mobility

Methodology Contract (re-)negotiation between components and middleware Contract enforcement by middleware Using:

Java Profiling Interface (for resource monitoring) Constraint solving algorithms


Resource contract monitoring

Service platform: Using Draco Component System

Component-based application infrastructure (cfr. SEESCOA)

With support for resource contract monitoring

WP8: Valorisation


task 8.1: internal dissemination and interaction with user commission kick-off meeting 2 workshops

context code mobility

project website accessible for user commission many bilateral contacts new member user commission: Commeto


task 8.2: external dissemination

publications: 19 papers in international journals,

conferences and workshops

external website


agenda

Inleiding en stand van zaken WP1

Context: definition and specification Building Scenarios

WP5: Designing Context-Sensitive User Interfaces WP6: Strong Code Mobility Plannen voor komend jaar Napraten, netwerking, drink … in faculty club


Vragen

context-driven adaptation of mobile services. leuven, 14 oktober 2004 agenda inleiding en stand van...

Documents