Description
The Serving Gateway User plane function (SGW-U) is the packet-forwarding engine resulting from the disaggregation of the traditional Serving Gateway. Introduced with Control and User Plane Separation (CUPS), the SGW-U handles all the data plane processing for user traffic in the Evolved Packet Core (EPC). Its primary role is to serve as the mobility anchor for the user plane during inter-eNodeB handovers within LTE and to route and forward traffic between the Radio Access Network (RAN) and the Packet Data Network Gateway (PGW). It operates under the direct command of its associated control plane function, the SGW-C, using the Packet Forwarding Control Protocol (PFCP) over the Sxa reference point.
Functionally, the SGW-U performs packet inspection, classification, and enforcement actions based on rules installed by the SGW-C. These rules are conveyed through PFCP messages and include Packet Detection Rules (PDRs), Forwarding Action Rules (FARs), and QoS Enforcement Rules (QERs). A PDR defines how to identify a packet flow (using parameters like source/destination IP, port, and GTP tunnel endpoint identifiers). Once a packet matches a PDR, the associated FAR dictates the action, such as forwarding the packet to a specific next-hop tunnel (e.g., towards an eNodeB or a PGW-U), buffering, or dropping it. QERs allow the SGW-U to apply rate policing, marking, and scheduling to ensure the agreed-upon Quality of Service. The SGW-U is also responsible for encapsulating and decapsulating user IP packets within GPRS Tunneling Protocol (GTP-U) tunnels that connect it to the eNodeB (S1-U) and the PGW-U (S5/S8-U).
Architecturally, the separation allows the SGW-U to be implemented as a high-performance, streamlined packet processing node, often using hardware acceleration. It can be deployed in a distributed manner, much closer to the RAN than a centralized data center. This distribution is critical for reducing latency, which benefits applications like mobile gaming, autonomous vehicles, and augmented reality. In 5G interworking scenarios, the SGW-U can be collocated with or interconnected to a 5G User Plane Function (UPF) to facilitate seamless user plane handovers between 4G and 5G access. Its specifications span architecture (23.214), management (28.708, 32.867), the PFCP protocol (29.244), and security requirements (33.127).
Purpose & Motivation
The SGW-U was developed to overcome the inflexibility of the integrated SGW appliance. In traditional EPC deployments, the SGW's user plane was tied to its control plane, preventing independent optimization and scaling. This coupling was ill-suited for emerging trends like network function virtualization (NFV) and the need for low-latency edge computing. Scaling user plane throughput required provisioning entire new SGW instances, including redundant control plane resources, leading to inefficient capital expenditure.
The creation of the SGW-U, finalized in 3GPP Release 14 as part of CUPS, was driven by the desire for a more agile, cloud-native network architecture. By extracting the user plane into a separate function, operators can deploy lightweight, stateless SGW-U instances using commercial off-the-shelf hardware or virtualized platforms at optimal locations in the network topology. This enables traffic breakout at the edge for local services and reduces backhaul costs. The SGW-U's programmability via PFCP also opens the door for software-defined networking (SDN) principles in the mobile core, allowing for more dynamic traffic steering and service chaining. This separation was a direct precursor to the native control/user plane separation seen in the 5G Core's SMF and UPF, proving the concept for next-generation networks.
What changed in its specifications
The latest release-to-release comparison of specifications that define SGW-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
- SGW-U part of SGW (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 4 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 introduces the SGW-U as the user plane function of the split Serving Gateway, controlled by the SGW-C over Sx, with end-marker handling, F-TEIDu allocation, DL data buffering and restoration procedures.
- “SGW-U Serving Gateway User plane function” TS 29.244 v14.8.0
- “SGW-C shall indicate the SGW-U to switch the S1 path(s) by sending an Sx session modification request message” TS 23.214 v14.9.0
- “During or immediately after an SGW-U Restart, the SGW-U shall place local SGW-U Recovery Time Stamp value” TS 23.007 v14.6.0
SGW-U selection, GTP-U header handling and restart/failure handling were specified or changed, including selecting an SGW-U optimized for NR and deleting Sx sessions after an SGW-C restart.
- “Correcting the condition for selection of SGW-U for NR as secondary RAT” TS 23.214 v15.5.0
- “The SGW-C shall select, among the candidate SGW-U functions, an SGW-U function which supports all the capabilities required for the particular UE session” TS 29.244 v15.10.0
- “the SGW-U shall delete all session contexts affected by the unreachability of the peer PFCP entity in the SGW-C that it may have stored.” TS 23.007 v15.4.0
In Rel-16 the SGW-U always allocates and releases F-TEIDu in the UP function, replacing the configuration-dependent behaviour, and gains MT-EDT reporting of DL data packet size.
- “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
- “to request the SGW-U to report the sum of DL Data Packets Size in byte when sending Downlink Data Report” TS 29.244 v16.13.0
- “The SGW-U allocates an F-TEIDu for each and every bearer received in the Sx Session Establishment Request.” TS 23.214 v16.2.0
SGW-U gained new reporting and charging roles in Rel-17: NSPOC start-pause-of-charging notification via user plane, GTP-U peer restart reporting, and expanded FQ-CSID handling.
- “to request the UP function (SGW-U or I/V-UPF) to send a Start Pause of Charging indication to the upstream GTP-U entity(s)” TS 29.244 v17.10.0
- “a user plane function (SGW-U or PGW-U) and a control plane function (SGW-C or PGW-C) may optionally support reporting of a peer GTP-U entity restart” TS 23.007 v17.7.0
Defining Specifications
3GPP specifications that define or reference SGW-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 28.708 vj00 | EPC NRM Integration Reference Point Information Service | Rel-19 read |
| TS 29.244 vk10 | PFCP for Control and User Plane Separation | 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 |