Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Core Network

BBERF

Bearer Binding and Event Reporting Function

Core Network →

BBERF is a logical function in the Evolved Packet Core that binds service data flows to bearers and reports events to the PCRF for dynamic QoS control and policy enforcement in non-3GPP access networks.

Introduced
Rel-8
Where
Core Network › Evolved Packet Core
Specifications
10 specs
BBERF Description Purpose What changed Family Neighbours Detected Changes Specifications

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.

What changed in its specifications

The latest release-to-release comparison of specifications that define BBERF. Each summary describes the whole specification, not only this term.

TS 23.203Rel-16 → Rel-17

NB-IoT/eMTC support for Non-Terrestrial Networks: adds QCI characteristic for satellite access, note on GEO/LEO delays, and PCRF policy control for satellite PDN connections.

Full comparison in TS 23.203 →
TS 29.154Rel-13 → Rel-14

Added Diameter Load Information Conveyance protocol and Load AVP. Updated Diameter Base Protocol notes referencing RFC 6733, keeping Vendor-Specific-Application-Id AVP required.

Full comparison in TS 29.154 →

Technology family

Core network elements and functions · Core Network

  1. Phase 1 AuC, EIR, GMSC, HLR, IWF, MSC, VLR
  2. Phase 2 SMS-GMSC, SMS-IWMSC
  3. R96 GGSN, SGSN
  4. R99 3G-SGSN, GLR, IM-GSN, IM-MSC
  5. Rel-4 CS-MGW, GMSC Server, MSC Server
  6. Rel-5 HSS, SLF
  7. Rel-6 3GPP AAA Server
  8. Rel-7 PCEF, PCRF
  9. Rel-8 ANDSF, BBERF, ePDG, MME, PGW, SGW
  10. Rel-9 HLR-FE, HSS-FE, UDR
  11. Rel-10 L-GW
  12. Rel-11 TDF
  13. Rel-14 PGW-C, PGW-U, SGW-C, SGW-U, TDF-C, TDF-U
  14. Rel-15 AMF, AUSF, PCF, SMF, SMF+PGW-C, UDM, UPF

Members and relations were proposed independently by several models and kept only where at least two agree; quotes are verified verbatim against the specifications. Release = first approved version of the defining specification.

Release Timeline

Detected Changes Across Releases

verified against 3GPP sources

Documented changes in 10 releases, each verified against the text of 3GPP specifications or approved change requests and shown with the exact wording. The release timeline above shows the same releases. A release without an entry has no documented change for this term.

Rel-8 introduced

BBERF is specified for the first time in Rel-8, with bearer binding, event reporting and QoS rule enforcement, and Gxx procedures for gateway control sessions and QoS rule requests.

  • “Event reporting: The BBERF shall report events to the PCRF based on the event triggers installed by the PCRF.” TS 29.212 v8.24.0
  • “the Bearer Binding Function (BBF) within BBERF shall ensure that the service data flow is carried over the bearer with the appropriate QoS class” TS 29.212 v8.24.0
  • “The BBERF includes the following functionalities:” TS 23.203 v8.15.0
Rel-9 specification text

BBERF behaviour changed in Rel-9: it supports emergency services and QoS rule requests without an IMSI, reports CSG user information changes, and sends PDN Connection ID in Gateway Control Session establishment.

  • “The PCEF, BBERF and PCRF shall support request for PCC/QoS Rules that do not include an IMSI.” TS 29.212 v9.19.0
  • “the BBERF should report any changes in user CSG information when the UE enters/leaves/accesses via a CSG cell.” TS 23.203 v9.14.0
  • “For case 2b the BBERF shall send the Called-Station-Id AVP including the Emergency APN.” TS 29.212 v9.19.0
Rel-10 specification text

BBERF gained new behaviour in Rel-10: multiple BBERFs for IP flow mobility with PCRF routing-rule-based QoS rule provisioning, per-BBERF event triggers, and PCRF restart handling.

  • “The PCRF shall select either the PCEF or any applicable BBERF as the bearer binding function for each service data flow” TS 29.212 v10.17.0
  • “the PCEF shall include the Routing-IP-Address AVP within the Event-Report-Indication AVP to identify the BBERF for which the event triggers are to be installed” TS 29.212 v10.17.0
  • “the BBERF should not send the Gateway Control Session modification request towards a PCRF and the BBERF may tear down the associated PDN connection” TS 29.212 v10.17.0
Rel-11 specification text

BBERF behaviour was extended in Rel-11: it derives uplink traffic mapping information when no suitable QoS rule exists, reports access network information (location, time zone) to the PCRF, and signals extended TFT filter support.

  • “the BBERF shall derive traffic mapping information based on implementation specific logic” TS 29.212 v11.19.0
  • “the BBERF shall determine if it can obtain the required location information for the used IP CAN type” TS 29.212 v11.19.0
  • “the indication of BBERF support for the extended TFT filter format” TS 23.203 v11.15.0
Rel-12 specification text

BBERF requirements were extended: it must re-evaluate bearer binding when the default bearer QoS changes, and ADC/TDF event-trigger handling now involves reporting via the BBERF.

  • “The BBERF shall re-evaluate the bearer binding (as defined in clause 6.1.1.4) taking into account the default bearer QoS change” TS 23.203 v12.11.0
  • “The PCEF/BBERF shall re-evaluate the bearer binding procedure defined in clause 5.4 in the 3GPP 3GPP TS 29.213 [8]” TS 29.212 v12.14.0
  • “The functional entities listed in clause 6.2 apply, except BBERF.” TS 23.203 v12.11.0
Rel-13 specification text

BBERF gained resource-sharing behaviour for QoS rules (common GBR/MBR calculation from Sharing-Key AVPs) and downlink QoS enforcement for TDF-marked DSCP traffic, plus a ResShare feature indicator.

  • “The BBERF shall then, for QoS rules bound to the same bearer and the same sharing key value, use the highest GBR value among those QoS rules” TS 29.212 v13.13.0
  • “The BBERF shall apply resource sharing if at least two QoS rules bound to the same bearer share the same value” TS 29.212 v13.13.0
  • “the BBERF shall support the same procedures for handling different IP‑CAN bearer establishment modes as specified for the PCEF” TS 23.203 v13.10.0
Rel-14 specification text

TS 29.212 adds QoS rule versioning for the BBERF: it must include Content-Version AVP(s) in the QoS-Rule-Report AVP for rules provisioned with a content version.

  • “Whenever the BBERF provides a QoS rule report for rules that were provisioned with a content version, the BBERF shall include the Content-Version AVP(s)” TS 29.212 v14.11.0
  • “When the RuleVersioning feature is supported, the BBERF and PCRF shall comply with the procedures specified in this subclause.” TS 29.212 v14.11.0
Rel-15 specification text

TS 29.212 added BBERF support for the Extended-BW-NR feature during Gateway Control Session establishment, following the PCEF behaviour, and S9 APN-AMBR handling gained extended AVPs.

  • “if the BBERF supports the Extended-BW-NR feature, the same behaviour as described for the PCEF in subclause 4.5.30 applies for the BBERF.” TS 29.212 v15.9.0
Rel-16 specification text

TS 29.212 now states that the BBERF is not integrated into the RLOS support, adding a limitation on BBERF capability.

Rel-17 specification text

When requesting QoS Rules at Gateway Control Session establishment, the BBERF may now send the IMEI(SV) in User-Equipment-Info or User-Equipment-Info-Extension (if that feature is supported) when the IMSI is unavailable.

  • “the BBERF shall include the IMEI(SV) within the User-Equipment-Info AVP or the User-Equipment-Info-Extension AVP if the User-Equipment-Info-Extension feature is supported” TS 29.212 v17.3.0

Defining Specifications

3GPP specifications that define or reference BBERF, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 23.203 vk10 Policy and Charging Control Architecture Rel-20 read
TS 29.154 vj00 Nt Reference Point Protocol Rel-19 read
TS 29.201 vj00 RESTful Rx Interface for AF-PC Communication Rel-19 read
TS 29.212 vk00 Diameter-Based PCC Reference Points Rel-20 read
TS 29.213 vj30 PCC Procedures and Flows Rel-19 read
TS 29.215 vj00 S9 Reference Point Stage 3 Specification Rel-19 read
TS 29.804 v801 CT3 Aspects of System Architecture Evolution Rel-8 read
TS 29.810 vd00 Diameter Load Control Study Rel-13 read
TS 29.816 va00 PCRF Failure and Restoration Study Rel-10 read
TS 29.817 vc10 Study on XML-based Rx interface for PCC Rel-12 read