Find JSRs
Submit this Search

Ad Banner

JSRs: Java Specification Requests
JSR 132: JAINTM OAM API Specification v2.0

This JSR has been Withdrawn
Reason: The JAIN community has decided to encapsulate the management functionality for each of the JAIN protocol specifications into their own specification as opposed to encapsulating this functionality in a separate JSR.

Original Java Specification Request (JSR)

Identification | Request | Contributions
Original Summary: This JSR is to develop the JAINTM Operations, Administration, and Maintenance (OAM) API v2.0 Specification, which defines a standard Interface for provisioning and managing various protocol interfaces, switching platforms, and applications servers in the Telecommunications and Internet Industry.

Section 1. Identification

Submitting Member: Sun Microsystems, Inc.

Name of Contact Person: Phelim O'Doherty

E-Mail Address:

Telephone Number: +44 (0) 7796274696

Fax Number:

Specification Lead: Phelim O'Doherty

E-Mail Address:

Telephone Number: +44 (0) 7796274696

Fax Number:

Initial Expert Group Membership:

  • Sun Microsystems

Section 2: Request

2.1 Please describe the proposed Specification:

This JSR is to develop the JAIN Operations, Administration, and Management(OAM) API v2.0 Specification. It will describe the Java standard API for provisioning and managing various protocol interfaces, switching platforms, and applications servers in the Telecommunications and Internet Industry, by building upon JSR 00018 - JAIN OAM API v1.3 specification.

The JAIN OAM API v2.0 specification will conform to the Java Instrumentation Level design patterns of the Java Management Extensions (JMX) v1.0 specification and use the Managed Bean (MBean) paradigm for the creation, deletion, modification of network components. JMX defines the architecture, design patterns, APIs and services for application and network management.

To effectively manage the resources provided by a network, it is necessary to monitor and measure the present, and estimate the future performance, utilization and availability of these resources. JAIN OAM v2.0 will enable this functionality by allowing a management application to monitor these protocol components, with regard to Errors, Alarms and Statistics via Java Events.

The JAIN OAM API provides a flexible interface that supplies the functionality necessary to manage and configure proprietary environments regardless of the supported protocol variant. A specific vendor implementation of the JAIN OAM API v2.0 can then be mapped to their proprietary management environment.

The JAIN OAM API v2.0 specification will be built upon the JavaBeans Event model where a Manager Application can register into one or more layers of a network through a JAIN OAM Managed Object (MO). This interface provides management capabilities to set, delete, modify, or monitor network component attributes as outlined above.

The latest public release of the JAIN OAM API v1.3 was limited to the management of the following SS7 Protocol layers, TCAP, SCCP, MTP-L3, and MTP-L2. JAIN OAM API v2.0 will compliment JAIN OAM API v1.3 by building on its architectural concepts and supporting the same Event Model adopted by it. Furthermore JAIN OAM API v2.0 will include management support for the following:-

  • SS7 protocols - ISUP, MAP and INAP
  • Internet Protocols - SIP, MGCP, Megaco and H.323
  • Softswitch Environments - JCC

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

JavaTMTM 2 Enterprise Edition platform and JavaTM 2 Standard Edition platform.

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

The JAIN OAM API specification allows for the rapid creation and deployment of dynamic telephony management objects into a Java telephony management 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 such as Network Operations Centres, Central Office switching environments, mobile telephony networks and telephony over IP networks such as Softswitch environments. A JAIN cross platform solution gives the Carriers, Service Providers, and Network Equipment Providers a consistent, open environment where they can develop and deploy a variety of application and protocol managed objects.

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

The purpose of JAIN OAM is to provide management interfaces specific to telephony protocols in today's Integrated Network. Were JMX exposes an abstracted view to the general management of interfaces in the Java environment, JAIN OAM API v2.0 will expose the complexity of the management of current telephony networks.

JAIN OAM API v1.3 exposes the lowers layers of the SS7 network, however their is need within the Java Community for a management interface into the application layers of the SS7 protocol, the respective telephony protocols in the Internet Industry and the Softswitch environment.

2.5 Please give a short description of the underlying technology or 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 second release of the JAIN OAM API will carry the same dependencies as JAIN OAM API v1.3 specification namely - TCAP, SCCP, MTP3, and MTP2 as well as the newly supported protocols INAP, MAP, ISUP, MGCP, Megaco, SIP, H.323 and JCC.

While there is no dependency on other management interfaces to build a JAIN OAM interface, the JAIN OAM API v2.0 specification will enable an implementation to operate with or without a JMX agent implementation. A management application should be able to manage a JAIN OAM implementation either through a JMX agent, or directly and expect the same results.

The JAIN OAM API moves the management of the Integrated Network up to a standardize Java interface where other management tools such as JMX 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.

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

Package names being considered are:

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


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


2.9 Are there any internationalization or localization issues?

None. JAIN OAM v2.0 is based on a wide range of standards that encompass the world-wide market.

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

JAIN OAM v2.0 enhances the architecture of JAIN OAM v1.3 and builds upon it by supporting the additional protocols outlined above. It is expected that JAIN OAM v2.0 will become the single Java source of telephony management in the industry, therefore deprecating JAIN OAM v1.3. JAIN OAM API will have no affect on other APIs, however, subsequent releases of the JAIN OAM API must adhere to and coexist with the JMX API. The JAIN OAM API will make no attempt to defined functionality already provided by JMX, but will instead utilize naming conventions or reference JMX interfaces where needed.

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

Initiation: May 2001
Community Review: September 2001
Public Review: November 2001
Proposed Final Draft: February 2002
Reference Implementation: March 2002
Technology Compatability Kit: April 2002
Final Draft: April 2002

2.12 Please describe the anticipated working model for the Expert Group working on developing this specification.

Primary form of collaboration will be via email and augmented by scheduled conference calls when necessary.

The expert group will draw upon the experts in the JAIN initiatives, therefore face-to-face meetings will be coordinated
with the regularly scheduled meetings of this initiative, to facilitate fluid exchange of information and encourage participation by the experts of this expert group.

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.

Documents describing JAIN OAM v1.3 can be found at:-

Documents describing JAIN can be found at:-

Documents describing JMX can be found at:-

Documents describing JavaBeans can be found at:-

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

OAM v2.0 will build upon the JAIN OAM v1.3 package. The Event Propagation and Naming Convention upon which OAM v2.0 will be based are described in the JavaBean Event Model and the JMX specification respectively.