PARLAY and the 3GPP Open Service Architecture TINA ideas and principles Dr. Lucas Klostermann chairman 3GPP-CN5 system manager PU SCSA

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

Parlay and UMTS Open Service Architecture; Migration and Convergence within public domain

UMTS OSA; Convergence with Enterprise domain Same application accessed from public and enterprise domain Flexibility in application ownership !

UMTS OSA; Convergence with Enterprise domain Same application accessed from public and enterprise domain Flexibility in application ownership ! Enterprise applications using public domain capabilities

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

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)

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/OSA details 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/OSA enterprise operator 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 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...