1 Objectives and Scope

 

The Java™ API's for the Integrated Network (JAIN) bring Service Portability and Network Convergence into the Telephony Network. JAIN encompasses a standard set of interfaces for service creation and a number of standard interfaces for service execution. The service creation interfaces allow new services to be described as JavaBeansä, which can be connected using standard graphics tools to create new services. The service execution environment includes JavaTM interfaces to a number of telephony protocols such as TCAP (Transaction Capabilities Application Part) and ISUP (ISDN User Part). How the development of JAIN OAM fits into overall JAIN program management is specified in Figure 1.1:

 

 

The reason why we need JAIN is due to the technological blockage with interfaces to switches, computers, and services. The problem, which is deep inside the network, is that services cannot be transported from one system to another. JAIN defines an interface into the specific domain of each vendor's SS7 stack, as well as providing an interface for an application to any vendor's stack.

The need to define a standard API has become paramount as users of the telephone and Internet demand better, coherent services. JavaTM provides a perfect environment for developing such a standard. The JavaTM write once, run anywhere philosophy commands interoperability between SS7 stack providers enabling Network Equipment Providers to choose between SS7 vendors and provide services compatible with any system.

A JavaTM approach to telephony offers telephone service providers interoperability between network components. Resulting from this, Network Equipment Providers and SS7 Vendors will be able to bring their true value to the market unobstructed by compatibility and interoperability issues.

The objective of JAIN OAM is to define a Javaä Application Programming Interface (API) that shall allow for the creation, deletion, modification and monitoring of SS7 network components. The JAIN OAM design concept shall provide a flexible interface that shall supply the functionality necessary to manage and configure any proprietary SS7 Stack regardless of the supported protocol variant. A specific implementation of the API can then be mapped to a proprietary SS7 Stack management system.

For Release 1.0 the scope of JAIN OAM shall be limited to the management of TCAP, SCCP, MTP-3, and MTP2 SS7 protocol layers. Release 1.0 shall not include support for ISUP management. This capability shall be included in a later release of JAIN OAM.

 

This document is laid out in the following format:

  • Chapter 1 - Objectives and Scope: This chapter provides an insight to JAIN, why we need JAIN, and what needs to be achieved in order to provide a JAIN OAM API SPECIFICATION.

  • Chapter 2 - Introduction: This chapter provides an introduction to the network components in an SS7 network and the management of these elements before introducing the JAIN OAM architecture.

  • Chapter 3 - Requirements Definition: This chapter defines the requirements necessary to develop JAIN OAM Release 1.0. Each requirement's function is explained in the subsequent paragraph and any additional information needed is provided at this point.

  • Chapter 4 - External Requirements: This chapter outlines the requirements that do not directly effect the API's implementation, however they may effect the API's development process.

  • Chapter 5 - Appendix I: This chapter lists the material, which was referenced throughout this document.

  • Chapter 6 - Appendix II: This chapter lists the abbreviations used throughout the document as well as any terms, which may need explanation.

  • Chapter 7 - Appendix III: This chapter lists the figures and tables supplied throughout this document.

  • Chapter 8 - Appendix IV: This chapter provides the URLs of the partner companies involved in developing JAIN OAM Release 1.0.

  • Chapter 9 - Appendix V: This chapter outlines the control, distribution and history of this document.

 

1.1 JAIN OAM Specification

 

The JAIN Operations, Administration and Maintenance (OAM) specification will provide a standard portable interface that shall allow a service provider to provision and maintain components in an SS7 network. For example, transmission rates, hardware characteristics, routing configurations, are all part of provisioning an SS7 stack and are all covered by the JAIN OAM API specification. While the other JAIN APIs, such the JAIN TCAP API and the JAIN ISUP API, define a common interface to proprietary implementations of protocol layers in an SS7 protocol stack, the JAIN OAM API specification defines a common interface to proprietary management interfaces for an SS7 protocol stack. The JAIN OAM API specification will allow for the creation, deletion, modification, measuring and monitoring of SS7 network components.

This document contains a concise list of all the requirements, which need to be satisfied for the public Release 1.0 of the JAIN OAM specification. It is important to note the syntax of the requirements, in that:

  • If the wording of a specific requirement includes ‘shall’ then the incorporation of this requirement in the JAIN OAM specification is mandatory.

  • If the wording of a specific requirement includes ‘should’ then the incorporation of this requirement in the JAIN OAM specification is strongly recommended, but is not mandatory.

 

The deliverables of the JAIN OAM specification release 1.0 shall encompass:

  • A Javaä Application Programming Interface (API) which shall define a common interface for operating, administrating and maintaining proprietary implementations any SS7 protocol stack. The API will provide the ability to securely provision network components required by MTP-2, MTP-3, SCCP and TCAP.

  • A Compatibility Test Suite (CTS) which tests the implementation of JAIN interfaces for compliance to the JAIN specification. The purpose of the JAIN CTS is to verify that a JavaTM OAM implementation is compatible to the JAIN OAM API specification.

  • A Reference Implementation (RI) which is the "proof of concept" implementation of the specification. The RI will emulate or simulate the functions of a SS7 stack management system in order to verify the requirements in this specification. The purpose of the RI is to provide a means to verify JavaTM applications are compatible with the JAIN specification.

The Participant whose Expert is chosen as Specification Lead is typically responsible for obtaining the appropriate rights the CTS and the RI to fulfil the JavaTM Specification Participant Agreement. The JavaTM specification definition and process can be found at

http://java.sun.com/aboutJava/communityprocess/index.html .


If you have any comments on these webpages or content, please send them to:
JainOam@East.Sun.Com
Copyright - 1999 Sun Microsystems