 
Use of JCP site is subject to the
JCP Terms of Use and the
Oracle Privacy Policy
 |
|
 JSRs: Java Specification Requests
JSR 195: Information Module Profile
The following information has been updated from the original request. 2015.04.13: The Maintenance Lead from Nokia Corporation has changed to Adamu Haruna. Maintenance Lead: Adamu Haruna E-Mail Address: adamu.haruna Telephone Number: - Fax Number: -
2013.05.24: Gemalto M2M has become the co-Maintenance Lead. Maintenance Lead: Thomas Lampart E-Mail Address: thomas.lampart Telephone Number: - Fax Number: - 2008.11.26: Cinterion Wireless Modules GmbH took over the Maintenance Lead role of this JSR. 2003.07.31: Siemens AG took over the Maintenance Lead role of this JSR.
Original Java Specification Request (JSR)
Identification |
Request |
Contributions
Section 1. Identification Submitting Member: Nokia Corporation and Siemens Mobile Name of Contact Person: Jari Lansio (Nokia Corporation) / Volker Bauche (Siemens Mobile) E-Mail Address: jari.lansio@nokia.com / volker.bauche@mch.siemens.de Telephone Number: +358 71 804 7025 (Jari Lansio) / +49-89-722-31644 (Volker Bauche) Fax Number: Specification Lead: Jari Lansio (Nokia Corporation) / Volker Bauche (Siemens Mobile) E-Mail Address: jari.lansio@nokia.com / volker.bauche@mch.siemens.de Telephone Number: +358 71 804 7025 (Jari Lansio) / +49-89-722-31644 (Volker Bauche) Fax Number: Initial Expert Group Membership: Motorola Supporting this JSR: Nokia 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 1.0, but that do not provide the graphical display capabilities required by MIDP 1.0. The Information Module Profile (IMP) will be a strict subset of MIDP 1.0, where the APIs relating to GUI functionality (the LCDUI) are simply removed. Functionality not already present in MIDP 1.0 is not anticipated or desired. 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 1.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 1.0, developer skills and application code can be easily transfered to IMs. Where devices do provide appropriate graphical display capabilities and user-input mechanisms, MIDP should be used. No alternative user-interface APIs should be standardized on top of the Information Module Profile. 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 1.0 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 1.0. Thus IMs cannot support all the semantics required by the MIDP 1.0 specification. IMs are also typically more memory constrained than Mobile Information Devices (MIDs), and either cannot store a full MIDP 1.0 implementation or are at least greatly disadvantaged by having to do so. 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 1.0 (JSR-037). The JSR will icreate a strict subset of the MIDP 1.0 specification. Features from the upcoming MIDP 2.0 specification (JSR-118) will not be used. 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 1.0 will retain the naming specified for MIDP 1.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 1.0 will apply. 2.8 Are there any security issues that cannot be addressed by the current security model?No. The MIDP 1.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 1.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?No 2.11 Please describe the anticipated schedule for the development of this specification.Community Review in January, 2003 2.12 Please describe the anticipated working model for the Expert Group working on developing this specification.The expert group will work primarily through e-mail and conference calls. It is anticipated that face-to-face meetings might prove unnecessary, but these will be called if needs arise. 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.Whitepaper J2ME (KVM): http://java.sun.com/products/cldc/wp Mobile Information Device Profile (MIDP 1.0):
http://jcp.org/jsr/detail/37.jsp Connected Limited Device Configuration (CLDC):
|
