The Java Community Process(SM) Program - JSRs: Java Specification Requests - detail JSR# 37

Specification Leads

Brian Deuser Motorola

Expert Group

America Online (AOL) Ericsson Inc. Espial Group, Inc.

Fujitsu Limited Hitachi, Ltd. KDDI Corporation

Matsushita Electric Industrial Co., Ltd. Mitsubishi Electric Corp. Motorola

NEC Networks Development Laboratories Nokia Corporation Oracle

Research In Motion, LTD (RIM) Samsung Electronics Corporation Sharp Corporation

Siemens AG Softbank Mobile Corporation Sony

Sun Microsystems, Inc. Symbian Ltd Telcordia Technologies, Inc.

Submitting Participant: Motorola, Inc.

Name of Contact Person: Mark VandenBrink

E-Mail Address: mark.vandenbrink@motorola.com

Telephone Number: +1 (512) 895-6064

Fax Number: +1 (512) 895-3798

2.1 Description of proposed Specification:

Under the new Java^TM 2 Micro Edition (J2ME^TM) technology, two notions have been introduced: a configuration, and a profile.? A configuration is defined as the combination of a Virtual Machine (VM) and "core" APIs that represent an underlying development platform for a broad class of devices.? A profile is defined as a set of APIs for a specific vertical market and relies upon an underlying configuration's capabilities to create new, market-specifc APIs.

This specification will define a profile that will extend and enhance the "J2ME Connected, Limited Device Configuration" (JSR-000030). By building upon this configuration, this profile will provide a standard platform for small, resource-limited, wireless-connected mobile information devices characterized as follows:

• 512K total memory (ROM + RAM) available for Java runtime and libraries
• Limited power, typically battery operated
• Connectivity to some type of wireless network with possibly limited bandwidth
• User interfaces with varying degrees of sophistication

This profile will enable application development within mobile, wireless-connected devices like cellular phones and two-way pagers. In addition to being wireless-connected, these devices have small displays, limited input devices, limited local storage, battery life, and CPU power. Two types of devices will be accommodated: mobile information appliances and voice communication devices.

This profile, in conjunction with the "J2ME Connected, Limited Device Configuration", will allow applications on these devices targeted at satisfying the mass consumer market demand for wireless access to at-your-fingertips information, service, and entertainment (e.g., sport scores, financial information, e-commerce, games, inter-personal communication, etc.)

Wherever possible, this profile will utilize the core functionality provided by the "J2ME Connected, Limited Device Configuration." Potential APIs that will need to be created, extended, or enhanced include the following:

• Display toolkit suitable for limited size and depth displays.
• User input methods such as pen, buttons, keyboard, etc.
• Persistent data storage for applications, data, and configuration information.
• Messaging (e.g., SMS, e-mail, etc.)
• Networking, such as datagram and connection oriented services.
• Security, as it applies to mobile information devices. (e.g., protecting the integrity of the devices and networks from rogue applications, end-to-end security and data integrity, etc.)
• Wireless telephony (i.e., functions for placing and receiving voice calls, tracking call states, etc.).

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

J2ME Connected, Limited Device Configuration as defined by JSR-000030

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

This specification will create a new standard API for wireless-connected devices running the J2ME Connected, Limited Device Configuration

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

Existing APIs, such as JavaPhone, are predicated on the capabilities and memory requirements of larger JVMs such as EmbeddedJava and Personal Java.

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

See section 2.1 for expected underlying device technologies.

2.6 Is there a proposed package name for the API Specification?

None identified at this time.

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

None identified at this time.

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

Due to the class of devices addressed by this specification, it is expected that existing security models will be too heavy weight; therefore, they will have to either be lightened or reworked; however, wherever possible, this specification will rely upon features of the J2ME Connected, Limited Device Configuration.

2.9 Are there any internationalization or localization issues?

Wherever possible, this specification will rely upon features of the J2ME Connected, Limited Device Configuration to implement internationalization and localization.

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

None identified at this time.

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.

• J2ME Connected, Limited Device Configuration
• JavaPhone
• Java Telephony API
• Mobile Network Computer Reference
• Mobile Station Application Execution Environment
• ECTF

The JavaPhone, Java Telephony API, and MNCR specifications, while developed for the PersonalJava^TM platform, and thus too large, are representative of the "state of the art" for wireless API definitions. The goal will be to provide similar (possibly subsets of) functionality to the above APIs in a much smaller size.