Find JSRs
Submit this Search

Ad Banner

Summary  |  Proposal  |  Detail (Summary & Proposal)
JSRs: Java Specification Requests
JSR 98: JAINTM User Location and Status API

Stage Access Start Finish
Final Release Download page 28 Feb, 2002  
Final Approval Ballot View results 05 Feb, 2002 19 Feb, 2002
Proposed Final Draft Download page 19 Dec, 2001  
Public Review Download page 30 May, 2001 29 Jun, 2001
Community Draft Ballot View results 07 May, 2001 14 May, 2001
Community Review Login page 06 Apr, 2001 07 May, 2001
Expert Group Formation   08 Jan, 2001 11 Jan, 2001
JSR Review Ballot View results 19 Dec, 2000 08 Jan, 2001
Status: Final
JCP version in use: 2.1
Java Specification Participation Agreement version in use: 1.0

The JAIN User Location and Status 1.0 API is the Java specification of the Parlay Mobility 2.1 API.

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

Specification Leads
  Ulf Lange Siemens AG
Expert Group
  AePONA BT Group plc Incomit AB
  Motorola Siemens AG Sun Microsystems, Inc.
  Telcordia Technologies, Inc. Ulticom

Original Java Specification Request (JSR)

Identification | Request | Contributions
Original Summary: The JAIN User Location and Status 1.0 API is the Java specification of the Parlay Mobility 2.1 API.

The API is intended to allow software developers to rapidly develop external Service Provider type applications using abstract primitives that hide the heterogeneity of underlying networks.

Section 1. Identification

Submitting Member: Siemens AG

Name of Contact Person: Ulf Lange

E-Mail Address:

Telephone Number: +49 30 386 23214

Fax Number: +49 30 386 23957

Specification Lead: Siemens AG

E-Mail Address:

Telephone Number: +49 30 386 23214

Fax Number: +49 30 386 23957

Initial Expert Group Membership:
(Please provide company or organization names. Note that expert group members must have signed the JSPA.)

Siemens AG

Section 2: Request

2.1 Please describe the proposed Specification:

The JAINTM User Location and Status 1.0 API specification will provide Java APIs for use in a Parlay client environment.

These APIs are functionally compatible with the Parlay Mobility 2.1 APIs.

State-of-the-art design patterns will be used hiding some details of the underlying communication model between Parlay client and server.

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

JAINTM User Location and Status 1.0 specification is targeted for the Java 2TM Platform, Standard Edition (J2SETM)

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

The JAINTM User Location and Status 1.0 API will be part of a Java technology instantiation of Parlay, which enables external enterprises to rapidly build and deploy applications that exploit capabilities of the underlying telco's network. By adopting Parlay, the Java community can leverage on the huge investment made by Parlay members into the specification and associated adoption across the IT & telecom industry.

This specification is required to ensure continued standardization across the computing industry with regard to public open APIs.

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

There exists no JAIN (or Java) API to represent a Java specification of the Parlay Mobility API at present.

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

The JAINTM User Location and Status 1.0 specification abstracts underlying network capabilities.

It is anticipated that the proposed API would be implemented on a Parlay client, using an arbitrary communication protocol to a Parlay Server, to access User Location and Status services in a controlled and secure telecoms environment.

Additionally it may be implemented on any other system providing mobility information. In particular the implementation may use the capabilities of the JAINTM MAP API.

It is highly desired that the API seamlessly interoperates with other JAINTM APIs including but not limited to:

JAINTM Call Control

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

The specification will be provided directly in, and in subpackages of
It will contribute common classes and interfaces to javax.jain and, as defined in the JAINTM Common API.

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?


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


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

We plan to provide the community draft immediately after approval of the JSR.

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 following specifications serve as design references for JAINTM User Location and Status 1.0 API:

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

The Parlay Mobility would form the basis of the JAINTM User Location and Status API.