 
Use of JCP site is subject to the
JCP Terms of Use and the
Oracle Privacy Policy
 |
|
 JSRs: Java Specification Requests
JSR 130: OSS Billing Mediation API
JCP version in use: 2.6 Java Specification Participation Agreement version in use: 2.0 Description: Provide an API via the OSS through Java initiative that allows telecom network management applications to be developed and integrated with Java-enabled IP Billing systems. Please direct comments on this JSR to the Spec Lead(s) Team
Updates to the Original Java Specification Request (JSR) The following information has been updated from the original JSR.
Specification Lead: James Jouett E-Mail Address: jjouett@necam.com Telephone Number: +1 214 262 3214 Fax Number: +1 214 272 3225 Original Java Specification Request (JSR)
Identification |
Request |
Contributions |
Additional Information
Section 1. Identification Submitting Member: NEC Name of Contact Person: Ken Dilbeck E-Mail Address: kdilbeck@necam.com Telephone Number: +1 214 262 3250 Fax Number: +1 214 262 3250 Specification Lead: Ken Dilbeck E-Mail Address: kdilbeck@necam.com Telephone Number: +1 214 262 3250 Fax Number: +1 978 262 3225 NOTE: This information has been updated from the original JSR. Co-Submitting Member: Ericsson Name of Contact Person: Lars Tenf? E-mail Address: Lars.Tenfalt@erv.ericsson.se Telephone Number: +46 31 747 1974 Fax Number: tbd
Co-Submitting Member: Motorola Name of Contact Person: Eric Coleman E-mail Address: E.Coleman@motorola.com Telephone Number: +1 480 732 3743 Fax Number: +1 480 732 5117
Co-Submitting Member: Nokia Name of Contact Person: Stefan Vaillant E-mail Address: Stefan.Vaillant@nokia.com Telephone Number: +49 211 9412 3973 Fax Number: +49 211 9412 3988
Co-Submitting Member: Nortel Networks Name of Contact Person: Peter Gorecki E-mail Address: pgorecki@nortelnetworks.com Telephone Number: +1 613 765-5165 Fax Number: NA Co-Submitting Member: Sun Microsystems Name of Contact Person: Philippe Goujard E-mail Address: philippe.goujard@uk.sun.com Telephone Number: +44 1276 689 414 Fax Number: +44 1276 677 121 Co-Submitting Member: Telcordia Technologies Name of Contact Person: B.Dasarathy E-mail Address: das@research.telcordia.com Telephone Number: +1 973 829 5038 Fax Number: +1 973 829 2645
Initial Expert Group Membership: Section 2: Request
2.1 Please describe the proposed Specification:In Operation Support Systems (OSS), the area of IP Billing is vast and complete standards or even de-facto standards in this area are lacking. Several products manage specific parts of Billing. They can be integrated into an end-to-end solution, but these custom integrated solutions are tremendously complex and difficult to achieve, due to the lack of integration standards. Therefore, the ability to reduce the integration effort via a set of standard, reusable software components to assemble OSS applications in a much shorter time is an appealing prospect for all players in the OSS marketplace. The OSS IP Billing API specification will define an API via the OSS through Java initiative that enables construction of total OSS solutions for IP Billing by assembling commercial-of-the-shelf components. The OSS IP Billing API will provide an interface between the billing data sources and the billing applications, i.e., the network charging elements, the mediation function and the billing system. The API will provide a standard interface between application components, so different vendors products can be easily combined. The API will therefore simplify data routing between components, for all types of billing records (CDRs, SDRs, IPDRs). The OSS IP Billing API will be applicable to data transmission initially and then for voice. It will apply to both 2.5 and 3G networks. The focus for the API will be wireless, but it is not wireless specific. As the market place and customer demands change, Service Providers who can quickly roll-out new services and actively bill for them, will find themselves in a very strong and competitive position. Being able to effectively bill for new services may require additional billing applications from one or more vendors. The IP Billing API will help reduce the time to market for these services and provide a faster time to revenue. The IP Billing API allows billing ISVs to focus on features and capabilities as discriminators, not integration and compatibility issues. This also allows Network Equipment Providers some measure of compatibility with a standard data format. Data format and protocol translations between equipment vendors are reduced. If the OSS IP Billing API is implemented by the previously mentioned products, system integrators and service providers can buy products from different sources and integrate them with no or minimal effort to build an end-to-end OSS solution for IP Billing. 2.2 What is the target Java platform? (i.e., desktop, server, personal, embedded, card, etc.)The target platform is Java 2 Platform, Enterprise Edition. 2.3 What need of the Java community will be addressed by the proposed specification?A number of software developers in the telecommunication industry are already using EJB components for their next-generation OSS software. Without some standardization conventions for these components, the industry runs the risk of proliferating similar components with slightly different APIs. Hence, standardizing these component APIs through a Java community process is an attractive proposition. 2.4 Why isn't this need met by existing specifications?Currently, no existing Java platform specification provides a standard API for OSS components. Specifically, no IP billing API exists that is defined within the OSS through Java Initiative. Existing APIs are generally vendor-proprietary. 2.5 Please give a short description of the underlying technology or technologies:The purpose of the IP Billing API specification is to define a standard API for Telecom Management applications, as described above. The API is considered to be independent of the network technology and will utilize existing standards as much as possible. The following standard bodies and fora will be considered when the API is defined and others may be added:
The OSS IP Billing API will be defined on top of J2EE. The most important J2EE APIs for this JCP will be the following:
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
