JAIN Java Call Control (JCC) and Java Coordination and Transactions (JCAT) © 2001, Telcordia Technologies, Inc. An SAIC Company Ravi Jain, John-Luc Bakker, and Farooq Anjum July 23, 2001 {rjain, jbakker,

Jain/Bakker – 2 Overview  Introduction  JCAT  Mapping JCC to SIP  Conclusion

Jain/Bakker – 3 JAIN “Religious Diagram” PSTN Broadband IP Satellit e Wireless

Jain/Bakker – 4 Call Control alignment process Joint work on parts 1-12 of ETSI ES & Doc ETSI SPAN 12 3GPP OSA JAIN JCC/SPA Parlay APIs = API for Open Service Access = API Mapping for Open Service Access

Jain/Bakker – 5 Parlay/3GPP/ETSI/JAIN call control timeline JCC 1.1JCC 1.0 JAIN JCC/JCAT Version 2Version 1 ETSI, SPAN 12 Parlay 3.1Parlay 3.0 Parlay, APIs Release 5Release 4, v ‡ Release 4, v † 3GPP, OSA July 01May 01Mar 01Jan 01 † The specification is not under change control: version 1.0.x. Release 4 contains GCCS and MPCCS. ‡ The specification is under “change control”: version In Sep/Oct 3GPP plenary will likely approve final version 4.0.x Rel. 4, v. 4.0.x ~Oct 01~Mar 02 JCAT

Jain/Bakker – 6 Fun Facts About JCC  JCC 1.0 Reference Implementation (RI) and Test Compatibility Kit (TCK) are available for free download at Telcordia site:  JCC 1.0 API (First Public Release) available at SUN site  JCC implementation discussion list:  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 – 7 Call control inheritance and alphabet soup CCS MPCCSGCCSCCCS MMCCS JCC 1.1JCP JCAT JTAPI 1.4 Core JCCCS Parlay/ETSI JAIN JMMCCS JTAPI CCS = Call Control Service GCCS = Generic CCS MPCCS = Multi-Party CCS CCCS = Conferencing CCS MMCCS = Multi-Media CCS JCP = Java Call Processing JCC = Java Call Control JCAT = Java Coordination & Transactions JTAPI = Java Telephony API Proposed 

Jain/Bakker – 8 JAIN JCAT Requirements  JCAT –A rich call model to address the concerns of the JAIN community and still have alignment with Parlay and JTAPI –Addresses end-office (Class 5, local exchange) environment –Explicitly models terminals unlike JCC and Parlay  Support first-party as well as third-party calls  JCAT Expert Group Spec Lead (Telcordia) is obligated to release: –API Specification document  Rigorously defined: Pre and post-conditions, FSM, use Java patterns –Reference Implementation (RI) –Test Compatibility Kit (TCK)

Jain/Bakker – 9 Java Coordination & Transactions (JCAT) Object Inheritance diagram Java Call Processing (JCP) JTAPI Core Java Call Control (JCC) Parlay Extensions JTAPI Extensions JCC 1.1 is based on Parlay 3.0 MPCCS alignment

Jain/Bakker – 10 Basic JCAT approach Application Call Provider Connection Call Listener Call Listener Connection Listener Connection Listener Provider Listener Provider Listener Synchronous method calls Java Events JCAT API Network JAIN and Parlay Terminology Map: Provider = Call Control Manager Connection = Call Leg

Jain/Bakker – 11 JCAT Objects

Jain/Bakker – 12 Mapping a Call Control API to a Signaling Protocol Other SIP Client/Proxy JCC Implementation Network Adapter SIP User Agent/ Proxy Application JCC API IP Network

Jain/Bakker – 13 “Canonical” SIP call setup User Agent A SIP- enabled network User Agent B SIP Registrar 1. Register 2a. Invite(B, codecs) 3. Trying 4b. Ringing 5b. OK(codec) 6a. ACK 2b. Invite(B, codecs) 4a. Ringing 5a. OK(codec) 6b. ACK

Jain/Bakker – 14 createCall() routeCall(B,A,-,-) new() INVITE(B,A) TRYING RINGING ACK ApplicationProviderCon-ACon-BCall SIP Party B SIP Party A Idle Call Delivery Alerting OK Connected Active Idle

Jain/Bakker – 15 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 – 16 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 JAIN TM - 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 – 17 Background Slides

Jain/Bakker – 18 JAIN organization = Led by Telcordia = Telcordia participation INAP (Mahindara BT) JAIN Program Management (Sun) MGCP (Telcordia) Protocol expert group TCAP (AePONA) ISUP (AePONA) MAP (Ericsson) SIP (Dynamicsoft) OA&M (Sun/AePONA) H.323 (Radvision) Service Logic Execution (Motorola) Service Creation (Telcordia / TBD) Policy Managment (Lucent/Cisco) Applications expert group Java Call Control (JCC/JCAT) (Telcordia) Service Provider API (SPA) (Sun / BT) JAIN Executive Committee (Multiple companies)

Jain/Bakker – 19 JAIN APIs timeline TCAP OAM SIP MGCP MAP INAP SCE ISUP Q3Q4Q1 Q Protocol APIs Application APIs SLEE MegacoH.323 SPA Mobility SPA (Parlay) JCC Remaining SPA = Led by Telcordia = Telcordia participation