Description
The MMS User Agent is a software application residing on a User Equipment (UE), Mobile Station (MS), or external device that performs Multimedia Messaging Service (MMS) operations on behalf of the user and/or another application. It is the client-side counterpart to the MMS Relay/Server and is responsible for composing, sending, receiving, retrieving, and displaying MMS messages. The MMS User Agent is not considered part of the MMS Environment (MMSE); rather, it is an external entity that interacts with the MMSE via the MM1 interface. This distinction is important because it clarifies that the MMS User Agent is outside the operator's core network and is typically implemented as an application on the user's device.
Functionally, the MMS User Agent provides a user interface for creating and viewing multimedia messages. It allows the user to attach images, audio, video, and text, and to specify recipients. When a message is sent, the MMS User Agent submits it to the MMS Relay/Server using the MM1 interface, which is typically based on HTTP or WAP. The MMS User Agent also handles incoming message notifications: when the MMS Relay/Server sends a notification (often via SMS or a WAP Push), the MMS User Agent retrieves the message from the server and presents it to the user. It manages local storage of messages and can perform operations such as forwarding, deleting, and saving messages.
The MMS User Agent is responsible for negotiating capabilities with the MMS Relay/Server. For example, it can inform the server about the device's supported media types and screen size, allowing the server to adapt message content accordingly. This capability negotiation is part of the MMS User Agent's role in ensuring that the recipient can view the message properly. The MMS User Agent also handles charging-related aspects, such as confirming message delivery and generating local logs.
In terms of architecture, the MMS User Agent communicates with the MMS Relay/Server over the MM1 interface, which supports both submission and retrieval of messages. The MMS User Agent may also interact with other applications on the device, such as a camera or address book, to facilitate message creation. It is typically implemented as a native application or a downloadable client. The MMS User Agent is defined in 3GPP TS 23.140, which specifies its functional responsibilities and the protocols it uses. It is also referenced in charging specifications TS 32.270 and TS 32.272.
The MMS User Agent has evolved over releases, with the definition refined to include operations on behalf of another application, not just the user. This reflects the growing use of MMS for application-to-person (A2P) messaging, such as notifications from banks or service providers. The MMS User Agent remains a key component of the MMS ecosystem, enabling rich multimedia messaging on mobile devices. Even as messaging shifts to IP-based services like RCS, the MMS User Agent continues to be relevant for legacy MMS support and interoperability.
Purpose & Motivation
The MMS User Agent was created to provide a standardized client-side component for Multimedia Messaging Service, ensuring that users can send and receive rich media messages consistently across different devices and networks. Before MMS, there was no standard way for mobile devices to handle multimedia messaging; each manufacturer might have implemented proprietary solutions, leading to fragmentation. The MMS User Agent solves this by defining a common set of functions that any device can implement, enabling interoperability between different handsets and operators.
The MMS User Agent addresses the need for a user-friendly interface to MMS. It handles the complexities of message composition, attachment handling, and retrieval, presenting a simple experience to the user. It also manages the interaction with the MMS Relay/Server, including capability negotiation and notification handling, so that the user does not need to worry about technical details. This abstraction is crucial for mass adoption of MMS.
Another key motivation was to support application-to-person messaging. By allowing the MMS User Agent to perform operations on behalf of another application, 3GPP enabled a wide range of services, such as mobile marketing, alerts, and content delivery. This expanded the utility of MMS beyond person-to-person communication. The MMS User Agent also plays a role in charging and policy enforcement by providing feedback to the network. Overall, the MMS User Agent was designed to make multimedia messaging accessible, interoperable, and extensible, and it remains a foundational element of mobile messaging.
What changed in its specifications
The latest release-to-release comparison of specifications that define MMS user agent. Each summary describes the whole specification, not only this term.
Rel-6 added online charging reference point IM9 and updated MMS charging details.
Full comparison in TS 23.140 →MMS converged charging in 5G system, with architecture, flows, CDR triggers, and message formats defined.
Full comparison in TS 32.270 →Technology family
Messaging services · Services
- Phase 1 CBC, MO-SMS, MT-SMS, SMS, SMS-CB
- Phase 2 CBE, SMS-GMSC, SMS-IWMSC
- R99 EMS, MMS, MMS User Agent, MMSE
- Rel-4 MMS Relay/Server
- Rel-6 IP-SM-GW, MSCF
- Rel-7 SMS over IP, SMS Router
- Rel-8 SMS over SGs
- Rel-15 CBCF, PWS-IWF, SMS over NAS, SMSF
- Rel-17 Legacy 3GPP Message Gateway, MSGin5G, MSGin5G Client, MSGin5G Server, Non-3GPP Message Gateway
- Rel-18 Broadcast Message Gateway
Members and relations were proposed independently by several models and kept only where at least two agree; quotes are verified verbatim against the specifications. Release = first approved version of the defining specification.
Release Timeline
Detected Changes Across Releases
verified against 3GPP sourcesDocumented changes in 2 releases, each verified against the text of 3GPP specifications or approved change requests and shown with the exact wording. The release timeline above shows the same releases. A release without an entry has no documented change for this term.
The MMS protocol framework is specified for the first time, with the MMS User Agent communicating through the MMS Relay with the MMS Server.
- “In this framework the MMS User agent communicates through the MMS Relay with the MMS Server.” TS 23.140 v3.1.0
MMS user agent behaviour is specified: forwarding user agent acts as originator for reply-charging and cannot forward the originator's reply-charging information.
- “forwarding MMS User Agent behaves as the originator MMS User Agent to support reply-charging function.” TS 23.140 v6.16.0
- “Fowarding MMS User Agent shall not be allowed to forward the reply-charging information set by the originator MMS User Agent.” TS 23.140 v6.16.0
Defining Specifications
3GPP specifications that define or reference MMS user agent, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.140 v690 | MMS Stage 2 & 3 Specification | Rel-6 read |
| TS 32.270 vj00 | MMS Charging Management Specification | Rel-19 read |
| TS 32.272 vj00 | Charging for Push-to-Talk over Cellular (PoC) | Rel-19 read |