Application Data

Description

Application data, in the context of 3GPP specifications, refers to information or data that is specific to an application other than the Multimedia Messaging Service (MMS) User Agent or Value Added Service Provider (VASP). This data is intended to be transported without alteration by using MMS. The definition, which has been stable since Release 6, emphasizes that application data can be of any content type and format, allowing MMS to serve as a generic transport mechanism for a wide variety of applications. This concept is defined in several 3GPP specifications, including TS 23.140 (Multimedia Messaging Service), TS 32.270 (Charging management for MMS), TS 32.272 (Advice of Charge supplementary service), and TS 32.278 (Charging management for MMS).

MMS is a store-and-forward messaging service that allows users to send and receive multimedia messages containing text, images, audio, video, and other rich content. The MMS architecture includes the MMS User Agent, which resides on the user equipment (UE) and interacts with the user; the MMS Relay/Server, which stores and forwards messages; and the VASP, which provides value-added services. Application data is the payload that is not generated or consumed by the MMS User Agent or VASP itself, but rather by some other application. For example, a user might send a vCard (electronic business card) as an attachment in an MMS message. The vCard is application data because it is specific to a contact management application, not to the MMS User Agent. The MMS system transports this data without altering it, ensuring that the receiving application can interpret it correctly.

The key characteristic of application data is that it is opaque to the MMS system. The MMS User Agent and VASP do not need to understand the content of the application data; they simply treat it as a binary object with a specified content type. This allows MMS to support an unlimited range of applications, from simple text files to complex multimedia formats. The content type is typically indicated by a MIME type, such as 'text/vcard' or 'application/pdf', which tells the receiving application how to handle the data. The MMS system may perform some processing, such as transcoding or compression, but the definition states that application data is transported 'without alteration,' meaning that the integrity of the data is preserved end-to-end.

Application data plays a crucial role in enabling rich communication services beyond simple text messaging. It allows users to share files, photos, videos, and other content seamlessly. It also enables machine-to-machine (M2M) communication, where devices can exchange application-specific data via MMS. For operators, application data drives traffic and revenue, as MMS messages containing large attachments may be charged differently. The charging aspects are covered in TS 32.270 and TS 32.278, which define how MMS events are charged, including the transport of application data.

The definition of application data has remained unchanged from Release 6 through Release 19, reflecting the stability of the MMS architecture and the continued relevance of MMS as a messaging service. Although newer messaging services like Rich Communication Services (RCS) have emerged, MMS remains widely used, especially for interoperability with non-RCS devices. The concept of application data ensures that MMS can evolve to support new applications without requiring changes to the core MMS specifications. This extensibility is a key reason for the longevity of MMS in the 3GPP ecosystem.

Purpose & Motivation

Application data exists to enable the transport of arbitrary application-specific content through the Multimedia Messaging Service (MMS) without requiring the MMS infrastructure to understand or modify the data. Before this concept was standardized, MMS was primarily designed for specific content types like images and audio, limiting its use for other applications. The definition of application data, introduced in Release 6, opened up MMS as a generic transport mechanism for any application, fostering innovation and interoperability.

The primary problem solved by application data is the need for a flexible and extensible messaging service that can carry any type of content. By treating application data as opaque, MMS can support new applications without changes to the MMS specifications. This is particularly important for services like vCard exchange, where the data is specific to a contact management application but needs to be transported reliably. Application data also enables value-added services provided by VASPs, which can embed application-specific data in MMS messages.

Historically, the introduction of application data in Release 6 coincided with the growth of multimedia messaging and the need for richer content. The definition has remained stable because it is fundamentally sound: it separates the transport function of MMS from the content being transported. This separation of concerns allows MMS to be used in diverse scenarios, from personal messaging to enterprise applications. The continued inclusion of application data in specifications through Release 19 demonstrates its enduring utility in the 3GPP ecosystem.