• 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 Original JSR

The following 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@nokia.com

Telephone Number: -

Fax Number: -

2012.08.22:

The following section has been updated.

2.15 Please provide a description of the business terms for the Specification, RI and TCK that will apply when this JSR is final.

TCK:
- Available free of charge to qualified not-for-profit organizations and individuals in accordance with the JSPA, solely for developing and testing their own implementations and not allowing to test any third party or commercial for-profit implementations.
- The TCK is licensed, in line with the MSA licensing principles, with a flat fee of USD 50 000 for a license term of 3 years. This includes all maintenance updates and releases, if any. The license will be worldwide, non-exclusive and will be granted on an AS IS basis without any warranties or indemnities given and with the exclusion of all indirect and consequential damages. Major new releases, from new follower JSR, are subject to a separate license fee.
- The license grant will be for a term of not less than three (3) years.
- A license allowing licensees to test implementations on behalf of third parties as a free or for-fee commercial service under certain conditions shall be available. This right may result in a higher license fee.

2012.08.21:

North Sixty-One has become the co-Maintenance Lead.

Maintenance Lead: Erkki Rysä

E-Mail Address: jsr234@northsixtyone.com

Telephone Number: -

Fax Number: -

2012.07.12:

The Maintenance Lead from Nokia Corporation has changed to Wang Cheng.

Maintenance Lead: Wang Cheng

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

Telephone Number: -

Fax Number: -

2005.06.20:

With the Final Release, Matti Paavola became Maintenance Lead.

Identification | Request | Contributions

Section 1. Identification

Submitting Member: Nokia

Name of Contact Person: Antti Rantalahti

E-Mail Address: antti.rantalahti@nokia.com

Telephone Number: +358 7180 36705

Fax Number: +358 7180 37133

Specification Lead: Antti Rantalahti

E-Mail Address: antti.rantalahti@nokia.com

Telephone Number: +358 7180 36705

Fax Number: +358 7180 37133

Initial Expert Group Membership:

Supporting this JSR:

Nokia Corporation
Sharp Labs of America
Ericsson Mobile Platforms
Motorola
Qsound Labs, Inc.
Siemens AG
Sun Microsystems, Inc
Symbian Ltd
Texas Instruments Inc
Vodafone Group PLC

Section 2: Request

2.1 Please describe the proposed Specification:

This specification will define an optional package for advanced multimedia functionality which is targeted to run as a supplement in connection with MMAPI (JSR-135) in J2ME/CLDC environment.
Java equipped terminals are evolving into general multimedia and entertainment platforms. Features like camera and radio which have traditionally belonged into different device categories are now integrated into same terminals. Increase in the processing power of modern mobile phones allow more sophisticated media processing capabilities. Displays will remain relatively small due physical limitations but rich aural experience can be achieved without adding the physical size of the terminals.
The purpose of this API is to give access to multimedia functionality of the modern mobile terminals. Specifically, better support for camera and radio and access to advanced audio processing will be introduced but it’s possible to add other functionality as well.

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

The API requires MMAPI (JSR-135) and therefore the main target platform of the API is J2ME/CLDC/MIDP but the API is usable as it is in CDC as well.

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

This specification will bring the following capabilities to the mobile terminals with J2ME/CLDC support:

- Access for camera specific controls like visual settings (brightness, contrast), flashlights, lighting modes and zooming.
- Proper access to radio and other channel/frequency based media sources including RDS (radio data system)
- Access to advanced audio processing capabilities like equalizer, audio effects, artificial reverberation and positional 3D audio. Dynamically changing audio resources are adressed as well.
- Media output direction. For example, the ability to choose whether the audio is played out from speaker of from headset.

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

MMAPI (JSR-135) is the media package for J2ME/CLDC environment which introduces basic playback functionality for audio and video. It allows media players to be created for various sources including camera and radio but it does not offer any specific methods to control them.
For camera, MMAPI allows video to be shown on the screen and image capturing by copying the image. For radio MMAPI allows player to be created on some specific frequency but a common procedure of changing a channel requires player to be closed and another one to be created on a different channel.
For audio processing MMAPI offers only setting of the volume. Even quite primitive equalizer with bass and treble settings is impossible to access from Java with current API’s.
MMAPI is a framework that was designed to be easily extensible. This JSR utilizes the framework by introducing control for advanced multimedia features.

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

The API is targeted to work as a supplement in connection with MMAPI . The playback architecture of MMAPI consists of Players to render the media (i.e. play it out) and Controls that are used to manage different features of Player and playback. This API will consist of a set of Controls to introduce the new functionality. Changing the existing classes and interfaces of MMAPI is not in the scope of this JSR.

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

Packages will be defined under javax.microedition.media. For example, camera functionality can be in javax.microedition.media.camera

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

No

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: Q2/2004
Public Review Draft: Q3/2004
Final specification: Q4/2004

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

E-mail, teleconference, and face-to-face discussions as needed and as appropriate

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.

RI and TCK will be delivered separately as stand-alone packages.

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.

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 Nokia 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 will charge a single one time fee of max $50 000 USD and annual maintenance fee, max $20 000 for a term of four years.
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 (esp. from new follower JSR) might be subject to additional single one time fee. Using the TCK for testing of implementations on behalf of third parties will be allowed, though, be subject to a higher fee which is capped at the sum of license fees due in accordance with license fees as desribed above in this section, if the third parties would have directly licensed the TCK from Nokia.
For RI in source code form we will charge one time access fee, and annual maintenance fee. Maintenance covers bug fixes, updates and new releases necessary due to spec changes, and when made generally available by specification lead.
Binary license is free of charge.

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.

MMAPI 1.1 specification http://jcp.org/en/jsr/detail?id=135

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

This API is a supplement in connection with MMAPI.