Parlay OSA open APIs for service development Damian O Neill

Parlay/OSA: open APIs for service development Damian O’Neill, Chair 3 GPP CT 5 Ultan Mulligan, ETSI PTCC Acknowledgements: Chelo Abarca, RIM, Andy Bennett, Lucent, Ard-Jan Moerdijk, Ericsson, Musa Unmehopa, Lucent Jeff Popoff, Redknee, Marc Leclerc, Ericsson 1

Outline 1 - What is OSA/Parlay? 2 - OSA in 3 GPP and IMS 3 - Under the hood - Framework and SCFs - Parlay X Web Services 4 - Reference 2

What is OSA? • A mediator API between Telecom networks and Operator or 3 rd Party applications • Secure interface between Network Operators and Application Servers. Application Server/ Applications OSA API • Open standards (specified by the Parlay Group, ETSI and 3 GPP). • Raises programming abstraction level and allows multi-network applications. Operator’s (Multi-) Network infrastructure 5

Bringing Telecoms and IT Together Developed by Operators, Independent Software Vendors, Enterprises and System Integrators Developed using IT technology and tools, using the power of the network The Parlay/OSA API Addressing the needs of multiple customer groups Wide Range of Applications Common Network Abstract the functions of the network, and Capabilities simplify development Fixed, Mobile, 3 G, Wi-Fi Open standard API, created by ETSI, Parlay and 3 GPP Supporting the same services on multiple networks reduces operating costs, eases migration and increases market share 6

OSA/Parlay Scenario Other Network Operator / MVNOs Internal Applications Network Operator Parlay/OSA SCS Parlay SMS ASP Parlay MMS WAP ASR/TTS MPC Signaling & Control Corporate Applications Corporate Database Enterprise Access Networks 7

Outline 1 - What is OSA/Parlay? 2 - OSA in 3 GPP and IMS 3 - Under the hood - Framework and SCFs - Parlay X Web Services 4 - Reference 8

OSA/Parlay Standardisation OSA specification and standardisation is a joint effort by the following: - 3 GPP CT 5 - ETSI TISPAN OSA Project - The Parlay Group The objective is to have a single API for the whole developer community OSA = Parlay - All meetings are joint meetings (Joint Working Group) -The joint work is based on a common (UML) model http: //docbox. etsi. org/tispan/open/osa. htm 9

OSA/Parlay Standardisation #2 JWG meets 4 times/year: 2 with 3 GPP CT WGs, 2 with Parlay Group, c. 20 delegates & 100 Tdocs/meeting Next meeting: 23 -26 October 2006, at ETSI Following meeting co-located with 3 GPP CT WGs, 5 -8 Feb 2007 Using 3 GPP working methods, Tdoc numbering, & MCC support Next meeting invite and Tdocs: http: //www. 3 gpp. org/ftp/tsg_ct/WG 5_osa_ex-CN 5/TSGC 5_37_Sophia. Antipolis/Docs/ 10

3 GPP 2 And The Joint Working Group • 3 GPP 2 have adopted OSA/Parlay • No separate specifications – 3 GPP 2 requirements brought to JWG – 3 GPP 2 differences listed in annex to 3 GPP specs – Only scope/references differences to date 11

OSA and IMS OSA is one of the service environments defined in IMS 12

OSA and IMS: Bridging multiple domains 3 rd party Applications + Content Parlay/OSA Applications + Content Web Services Parlay X Unprotected Applications + Content Protected Web Service GW Walled garden Parlay/OSA GW IN Video + Messaging Group Management Presence + Applications Multimedia Applications SIP AS Vendor B Service Layer SS 7, MM 7. . CS Domain ISC Operator SIP AS ISC IMS Core Network 13

OSA Parlay/Parlay-X Proposition SDP IN Enhancement or SCP Replacement Convergence and Migration to IP (Service Delivery Platform) Web Services Network Integration Network API OSA Parlay/Parlay-X Gateways Fixed, Mobile, Wi. Fi – Circuit switched, SIP 15

Outline 1 - What is OSA/Parlay? 2 - OSA in 3 GPP and IMS 3 - Under the hood - Framework and SCFs - Parlay X Web Services 4 - Reference 16

Choices, Choices • OSA/Parlay full API: – – CORBA IDL specification Web Services technologies J 2 SE API specification J 2 EE API specification • Parlay X – Abstraction, simplified interfaces – Web Services only 17

Parlay/OSA Terminology: SCSs and SCFs Interface SCF SCS - The Parlay/OSA Gateway consists of several Service Capability Servers (SCS): functional entities that provide Parlay/OSA interfaces towards applications. - Each SCS is seen by applications as one or more Service Capability Features (SCF): abstractions of the functionality offered by the network, accessible via the Parlay/OSA API. - The Parlay/OSA SCFs are specified in terms of interface classes and their methods 18

OSA: Framework + A Set Of SCFs Application server Application OSA API framework User Call control Service Capability Servers Location interface class Not standardized OSA Internal API HLR CSE WGW WPP Servers E. g. Location server Billing server One of the Parlay/OSA SCSs is called the Parlay/OSA Framework, and is always present, one per network 20

The Parlay/OSA Framework - control of access to the network - integrity management - discovery of network functionality Client Application 1 Enterprise Operator 4 2 2 Framework Call Control Mobility - Application subscription to services 3 etc Registered Services - SCF registration - support of multi-domain 21

Framework Features • Authentication • Load & Fault Management • Event Notification • Service Agreement Management • Grouped Contract Management • SCF Management – Registration – Discovery – Factory 23

OSA/Parlay APIs • Call Control – Generic – Multi-Party – Conference – Multi-media • User Interaction • Policy Management • Charging • Account Management • • Messaging Location & User Status Presence & Availability Connectivity Management Terminal Capabilities Data Session Control Service Broker 24

Outline 1 - What is OSA/Parlay? 2 - OSA in 3 GPP and IMS 3 - Under the hood - Framework and SCFs - Parlay X Web Services 4 - Reference 25

The Motivation for Parlay X: Web Services for Telecom • There is a requirement to publish the capabilities of the network for software developers • There is a demand for enterprise applications to exploit the capabilities of the telecom network Number of Developers Parlay-X millions Parlay/OSA thousands INAP, SIP thousand Expressive Power – The Real-Time Enterprise (Gartner) • Web Services is a key software development technology: • • Parlay-X defines a set of easy-to-use Web Services, which provide simple and high level access to widely used telecommunications functions Third Party Call Control, Network Initiated Third Party Call Control, SMS, Multimedia Messaging, Payment, Account Management, User Status, User Location 26

The OSA/Parlay APIs Name Description Usage OSA/Parlay Rich set of telecom APIs, for use in CORBA (C, C++), Java and web services environments. Several hundred methods. Suitable for use by professional software developers. Suitable for developing a prepaid application. Parlay-X Web Services Set of high-level, simple to use telecom APIs, for use in a Web Services environment. 16 interfaces. Suitable for use by web developers. Designed for use with an Integrated Development Environment (IDE). Suitable for developing a ‘callme’ button on a web page. 27

Parlay Web Services • Defines a set of business models for using Web Services in a telecom environment. – Mobile Operator Cross Network Access – Network Operator and 3 rd Party Integration – Enterprise Application Extension • Open Standard key to interoperability • Leading to: – Application Deployment Infrastructure for Parlay Web Services – Comparison of OSA/Parlay and Web Services Architecture – WSDL Style guide – WSDL version of OSA/Parlay Specifications 28

Parlay and Parlay X 29

Web Services Web Service Registry UDDI Discovery Point Find Web Service Requester Application Policy Publishing Publish Bind Web Service Provider Manage Policy Negotiation Access Point Access Binding Point Policy Enforcement Operational Point 30

Web Services Technologies • Parlay. X and Parlay WS use SOAP over HTTP – – – WSDL used for interface definitions XML Schema for data types WS-Security WS-I Basic Profile compliance required Links to these specifications at the end 31

Parlay X APIs • Call Control • – 3 rd Party Call • – Call Notification • – Call Handling • – Audio Call • – Multimedia Conference • • Address List Management • • Presence • • Message Broadcast • • • Short Messaging Multimedia Messaging Location & User Status Presence & Availability Connectivity Management Terminal Status Terminal Location Payment Account Management Geocoding Application Driven Qo. S 32

Outline 1 - What is OSA/Parlay? 2 - OSA in 3 GPP and IMS 3 - Under the hood - Framework and SCFs - Parlay X Web Services 4 - Reference 33

Specifications 3 GPP ETSI Description TS 22. 127 (Rel-4, 5, 6, 7) EG 201 988 (4 parts) TS 23. 127 (Rel-4, 5) - VHE/OSA Architecture TS 23. 198 (Rel-6, 7) - OSA Architecture TS 29. 198 Rel-4 ES 201 915 OSA API Rel-4, Parlay 3 TS 29. 198 Rel-5 ES 202 915 OSA API Rel-5, Parlay 4 TS 29. 198 Rel-6 ES 203 915 OSA API Rel-6, Parlay 5 TS 29. 198 Rel-7 ES 204 915 OSA API Rel-7, Parlay 6 TS 29. 199 Rel-6 ES 202 391 Parlay X 2 TS 29. 199 Rel-7 ES 202 504 Parlay X 3 TR 29. 998 (Rel-4, 5, 6, 7) - - TR 102 397 OSA Requirements OSA Mapping Reports Parlay X Mapping 34

Links • General information: – http: //portal. etsi. org/docbox/TISPAN/Open/OSA/osa. htm • Overview and links to all OSA Specifications: – http: //portal. etsi. org/docbox/TISPAN/Open/OSA/Overvie w. html • 3 GPP CT 5 specifications: – http: //www. 3 gpp. org/ftp/Specs/html-info/TSG-WG-C 5. htm • The Parlay Group – http: //www. parlay. org 35

Web Services Useful Links • Basic Web Services information/tutorials: – http: //www 128. ibm. com/developerworks/webservices/newto/websvc. html – http: //www. w 3 schools. com/soap/default. asp – http: //www. w 3 schools. com/wsdl/default. asp • W 3 C – WSDL 1. 1: http: //www. w 3. org/TR/wsdl – SOAP: http: //www. w 3. org/2000/xp/Group/ • WS-I – WS-I Basic Profile: http: //www. wsi. org/deliverables/workinggroup. aspx? wg=basicprofile • OASIS – WS Security: http: //www. oasisopen. org/committees/tc_home. php? wg_abbrev=wss – UDDI: http: //www. uddi. org/ 36

3 GPP – ETSI Differences • TS 29. 199 Parlay X: No Differences • TS 29. 198 OSA/Parlay base APIs – Part 3 Framework: No Framework to Enterprise Operator interfaces in 3 GPP – Part 4 -5: No Conference Call Control in 3 GPP – Part 6: No User Location Emergency or User Binding interfaces in 3 GPP – Part 9: Not in 3 GPP – Part 10: Not in 3 GPP – Part 14: Agent Presence interface not in 3 GPP 37

Thank you! 38