• JSRs by Platform
• JSRs by Technology
• JSRs by Stage
• JSRs by Committee
• List of All JSRs



Register for Site

Use of JCP site is subject to the JCP Terms of Use and the Oracle Privacy Policy


• About JCP
  • Program Overview
  • JCP Process Document
  • Calendar
  • JCP Members
  • Executive Committee
  • Elections
• Get Involved
  • Overview
  • Becoming a JCP Member
  • Java in Education
• Community Resources
  • Overview
  • Tutorials
  • JCP Podcasts
  • Spec Lead Guide
  • TCK Tool & Info
  • License Reference
• Community News
  • News
  • Programs & Awards
  • Press Releases
  • Success Stories
• FAQ
• Contact Us

This JSR has been Withdrawn
Reason: Withdrawn due to Spec Lead's move to another company and the lack of interest from the rest of the Expert Group in driving the spec to Final Release. At the time it was withdrawn, there had been no activity in the JSR since September 2001.

Original Java Specification Request (JSR)

Identification | Request | Contributions

Section 1: Identification

Matti Drisin,
Ericsson Infotech AB.

Phone: +46 8 1 719 8429
E-Mail: Matti.Drisin@ein.ericsson.se

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

• Sun Microsystems
• APiON Ltd
• Ulticom
• ADC Newnet
• Ericsson
• Telcordia
• Trillium Digital Systems
• NTT
• Nokia

Section 2: Request

This JSR is to develop the Java APIs for Integrated Network (JAINtm) Mobile Application for GSM & IS41 (MAP) Specification. It will describe the Java standard API for MAP in the Telecommunications Industry.

2.1 What is MAP?

MAP adds functionality for Mobile text Applciations to the Public Land Mobile Network (PLMN). MAP handles numerous services for text messaging to and from Mobile Terminals, for example Short Message Service Centres in GSM Networks and Message Centres in IS41 Networks

2.2 Target Java Platform

The JAIN MAP Specification is targeted towards Central Office switching environments, mobile telephony networks, and telephony over Internet Protocol networks. This will typically be NEBS Certified equipment or servers that support SS7 or Signaling environments.

2.3 Needs of Java Community this Specification Addresses

The JAIN MAP specification defines an API which allows for the rapid creation and deployment of dynamic telephony services into a Java telephony platform. Standard Telephony applications require costly resources to develop, test, and deploy. A JAIN MAP component 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 The API being defined.

The API specified by the JAIN SS7 Java Community Process Participants for MAP are based on the ETSI MAP GSM and IS41 TIA/EIA specifications. Instead of mapping the standard specifications to a Java interface, the JAIN MAP specification abstracts a functional definition into the variant protocol stacks.

The JAIN MAP API is built upon the Java Beans Event model. The protocol stack vendor supplies the JAIN MAP 'provider' interface into the protocol stack. JAIN MAP 'listeners' may readily be rolled onto the platform by an object manager.

Proprietary stack features are hidden behind a JAIN MAP Factory. Through JAIN MAP interfaces, a protocol stack provider is obtained from the factory, and JAIN MAP listeners are then attached to the providers.

2.5 Underlying technologies

The JAIN MAP specification is based upon the underlying SS7 protocol stacks supplied by the JAIN JSPA members and other 3rd party protocol stack implementations and its initial purpose is to provide a ubiquitous, standard Java interface into SS7 protocol stacks.

A JAIN MAP application can be written as a program, applet, servlet, or bean. The Java bean makes for an ideal telephony component for rapid dynamic service integration. The Telecom industry has defined telephony services built by integrating components in a Service Creation Environment (SCE). The service is then loaded onto a Service Logic Execution Environments (SLEE) where they receive incoming calls and perform the service logic.

Telephony components are analogous to objects or Java Beans. A Service Logic Execution Environments may be built within a Java Virtual Maching using Java Bean technology. The SLEE requires Java Beans and a Java Bean Management tool. Service Creation Environments may be built using Java visual tools such as Java Studio, or Visual Cafe.

While there is no dependancy on such tools to build a JAIN MAP component, a Java Bean Manager and/or a visual Java bean builder aids in the development, integration, testing, and deployment of telephony services.

2.6 Proposed package names

Package names being considered are:

jain.ss7.MAP

This package contains the main interfaces, classes and exceptions required to send and receive MAP messages.

2.7 Possible platform dependencies

The Reference Implementation will have a dependency on RMI.

2.8 Security implications

None. JAIN MAP expects to utilize standard JDK security.

2.9 Internationalization implications

Because JAIN MAP is based on ETSI GSM and TIA/EIA IS41 specifications, the API can be readily adopted in all GSM and IS41 networks world wide.

2.10 Risk assessment

JAIN MAP 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.

Section 3: Contributions

Documents describing JAIN can be found at:

http://www.sun.com/products-n-solutions/telco/jain/index.html