Service Data Flow

Description

A Service Data Flow (SDF) is a cornerstone of the 3GPP Policy and Charging Control (PCC) architecture, defined from Release 6 onwards. It represents a collection of IP packet flows that are identified by a set of packet filters (e.g., based on source/destination IP addresses, ports, protocol type, and optionally deep packet inspection (DPI) information). The primary function of an SDF is to serve as the granular entity to which network policies—specifically Quality of Service (QoS) and charging rules—are uniformly applied. When user data packets traverse the network, they are matched against these predefined SDF filters at the Policy and Charging Enforcement Function (PCEF), typically located in the Gateway GPRS Support Node (GGSN) or Packet Data Network Gateway (PGW).

The architecture for managing SDFs is centralized around the Policy and Charging Rules Function (PCRF). The PCRF is the brain of the PCC system. It makes dynamic policy decisions based on subscriber information, service requests, and network conditions received from various sources like the Application Function (AF) and Subscription Profile Repository (SPR). These decisions are translated into PCC rules, each containing an SDF template (the filters) and the corresponding policy actions. These PCC rules are then provisioned to the PCEF via the Gx interface. The PCEF enforces these rules in real-time, performing operations like gating (allowing/blocking packets), QoS marking (setting the QoS Class Identifier), and usage monitoring for charging.

The role of the SDF is integral to enabling sophisticated service models. It allows the network to differentiate traffic not just per user or per Access Point Name (APN), but per specific application or service type. For example, video streaming traffic can be identified as a distinct SDF and granted higher bandwidth (guaranteed bit rate) compared to best-effort web browsing traffic. From a charging perspective, an SDF can be associated with specific charging keys and methods (e.g., volume-based, time-based, or event-based), enabling flexible monetization strategies like sponsored data or zero-rating. The SDF abstraction thus decouples service logic from network transport, providing operators with a powerful tool for traffic management and revenue generation.

Purpose & Motivation

The SDF concept was introduced to address the limitations of earlier mobile data networks, which primarily offered simple, best-effort internet access with flat-rate charging. As mobile services evolved to include VoIP, video streaming, and enterprise applications, there was a critical need for the network to intelligently identify different types of traffic and apply appropriate quality and billing treatments. Prior to PCC, any policy enforcement was static and configured manually on network gateways, lacking the dynamism and subscriber-awareness required for modern services.

The creation of the PCC framework, with the SDF at its core, was motivated by the need for standardized, dynamic policy control. It solves the problem of how to seamlessly integrate application-layer service requirements (e.g., a video call needing low latency) with the transport network's capabilities. By defining traffic at the granularity of an SDF, operators can create and monetize tiered service plans, ensure network resources are optimally allocated, and provide a consistent quality of experience for specific applications. It enabled the transition from being a 'dumb pipe' to becoming a 'smart pipe' capable of service innovation.

Key Features

• Granular traffic identification using IP 5-tuple and DPI filters
• Basis for dynamic QoS policy enforcement (gating, bandwidth, priority)
• Foundation for flexible, service-aware charging (online/offline)
• Centralized control via PCRF with real-time rule provisioning
• Decouples service logic from network transport layer
• Enables sponsored data, zero-rating, and tiered service plans

Evolution Across Releases

Defining Specifications