Adaptability for flexible mobile service provision in 3G and beyond Nikos Houssos...
-
Upload
tobias-french -
Category
Documents
-
view
212 -
download
0
Transcript of Adaptability for flexible mobile service provision in 3G and beyond Nikos Houssos...
Generic adaptation mechanisms Generic, re-usable, run-time updatable adaptation engine Generic indicates independence from:
Types of context parametersAdaptation 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 architectureContext sources
Context Repository
User Session State
UIMM logic (including
context retrieval)
Adapters
Adapter
Adapter
Adapter
Adapter
Main AdaptationEngine
Generic Interface
Generic Adaptation Module Algorithm repository
UIMM
Reconfiguration Manager
Packaging and Downloading Module
Context Retrieval
Adaptation Decision Making
Adaptation Enforcement/Application
Reconfiguration Control & Service Provision Manager
to MTS
(1), (5)
(10)
(9)
(4), (8)(3)
(2)
(7) (6)
Context sources
Context Repository
User Session State
UIMM logic (including
context retrieval)
Adapters
Adapter
Adapter
Adapter
Adapter
Main AdaptationEngine
Generic Interface
Generic Adaptation Module Algorithm repository
UIMM
Reconfiguration Manager
Packaging and Downloading Module
Context Retrieval
Adaptation Decision Making
Adaptation Enforcement/Application
Reconfiguration Control & Service Provision Manager
to MTS
(1), (5)
(10)
(9)
(4), (8)(3)
(2)
(7) (6)
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
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
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 domain
Application using network functionality
Application using network functionality
. . .
Application using network functionality
VASP enterprise servers
Telecom network domain
Open interfaces (OSA/Parlay,JAIN SPA)
Proprietary interfaces
VASP domain
Application using network functionality
Application using network functionality
. . .
Application using network functionality
VASP enterprise servers
Application using network functionality
Application using network functionality
. . .
Application using network functionality
Application using network functionality
Application using network functionality
. . .
Application using network functionality
VASP enterprise servers
Telecom
Open API GatewayOpen API Gateway
Network infrastructure
Non- JAIN implementation
JSLEE
JCC/JCAT
Protocol APIs (INAP, SIP, etc)
Non - JAIN implementation
JSLEE
JCC/JCAT
Protocol APIs (INAP, SIP, etc)
Non - JAIN implementation
JSLEE
JCC/JCAT
Protocol APIs (INAP, SIP, etc)
Open interfaces (OSA/Parlay,JAIN SPA)
JAIN interfaces
VASP domainVASP domain
Application using network functionality. . .. . .
Application using network functionality
Telecom network domain
Proprietary interfaces
Telecom
Open API GatewayOpen API Gateway
Network infrastructure
Non -JAIN implementation
JSLEE
JCC/JCAT
Protocol APIs (INAP, SIP, etc)
Non -JAIN implementation
JSLEE
JCC/JCAT
Protocol APIs (INAP, SIP, etc)
Non -JAIN implementation
JSLEE
JCC/JCAT
Protocol APIs (INAP, SIP, etc)
Open interfaces (OSA/Parlay,JAIN SPA)
JAIN interfaces
Service Provision and Management Platform
Reconfiguration Manager
Reconfiguration Control / Service Provision ManagerUIMM - - -
ChargingAccountingBillingSDM PDM LIM
Application using network functionalityApplication using network functionality
Service platform client
(management application)
Service platform interfaces
Service management platform domain
Thank you