Microsoft Word Master master doc

2.1
 
OMA Multimedia Messaging Service 
OMA was formed in 2002 by some of the leading companies within the mobile world. 
Among some of the main goals of the OMA is to deliver high qualified technical 
specifications and to be a catalyst for the consolidation of standards activity within the 
mobile data industry. As a part of this thesis our TMMS is based on OMA’s MMS [1]. 
Here follows an outline on how OMA’s MMS works. 
OMA’s MMS is a messaging system for various media types (text, image, audio and 
video). The MMS Client can send and retrieve messages through a MMS Proxy-Relay 
(PR). Also MMS may interoperate with other messaging systems, such as e-mail. The 
Figure 2-1 shows the MMS architecture. 
Figure 2-1: MMS Architecture (from MMS-ARCH spec) 
The payload carried through the MMS system is described in the MMS Message 
Encapsulation standard [2] A MMS message consists of a header part and a body part. 
The header part describes the message with various fields, such as sender, destination 
and flags. A MMS message does not need to have a body part, but if it is present it 
consists of one or more media objects and zero or more presentation descriptions. 

---

2.2 Background information: : Java 2 Platform, Micro Edition 
Page 4 of 93 
The end-user interacts with the MMS Client, and it is responsible for rendering and 
composing of messages. Also it must be able to send and retrieve messages to/from the 
MMS PR. 
The MMS PR is responsible for routing the messages to and from the MMS Clients. It 
may also provide a storage service for MMS messages, which logical is named the MMS 
Server. Instead of doing simple message delivery the MMS PR may decide to convert the 
message body into a streaming delivery, depending on various properties like message 
content and user profile.