Description
The Bearer Binding and Event Reporting Function (BBERF) is a critical component in 3GPP's Policy and Charging Control (PCC) architecture, specifically designed for non-3GPP access networks such as Wi-Fi, WiMAX, and fixed broadband. As a logical function, BBERF resides in the access gateway of non-3GPP networks and serves as the policy enforcement point that interfaces with the PCRF via the Gxx reference point. Its primary responsibility is to map service data flows identified by the PCRF to appropriate bearers or tunnels in the access network, ensuring that QoS policies are correctly applied to user traffic.
Architecturally, BBERF operates as an intermediary between the PCRF and the access network's bearer management system. When a user establishes connectivity through a non-3GPP access network, the PCRF provides PCC rules containing QoS parameters and charging information to the BBERF via the Gxx interface. The BBERF then translates these PCC rules into access-specific bearer commands, creating, modifying, or deleting bearers as needed. This translation is crucial because different access technologies have varying bearer models and QoS capabilities—BBERF abstracts these differences, providing a uniform interface to the PCRF.
BBERF's operation involves several key processes: bearer binding, event reporting, and policy enforcement. During bearer binding, the BBERF examines incoming PCC rules and determines which existing bearer should carry each service data flow based on QoS requirements. If no suitable bearer exists, it triggers the creation of a new bearer with appropriate QoS characteristics. Event reporting allows the BBERF to notify the PCRF about significant occurrences in the access network, such as bearer establishment failures, QoS parameter changes, or access technology transitions. These reports enable the PCRF to make informed policy decisions and maintain session continuity.
The function also plays a vital role in mobility scenarios involving handovers between 3GPP and non-3GPP networks. During such transitions, BBERF coordinates with the PCRF to ensure that QoS policies are transferred seamlessly between access technologies. This capability is particularly important for maintaining service quality during vertical handovers, where users move between cellular and Wi-Fi networks without service interruption. BBERF's event reporting mechanism provides the PCRF with real-time information about access network conditions, enabling dynamic policy adjustments based on current network capabilities and user location.
In terms of network deployment, BBERF is typically implemented within the Trusted Non-3GPP Access Gateway (TNW-AGW) or the evolved Packet Data Gateway (ePDG) for untrusted access. Its integration with these gateways allows for centralized policy control while maintaining distributed enforcement at the network edge. This distributed architecture balances scalability with responsiveness, ensuring that QoS decisions can be implemented rapidly without overloading the core network. BBERF's design reflects 3GPP's vision of converged policy management across heterogeneous networks, providing a foundation for consistent user experiences regardless of access technology.
Purpose & Motivation
BBERF was introduced in 3GPP Release 8 as part of the Evolved Packet System (EPS) architecture to address the growing need for integrated policy control across heterogeneous networks. Prior to its introduction, 3GPP networks had well-defined PCC mechanisms for cellular access through the Policy and Charging Enforcement Function (PCEF), but non-3GPP access networks lacked standardized interfaces for policy coordination with the core network. This limitation created service quality inconsistencies when users connected through Wi-Fi or other alternative access technologies, as QoS policies couldn't be uniformly applied across different network types.
The primary motivation for BBERF's creation was to extend 3GPP's PCC framework to non-3GPP access networks, enabling operators to offer consistent service quality and charging models regardless of how users connect to the network. This capability became increasingly important as mobile operators began integrating Wi-Fi offloading into their service offerings and users expected seamless transitions between cellular and Wi-Fi networks. Without BBERF, operators faced challenges in applying the same sophisticated QoS policies and charging rules to non-3GPP access, limiting their ability to monetize services effectively across all access types.
BBERF solved several key problems: it provided a standardized interface (Gxx) between non-3GPP access networks and the PCRF, enabled dynamic bearer management for service flows in non-3GPP environments, and facilitated event reporting from access networks to the policy controller. These capabilities allowed operators to implement advanced services like guaranteed bitrate video streaming, prioritized voice services, and differentiated charging across all access technologies. By abstracting the differences between various non-3GPP access technologies, BBERF simplified policy implementation and reduced integration complexity for multi-access network deployments.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (6 CRs across 3 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-8, normative work from Rel-15.
In Release 15, the BBERF function was enhanced with new event reporting capabilities. Specifically, it introduced support for group-based event configuration and reporting, and added the Presence Reporting Area Node AVP. Additionally, a correction was made to include CSG-Information-Reporting within the Re-Auth-Request (RAR) command.
In Release 17, the BBERF's functionality was enhanced to support PCRF control of the Multimedia Priority Service (MPS) for the Dedicated Transport Service (DTS). This update specifically introduced procedures allowing the PCRF to manage priority service policies for dedicated transport bearers. The change enabled the network to apply MPS prioritization to DTS sessions via the BBERF.
- PCRF control of MPS for DTS TS 29.213CR0743
In Release 19, enhancements were made to improve reliability by introducing a new condition for the PCRF to detect a PCEF failure in a timely manner. Furthermore, the procedure for an Application Function (AF) to trigger the PCEF failure checking mechanism was updated. These changes focused on the interaction between the PCRF, AF, and PCEF to bolster failure detection and reporting.
Explore further
Broader topics and technologies where BBERF plays a role.
Defining Specifications
3GPP specifications that define or reference BBERF, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.203 vj20 | Policy and charging control architecture | Rel-19 |
| TS 29.154 vj00 | Nt Reference Point Protocol | Rel-19 |
| TS 29.201 vj00 | RESTful Rx Interface for AF-PC Communication | Rel-19 |
| 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.804 v801 | CT3 Aspects of System Architecture Evolution | Rel-8 |
| TS 29.810 vd00 | Diameter Load Control Study | Rel-13 |
| TS 29.816 va00 | PCRF Failure & Restoration Study | Rel-10 |
| TS 29.817 vc10 | Study on XML-based Rx interface for PCC | Rel-12 |