Description
The PGW-U (PDN Gateway User plane function) is the data plane component resulting from the separation of the traditional P-GW (Packet Data Network Gateway) as defined in 3GPP's Control and User Plane Separation (CUPS) architecture starting in Release 14. It is responsible for the actual forwarding and processing of user data packets between the User Equipment (UE) and external Packet Data Networks (PDNs), such as the internet or an IMS network. While the PGW-C handles signaling and intelligence, the PGW-U handles the high-throughput, latency-sensitive data path.
Architecturally, the PGW-U sits on the user plane path between the Serving Gateway User plane function (SGW-U) and the external network. It interfaces with the SGW-U via the S5/S8-U interface (using GTP-U tunnels) and connects to the external PDN via the SGi interface. Its most critical relationship is with its controlling PGW-C, with which it communicates using the Packet Forwarding Control Protocol (PFCP) as defined in TS 29.244. The PGW-C acts as the master, sending control commands, while the PGW-U acts as the slave, executing those commands on the user plane traffic.
Its operation is rule-driven. The PGW-C installs rules in the PGW-U via PFCP sessions. These rules include Packet Detection Rules (PDRs) that identify which user plane packets to act upon based on criteria like tunnel endpoint identifiers (TEIDs), IP addresses, and port numbers. For packets matching a PDR, the PGW-U applies corresponding Forwarding Action Rules (FARs), which dictate actions such as forwarding the packet to a specific tunnel (e.g., towards the SGW-U or the external network), dropping it, or buffering it. It also applies QoS Enforcement Rules (QERs) to mark packets with DiffServ Code Points (DSCP), enforce uplink/downlink bitrate limits, and apply QoS Flow identification.
The PGW-U performs several key user plane functions. It acts as the anchor point for mobility, meaning the UE's IP address is anchored here, providing session continuity as the user moves and the access network connection point (e.g., the SGW-U) changes. It performs packet inspection and enforcement of charging policies by counting packets/bytes per service data flow as instructed by Usage Reporting Rules (URRs), sending usage reports to the PGW-C for charging. It also handles lawful interception by duplicating packets as required. The decoupled nature of the PGW-U allows it to be implemented as a high-performance, potentially hardware-accelerated function that can be deployed in distributed locations, such as at the network edge, to reduce latency for applications like augmented reality or autonomous vehicles.
Purpose & Motivation
The PGW-U was created to solve the scalability and deployment inflexibility inherent in the monolithic P-GW design of pre-Release 14 EPC networks. In the traditional architecture, the user plane and control plane were tightly integrated within a single physical or virtual network appliance. This coupling meant that scaling to handle more user plane data traffic required scaling the entire node, including the control plane resources, which was inefficient and costly. It also forced a centralized deployment model, preventing operators from placing data forwarding functions closer to users to improve performance.
The driving force behind its development was the industry trend towards network virtualization, cloud-native design, and the need to support diverse, low-latency services anticipated with 5G. The CUPS architecture, formalizing the split, was a direct response. By creating a standalone PGW-U, operators gained the ability to scale the data plane independently and massively, using commodity hardware or specialized data plane accelerators. It also enabled distributed deployment, allowing user plane functions to be placed at central offices, base station aggregation sites, or even at the base station itself (as in Mobile Edge Computing), drastically reducing round-trip time for latency-critical applications.
Furthermore, this separation aligned with Software-Defined Networking (SDN) principles, where the control logic (PGW-C) is centralized and programmable, while the forwarding elements (PGW-U) are simple and distributed. This model simplifies network management, enables faster introduction of new services, and reduces operational costs. The PGW-U concept directly evolved into the User Plane Function (UPF) in the 5G Core network, making it a crucial architectural stepping stone. It solved the problems of monolithic scaling, lack of deployment flexibility, and inability to optimize for both control plane signaling efficiency and user plane throughput/low-latency, which were significant limitations for handling the exponential growth and evolving requirements of mobile broadband traffic.
What changed in its specifications
The latest release-to-release comparison of specifications that define PGW-U. Each summary describes the whole specification, not only this term.
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 →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
- Phase 1 AuC, EIR, GMSC, HLR, IWF, MSC, VLR
- Phase 2 SMS-GMSC, SMS-IWMSC
- R96 GGSN, SGSN
- R99 3G-SGSN, GLR, IM-GSN, IM-MSC
- Rel-4 CS-MGW, GMSC Server, MSC Server
- Rel-5 HSS, SLF
- Rel-6 3GPP AAA Server
- Rel-7 PCEF, PCRF
- Rel-8 ANDSF, BBERF, ePDG, MME, PGW, SGW
- Rel-9 HLR-FE, HSS-FE, UDR
- Rel-10 L-GW
- Rel-11 TDF
- Rel-14 PGW-C, PGW-U, SGW-C, SGW-U, TDF-C, TDF-U
- Rel-15 AMF, AUSF, PCF, SMF, SMF+PGW-C, UDM, UPF
- PGW-U 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 sourcesDocumented changes in 6 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.
Introduced in Rel-14 (release dating of the term; no individual change cited).
PGW-U behaviour was specified and changed in Rel-15: PFCP-based gating, QER correlation, restart/failure handling, and PGW-U selection (including DCNR and Mapped UE Usage Type) were added or modified.
- “Gating control refers to the process within the user plane function (i.e. PGW-U and TDF-U for EPC, UPF for 5GC)” TS 29.244 v15.10.0
- “When a PGW-U detects that a peer PFCP entity in the PGW-C has restarted, the PGW-U shall delete all session contexts” TS 23.007 v15.4.0
- PGW-U selection based on Mapped UE Usage Type with Gn SGSNs TS 29.060CR1055
In the CP/UP split, F-TEIDu allocation moved to always being done by the PGW-U, with the PGW-U returning the allocated F-TEIDu in Sx Session Establishment/Modification Responses, replacing the earlier network-configuration condition.
- “The PGW-U allocates F-TEIDu for the bearer. The PGW-U sends an Sx Session Establishment Response to the PGW-C confirming the successful creation of the Sx session.” TS 23.214 v16.2.0
- “If functional split into SGW-C/PGW-C and SGW-U/PGW-U is supported, F-TEIDu allocation and release is done in the UP function” TS 23.214 v16.2.0
- “the PGW-C shall include a restoration indication in the PFCP Session Establishment Request message to indicate to the PGW-U it is for a restoration of an existing PFCP session” TS 23.007 v16.1.0
PGW-U gained new Rel-17 roles: acting as L2TP LAC towards an LNS, supporting UE IP address management/forwarding of address messages, and handling PFCP session restoration and NSPOC with PGW-C/SMF sets.
- “the PGW-U may setup L2TP towards an L2TP network server (LNS) in the DN and tunnel the PDN Connection user plane traffic in L2TP” TS 23.214 v17.0.0
- “The PGW-U shall support forwarding of the UE IP address management related messages to the PGW-C” TS 23.214 v17.0.0
- “upon detecting a GTP-U user plane path failure, the SGW-U or PGW-U shall report the user plane path failure” TS 23.007 v17.7.0
TS 29244 now lets the SMF/PGW-C provision more than two UL PDRs and DL FARs in the UPF/PGW-U for MA PDU sessions with dedicated EPS bearers, and extends PFCP restoration requirements for PGW-U.
- “more than two UL PDRs and DL FARs may be provisioned by the SMF/PGW-C in the UPF/PGW-U” TS 29.244 v18.10.0
- “the CP function (e.g. a PGW-C or a SMF) and the UP function (a PGW-U or a UPF) may support the feature” TS 29.244 v18.10.0
PGW-U gains optional UDP/IP Header Removal & Restoration for IMS PDN connections over NB-IoT (GEO), inserting or removing the UDP/IP header on IMS voice packets as instructed by the PGW-C via PDR/FAR.
- “to instruct the PGW-U to forward the IMS voice packets over SGi to IMS network” TS 29.244 v20.1.0
- “to instruct the PGW-U to forward these IMS voice packets (without UDP/IP header) over S5/S8 tunnel” TS 29.244 v20.1.0
- “The support of UDP/IP Header Removal & Restoration as described in this clause is optional for both the PGW-C and the PGW-U.” TS 29.244 v20.1.0
Defining Specifications
3GPP specifications that define or reference PGW-U, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.214 vj00 | Control and User Plane Separation for EPC | Rel-19 read |
| TS 23.700 vk10 | AI/ML Application Layer Support Phase 2 | Rel-20 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 |