Delivery Function

Description

The Delivery Function (DF) is a standardized network component within the 3GPP architecture that serves as a delivery mechanism for various services, most notably within the Multimedia Messaging Service (MMS) environment. It functions as a specialized server that receives content from originating applications or users, processes it according to network policies and subscriber profiles, and then forwards it to the appropriate destination, which could be another user's device or a different network element. The DF handles the complexities of delivery across potentially heterogeneous networks, managing store-and-forward operations, delivery reports, and interoperability between different service providers.

Architecturally, the DF typically interfaces with several other network elements. In the MMS context, it works closely with the MMS Relay/Server (MMS-RS), which acts as the central hub for MMS traffic. The DF receives messages from the MMS-RS that require delivery to a recipient. It then determines the optimal delivery path, which may involve querying the Home Location Register (HLR) or Home Subscriber Server (HSS) for subscriber status and routing information. For delivery to the recipient's device, the DF interacts with the Gateway GPRS Support Node (GGSN) and Serving GPRS Support Node (SGSN) in 2G/3G networks, or the Packet Data Network Gateway (PGW) and Serving Gateway (SGW) in 4G/5G networks, to establish the data bearer for content transfer.

The DF's operation involves several key processes. First, it performs address resolution and validation, ensuring the recipient identifier (like an MSISDN) is valid and reachable. Second, it applies service logic, which may include checking for delivery restrictions, applying content adaptation (like image resizing for the recipient's device capabilities), or implementing charging triggers. Third, it manages the actual delivery attempt, handling retries if the initial attempt fails (e.g., if the recipient's device is offline) and managing expiration timers. Finally, it generates and returns delivery reports back to the originating system, confirming whether the content was successfully delivered or indicating the reason for failure.

A critical aspect of the DF is its ability to support different delivery methods. For immediate delivery, it pushes content directly to the recipient when they are attached to the network. For deferred delivery, it can store content and deliver it later when the recipient becomes available, a fundamental feature for asynchronous messaging services like MMS. The DF also plays a role in inter-operator messaging, where it may communicate with a DF in another operator's network using standardized interfaces (like the MM4 interface in MMS) to deliver messages to subscribers of other mobile networks. This requires support for protocol translation, security (like mutual authentication), and settlement between operators.

Purpose & Motivation

The Delivery Function was created to address the need for a reliable, standardized mechanism to deliver content and messages in packet-switched mobile networks, particularly as services evolved beyond simple voice calls and SMS. Before its standardization, proprietary solutions for content delivery existed, leading to interoperability issues between different network vendors and mobile operators. This fragmentation hindered the development of widespread, reliable value-added services. The DF, as part of the 3GPP service architecture, provided a common framework that ensured content from any compliant application could be delivered to any subscriber on any compliant network, fostering a global ecosystem for mobile data services.

Its introduction with 3GPP Release 4 was closely tied to the specification of the Multimedia Messaging Service (MMS), which was envisioned as a successor to SMS. MMS required the ability to deliver larger, multimedia messages (images, audio, video) which could not be handled by the existing SMS infrastructure. Unlike SMS's store-and-forward in the SMSC, MMS needed a more sophisticated delivery mechanism that could handle different content types, adapt to device capabilities, manage data sessions, and provide detailed delivery reporting. The DF fulfilled this role, separating the delivery logic from the core messaging application and enabling efficient use of network resources.

Furthermore, the DF solved the problem of asynchronous delivery in a network where users are not always connected. Mobile data connections in early 3G networks were not always 'always-on.' The DF's store-and-forward capability ensured messages were not lost when a recipient was offline, attempting delivery when the device reattached. It also addressed charging and policy enforcement by integrating with billing systems and applying operator-defined rules before content was delivered, allowing for prepaid credit checks, content filtering, and differentiated service treatment. This made commercial, billable services feasible and manageable for operators.

Key Features

• Store-and-forward message delivery for asynchronous communication
• Interworking with core network elements (HLR/HSS, GGSN/PGW) for subscriber status and routing
• Support for content adaptation based on recipient device capabilities
• Generation and management of detailed delivery status reports
• Integration with charging systems for service billing and prepaid checks
• Inter-operator communication via standardized interfaces (e.g., MM4)

Evolution Across Releases

Defining Specifications