Find JSRs
Submit this Search

Ad Banner

JSRs: Java Specification Requests
JSR 18: JAINTM OAM API Specification

Original Java Specification Request (JSR)

Identification | Request | Contributions

Section 1: Identification

Contact Information:

Douglas Tait,
Sun Telco, Sun Microsystems, Inc.

Phone: +1 609 231-5790

This JSR is being submitted and endorsed by the following Java Community Process Participants:

  • Sun Microsystems
  • APiON Ltd
  • DGM&S Telecom
  • ADC Newnet
  • Ericsson
  • NTT Comware
  • Telcordia
  • Trillium Digital Systems

Section 2: Request

This JSR is to develop the JAIN Operations, Administation, and Management (OAM) API Specification. It will describe the Java standard API for provisioning and managing protocol interfaces in the Telecommunications and Internet Industry.

2.1 What is OAM?

The JAIN OAM Application Programming Interface (API) allows for the creation, deletion, modification and monitoring of network protocol components. The JAIN OAM API provides a flexible interface that supplies the functionality necessary to manage and configure proprietary protocol stacks regardless of the supported protocol variant. A specific implementation of the API can then be mapped to a proprietary protocol stack management system.

The first release of the JAIN OAM API will be limited to the management of SS7 Protocol layers TCAP, SCCP, MTP-3, and MTP2. This release will not include support for ISUP management, Internet Protocol Management, or for the collection of SS7 network statistics (measurements). These capabilities will be included in a later release.

2.2 Target Java Platform

The first release of the JAIN OAM API is targeted towards Network Operations Centers, Central Office switching environments, and mobile telephony networks. Subsequent releases will incorporate telephony over Internet Protocol networks. Most JAIN OAM API applications will typically be deployed on NEBS Certified equiOAMent or servers that support SS7 or Signaling environments.

2.3 Needs of Java Community this Specification Addresses

The JAIN OAM API specification allows for the rapid creation and deployment of dynamic telephony management objects into a Java telephony managment platform. The price to build and maintain telephony network management systems is very high due to the integration of various divergent network protocols and management components.

A JAIN OAM API managed interface can be rapidly developed, tested, and integrated on a variety of platforms and protocols with access to numerous tools and utilities. A JAIN cross-platform solution gives the Carriers, Service Providers, and Network EquiOAMent Providers a consistent, open environment where they can develop and deploy protocol managed objects.

2.4 The API being defined.

The API specified by the JAIN SS7 Java Community Process Participants for TCAP are based on the ANSI'92, ANSI'96, ITU'93, and ITU'97 specifications. Instead of mapping the standard specifications to a Java interface, the JAIN OAM API specification abstracts a network topological definition onto the variant protocol stacks.

The JAIN OAM API is built upon the Java Beans Event model where a Java Manager Interface can register into one or more layers of the protocol through a JAIN OAM Manageed Object (MO). This interface provides management capabilities to set, delete, modify, or monitor protocol attributes. The first release of JAIN OAM API will focus on management of TCAP, SCCP, MTP-3, and MTP2 SS7 protocol attributes..

2.5 Underlying technologies

The JAIN OAM API specification is based upon the underlying network protocol stacks supplied by the JAIN JSPA members and other 3rd party protocol stack implementations. The first release of JAIN OAM API encompasses the lower layers of an SS7 Protocol stack - TCAP, SCCP, MTP3, and MTP2.

A JAIN OAM application can be written as a program, applet, servlet, or bean. The JAIN OAM API moves the management of underlying protocols up to a standardize Java interface where other managment tools can readily integrate to other systems such as Corba, SNMP, TMN, etc. The eventual integration of all these components allows for human interaction at the highest level to build and manage networks.

While there is no dependancy on other managment interfaces to build a JAIN OAM interface, a Java Bean Manager and/or a visual Java bean builder aids in the develoOAMent, integration, testing, and deployment of a telephony management system.

2.6 Proposed package names

Package names being considered are:
This package contains the main interfaces, classes and exceptions required to set timers, receive alarms, and implement Managed Objects.
This package contains the interfaces, classes and exceptions required to set timers, receive alarms, and implement Managed Objects specific to SS7 Protocol layer Message Transport Part 2 (MTP2). Where MTP1 is concerned the physical connection, MTP2 builds the data messages sent and received from MTP1.
This package contains the interfaces, classes and exceptions required to set timers, receive alarms, and maintain link attributes. Through this package the SS7 Signaling Links, Signaling Link Sets, Signaling Routes, and Signaling Route Sets can be acquired, set , or deleted. Message Transport Part layer 3 is concerned with the Network interconnection.
This package contains the interfaces, classes and exceptions required to receive alarms and maintain link attributes. Through this package the SS7 Global Title, Local Subsystem, Own Signaling Point, Remote Signaling Point, SCCP Timer can be acquired, set , or deleted. The Signaling Connection Control Part (SCCP) is concerned with the quality of service upper layers require. Through SCCP, upper protocols an insure delivery of messages.
This package contains the interfaces, classes and exceptions required to set and receive alarms, and implement Managed Objects specific to SS7 Protocol layer Transaction Capabilities Application Part.

2.7 Possible platform dependencies

The Reference Implementation will have a dependency on RMI.

2.8 Security implications

None. JAIN OAM API expects to utilize standard JDK security.

2.9 Internationalization implications

Because JAIN OAM API is based on ITU and ANSI specifications, the API can be readily adopted in the European market. Adherance to Japanese standards will also make JAIN OAM API ready for the Asian market.

2.10 Localization implications

Since JAIN OAM API is also based on ANSI/Bellcore standards, the OAM API can be readily adapted to most North American SS7 Protocol Stacks.

2.11 Risk assessment

JAIN OAM API moves Java into telco carrier grade service. The Telcoms Industry levies Stingent performance and failure requirements on hardware and software platforms. Risks include failure of the Java platform due to poor performance or the inability to failover or recover. Performance evaluation and tests based on API architecture will be published with each release of the API. Failover will be measured and published based on latency to recover to a like platform and recover state data through JDBC interfaces or Transaction based tools.

2.12 Existing specifications rendered obsolete or deprecated

Not applicable.

2.13 Existing specifications needing revisions

The first release of JAIN OAM API will have no affect on other APIs, however, subsequent releases of JAIN OAM API must adhere to and coexist with the JMAPI API. The JAIN OAM API will make no attempt to defined functionality already provided by JMAPI, but will instead utilize or reference JMAPI interfaces where needed. The purpose of JAIN OAM is to provide management interfaces specific to protocol stacks, where JMAPI is concerned with general management interfaces.

Section 3: Contributions

Documents describing JAIN can be found at