1. Adaptability for flexible mobile service provision in 3G and beyond Nikos Houssos nhoussos@di.uoa.gr

2. Generic adaptation mechanisms  Generic, re-usable, run-time updatable adaptation engine  Generic indicates independence from:  Types of context parameters  Adaptation algorithms  Re-usable for adaptation decisions across different functional layer  Updatable at run-time -> inline with 4G requirements  Already available: Development of core functionality, integration with MOBIVAS platform, implementation of certain adapters  Further steps:  Development of remote algorithm loading function (Java, network programming)  Generic interface for context retrieval/update (Java, network programming)  Development of further adapters (Java, RDF/XML)

3. Generic adaptation architecture

4. Service adaptation  Many possible adaptation functions (Re)allocation of service components Composite services (multiple components) Dynamic interactions with other components  Many possible approaches Deployment-time vs. run-time Application-aware vs. application transparent  Many possible service “models” Java, Web services,…  Further steps: Deployment-time component allocation (Java, UML) Run-time component re-allocation (Java, UML) Independence from service model and representation (Java, UML. RDF/XML)

5. Service adaptation/packaging Client Component Locations (Application Servers) Downloading and Packaging Module Component Locations (Application Servers) Client Single service bundle (a)(b) - Efficient utilization of the wireless link - Dynamic, on-demand composition - Support for multiple service models/representations

6. Support for automated deployment of OSA/Parlay services  Applications may use (in a secure manner) functionality of the underlying infrastructure through open APIs (e.g,. OSA/Parlay)  Registration/deployment of those applications introduces significant management overhead  Mediating service platform simplifies this procedure – easier deployment for VASPs  Already developed: basic functionality + OSA/Parlay emulator  Further steps Integration with service profile manipulation/storage functions (RDF/XML, JDBC) Enhancement of GUI (Java) Generic service validation functionality (Java, UML, XML) Contract management and monitoring (Java, UML, XML)

9. Thank you