Parlay/OSA: open APIs for service development

Slides:



Advertisements
Similar presentations
SIP, Presence and Instant Messaging
Advertisements

SIP and Instant Messaging. SIP Summit SIP and Instant Messaging What Does Presence Have to Do With SIP? How to Deliver.
Oct, 26 th, 2010 OGF 30, NSI-WG: Network Service Interface working group Web Services Overview Web Services for NSI protocol implementation
Kickoff Meeting Introduction to Parlay 31 March 2005 Introduction to Parlay/OSA Michel Genette (Alcatel) Member, Parlay Board of Directors.
Geneva, Switzerland, 17 October 2011 ITU Workshop on Service Delivery Platforms (SDP) for Telecommunication Ecosystems: from todays realities to requirements.
Overview of Web Services
1 Requirements Catalog Scott A. Moseley Farbum Scotus.
Presents H.323 Forum ETSI TIPHON Presented by: Richard Brennan - Telxxis LLC Vice-Chair ETSI-TIPHON.
PARLAY and the 3GPP Open Service Architecture TINA ideas and principles Dr. Lucas Klostermann chairman 3GPP-CN5 system manager PU SCSA
IMS Workshop- Summary James Rafferty August
Fixed Mobile Convergence T Research Seminar on Telecommunications Business Johanna Heinonen.
© 2003 Open Mobile Alliance Ltd. All Rights Reserved. Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document.
Introduction to Service-Oriented Architecture. Outline Definition Features Examples of SOA Web Service Standards Example Pros and Cons Integration with.
Ch 12 Distributed Systems Architectures
“Securing IP Multimedia Subsystem (IMS) infrastructures …,” M. Tsagkaropoulos UNIVERSITY OF PATRAS Department of Electrical & Computer Engineering Wireless.
Support Services & IP Multimedia Subsystem (IMS)
Network Resource Gateway (NRG) Application DevelopmentDSLD Unit Florin van Slingerland Rev A Slide 1 Application Development Presentation/Course Teaser.
World Class Standards WG8 presentation of current Subscription Management Activities TISPAN WG8 – 3GPP SA#5 Joint meeting Sophia Antipolis, May14th - 15.
International Telecommunication Union Geneva, 9(pm)-10 February 2009 ITU-T Security Standardization on Mobile Web Services Lee, Jae Seung Special Fellow,
An Operators Input for oneM2M Baseline  Group name: TP#2/WG1  Source: DTAG, Vodafone Group  Meeting Date:  Agenda Item: WG1 agenda item.
Parlay Emergency Telecommunications Service (ETS) Working Group Ravi Jain, John-Luc Bakker, Ken Erney Frank Suraci & Vernon Mosley
Web Services based e-Commerce System Sandy Liu Jodrey School of Computer Science Acadia University July, 2002.
Developing Convergent Network Applications Doug Tucker, CTO, Ubiquity VOIP Developers Conference Thu 2:30p – 3:15p.
1 Multimedia Services Service provider Service client Service registry Publish Find/discovery Bind Multimedia Services Framework and architecture.
Open Service Access(OSA) Application Programming Interface(API) Framework ZTE (USA)
Web Services. Abstract  Web Services is a technology applicable for computationally distributed problems, including access to large databases What other.
An Overview of CORBA and Parlay/OSA APIs ZTE (USA)
Service Network, OSA, Parlay,
WG2 – Enabling Technologies Status of white paper Olaf Droegehorn, Klaus David University of Kassel Chair for Communication Technology (ComTec)
1 G52IWS: Web Services Chris Greenhalgh. 2 Contents The World Wide Web Web Services example scenario Motivations Basic Operational Model Supporting standards.
© 2004 IBM Corporation ICSOC2004 Panel Discussion: Grid Systems: What is needed from web service standards? Jeffrey Frey IBM.
France Télécom R&D – February 5th 2003 Internet Telephony Conference – Miami, Florida Bridging the Chasm Between Legacy and Next-Generation Networks Internet.
IMS developments in 3GPP
A Scalable SIP-based Architecture to Offer Value-added Services in a Converged IN/IP Environment F.S.Salloum, Tasos Dagiuklas, Maria Skoura 16 January.
Introduction to Web Services Presented by Sarath Chandra Dorbala.
Page 1TTT - May 12, GPP IMS Standardization Update Bell Labs Innovations Lucent Technologies Room 9C Lucent Ln. Naperville, IL E Mail.
Services – a perspective on building applications Richard Swale ETSI TIPHON Wg1 chair VoIP Technologist BTexaCT ITU Workshop on IP Networking and Mediacom.
By Jeremy Burdette & Daniel Gottlieb. It is an architecture It is not a technology May not fit all businesses “Service” doesn’t mean Web Service It is.
January 23-26, 2007 Ft. Lauderdale, Florida Services Transformation New Approaches to Delivering Blended Services Over IP Networks Keith Chappell Alcatel-Lucent.
Name of Presentation Red Hat Presenter RED HAT Developer conference Brno 2009 Mobicents/JBCP Pavel Slegr.
Service Control Using SIP in 3GPP’s IP Multimedia Subsystem (IMS) Xin Chen Fujitsu Laboratories of Europe LTD
World Class Standards 1 ETSI/Parlay and 3GPP Correspondence  Parlay 3 published as ETSI ES  Aligned with 3GPP TS Rel-4  Parlay 4 published.
Introduction to Web Services
Unified Communication (UC) -A new topic in CCSA
ETSI–3GPP NGN ACTIVITIES
ETSI–3GPP NGN ACTIVITIES
Sabri Kızanlık Ural Emekçi
China Communications Standards Association ZTE Corporation, P.R. China
Integration of Network Services Interface version 2 with the JUNOS Space SDK
Web Services CO5027.
High Interest Subject: Service Platforms and Interworking of Services
Overview of Web Services
Wsdl.
Parlay/OSA: an open API for service development
GPRS GPRS stands for General Packet Radio System. GPRS provides packet radio access for mobile Global System for Mobile Communications (GSM) and time-division.
Inventory of Distributed Computing Concepts and Web services
Parlay Application Servers providing Robust Scalable Services
“That’s P-a-r-l-a-y not P-a-r-l-e-z!” Richard Kett BT ACE
IMS & Wireline to Wireless Convergence
Arve Meisingset WP3/10 chairman Telenor R&D, Norway
OSA Overview and J2EE Implementation
IP and NGN Projects in ITU-T Jean-Yves Cochennec France Telecom SG13 Vice Chair Workshop on Satellites in IP and Multimedia - Geneva, 9-11 December 2002.
Web Application Server 2001/3/27 Kang, Seungwoo. Web Application Server A class of middleware Speeding application development Strategic platform for.
ETSI Protocol and Testing Competence Centre (PTCC)
The Anatomy and The Physiology of the Grid
Software interoperability in the NGN Service layer
Document Management Policy
JAIN FOR MAP PROJECT GROUP: Maurizio Bonuccelli Piero Lauri
Hans, KIM TTA Release approach and CJK requirements Hans, KIM TTA
Distributed Systems Architectures
Presentation transcript:

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

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

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

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

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

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

OSA/Parlay Standardisation OSA specification and standardisation is a joint effort by the following: - 3GPP CT5 - 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/osa.htm

OSA/Parlay Standardisation #2 JWG meets 4 times/year: 2 with 3GPP 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 3GPP CT WGs, 5-8 Feb 2007 Using 3GPP working methods, Tdoc numbering, & MCC support Next meeting invite and Tdocs: http://www.3gpp.org/ftp/tsg_ct/WG5_osa_ex-CN5/TSGC5_37_SophiaAntipolis/Docs/

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

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

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

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

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

Choices, Choices OSA/Parlay full API: Parlay X CORBA IDL specification Web Services technologies J2SE API specification J2EE API specification Parlay X Abstraction, simplified interfaces Web Services only

Parlay/OSA Terminology: SCSs and SCFs - The Parlay/OSA Gateway consists of several Service Capability Servers (SCS): functional entities that provide Parlay/OSA interfaces towards applications. Interface SCF - 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. SCS - The Parlay/OSA SCFs are specified in terms of interface classes and their methods

OSA: Framework + A Set Of SCFs Application server Application OSA API interface class User Call control framework Location Service Capability Servers Not standardized OSA Internal API WGW HLR CSE Servers WPP 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

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

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

OSA/Parlay APIs Call Control Messaging Generic Location & User Status 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

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

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 The Real-Time Enterprise (Gartner) Web Services is a key software development technology: Number of Developers Parlay-X millions Parlay/OSA thousands INAP, SIP thousand Expressive Power 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

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 pre-paid 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 ‘call-me’ button on a web page.

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 3rd 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

Parlay and Parlay X

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

Web Services Technologies ParlayX 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

Parlay X APIs Call Control Short Messaging 3rd 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 QoS

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

Specifications 3GPP ETSI Description TS 22.127 (Rel-4, 5, 6,7) EG 201 988 (4 parts) OSA Requirements 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) OSA Mapping Reports TR 102 397 Parlay X Mapping

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/Overview.html 3GPP CT5 specifications: http://www.3gpp.org/ftp/Specs/html-info/TSG-WG--C5.htm The Parlay Group http://www.parlay.org

Web Services Useful Links Basic Web Services information/tutorials: http://www-128.ibm.com/developerworks/webservices/newto/websvc.html http://www.w3schools.com/soap/default.asp http://www.w3schools.com/wsdl/default.asp W3C WSDL 1.1: http://www.w3.org/TR/wsdl SOAP: http://www.w3.org/2000/xp/Group/ WS-I WS-I Basic Profile: http://www.ws-i.org/deliverables/workinggroup.aspx?wg=basicprofile OASIS WS Security: http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wss UDDI: http://www.uddi.org/

3GPP – 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 3GPP Part 4-5: No Conference Call Control in 3GPP Part 6: No User Location Emergency or User Binding interfaces in 3GPP Part 9: Not in 3GPP Part 10: Not in 3GPP Part 14: Agent Presence interface not in 3GPP

Thank you!