umts open service architecture
DESCRIPTION
PARLAY and the 3GPP Open Service Architecture TINA ideas and principles Dr. Lucas Klostermann chairman 3GPP-CN5 system manager PU SCSA [email protected]. UMTS Open Service Architecture. Abstraction, opening the network for application development It’s all about combinations - PowerPoint PPT PresentationTRANSCRIPT
PARLAY and the 3GPP Open Service ArchitectureTINA ideas and principles
Dr. Lucas Klostermann chairman 3GPP-CN5
system manager PU SCSA
FutureMulti-service network
Access, Transport & Switching Networks
TodaySingle-service networks
Services
Ce
llula
r M
obile
Third-generation network structureThird-generation network structure
Connectivity/Connectivity/Backbone NetworkBackbone Network
Service Network
Access NetworksMGWMGWMGWMGW
MGWMGW MGWMGW
S
S S
SD
ata/
IP N
etw
ork
s
PL
MN
PS
TN
/IS
DN
Ce
llula
r M
obile
CA
TV
ContentContent
framework Loc. information Call control
Service capability server(s)
Interfaceclass
OSA interface
OpenService
Architecture
discovery Application
Applicationserver
HLR CSE Msg.server
WAPserver
serverSIP
UMTS Open Service Architecture• Abstraction, opening the network for application development
• It’s all about combinations – applications combine different network capabilities
– applications combine network capabilities with data not available in network
• Application convergence– fixed/mobile/IP migration and convergence
– application convergence/integration between public and enterprise domain
PLMN(GSM/UMTS CS)
PSTN/ISDN (CS) IP Multi-Media (PS)
Capability Server(s)(including interface classes)
Application
Application Server
Application
Application Server
Application
Application Server
OSA Interface providing open API’s to Applications
Capability Server(s)(including interface classes)
Capability Server(s)(including interface classes)
Parlay and UMTS Open Service Architecture;Migration and Convergence within public domain
PLMN(GSM/UMTS CS)
PSTN/ISDN (CS) ENTERPRISE
Capability Server(s)(including interface classes)
OSA Interface providing open API’s to Applications
Capability Server(s)(including interface classes)
Capability Server(s)(including interface classes)
Application
Application Server
UMTS OSA; Convergence with Enterprise domain
• Same application accessed from public and
enterprise domain
Flexibility in application ownership !
PLMN(GSM/UMTS CS)
PSTN/ISDN (CS) ENTERPRISE
Capability Server(s)(including interface classes)
Application
Application Server
OSA Interface providing open API’s to Applications
Capability Server(s)(including interface classes)
Capability Server(s)(including interface classes)
UMTS OSA; Convergence with Enterprise domain
• Same application accessed from public and
enterprise domain
Flexibility in application ownership !
• Enterprise applications using public domain capabilities
framework Loc. information Call control
Service capability server(s)
Interfaceclass
OSA interface
OpenService
Architecture
discovery Application
Applicationserver
HLR CSE Msg.server
WAPserver
serverSIP
Openness; the crucial role of the OSA Framework• Framework provides controlled access to Service Capabilities
– authentication of applications (possibly from different domains)
– authorize access to one or more Service Capabilities (SLA!)
• Framework enables incorporation of new Service Capabilities
– enables to include non-standardized capabilities, and make them available
for (some) applications
– enables SCS’s from different vendors
f r a m e w o r k L o c . i n f o r m a t i o n C a l l c o n t r o l
H L R C S E M s g .s e r v e r
W A Ps e r v e r
s e r v e rS I P
S e r v i c e c a p a b i l i t y s e r v e r ( s )
I n t e r f a c ec l a s s
O S A i n t e r f a c e
O S A i n t e r f a c eO p e n
S e r v i c eA r c h i t e c t u r e
d i s c o v e r y
J - A S
E r i c s s o n A p p l i c a t i o n s N o n - E r i c s s o n a p p l i c a t i o n s ( p o s s i b l y p a r t n e r s )
P a r l a y A P Ie x t e n s i o n s ?
P a r l a y A P Ip o s s i b l y e x t e n s i o n s
Openness; API’s bridging IT and telecoms world • flexibility in application development
– applications by Ericsson, by partners, or without Ericsson involvement
– applications using only API standards based, some use extensions used within operator domain, some use extensions used by SCS vendor
• flexibility in business scenarios (ownership and location of applications)
f r a m e w o r k L o c . i n f o r m a t i o n C a l l c o n t r o lS e r v i c e c a p a b i l i t y s e r v e r ( s )
I n t e r f a c ec l a s s
O S A i n t e r f a c e
O S A i n t e r f a c eO p e n
S e r v i c eA r c h i t e c t u r e
d i s c o v e r y
J - A S
H E - V A S P A p p l i c a t i o n s V A S P A p p l i c a t i o n s
P a r l a y / O S A. A P I
P a r l a y / O S A A P Ip o s s i b l y e x t e n s i o n s
VHE and OSA; subscriber ownership and openness • Business model of UMTS VHE (3GPP)
– Home Environment in control; HE owns subscriber
– Home Environment VAS-provider helps HE to offer service portfolio
– HE-VASP has relationship with HE, but not with subscribers
• Possible with OSA R99 already, but more explicit support in R00
The Framework; main TINA influence on Parlay/OSAdetails• Trust and Security Management
– initial interface
– authentication interface
– access interface
• Service Discovery
• Service Registration
• Integrity Management (less stable)
– load management
– fault management
– heartbeat management
• Service Subscription
The Framework; main TINA influence on Parlay/OSAenterprise operator
Enterprise Operator (In the roleof Service Subscriber)
Framework (In the roleof Service Retailer)
Client Application (In the role ofUser or Consumer of Services)
Signs contract about service usage
Uses service
Authorizes
Services in this context are capabilities!Consumer is not necessarily end-user
• UMTS OSA concept in 3GPP introduced by Ericsson
• Parlay APIs fit well in OSA concept
• Ericsson joined Parlay and strives to harmonize Parlay and
UMTS OSA, joint effort with ETSI SPAN3
• One API standard, one developer community!– 3GPP and ETSI joined forces on UMTS OSA, Parlay as input
– ITU refers to joint 3GPP/ETSI work on API’s
– Parlay call control work being continued jointly with 3GPP/ETSI
OSA/API Standardization bodies and collaboration
OSA/API Standardization Status
• 3GPP Release 99– generic call control, user interaction, user location/status
– call supervision, data session supervision, terminal cap’s
– framework (towards applications, and towards service capabilities)
• Parlay 2.1– call control interfaces (generic, multiparty, multimedia, conference),
– connectivity management
– fully aligned with 3GPP R99 where overlap
• 3GPP Release 2000 and ETSI SPAN3– roughly same scope, so ONE activity, ONE developer community!
– coordination with Parlay 3.0 activities
3GPP Release 2000 - Parlay 3.0 scope• Call Control
– multiparty and multimedia support (SIP)
• User Profile management issues………….– responsibilities SCS/FW/AS
– relationship to HSS
• Charging– E-commerce support, content-based charging
– …
• QoS support enhancement
• Messageing
• ...