Associated Delivery Procedures

Description

Associated Delivery Procedures (ADP) constitute a framework within the 3GPP service architecture, primarily defined in the Technical Specifications for the Multimedia Messaging Service (MMS) and related service enablers. The procedures govern how multimedia content, most notably Multimedia Messages, is delivered from a service platform (like an MMSC - Multimedia Messaging Service Centre) to the User Equipment (UE) and, in some cases, between network elements. ADP is not a single protocol but a collection of logical procedures and interactions that ensure delivery is attempted, managed, and reported upon in a reliable and network-efficient manner.

Architecturally, ADP operates within the service layer, interfacing with core network elements like the MSC (Mobile Switching Centre) or SGSN/MME (Serving GPRS Support Node / Mobility Management Entity) for mobility and session management, and the HSS (Home Subscriber Server) for subscriber data. The key component initiating ADP is typically the MMSC or another application server. The procedures define the sequence of signaling messages, the handling of delivery reports, read-reply reports, and the management of message expiration and retry attempts. They specify how the network should behave when a UE is unavailable (e.g., out of coverage), including storage and forward mechanisms.

From a functional perspective, ADP works by establishing a context for the delivery attempt. When a message is submitted for delivery, the procedures dictate how the serving network is determined, how the UE's reachability is assessed (e.g., attached, idle, busy), and how the content is pushed or a notification is sent to the UE to pull the message. A critical aspect is the association of the delivery with other procedures; for example, delivery may be deferred until a signaling connection is established for another purpose, or it may be triggered by a specific network event. The procedures also define error handling, ensuring that failures are logged and, where appropriate, reported back to the originator.

Its role in the network is to provide a standardized, carrier-grade mechanism for non-real-time content delivery. By being 'associated,' it implies a level of intelligence and coordination beyond simple store-and-forward. This coordination helps optimize network resource usage by piggybacking on existing signaling connections where possible and provides a consistent user experience for messaging services. It forms the backbone of the reliability features for MMS, ensuring messages are not silently lost and that users and service providers receive confirmation of delivery outcomes.

Purpose & Motivation

ADP was created to solve the problem of unreliable and non-interoperable multimedia content delivery in early mobile data services. Prior to its standardization in 3GPP Release 5, proprietary mechanisms for delivering picture messages and other rich content led to fragmented user experiences and limited service adoption across different operators and device manufacturers. The lack of a common procedure made cross-operator MMS and other value-added services difficult to implement reliably.

The primary motivation was to enable the Multimedia Messaging Service (MMS) as a successful, ubiquitous service. MMS required a more complex delivery mechanism than SMS due to larger message sizes, the need for data bearer establishment, and handling of diverse device capabilities. ADP provided the necessary procedural framework to manage this complexity, ensuring messages could be delivered despite user mobility, temporary network unavailability, and varying terminal states. It addressed limitations such as uncoordinated delivery attempts wasting network resources and the absence of standardized delivery/read reports for multimedia content.

Historically, ADP's introduction in Release 5 was part of the broader push for packet-switched multimedia services in 3G networks. It established the foundational model for associated delivery, where message transfer is intelligently linked to other network activities. This solved the problem of how to efficiently deliver content without requiring the UE to be continuously active on a data bearer, thereby improving battery life and network efficiency while guaranteeing service reliability.

Key Features

• Standardized delivery and reporting procedures for multimedia content
• Coordination with UE mobility and session management states
• Support for store-and-forward mechanisms for unavailable recipients
• Definition of delivery reports and read-reply reports
• Association of content delivery with other network signaling events
• Error handling and retry logic for failed delivery attempts

Evolution Across Releases

Defining Specifications