Description
The Broadband Policy Control Function (BPCF) is a specialized network function introduced in 3GPP Release 10 as part of the Policy and Charging Control (PCC) architecture for Fixed Broadband Access Interworking. Its primary role is to serve as a policy control proxy and translator between the 3GPP core network's PCC framework and the policy control mechanisms used in non-3GPP access networks, specifically fixed broadband networks (e.g., DSL, cable, fiber). Architecturally, the BPCF resides within the 3GPP operator's domain but interfaces with the fixed broadband network's policy server, typically a Broadband Policy Server (BPS) or a Resource and Admission Control Subsystem (RACS) as defined by standards like BBF (Broadband Forum). The BPCF does not generate policy rules itself; instead, it receives PCC rules from the 3GPP Policy and Charging Rules Function (PCRF) and maps them into equivalent policy decisions or requests that can be enforced in the fixed access network. This mapping involves translating 3GPP-specific QoS parameters (like QCI, ARP, GBR, MBR) into parameters understood by the fixed network's policy enforcement points, such as gateways or routers.
Operationally, the BPCF works in conjunction with the PCRF and the Packet Data Network Gateway (PGW) or Gateway GPRS Support Node (GGSN) for user plane traffic. When a user establishes a PDN connection via a trusted non-3GPP access network (like a fixed Wi-Fi network managed by the operator), the PGW interacts with the PCRF for policy decisions. If the access network is a fixed broadband network, the PCRF identifies the need for interworking and communicates with the BPCF. The BPCF then uses the Diameter-based S9a* reference point (or Rx+ in some deployments) to interface with the PCRF, and it uses other protocols (like Diameter or proprietary interfaces) to communicate with the fixed network's policy server. This allows the PCRF's centralized policy decisions—covering service data flow detection, gating, QoS control, and charging—to be enforced end-to-end, even when the last-mile access is a non-3GPP technology.
The BPCF's key components include its interface handlers for the 3GPP side (S9a*) and the fixed network side, a policy translation function, and session management logic. It maintains binding between the 3GPP IP-CAN (IP Connectivity Access Network) session and the corresponding fixed broadband session. This enables scenarios like seamless mobility between 3GPP and fixed access (e.g., ANDSF-assisted handovers) with consistent policy application. The BPCF is particularly important in the context of Next Generation Fixed-Mobile Convergence (FMC), where operators aim to provide a unified service experience. By extending 3GPP PCC to fixed access, operators can offer guaranteed QoS for services like IPTV, VoIP, or prioritized enterprise traffic over their broadband lines, apply consistent charging models, and implement advanced parental controls or security policies across all access types.
Purpose & Motivation
The BPCF was created to address the growing need for Fixed-Mobile Convergence (FMC) and unified policy control across heterogeneous networks. Prior to its introduction, 3GPP networks had a mature PCC architecture (PCRF, PCEF) for cellular access, but fixed broadband networks used separate, often proprietary, policy control systems (like BBF's RACS). This created silos where operators could not apply consistent QoS, charging, or service policies to subscribers using both mobile and fixed services. For example, a video streaming service might have guaranteed QoS on LTE but best-effort delivery on a subscriber's home Wi-Fi over DSL, leading to a fragmented user experience. The BPCF solves this by bridging these two policy domains.
The historical context is rooted in 3GPP Release 10's work on "Fixed Broadband Access Interworking," which was driven by operators wanting to leverage their fixed assets (like fiber or cable) to offload mobile traffic (e.g., via Wi-Fi) or offer bundled services. The limitation of previous approaches was the lack of a standardized interface between 3GPP PCRF and fixed network policy servers. Without the BPCF, any interworking required complex, vendor-specific integrations that were not scalable. The BPCF provides a standardized, 3GPP-defined function that translates PCRF decisions into fixed-network actions, enabling operators to deploy converged policy control. This allows for new business models, such as single billing for fixed and mobile data, or premium QoS for gaming across both accesses.
Furthermore, the BPCF supports regulatory and technical requirements like Lawful Interception (LI) and enhanced charging by ensuring policy events from fixed access can be reported back to the 3GPP charging systems. It also facilitates network resource optimization by allowing the PCRF to have a holistic view of a subscriber's resource usage across all access types, enabling smarter traffic steering and congestion management policies in a truly converged network.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (5 CRs across 4 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-10, normative work from Rel-15.
In Release 15, the BPCF function was extended to support policy updates when a User Equipment (UE) suspends its session, as indicated by the relevant Change Request. This enhancement is part of the broader specification for policy interworking between 3GPP EPC and Fixed Broadband Access networks, which includes architectures for both trusted and untrusted access using S2b and S2c interfaces.
- Policy Update when UE suspends TS 29.212CR1666
In Release 17, the Broadband Policy Control Function (BPCF) was enhanced to support policy and QoS control for satellite access networks. Additionally, the release introduced PCRF control of MPS for DTS, expanding the policy interworking capabilities for non-seamless WLAN offload (NSWO) traffic scenarios over the S9a reference point.
In Release 18, the Broadband Policy Control Function (BPCF) was enhanced to support access control for users with eRedcap or RedCap subscriptions. This update integrates the policy framework for these reduced capability devices into the existing interworking architecture between 3GPP and Fixed Broadband Access networks. The change ensures that policy and charging control mechanisms, including those for Non-Seamless WLAN Offload (NSWO) traffic, are applied to these specific UE types.
- Access control for users with eRedcap/Redcap subscriptions TS 29.212CR1714
In Release 19, a key enhancement for the BPCF interworking function introduced a new condition for the PCRF to detect a PCEF failure in a timely manner. This improvement specifically addresses reliability within the policy control framework for Fixed Broadband Access network integration. The update focuses on the PCRF's procedures for managing sessions over interfaces like S9a, ensuring more robust fault detection in the interworking architecture.
- Add a new condition for the PCRF detecting PCEF failure in time TS 29.213CR0751
Explore further
Broader topics and technologies where BPCF plays a role.
Defining Specifications
3GPP specifications that define or reference BPCF, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.139 vj00 | 3GPP-Fixed Broadband Interworking Stage 2 | Rel-19 |
| TS 23.203 vj20 | Policy and charging control architecture | Rel-19 |
| TS 23.839 vc00 | Fixed-Mobile Convergence Architecture Study | Rel-12 |
| TS 23.896 vc00 | Policy & Charging Control for Fixed Broadband Convergence | Rel-12 |
| TS 29.212 vj00 | Gx/Gxx/Sd/St Diameter Protocol | Rel-19 |
| TS 29.213 vj20 | PCC Signalling Flows and QoS Mapping | Rel-19 |
| TS 29.215 vj00 | S9 Reference Point Stage 3 Specification | Rel-19 |
| TS 29.810 vd00 | Diameter Load Control Study | Rel-13 |