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

Glossary term · Interface

S8

Inter-PLMN reference point between the Serving GW and the PDN GW

Interface →

S8 is the inter-PLMN user-plane reference point between a Serving GW in the visited network and a PDN GW in the home network, enabling home-routed roaming in LTE/EPC.

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

Description

S8 is a reference point defined in the LTE/EPC architecture for inter-PLMN roaming. It connects a Serving Gateway in one PLMN to a PDN Gateway in another PLMN, typically the visited Serving Gateway to the home PDN Gateway. In home-routed roaming, the UE establishes a PDN connection through the visited radio access network and MME, while the IP anchor remains in the home network. S8 carries the user-plane path between those two core nodes and may also carry GTP control-plane messages used to create, modify, and delete bearers. The interface therefore sits between the radio-access-facing Serving GW and the IP-facing PDN GW, enabling the visited network to forward traffic to the home network without anchoring the session locally.

Technically, S8 is implemented with GTP-U for user-plane encapsulation. Each EPS bearer or PDN connection is associated with tunnel endpoint identifiers, bearer identifiers, and QoS parameters that allow the Serving GW and PDN GW to separate and forward packets correctly. The Serving GW terminates the radio-side user-plane path from the eNodeB over S1-U and forwards packets to the PDN GW over S8. At the PDN GW, packets are de-encapsulated, routed to the external packet data network, and mapped to IP or Ethernet PDN connectivity as configured. The PDN GW also applies policy, charging, lawful interception, and QoS enforcement before traffic enters or leaves the operator network.

S8 is closely related to S5. S5 is used when the Serving GW and PDN GW are in the same PLMN, while S8 is used when they are in different PLMNs. This distinction is important in roaming because the visited operator may host the Serving GW, but the subscriber profile, IP address allocation, policy control, and charging anchor may remain in the home operator network. S8 also complements S11, which is the control-plane reference point between the MME and the Serving GW. Together, S11, S8, and S5 allow the MME, Serving GW, and PDN GW to coordinate bearer establishment, modification, and release across radio and core domains.

From a bearer perspective, S8 supports default and dedicated EPS bearers. The default bearer is established during attach or PDN connection creation and provides always-on IP connectivity. Dedicated bearers may be created by the PDN GW, often under PCRF control, to satisfy application QoS requirements such as voice, video, or guaranteed bit rate services. When a dedicated bearer is created, the PDN GW signals the Serving GW over S8 to install the corresponding tunnel and QoS context, and the Serving GW forwards the bearer establishment information to the MME over S11. The MME then coordinates with the eNodeB to map the EPS bearer to a radio bearer. This end-to-end bearer chain makes S8 a key part of QoS delivery in roaming scenarios.

S8 is also relevant to mobility and data forwarding. During inter-MME or inter-Serving GW changes, the Serving GW endpoint may move, but the PDN GW anchor may remain. The S8 tunnel can be re-established or updated so that the home PDN GW continues to anchor the session. Although inter-eNodeB user-plane forwarding is typically handled by S1 or X2, the S8 interface ensures that the core-side anchor path remains stable while the radio and Serving GW endpoints change. This stability is important for roaming subscribers who move between visited networks or between different Serving GWs while maintaining the same IP session.

The role of S8 in the network is to make inter-operator packet transport predictable and standardized. It allows roaming subscribers to reach the same home IP services, corporate networks, and policy anchors as when they are in their home network. Because the interface crosses administrative boundaries, it depends on transport security, operator agreements, and correct QoS mapping. IPsec, transport isolation, and network-level authentication are commonly used to protect S8 traffic. The interface does not expose UE NAS signaling; that is carried through the MME and PDN GW over other reference points. Instead, S8 focuses on bearer-level packet forwarding and the control messages needed to maintain those bearers between the two gateways.

Purpose & Motivation

S8 exists to solve the problem of roaming subscribers needing access to home-network anchored services without forcing the visited operator to replicate the subscriber's IP anchor, policy, and charging environment. Before standardized inter-PLMN gateway interfaces, operators would need custom tunneling, routing, and bearer control mechanisms to carry roaming traffic. These approaches were difficult to scale, hard to troubleshoot, and inconsistent across vendors and operators. S8 provides a common reference point so that any compliant Serving GW can interoperate with any compliant PDN GW across PLMNs.

The motivation is also architectural. LTE/EPC separates the Serving GW, which handles mobility anchoring and radio-side user-plane aggregation, from the PDN GW, which handles IP anchoring, policy, charging, and external network access. In non-roaming cases, these functions may be in the same PLMN and connected by S5. In roaming, however, the Serving GW is often in the visited network while the PDN GW is in the home network. S8 makes this split possible. It preserves the home network's role as the service anchor while allowing the visited network to provide radio access and local mobility handling.

S8 also addresses QoS and roaming business requirements. Operators want roaming subscribers to receive the same default and dedicated bearer treatment as home subscribers, including voice over LTE, video, and guaranteed bit-rate services. By carrying bearer-level tunnel and QoS information between the Serving GW and PDN GW, S8 enables the home PDN GW to enforce policy and charging while the visited network transports the packets. This reduces the need for complex interworking and supports predictable roaming agreements, lawful interception, and IP address management.

What changed in its specifications

The latest release-to-release comparison of specifications that define S8. 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
  • S8 counterpart in another generation: Gp
    “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
  • S8 coexists with S5
    “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 in Rel-8 EPC as the inter-PLMN reference point between Serving GW and PDN GW, primarily for home-routed roaming. It established GTP-based user-plane tunneling and bearer control between visited and home core nodes. The definition carried over unchanged in the available release information.

Defining Specifications

3GPP specifications that define or reference S8, 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