Description
Gating control is a fundamental policy enforcement function in 3GPP networks, defined within the Policy and Charging Control (PCC) architecture. It refers to the process of blocking or allowing packets that belong to a specific service data flow (SDF) or a detected application's traffic to pass through to the desired endpoint. This control is typically applied at the User Plane Function (UPF) or a similar enforcement point, based on instructions received from the Policy Control Function (PCF) or PCRF. Gating control is essential for ensuring that only authorized traffic is allowed to traverse the network, and it is often used in conjunction with other policy controls such as QoS enforcement and charging.
The mechanism works by installing gating control instructions in the enforcement point (e.g., UPF, P-GW, BBERF). These instructions specify whether the packets of a particular SDF or application should be allowed to pass (gate open) or blocked (gate closed). The decision to open or close the gate is made by the policy function based on various criteria, such as subscription information, application requirements, network conditions, or operator policies. For example, a gate might be closed for a service that the user is not subscribed to, or it might be opened only during certain times of day. Gating control can also be used to implement temporary blocking, such as during congestion or for legal interception.
In the 5G system, gating control is part of the Session Management Function (SMF) and UPF interactions, where the SMF receives policy decisions from the PCF and configures the UPF accordingly. The UPF then enforces the gating by inspecting packet headers and matching them against the SDF filters. If a packet matches an SDF with a closed gate, it is discarded; if the gate is open, the packet is forwarded. The gating control information is typically included in the QoS rules or PCC rules that are installed in the enforcement point.
Gating control is closely related to other PCC functions such as QoS control and charging. While QoS control manages the bandwidth and priority of traffic, gating control simply determines whether traffic is allowed or not. Charging control, on the other hand, may be influenced by gating decisions, as traffic that is blocked may not be charged. The integration of these functions allows operators to implement sophisticated policies that balance network resources, user experience, and revenue.
Over the releases, the definition of gating control has evolved to include not only service data flows but also detected application's traffic, reflecting the increasing importance of application-aware policies. In Release 20, the definition was further updated to specify that packets are blocked or allowed to pass through to the UPF, aligning with the 5G core architecture. This evolution demonstrates the ongoing adaptation of gating control to new network paradigms and service requirements.
Purpose & Motivation
Gating control exists to provide a simple yet powerful mechanism for controlling access to network services at the packet level. It solves the problem of unauthorized or unwanted traffic consuming network resources or reaching endpoints. By allowing operators to selectively block or allow specific service data flows or applications, gating control enables fine-grained policy enforcement without complex traffic shaping or deep packet inspection. It is particularly useful for implementing subscription-based access control, where certain services are only available to users with appropriate subscriptions.
Historically, gating control was introduced in Release 7 as part of the PCC architecture to support the growing need for differentiated services in mobile networks. Before its introduction, access control was often limited to basic firewall rules or access control lists, which lacked the dynamic and policy-driven nature required for mobile broadband. Gating control provided a standardized way to enforce policy decisions from the PCRF/PCF, ensuring consistent behavior across different access technologies and vendor equipment.
With the evolution to 5G, gating control continues to play a vital role in network slicing and edge computing, where traffic must be steered and controlled based on slice-specific policies. It also supports new use cases such as ultra-reliable low-latency communications (URLLC) and massive IoT, where precise control over traffic flows is essential. The adaptation of the definition to include detected application's traffic and the UPF reflects the shift towards application-aware and cloud-native core networks.
Release Timeline
Evolution Across Releases
Wording changed: The definition was expanded to include 'detected application's traffic' in addition to 'service data flow', reflecting the introduction of application detection and control features. The new definition reads: 'The process of blocking or allowing packets, belonging to a service data flow/ detected application's traffic, to pass through to the desired endpoint.'
Wording changed: The definition was updated to specify that packets are blocked or allowed to pass through to the UPF, aligning with the 5G core architecture. The new definition reads: 'The process of blocking or allowing packets, belonging to a service data flow / detected application's traffic, to pass through to the UPF.'
Defining Specifications
3GPP specifications that define or reference Gating control, 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 |