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.
Key Features
- Local mobility anchor point for user plane during intra-LTE (eNodeB) handovers
- Anchor for mobility between different 3GPP radio access technologies (e.g., LTE to GERAN/UTRAN)
- Terminates the downlink data path for idle UEs and initiates paging
- Routes and forwards user IP packets between the eNodeB (S1-U) and the P-GW (S5/S8)
- Manages and enforces QoS on Evolved Packet System (EPS) bearers
- Performs lawful interception and generates charging data records (CDRs)
Evolution Across Releases
Initial definition of the S-GW as a core component of the Evolved Packet Core (EPC) for LTE. Established its core functions: mobility anchor for intra-LTE handovers, inter-RAT anchor via S4 interface to SGSN, downlink data termination/paging for idle mode, and user plane routing via GTP-U tunnels over S1-U and S5/S8 interfaces.
Defining Specifications
| Specification | Title |
|---|---|
| TS 21.905 | 3GPP TS 21.905 |
| TS 23.221 | 3GPP TS 23.221 |
| TS 24.302 | 3GPP TS 24.302 |
| TS 25.401 | 3GPP TS 25.401 |
| TS 25.410 | 3GPP TS 25.410 |
| TS 25.413 | 3GPP TS 25.413 |
| TS 29.061 | 3GPP TS 29.061 |
| TS 29.215 | 3GPP TS 29.215 |
| TS 29.804 | 3GPP TS 29.804 |
| TS 32.251 | 3GPP TR 32.251 |
| TS 32.298 | 3GPP TR 32.298 |
| TS 32.820 | 3GPP TR 32.820 |
| TS 32.833 | 3GPP TR 32.833 |
| TS 33.107 | 3GPP TR 33.107 |
| TS 33.108 | 3GPP TR 33.108 |
| TS 33.320 | 3GPP TR 33.320 |
| TS 33.863 | 3GPP TR 33.863 |
| TS 36.300 | 3GPP TR 36.300 |
| TS 36.401 | 3GPP TR 36.401 |
| TS 36.410 | 3GPP TR 36.410 |
| TS 36.413 | 3GPP TR 36.413 |
| TS 36.423 | 3GPP TR 36.423 |
| TS 36.875 | 3GPP TR 36.875 |
| TS 43.129 | 3GPP TR 43.129 |