Find JSRs
Submit this Search


Ad Banner
 
 
 
 

JSRs: Java Specification Requests
JSR 122: JAINTM JCAT

This JSR has been Dormant
Reason: The Executive Committee voted to list this JSR as dormant in May 2012.

Updates to the Original Java Specification Request (JSR)

This section contains updates to the original request.

2013.04.16: Ericsson AB has become the Specification Lead.

Specification Lead: Christer Boberg, Ericsson AB

E-Mail Address: christer.boberg@ericsson.com

Telephone Number: -

Fax Number: -


Original Java Specification Request (JSR)

Identification | Request | Contributions
Original Summary: This JSR is to develop the JavaTM Coordination and Transaction (JCAT) specification. JCAT perceives Java Call Control (JCC) as its core package and extends it with concepts to model and control terminal capabilities. Furthermore, JCC's state transitions models are enriched and more control is provided over its processing.

Section 1. Identification

Submitting Member: Telcordia Technologies, Inc.

Name of Contact Person: Ravi Jain

E-Mail Address: rjain@telcordia.com

Telephone Number: +1 973 829 3178

Fax Number: +1 973 829 2645


Specification Lead: Ravi Jain

E-Mail Address: rjain@telcordia.com

Telephone Number: +1 973 829 3178

Fax Number: +1 973 829 2645


Initial Expert Group Membership:

AePONA

  • BT
  • IBM
  • Lucent
  • Motorola
  • Nokia
  • Nortel Networks
  • Telcordia
  • Ulticom
  • SUN


  • Section 2: Request

    2.1 Please describe the proposed Specification:

    JavaTM Coordination and Transaction (JCAT) includes (but is not limited to) the facilities required for applications to be invoked and return results before, during or after calls; to process call parameters or subscriber-supplied information; and to engage in further call processing and control.

    JCAT perceives JavaTM Call Control (JCC) as its core call control model. JCAT extends the JCC call control model with terminal capabilities and it enriches JCC's state diagrams such that an even more diverse range of applications can be supported. The AIN/IN class of applications is an example of applications that can be supported.

    The name JCAT was taken from a previous JSR (JSR 000021). If the expert group feels the name is not applicable, it may be decided to change the name.

    2.2 What is the target Java platform? (i.e., desktop, server, personal, embedded, card, etc.)

    JavaTM 2 platform Standard Edition, JavaTM 2 platform Enterprise Edition.

    2.3 What need of the Java community will be addressed by the proposed specification?

    The JAIN JCAT Specification defines an API which allows for the rapid creation and deployment of a diverse range of and dynamic telephony services into a Java telephony platform. Traditionally, telephony applications require costly resources to develop, test, and deploy. A JAIN software component written to the JCAT API can be rapidly developed, tested, and integrated on a variety of platforms with access to numerous tools and utilities. A JAIN cross-platform solution gives the Carriers, Service Providers, and Network Equipment Providers a consistent, open environment where they can develop and deploy telephony services.

    2.4 Why isn't this need met by existing specifications?

    JCAT includes facilities not found in existing specifications, such as JCC. JCC is intended to be the core for JCAT and therefore JCC's facilities do not conflict with the JCAT facilities.

    2.5 Please give a short description of the underlying technology or technologies:

    The JAIN JCAT Specification will provide an interface to underlying call processing platforms (which are assumed to include coordination and transactions facilities) supplied by the JAIN JSPA members and other third-party platform implementers. It is expected that JAIN JCC/JCAT platform providers will support a variety of lower-layer signaling, coordination and transaction protocols, such as MGCP, SIP, H.323, ISUP, TCAP, etc., in order to implement the facilities provided via the JCC/JCAT APIs. However, through the JAIN JCC/JCAT APIs, a JAIN JCC/JCAT application is abstracted from the functions and peculiarities of different vendors' call processing platforms.

    2.6 Is there a proposed package name for the API Specification? (i.e., javapi.something, org.something, etc.)

    jain.application.services.jcat

    2.7 Does the proposed specification have any dependencies on specific operating systems, CPUs, or I/O devices that you know of?

    None

    2.8 Are there any security issues that cannot be addressed by the current security model?

    None

    2.9 Are there any internationalization or localization issues?

    JCAT is expected to be modular, extensible and defined at a sufficient level of abstraction so that it can be adapted to the needs of the markets.

    2.10 Are there any existing specifications that might be rendered obsolete, deprecated, or in need of revision as a result of this work?

    JCAT depends on JAIN JCC. This specification may impact JAIN JCC and may draw new requirements for the JCC specification. JCAT is aware of the APIs developed under the JAIN SPA activity, JCAT foresees to interwork with these APIs. None of the JAIN SPA APIs are expected to be duplicated or impacted by this work.

    2.11 Please describe the anticipated schedule for the development of this specification.

    JSR Approved : April '01

  • Expert Group Draft : end Jun '01
  • Community Draft on JCP website : end Sept '01
  • Proposed Final Draft on JCP website : end Dec '01
  • RI & TCK complete : end Jan '02
  • Final Release on JCP website : end Feb '02




  • Section 3: Contributions

    3.1 Please list any existing documents, specifications, or implementations that describe the technology. Please include links to the documents if they are publicly available.

    • JCC Specification (JSR 000021)
    • ITU-T Q.1200 series recommendations
    • JTAPI

    3.2 Explanation of how these items might be used as a starting point for the work.

    JCAT inherits from the JCC package. The mentioned terminal capabilities are similar to those found in JTAPI. Furthermore, concepts found in the Basic Call Model (BCM) are applied to extend JCC's call information retrieval capabilities and to engage in further call processing and control.