 
Use of JCP site is subject to the
JCP Terms of Use and the
Oracle Privacy Policy
 |
|
 JSRs: Java Specification Requests
JSR 191: JAINTM GCCS API
Reason: Withdrawn following agreement with the Expert Group after the 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: The API was intended to allow software developers to rapidly develop external Service Provider type applications to interact with the GCCS Service. Please direct comments on this JSR to the Spec Lead(s) Team
This JSR has been Withdrawn
Identification |
Request |
Contributions |
Additional Information
Original Summary: The JAINTM GCCS 1.x API is the Java specification of the ETSI/OSA ES 201 915 GCCS 1.x, Parlay GCCS 3.x and 3GPP/OSA GCCS 4.x The API is intended to allow software developers to rapidly develop external Service Provider type applications to interact with the GCCS Service. Section 1. Identification Submitting Member: AePONA Ltd Name of Contact Person: Judith Russell E-Mail Address: judith.russell@aepona.com Telephone Number: +028 9026 9100 Fax Number: +028 9026 9111 Specification Lead:Judith Russell E-Mail Address: judith.russell@aepona.com Telephone Number: +028 9026 9100 Fax Number: +028 9026 9111 Initial Expert Group Membership: AePONA Ltd Supporting this JSR: AePONA Ltd Section 2: Request
2.1 Please describe the proposed Specification:The JAINTM GCCS specification will provide Java APIs for use in an ETSI/OSA, Parlay or 3GPP/OSA environment. The 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 GCCS 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 GCCS API will be part of a Java 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 telco'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 Java specification of the ETSI/OSA, Parlay and 3GPP/OSA GCCS 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 GCCS 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 JAIN APIs including but not limited to: 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.cc.gccs It will reuse common classes and interfaces from javax.csapi and javax.csapi.cc as defined in the JAIN 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) 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.- JAINTM documents can be found at:
- ETSI/OSA documents can be found at:
- Parlay documents can be found at:
- 3GPP/OSA documents can be found at:
- Parlay UML-to-JAINTM SPA "Java API Realization" rulebook can be found at: 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 GCCS API. The Parlay UML-to-JAINTM SPA "Java API Realization" rulebook and automated scripts would be used to rapidly create a Community Review draft of the JAINTM GCCS 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 GCCS specification, the Export Group will deliver the following: - a "JAINTM GCCS 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 GCCS API Tutorial" containing a slidset presentation pack of the above. - a"JAINTM GCCS 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 Export Group to relaize this API. |
|||||||||||||||||||||||||||||||||||||
