JSRs: Java Specification Requests
JSR 325: IMS Communication Enablers (ICE)
JCP version in use: 2.11
Java Specification Participation Agreement version in use: 2.0
This specification will define a high level, IMS Communications Enabler framework API that will provide Java ME based devices effortless access to a set of essential IMS Communication Enablers.
Section 1. Identification
Submitting Member: Ericsson AB
Name of Contact Person: Martin Johansson
E-Mail Address: martin.z.johansson
Telephone Number: +46 705 94 42 07
Fax Number: +46 46 23 12 38
Specification Lead: Martin Johansson, Niclas Palm
E-Mail Address: martin.z.johansson
Telephone Number: +46 705 94 42 07, +46 702 22 35 67
Fax Number: +46 46 23 12 38
Initial Expert Group Membership:
Supporting this JSR:
Section 2: Request
2.1 Please describe the proposed Specification:
This specification will define a high level, IMS Communications Enabler framework API that will provide Java ME (Connected Limited Device Configuration-CLDC and Connected Device Configuration-CDC) based devices effortless access to a set of essential IMS Communication Enablers. This specification will at a minimum aim to provide the capabilities to expose a set of the high level IMS Communication Enablers that is anticipated by the mobile industry and IMS Community:
In order to accelerate adoption and time to market this specification will align, and leverage existing specifications both inside the JCP as well as specifications being developed in the industry.
2.2 What is the target Java platform? (i.e., desktop, server, personal, embedded, card, etc.)
The main target Java platform is the Java ME. This optional package will run on both configurations CLDC and CDC. This API will be typically used in conjunction with the Mobile Information Device Profile (MIDP), but it can be used with other profiles. We will also investigate the possibility to support the Java SE platform.
2.3 The Executive Committees would like to ensure JSR submitters think about how their proposed technology relates to all of the Java platform editions. Please provide details here for which platform editions are being targeted by this JSR, and how this JSR has considered the relationship with the other platform editions.
This API targets Java ME.
2.4 Should this JSR be voted on by both Executive Committees?
2.5 What need of the Java community will be addressed by the proposed specification?
This API provides high-level access to IMS Communication Enablers (ICE) to facilitate rapid development of innovative applications using standardized IMS services like MMTel and GLM on Java ME devices. The ICE API addresses the enablers part of the initial JSR-281 scope that eventually had to be left out. The enablers in the ICE API will make use of the framework defined in JSR-281, used by the CoreService in JSR-281.
2.6 Why isn't this need met by existing specifications?
Existing JSRs are either low-level (such as JSR-180) or high-level but specific to a particular application (such as JSR-186/187). JSR-180 requires detailed SIP knowledge and focuses a lot on P2P SIP based communication. Additionally usage of JSR 180 for applications utilizing the IMS, can lead to security issues if IMS conventions are not observed by the application developer. A high-level API does not only minimize those security problems but also reduces the risk to affect the operational safety of the IMS by restricting applications to proper behavior.
2.7 Please give a short description of the underlying technology or technologies:
IMS is a multimedia platform for packet-oriented access networks such as UMTS, EDGE, GPRS or W-LAN standardized by the 3GPP (3rd Generation Partnership Project). It enables mobile operators to offer numerous voice, multimedia and data services based on IP (Internet Protocol), SIP (Session Initiation Protocol) and 3GPP Release 6 & 7.
An IMS subscriber can make use of a whole host of interaction and communication options - from games for the entertainment sector to business applications - with a single login. IMS offers a variety of basic network services, such as session control services (including registration, routing and roaming), secure authentication, flexible charging and payment, quality of service, presence and Push-to-Talk over Cellular.
2.8 Is there a proposed package name for the API Specification? (i.e., javapi.something, org.something, etc.)
2.9 Does the proposed specification have any dependencies on specific operating systems, CPUs, or I/O devices that you know of?
2.10 Are there any security issues that cannot be addressed by the current security model?
No. The platform that this API is implemented upon needs to have a security framework that can be used to enforce the appropriate policy. Defining the security framework is out of the scope for this JSR. For example, the MIDP2 and MIDP3 security frameworks can be re-used. In addition, the applications can rely on the security mechanisms provided by the IMS system (e.g. authentication) but this has to be supported by the underlying implementation.
2.11 Are there any internationalization or localization issues?
2.12 Are there any existing specifications that might be rendered obsolete, deprecated, or in need of revision as a result of this work?
2.13 Please describe the anticipated schedule for the development of this specification.
Expert Group Formation: Q2 2008
2.14 Please describe the anticipated working model for the Expert Group working on developing this specification.
The Expert Group will conduct its work via direct e-mail and mailing lists. We will have periodic phone conferences where technical discussions are encouraged! There will also be face-to-face meetings for the major milestones and for critical decisions. Decisions will be made by technical consensus. The Expert Group will take part of the specification work as discussing and developing Use Cases, requirements and the API. The Expert Group will review the API in between and prior to all milestones of this JSR.
2.15 It is important to the success of the community and each JSR that the work of the Expert Group be handled in a manner which provides the community and the public with insight into the work the Expert Group is doing, and the decisions that the Expert Group has made. The Executive Committees would like to ensure Spec Leads understand the value of this transparency and ask that each JSR have an operating plan in place for how their JSR will address the involvement of the community and the public. Please provide your plan here, and refer to the Spec Lead Guide for a more detailed description and a set of example questions you may wish to answer in your plan.
The expert group will remain open for new nominations until Early Draft Review (EDR). Interim drafts of the specification will be made available on the JSR community page. The schedule will be defined by the expert group. Additionally the observer alias will be used, to inform interested members of the community about progress and open issues in this JSR. The users@jsp-spec-public mailing list will be open to the public to discuss issues related to the JSP specification.
2.16 Please describe how the RI and TCK will de delivered, i.e. as part of a profile or platform edition, or stand-alone, or both. Include version information for the profile or platform in your answer.
The RI and TCK will be licensed separately, as stand-alone optional packages for the JavaTM ME platform.
2.17 Please state the rationale if previous versions are available stand-alone and you are now proposing in 2.13 to only deliver RI and TCK as part of a profile or platform edition (See sections 1.1.5 and 1.1.6 of the JCP 2 document).
2.18 Please provide a description of the business terms for the Specification, RI and TCK that will apply when this JSR is final.
These are initial commercial terms to be used and remain subject to the execution of final legal agreements covering the subject matter hereof.
RI and TCK will be licensed to all interested parties, TCK and RI will be licensed separately. For TCK we plan to introduce a single one time fee of max $50,000 and annual maintenance fee of max $20,000 for a term of three years. TCK will include both binary environment and source code of the test suite.
We will investigate other licensing models, during the development of this JSR; for the Specification, as well as for the RI and TCK.
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.
OMA Presence SIMPLE Specification, Approved Version 1.0.1
3.2 Explanation of how these items might be used as a starting point for the work.
Section 4: Additional Information (Optional)
4.1 This section contains any additional information that the submitting Member wishes to include in the JSR.