JSRs: Java Specification Requests
JSR 271: Mobile Information Device Profile 3
This JSR will specify the 3rd generation Mobile Information Device
Profile, expanding upon the functionality in all areas as well as
improving interoperability across devices.
Status: In Progress
Stage
Start
Finish
Expert Group Formation
22 Mar, 2005
JSR Review Ballot
08 Mar, 2005
21 Mar, 2005
JCP version in use: 2.6
Java Specification Participation Agreement version in use: 2.0
Please direct comments on this JSR to: jsr-271-comments@jcp.org
Specification Lead
Jim Van Peursem
Motorola
Expert Group
Motorola
I would like to join this Expert Group
Original Java Specification Request (JSR)
Request |
Section 1. Identification
Submitting Member: Motorola
Name of Contact Person: Dr. James E. Van Peursem
E-Mail Address: Jim.Van.Peursem@motorola.com
Telephone Number: +1 847 523 1051
Fax Number: +1 847 523 2854
Specification Lead: Dr. James E. Van Peursem
E-Mail Address: Jim.Van.Peursem@motorola.com
Telephone Number: +1 847 523 1051
Fax Number: +1 847 523 2854
Initial Expert Group Membership:
Initial EG membership:
* Aplix
* Cingular
* Ericsson Mobile Platforms (EMP)
* Esmertec
* IBM
* Intel
* Nokia
* Orange France
* Philips
* RIM
* Siemens
* Sony-Ericsson Mobile
* Sun Microsystems, Inc
* T-Mobile
* Vodafone
Supporting this JSR:
* Aplix
* Cingular
* Ericsson Mobile Platforms (EMP)
* Esmertec
* IBM
* Intel
* Orange France
* Philips
* RIM
* Siemens
* Sony-Ericsson Mobile
* Sun Microsystems, Inc
* T-Mobile
* Vodafone
Section 2: Request
2.1 Please describe the proposed Specification:
This JSR will build upon the success of MIDP2 by enhancing the Profile with the following additions/changes:
* Enable and specify proper behavior for MIDlets on each of CLDC, CDC, and OSGi, for example:
o Enable multiple concurrent MIDlets in one VM
o Specify proper firewalling, runtime behaviors, and lifecycle management issues for MIDlets
o Enable background MIDlets (e.g. UI-less)
o Enable ?auto-launched? MIDlets (e.g. started at platform boot time)
o Enable inter-MIDlet communications
* Enable shared libraries for MIDlets
* Tighten spec in all areas to improve cross-device interoperability
* Increase functionality in all areas. E.g.
o Improve UI expressability and extensibility
o Better support for devices with larger displays
o Enable MIDlets to draw to secondary display(s)
o Enable richer and higher performance games
o Secure RMS stores
o Removable/remote RMS stores
o IPv6
o Multiple network interfaces per device
* Specify standard ways for doing MIDlet provisioning through other
means (e.g. OMA (SyncML) DM/DS, Bluetooth, removable media, MMS,
JSR-232, etc.)
* Extensive device capabilities query
* Localization & Internationalization (if appropriate, integrating/augmenting JSR-238 as needed)
A key design goal of MIDP3 will be backward compatibility with MIDP2 content.
2.2 What is the target Java platform? (i.e., desktop, server, personal, embedded, card, etc.)
MIDP on Mobile Handsets
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.
The target platform is the MID Profile in J2ME.
2.4 Should this JSR be voted on by both Executive Committees?
No
2.5 What need of the Java community will be addressed by the proposed specification?
This JSR will specify the 3rd generation Mobile Information Device
Profile, expanding upon the functionality in all areas as well as
improving interoperability across devices.
2.6 Why isn't this need met by existing specifications?
N/A
2.7 Please give a short description of the underlying technology or technologies:
CLDC, CDC, OSGi, and MIDP 2.0
2.8 Is there a proposed package name for the API Specification? (i.e., javapi.something, org.something, etc.)
javax.microedition.*
2.9 Does the proposed specification have any dependencies on specific operating systems, CPUs, or I/O devices that you know of?
No
2.10 Are there any security issues that cannot be addressed by the current security model?
No
2.11 Are there any internationalization or localization issues?
No
2.12 Are there any existing specifications that might be rendered
obsolete, deprecated, or in need of revision as a result of this work?
Yes. JSR-118 MIDP 2.0
2.13 Please describe the anticipated schedule for the development of this
specification.
The targeted schedule for the JSR is as follows:
- Expert Group formation: March 2005
- Early Draft Review: September 2005
- Public Review: January 2006
- Proposed Final Draft: March 2006
- Final Approval Ballot: May 2006
2.14 Please describe the anticipated working model for the Expert Group working on developing this
specification.
The Expert Group will conduct its work in a similar fashion to the
MIDP 2 Expert Group. That is, the primary means of communication will
be via email list(s) and web site(s). In addition, periodic
face-to-face meetings will be held approximately every 6-8 weeks, and
phone conferences as needed for special issues that need to be resolved
between meetings. Decisions will be made by technical consensus.
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.
Transparency plan:
a) All members of the expert group will be allowed to subscribe to and
participate in discussions on the email list(s) as they choose. The
face-to-face meetings will be open to all active participants with a
limit of one representative per company in order to keep the meeting
space to a reasonable size (i.e. approx 30-35 people). Any free seats
will be made available to Observers on some kind of simple lottery-type
system, similar to how MIDP2 was organized.
b) The specification lead will, on a quarterly basis, provide a brief
JSR status to the JCP PMO, for publication to the Java community. This
will include the current schedule for the JSR and notes on any major
events that have occurred in the previous quarter.
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.
An independent RI and TCK will be produced as a part of this JSR with each being licensed separately.
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).
N/A
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 terms only represent the initial commercial terms to be used
and remain subject to the execution of final legal agreements covering
the subject matter hereof to be determined by Motorola at its sole
discretion.
We will license to all interested parties.
Independent implementations will be allowed - TCK and RI will be licensed separately.
For TCK we plan to charge a single one-time fee for access and an
annual maintenance fee for a term of four years. The actual size of the
license fees will be based on the associated development cost, with a
target of cost recovery. Since MIDP is much larger and more complex
than most other JSRs, we anticipate the fees of $100,000 USD for
one-time fee and $50,000 for annual maintenance fee.
TCK will include both binary environment and source code of the test suite.
Maintenance fee covers limited basic support, first level TCK appeals
process, bug fixes when available and updates, which are due to changes
in the specification. Major new releases may be subject to additional
single one time fee.
For RI in source code form we will charge a per unit license fee.
Maintenance releases will cover bug fixes, updates and new releases
necessary due to spec changes, and when made generally available by
specification lead.
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.
JSR-118 MIDP 2.0
3.2 Explanation of how these items might be used as a starting point for the work.
This specification will serve as the basis for beginning the work,
which will be extended, enhanced, and clarified. Note that backward
compatibility with specified MIDP 2.0 behaviors will be of paramount
importance wherever possible.
Section 4: Additional Information (Optional)
4.1 This section contains any additional information that the submitting Member wishes to include in the JSR.
