1 / 9

Adaptability for flexible mobile service provision in 3G and beyond Nikos Houssos

Adaptability for flexible mobile service provision in 3G and beyond Nikos Houssos nhoussos@di.uoa.gr. Generic adaptation mechanisms. Generic, re-usable, run-time updatable adaptation engine Generic indicates independence from: Types of context parameters Adaptation algorithms

esimons
Télécharger la présentation

Adaptability for flexible mobile service provision in 3G and beyond Nikos Houssos

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  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. Component Locations (Application Servers) Component Locations (Application Servers) Downloading and Packaging Module Single service bundle Client Client (a) (b) Service adaptation/packaging • 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)

  7. VASP enterprise servers VASP enterprise servers VASP enterprise servers VASP VASP Application using Application using Application using Application using Application using Application using Application using Application using Application using Application using Application using Application using domain domain network functionality network functionality network functionality network functionality network functionality network functionality network functionality network functionality network functionality network functionality network functionality network functionality . . . . . . . . . . . . Open interfaces (OSA/Parlay,JAIN SPA) Open interfaces (OSA/Parlay,JAIN SPA) Open API Gateway Open API Gateway Proprietary JAIN JSLEE JSLEE JSLEE interfaces interfaces Non Non Non - - - JAIN JAIN JAIN JCC/JCAT JCC/JCAT JCC/JCAT implementation implementation implementation Telecom Telecom Protocol APIs (INAP, SIP, etc) Protocol APIs (INAP, SIP, etc) Protocol APIs (INAP, SIP, etc) network domain Network infrastructure

  8. VASP VASP Service platform client (management application) Application using Application using Application using Application using domain domain network functionality network functionality network functionality network functionality . . . . . . Service platform interfaces Service Provision and Management Platform Service management platform domain Charging Reconfiguration Control / Service Provision Manager Accounting Billing UIMM SDM PDM LIM - - - Reconfiguration Manager Open interfaces (OSA/Parlay,JAIN SPA) JSLEE Non - JAIN JCC/JCAT implementation Open API Gateway Open API Gateway Protocol APIs (INAP, SIP, etc) Proprietary JAIN JSLEE JSLEE interfaces interfaces Non Non - - JAIN JAIN JCC/JCAT JCC/JCAT implementation implementation Telecom Telecom Protocol APIs (INAP, SIP, etc) Protocol APIs (INAP, SIP, etc) network domain Network infrastructure

  9. Thank you

More Related