Transcript About OSA - Docbox

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
1
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
2
What is OSA?
• A mediator API between Telecom
networks and Operator or 3rd
Party applications
• Secure interface between
Network Operators and
Application Servers.
Application Server/
Applications
OSA
API
• Open standards (specified by
the Parlay Group, ETSI and
3GPP).
• Raises programming abstraction
level and allows multi-network
applications.
Operator’s
(Multi-) Network
infrastructure
5
Bringing Telecoms and IT Together
Addressing the needs of multiple
customer groups
Wide Range of Applications
The Parlay/OSA API
Developed using IT
technology and tools,
using the power of the
network
Developed by Operators,
Independent Software Vendors,
Enterprises and System Integrators
Common Network Capabilities
Abstract the functions
of the network, and
simplify development
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
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 3GPP 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:
- 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
9
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/
10
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
11
OSA and IMS
OSA is one of the service environments defined in IMS
12
OSA and IMS:
Bridging multiple domains
3rd 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
SS7, MM7..
CS Domain
Operator SIP AS
ISC
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, WiFi – Circuit switched, SIP
15
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
16
Choices, Choices
• OSA/Parlay full API:
–
–
–
–
CORBA IDL specification
Web Services technologies
J2SE API specification
J2EE 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
Enterprise
Operator
4
1
2
2
Framework
Call
Control
Mobility
3
etc
Registered Services
- Application subscription
to 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 3GPP 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 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
28
Parlay and Parlay X
29
Web Services
Web Service Registry
UDDI
Discovery Point
Find
Web Service
Requester
Application
Policy Publishing
Publish
Web Service Provider
Bind
Access
Manage
Binding Point
Policy Negotiation
Access Point
Policy Enforcement
Operational Point
30
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
31
Parlay X APIs
• Call Control
•
– 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
32
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
33
Specifications
3GPP
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
• 3GPP CT5 specifications:
– http://www.3gpp.org/ftp/Specs/html-info/TSG-WG-C5.htm
• The Parlay Group
– http://www.parlay.org
35
Web Services Useful Links
• Basic Web Services information/tutorials:
– http://www128.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.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
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
37
Thank you!
38