Service Network, OSA, Parlay, TSG-S 2001.01.___.___ TSG-N/TR45.2.___ 2001.01.___.___ Service Network, OSA, Parlay, Michel Houde Dr.ir. Ard-Jan Moerdijk Strategic Product and System Management PU-Service Capability Servers and Applications Ericsson EuroLab Netherlands B.V. Ard.Jan.Moerdijk@eln.ericsson.se _PA5_

Copyright statement c 2001 Telefonaktiebolaget LM Ericsson. The information contained in this contribution is provided for the sole purpose of promoting discussion within the Technical Specifcation Groups of TIA/3GPP2 and is not binding on Ericsson. Ericsson. reserves the right to add to, amend or withdraw the statements contained herein. The contributor grants a free, irrevocable license to TIA/3GPP2 and its Organizational Partners to incorporate text or other copyrightable material contained in the contribution and any modifications thereof in the creation of TIA/3GPP2 publications; to copyright and sell in Organizational Partner's name any Organizational Partner's standards publication even though it may include portions of the contribution; and at the Organizational Partner's sole discretion to permit others to reproduce in whole or in part such contributions or the resulting Organizational Partner's standards publication. The contributor must also be willing to grant licenses under such contributor copyrights to third parties on reasonable, non-discriminatory terms and conditions, as appropriate. _PA5_

Agenda Service Network Open Service Access OSA’s usage in 3GPP2 Standardization OSA application example _PA5_

3rd generation network Need for speed: higher bit rates (access to) Packet switched technology Separation of connectivity control service Enabling (portable) multi-media services /applications with reduced Time To Market _PA5_

Layered network architecture principles in 3G Defining the open interfaces towards applications to access core network functionalities Applications Service network Services/Applications layer APIs OPEN SERVICE ACCESS WIN (ANSI-41) CAMEL SIP Network specific Call control Session management Mobility management Control layer The layered network architecture in 3G networks is shown here. The access or radio layer is not shown here. There is a clear functional separation between the service network and the core network. The specific functions are listed in the sheet. Core network User data handling Transport Switching Routing User Data Connectivity layer _PA5_

_PA5_

Service Network enabler:OSA OSA: collection of APIs for access to core network functionality OSA further implies: Combinations: Applications by combining Network capabilities Applications combine network capabilities with data not available in network. Opening up of networks for application development technology: Java, CORBA, COM standards: Open APIs for support of innovative 3rd party service provisioning Application convergence (with the right Abstraction) fixed, mobile, IP: OSA is beyond standards committees (i.e., 3GPP2, UMTS) public / enterprise domain Backwards compatibility Allows to generalize PLMN applications (i.e., features) logic, and reuse in the 3G context _PA5_

Open Service Access: Concept Application server Appli cation OSA interface Interface class framework Loc . information Call control Network Capability Gateway ANSI SCM Location AAA Servers(SIP) 41 server NB: The Network Capability Gateway (NCG; 3GPP: Service Capability Server) is a logical entity. It can then either be implemented as a standalone functionality, or the needed functional subset can be collocated with a network entity. _PA5_

Providing the API implementations: Service Capability Servers Raise the abstraction layer Hide network specific protocols Protect core network Act as proxies Examples: Call control (used for “traditional” + IP) User interaction User status / User location Multi-media (IP) Conferencing Terminal Capability QoS management (i.e. policy) Content based charging (Content provider) _PA5_

Providing the infrastructure: OSA application Framework Framework provides controlled access to Service Capabilities authentication of applications (possibly from different domains) authorize access to one or more Service Capabilities Framework enables incorporation of new Service Capabilities enables NCGs (SCSs) from different vendors enables to include non-standardized capabilities, and make them available for (some) applications _PA5_

OSA’s usage in 3GPP2; Figure 3. 1 OSA’s usage in 3GPP2; Figure 3.1.4b Multimedia SIP Services Control Plane _PA5_

OSA’s usage in 3GPP2; Figure 3. 1 OSA’s usage in 3GPP2; Figure 3.1.4b Multimedia SIP Services Control Plane _PA5_

OSA’s usage in 3GPP2 _PA5_

OSA’s usage in 3GPP2 _PA5_

OSA’s usage in 3GPP2 HLR SCP Roaming Signaling Gateway Trunk Service Other Access Networks Roaming Signaling Gateway Trunk Network Service EIR DSI Subscrption Policy . . . Profile Legacy MS Domain Support Rules Application Databases 2 5 6 Network Capability Gateway MAP TIA/EIA-41 14 GSM 25 a b c d e f 27 cdma2000 Access Network Media Access Gateway Gateway PSTN BSC/RNC 31 34 BTS (includes IWF) + PCF 35 39 40 MM FA / Attendant a Border Router 48 45 46 47 IP Mobile Network MSC Station Server Figure 3.4 Legacy MS Domain Support Contro l and Bearer View _PA5_

OSA Standardization: Historical background Parlay: closed community, initiated by British Telecom. Now open. Goal: define API’s that provide enterprises access to network information and allow them to control a range of network capabilities. ETSI SPAN12 (formerly SPAN3): initiators of CSx, mostly for landline JAIN Service Logic Execution Environment: defines a similar concept to OSA 3GPP adopted the Virtual Home Environment concept, using Open Service Access as a tool _PA5_

OSA Standardization: harmonization Ongoing effort to harmonize Parlay and UMTS OSA, joint effort with ETSI SPAN12 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 continuous feedback and alignment with Parlay group ensure alignment with JAIN initiative and OMG _PA5_

OSA application… just a sample _PA5_

Recall Converged Service infrastructure, even within the Enterprise domain ! Same application accessed from public and enterprise domain Flexibility in application ownership ! Enterprise applications using public domain capabilities Workforce organization (typically data from an enterprise domain), using the positioning/location information of the network. _PA5_

Leads to wide variety of OSA applications combinations of capabilities and data different business roles converged service infrastructure gives different kind of applications: HE: Home Environment _PA5_

Location service for private subscribers Bank services Location services Leisure News _PA5_

Location service for private subscribers Directions From To Default Now we have moved money to our cash card. The nest problem is get cash from that card and for that we need to find an automatic teller machine - an ATM. Hopefully using a language I know. For this we use a local location service, which include positioning and giving you a map on the terminal and if you want with certain things pointed out. Positioning is one of the applications least people in our industry seams to be argue against being important as a service. Our strong believe is that he success comes from including positioning a component in services to refine them more. To give me more specific information to the end-user. ATM Bank Police _PA5_

Location service for private subscribers _PA5_

HE location application; interaction flow before traffic Application registers and authenticates towards FW FW checks Service Level Agreement, and starts suitable application UserLocationManager, returns reference to application Application Application Server OSA Interface FW User Location SCS CC/UI SCS WAP GW Workforce organization (typically data from an enterprise domain), using the positioning/location information of the network. PLMN PSTN (CS) (ANSI41 CS) _PA5_

HE location application; interaction flow during traffic Terminal interacts via WAP with application, selects ATM location option application invokes ‘userLocationRequest’ method, gets response application produces suitable map (including term.caps from WAP GW), provides this to terminal Application Application Server OSA Interface FW User Location SCS CC/UI SCS WAP GW Workforce organization (typically data from an enterprise domain), using the positioning/location information of the network. PLMN PSTN (CS) (ANSI41 CS) _PA5_

1- Adopt Open Service Access concept for reference point 8 Recommendations 1- Adopt Open Service Access concept for reference point 8 Workforce organization (typically data from an enterprise domain), using the positioning/location information of the network. _PA5_

OSA’s usage in 3GPP2; Figure 3. 1 OSA’s usage in 3GPP2; Figure 3.1.4b Multimedia SIP Services Control Plane _PA5_

Recommendations 2- Add Network Capability Gateway, between the Service Application(s) and the SCP (i.e., for access to legacy features) ------ NB: The Network Capability Gateway (NCG; 3GPP: Service Capability Server) is a logical entity. It can then either be implemented as a standalone functionality, or the needed functional subset can be collocated with a network entity. ------ 3- Add a reference point between the NCG and the MSC server Workforce organization (typically data from an enterprise domain), using the positioning/location information of the network. _PA5_

OSA’s usage in 3GPP2 HLR SCP Roaming Signaling Gateway Trunk Service Other Access Networks Roaming Signaling Gateway Trunk Network Service EIR DSI Subscrption Policy . . . Profile Legacy MS Domain Support Rules Application Databases 2 5 6 Network Capability Gateway MAP TIA/EIA-41 14 GSM 25 a b c d e f 27 cdma2000 Access Network Media Access Gateway Gateway PSTN BSC/RNC 31 34 BTS (includes IWF) + PCF 35 39 40 MM FA / Attendant a Border Router 48 45 46 47 IP Mobile Network MSC Station Server Figure 3.4 Legacy MS Domain Support Contro l and Bearer View _PA5_

Background material Workforce organization (typically data from an enterprise domain), using the positioning/location information of the network. _PA5_

Parlay API example : IparlayApp : IparlayApp : IparlayCall PartyA : Iparlay PartyB : Iparlay : IparlayCall Logic Call ControlManager CallLeg CallLeg 1: new() 2: createCall() 3: new() 4: routeReq() 5: new() 6: routeRes() 7: 'forward event' 8: routeReq() 9: new() 10: routeRes() 11: 'forward event' _PA5_

Standardization of Parlay 3GPP R99 (CN5): Adoption of a subset of Parlay 2.1 APIs : TS 23.127 +TS 29.198 Framework: Service View Generic Call Control User Interaction (also for WAP push) CAMEL based Mobility Management Terminal Capabilities (based on WAP UAProf) Data Session (GPRS charging) Informative mapping to network protocols: TR 29.998 ETSI SPAN 12 (former SPAN3): adoption of all Parlay 2.1 APIs, base for ETSI, 3GPP and ITU _PA5_