Transcript Parlay Call Control and related topics

Introduction to Parlay
Call Control and Related Topics
Ravi Jain and John-Luc Bakker
July 23, 2001
{rjain, jbakker}@telcordia.com
© 2001, Telcordia Technologies, Inc.
An SAIC Company
Overview
 Introduction
 Parlay Services and Working Groups (WG)
 Parlay Call Control
 Alignment of Call Control APIs: ETSI, JAIN, OSA, ...
 Mapping an API to a Protocol
 Conclusion
Jain/Bakker – 2
Parlay in the network
Parlay Applications
Fire
wall
Application
Server
Enterprise
Domain
Hosted Application
Server
Intranet
Internet
The Parlay APIs
Service
Provider
Domain
Router
Network
Elements
Managed IP
network
Network
Security
Boundary
Parlay
Parlay
Gateway
Gateway
Network
Elements
Network
Elements
SCP
Mobile
Network
HLR
PSTN
Jain/Bakker – 3
Where Parlay Is Going
 Version 3.0 Specification Release - Fall 2001
 Interop Testing and Trials
– EURESCOM P1110 Project
– AT&T Trial Activity
 Symposiums and Commercial Sponsored Events
– IBC: Next Gen Service Creation, Barcelona, 26-27 June
– IIR: IP-PSTN Network Convergence, Cannes, 20-21 Sept
– pulver.com: Open Network APIs Event, San Jose, 29-30 October
 General Meetings
– Munich 11-13 September 2001
– Hong Kong 29-31 January 2002
 Parlay 4 - Planning Has Begun; Time For You to Join
Jain/Bakker – 4
Parlay APIs - Technical View
 Framework Interfaces: Common functions required to access
network functionality in a secure, manageable manner
– Authentication, Authorization, Discovery, Integrity Mgmt,
Service Registration, OAM&P Functions
 Service Interfaces: Packaged sets of network functionality
offered in a manner abstracted from the underlying network
details
– Call Control
– Messaging
– Mobility
– Presence and Availability
– Content Based Charging
– Policy Management
Jain/Bakker – 5
Parlay Working Groups
 Parlay Activities Are Organized via Working Groups; These
Groups Perform the Work of Specification Creation and Also
Perform Other Work As Required by the Board of Directors
 The Chair of Each Working Group Automatically Becomes a
Member of the Technical Advisory Committee (TAC) Which Is
Chaired by Julian Richards (Ulticom)
 Working Groups Are Chartered by the Parlay Board of Directors,
Based Upon an Agreed Task Definition, Deliverable Set, and
Schedule
Jain/Bakker – 6
Policy Management WG
 Task: Define Parlay Policy Management APIs, and to Manage
Policy Domains Within the Network That Are
– (1) Independent of Network Architectures, and
– (2) Independent of Transport/application Protocols.
 Goals
– Establish a Policy Management Information Model for Parlay
– Enable Use of Policy Management APIs by 3rd Party Application
Providers,
– Facilitate Use of Policy Management APIs Within the Network
 Co-Chair: Shehryar Qutub (Lucent Technologies)
 Co-Chair: Peter Heitman (Cisco Systems)
Jain/Bakker – 7
Content Based Charging WG
 Task: Define an API that fits diverse application
types:
– Games, Web Applications, WAP Applications/Gateways,
Telephony.
 Goals:
– Employ the charging, rating and billing capabilities of
telecommunications networks to charge subscribers
– Enable independent service vendors and Application Service
Providers to create applications that support accounting and
charging in a simple, affordable way that helps
 Mask Payment Policy (pre-paid/post-paid)
 Mask Payment Type (Credit Card, Cash, Bank Withdrawal)
 Avoids the need to establish and maintain their own subscriber
database and billing processing facilities
 Chair: Jorg Oppat (Siemens AG)
Jain/Bakker – 8
Presence and Availability Mgmt WG
 Task: Define Parlay Presence and Availability Management APIs
in Order to
– Export and to Manage Presence Information in the Network and
– Policy or Preference Based Availability of Users.
 Goal: To Be Independent of Network Architectures and
Independent of Transport/application Protocols.
 Coordinating With the PAM Forum (www.pamforum.org) to
Promote a Single and Consistent Standard
 Chair: Guda Venkatesh (Teltier, Inc.)
Jain/Bakker – 9
Proposed Java API WG
Objective
– Document rules that define how Java APIs are realised from
Parlay UML
– These Java APIs will be:
 The standard Java API realisation of the Parlay APIs
 Independent of Distribution Mechanism Technology
 Independent of Network Architectures
 Independent of Transport/Application Protocols
 Known as the JAINTM Service Provider APIs (SPA)
 Engineered to exploit other JAIN APIs
Contact:
– Gary Bruce, Sun
Jain/Bakker – 10
Call Control WG
 Task: Define Parlay Call Control APIs to enable
services
– For real-time multimedia (audio, video, and/or data)
applications
– Independent of platforms and networks
– Include aspects of Mobility and Generic User Interaction
– Capture enhancements on Terminal Capabilities and Data
Session Control
 Chair: Richard Stretch (BT)
Jain/Bakker – 11
Parlay Call Control Packages (1 of 5)
Top
GCCS
CCS = Call Control Service
GCCS = Generic CCS
MPCCS = Multi-Party CCS
MMCCS = Multimedia CCS
CCCS = Conferencing CCS
MPCCS
MMCCS
CCCS
Jain/Bakker – 12
Parlay Call Control Packages (2 of 5)
•Traditionally developed for two party calls
•Functionally Simple Applications
Number Translation
Application initiated
Call Barring
Jain/Bakker – 13
Parlay Call Control Packages (3 of 5)
•Traditionally for two or more legs to a call
•Enhanced Application capability
•Leg/Connection specific events
Jain/Bakker – 14
Parlay Call Control Packages (4 of 5)
Enhances the multi-party functionality with multi media capabilities
Media channel control capabilities
•enables - provides a means whereby the app knows when a media
channel is created
•can reject or allow the set up
•permits a certain time period for the media channel
Jain/Bakker – 15
Parlay Call Control Packages (5 of 5)
This really stands for itself:
Used in conjunction with Multi-party and multi-media Interfaces
•reserve resources i.e.bridge
•create conference calls
•create and manage sub-conferences
•Allow parties to join and leave conference
•Split existing conference and move legs
•select chairs
•send video stream to one leg
Jain/Bakker – 16
API Standards Cooperation
 There Is Ongoing Cooperation between Multiple Groups
Involved With API Standards
 Together, We Are Creating a Global Set of Common API
Standards
– Parlay
– JAIN
– 3GPP CN WG5
– ETSI Span 3, 12
– ITU-T
– IETF Policy Management
– PAM Forum
Jain/Bakker – 17
Call Control alignment process
ETSI
SPAN 12
3GPP
OSA
Joint
work on parts 1-12 of
ETSI ES 120070 &
Doc. 120075
JAIN
JCC/SPA
Parlay
APIs
120070 = API for Open Service Access
120075 = API Mapping for Open Service Access
Jain/Bakker – 18
Parlay/3GPP/ETSI/JAIN call control timeline
Jan 01
3GPP,
OSA
Mar 01
May 01
Release 4,
v. 1.0.0†
Release 4,
v. 4.0.0‡
July 01
~Oct 01 ~Mar 02
Rel. 4, Release 5
v. 4.0.x
Parlay,
APIs
Parlay 3.0
Parlay 3.1
ETSI,
SPAN 12
Version 1
Version 2
JCC 1.0
JAIN
JCC 1.1 JCAT
JCC/JCAT
†
‡
The specification is not under change control: version 1.0.x.
Release 4 contains GCCS and MPCCS.
The specification is under “change control”: version 4.0.0.
In Sep/Oct 3GPP plenary will likely approve final version 4.0.x
Jain/Bakker – 19
The mother of all …
 SPAN 12 public accessible document server:
http://docbox.etsi.org/techorg/span/Open/Span12/index.html
 120070 (latest normative UML & OMG IDL of APIs)
http://docbox.etsi.org/techorg/span/Open/Span12/Drafts/
 120075 (latest descriptive mapping documents)
http://docbox.etsi.org/techorg/span/Open/Span12/Mapping/
Jain/Bakker – 20
JAIN “Religious Diagram”
Java Service
Creation
Environment
(JSCE)
Untrusted
third-party
applications
Trusted
third-party
applications
JAIN SPA
Security Interface
Secure Network Space
Java Service Logic Execution
Environment (JSLEE)
API
Java Call Control (JCC)
& Java Coordination and Transactions (JCAT)
TCAP
IP
Broadband
ISUP
INAP
Wireless
SIP
etc
PSTN
Satellit
e
Applications
Protocols
Jain/Bakker – 21
JAIN organization
JAIN Executive Committee (Multiple companies)
JAIN Program Management (Sun)
Protocol expert
group
Applications
expert group
MGCP (Telcordia)
Java Call Control
(JCC/JCAT)
(Telcordia)
TCAP (AePONA)
ISUP (AePONA)
Service Creation
(Telcordia / TBD)
MAP (Ericsson)
Service Logic
Execution (Motorola)
SIP (Dynamicsoft)
OA&M (Sun/AePONA)
Service Provider API
(SPA)
(Sun / BT)
H.323 (Radvision)
INAP (Mahindara BT)
= Led by Telcordia
= Telcordia participation
Policy Managment
(Lucent/Cisco)
Jain/Bakker – 22
JAIN APIs timeline
2000
2001
Remaining SPA
SCE
H.323
Megaco
Q2+
SPA Mobility
ISUP
INAP
MAP
SLEE
Application APIs
Q1
SPA (Parlay)
MGCP
SIP
Q4
JCC
Q3
OAM
TCAP
Protocol APIs
= Led by Telcordia
= Telcordia participation
Jain/Bakker – 23
Fun Facts About JCC
 JCC 1.0 Reference Implementation (RI) and Test Compatibility
Kit (TCK) are available for free download at Telcordia site:
http://www.argreenhouse.com/JAINRefCode/
 JCC 1.0 API (First Public Release) available at SUN site
 JCC implementation discussion list:
http://groups.yahoo.com/group/jainjcc
 Telcordia AR Mini Call Agent prototype passes the TCK
JCC is a simplified version of Parlay’s MPCCS. JCC aligns
with JTAPI and Parlay MPCCS. JCC is protocol agnostic.
JCC is out there and available!
Jain/Bakker – 24
JAIN/OSA/Parlay/ETSI Span 12/SPIRITS
Parlay WG, ETSI SPAN 12
Framework, GUI
3GPP OSA
TC, DSC
AM, C
Generic Messaging,
Connectivity Mgr
 TC: Terminal Cap.
 DCS: Data Session
Control
 AM: Account Mgmt
 C: Charging
Call Control
Mobility
1st Party
CC
Supplementary
Services
SPIRITS
 SLEE:
Service Logic
Execution
Environment
 SCE: Service
Creation
Environment
CC: Call Control
SIP: SIP Servlet
Protocols like MGCP,SIP,
INAP, ISUP, H.323
GUI: Generic User
Interaction
SIPlets,
SLEE,
Protocols,
SCE
JAIN




Jain/Bakker – 25
Mapping a Call Control API to a Signaling
Protocol
Application
JCC API
JCC Implementation
Network Adapter
SIP User Agent/
Proxy
IP
Network
Other SIP
Client/Proxy
Jain/Bakker – 26
“Canonical” SIP call setup
SIP
Registrar
1. Register
1. Register
User
Agent
A
2a. Invite(B, codecs)
3. Trying
4b. Ringing
5b. OK(codec)
6a. ACK
2b. Invite(B, codecs)
SIPenabled
network
4a. Ringing
5a. OK(codec)
6b. ACK
User
Agent
B
Jain/Bakker – 27
Application
Provider
createCall()
Con-A
Con-B
Call
SIP
Party A
SIP
Party B
new()
Idle
routeCall(B,A,-,-)
new()
Idle
Active
Call Delivery
new()
Idle
Call Delivery
INVITE(B,A)
TRYING
RINGING
Alerting
OK
Connected
Connected
ACK
Jain/Bakker – 28
Conclusions
 Open APIs are here!
 Call Control APIs and network signaling protocols like SIP are
complementary, not competing
“The JAIN and Parlay sets of APIs are among the first to emerge
that hold the promise of this simplified, collaborative
development environment. … While these initiatives compete
with each other in some respects, they are also complementary,
with each API incorporating elements of the others. Most
emerging vendors will support at least JAIN and Parlay …”
- Yankee Group, 9/2000
Jain/Bakker – 29
Acronym List
AIN - Advanced Intelligent Network
APIs - Application Programming Interfaces
CAP - CAMEL Application Part
CORBA - Common Object Request Broker
Architecture
CS - Capability Set
ETSI - European Telecommunications
Standards Institute
IDE - Integrated Development Environment
IDL - Interface Definition Language
IIOP - Internet Inter-ORB Protocol
INAP - Intelligent Network Application
Protocol
IT - Information Technology
JAINTM - Java APIs for Integrated
Networks
JCAT - Java Coordination and Transactions
JCC - Java Call Control
JSLEE - Java Service Logic Execution
Environment
MAP - Mobile Application Part
MGCP - Media Gateway Control Protocol
ORB - Object Request Broker
OSA - Open Services Architecture
OSS - Operations Support Systems
PAM - Presence and Availability
Management
SCE - Service Creation Environment
SIP - Session Initiation Protocol
TCP/IP - Transaction Control
Protocol/Internet Protocol
WIN - Wireless Intelligent Network
UML - Universal Machine Language
XML - eXtensible Markup Language
3GPP - 3G Partnership Program
Jain/Bakker – 30
Background Slides
Jain/Bakker – 31
What’s in OSA Release 4?
29.198-400 (N5): OSA API
Part 1:
Part 2:
Part 3:
Part 4:
Part 5:
Part 6:
Part 7:
Part 8:
Part 9:
Part 10:
Part 11:
Part 12:
Overview
Common Data Definitions
Framework
Call Control SCF
User Interaction SCF
Mobility SCF
Terminal Capabilities SCF
Data Session Control SCF
Generic Messaging SCF
Connectivity Manager SCF
Charging SCF
Accounting SCF
 29.198 is captured in
ETSI document
120070
 Parts 4, 11, 12 will go
under change control
in mid. 2001
 Parts 9 and 10 are
not part of release 4
 This diagram does
not show the mapping
parts, to be found in
29.998, ETSI
document 120075
(see next viewgraph)
Jain/Bakker – 32
What’s in Release 4? (cont’d)
29.998-400 (N5): OSA Mapping
Part 1:
General issues on API mapping
Part 2:
n.a. (common data has no mapping)
Part 3:
n.a. (framework has no mapping)
Part 4:
Call Control Service Mapping;
Subpart 1: generic call control CAP Mapping
Subpart 2: generic call control INAP (not in r4)
Subpart 3: multiparty call control INAP
(not in r4)
Subpart 4: multiparty call control SIP
(not in r4)
Subpart 5: multimedia call control extensions
mapping to SIP (not in r4)
Jain/Bakker – 33
What’s in Release 4? (cont’d)
29.998-400 (N5): OSA Mapping
Part 5:
User Interaction Service Mapping
Subpart 1: user interaction CAP Mapping
Subpart 2: user interaction INAP (not in r4)
Subpart 3: user interaction Megaco (not in r4)
Subpart 4: user interaction SMS Mapping
Part 6:
User Location – User Status
Service Mapping to MAP
Part 7:
Terminal Capabilities mapping – n.a.
Part 8:
Data Session Control Service
Mapping to CAP
Part 9:
Messaging mapping – n.a.
Part 10: Connectivity Management mapping – n.a.
Part 11: Account Management – n.a.
Part 12: Charging – n.a.
Jain/Bakker – 34