• JSRs by Platform
• JSRs by Technology
• JSRs by Stage
• JSRs by Committee
• List of All JSRs



Register for Site

Use of JCP site is subject to the JCP Terms of Use and the Oracle Privacy Policy


• About JCP
  • Program Overview
  • JCP Process Document
  • Calendar
  • JCP Members
  • Executive Committee
  • Elections
• Get Involved
  • Overview
  • Becoming a JCP Member
  • Java in Education
• Community Resources
  • Overview
  • Tutorials
  • JCP Podcasts
  • Spec Lead Guide
  • TCK Tool & Info
  • License Reference
• Community News
  • News
  • Programs & Awards
  • Press Releases
  • Success Stories
• FAQ
• Contact Us

Updates to the Java Specification Request (JSR)

The following information has been updated from the original JSR:

2012.07.12:
The Maintenance Lead from Nokia Corporation has changed to Wang Cheng. The Motorola Maintenance Lead is unchanged.

Maintenance Lead: Wang Cheng (Nokia Corporation)

E-Mail Address: cheng.9.wang@nokia.com

Telephone Number: -

Fax Number: -

2007.07.01: The Maintenance Lead of the JSR from Nokia changed on 2007-07-01:

Maintenance Lead: Erkki Rysa (Nokia Corporation) / Venkat Amirisetty (Motorola)

E-Mail Address: JSR-232-TCK-RI-support@nokia.com / -

Telephone Number: +358 71 800 8000 / -

Fax Number: +358 71 807 4160 / -

Original Java Specification Request (JSR)

Identification | Request | Contributions | Additional Information

Section 1. Identification

Submitting Member: Nokia Corporation

Name of Contact Person: Jon Bostrom

E-Mail Address: jon.bostrom@nokia.com

Telephone Number: +1 858 663 1511

Fax Number: +1 775 849 0984

Specification Lead: Gabor Paller and Sanjay Gupta

E-Mail Address: gabor.paller@nokia.com and sanjay.gupta@motorola.com

Telephone Number: +36 20 936 9597 and +1 847 523 6230

Fax Number: +36 1 216 7689

Initial Expert Group Membership:

Nokia
Motorola
IBM

Supporting this JSR:

Nokia
Motorola
IBM

Section 2: Request

2.1 Please describe the proposed Specification:

This Specification will define a component management framework that will allow mobile devices based on the J2ME ^TM Connected Device Configuration to evolve and adapt their capabilities by installing new components on demand. These components can be a combination of active elements with no user interaction (services), active elements with user interfaces (applications), and shared libraries (both native and Java). The framework will enforce a predictable lifecycle model for these sharable components that will encompass install, start, stop, update, and uninstall. The framework will also provide for multiple applications to coordinate the use of single-access resources such the device display. In order to ensure a safe environment, these components will be controlled via a mandatory security model based on the Java^TM 2 Platform security model.
In order to minimize fragmentation, accelerate adoption, and reduce time to market, this Specification will reference existing standards and implementations wherever possible. In order to ensure backward compatibility this Specification will also describe how Mobile Information Device Profile 2.0 MIDlet suites will be managed.

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

This Specification is targeted towards devices capable of supporting at least the J2ME (TM) Connected Device Configuration and the J2ME^TM Foundation Profile.

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

Mobile devices based on the J2ME^TM Connected Device Configuration are coming to market very quickly, and the J2ME (TM) Connected Device Configuration brings new capabilities and challenges. The J2ME^TM Connected Device Configuration offers enhanced capabilities over the J2ME^TM Connected, Limited Device Configuration such as the capability to install new, shared libraries after manufacture and the ability to run multiple, simultaneous applications. These and other new powerful capabilities require a correspondingly powerful management environment.
The management framework described by this Specification will allow developers to create applications as simple, interoperable, sharable components that can be dynamically deployed. Because these components are installable and manageable as aftermarket items, the solution creates new business opportunities for members of the value chain including independent software developers, carriers, device manufacturers, and enterprises.

2.4 Why isn't this need met by existing specifications?

Today, the preponderance of phones in the market can only support "monolithic" Mobile Information Device Profile 2.0 applications. This market is being addressed by activities in the Java^TM Technology for the Wireless Industry expert group. Existing specifications also do not deal with the management requirements of the J2ME^TM Connected Device Configuration. If these details are left up to each implementer, the resulting environment will not be predicable for developers and management systems and thus will inhibit adoption.

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

- J2ME^TM Connected Device Configuration ( http://www.jcp.org/en/jsr/detail?id=36)
- J2ME^TM Foundation Profile ( http://www.jcp.org/en/jsr/detail?id=46)
- The Open Mobile Alliance Device Management ( http://www.openmobilealliance.org/devicemanagement.html)
- Open Systems Gateway Initiative (OSGi^TM) Service Platform ( http://www.osgi.org/resources/spec_overview.asp)
- Mobile Information Device Profile 2.0 ( http://www.jcp.org/en/jsr/detail?id=118)

Note: the J2ME^TM Connected Device Configuration 1.1 (JSR-218) and the J2ME^TM Foundation Profile 1.1 (JSR-219) may be considered if these JSRs are public and final before this Specification completes.

2.6 Is there a proposed package name for the API Specification? (i.e., javapi.something, org.something, etc.)

TBD by Expert Group.

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

Only in those dependencies imposed by the underlying Java^TM Configurations and Profiles referenced.

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.

Community Review Draft: Early Q1 2004
Public Review Draft: Q1 2004
Completion: Q1-Q2/2004

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

As typical, we anticipate a mixture of mailing list and occasional face-to-face or teleconference meetings.

2.13 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 delivered stand-alone.

2.14 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.15 Please provide a description of the business terms for the Specification, RI and TCK that will apply when this JSR is final.

The Specification Lead will publish the Specification without restriction for those who wish to read, study, or implement the Specification.

Likewise, the Specification Lead will deliver the RI and TCK under reasonable and non-discriminatory terms to implementers. In particular:
- The TCK will be licensed separately from the RI.
- Both the RI and the TCK, will be licensed subject to a one-time fee having a cap of a maximum of $50,000 (USD), or at the option of the licensee subject to royalties based on the number of copies of a tested program that is distributed, but with per unit royalties capped at the one-time fee calculated to defray the direct cost of creating and maintaining both RI and TCK and assuming a reasonable number of prospective licensees.
- All licenses will have at least a term of three years.
- The TCK license will allow testing on behalf of third parties subject to a respectively higher fee or royalties as applicable.
- Maintenance and upgrade releases will follow the same licensing practices as listed above.

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.

See Section 2.5

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

The OSGi Service Platform and the OMA DM specifications provide the basis for building the standard for end-to-end management of mobile handsets that use J2ME^TM Connected Device Configuration and the J2ME^TM Foundation Profile.

Section 4: Additional Information (Optional)

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

The Specification Lead will track revisions in both the Open Mobile Alliance and OSGi Alliance standards bodies as they apply to this JSR and will publish updates to this JSR as those standards are updated.