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

Glossary term · Interface

S5

Reference point between the Serving GW and the PDN GW

Interface →

S5 is the 4G EPC reference point between the Serving Gateway and PDN Gateway that provides GTP-based user plane tunnels and control plane signaling for bearer management and mobility.

Introduced
Rel-8
Where
Core Network › Evolved Packet Core
Specifications
1 specs
S5 Description Purpose What changed Family Neighbours Specifications

Description

The S5 interface is a standardized point-to-point interface within the 4G LTE Evolved Packet Core (EPC). It interconnects two key network entities: the Serving Gateway (S-GW), which acts as the local mobility anchor for the user plane during inter-eNodeB handovers, and the Packet Data Network Gateway (P-GW), which serves as the anchor point for connectivity to external Packet Data Networks (e.g., the internet). The interface has two distinct components: the S5 control plane (S5-C) and the S5 user plane (S5-U).

The control plane (S5-C) utilizes the GPRS Tunneling Protocol for the control plane (GTP-C). Over this protocol, the S-GW and P-GW exchange signaling messages to create, modify, and delete GTP tunnels (bearers) for user data. Key procedures include the creation of a default and dedicated bearers during initial UE attachment, bearer modification for QoS updates, and bearer deletion during session termination or handovers that require S-GW relocation. The S-GW initiates these procedures towards the P-GW based on instructions received from the MME over the S11 interface.

The user plane (S5-U) employs the GPRS Tunneling Protocol for the user plane (GTP-U). This component is responsible for the actual encapsulation and transport of user IP packets between the S-GW and P-GW. Each EPS bearer is mapped to a unique GTP-U tunnel identified by a Tunnel Endpoint Identifier (TEID). The P-GW performs functions like policy enforcement, charging, and packet filtering before routing traffic to/from the external network, while the S-GW manages the mobility tunnel towards the eNodeB (S1-U). In architectures where the S-GW and P-GW are combined (a Collapsed Gateway deployment), the S5 interface becomes an internal interface within the same physical node.

Purpose & Motivation

The S5 interface was defined in 3GPP Release 8 as part of the new, flat-IP architecture of the Evolved Packet Core (EPC) for LTE. Its primary purpose is to decouple the mobility anchoring function (S-GW) from the external connectivity and policy enforcement function (P-GW). In prior 3G UMTS architectures, the SGSN and GGSN were more tightly coupled, limiting deployment flexibility.

This separation solved several problems. It enabled flexible network deployments, allowing operators to locate S-GWs closer to the radio network for optimized user plane latency while centralizing P-GWs for efficient policy control and external peering. It also facilitated efficient inter-S-GW mobility; when a UE moves to an area served by a different S-GW, only the S5 tunnel from the new S-GW to the anchored P-GW needs to be established, preserving the UE's IP address and session continuity.

Furthermore, the S5 interface, through its use of GTP, provided a proven and reliable tunneling mechanism for both control and user plane, ensuring backward compatibility and smooth interworking with 2G/3G GPRS networks. It established a clear functional split that became a model for later architectures, influencing the design of interfaces in 5G, albeit with different protocols.

What changed in its specifications

The latest release-to-release comparison of specifications that define S5. Each summary describes the whole specification, not only this term.

TS 23.401Rel-18 → Rel-19

Rel-19 adds Disaster Roaming in EPS, which covers disaster-roaming procedures and attach, tracking area update and mobility signalling. It also adds Time Reference Information Distribution Indication to subscription data and the MME-to-eNB path, along with Store and Forward Satellite operation text.

Full comparison in TS 23.401 →

Technology family

Core network interfaces and reference points · Core Network

  1. R97 Gi, Gn, Gp
  2. Rel-7 Gx
  3. Rel-8 S1-MME, S1-U, S11, S5, S8, SGi
  4. Rel-15 N11, N2, N3, N4, N6, N7, N9
  • S5 counterpart in another generation: Gn
    “The EPC specific S1/3/4/5/8/10/11/12/ series are specified in TS 29.274 [90] for GTP based protocols and for PMIP based S5/8 interfaces are speci” TS 23.002
  • S5 counterpart in another generation: N9
    “The UPF shown in Figure 4.2.10-1 can be connected via an N9 reference point, instead of the N3 reference point.” TS 23.501
  • S5 coexists with S8
    “The same applies to the S5 and S8 interfaces if they are based on GTP.” TS 23.401

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.

Evolution Across Releases

An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.

Rel-8 Initial

Introduced as a foundational interface of the LTE Evolved Packet Core, defining the GTP-based signaling and tunneling between the newly separated Serving Gateway and Packet Data Network Gateway entities.

Defining Specifications

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

SpecificationTitleRelease
TS 23.401 vk10 Evolved Packet System Architecture Rel-20 read