Find JSRs
Submit this Search


Ad Banner
 
 
 
 

Summary  |  Proposal  |  Detail (Summary & Proposal)
JSRs: Java Specification Requests
JSR 137: JAINTM 3G MAP Specification

Stage Access Start Finish
Withdrawn   04 Mar, 2003  
Expert Group Formation   26 Jun, 2001  
JSR Review Ballot View results 12 Jun, 2001 25 Jun, 2001
Status: Withdrawn
Reason: Seeing that there has been no active interest in the JAIN 3G Map APIs recently and because of lack of member contributions to the Expert Group, the Spec Lead decided to withdrawn the JSR.
JCP version in use: 2.1
Java Specification Participation Agreement version in use: 1.0


Description:
This JSR is to develop the JAINTM 3G MAP APIs which will enable mobile applications in the 3G domain to talk to each other.

Please direct comments on this JSR to the Spec Lead(s)
Team

Specification Leads
  Sanjiv Kapur Hughes Software Systems
Expert Group
  Hughes Software Systems    

This JSR has been Withdrawn
Reason: Seeing that there has been no active interest in the JAIN 3G Map APIs recently and because of lack of member contributions to the Expert Group, the Spec Lead decided to withdrawn the JSR.

Section 1. Identification

Submitting Member: Hughes Software Systems

Name of Contact Person: Sanjiv Kapur

E-Mail Address: skapur@hss.hns.com

Telephone Number: 91-124-6455555 (x 3512)

Fax Number: +91-124-6346530

Specification Lead: Sanjiv Kapur

E-Mail Address: skapur@hss.hns.com

Telephone Number: 91-124-6455555 (x 3512)

Fax Number: +91-124-6346530

Initial Expert Group Membership:
Sun Microsystems

Section 2: Request

2.1 Please describe the proposed Specification:

This JSR is to develop the JAINTM 3G MAP APIs for the mobile application in the 3G domain.

The entities in a Public Land Mobile Network (PLMN) need to exchange information to manage roaming mobile stations (MSs). The 3G MAP defines protocol through which the core network entities in the 3G domain can transfer information between them. It defines the message syntax and the procedures for message exchange between network entities e.g, MSC,HLR,VLR,GMSC,gsmSCF,IWMSC,SIWF,SGSN,GGSN,GMLC.

The representative set of services between these entities are

  • Location Management services(HLR/VLR, LCS, gsmSCF)
  • Authentication Management services(HLR/VLR)
  • Subscriber Management services(HLR/VLR)
  • Subscriber Information services(HLR/gsmSCF)
  • Supplementary services (MSC/VLR,HLR/VLR)
  • Messaging services (MSC/HLR,SGSN/HLR)

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

The target for JAIN(TM) 3G MAP is Java 2 Platform, Standard Edition (J2SE) and possibly the Java 2 Enterprise Edition (J2EE)

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

The JAIN 3G 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 3G 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 Why isn't this need met by existing specifications?

The JAIN MAP API (JSR #000029) caters to APIs required for text messaging to and from Mobile Terminals, for example Short Message Service Centres in GSM Networks and Message Centres in IS41 Networks. The 3G architecture introduces a number of new entities like SGSN, GGSN, gmLC, LCS etc and new interactions and procedures between them resulting in a number of new mobile based services like location services etc. Since these new entities and new interactions are not catered by the existing JAIN MAP API, there is a need to define 3G MAP JAIN APIs.

2.5 Please give a short description of the underlying technology or technologies:

The JAIN 3G MAP specification is based upon the underlying 3G MAP 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 3G MAP protocol stacks. JAIN 3G MAP may extend the JAIN MAP API. Additionally it may be implemented below other systems providing mobility information. In particular the implementation may be used by the capabilities provided by the JAIN SPA Mobility API.

A JAIN 3G 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 3G 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 Is there a proposed package name for the API Specification? (i.e., javapi.something, org.something, etc.)

Package names being considered are:

jain.protocol.3g.map
This package contains the main interfaces, classes and exceptions
required to send and receive 3G MAP messages.

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

No, The proposed specification does not have any dependencies on specific operating systems, CPUs, or I/O devices.

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

None. JAIN MAP expects to utilize standard JDK security.

2.9 Are there any internationalization or localization issues?

Because JAIN 3G MAP is based on 3GPP specifications, the API can be readily adopted in all networks world wide.

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

None of the existing specifications are expected to get affected by these specifications.

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

The anticipated schedule for the development of this specification will be
JSR Approved: early June '01
Expert Group Draft: August '01
Community Review: Sept '01
Public Review: November '01
Proposed Final Draft: December '01/January '02
RI & TCK complete: end January '02
Final Release: Feb '02

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

Regular meetings facilitated by the JAIN Community meetings (usually a minimum of 3 in a year), conference calls and email discussions.

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.

The APIs will be based on the following specifications of 3gpp :
3G TS 29.002 - latest version of the 3GPP specs.

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

Since the 3G MAP APIs are based on the above 3GPP MAP specifications, it will form the starting point for the implementation.