MMS Delivery Report

Description

A Delivery Report in 3GPP is feedback information provided to the originator of a Multimedia Message (MM) by an MMS Relay/Server, describing the status of delivery of that MM. The originator may be an MMS User Agent — the software on the sending device — or, in earlier definitions, a Value Added Service Provider (VASP). The delivery report is a core feature of the Multimedia Messaging Service (MMS) specified in TS 23.140, and it is also referenced in management and charging specifications such as TS 32.270, TS 32.272, and TS 32.278.

MMS operates on a store-and-forward model. When a user sends a multimedia message, the MMS User Agent submits it to the MMS Relay/Server, typically via the MM1 interface. The Relay/Server stores the message and attempts to deliver it to the recipient's MMS User Agent, often through another Relay/Server in a different network. Because delivery is asynchronous and may involve retries, temporary unavailability of the recipient, or rejection, the sender needs a way to learn the outcome. The delivery report fulfills this need by carrying status information back to the originator.

The status values carried in a delivery report include outcomes such as delivered (the message reached the recipient), expired (the message could not be delivered within its validity period), rejected (the recipient or network refused it), deferred (delivery is delayed), and indeterminate (the status could not be determined). These statuses are conveyed using standardized information elements in the MMS protocol, allowing interoperability between different vendors and operators. The report may be requested by the sender and is generated by the Relay/Server handling the final delivery or by intermediate relays along the path.

The delivery report is distinct from a read report, which indicates that the recipient has actually opened or viewed the message. A delivery report only confirms delivery to the recipient's MMS User Agent or mailbox, not that the content was read. This distinction is important for privacy and for defining what the sender can expect to learn.

Over time the definition of delivery report was refined. The Rel-5 and Rel-6 definitions referred to the originator as "an originator of MM (MMS User Agent or VASP)," acknowledging that value-added service providers could also originate messages. Starting in Rel-8, the wording was tightened to "an originator MMS User Agent," focusing on the user agent as the primary recipient of the report, and this wording persisted through later releases. The concept itself remained stable: a standardized feedback mechanism that gives message originators visibility into the fate of their multimedia messages.

Purpose & Motivation

The delivery report exists to give senders of multimedia messages reliable feedback about whether and when their messages were delivered. MMS is inherently asynchronous and store-and-forward: messages may be held in relays, retried during recipient unavailability, or expire after a validity period. Without a standardized delivery report, senders would have no way to distinguish between a message still in transit, one that failed permanently, or one successfully delivered, leading to uncertainty and poor user experience.

Before MMS delivery reporting was standardized, messaging status was largely implementation-specific or limited to simpler services like SMS status reports. MMS introduced richer content and more complex delivery paths involving multiple relays and heterogeneous devices, which made a standard feedback mechanism essential for interoperability. The delivery report defines a common set of status values and a common MM1/MM4 signaling procedure so that devices and servers from different vendors can consistently inform senders of outcomes.

The mechanism also supports operational needs such as charging, troubleshooting, and customer care. Operators can use delivery reports to verify service performance and to resolve disputes about whether a message was received. Service providers can trigger follow-up actions based on report status. By standardizing the vocabulary and protocol, 3GPP ensured that delivery reporting works across network boundaries and generations, remaining a stable and widely used feature of MMS from Rel-5 onward.