Multimedia Messaging Service

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.

Key Features

• Store-and-forward architecture with central MMSC (Relay/Server)
• Support for multimedia content (text, image, audio, video) using MIME types
• Standardized interfaces (MM1-MM8) for interoperability between devices and networks
• Integration with subscriber databases (HLR/HSS) for routing and service authorization
• Interworking with external messaging systems like email (SMTP) and SMS
• Support for message notification (e.g., WAP Push) and retrieval by the recipient device

Evolution Across Releases

Defining Specifications