Java™ API's for the Integrated Network (JAIN™)

Transactions Capabilities Application Part (TCAP)

White Paper

Executive Summary

JAIN™ TCAP (Transaction Capabilities Application Protocol) defines a standard Java interface for the TCAP layer of the Signalling System 7 (SS7) Stack. It describes the Java standard API for transaction processing in the Telecommunications Industry.

Further information on the TCAP API as well as JAIN™ can be found from the Sun’s JAIN™ web site: http://www.java.sun.com/products/jain

 

 

What is JAIN?

The JAIN™ APIs for Integrated Networks brings service portability, convergence, and secure network access to telephony and data networks.

By providing a new level of abstraction and associated Java interfaces for service creation across PSTN, packet (e.g. IP or ATM) and wireless networks, JAIN™ enables the integration of Internet (IP) and Intelligent Network (IN) protocols. This is referred to as Integrated Networks. Furthermore, by allowing Java applications to have secure access to resources inside the network, the opportunity is created to deliver thousands of services rather than the dozens currently available.

Thus, JAIN™ technology is changing the telecommunications market from many proprietary closed systems to a single open network architecture where services can be rapidly created and deployed.

The JAIN™ initiative consists of two Expert Groups:

 

 

What is TCAP?

Transaction Capabilities Application Protocol (TCAP) is a layer of the SS7 communications protocol that was developed to add transaction based functionality to the existing telephone network. The TCAP layer is designed for signalling related messages and provides a means for transfer of information from one application at a switch to another application within another network entity. The information passed through the TCAP layer must be transferred between applications, transparently through the network. The following diagram shows TCAP messages being passed from the switch to the database.

 

 

 

TCAP is used in the real world today by a variety of applications including:

 

 

What is JAIN™ TCAP?

JAIN™ TCAP Specification defines a Java API for the TCAP layer of the Signalling System 7 (SS7) stack. JAIN™ TCAP provides a high level common interface which supports the functionality required by all the supported variants. A specific implementation of the API can be mapped to a specific protocol variant. Any application written to the JAIN™ TCAP API will be portable over different protocol variants and proprietary vendor.

The JAIN™ TCAP Specification comprises of the JAIN™ TCAP API Requirements Specification, the JAIN™ TCAP Reference Implementation (RI) Specification and the JAIN™ TCAP Test Compatibility Kit (TCK) Specification.

The Java API Requirements Specification provides a high level overview of JAIN™ and the JAIN™ TCAP API Specification as well as explaining the JAIN™ Architecture, Transaction Capabilities and the functionality provided by each of the requirements.

The JAIN TCAP Reference Implementation (RI) is a an example Java program that emulates the functions of an SS7 stack in order to verify that JAIN TCAP applications are compatible with the JAIN TCAP specification.

The purpose of the JAIN TCAP CTS is to verify that a JAIN TCAP implementation is compatible with the JAIN TCAP API Specification.

 

JAIN™ TCAP architecture (High Level)

 

A JAIN™ TCAP Application or Listener would use a Provider to send JAIN™ Events. Events are used to send TCAP messages between JAIN™ TCAP objects, and can contain dialogue or component information. To send a JAIN™ TCAP message, a Listener would send component Events to a Provider, interspersed with dialogue Events. These component and dialogue events are the Primitives that are sent between the Provider and the Listener. The diagram below shows the JAIN™ TCAP Events being passed.

 

The companies involved in the JAIN™ TCAP Edit Group are:

 

 Benefits

Benefits to TCAP Application Developers

- A simple API makes applications easier to develop

=> Rapid, inexpensive development of portable applications

 

Benefits to Stack Vendors

 

 

Conclusion

By defining a simple, standardised interface to TCAP, portable TCAP applications can be rapidly developed, resulting in a faster overall time to market.