Find JSRs
Submit this Search

Ad Banner

Summary  |  Proposal  |  Detail (Summary & Proposal)
JSRs: Java Specification Requests
JSR 228: Information Module Profile - Next Generation (IMP-NG)

Stage Access Start Finish
Final Release Download page 30 Nov, 2005  
Final Approval Ballot View results 13 Sep, 2005 26 Sep, 2005
Proposed Final Draft Download page 28 Apr, 2005  
Public Review Ballot View results 01 Mar, 2005 07 Mar, 2005
Public Review Download page 01 Feb, 2005 07 Mar, 2005
Early Draft Review Download page 02 Nov, 2004 02 Dec, 2004
Expert Group Formation   23 Sep, 2003  
JSR Review Ballot View results 09 Sep, 2003 22 Sep, 2003
Status: Final
JCP version in use: 2.6
Java Specification Participation Agreement version in use: 2.0

This specification will define a profile that will extend and enhance the "J2METM Information Module Profile" (JSR-195).

Please direct comments on this JSR to the Spec Lead(s)

Specification Leads
  Thomas Lampart Cinterion Wireless Modules GmbH
Expert Group
  Aplix Corporation Cinterion Wireless Modules GmbH Esmertec AG
  IOPSIS Software Inc. Ortiz, C. Enrique Sun Microsystems, Inc.

Updates to the Original JSR

The following information has been updated from the original proposal.

2013.05.24: Gemalto M2M has become the Maintenance Lead.

Maintenance Lead: Thomas Lampart

E-Mail Address:

Telephone Number: -

Fax Number: -

2008.11.26: Cinterion Wireless Modules GmbH has taken over the Maintenance Lead role for this JSR.

Maintenance Lead: Thomas Lampart, Cinterion Wireless Modules

E-Mail Address:

Telephone Number: +49 30 31102 8231

Fax Number: +49 30 31102 8305

Original Java Specification Request (JSR)

Identification | Request | Contributions | Additional Information

Section 1. Identification
Please note that this information has been updated from this original proposal.

Submitting Member: Siemens Mobile and Nokia Corporation

Name of Contact Person: Volker Bauche (Siemens Mobile) / Jari Lansio (Nokia Corporation)

E-Mail Address: /

Telephone Number: +49-89-722-31644 (Volker Bauche) / +358 71 804 7025 (Jari Lansio)

Fax Number: +49-89-722-35087 (Volker Bauche) / +358 42 559 7025(Jari Lansio)

Please note that this information has been updated from this original proposal.

Specification Lead: Volker Bauche (Siemens Mobile) / Jari Lansio (Nokia Corporation)

E-Mail Address: /

Telephone Number: +49-89-722-31644 (Volker Bauche) / +358 71 804 7025 (Jari Lansio)

Fax Number: +49-89-722-35087 (Volker Bauche) / +358 42 559 7025(Jari Lansio)

Initial Expert Group Membership:

Siemens Mobile
Nokia Corporation
Motorola Inc.
Sun Microsystems, Inc.

Supporting this JSR:

Siemens Mobile
Nokia Corporation
Motorola Inc.
Sun Microsystems, Inc

Section 2: Request

2.1 Please describe the proposed Specification:

This JSR will define a J2ME profile targeting embedded networked devices that wish to support a Java runtime environment similar to the Mobile Information Device Profile (MIDP) version 2.0, but that do not provide the graphical display capabilities required by MIDP 2.0.
The Information Module Profile - Next Generation (IMP-NG) will be a strict subset of MIDP 2.0, where at least the APIs relating to GUI functionality (the LCDUI) are removed. Functionality not already present in MIDP 2.0 is not anticipated or desired.
The primary focus of this "IMP_NG" specification scope will address:

    - Backward compatibility with IMP
    - Maintain tight footprint objectives to limit growth in the core APIs
    - Overtake all functional areas from MIDP 2.0, which are useful for embedded networked devices, on particular
    - The domain security model, including signing of applications and verification of certificates
    - HTTPS and secure networking
    - Network connectivity via sockets and datagrams
    - OTA Provisioning
    - Push architecture: external events and messages routed to appropriate IMlets

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

The J2METM platform.

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

This JSR addresses the needs of users of Information Modules (IMs). Such devices include, for example, modems, home electronics devices, and industrial metering devices. Their users want access to a Java runtime environment to ease development and increase application portability; however these devices do not provide the graphical display capabilities or user-input mechanisms required by MIDP 2.0 When outfitted with an appropriate Java runtime environment, such devices become much more broadly and easily applicable, increasing time to market and economy of scale. By basing the Java runtime environment on MIDP 2.0, developer skills and application code can be easily transferred to IMs.
IMP (JSR-195) addressed this kind of devices, and therefore opened a new market for Java. This very dynamic market has a strong need in usage of the advanced features as defined in MIDP 2.0. It is the intention of IMP-NG to meet those needs.
As for IMP, it is a very important precondition to avoid fragmentation in the J2ME profile landscape. That?s why a similar condition is formulated also for IMP-NG: where devices do provide appropriate graphical display capabilities and user-input mechanisms, MIDP 2.0 should be used. No alternative user-interface APIs should be standardized on top of the Information Module Profile NG.

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

IMs typically have no user interface, or at most have a primitive one using simple mechanisms such as buttons or LEDs. While MIDP supplies the functionality that IMs need (e.g. networking APIs), IMs typically lack the minimum display capabilities (96x54 pixels) and input devices (a one-or two-handed keyboard or touch screen) required by MIDP. Thus IMs cannot support all the semantics required by the MIDP 1.0 or 2.0 specifications.
IMs are also typically more memory constrained than Mobile Information Devices (MIDs), and either cannot store a full MIDP 1.0 or MIDP 2.0 implementation or are at least greatly disadvantaged by having to do so.
While IMP (JSR-195) opened the possibility of using all non-graphical features of MIDP 1.0 to IMs, the same need now exists for the non-graphical features of MIDP 2.0. It is this gap, that should be closed by IMP-NG.

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

The technology specified through this JSR will derive from the Mobile Information Device Profile version 2.0 (JSR-118). The JSR will create a strict subset of the MIDP 2.0 specification.
The dependency of the profile will be the Connected Limited Device Configuration version 1.0 (JSR-030).

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

APIs used from MIDP 2.0 will retain the naming specified for MIDP 2.0.

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

Except for the expected absence of graphical display capabilities and user-input mechanisms, the restrictions and prerequisites of MIDP 2.0 will apply.

2.8 Are there any security issues that cannot be addressed by the current security model?

No. The MIDP 2.0 solutions will be used directly.

2.9 Are there any internationalization or localization issues?

No. To the extent internationalization or localization apply in the absence of graphical display capabilities and user-input mechanisms, the MIDP 2.0 solutions will be used.

2.10 Are there any existing specifications that might be rendered obsolete, deprecated, or in need of revision as a result of this work?


2.11 Please describe the anticipated schedule for the development of this specification.

Community Review in Q1/2004
Final Approval Ballot at begin of Q2/2004

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

It is anticipated that a combination of email discussion, feedback on regular drafts, conference calls and face-to-face meetings will work well.

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.

Stand-alone delivery, on the same platform as MIDP 2.0.

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).


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 business terms are very likely to be similar to those of JSR-195 (Information Module Profile):
Sun made the JSR 195 TCK and RI available for license separately:
* TCK:
- Available free of charge to qualified not-for-profits organizations and individuals
- Per unit royalty fee, with an annual maintenance fee.
* RI:
- Per unit royalty fee, with an annual maintenance fee.
Please be aware, that the general issue of licensing terms is about to be discussed, which could have influence on the JSR-195 business terms
and even the terms of this new JSR. Besides, the final business terms will be determined by the EG in discussions and may therefore be subject of change.

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.

White paper J2ME (KVM):
Mobile Information Device Profile (MIDP 2.0):
MIDP 2.0 Reference Implementation
Connected Limited Device Configuration (CLDC):
Information Module Profile (IMP):

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

The intention of IMP-NG is it to become a strict subset of MIDP 2.0. MIDP 2.0 is a profile running on the CLDC configuration (as IMP-NG also will). The IMP-NG profile is also an advanced profile for information modules, like IMP also is.

Section 4: Additional Information (Optional)

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