Motorola maxx V6 manual Requirements to the Native MMS Client, Draft Subject to Change 121/201

Java ME Developer Guide

Chapter 15 - JSR-205 - WMA 2.0

Since the Application-ID / from_address in the message does not match the routing parameters registered by the client, the handling of the message shall use one of the following methods:

∙Retain the message in the native clients Inbox, or

∙Delete the message and display the transient notice about the removal of the message.

The transient notice shall have the following UI dialogue elements (to be used for

P04.4 integration releases):

∙Generic Dialog

∙Title Bar text: "Unknown message"

∙Body Area text: "Message <message_index>was sent by an unknown application. Message deleted."

∙Left Soft Key: [empty]

∙Right Soft Key: OK

∙The icon used in the Dialog: notice_generic_prmicn

Starting with P05.1 releases, due to entire UI adjustment for the 2-softkey paradigm, the "OK" shall be on the Left Soft Key.

The decisions to deploy options above shall be controlled by a Feature-ID as it de- pends on the behaviour desired by the Operator.

15.3Requirements to the Native MMS Client

The mobile originated MMS Messages that are sent out by the Java client shall not be stored in the Native clients Draft/Outbox folder.

The Current OMA Standards do not support having the Application-ID parameter in the Notification. The Application-ID is only present in the Message body. Due to this, certain limitations exist as described here.

15.3.1 Anonymous Rejection Feature

The Native MMS Client shall support anonymous rejection feature.

DRAFT - Subject to Change [121/201]