Download Generic adaptation mechanisms

Adaptability
for flexible mobile service provision
in 3G and beyond
Nikos Houssos
[email protected]
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)
Generic adaptation architecture
Context sources
UIMM
Reconfiguration Control &
Service Provision Manager
Adapters
UIMM logic
(including
context retrieval)
Context
Retrieval
Context
Repository
User Session State
(1), (5)
Generic Adaptation Module
(2)
(4), (8)
to MTS
Adaptation
Decision
Making
(7) (6)
(9)
Generic Interface
(3)
Algorithm
repository
Adapter
Adapter
Main Adaptation
Engine
Adapter
Adapter
(10)
Reconfiguration Manager
Adaptation
Enforcement/
Application
Packaging and
Downloading Module
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)
Service adaptation/packaging
Component Locations (Application Servers)
Component Locations (Application Servers)
Downloading and
Packaging Module
Single service bundle
Client
Client
(a)
(b)
- Efficient utilization of the wireless link
- Dynamic, on-demand composition
- Support for multiple service models/representations
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)
VASP enterprise servers
VASP
domain
Application using
network functionality
Application using
network functionality
. . .
Application using
network functionality
Open interfaces (OSA/Parlay,JAIN SPA)
Open API Gateway
Proprietary
interfaces
Telecom
network
domain
JSLEE
Non -JAIN
implementation
JCC/JCAT
Protocol APIs (INAP, SIP, etc)
Network infrastructure
JAIN
interfaces
VASP
domain
Service platform
client
(management
application)
Application using
network functionality
. . .
Application using
network functionality
Service platform interfaces
Service Provision and Management Platform
Reconfiguration Control / Service Provision Manager
UIMM
SDM
PDM
LIM
---
Service
management
platform
domain
Charging
Accounting
Billing
Reconfiguration Manager
Open interfaces (OSA/Parlay,JAIN SPA)
Open API Gateway
Proprietary
interfaces
Telecom
network
domain
JSLEE
Non -JAIN
implementation
JCC/JCAT
Protocol APIs (INAP, SIP, etc)
Network infrastructure
JAIN
interfaces
Thank you