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

Glossary term · Interface

Gx

Reference point between the PCRF and the PCEF

Interface →

Gx is the 3GPP Diameter-based reference point between the PCRF and the PCEF used to transport policy decisions, PCC rules, QoS parameters, charging instructions, and session events for dynamic network resource control.

Introduced
Rel-7
Where
Core Network › Evolved Packet Core
Specifications
2 specs
Gx Description Purpose What changed Family Neighbours Specifications

Description

Gx is a 3GPP control-plane reference point between the Policy and Charging Rules Function (PCRF) and the Policy and Charging Enforcement Function (PCEF). In the EPC PCC architecture, the PCEF is normally located in the PDN Gateway, while the PCRF is a centralized policy decision node. Gx is specified in 23.203 and 29.212 and uses the Diameter protocol to exchange policy-related information. It does not carry user traffic; instead, it carries session-level and rule-level signaling that tells the PCEF how to handle a UE's IP-CAN session.

The basic operation of Gx begins when the PCEF establishes an IP-CAN session for a UE. The PCEF sends a Diameter Credit-Control Request (CCR) message containing session identifiers, user identity, UE IP address, APN, radio access technology type, user location, and service information. The PCRF evaluates this information against subscriber profiles, service rules, operator policies, and any application-level input received from the Rx interface. The PCRF responds with a Diameter Credit-Control Answer (CCA) message that may include one or more PCC rules. These rules define packet filters, precedence, QoS parameters, charging identifiers, and event reporting triggers.

A PCC rule is the core object transported by Gx. It tells the PCEF how to classify user-plane packets, which EPS bearer to use, what QoS characteristics to enforce, and how charging should be applied. For example, a rule may require a video stream to receive a guaranteed bitrate bearer with a specific QCI, while best-effort browsing is mapped to a non-GBR default bearer. The PCEF installs the rule, binds matching traffic to the appropriate bearer, marks packets, gates traffic if needed, and reports events back to the PCRF. When session conditions change, such as UE IP address, APN, or bearer status, the PCEF can send an update, and the PCRF can provision, modify, or remove rules.

Gx also supports event reporting and re-authorization. The PCRF can ask the PCEF to report when a UE moves to a new location, changes radio access, exceeds a data volume threshold, or starts or stops a service. This enables dynamic policy adjustment, such as throttling a session when a quota is reached or elevating priority for a voice call. The PCRF can also initiate changes through Diameter re-authentication mechanisms when service information arrives from an application function via Rx. In this way, Gx connects the service layer to the network enforcement layer without requiring the application to directly manage bearers.

The interface is critical to charging and quality control. Online charging and offline charging may depend on Gx-provided rules and reporting triggers, while Gy and Gz interfaces handle charging interactions. Gx complements the S9, Rx, and other Diameter interfaces by focusing on the PCEF-PCRF relationship. It allows operators to move from static, pre-provisioned QoS and charging configurations to dynamic, per-service policy decisions. This is especially important for LTE, where multiple bearers, APNs, and roaming scenarios require a consistent policy anchor at the PGW. Gx therefore provides the control-plane foundation for differentiated services, congestion management, and revenue assurance in 3GPP packet core networks.

Purpose & Motivation

Gx was introduced to support dynamic policy and charging control in 3GPP packet core networks. Before Rel-7, QoS and charging were often configured statically or handled separately by different network elements. This made it difficult for operators to apply service-aware policies, especially as IP multimedia services, video streaming, VoLTE, and differentiated data plans emerged. A centralized policy decision point was needed to translate subscriber profiles, application requests, and network conditions into enforceable rules at the PCEF.

Gx addresses this by defining a Diameter-based interface between the PCRF and the PCEF. The PCRF can make decisions based on user identity, APN, service information from the Rx interface, subscriber profile, and network context. The PCEF enforces those decisions by installing PCC rules, mapping traffic to bearers, applying QoS, and triggering charging. This separation solves the problem of fragmented control: applications do not need to manage bearers directly, and the network can enforce consistent policy even when radio conditions, roaming state, or session parameters change.

Its motivation also includes revenue assurance and congestion management. Operators needed to distinguish between services that require guaranteed bandwidth and those that can be best-effort, and to report usage events for online or offline charging. Gx provides the mechanism for provisioning rules, modifying them during a session, and reporting events. This enables per-service charging, policy-based bearer selection, and dynamic adjustment of network resources, which were not practical with static provisioning alone.

What changed in its specifications

The latest release-to-release comparison of specifications that define Gx. 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.212Rel-18 → Rel-19

Rel-19 adds an EPC function health monitoring reporting procedure to TS 29.212. It also adds a session recovery status AVP and a CnHealthMonitor supported feature.

Full comparison in TS 29.212 →

Technology family

Core network interfaces and reference points · Core Network

  1. R97 Gi, Gn, Gp
  2. Rel-7 Gx
  3. Rel-8 S1-MME, S1-U, S11, S5, S8, SGi
  4. Rel-15 N11, N2, N3, N4, N6, N7, N9
  • Gx counterpart in another generation: N7
    “This reference point corresponds to the Gx which resides between the PCEF in the IP-Edge and the PCRF.” TS 23.203

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.

Evolution Across Releases

An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.

Rel-7 Initial

Introduced as part of the Release 7 Policy and Charging Control architecture in 23.203 and 29.212, defining the Diameter-based reference point between the PCRF and the PCEF. It enabled IP-CAN session signaling, dynamic PCC rule provisioning, QoS and charging control, event reporting, and coordination with Rx and charging interfaces.

Defining Specifications

3GPP specifications that define or reference Gx, 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.212 vk00 Diameter-Based PCC Reference Points Rel-20 read