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

Glossary term · Services

MMSE

Multimedia Messaging Service Environment

Services →

MMSE is the complete set of network elements, interfaces, and protocols that collectively enable the Multimedia Messaging Service.

Introduced
R99
Where
Radio Access Network › NG-RAN (5G)
Specifications
10 specs
Also in
Services, User Equipment
MMSE Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

The Multimedia Messaging Service Environment (MMSE) refers to the entire system architecture and collection of functional entities required to provide the Multimedia Messaging Service. It is not a single node but a logical environment comprising several core components defined by 3GPP specifications. The central entity is the Multimedia Messaging Service Centre (MMSC), which itself consists of the MMS Relay and the MMS Server. The MMS Relay is responsible for the routing, transfer, and adaptation of messages between different entities, while the MMS Server handles storage functions, such as storing messages temporarily when the recipient is unavailable. Beyond the MMSC, the MMSE includes other critical network elements like the MMS User Databases (which store MMS-specific user profiles and settings), and various interworking functions.

The environment operates through a set of standardized reference points (interfaces), labeled MM1 through MM8. MM1 is the interface between the MMS User Agent (on the handset) and the MMS Relay/Server, used for message submission, delivery, and notification, typically implemented over WAP or HTTP. MM3 is the interface for connecting the MMSC to external servers, such as email servers (SMTP) or other messaging systems. MM4 is the crucial interface for inter-operator MMS exchange, allowing an MMSC in one network to relay messages to an MMSC in another network. MM5 is the interface to subscriber databases like the HLR or HSS for routing information and service provisioning. MM7 is the interface for Value-Added Service Providers (VASPs) to submit messages (e.g., for content delivery services). These interfaces ensure interoperability within a single operator's network and between different operators globally.

From a procedural standpoint, the MMSE manages the complete lifecycle of an MMS. This includes message submission from the originator's User Agent, address resolution and routing (potentially involving inter-operator communication), media adaptation and transcoding to suit recipient device capabilities, storage, notification to the recipient, and final delivery or retrieval. The environment also integrates with charging systems (via interfaces like MM8) to generate billing records for message transactions. The MMSE, therefore, represents the complete backend infrastructure that makes the MMS service possible, abstracting its complexity from the end-user who simply uses the MMS application on their phone.

Purpose & Motivation

The concept of the Multimedia Messaging Service Environment was defined to provide a comprehensive, standardized framework for deploying MMS. Without a standardized environment, each vendor or operator might implement the service using proprietary architectures and interfaces, leading to fragmentation and an inability for subscribers on different networks to exchange multimedia messages. The MMSE specification solved this by defining a clear, interoperable ecosystem where all functional entities and the interfaces between them are standardized.

This approach addressed several key problems. It ensured that handsets from any manufacturer could connect to any standards-compliant MMSC. It enabled global interoperability between mobile operators by strictly defining the MM4 interface for inter-carrier message exchange. It also facilitated the creation of a vibrant ecosystem for value-added services by defining the MM7 interface for third-party content providers. By creating this holistic environment, 3GPP enabled the rapid and widespread rollout of MMS as a globally consistent service, which was critical for its commercial success and user adoption in the 2000s.

What changed in its specifications

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

TS 23.140Rel-5 → Rel-6

Rel-6 added online charging reference point IM9 and updated MMS charging details.

Full comparison in TS 23.140 →
TS 32.240Rel-18 → Rel-19

Uncrewed Aerial System Phase 3 added charging support, abbreviations, and definitions. CAPIF Phase 3 added charging support and a new reference point. Energy Efficiency as Service Criteria added clauses for energy KPIs, measurement, and slice charging references.

Full comparison in TS 32.240 →

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
  • MMSE used together with MMS
    “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 4 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

The Multimedia Message Service Environment (MMSE) is defined for the first time as the set of elements, interfaces and networks that together provide a complete MMS, including roaming and inter-MMSE handling.

  • “The Multimedia Message Service Environment encompasses all the various elements that provide a complete MMS to a user.” TS 23.140 v3.1.0
  • “The MMSE provides all the necessary service elements, e.g. delivery, storage and notification functionality.” TS 23.140 v3.1.0
  • “6.1 Involved MMSE Interfaces” TS 23.140 v3.1.0
Rel-4 specification text

The MMSE is newly defined as a collection of MMS-specific network elements under a single administration, excluding the MMS User Agent, with originator/recipient MMSE roles and peer MMSE discovery and interworking.

  • “MMSE: collection of MMS-specific network elements under the control of a single administration” TS 23.140 v4.10.0
  • “NOTE 4: An MMS User Agent is not considered part of an MMSE.” TS 23.140 v4.10.0
  • “An MMSE may be able to discover a peer MMSE.” TS 23.140 v4.10.0
Rel-5 specification text

Rel-5 changes MMSE interworking: an MMSE shall discover peer MMSEs, address resolution uses DNS-ENUM, MMSE supports VASP value added services, and the MM7 interface is added.

  • “An MMSE shall be able to discover a peer MMSE as described in clause 7.2.2.” TS 23.140 v5.11.0
  • “should use the DNS-ENUM protocol [61]” TS 23.140 v5.11.0
  • “The MMSE may support Value Added Services in addition to the basic messaging services defined for MMS.” TS 23.140 v5.11.0
Rel-6 specification text

In Rel-6 TS 23.140 the MMSE gains support for interrogating an external MSCF, advanced addressing, and MMSE-domain-based routeing and MM4 domain naming rules.

  • “The MMSE may support the interrogation of an external MSCF.” TS 23.140 v6.16.0
  • “which allows the operator to handle advanced addressing within the MMSE.” TS 23.140 v6.16.0
  • “For the addressing of the MMSE on the MM4 interface an unique domain name should be used.” TS 23.140 v6.16.0

Defining Specifications

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

SpecificationTitleRelease
TS 23.140 v690 MMS Stage 2 & 3 Specification Rel-6 read
TS 32.240 vk10 3GPP Charging Architecture and Principles Rel-20 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 36.306 vj30 E-UTRA UE Radio Access Capability Parameters Rel-19 read
TS 36.867 vd00 LTE Downlink 4-Rx Antenna Ports Study Rel-13 read
TS 36.884 vd10 LTE BS MMSE-IRC Performance Rel-13 read
TR 38.812 vg00 Study on NOMA for NR Rel-16 read
TR 38.889 vg00 NR-based access to unlicensed spectrum study Rel-16 read
TR 38.922 vj30 IMT parameters study for NR in higher frequency ranges Rel-19 read