Description
The Multimedia Messaging Service Network Architecture (MMSNA) is a comprehensive framework defined by 3GPP that outlines the complete system for delivering Multimedia Messaging Service. It details the logical arrangement of network elements, their responsibilities, and the standardized protocols used for communication between them. The architecture is designed to be flexible, supporting various deployment scenarios including integration with legacy systems and enabling value-added services from third-party providers.
At its core, MMSNA identifies key functional entities such as the MMS User Agent (MMS UA) on the user device, the MMS Relay/Server (MMS-R/S) which acts as the central hub for message storage and forwarding, and external servers like the MMS Value-Added Service Application (MMS VAS Application). The architecture also defines interfaces like MM1 between the MMS UA and the MMS-R/S, MM3 between the MMS-R/S and external messaging systems (like SMTP for email), MM4 for inter-operator MMS-R/S communication, MM5 for interactions with the HLR or HSS for subscriber data, and MM7 for value-added service applications. These interfaces use protocols like WAP, HTTP, and SMTP to transport messages and their associated control information.
The MMS-R/S is the workhorse of the architecture, performing critical functions like message submission, retrieval, notification, and delivery. It handles address resolution, charging data generation, and adaptation between different transport protocols. The architecture supports store-and-forward operation, allowing messages to be delivered even when the recipient is temporarily unavailable. Security aspects, such as user authentication and message privacy, are also integrated into the architectural design. MMSNA's role is to provide a blueprint that ensures any compliant MMS implementation can successfully exchange multimedia messages in a multi-vendor, multi-operator environment, forming the backbone of the commercial MMS services deployed globally.
Purpose & Motivation
MMSNA was created to standardize the network infrastructure for Multimedia Messaging Service (MMS), which was introduced as an evolution beyond simple text-based SMS. Prior to its standardization, proprietary implementations for sending pictures, audio, and video via mobile networks would have led to fragmentation, preventing interoperability between subscribers on different networks and handset manufacturers. The primary problem MMSNA solves is defining a universal architectural model that guarantees seamless end-to-end multimedia message delivery across diverse network infrastructures.
The motivation stemmed from the commercial need to launch a compelling, revenue-generating service that leveraged improving handset capabilities and faster data networks (GPRS, EDGE, UMTS). A standardized architecture was essential to accelerate market adoption by giving operators, device makers, and content providers a clear and common technical foundation. It addressed limitations of SMS by enabling rich content, supporting store-and-forward delivery for asynchronous communication, and providing hooks for billing and value-added services. By specifying interfaces and protocols, MMSNA decoupled the development of handsets, network servers, and applications, fostering a competitive ecosystem while ensuring service reliability and a consistent user experience.
Key Features
- Defines functional entities like MMS Relay/Server and MMS User Agent
- Specifies standardized interfaces (MM1-MM8) for interoperability
- Supports store-and-forward delivery of multimedia content
- Integrates with subscriber databases (HLR/HSS) for address resolution and profiling
- Enables interconnection with external messaging systems (e.g., email via SMTP)
- Provides framework for value-added service applications via the MM7 interface
Evolution Across Releases
Introduced the initial MMSNA framework, defining the core architecture with key entities (MMS UA, MMS Relay/Server) and the primary interfaces MM1-MM4. It established the foundational message flows for submission, notification, and retrieval, and specified support for basic multimedia content types over packet-switched bearers.
Enhanced the architecture with the formal definition of the MM7 interface for Value-Added Service (VAS) applications, enabling richer third-party services. Introduced support for Digital Rights Management (DRM) and improved message size handling and reporting features.
Defining Specifications
| Specification | Title |
|---|---|
| TS 23.140 | 3GPP TS 23.140 |
| TS 32.270 | 3GPP TR 32.270 |
| TS 32.272 | 3GPP TR 32.272 |