MMS

Multimedia Messaging Service

Services →
Introduced in R99

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.

Category
Services
Introduced
R99
Where
Services › Codecs
Specifications
51 specs
MMS Description Purpose 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.

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (14 CRs across 3 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-16 2 changes

In Release 16, the primary update for the Multimedia Messaging Service (MMS) was the removal of the H.263 video codec from the standardized set of supported media types. This change refines the minimum set of supported formats to ensure continued interoperability between different terminals and networks. The update aligns with the release's principle of supporting the evolution of multimedia messaging technologies by re-using and adapting existing standards.

Rel-18 8 changes

In Release 18, the MMS function was enhanced with a new, standardized reference point between the MMS node and the Charging Function (CHF) to support converged charging. This addition formalizes the architecture for MMS charging and introduces the MMS relay and server as defined functional entities. Furthermore, the release provided clarifications on service delivery scoping and the generation of MMS Charging Data Records (CDRs).

  • Adding New Consumer for MMS in Charging Architecture TS 32.240CR0446
  • Add reference point between MMS node and CHF TS 32.240CR0469
  • Add reference point between MMS node and CHF TS 32.270CR0035
  • Addition of MMS relay and server TS 32.290CR0186
  • Addition of MMS converged charging information TS 32.298CR0920
  • Clarification on the delivery of different services and the applicability of messaging service scoping TS 33.128CR0606

+ 2 more changes

Rel-19 4 changes

In Release 19, the Multimedia Messaging Service (MMS) introduced specific enhancements including Media Messaging Enhancements (MeME-MED) and support for new media types like AMR and mp3 files for messaging. The release also provided a solution for using an email target identifier in MMS and included necessary corrections on MMS target identities. These updates ensured forward compatibility and interoperability by extending the standardized set of service capabilities and supported media formats.

  • [MeME-MED] Media Messaging Enhancements TS 26.143CR0005
  • Solution for email target identifier in MMS TS 33.128CR0687
  • [MeME-MED] AMR and mp3 files for messaging TS 26.143CR0008
  • Corrections on MMS target identities TS 33.128CR0677

Explore further

Broader topics and technologies where MMS plays a role.

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