Find JSRs
Submit this Search


Ad Banner
 
 
 
 

Summary  |  Proposal  |  Detail (Summary & Proposal)
JSRs: Java Specification Requests
JSR 194: JAINTM ULS API

Stage Access Start Finish
Withdrawn   21 Feb, 2003  
Expert Group Formation   22 Oct, 2002  
JSR Review Ballot View results 08 Oct, 2002 21 Oct, 2002
Status: Withdrawn
Reason: With agreement from his Expert Group, the Spec Lead decided to withdrawn this JSR following decisions at the November 2002 JAIN meeting in Austin.
JCP version in use: 2.1
Java Specification Participation Agreement version in use: 1.0


Description:
This was intended to allow software developers to rapidly develop external Service Provider-type applications to interrogate the location and status of a user's mobile device.

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

Specification Leads
  Jorgen Dyst Appium Technologies AB
Expert Group
  AePONA Appium Technologies AB Incomit AB
  Siemens AG Sun Microsystems, Inc.
Contributors
       

This JSR has been Withdrawn
Reason: With agreement from his Expert Group, the Spec Lead decided to withdrawn this JSR following decisions at the November 2002 JAIN meeting in Austin.

Original Java Specification Request (JSR)

Identification | Request | Contributions | Additional Information

Original Summary: The JAINTM User Location and Status (ULS) 2.x API is the Java specification of the ETSI/OSA ES 202 915 Mobility 2.x, Parlay Mobility 4.x and 3GPP/OSA Mobility 5.x APIs.

The API is intended to allow software developers to rapidly develop external Service Provider type applications to interrogate the location and status of a user?s mobile device.

Section 1. Identification

Submitting Member: Appium AB

Name of Contact Person: Jorgen Dyst

E-Mail Address: jorgen.dyst@appium.com

Telephone Number: + 46 40 662 29 73

Fax Number: + 46 40 30 32 62


Specification Lead: Jorgen Dyst

E-Mail Address: jorgen.dyst@appium.com

Telephone Number: + 46 40 662 29 73

Fax Number: + 46 40 30 32 62


Initial Expert Group Membership:

Aepona
Appium Technologies
Siemens AG
Sun Microsystems, Inc.

Supporting this JSR:

Aepona
Appium Technologies
Siemens AG
Sun Microsystems, Inc.



Section 2: Request

2.1 Please describe the proposed Specification:

The JAINTM ULS specification will provide JavaTM APIs for use in an ETSI/OSA, Parlay or 3GPP/OSA environment.

These APIs are functionally compatible with the equivalent Parlay APIs.

State-of-the-art design patterns will be used, hiding some details of the underlying communication model within the ETSI/OSA, Parlay or 3GPP/OSA environment.

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

The JAINTM ULS specification is targeted for the Java 2 Platform, Standard Edition (J2SE) and the Java 2 Platform, Enterprise Edition (J2EE).

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

The JAINTM ULS API will be part of a JavaTM technology instantiation of the ETSI/OSA, Parlay and 3GPP/OSA specifications, which enables external enterprises to rapidly build and deploy applications that exploit capabilities of the underlying telecommunications company's network. By adopting ETSI/OSA, Parlay and 3GPP/OSA, the Java community can leverage on the huge investment made by ETSI, Parlay and 3GPP members into the specification and associated adoption across the IT & Telecommunications 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 JAINTM (or Java) API to represent a JavaTM specification of the above specified version of the ETSI/OSA, Parlay and 3GPP Mobility API at present.

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

It is anticipated that the proposed API would be implemented on a local client, using an arbitrary communication protocol to a Parlay server, to access ULS services in a controlled and secure telecommunications environment.

It is essential that the API seamlessly interoperates with other Java technology instantiations of the ETSI/OSA, Parlay and 3GPP/OSA specifications.

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

? JAINTM SLEE
? JAINTM SCE
The JAINTM protocol APIs

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 javax.csapi.mm

It will contribute common classes and interfaces to javax.csapi, as defined in the JAINTM Common API (JSR 145).

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

No

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

No

2.9 Are there any internationalization or localization issues?

No

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

No

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

? Expert group creation as soon as the JSR is approved (Time = T)
? Community Review: T + 1 month
? Public Review: T + 2 months
? Proposed Final Draft: T + 3 months
? RI & TCK: T + 5 months
Final Release: T + 6 months

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

Technical sessions hosted during JAINTM, ETSI, Parlay and/or 3GPP meetings Conference calls and email dialogue to solve specific issues when required.





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.

JAIN documents can be found at: http://java.sun.com/jain/index.html

? ETSI/OSA documents can be found at: http://docbox.etsi.org/tech-org/span/Open/Span12 or http://www.etsi/org

? Parlay documents can be found at: http://www.parlay.org/specs/index.asp

? 3GPP/OSA documents can be found at: http://www.3gpp.org/ftp/tsg_cn/WG5_osa or http://www.3gpp.org

? Parlay UML-to-JAIN SPA ?Java API Realization? rulebook can be found at: http://www.parlay.org/members/workgroups/java_api_realization/index.asp (members only) or (public) http://www.parlay.org/specs/index.asp

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

They would form the basis of the JAINTM ULS API. The Parlay UML-to-JAINTM SPA ?Java API Realization? rulebook would be used to rapidly create a Community Review draft of the JAINTM ULS API.



Section 4: Additional Information (Optional)

4.1 This section contains any additional information that the submitting Member wishes to include in the JSR.

In addition to the development of the JAINTM ULS specification, the Expert Group will deliver the following:

? A ?JAINTM ULS API User Guide? describing the API in some detail. The guide should contain example applications together with associated sequence diagrams and Java code.

? A ?JAINTM ULS API Tutorial? containing a slideset presentation pack of the above.

? A ?JAINTM ULS API Realization? document referencing the use of the Parlay UML-to-JAINTM SPA ?Java API Realization? rulebook and any further changes deemed necessary by the Expert Group to realize this API.

This JSR?s scope was originally included within the scope of the original JAINTM SPA JSR (JSR 24). This JSR has been created as a pragmatic way to complete the original JSR 24, the scope of which was considered too great to be completed by a single expert group.

It is essential that all JAINTM SPA JSRs are initiated as they form the full set of Java APIs that realize the ETSI/OSA, Parlay and 3GPP/OSA specifications, which enables external enterprises to rapidly build and deploy applications that exploit capabilities of the underlying telecommunications company's network. Only by completing the JAINTM SPA specifications will ETSI/OSA, Parlay and 3GPP/OSA reference the JAINTM Service Provider APIs from within their specifications.