MEXE
Outline
•2G and 3G Services
•What is MExE ?
•Example MExE services
•MExE functionality
•MExE security
•MExE secure transfer
•MExE timetable and summary
2
2G mobile services
• core network supplementary services (e.g.
call forwarding, call barring, call diversion
etc.)
• limited, expensive to develop, difficult to
deploy
• all operators with same bland standardised
services
• little scope for operators to differentiate
• tariffs are principle differentiators
3
3G mobile multimedia
mobile phones fully internet integrated
–internet and multimedia services, on the move
– by 2005 more people will be interacting with the
WWW via wireless devices than traditional
computers
• operator and third party multimedia services
• generally no services standardised, but enabled
using 3GPP services toolkits (e.g. services toolkits
(e.g. MExE MExE, CAMEL, USAT, OSA) and IP/IT
toolkits)
• new personalised multimedia services rapidly
developed to differentiate from competitors
4
Services toolkits in 3G networks
5
MExE Overview
•standardised execution environments in a mobile
phone



WAP
PersonalJava
CLDC/MIDP Java
Applicable to 3G, non-3G, cordless and fixed
environments
•IT/IP multimedia services running on mobile phones

write once, execute on many mobile phones
• transfer of multimedia services

up/downloading, network/3rd party, MExE-to-MExE services
•standardised negotiation of capabilities with servers

i.e. device type, screen size, memory, bearers etc.
6
MExE Service Scenarios
7
MExE Architecture
8
Example MExE Device
9
Example MExE services
10
Example MExE services
11
Example MExE Services
12
Example MExE Services
13
Example MExE Services
14
Example MExE Services
s
15
MExE Functionality
16
MExE Functionality
17
MExE Functionality
18
MExE Functionality
19
MExE Functionality
20
MExE Summary
21
Reconfigurability
Outline
 Why Reconfigurabillity?
 Reconfigurability Perspective
 Road-map
 Main challenges for Reconfigurability
implementation
 Synthesis
23
Why Reconfigurabillity?
Various
service
profiles
Complexity for profile
interpretation, policy
enforcement, protocol
download etc.
Various user
profiles
Reconfigurability/adaptability
management Ubiquitous Service
provision
SP
SP
Service
Service
Provider
Network
Various terminal
profiles
Various
service
providers
Various access and
network capabilities
24
Reconfigurability & AdaptabilityKey Enablers of systems integration and advanced service
provision for 3G/4G
Internet
2G
3G
4G
25
Reconfigurability Perspective
Current Status
 Service provision in 2G networks has been mainly based on voice
services
 “Closed” business model support
 Limited operator differentiation
 Limited set of offered services
 Mobile service provision is facing important advancements
 “Re-configurability is a concept that embraces advanced new
capabilities in service provision and support and extends them to
cover more challenging possibilities including the reconfiguration of
mobile terminal capabilities, the dynamic adaptation of the
communication protocol stacks or even the re-definition of the
physical layer of the PLNM”
26
Reconfigurability Perspective
Beyond 3G
Support for flexible business models with novel dynamic services
Convergence towards an IP-based core network and ubiquitous, seamless
access between 2G, 3G, broadband and broadcast wireless access schemes,
augmented by self-organizing network schemes and short range connectivity
between intelligent communication appliances
Dynamic service registration, deployment and update by Service Providers
(SPs)
Dynamic user registration
Support for QoS, flexible security schemes
Support for flexible charging/accounting models
Advanced profile management
(user/service/network/terminal/charging/security)
Context aware and adaptable service deployment
Advanced Service discovery - based on various parameters, e.g.:
Terminal capabilities
User profile
Service profile
Location etc.
27
Road-map
Terminal, networks, services and regulation evolutions
1-Mode
2G/3G Dual
(Multiband) Mode
Circuit
Switched
Packet
Switched
Limited, static
Static Spectrum
Allocation
2000
Composite
Multimode
Fully Software
Definable
Convergent,
reconfigurable
Self Organising
Flexible, reconfigurable
service provision
Limited Spectrum
Sharing
2005
Adaptable, ubiquitous
service provision
Dynamic and Flexible
Spectrum Allocation
2010
28
Main challenges for Reconfigurability
implementation
 Flexible service provision:
• Reconfigurability management
• Policy provision
• Profile management
• Protocol/software download
• Adaptable service deployment
• Open APIs
• Reconfigurable charging models
• Flexible QoS and security schemes
29
Main challenges for Reconfigurability
implementation
Radio resource management:
• Handover management procedures
• Mobility management
• Dynamic and flexible spectrum management
User perspective:
• User requirements
• User interactions with the SDR terminal
• User anonymity and profile management
• Re-configurable and value added service provision
30
Main challenges for Reconfigurability
implementation
 System level issues:
• Generic architectures for flexible service provision and
reconfigurability management
• Network reconfiguration mechanisms and applications
• Hierarchical and decentralized network architectures
• Terminal re-configuration procedures
• Interactions between terminal and network
• Novel signaling mechanisms
• Distributed processing
• Adaptive protocols
• SW downloading and impact on traffic
31
Main challenges for Reconfigurability
implementation
 Enabling technologies:
• Adaptable service provision environments
• Reconfigurability control middleware
• Software download and repository techniques
• APIs definition
• Applications enabling network recofiguration features
• Re-configurable baseband SW architecture
• Re-configurable signal processing algorithms
• Adaptive air-interfaces
• Novel HW-SW co-design methodologies
• Resource management
32
Issues for Reconfigurability
 Requirements analysis from user/operator/service provider/regulator
points of view
 Identification of generic architectures and middleware for the support
of flexible service provision and reconfiguration management
 Identification of protocol adaptability mechanisms
 Identification of protocol/software downloading procedures
 Identification of supporting network/terminal reconfiguration
mechanisms
 Research integration on enabling technologies and identification of
solutions to all bottlenecks
 Identification of technology concepts applicable to reconfigurable
environments, e.g., CORBA (Wireless CORBA), JAVA-RMI, JINI,
(Mobile) Agents etc.
33
Reconfigurability business model
•
Independent software vendors
– Develops implementations for a
particular functionality as defined
by a specification
•
Conformance Provider
Standardisation bodies
1
1..n
1
– Publishes functional specifications
•
Authoritative bodies
– Ascertains conformance of
implementations
•
Reconfigurability providers
– Orchestrates the reconfigurability
process
•
1..n
Specification Provider
1..n
1..n
1..n
0..n
1..n
Reconfigurability Provider
0..n
Implementation Provider
1
Reconfigurability users
– End users
– Network operators
– etc
0..n
Reconfigurability User
34
The reconfigurability process
• Identification of context
– Spatially scope the technological surrounding of the requesting entity by
identifying affected elements in the communication and computing
infrastructure
• Identification of feasible alternative solutions
– Capability exchange and negotiation procedure under a specific policy (e.g.,
maximise system features)
• Decision on solution and respective implementation
– Take into account generic (e.g. user) preferences alongside with strictly
technical considerations (type-checking)
• Physical deployment of solution
– Reserve necessary resources then download and install solution
• Activation of solution
35
SDR Forum – Architecture of CCL/ITRI
SDR software framework
36
SDR Forum – Use case diagram of SDR
core framework
37
Standardisation activities for open service
access
 Parlay. Parlay is an object-oriented API, developed by the homonymous industry forum, that provides
independent software developers access to a selected range of network capabilities, abstracted by the socalled Service Capability Features (SCFs). Currently specified SCFs (in Parlay version 4.0) include
interfaces for call control, retrieval of user location and status, terminal capabilities and user presence and
availability information, content-based charging, policy-based management and others. Security issues
regarding access to these SCFs (e.g., authentication, authorization and access control) are controlled in a
unified way by an entity called the Parlay Framework, which acts as the first contact point for Parlay clients.
Parlay interfaces are independent of particular hardware platforms, operating systems, programming
languages as well as of network technology.
 OSA. OSA (Open Service Access) is a 3GPP specification that provides an API for the particular case of
3G mobile networks. OSA was from its origins largely based on Parlay. Since late 2001 both specifications
are fully aligned and the future versions of both interfaces are jointly developed by 3GPP and the Parlay
group.
 JAIN. JAIN (Java APIs for Integrated Networks) is a set of Java APIs that aim to enable the rapid
development of next generation telecommunications services on top of the Java platform. The JAIN family
of specifications is divided into Protocol APIs¸ which define interfaces to wireline, wireless and IP signalling
protocols (e.g., TCAP, ISUP, MAP, SIP) and Application APIs that specify APIs required for creating enduser services. A Java version of the Parlay APIs, called JAIN Service Provider API (SPA) [10] has been
included in the latter category, together with other APIs that such as the definitions of a server-side service
execution environment, called JSLEE (JAIN Service Logic Execution Environment) as well as of a service
creation environment (SCE).
38
OSA
39
OSA
Application
server
Application
discovery
OSA interface
Open
Service
Architecture
Interface
class
framework
Loc. information
Call control
Service capability server(s)
HLR
CSE
MExE
server
SAT
server
Servers
E.g. Location server
40
OSA - Application Programming Interface
OSA Interface
SCS
‘Gateway’
OSA Interface
SCS
SCS
SCS
Non-standardised
Interfaces
Non-standardised
Interfaces
HLR
CSE
….
Physical entity
Option 1A
‘Gateway’
HLR
CSE
….
Functional entity
Option 1B
41
OSA - Application Programming Interface (2)
OSA Interface
OSA Interface
SCS
SCS
SCS
HLR
CSE
….
SCS
‘Gateway’
Non-standardised
Interfaces
HLR
Option 2
SCS
CSE
….
Option 3
42
Open Services Gateway initiative
43
OSGi mission
With OSGi, high-value services may be dynamically loaded over a wide-area network,
and accessed through a Services Gateway in a home, office, vehicle, or mobile device.
Applications enabled by OSGi include:
Services in the Home:
•Information/Entertainment
•Communication
•Energy Management and Metering Appliance
•Diagnostics and Servicing
•Safety and Security monitoring
•Telemedicine and healthcare monitoring
Services in the Car:
•Vehicle diagnostics
•Emergency assistance
•Mobile commerce
•Navigation
•Location-based services
•Information/entertainment
44
UMTS Service Architecture
45
Mapping of SCFs to Release 2000 Network
Architecture
46
Requirements for Flexible Service Provision in
3G systems and beyond
Flexible business models
Dynamic service registration, deployment
and update by Value Added Service
Providers (VASPs)
Dynamic user registration
Advanced Service discovery - based on
various parameters, e.g.:



Terminal capabilities
User profile and location
Service profile
• Profile interpretation:User,
Terminal, Service, Security
• Identification of network/terminal
capabilities
• Support downloadability
• Support for QoS
• Support for secure service usage
Charging, Accounting and Billing (CAB):


Support of flexible charging/accounting
models
Provision of single bill to end user for all
consumed VASs
47
Basic Requirements for Reconfigurability in 3G
and beyond
Support for flexible business models with novel dynamic services
Dynamic reconfiguration based on profiles (e.g., user, terminal, service),
service provision requirements
Dynamic reconfiguration based on MT/access/network capabilities
Dynamic reconfiguration based on policy provision (charging, QoS etc.)
48
Applications enabling reconfigurability
management
Applications supporting reconfigurability and flexible service
provision:


reconfigurability management/control
adaptability enablers
Applications enhancing network functionality/ capabilities/
interoperability/ management
Applications enhancing/optimising terminal functionality/capabilities
Adaptable Services
49
Business model for flexible service provision through
Service Provision and Reconfigurability Middleware
Provision of portal reference
Portal access control
Business level relationship
for VAS provision
Third Trusted Party/HE-VASP
Domain
User
User
(U)
(U)
Service Provision and
Reconfigurability
Retailer
Platform
(R)
Provider
Value-added
Application/
Service/Application
Service
Provider
Provider
(SAP)
(VASP)
Mobile network operator
Access Provider
Network Access
(AP) Provider
(NAP)
50
Generic Business model for flexible service
provision
1..*
VAS Management Delegation
1..*
0..*
VASP
SPPlatform Operator
1..*
VAS provision agreement
0..*
Subscription
ProfileManagement
0..* OSA client agreement delegation
0..*
Platform_OSA
1..*
OSA_VASP
1..*
OSA management interactions delegation
0..*
Subscription
NetworkOperator
OSA client agreement
1..*
User
0..*
OSA client agreement
1..*
1..*
OSA_VASP_Non
Deleg
OSA Operator
Operator
51
Generic Architecture for Flexible Service
Provision and Reconfiguration Management
VASP
VASs
VASP
VASs
VASP
VASs
APIs
Service Provision and Reconfiguration management
middleware
APIs
UMTS Network
GGSN
LCS
CGF
SGSN
Node B PC
HSS
Node B PC
SGSN
52
Software/Protocol Download to support
Reconfigurability
AR
R
R
R
R
R
R
Physical/Terminal Features Plane
Software/Protocol Downloading
Network Features Plane
Reconfigurability Management Plane
Service Plane
MT
53
Generic Business model for reconfigurability and
flexible service provision
1..*
VAS Management Delegation
0..*
0..*
1..*
0..*
Reconfigurability
0..*
Reconfiguration actions request
0..*
VASP
SP Platform Operator
1..*
Management Platform
Operator
VAS provision agreement
0..*
Subscription
ProfileManagement
Reconfigurability
management
0..* OSA client agreement delegation
0..*
Platform_OSA
1..*
0..*
OSA_VASP
1..*
OSA management interactions delegation
0..*
Subscription
Netw orkOperator
OSA client agreement
1..*
User
0..*
OSA client agreement
1..*
1..*
OSA_VASP_Non
Deleg
OSA Operator
54
Generic Architecture for Downloadable
Adaptable VASs
Service/ application
Stationary part
Adaptability
management
Downloadable part
Interface part
55
Architecture for Flexible Service Provision and
Reconfiguration management
VASP2
VASP1
VASs
Service
provision
platform
VASs
VASP Network
Services
and
Users DB
VASP3
VASM
L4+sys
VASs
ANAI
CAB
L4+sys
UMTS Network
GGSN
LCS
CGF
SGSN
Node B PC
HSS
Node B PC
SGSN
56
Basic Value-Added Service Provision Phases
MS
VAS
Manager
ANAI
L4+
System
CAB
System
VASP
Service Registration
Protocol Download
Configuration
User Registration/Authentication
Terminal classification
Service filtering/Lookup service
VAS selection/activation
VAS download
VAS usage
Configuration
Configuration
Charging records
57
Generic architecture enabling reconfigurability
for flexible service provision
Open
APIs
Reconfiguration Control/
Service Provision Manager
Service Discovery
Services
Service Deployment
Service Profile
Management
User Access Session
User Profiling
Reconfiguration
Manager
Technology independent interfaces
OSA, Parlay, JAIN APIs
API extensions for reconfigurability
(Policy e.g., Charging, QoS)
Network infrastructure
MS
UTRAN
GERA
N
Laptop
WLAN
3G
Core
Networ
k
VAS
P
VAS
P
IP Network
VAS
P
VAS
P
58
Service Registration & Deployment
Open intrerface to VASPs to dynamically register and update their
services
Service profile

Service profile may include:
 service description
 service specific
parameters for execution
 location indication
 estimated service cost
 available versions of same
service
 targeting devices’ minimum
terminal capabilities
 minimum QoS policy required
 associated tariffing policy
Dynamic configuration of metering and classification systems (e.g.,
L4+sys) to monitor IP flows and provide for QoS
Dynamic provisioning of tariffing models and pricing policies to the
Charging/Accounting/Billing
59
Service Discovery
Personalised Service filtering based on
–
terminal capabilities
– user’s service preferences
– user location (for local services provisioning)
– user instructions/inquiry (category, keyword, description, cost)
Terminal capabilities negotiation
–
the CC/PP specification
– the MExE terminal classification
– provision for server-driven negotiation
User profile:
–
–
–
–
–
Basic user identification data (possibly derived from NO databases)
List of favorite/subscribed services
Generic service configuration preferences (e.g. language)
Personal “bookmark” list
Information on user interface personalization
60
MT
CGF/L4
CAB
VASM
VASP
User Login/Authentication
Lookup_Request
Service DB data retrieval
User Preferences retrieval
Service DB content filtering
Lookup_Response
VAS_Selection_Request
VAS_Selection_Response
VAS Downloading
VAS-specific Interactions
VAS_Usage_Data(CDRs, VASDRs)
Usage data processing
User charging/Profit accounting
User Logoff
61
MT
UIMM
VASM
VASDBMM
UDBMM
Lookup_Request
Terminal Capabilities/Location
processing
User_Profile_Request
User Preferences retrieval
Favorite VAS retrieval
User_Profile_Response
Filter_VAS_DB_Request
VAS records filtering
Filter_VAS_DB_Response
LookUp formulation
Lookup_Response
62
Generic architecture enabling reconfigurability for
flexible Charging/Accounting/Billing
Open
APIs
Services
Accounting
Indications
Location-based
Charging
Pricing Policies & Tariffs
Definition
Technology independent interfaces
OSA, Parlay, JAIN APIs
API extensions for reconfigurability
(Policy e.g., Charging, QoS)
Network infrastructure
MS
UTRAN
GERA
N
Laptop
WLAN
3G
Core
Networ
k
VAS
P
VAS
P
IP Network
VAS
P
VAS
P
63
Separation of charges
Transport plane
Service plane
Content plane
64
Advanced Charging Schemes
65
Separation of charges
Transport charges:
Based on attributes such as:
–
–
–
–
–
–
Volume of transferred data
QoS
Duration
Time of day
Location
APN
Provided by CDRs
Service charges:
Based on attributes such as:
– Service specific parameters
– Transport protocol
• TCP
• UDP
– QoS params (DSCP code)
– Application protocol
• http
• ftp
• rtp
Provided by VASDRs
66
Transport billing
CGF
Charging
Billing
CDRs
processing CDRs
(store imsi and user IP address,
production of transport billing
record)
TRANSPORT_BILLING_RECORD
Find transport tariffs and
pricing model, calculate the
charge and store the record
TRANSPORT _BILLING_RECORD_RESPONSE
67
Service billing and accounting
VASM
L4+sys
Charging
Billing
Accounting
VASDRs
Processing VASDRs
(find imsi, production of
service billing record)
SERVICE_BILLING_RECORD
SERVICE_TARIFFS_REQUEST
Create a SERVICE_
TARIFFS_REQUEST
SERVICE_TARIFFS
SERVICE_TARIFFS_RESPONSE
Find service tariffs and pricing
model and calculate the charge
and store the record
SERVICE_BILLING_RECORD_RESPONSE
ACCOUNTING_RECORD
Find service tariffs and
pricing model, calculate the
charge and store the record
VASDRs_response
ACCOUNTING_RECORD_RESPONSE
68
Generic Architecture enabling reconfigurability
based on Location Awareness
Open
APIs
Services
QoS Policy
Provisioning
Network Nodes
Reallocation
Charging/Billing
Service
Provisioning
Media
Conversion
User Notification
Terminal
Reconfiguration
Mobility
Management
Technology independent interfaces
OSA, Parlay, JAIN APIs
API extensions for reconfigurability
(Policy e.g., Charging, QoS)
Network infrastructure
MS
UTRAN
GERA
N
Laptop
WLAN
3G
Core
Networ
k
VAS
P
VAS
P
IP Network
VAS
P
VAS
P
69
L4+ System objectives & characteristics
Application and Content-based QoS traffic control
through DiffServ classification and routing

On a per VAS and per User basis
Traffic measurement on a per flow basis i.e., specific
for each User-Service tuple:


Application/Content based
Volume based
Collect and edit VAS usage records for the CAB
‘Enhanced IP-Router’ transparent to Service and
User
70
L4+System Implementation
L4CABCM
CAB
(VASM)
(VASM)
configure
information
L4+System
Service Access Accounting
VASP
Manager
Reader
L4+
Classifier
Traffic
Meter
F O R W A R D I
IP Flows
N G
ON
(Service Data Packets)
71
Reconfigurability related to the access part
Task: Assure QoS



for wireless Internet terminals
Adapt to application and wireless channel
a priori unknown requirements
Use Protocols, which split wireless and wireline of data transmissions:



Proxies
Boosters
Data Link Protocols and middleware adaptation
Task: downloadable protocols on a re-configurable terminal
Challenges:




Minimize runtime overhead of execution environments
Minimize impact of downloading and re-configuration
Automatic deployment of protocols
APIs
72
Requirements on Mobile Terminal Functionality
RTE Provisioning
VASM Security
Module
Registration
& Login Certificate
IHM
Management
Service
Management
User
Profile
DB
Profile
Management
Terminal
Service
Discovery
LookUp
VAS
DB
Service
Downloading
Downloading
Provision for RTE
Flexible & user-friendly interface for
access to VASs,
Interaction with VASM & VASP,
User registration & authentication with
VASM,
VASP
Profile management,
Capability negotiation with VASM,
Service lookup and Selection,
Secure download
Service execution on terminal.
73
End User Terminal Platform (EUT)
Application Support

Contains the necessary APIs for service
execution
Authentication and Registration
Manager

Service Management Support Component

Controls and manages service provision
procedures
Service Look-Up Manager

Adaptation Component

Deals with low level issues concerning
QoS and protocol downloading
Profile Manager

Manages the access and modification of
Profiles

Layered architecture of
EUT-Platform
Responsible for the software
downloading process
Service Management
Application Support
Programming Interface
(MExE APIs, MAs APIs,
Java Standard APIs)
Adaptation Component
(QoS monitoring, Adaptive
protocol downloading)
Manages the Look_Up table
formulation
Software Downloading

Service Management
Support Component
Ensures registration and
authentication processes
Manages the service once recovered
in the terminal component
GUI
Manager
Service
Lookup
Manager
Service
Download
Manager
Authentication
Manager
Service
Management
Security
Manager
Service Management Support Component
Functional modules of Service Management
Support Component
74
Security requirements
VASP :

Restricted access
 Client authentication
User :

Protection of mobile terminal resources
 Protection of his/her private life e.g. “Anonymity” when accessing
VAS
VAS (mobile code) :

Intellectual property rights protection
 Conditions of use
 Run-time tuning and control
75
Mobile code security
Secure software packaging

Classes ciphering
 Rules insertion
 Electronic signature
Use of a secure SIM card to store security parameters provided
during service download
Secure Run-Time machine

Able to open and check the secure software package
 Then run the java classes deciphering them on the fly
Server Side
Client Side
Original
software
Packaged
software
Download
Packaging
Write on SIM card
Secret Key Generated
76
Technology used for the implementation of
Security components
VASP side

Java (Servlets)
 Web server (Tomcat)
End-user side

Java application
 RSA based signature
–
Code authentication
– Code integrity check

Symmetric Ciphering
algorithm (DES)
 Electronic signing
 SSL- like Protocol
 Linux

DES
–

On the fly classes
deciphering
Linux
VASM side

Java (Servlets)
 Web server (Tomcat)

Certificate generation
 Electronic signing
 Linux
77
Downloading Mobile Code
Secret
Key
Stored
Packaged
software
Decrease counters
Right
expires
Check SIM card
Rules System
Deciphering module
Mobivas Software Loader
Interrupt
Load
Functions
Application
78
Mobivas security architecture
Implementation of SPKI in MOBIVAS :
MT  VASM :
 SPKI certificate delivery in the Registration
procedure
 Authentication with SPKI certificate in the login
procedure
MT  VASP :
VASM
Users
Database
 Check the user access rights with SPKI
certificate during the VAS selection procedure
MT  MT :
End-User
 SPKI certificate delegation
VASP
Rules
Production
Java programs
repository
HTTP
Internet
Rules Engine
Cipher
Module
Signature
Module
SIM Card
Transmitting Rules
Mobivas & DES key to SIM card
Package
+
Mobivas Mobivas
Class Loader
Package
Transmitting mobile code
79