Electronic Message Association

Description

The Electronic Message Association (EMA) was a service capability defined in early 3GPP releases, specifically within the context of Multimedia Messaging Service (MMS). It provided a standardized architectural framework and protocol set for the exchange of rich multimedia messages. An EMA-based system involved several key functional components: the MMS User Agent (resident on the User Equipment), the MMS Relay/Server (which stored and forwarded messages), and associated databases like the MMS User Profile. The protocols defined for communication between these entities included MM1 (between UE and Relay/Server), MM3 (between Relay/Server and external email/SMTP servers), MM4 (for inter-operator MMS Relay communication), and MM7 (for value-added service provider interfaces).

How EMA worked centered on the store-and-forward model. When a user sent an MMS, the User Agent would submit the message (using a WAP or HTTP POST over MM1) to its home MMS Relay/Server. This server would then process the message, which involved checking the recipient's address, applying any service logic based on the sender's or recipient's profile (e.g., message size limits, content adaptation), and determining the next hop. If the recipient was on a different network, the server would forward the message using the standardized MM4 protocol to the recipient's home MMS Relay/Server. That server would then notify the recipient's User Agent (via MM1) of the waiting message, which the agent could then retrieve. This process allowed for asynchronous delivery and handling of messages that might be large or require the recipient's device to be powered on and in coverage.

Its role in the network was as a key enabler for interoperable multimedia messaging in the 2.5G and 3G era. Before widespread internet-based messaging apps, MMS was the primary method for sending photos and audio clips between mobile users. EMA provided the essential glue that allowed an MMS sent from a subscriber on Operator A's network using a Nokia handset to be successfully delivered to a subscriber on Operator B's network using a Sony Ericsson handset. It defined content formats (like SMIL for presentation), charging data records, and privacy settings, making MMS a billable, standardized service integral to operator service portfolios.

Purpose & Motivation

EMA was created to solve the problem of proprietary, non-interoperable multimedia messaging systems in the early 2000s. As mobile networks evolved from voice and SMS to support data (GPRS, EDGE), there was a strong market demand for sending pictures and audio. However, without a standard, each manufacturer or operator might develop their own system, leading to a fragmented market where users on different networks or with different phones could not exchange messages. EMA, as defined by 3GPP, provided this missing standard, enabling global interoperability.

The technology addressed the limitations of simple SMS, which was restricted to 160 characters of text, and proprietary picture messaging solutions. It defined a complete service architecture that could handle various media types, adapt content to device capabilities, interface with external email systems, and support flexible charging models. This allowed operators to deploy a revenue-generating service with a clear path for evolution. The historical context is the transition from circuit-switched SMS to packet-switched multimedia services, leveraging the new IP-based capabilities of GPRS and UMTS networks.

Motivation for its inclusion in 3GPP stemmed from the desire to create a unified mobile multimedia service layer that could be adopted globally, similar to the success of SMS. By standardizing the protocols and interfaces, it reduced market fragmentation, lowered costs for handset manufacturers (who could build to one standard), and gave operators a competitive service to offer against emerging internet-based alternatives. It laid the groundwork for later rich communication services.

Key Features

• Standardized store-and-forward architecture for multimedia messaging
• Defined a set of interoperable protocols (MM1, MM3, MM4, MM7) between system components
• Supported message content including text, image, audio, and video formats
• Included content adaptation features for recipient device capabilities
• Specified charging interfaces and data records for billing
• Enabled interconnection between different operator MMS systems

Evolution Across Releases

Defining Specifications