1. Context-Driven Adaptation of Mobile Services

2. 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

3. Context-Driven Adaptation of Mobile Services Inleiding en stand van zaken

4. Leuven, 14 oktober 2004 Overzicht project: vertrouwde slides Projectplanning Inzoomen op werk uit afgelopen jaar dat verder niet aan bod komt in de presentaties  WP2, WP3, WP4, WP8

5. Leuven, 14 oktober 2004 Motivatie en probleemstelling toekomstvisie 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

6. Leuven, 14 oktober 2004 Service Deployment Infrastructure (SDI) Service Provider Service Users CoDAMoS Service Platform

7. Leuven, 14 oktober 2004 Service Provider SDI Service Deployment Infrastructure (SDI) Context Specification Comp. LibraryCompositions Service Provider Service Users CoDAMoS Service Platform

8. Leuven, 14 oktober 2004 Service Provider SDI Service Deployment Infrastructure (SDI) Context Specification Comp. LibraryCompositions Service Provider Service Users CoDAMoS Service Platform WP 1 context specification

9. Leuven, 14 oktober 2004 Service Provider SDI Service Deployment Infrastructure (SDI) Context Specification Comp. LibraryCompositions R h, User profile, Location, … R s  R h Service Provider Service Users RhRh RsRs CoDAMoS Service Platform

10. Leuven, 14 oktober 2004 Service Provider SDI Service Deployment Infrastructure (SDI) Context Specification Generated Implementation Service S1 Comp. LibraryCompositions R h, User profile, Location, … R s  R h Service Provider Service Users RhRh RsRs CoDAMoS Service Platform Service S1’’

11. Leuven, 14 oktober 2004 Service Provider SDI Service Deployment Infrastructure (SDI) Context Specification Generated Implementations Service S Comp. LibraryCompositions R h, User profile, Location, … R s  R h Service Provider Service Users RhRh RsRs CoDAMoS Service Platform WP 2: context driven implementation generation WP 3: performance modelling

12. Leuven, 14 oktober 2004 Service Provider SDI Service-User SDI Service Deployment Infrastructure (SDI) Context Specification Generated Implementations Service S Comp. LibraryCompositions R h, User profile, Location, … R s  R h Service Provider Service S1’ Service S2’ Service S3 Service S1’’ Service S2’’ Users Service Users Device resources RhRh RsRs CoDAMoS Service Platform Service S4

13. Leuven, 14 oktober 2004 Service Provider SDI Service-User SDI Service Deployment Infrastructure (SDI) Context Specification Generated Implementations Service S Comp. LibraryCompositions R h, User profile, Location, … R s  R h Service Provider Service S1’ Service S2’ Service S3 Service S1’’ Service S2’’ Users Service Users Device resources RhRh RsRs CoDAMoS Service Platform Service S4 UI: speech UI: graphical, speech

14. Leuven, 14 oktober 2004 Service Provider SDI Service-User SDI Service Deployment Infrastructure (SDI) Context Specification Generated Implementations Service S Comp. LibraryCompositions R h, User profile, Location, … R s  R h Service Provider Service S1’ Service S2’ Service S3 Service S1’’ Service S2’’ Users Service Users Device resources RhRh RsRs CoDAMoS Service Platform Service S4 UI: speech UI: graphical, speech WP 5: context aware user interface

15. Leuven, 14 oktober 2004 Service Provider SDI Service-User SDI Service Deployment Infrastructure (SDI) Context Specification Generated Implementations Service S Comp. LibraryCompositions R h, User profile, Location, … R s  R h Service Provider Service S1’ Service S2’ Service S3 Service S1’’ Service S2’’ Service S4 Users Service Users Device resources Cooperation Context awareness/discovery UI: speech RhRh RsRs UI: graphical, speech Service S4 CoDAMoS Service Platform

16. Leuven, 14 oktober 2004 Service Provider SDI Service-User SDI Service Deployment Infrastructure (SDI) Context Specification Generated Implementations Service S Comp. LibraryCompositions R h, User profile, Location, … R s  R h Service Provider Service S1’ Service S2’ Service S3 Service S1’’ Service S2’’ Service S4 Users Service Users Device resources Cooperation Context awareness/discovery UI: speech RhRh RsRs UI: graphical, speech Service S4 CoDAMoS Service Platform WP 4: service integration

17. Leuven, 14 oktober 2004 Service Provider SDI Service-User SDI Service Deployment Infrastructure (SDI) Context Specification Generated Implementations Service S Comp. LibraryCompositions R h, User profile, Location, … R s  R h Service Provider Service S1’ Service S2’ Service S3 Service S1’’ Service S2’’ Service S4 Mobility Users Service Users Device resources RhRh RsRs CoDAMoS Service Platform

18. Leuven, 14 oktober 2004 Service Provider SDI Service-User SDI Service Deployment Infrastructure (SDI) Context Specification Generated Implementations Service S Comp. LibraryCompositions R h, User profile, Location, … R s  R h Service Provider Service S1’ Service S2’ Service S3 Service S1’’ Service S2’’ Service S4 Mobility Users Service Users Device resources RhRh RsRs CoDAMoS Service Platform

19. Leuven, 14 oktober 2004 Service Provider SDI Service-User SDI Service Deployment Infrastructure (SDI) Context Specification Generated Implementations Service S Comp. LibraryCompositions R h, User profile, Location, … R s  R h Service Provider Service S1’ Service S2’ Service S3 Service S1’’ Service S2’’ Service S4 Mobility Users Service Users Device resources RhRh RsRs CoDAMoS Service Platform Service S4

20. Leuven, 14 oktober 2004 Service Provider SDI Service-User SDI Service Deployment Infrastructure (SDI) Context Specification Generated Implementations Service S Comp. LibraryCompositions R h, User profile, Location, … R s  R h Service Provider Service S1’ Service S2’ Service S3 Service S1’’ Service S2’’ Service S4 Mobility Users Service Users Device resources RhRh RsRs CoDAMoS Service Platform Service S4 WP 6: code mobility

21. Leuven, 14 oktober 2004 Service Provider SDI Service-User SDI Service Deployment Infrastructure (SDI) Context Specification Generated Implementations Service S Comp. LibraryCompositions R h, User profile, Location, … R s  R h Service Provider Service S1’ Service S2’ Service S3 Service S1’’ Service S2’’ Service S4 Mobility Users Service Users Device resources Cooperation Context awareness/discovery UI: speech RhRh RsRs UI: graphical, speech Service S4 CoDAMoS Service Platform

22. Leuven, 14 oktober 2004 Doelstellingen 1 contextspecificatie 2 contextgedreven implementatiegeneratie 3 modelleren van prestatie 4 integratie van diensten 5 contextbewuste User Interfaces 6 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 werkpakketten in demonstrators CoDAMoS beoogt strategisch, generisch basisonderzoek. Alle ontwikkelde software dient louter als proof-of-concept. Wetenschappelijke doelstellingen Technologische doelstellingen Economische doelstellingen 1 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

23. Leuven, 14 oktober 2004 Projectstructuur WP 8 WP 1 WP 7 0 12 24 24 36 48 fase 1fase 2 WP9 WP 2 - 6 mijlpalen M m M m M

24. Leuven, 14 oktober 2004 Projectplanning

25. WP2: Context-Driven Implementation Generation

26. Leuven, 14 oktober 2004 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

27. Leuven, 14 oktober 2004 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

28. Leuven, 14 oktober 2004 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

29. Leuven, 14 oktober 2004 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

30. Leuven, 14 oktober 2004 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

31. WP3: Performance Modeling

32. Leuven, 14 oktober 2004 WP3: Performance modeling Cycle budgetPower budgetMemoryBandwidth program ? Proof-of-concept tool uses statistical simulation to get very accurate results IPC, EPC, memory usage required bandwidth

33. Leuven, 14 oktober 2004 Statistical simulation (1) Program trace μ-arch independent μ -arch dependent Statistical profile of the program Assemble synthetic trace simulate Synthetic trace (much smaller) IPC estimate EPC estimate

34. Leuven, 14 oktober 2004 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%) 1 st order statistical flow graph for 3 basic blocks A, B, and C

35. Leuven, 14 oktober 2004 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.

36. Leuven, 14 oktober 2004 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?

37. WP4: Service Integration

38. Leuven, 14 oktober 2004 Services formalism and resource contract 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

39. Leuven, 14 oktober 2004 Component-based service specification

40. Leuven, 14 oktober 2004 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

41. Leuven, 14 oktober 2004 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

42. Leuven, 14 oktober 2004 Resource contract monitoring Service platform:  Using Draco Component System Component-based application infrastructure (cfr. SEESCOA) With support for resource contract monitoring

43. WP8: Valorisation

44. Leuven, 14 oktober 2004 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

45. Leuven, 14 oktober 2004 task 8.2: external dissemination publications: 19 papers in international journals, conferences and workshops external website

46. 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

47. Leuven, 14 oktober 2004 Vragen