Description
The Binding mechanism is a procedural component of the 3GPP Policy and Charging Control (PCC) architecture, responsible for the creation, modification, and deletion of bindings between service data flows (SDFs) and the underlying transport resources, such as IP-CAN bearers in 4G or QoS Flows in 5G. This mechanism ensures that each SDF is mapped to a bearer or QoS Flow that can satisfy its QoS requirements, as defined by policy rules. The binding mechanism is typically executed by the Policy and Charging Rules Function (PCRF) in 4G or the Policy Control Function (PCF) in 5G, which evaluates the service information, subscription data, and operator policies to determine the appropriate binding. When a new SDF is detected, the PCRF/PCF decides whether to bind it to an existing bearer/QoS Flow or to create a new one. This decision is based on factors such as the QoS Class Identifier (QCI) or 5G QoS Identifier (5QI), Allocation and Retention Priority (ARP), and other QoS parameters. The binding mechanism then instructs the Policy and Charging Enforcement Function (PCEF) or Session Management Function (SMF) to enforce the binding by installing packet filters and QoS parameters. Modifications to bindings occur when QoS requirements change, for example due to a change in the service or network conditions. Deletions happen when an SDF is no longer active. The binding mechanism also handles the removal of bindings when bearers or QoS Flows are released. It ensures efficient resource utilization by allowing multiple SDFs with similar QoS to share the same bearer/QoS Flow, while keeping flows with different QoS separate. The mechanism is defined in 3GPP specifications such as TS 23.203 and TS 23.503, and it is essential for end-to-end QoS enforcement and policy control. In 5G, the binding mechanism has been adapted to work with QoS Flows, which provide more granular QoS handling and support new service requirements. The binding mechanism is a critical enabler for differentiated services and network slicing, allowing operators to dynamically manage QoS based on application needs.
Purpose & Motivation
The Binding mechanism exists to provide a standardized, dynamic method for associating service data flows with the appropriate transport resources in the network. Before its introduction, QoS enforcement was often static and based on bearer-level parameters, which limited the ability to differentiate services and to adapt to changing conditions. The binding mechanism, introduced in 3GPP Release 7 as part of the PCC architecture, solves this by enabling policy-driven, real-time decisions on how to map SDFs to bearers. It allows the network to optimize resource usage by multiplexing flows with similar QoS requirements onto the same bearer, while ensuring that each flow receives the required QoS. This is crucial for supporting a wide range of services with different characteristics, such as voice, video, and data. The mechanism also facilitates the enforcement of fair usage policies and the charging of services based on QoS. In 5G, the binding mechanism has been extended to QoS Flows, which provide more flexible and granular QoS handling, supporting diverse use cases like URLLC and mMTC. The binding mechanism is a key component of the 3GPP QoS framework and continues to evolve to meet new requirements.
What changed in its specifications
The latest release-to-release comparison of specifications that define Binding mechanism. Each summary describes the whole specification, not only this term.
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 →Rel-19 TS 23.503 adds Network Slice Replacement and Energy Saving Indicator reporting, Application Function influence on payload header handling, and Local Offloading Management Policy for edge computing. It also adds ATSSS Phase 4 multi-access steering (MPQUIC-E, ATSSS-LL), spending-limit policy for roaming, and PCF use of network analytics.
Full comparison in TS 23.503 →Release Timeline
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (2 CRs across 2 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Defining Specifications
3GPP specifications that define or reference Binding mechanism, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.203 vk10 | Policy and Charging Control Architecture | Rel-20 read |
| TS 23.503 vk30 | 5G Policy and Charging Control Framework | Rel-20 read |
| TS 29.512 vk10 | Session Management Policy Control Service Stage 3 | Rel-20 read |