Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Services

MMS

Multimedia Messaging Service

Services →

MMS is a standardized cellular messaging service that uses a store-and-forward mechanism to send and receive multimedia messages containing text, images, video, and audio between mobile devices.

Introduced
R99
Where
Services › Codecs
Specifications
51 specs
Also in
Management
MMS Description Purpose What changed Family Detected Changes Specifications

Description

Multimedia Messaging Service (MMS) is a store-and-forward messaging service standardized by 3GPP that allows mobile subscribers to send and receive messages containing multimedia content such as formatted text, photographs, audio clips, and video clips. Unlike SMS, which is limited to plain text, MMS utilizes a client-server architecture where the user's device (MMS User Agent) communicates with network-based servers. The core network elements include the MMSC (Multimedia Messaging Service Centre), which acts as the central hub for processing messages. The MMSC comprises the MMS Relay, which handles the routing and transfer of messages between different networks and user agents, and the MMS Server, which provides storage capabilities for messages (e.g., when the recipient is unavailable) and interfaces with external systems like email servers.

The technical operation involves several stages. When a user sends an MMS, the User Agent submits the message, encoded in a multimedia format like SMIL (Synchronized Multimedia Integration Language) for presentation, to the MMS Relay/Server via the MM1 reference point, typically using WAP or HTTP protocols. The MMSC then processes the message, which may involve transcoding media formats for compatibility with the recipient's device, determining routing based on the recipient's address, and interfacing with other messaging systems (e.g., via MM3 for email or MM4 for inter-operator MMS exchange). For delivery, if the recipient is on a different network, the MMSC uses the MM4 interface to relay the message to the recipient's home MMSC, which then delivers it to the recipient's device via the MM1 interface, often using a push notification mechanism like WAP Push to alert the device to retrieve the message.

MMS also integrates with core network subsystems. It interfaces with the Home Location Register (HLR) or Home Subscriber Server (HSS) via the MM5 reference point to retrieve subscriber data and routing information. Billing and charging are facilitated through interactions with charging systems (e.g., via MM8). The service supports a variety of content types defined by MIME types and requires support in both the device and the network, making it a more complex service than SMS but enabling rich multimedia communication in the pre-smartphone and early mobile data era.

Purpose & Motivation

MMS was created to extend the capabilities of the wildly successful Short Message Service (SMS) beyond simple text, enabling rich multimedia communication over mobile networks. Prior to MMS, sending a picture or sound clip from one phone to another was not a standardized service, often relying on proprietary solutions or email, which were not seamlessly integrated into the mobile user experience. The motivation was to drive the adoption of mobile data services (GPRS, later 3G) by providing a compelling, user-friendly application that demonstrated the value of higher bandwidth.

The service addressed the limitation of SMS's 160-character text-only format, allowing for more expressive communication. It also provided a standardized, interoperable framework that ensured messages could be exchanged between subscribers on different mobile operators' networks globally, a key factor for its widespread adoption. By using a store-and-forward architecture, MMS could guarantee message delivery even if the recipient's phone was switched off or out of coverage, storing the message on the server until it could be delivered. This made it a reliable service that fit well with the usage patterns of cellular networks at the time.

What changed in its specifications

The latest release-to-release comparison of specifications that define MMS. Each summary describes the whole specification, not only this term.

TS 22.140Rel-5 → Rel-6

Added configurable error messages, prepaid error notification, UICC interaction, forwarding loop prevention, blacklists, and conditional delivery.

Full comparison in TS 22.140 →
TS 22.233Rel-5 → Rel-6

Rel-6 added charging for streaming content, data volume, and QoS parameters.

Full comparison in TS 22.233 →

Technology family

Messaging services · Services

  1. Phase 1 CBC, MO-SMS, MT-SMS, SMS, SMS-CB
  2. Phase 2 CBE, SMS-GMSC, SMS-IWMSC
  3. R99 EMS, MMS, MMS User Agent, MMSE
  4. Rel-4 MMS Relay/Server
  5. Rel-6 IP-SM-GW, MSCF
  6. Rel-7 SMS over IP, SMS Router
  7. Rel-8 SMS over SGs
  8. Rel-15 CBCF, PWS-IWF, SMS over NAS, SMSF
  9. Rel-17 Legacy 3GPP Message Gateway, MSGin5G, MSGin5G Client, MSGin5G Server, Non-3GPP Message Gateway
  10. Rel-18 Broadcast Message Gateway
  • MMS coexists with SMS
    “The present document serves as a foundation for the development of MMS. It describes a new service which has no direct equivalent in the previous ETSI/GSM world or in the fixed network world.” TS 23.140
  • MMS used together with MMSE
    “The Multimedia Messaging Service Network Architecture encompasses all the various elements that provide a complete MMS to a user (including interworking between service providers).” TS 23.140

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 sources

Documented changes in 13 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.

R99 introduced

MMS is specified for the first time in Release 99, with stage 2 and stage 3 core functions, an architecture of MMS user agent, relay and server, and addressing by e-mail address or MSISDN.

  • “It describes a new service which has no direct equivalent in the previous ETSI/GSM world or in the fixed network world.” TS 23.140 v3.1.0
  • “The present document defines the stage 2 and stage 3 description of the non realtime Multimedia Messaging Service, MMS.” TS 23.140 v3.1.0
  • “In this framework the MMS User agent communicates through the MMS Relay with the MMS Server.” TS 23.140 v3.1.0
Rel-4 specification text

TS 23.140 Rel-4 adds MMS requirements: address hiding, streaming retrieval, reply-charging, email/MSISDN addressing, and a revised Relay/Server and External Server architecture.

  • “MMS shall support address hiding i.e. anonymous messages where the sender's address is not shown to the recipient MMS User Agent.” TS 23.140 v4.10.0
  • “MMS supports streaming for the retrieval of MM contents (one or more MM elements).” TS 23.140 v4.10.0
  • “Therefore the originator of an MM should be able to mark the MM as reply-charged.” TS 23.140 v4.10.0
Rel-5 specification text

MMS addressing and behaviour were extended: recipients may be addressed by E-Mail, MSISDN or short codes, address hiding became a firm requirement, and MMs can carry keyword flags set by the MMS User Agent.

  • “MMS shall support the use of E-Mail addresses (RFC 822) [5] or MSISDN (E.164) or both to address the recipient of an MM.” TS 23.140 v5.11.0
  • “MMs may be flagged with keyword values, which shall be set by the MMS User Agent.” TS 23.140 v5.11.0
  • “The recipient MMS Relay/Server shall not show the originator address to the recipient MMS User Agent.” TS 23.140 v5.11.0
Rel-6 specification text

TS 23.140 in Rel-6 adds MMS support for OMA DRM, transport of application-specific data via MMS, and VAS application operations, and removes the MM8 billing reference point and terminal capability negotiation text.

  • “The support of DRM in MMS shall conform to the OMA DRM specifications [76], [77] and [78].” TS 23.140 v6.16.0
  • “MMS may also be used to transport data specific to applications.” TS 23.140 v6.16.0
  • “MM Cancellation: act of the originating MMS VAS Application to cancel an already submitted MM on the originator MMS Relay/Server” TS 23.140 v6.16.0
Rel-7 1 CR

A CR for 31.111 adds transfer of MMS commands to the SCP, extending USAT handling of MMS-related commands.

  • Transfer MMS commands to SCP TS 31.111CR149
Rel-9 specification text

MMS charging in 32270 now requires a single online charging principle (either IEC or ECUR) for all chargeable events within one MMS service instance, with a related correction to the MMS online charging principles.

  • “An implementation shall use only one principle for all chargeable events throughout a given instance of providing MMS service to the user” TS 32.270 v9.1.0
  • “Correction on MMS Online Charging principles” TS 32.270 v9.1.0
Rel-10 1 CR

MMS charging data in 32.270 gained fields for SCCP calling address and recipient information, plus E.164 address format alongside E.212, and MMS test applicability was corrected in 31.121.

  • “This field holds the SCCP calling address used to receive the MMS.” TS 32.270 v10.0.1
  • “Add E.164 harmonized address format to the current E.212 in MMS Charging” TS 32.270 v10.0.1
  • Essential correction of the phonebook and MMS tests applicability TS 31.121CR0163
Rel-14 specification text

TS 31.121 added UE test requirements for MMS: use of MMS data on the USIM, MMS notification storage, and priority order of MMS issuer and user connectivity parameters.

  • “Support of MMS notification storage on the USIM” TS 31.121 v14.6.0
  • “UE recognising the priority order of MMS Issuer Connectivity Parameters over the MMS User Connectivity Parameters” TS 31.121 v14.6.0
  • “Support of usage of MMS related data stored on the USIM” TS 31.121 v14.6.0
Rel-15 2 CRs

Lawful interception specifications for MMS were corrected in Rel-15: HSS triggered event references in the MMS clauses of TS 33.107 and the Network Identifier parameter's referenced server in TS 33.108 clause 15.3.

  • Incorrect references to HSS triggered events in the SMS, MMS clauses TS 33.107CR0292
  • Correction of the Network Identifier parameter referenced server in clause 15.3 MMS within Table 15.3.6.1.2 TS 33.108CR0403
Rel-16 1 CR

Lawful interception specifications gain MMS support: an IRI-POI in the MMS Proxy-Relay provisioned over LI_X1 sends xIRI over LI_X2, with MMS-specific correlation IDs and target identifier formats.

  • “The IRI-POI present in the MMS Proxy-Relay is provisioned over LI_X1 by the LIPF using the X1 protocol as described in clause 5.2.2.” TS 33.128 v16.22.0
  • “The IRI-POI present in the MMS Proxy-Relay shall send xIRI over LI_X2 for the events listed in clause 7.5.2.3 of TS 33.127” TS 33.128 v16.22.0
  • Support for MMS TS 33.127CR0036
Rel-17 specification text

The clause reference for the MMS 'store' parameter encoding values changed from OMA-TS-MMA_ENC clause 7.3.52 to OMA-TS-MMS_ENC clause 7.3.56.

  • “The values given in OMA-TS-MMS_ENC [39] clause 7.3.56 shall be encoded as follows: "Yes" = True, "No" = False.” TS 33.128 v17.22.0
Rel-18 1 CR

Rel-18 adds MMS converged charging via CHF: an MMS Node (relay/server) architecture, Nchf-based charging scenarios and triggers, plus updated LI provisioning for the MMS Proxy-Relay.

  • “The MMS Node shall be able to perform convergent charging by interacting with CHF, for charging data related to MMS.” TS 32.270 v18.3.0
  • Addition of MMS relay and server TS 32.290CR0186
  • “The IRI-POI and CC-POI present in the MMS Proxy-Relay are provisioned over LI_X1 by the LIPF” TS 33.128 v18.17.0
Rel-19 1 CR

In Rel-19, TS 33.128 revised MMS record generation and MMS lawful interception: new triggers and categories, new MMBox view request/response xIRI records, and corrected MMS target identities.

  • “shall generate an xIRI containing an MMSMBoxViewRequest record when the MMS Proxy-Relay receives a m-mbox-view-req” TS 33.128 v19.8.0
  • “shall generate an xIRI containing an MMSMBoxViewResponse record when the MMS Proxy-Relay sends a m-mbox-view.conf” TS 33.128 v19.8.0
  • Solution for email target identifier in MMS TS 33.128CR0687

Defining Specifications

3GPP specifications that define or reference MMS, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 22.140 vj00 MMS Stage 1 Requirements Rel-19 read
TS 22.233 vj00 Packet-switched Streaming Service (PSS) Stage 1 Rel-19 read
TS 22.242 vj00 DRM Service Requirements Rel-19 read
TR 22.940 vj00 IMS Messaging Requirements Analysis Rel-19 read
TR 22.945 v300 Fax Services Guidance for GSM/UMTS R99 read
TS 23.140 v690 MMS Stage 2 & 3 Specification Rel-6 read
TS 23.722 vf10 Common API Framework (CAPIF) for 3GPP Northbound APIs Rel-15 read
TS 24.447 v800 Advice Of Charge (AOC) Service Protocol Rel-8 read
TS 24.526 vk00 5GS UE Policies Rel-20 read
TS 25.305 vj00 UTRAN UE Positioning Stage 2 Rel-19 read
TS 26.140 vj00 MMS Media Formats and Codecs Specification Rel-19 read
TS 26.141 vj00 IMS Messaging & Presence Media Formats Rel-19 read
TS 26.142 vj00 3GPP TS 26.142: Dynamic and Interactive Multimedia Scenes (DIMS) Rel-19 read
TS 26.143 vj10 Messaging Media Profiles Rel-19 read
TS 26.233 vf00 3GPP Packet-Switched Streaming Service (PSS) Rel-15 read
TS 26.234 vj00 3GPP PSS Protocols and Codecs Specification Rel-19 read
TS 26.244 vj10 3GPP File Format (3GP) Specification Rel-19 read
TS 26.245 vj00 3GPP Timed Text Format Specification Rel-19 read
TS 26.246 vj00 3GPP SMIL Language Profile Specification Rel-19 read
TS 26.307 vj00 3GPP HTML5 Profile Specification Rel-19 read
TS 26.346 vj30 MBMS User Services Specification Rel-19 read
TS 26.841 vj00 Study on Media Messaging Enhancements Rel-19 read
TS 26.851 vb20 MBMS Multimedia Service Enhancements Rel-11 read
TR 26.906 vj00 HEVC Evaluation for 3GPP Services Rel-19 read
TR 26.907 vj00 HTML5 for 3GPP Services Study Rel-19 read
TR 26.914 vj00 Multimedia Telephony over IP Optimization Rel-19 read
TR 26.928 vj00 Study on eXtended Reality (XR) in 5G Rel-19 read
TR 26.936 vj00 Audio Codec Characterization Technical Report Rel-19 read
TR 26.946 vj00 MBMS User Services Overview Rel-19 read
TR 26.948 vj00 Video enhancements for 3GPP Multimedia Services Rel-19 read
TR 26.955 vj00 Video Codec Analysis for 5G Services Rel-19 read
TS 29.199 3GPP TS 29.199 R99 read
TS 31.102 vk00 USIM Application Specification Rel-20 read
TS 31.111 vj40 3GPP TS 31111 vj40: USIM Application Toolkit Rel-19 read
TS 31.121 vj00 UICC Application Test Specification Rel-19 read
TR 31.901 ve00 USIM/ISIM/USAT Feature Review Study Rel-14 read
TS 32.102 vj00 Telecom Management Physical Architecture Framework Rel-19 read
TS 32.140 vj00 Subscription Management (SuM) requirements Rel-19 read
TS 32.240 vk10 3GPP Charging Architecture and Principles Rel-20 read
TS 32.251 vj00 PS Domain Charging Management Rel-19 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
TS 32.290 vk00 5G Charging Service-Based Architecture Rel-20 read
TS 32.296 vj00 Online Charging System (OCS) Architecture Rel-19 read
TS 32.297 vj00 Charging Data Record File Transfer Rel-19 read
TS 32.298 vk10 Charging Data Record Specification Rel-20 read
TS 32.808 v800 Common Profile Storage Framework for User Data Rel-8 read
TS 33.106 vj00 Lawful Interception Requirements (Pre-Rel-15) Rel-19 read
TS 33.128 vj80 Lawful Interception Protocols and Procedures Rel-19 read
TR 43.901 vj00 Generic Access to A/Gb Interface Feasibility Study Rel-19 read
TR 45.903 vj00 SAIC Feasibility Study for GSM Networks Rel-19 read