WMA shall be responsible for listening to the inbound connections for incoming MMS
messages with registered Application IDs.
The WMA shall launch the MMS application and suspend listening of incoming MMS
messages for this Application ID. Then the application is responsible for the handling
of inbound connections (open/close) for the MMS messages (receive/send).
Once the Application exits (terminated, or not successful launch, or user denied the
MMS application launch) then WMA shall resume the listening of the inbound connec-
tions.
The incoming MMS messages shall be stored in a separate FIFO message Inbox that
is not visible to the user. The amount of memory allocated for this transparent inbox
is product specific.The MMS application Inbox shall not be accessible for native MMS
application.
The WMA shall pass the received MMS messages to concrete Java application assosi-
ated with the Application-ID.
Application running/resuming
The Application startup and resume shall be implemented in accordance with require-
ments outlined in the MIDP 2.0 chapter.
If an MMS application startup was denied by the user then WMA shall remove all buf-
fered unread messages for this MMS application.
Application is running/background
The Application receiving the incoming MMS message will handle this MMS message.
When the MMS message is received by an application, it shall be removed from the
Phone/SIM memory where they may have been stored prior to being delivered to the
application.
An application is responsible to handle a corresponded (Application ID) received mes-
sage (store it more persistently if needed). An MMS message may get lost if an ap-
plication can not save it due to lack of space.
Java ME Developer Guide
Chapter 15 - JSR-205 - WMA 2.0
[119/201]
DRAFT - Subject to Change