Printed: Apr 20, 2024
From: http://www.jcp.org/en/jsr/detail?id=205
|
Specification Leads | |||
Marquart Franz | Siemens AG | ||
Expert Group | |||
Aplix Corporation | Cellon France SAS | Cingular Wireless | |
Esmertec AG | iaSolution Inc. | Intel Corp. | |
IOPSIS Software Inc. | Kada Systems | Macromedia, Inc. | |
Motorola | Nokia Corporation | Sharp Corporation | |
Siemens AG | Sony Ericsson Mobile Communications AB | Sun Microsystems, Inc. | |
Symbian Ltd | Telefonica Of Spain | Vodafone Group Services Limited |
The following updates have been made to the original request.
Maintenance Lead: Marquart Franz
E-Mail Address: marquart.franz
Telephone Number: +49 89 636 48767
Fax Number: +49 89 636 45450
Original Java Specification Request (JSR)
Identification |
Request |
Contributions
Section 1. Identification
Submitting Member: Siemens AG
Name of Contact Person: Jan Eichholz
E-Mail Address: jan.eichholz@siemens.com
Telephone Number: +49 89 722 21405
Fax Number: +49 89 722 53164
NOTE that this information has been updated from this original request.
Specification Lead: Jan Eichholz
E-Mail Address: jan.eichholz@siemens.com
Telephone Number: +49 89 722 21405
Fax Number: +49 89 722 53164
Initial Expert Group Membership:
Nokia
Siemens AG
Supporting this JSR:
Nokia
Section 2: Request
This specifaction will define an interface for sending and receiving MMS. It's not the scope of this JSR to offer interfaces for visualization!
J2ME, MIDP
Like JSR 120 the new WMA 2.0 should be applicable to all MIDP versions.
Possibility for Java applications to compose, send and receive MMS messages. It's not the scope of this JSR to offer interfaces for visualization!
JSR 120 is offering a message framework. At the moment it offers only the possibilities to deal with Broadcasted and Short Messages.
With the WMA 2.0 it will be possible for Java applications to compose and send messages, which can contain text, images and sound. This technology allows a richer possibility for messaging on mobile devices. For the realisation the framework of JSR 120 will be used.
javax.wireless.messaging.mms
MMS (see 3.1)
No. The platform that this API is implemented on needs to have a security framework that can be used to enforce the appropriate policy. Defining the security framework is out of the scope for this JSR. For example, the MIDP 2.0 security framework can be used.
No.
No.
Expert Group formation: Feb 2003
Community Draft: Mar 2003
Public Draft: May 2003
Final Draft: August 2003
RI & TCK: September 2003
Initial face to face meeting. Conference Calls and EMail. Additional meetings if necessary.
Stand-Alone, it should at least be combinable with MIDP 1.0.
-
For early information and subject to change, as defined in the JCP process.
- Siemens will license to all interested parties.
- It is intended to charge a single one-time fee for RI/TCK and annual maintenance fee. A per-unit royalty fee will be charged for the RI.
Section 3: Contributions
JSR 120: http://www.jcp.org/
JSR 118: http://www.jcp.org/
MMS-API: 3GPP TS 23.140 V4.4.0
This JSR should use as a basis the framework offered by JSR 120.
The necessary integration with the security framework of JSR 118 will be specified.
For WMA 1.0 the MIDP 2.0 spec was not ready so that JSR 120 could define the WMA 1.0 - MIDP 2.0 relation. WMA 1.0 only specifies in the security section "... applications MUST be granted a permission to perform the requested operation. The mechanisms for granting permission are implementation dependent ..."
WMA 2.0 will specify the relation regarding the existing MIDP 2.0 security model by defining the integration. WMA 2.0 will NOT define an own security model.