Multimedia Messaging Service Originator

Description

The Multimedia Messaging Service Originator (MMSO) is a logical role defined in the 3GPP MMS standards that encapsulates the source of a multimedia message. In the vast majority of cases, the MMSO is implemented as software (the MMS User Agent) on a subscriber's mobile device, such as a smartphone. However, it can also be an automated application or server in scenarios like application-to-person (A2P) messaging, such as news alerts or marketing campaigns. The MMSO's primary function is to compose a multimedia message—which can include text, images, audio, or video—and then submit it to the network's MMS Relay/Server (MMS-R/S) for processing and delivery.

The technical operation begins with the MMSO establishing a data connection (e.g., over GPRS, UMTS, or LTE). It then uses the MM1 interface, typically over HTTP or WAP, to communicate with the MMS-R/S. The submission process involves sending a MM1_submit.REQ message. This message is a complex PDU (Protocol Data Unit) that contains not only the multimedia content itself (encoded in a MIME format like multipart/related) but also crucial metadata. This metadata includes the recipient address(es), sender address, subject, desired delivery time, expiry time, and an indication of whether a delivery report or read-reply report is requested. The MMSO is responsible for properly formatting this PDU according to the 3GPP specifications.

Upon receiving a MM1_submit.RES response from the MMS-R/S, the MMSO knows the submission was accepted. The MMSO may later receive a MM1_delivery_report.REQ if it requested one, informing it of the final delivery status to the recipient's network. The role of the MMSO is distinct from the MMS Recipient, though a single MMS User Agent can perform both roles. The specifications governing the MMSO behavior ensure that all originating devices and applications interact with the network in a consistent manner, which is vital for reliable service operation, accurate charging, and a predictable user experience. Charging records related to the message origination are often triggered based on the MMSO's submission request.

Purpose & Motivation

The MMSO role was formally defined to create a clear contractual and functional boundary within the MMS architecture. It identifies the point of origin for a message, which is critical for several operational and commercial reasons. Before such standardization, the concept of 'sender' was ambiguous, especially with the introduction of automated services, making billing, dispute resolution, and spam control difficult.

Its creation solves the problem of accountability and responsibility in the message flow. By precisely defining the MMSO, the standards establish which entity initiates the transaction, who is responsible for the content and formatting of the initial submission, and which party should be charged for the message origination. This is essential for generating accurate Charging Data Records (CDRs) for billing purposes. Furthermore, it enables features like sender-requested delivery reports, as the MMSO is the entity that signals this desire during submission. The role also facilitates the development of A2P services by providing a standardized model for servers to act as originators, thereby expanding the commercial use cases for MMS beyond person-to-person communication.

Key Features

• Initiates the MMS transaction by submitting messages to the MMS Relay/Server
• Formats the MM1_submit.REQ PDU with content and metadata (recipients, subject, etc.)
• Can request delivery reports and read-reply reports for sent messages
• Implemented typically as an MMS User Agent on a mobile device
• Can also be an automated server for Application-to-Person (A2P) messaging
• Triggers the creation of charging records for message origination

Evolution Across Releases

Defining Specifications