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.
What changed in its specifications
The latest release-to-release comparison of specifications that define S-GW. Each summary describes the whole specification, not only this term.
Rel-18 brings only minor changes to TS 21.905: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TR 21.905 →Rel-19 brings only minor changes to TS 23.221: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TS 23.221 →Architecture
Where it sits in the network
- 4G EPC → S-GW (Packet Gateways)
Evolution Lineage
- Evolved from: SGSN (3G→4G)
- Succeeded by: SMF (4G→5G), UPF (4G→5G)
- Network evolution overview →
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
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 9 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.
The S-GW is specified for the first time across lawful interception, charging and E-UTRAN architecture, including its functions, CDR generation (SGW-CDR) and interception at the S-GW.
- “The Serving Gateway (S-GW) hosts the following functions (see 3GPP TS 23.401 [17]):” TS 36.300 v8.12.0
- “For the delivery of the CC and IRI the S-GW and/or, per national option PDN-GW provides correlation number and target identity” TS 33.107 v8.12.0
- “SGW-CDR S-GW (IP-CAN bearer) generated – CDR” TS 32.251 v8.16.0
Charging specs for the S-GW gained IPv4v6 dual-stack control plane address fields (S-GW Address IPv6) and user CSG information change as a charging trigger, with clarified change-condition handling.
- “This field is the S-GW IPv6 Address used for the Control Plane, when both IPv4 and IPv6 addresses of the S-GW are available.” TS 32.298 v9.23.0
- “Change of charging condition in the S-GW: e.g. QoS change, tariff time change, user location change, user CSG information change.” TS 32.251 v9.13.0
- “Clarify “Change Condition” setting for containers level and “Cause for record Closing” for CDR level for P-GW and S-GW.” TS 32.298 v9.23.0
Rel-10 adds S-GW roles: S-GW/P-GW-like functions embedded in the DeNB for relay nodes, S-GW CDR handling on MME/S4-SGSN changes, and Charging Characteristics in S-GW (new Annex A.5).
- “the DeNB also embeds and provides the S-GW/P-GW-like functions needed for the RN operation.” TS 36.300 v10.12.0
- “MME to S4-SGSN. In S-GW a new S4-SGSN address is added to CDR upon encountering this trigger.” TS 32.251 v10.15.0
- “A.5 Charging Characteristics in S-GW” TS 32.251 v10.15.0
MME and ePDG are added as nodes that can produce CDRs or report charging events alongside the S-GW and P-GW, and TWAG is added as a serving node address source.
- “based on the PCN nodes (MME, S-GW, ePDG and P-GW) reporting charging information for chargeable events” TS 32.251 v11.13.0
- “the MME, S-GW, ePDG and P-GW shall be able to produce CDRs or report charging events” TS 32.251 v11.13.0
In Rel-12 the S-GW gains new behaviour: S-GW relocation without UE mobility via E-RAB MODIFY REQUEST, SIPTO@LN with a collocated S-GW/L-GW, and extended charging and lawful-interception roles.
- “support for MME-triggered S-GW relocation without UE mobility through the E-RAB MODIFY REQUEST message.” TS 36.300 v12.10.0
- “SIPTO@LN is supported using a stand-alone gateway (with co-located S-GW and L-GW) deployed in the local network.” TS 36.300 v12.10.0
- “Change of charging condition in the S-GW: e.g. QoS change, tariff time change, user location change, user CSG information change, change of UE presence in a Presence Reporting Area.” TS 32.251 v12.13.0
S-GW requirements were extended in Rel-13: lawful interception now covers ProSe Remote UE start-of-communication events at the S-GW, and charging adds Non-IP PDN connections and MO exception data counter receipt.
- “If the ProSe Remote UE is a target, a ProSe Remote UE start of communication event shall be generated by the S-GW, PDN-GW.” TS 33.107 v13.8.0
- “19) The P-GW/S-GW shall support charging for Non-IP PDN connection.” TS 32.251 v13.6.1
- “MO exception data counter receipt in the S-GW: This event closes the CDR.” TS 32.251 v13.6.1
LI specification extended to the S-GW with CUPS: Serving Gateway-C and Serving Gateway-U split, with Serving Gateway-C delivering IRI over X2 and activating CC interception in the Serving Gateway-U.
- “the Serving Gateway-C shall deliver the IRI over the X2 reference point to DF2” TS 33.107 v14.7.0
- “the Serving Gateway-C shall send/activate the following information to the Serving Gateway-U” TS 33.107 v14.7.0
- S8HR LI with CUPS for S-GW TS 33.107CR0245
S-GW/BBIFF now notifies the LMISF of IMS signalling and media bearer creation, modification or deletion for S8HR APNs, including UE location received from the MME, independently of active intercepts.
- “the S-GW/BBIFF notifies the LMISF whenever an IMS Signalling Bearer or Media Bearer for S8HR APNs is created, modified or deleted” TS 33.107 v15.6.0
- “shall be reported by the S-GW and P-GW for offline charging in Charging Data Request[Start] / [Interim] when the subscription is activated” TS 32.251 v15.5.0
- “Volume reporting for Secondary RAT is an optional capability in the S-GW and P-GW” TS 32.251 v15.5.0
In Rel-17, TS 33.107 adds LI requirements for the S-GW under CUPS (split Serving Gateway-C/U, IRI delivery over X2) and S8HR BBIFF, and TS 32.251 adds PSCELL Id collection for SGW-CDR.
- “the Serving Gateway-C shall deliver the IRI over the X2 reference point to DF2” TS 33.107 v17.0.0
- “When available by the S-GW, the PSCELL Id associated to the Secondary RAT is collected for SGW-CDR.” TS 32.251 v17.0.0
- “the LI functions available in the Serving Gateway and PDN Gateway shall be carried over to the split Serving Gateway and PDN Gateway” TS 33.107 v17.0.0
Defining Specifications
3GPP specifications that define or reference S-GW, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj20 | 3GPP Terminology and Definitions | Rel-19 read |
| TS 23.221 vj00 | 3GPP System Architectural Requirements | Rel-19 read |
| TS 24.302 vj00 | Access to EPC via non-3GPP networks; Stage 3 | Rel-19 read |
| TS 25.401 vj00 | UTRAN Overall Architecture | Rel-19 read |
| TS 25.410 vj00 | Iu Interface Introduction for UTRAN | Rel-19 read |
| TS 25.413 vj00 | Radio Access Network Application Part (RANAP) | Rel-19 read |
| TS 29.061 vk10 | Packet Domain Interworking Requirements | Rel-20 read |
| TS 29.215 vj00 | S9 Reference Point Stage 3 Specification | Rel-19 read |
| TS 29.804 v801 | CT3 Aspects of System Architecture Evolution | Rel-8 read |
| TS 32.251 vj00 | PS Domain Charging Management | Rel-19 read |
| TS 32.298 vk10 | Charging Data Record Specification | Rel-20 read |
| TS 32.820 v801 | Study on Evolved 3GPP Charging Architecture | Rel-8 read |
| TS 32.833 vb00 | Fixed-Mobile Convergence Management Study | Rel-11 read |
| TS 33.107 vj00 | Lawful Interception Architecture & Functions | Rel-19 read |
| TS 33.108 vj00 | LI Handover Interface Specification | Rel-19 read |
| TS 33.320 vj00 | H(e)NB Subsystem Security Architecture | Rel-19 read |
| TS 33.863 ve20 | Security for Battery-Efficient IoT Device to Enterprise | Rel-14 read |
| TS 36.300 vj20 | E-UTRAN Radio Interface Protocol Architecture | Rel-19 read |
| TS 36.401 vj00 | E-UTRAN Overall Architecture Description | Rel-19 read |
| TS 36.410 vj00 | S1 Interface: General Aspects and Principles | Rel-19 read |
| TS 36.413 vj20 | S1 Application Protocol (S1AP) for E-UTRAN | Rel-19 read |
| TS 36.423 vj10 | X2 Application Protocol (X2AP) Specification | Rel-19 read |
| TS 36.875 vd10 | Dual Connectivity Extension Requirements | Rel-13 read |
| TS 43.129 vj00 | PS Handover in GERAN A/Gb and GAN Modes | Rel-19 read |