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

Glossary term · Core Network

PGW-C

PDN Gateway Control plane function

Core Network →

PGW-C is the control plane component of the PDN Gateway in the 5G Core network, handling session management, policy enforcement, and charging control as part of the CUPS architecture.

Introduced
Rel-14
Where
Core Network › 5G Core
Specifications
8 specs
Also in
Management
PGW-C Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

The PGW-C (PDN Gateway Control plane function) is a core network function introduced as part of the Control and User Plane Separation (CUPS) architecture in 3GPP Release 14. It represents the decoupling of the traditional P-GW (Packet Data Network Gateway) into separate control plane (PGW-C) and user plane (PGW-U) entities. This separation allows for independent scaling, deployment, and evolution of the control and user plane functions. The PGW-C is responsible for the intelligence and signaling aspects of the gateway.

Architecturally, the PGW-C interfaces with several other core network functions. It communicates with the Policy and Charging Rules Function (PCRF) via the Gx interface to receive policy and charging control (PCC) rules. It interacts with the Online Charging System (OCS) via the Gy interface for online credit control and with the Offline Charging System (OFCS) via the Gz interface for offline charging data record (CDR) generation. For session management, it connects to the Serving Gateway Control plane function (SGW-C) and the Mobility Management Entity (MME) in the Evolved Packet Core (EPC).

Its primary operational role involves managing Packet Data Network (PDN) connections for User Equipment (UE). When a UE attaches to the network and requests a PDN connection, the PGW-C is responsible for session establishment, modification, and termination. It allocates an IP address to the UE (or delegates this to the PGW-U), enforces QoS policies based on PCC rules from the PCRF, and manages charging based on the user's service data flow. It also handles mobility events, such as handovers between different access technologies (e.g., LTE to Wi-Fi), ensuring session continuity.

The PGW-C works in tandem with the PGW-U via a standardized control protocol, defined in 3GPP specifications such as TS 29.244 (PFCP - Packet Forwarding Control Protocol). The PGW-C uses PFCP to instruct the PGW-U on how to handle the user plane traffic. This includes installing, modifying, or deleting packet detection rules (PDRs), forwarding action rules (FARs), QoS enforcement rules (QERs), and usage reporting rules (URR). This master-slave relationship allows the PGW-C to centrally control multiple, potentially distributed, PGW-U instances, enabling flexible and efficient traffic routing and processing.

Purpose & Motivation

The PGW-C was created to address the limitations of the monolithic P-GW architecture used in earlier 3GPP releases. In traditional EPC, the P-GW was a single network node combining both control and user plane functionalities. This monolithic design posed several challenges, including inefficient scaling (the entire node had to be scaled even if only user plane capacity was needed), limited deployment flexibility (control and user plane functions had to be co-located), and hindered innovation (upgrades to one plane could impact the other).

The primary motivation for its creation was the industry-wide drive towards network function virtualization (NFV) and software-defined networking (SDN), which demand disaggregated, software-based components that can be deployed independently. The Control and User Plane Separation (CUPS) architecture, formalized in Release 14, was the 3GPP's response. By splitting the P-GW into PGW-C and PGW-U, operators gained the ability to scale the control plane (which handles signaling and policy) and the user plane (which handles high-throughput data packets) independently based on traffic patterns. For instance, user plane functions could be deployed at the network edge for low-latency services, while control plane functions could remain centralized for efficient management.

This separation also paved the way for the 5G Core (5GC) network architecture, where the Session Management Function (SMF) and User Plane Function (UPF) are direct conceptual successors to the PGW-C and PGW-U, respectively. The introduction of PGW-C allowed for a smoother evolution from EPC to 5GC, enabling early adoption of cloud-native principles and distributed architectures within the 4G network, thus solving the problems of scalability, flexibility, and cost-efficiency in the face of exponentially growing mobile data traffic.

What changed in its specifications

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

TS 23.214Rel-14 → Rel-15

Rel-15 added a functional split between Radio and Core, incorporating UE capabilities including dual connectivity with NR support into PGW-U and SGW-U selection.

Full comparison in TS 23.214 →
TS 28.708Rel-18 → Rel-19

Rel-19 adds management for NTN Phase 2, including generic store-and-forward satellite configuration, onboard satellite attributes, and storage/time-related fields.

Full comparison in TS 28.708 →

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
  • PGW-C part of PGW (not stated verbatim in the specifications)

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 7 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-14 introduced

The PGW-C is specified for the first time as the control plane function of the split PGW, selecting and controlling the PGW-U, managing UE IP addresses and F-TEIDu allocation, and controlling charging via Sx.

  • “the PGW-C is responsible for selecting the PGW-U (as described in clause 4.3.3) and for controlling the PGW-U” TS 23.214 v14.9.0
  • “The UE IP address management shall be performed by the PGW-C.” TS 23.214 v14.9.0
  • “When the PGW-C determines to stop the charging and usage monitoring actions for the PDN connection, it shall indicate the PGW-U to stop collecting the usage information.” TS 23.214 v14.9.0
Rel-15 specification text

PGW-C gained 5GS interworking roles in Rel-15: combined PGW-C+SMF selection, SM policy interactions with PCF, and UPF selection taking UE NR capabilities into account.

  • “policy interactions between PDN GW and PCRF specified in TS 23.401 [13] are replaced by equivalent interactions between PGW-C+SMF and PCF” TS 23.502 v15.17.0
  • “Enable SGW-C & PGW-C selection of UPF to take UE's NR capabilities into account” TS 23.214 v15.5.0
  • “it indicates to the PGW-C+SMF that 5GS Interworking is supported without the N26 interface” TS 29.274 v15.9.0
Rel-16 1 CR

In Rel-16 the combined SMF+PGW-C gained new behaviour: it serves UEs without 5GC NAS, uses SMF+PGW-C selection by the MME, and handles emergency configuration, FQDN discovery and PCF policy interactions.

  • “the MME may use the UE's support for 5GC NAS indication included in the UE Network Capability and/or UE's subscription from HSS” TS 23.502 v16.19.0
  • “the AMF shall discover the SMF instance by an NF/NF service discovery procedure using the FQDN for the S5/S8 interface received from the MME” TS 23.502 v16.19.0
  • Serving 4G only UEs by SMF+PGW-C TS 23.502CR1328
Rel-17 specification text

In Rel-17 the SMF+PGW-C gained new behaviour: restoration of PDN connections after a PGW-C/SMF change, UP integrity protection enforcement, ECS address provisioning via PCO, and UDM registration of PDU Session IDs.

  • “the SMF+PGW-C releases the bearers associated with the PDN CONNECTION.” TS 23.502 v17.15.0
  • “the SMF+PGW-C may provide the ECS Address Configuration Information (as described in clause 6.5.2 of TS 23.548 [74]) to the UE in the PCO.” TS 23.502 v17.15.0
  • “the (alternative) PGW-C/SMF shall consider that other flags in the Indication Flags IE set for the PDN connection (before the restoration) remain unchanged.” TS 29.274 v17.12.0
Rel-18 1 CR

In Rel-18 the SMF+PGW-C gained URSP provisioning support in EPS: it receives the UE indication, selects a URSP-capable PCF, forwards the UE Policy Container to the PCF, and reports delivery results.

  • “the SMF+PGW-C receives the Indication of URSP Provisioning Support from the UE as defined in TS 23.501 [2].” TS 23.502 v18.14.0
  • “the SMF+PGW-C provides the UE Policy Container to the PCF.” TS 23.502 v18.14.0
  • Support of PGW-C/SMF Set feature over S11 TS 29.274CR2094
Rel-19 1 CR

PGW-C+SMF behaviour was extended in Rel-19, e.g. handling of Ethernet MA PDU Sessions with MPQUIC-E, and PGW-C/SMF PDN connection restoration with new network-slice-based PGW selection and redirection.

  • “The PGW-C+SMF excludes MPQUIC-E from the MA PDU Session capabilities. In this case only ATSSS-LL may be enabled.” TS 23.502 v19.9.0
  • “the source PGW/SMF may select another PGW/SMF supporting the network slice for which the UE has a subscription” TS 29.274 v19.6.0
  • P-CSCF triggering SMF/PGW-C failure checking TS 23.380CR0129
Rel-20 1 CR

SMF+PGW-C gains NSSAA support over EPC: it checks for existing PDN connections for the S-NSSAI, runs EAP authentication via NSSAAF, and signals Pending status and failure in PCO.

  • “the SMF+PGW-C shall check locally whether there is already any PDN connection established associated with the same S-NSSAI.” TS 23.502 v20.3.0
  • “the SMF+PGW-C shall determine that session continuity from EPS to 5GS is not supported if the S-NSSAI of the PDN connection is in Pending status.” TS 23.502 v20.3.0
  • Correcting the behaviour of PCF and SMF+PGW-C for 5GS to EPS mobility scenario TS 29.512CR1495

Defining Specifications

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

SpecificationTitleRelease
TS 23.214 vj00 Control and User Plane Separation for EPC Rel-19 read
TS 28.708 vj00 EPC NRM Integration Reference Point Information Service Rel-19 read
TS 29.061 vk10 Packet Domain Interworking Requirements Rel-20 read
TS 29.244 vk10 PFCP for Control and User Plane Separation Rel-20 read
TS 29.561 vk10 5G Network Interworking Procedures Rel-20 read
TS 29.844 ve00 Control and User Plane Separation for EPC Nodes Rel-14 read
TS 32.867 vf10 Management Impacts of EPC CUPS Rel-15 read
TS 33.127 vj80 Lawful Interception Architecture Rel-19 read