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

Glossary term · Core Network

SGW-C

Serving Gateway Control plane function

Core Network →

SGW-C is the control plane component of the Serving Gateway that handles session management, mobility anchoring, and policy enforcement, separating control logic from packet forwarding.

Introduced
Rel-14
Where
Core Network › Evolved Packet Core
Specifications
6 specs
Also in
Management
SGW-C Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

The Serving Gateway Control plane function (SGW-C) is a critical network function introduced as part of the Control and User Plane Separation (CUPS) architecture for the Evolved Packet Core (EPC) and its evolution into 5G. It represents the disaggregation of the monolithic Serving Gateway (SGW) into separate control and user plane entities. The SGW-C is responsible for all the control logic associated with managing user sessions. This includes processing signaling from the Mobility Management Entity (MME) or Access and Mobility Management Function (AMF), such as session establishment, modification, and termination requests. It manages the mobility anchoring point for inter-eNodeB handovers within LTE and acts as the local mobility anchor for 3GPP access when the user equipment (UE) moves between eNodeBs. The SGW-C also interfaces with the Policy and Charging Rules Function (PCRF) or Policy Control Function (PCF) to enforce QoS policies and charging rules for each data session.

Architecturally, the SGW-C communicates with its corresponding user plane function, the SGW-U, using the Packet Forwarding Control Protocol (PFCP) as defined in 3GPP TS 29.244. This protocol allows the SGW-C to instruct the SGW-U on how to handle user plane packets. For example, the SGW-C sends PFCP Session Establishment/Modification/Deletion requests to the SGW-U to create, update, or remove packet detection rules (PDRs), forwarding action rules (FARs), QoS enforcement rules (QERs), and usage reporting rules (URR). This separation allows the SGW-C to be deployed centrally for efficient control, while SGW-U instances can be distributed to the network edge to reduce latency for user traffic.

In a 5G context, the SGW-C is part of the interworking function between the 5G Core (5GC) and the EPC, particularly in non-standalone (NSA) deployment scenarios. It works in conjunction with the User Plane Function (UPF) and the Session Management Function (SMF). The SGW-C's role is to maintain continuity for 4G sessions as networks transition to 5G, ensuring seamless mobility and service. Its operation is detailed across multiple specifications, including architecture (23.214), management (28.708, 32.867), protocol (29.244), and security (33.127).

Purpose & Motivation

The SGW-C was created to address the limitations of the traditional, integrated Serving Gateway in 4G networks. The monolithic SGW combined both control and user plane functions in a single network element, which led to scaling inefficiencies. Scaling for increased control signaling (e.g., during mass device attach events) required scaling the entire box, including expensive user plane packet processing resources. Conversely, scaling for user plane throughput (e.g., during a video streaming surge) necessitated scaling the control plane capacity as well, leading to cost-ineffective and rigid deployments.

The introduction of the SGW-C, as part of the CUPS framework standardized in 3GPP Release 14, was motivated by the need for greater network flexibility, scalability, and innovation. By separating the control plane, operators can centralize and pool SGW-C resources in large data centers for efficient management and signaling processing. This separation enables independent scaling of control and user plane resources based on actual network demands. It also facilitates the deployment of user plane functions (SGW-U) at distributed locations closer to the radio access network, which is a key requirement for low-latency applications and edge computing. This architectural shift was a foundational step towards the fully cloud-native, service-based architecture of the 5G Core network.

What changed in its specifications

The latest release-to-release comparison of specifications that define SGW-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
  • SGW-C 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 sources

Documented changes in 5 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

SGW-C is specified for the first time as the control plane of the split Serving Gateway, selecting and controlling the SGW-U, allocating F-TEIDs, managing buffering, and handling restoration over Sx.

  • “the SGW-C is responsible for selecting the SGW-U (as described in clause 4.3.3) and for controlling the SGW-U” TS 23.214 v14.9.0
  • “SGW-C Serving Gateway Control plane function” TS 29.244 v14.8.0
  • “An SGW-C shall always apply in addition the related PFCP procedures towards the SGW-U.” TS 23.007 v14.6.0
Rel-15 specification text

SGW-C gained new behaviour in Rel-15: it provides UE NR dual-connectivity capabilities over S5/S8, is selected as NR-optimized, and has revised PFCP restart/heartbeat handling with the SGW-U.

  • “the SGW-C shall provide the relevant UE's capabilities when available (e.g. UE support for dual connectivity with NR) over the S5/S8 interface.” TS 23.214 v15.5.0
  • “The MME/SGSN shall be able to select an SGW-C and a PGW-C optimized for NR” TS 29.244 v15.10.0
  • “The SGW-C can determine to reestablish the Sx Association if it receives the cause code "No established PFCP Association"” TS 23.007 v15.4.0
Rel-16 specification text

In Rel-16, F-TEIDu allocation moved to the user plane (SGW-U) instead of the SGW-C, and SGW-C gained a restoration indication and an LI role providing BBIFF-C for S8HR.

  • “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 SGW-C shall include a restoration indication in the PFCP Session Establishment Request message” TS 23.007 v16.1.0
  • “the architecture presented in figure 7.4.7.4-1 is used with SGW-C providing the BBIFF-C and SGW-U providing the BBIFF-U functions” TS 33.127 v16.14.0
Rel-17 specification text

Rel-17 adds SGW-C behaviour: reporting GTP-U user plane path failure and recovery handling, peer GTP-U restart reporting, combined SGW-C/PGW-C/SMF triggered PDN connection restoration, and NSPOC pause-of-charging support.

  • “upon being notified about the user plane path failure, when deciding to delete the bearer contexts associated with the path in failure, the SGW-C or PGW-C shall modify or delete” TS 23.007 v17.7.0
  • “the (new) SGW-C/PGW-C/SMF may include a New S11 SGW-C IP Address IE in the PGW Change Info IE” TS 23.007 v17.7.0
  • “the CP function (SGW-C, or I/V-SMF) may set the SSPOC bit to "1" in the Measurement Information included in the URR” TS 29.244 v17.10.0
Rel-18 specification text

The MME must now respond to the SGW-C's PGW Restart Notification with a PGW Restart Notification Acknowledge message, a step added as 2d.

  • “the SGW-C shall send a PGW Restart Notification to the MME as specified in clause 16.1A.2 and the MME shall respond with a PGW Restart Notification Acknowledge message” TS 23.007 v18.5.0

Defining Specifications

3GPP specifications that define or reference SGW-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.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