Motorola MOTORAZR maxx V6 Developer's Manual page 120

Java ME Developer Guide
Chapter 15 - JSR-205 - WMA 2.0
The application will be responsible for the interpretation and representation of the
MMS MIME content including the SMIL(presentation) content if any is attached.
In the case of full incoming message buffer, any new message for the application
with the same Application-ID shall be discarded. WMA shall not remove the first MMS
message in the buffer which was a cause of Push until:
MMS message is handled by MMS application, or
MMS application exits.
Application suspending
The Application suspending shall be implemented in accordance with requirements
outlined in the MIDP 2.0 chapter.
If the user selects not to launch the new MMS application then the incoming MMS
message shall be ignored and deleted from the handset.
Application ending
At Application exit, WMA should remove all buffered messages that were not received
by the Application.
If the MMS application needs to keep messages more persistently, it has to use other
APIs (File System API, RMS, etc.) to save incoming MMS messages on the handset
for later use. This is handled by the Application and outside the of scope of this MRS.
MMS Push
When received a message which has an unknown Application-ID, the MMS Engine
shall validate the routing options registered by each of its clients.
Since the Application-ID does not match with the routing parameters, a NotifyRe-
sponse shall be sent back to the MMSC, with status set to REJECTED.
When received a message which has an unknown Application-ID / from_address,
MMS Engine shall validate the routing options registered by each of its clients.
DRAFT - Subject to Change
[120/201]