S-GW

Serving Gateway

Core Network →
Introduced in Rel-8 Also in: Radio Access Network, Security

S-GW is the core network node in 4G and early 5G NSA that routes user data, manages bearers, acts as the mobility anchor during handovers, and performs lawful interception.

Category
Core Network
Introduced
Rel-8
Where
Core Network › Evolved Packet Core
Also touches
2 segments
Specifications
24 specs
S-GW Description Purpose Detected Changes Specifications

Description

The Serving Gateway (S-GW) is a fundamental data plane entity within the Evolved Packet Core (EPC), the core network for 4G LTE systems, and it is also used in 5G Non-Standalone (NSA) deployments. It is a per-user equipment (UE) granularity node, meaning a UE is connected to a single S-GW at any given time for its active PDN connections. Architecturally, the S-GW sits between the Radio Access Network (RAN), specifically the eNodeB in LTE, and the Packet Data Network Gateway (P-GW). Its primary function is to be the mobility anchor for the user plane. During handovers between eNodeBs, the S-GW remains the termination point, and the data path is switched from the source to the target eNodeB, ensuring seamless session continuity without involving the P-GW. For idle UEs, the S-GW terminates the downlink data path and triggers paging when downlink data arrives. It buffers the packets and initiates the network-triggered service request procedure to re-establish the bearers. The S-GW also acts as the anchor for mobility between 3GPP access technologies (e.g., handover from LTE to 2G/3G GPRS), interfacing with the 2G/3G SGSN via the S4 interface. It routes and forwards all user IP packets, performing basic functions like marking uplink and downlink packets with QoS Class Identifier (QCI) and Allocation and Retention Priority (ARP). The S-GW also generates charging data records (CDRs) for per-UE bearer-based charging, which are sent to the Charging Gateway Function (CGF). It interfaces with the Policy and Charging Rules Function (PCRF) via the Gxc reference point for QoS policy enforcement on the GPRS Tunneling Protocol (GTP) bearers. Lawful interception of user traffic is also performed at the S-GW. It connects to the MME via the S11 interface for control signaling and to the P-GW via the S5/S8 interface for the user plane.

Purpose & Motivation

The S-GW was created as part of the revolutionary flat-IP architecture of the Evolved Packet System (EPS) in 3GPP Release 8, which defined LTE. It solved critical problems inherent in the previous 3G UMTS architecture. In UMTS, the Serving GPRS Support Node (SGSN) handled both control and user plane, creating a potential bottleneck. The EPS split these functions: the MME for control and the S-GW for user plane, enabling independent scaling and optimized data routing. A key problem was efficient mobility management. The S-GW's role as the local mobility anchor for intra-LTE handovers minimized signaling load on the core (P-GW) and reduced handover latency, which was essential for supporting real-time services. It also provided a stable anchor point for inter-RAT mobility, simplifying handovers between LTE and legacy 2G/3G networks during the transition period. Furthermore, by centralizing the user plane termination for a UE, it enabled efficient downlink data buffering and paging for idle devices, which is crucial for battery life optimization. The S-GW's design was motivated by the need for a high-performance, scalable, and cost-effective core network to handle the massive growth in mobile data traffic anticipated with 4G, while maintaining robust mobility and service continuity.

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (8 CRs across 3 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Studied in Rel-8, normative work from Rel-15.

Rel-15 3 changes

In Release 15, the S-GW's role was clarified within the context of the serving network function, with corrections made to its stage 2 procedures. Specifically, the release introduced the use of the serving network name as the Access Network Identity for 5G interoperability. Additionally, it included stage 2 corrections for the serving system event reported by the HSS for EPS.

  • Using Serving network name as Access Network Identity for 5G TS 24.302CR0672
  • Correction of serving network function TS 32.298CR0703
  • Stage 2 Corrections to the Serving System event reported by HSS for EPS TS 33.107CR0283
Rel-16 4 changes

In Release 16, the S-GW-related updates included clarifying procedures for a Serving Node change and explicitly adding the ePDG (evolved Packet Data Gateway) as a type of serving node. Furthermore, enhancements were made to support Serving PLMN Rate Control within traffic volume reporting mechanisms. These changes provided greater specificity in node management and traffic policy enforcement within the serving network.

  • Add ePDG as serving node TS 32.298CR0828
  • Serving PLMN Rate Control in List of Traffic Data Volumes TS 32.298CR0729
  • Correction of Serving Node change TS 32.298CR0771
  • Clarification on TAC presence in Serving Cell Info over X2 TS 36.423CR1539
Rel-17 1 change

In Release 17, the specific update for the Serving Gateway (S-GW) involved enhancements to support Non-Terrestrial Networks (NTN) for IoT. This included the addition of serving PLMN (Public Land Mobile Network) information within the User Location Information (ULI) for IoT devices. This change allows the serving network to more accurately apportion charges and manage roaming for users in these specialized network environments.

  • Adding serving PLMN information in ULI for IoT NTN TS 36.413CR1893

Explore further

Broader topics and technologies where S-GW plays a role.

Defining Specifications

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

SpecificationTitleRelease
TR 21.905 vj00 3GPP Technical Terms and Definitions Rel-19
TS 23.221 vj00 3GPP System Architectural Requirements Rel-19
TS 24.302 vj00 Access to EPC via non-3GPP networks; Stage 3 Rel-19
TS 25.401 vj00 UTRAN Overall Architecture Rel-19
TS 25.410 vj00 Iu Interface Introduction for UTRAN Rel-19
TS 25.413 vj00 Radio Access Network Application Part (RANAP) Rel-19
TS 29.061 vj00 Packet Domain Interworking for PLMN Rel-19
TS 29.215 vj00 S9 Reference Point Stage 3 Specification Rel-19
TS 29.804 v801 CT3 Aspects of System Architecture Evolution Rel-8
TS 32.251 vj00 PS Domain Charging Management Rel-19
TS 32.298 vj30 Charging Data Record (CDR) Parameter Specification Rel-19
TS 32.820 v1801 Charging Architecture Study for Evolved 3GPP Rel-8
TS 32.833 vb00 Converged OSS End-to-End Management Study Rel-11
TS 33.107 vj00 Lawful Interception Architecture & Functions Rel-19
TS 33.108 vj00 LI Handover Interface Specification Rel-19
TS 33.320 vj00 H(e)NB Subsystem Security Architecture Rel-19
TS 33.863 ve20 Security for Battery-Efficient IoT Device to Enterprise Rel-14
TS 36.300 vj00 E-UTRAN Radio Interface Protocol Architecture Overview Rel-19
TS 36.401 vj00 E-UTRAN Overall Architecture Description Rel-19
TS 36.410 vj00 S1 Interface: General Aspects and Principles Rel-19
TS 36.413 vj10 S1 Application Protocol (S1AP) Rel-19
TS 36.423 vj10 X2 Application Protocol (X2AP) Specification Rel-19
TS 36.875 vd10 Dual Connectivity Extension Requirements Rel-13
TS 43.129 vj00 PS Handover in GERAN A/Gb and GAN Modes Rel-19