Description
The S1-U interface is a critical user plane component within the Evolved Packet System (EPS), defined by 3GPP as the logical interface that connects the Evolved NodeB (eNodeB) in the E-UTRAN to the Serving Gateway (SGW) in the Evolved Packet Core (EPC). It operates over an IP-based transport network, employing the GPRS Tunneling Protocol for the user plane (GTP-U) to encapsulate and tunnel user data packets between these nodes. GTP-U uses UDP as its transport layer protocol, providing a lightweight and efficient mechanism for data forwarding that includes tunnel endpoint identifiers (TEIDs) to distinguish between different data flows and UEs. The interface is designed for high-throughput, low-latency data transfer, supporting the dynamic establishment, modification, and release of tunnels as UEs attach, move, or change bearers.
In operation, S1-U handles the actual user data traffic, such as web browsing, video streaming, or VoIP packets, once the corresponding control plane signaling (over S1-MME) has set up the necessary bearers. When a UE establishes a data session, the MME coordinates with the SGW and eNodeB to create an Evolved Radio Access Bearer (E-RAB), which includes a radio bearer over the air interface and a GTP-U tunnel over S1-U. Data packets from the UE are encapsulated by the eNodeB into GTP-U packets with a TEID corresponding to the SGW's tunnel endpoint, and vice versa for downlink traffic. The interface supports path management procedures, such as Echo Requests and Responses, to monitor tunnel liveliness, and it can handle error indications for troubleshooting. During handovers, S1-U plays a key role in data forwarding—for example, in X2-based handovers, the source eNodeB may forward in-flight packets to the target eNodeB via indirect tunneling through the SGW to prevent data loss.
Architecturally, S1-U embodies the principle of Control and User Plane Separation (CUPS), allowing independent scaling and optimization of data transport functions. Unlike the control plane's S1-MME, which uses reliable SCTP, S1-U leverages UDP for speed and simplicity, relying on higher-layer protocols (e.g., TCP in user data) for reliability when needed. The interface is typically point-to-point, with each eNodeB connected to one or more SGWs for load balancing and redundancy, though it does not support pooling in the same way as S1-MME. S1-U's design emphasizes efficiency: GTP-U tunneling minimizes overhead by reusing IP infrastructure, while features like header compression (e.g., ROHC) can be applied at the eNodeB to optimize radio resource usage. Overall, S1-U is fundamental to LTE's data delivery, enabling seamless mobility, QoS enforcement through bearer mapping, and integration with external packet data networks via the PGW.
Purpose & Motivation
The S1-U interface was introduced in 3GPP Release 8 as part of the LTE/EPC architecture to address limitations in earlier 3GPP systems, particularly UMTS, where user plane interfaces were more complex and less efficient. In UMTS, user data traveled through the Iu-PS interface between the RNC and SGSN, involving multiple protocol layers and the RNC as an intermediary, which added latency and reduced data throughput. S1-U was created to flatten the network by enabling direct user plane connectivity between the base station (eNodeB) and the gateway (SGW), eliminating the RNC layer. This design reduces the number of hops for data packets, lowers latency, and increases bandwidth efficiency, which is essential for supporting high-speed mobile broadband services and real-time applications like online gaming and video conferencing.
Historically, the motivation for S1-U stemmed from the explosive growth of mobile internet usage and the need for an all-IP network architecture that could scale to meet demand. By separating the user plane (S1-U) from the control plane (S1-MME), 3GPP allowed operators to deploy and scale data processing functions independently—for instance, distributing SGWs geographically to reduce latency while centralizing control functions. This separation also facilitated the adoption of GTP-U tunneling, a proven technology from earlier GPRS/UMTS networks, which provides a standardized method for encapsulating user data and supporting mobility without requiring changes to the underlying IP infrastructure. S1-U's use of UDP and GTP-U enables fast packet forwarding and efficient tunnel management, critical for handling the bursty nature of internet traffic.
Furthermore, S1-U solves problems related to seamless mobility and service continuity. Through GTP-U tunneling, it allows data packets to be rerouted dynamically during handovers, minimizing packet loss and ensuring smooth user experiences. This was a significant improvement over previous systems, where mobility events could cause noticeable interruptions. The interface also supports QoS differentiation by mapping different data flows to specific bearers with appropriate tunnel characteristics, enabling operators to offer tiered services. By standardizing S1-U across releases, 3GPP ensured interoperability with legacy systems (e.g., via inter-RAT handovers) and provided a foundation for future enhancements, such as those in LTE-Advanced and 5G interworking. Ultimately, S1-U's purpose is to deliver a high-performance, scalable user plane interface that underpins LTE's data capabilities, enabling efficient transport of user traffic while supporting advanced mobility and QoS features.
What changed in its specifications
The latest release-to-release comparison of specifications that define S1-U. 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 adds S-NSSAI text to the Create Session Request and Response procedures for edge computing phase 3. It also clarifies eMLPP priority values and GTP priority handling for MPS messaging and emergency traffic.
Full comparison in TS 29.274 →Technology family
RAN interfaces · Radio Access Network
Core network interfaces and reference points · Core Network
- S1-U counterpart in another generation: N3
“Both the N3IWF and the TNGF interface with the 5G Core Network CP and UP functions via the N2 and N3 interfaces, respectively.” TS 23.501
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 11 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 S1-U user plane interface between eNodeB and Serving GW is first specified in Rel-8, based on GTP-U, with per-bearer tunnelling, path switching and GTP-U signalling for F-TEIDs and data forwarding.
- “The S1 user plane interface (S1-U) is defined between the eNB and the S-GW.” TS 36.300 v8.12.0
- “S1-U: Reference point between E-UTRAN and Serving GW for the per bearer user plane tunnelling and inter eNodeB path switching during handover.” TS 23.401 v8.18.0
- “The S1-U is based on GTP-U protocol;” TS 23.401 v8.18.0
Rel-9 specs changed S1-U handling: the S1-U GTP-U tunnel setup now carries location, CSG and time zone info with ISR, and the S1-U link MTU configuration text now applies to the eNB only.
- “If ISR is active, this IE shall also be included on the S11 interface in the S1-U GTP-U tunnel setup procedure” TS 29.274 v9.14.0
- “the User Location Info/User CSG Information/UE Time Zone shall not be sent in S1-U GTP-U tunnel setup procedure during the TAU procedure” TS 29.274 v9.14.0
- “Configuration of S1-U (X2-U) link MTU in the eNB according to the MTU of the network domain the node belongs to” TS 36.300 v9.10.0
Rel-10 adds S1-U bearer handling: a Modify Access Bearers Request can modify S1-U bearers of all UE PDN connections, with a new cause 'Modifications not limited to S1-U bearers' and an S1-U eNodeB F-TEID IE.
- “the MME may modify the S1-U bearers of all the PDN connections of the UE by sending a Modify Access Bearers Request message” TS 29.274 v10.15.0
- “The SGW shall send the cause value "Modifications not limited to S1-U bearers" if” TS 29.274 v10.15.0
- “If the eNodeB receives a GTP error indication from the SGW over an S1-U tunnel not doing indirect forwarding” TS 23.007 v10.7.0
GTP-C specification added UL data forwarding F-TEID interface type 28 for S1-U/SGW and DL forwarding type 23 for S1-U, defining S1-U tunnel handling for data forwarding.
- “For UL data forwarding the SGW shall set the interface type in the F-TEID to 28” TS 29.274 v11.14.0
- “For DL data forwarding the SGW shall set the interface type in the F-TEID to 23” TS 29.274 v11.14.0
Rel-12 adds S1-U termination options for dual connectivity: S1-U may end in the MeNB or SeNB, with new GTP error handling and F-TEID rules for S1-U.
- “a second architecture where the S1-U can terminate in the SeNB” TS 36.300 v12.10.0
- “For SCG bearers, the SeNB is directly connected with the S-GW via S1-U.” TS 36.300 v12.10.0
- “If the SeNodeB receives a GTP error indication from the SGW over an S1-U tunnel, it shall delete the S1-U tunnel locally;” TS 23.007 v12.9.0
S1-U behaviour was extended in Rel-13: S1-U bearer establishment during Control Plane CIoT data transport, S1-U data transfer capability indication, and the SGW sending both IPv4 and IPv6 addresses in the S1-U F-TEID.
- “S1-U does not apply to the Control Plane CIoT EPS optimisation.” TS 23.401 v13.14.0
- “the MME may send a Modify Bearer Request to the SGW, to request the establishment of the S1-U bearers” TS 29.274 v13.13.0
- Add both IP addresses within S1-U SGW F-TEID in Create Bearer Request TS 29.274CR1718
Rel-14 allows S11-U to be separated from S1-U, so the SGW and MME handle separate S1-U and S11-U F-TEIDs and IP address spaces under Control Plane CIoT EPS Optimisation.
- “If separation of S11-U from S1-U is required, the Serving GW shall include the Serving GW IP address and TEID for S11-U and additionally the Serving GW IP address and TEID for S1-U” TS 23.401 v14.11.0
- “when separate IP address spaces are used for S11-U and S1-U, for Control Plane CIoT EPS Optimization, a different IP address and TEID may be used for the S11-U F-TEID” TS 29.274 v14.8.0
- Clarification on S1-U establishment during CP optimisation is in use TS 23.401CR3091
Rel-15 added an S1-U path failure notification feature, with the SGW reporting the cause code "S1-U Path Failure" to the MME, and separated S11-U from S1-U addressing.
- “"S1-U Path Failure" is used by the SGW in the Create Session Response, or in the Modify Bearer Response message” TS 29.274 v15.9.0
- “If the feature is supported and deployed in the network, after detecting a S1-U user plane path failure:” TS 23.007 v15.4.0
- S1-U Path Failure TS 29.274CR1925
Rel-16 specs extend S1-U handling: 36.300 adds 5GS interworking for S1-U bearer release/activation and UE-AMBR applicability for S1-U data transfer, and a CR corrects S1-U data capability handling in the MME.
- Correction on S1-U data capability indication and handling in the MME TS 24.301CR3190
- “In EPS, the MME requests the S-GW to release all S1-U bearers for the UE.” TS 36.300 v16.9.0
- “the UE-AMBR part in 11.4 is applicable only for UE which is enabled to use S1-U data transfer or User Plane CIoT EPS optimisation” TS 36.300 v16.9.0
For PDN connection restoration after a PGW-C/SMF change, the MME includes the S1-U eNodeB F-TEID in Create Session Request and the SGW should return the same S1-U SGW F-TEID.
- “if the MME includes the S1-U eNodeB F-TEID in the Create Session Request message and if the same SGW” TS 29.274 v17.12.0
- “if the S1-U eNodeB F-TEID for the EPS Bearer Context has been allocated by the eNB and if it is available at the MME” TS 29.274 v17.12.0
- “the MME shall update the eNB with the new SGW's S1-U F-TEID using the MME triggered Serving GW relocation procedure” TS 23.007 v17.7.0
TS 23.401 now states that S1-U user plane establishment and data transfer cannot be supported when a satellite operates in S&F Mode with the split MME deployment.
- “S1-U user plane establishment and S1-U user plane data transfer cannot be supported, when a satellite is operating in S&F Mode” TS 23.401 v19.6.0
- Clarify S1-U not supported by split MME TS 23.401CR3907
Defining Specifications
3GPP specifications that define or reference S1-U, 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 |
| TR 25.912 vj00 | Evolved UTRA and UTRAN Technical Report | Rel-19 read |
| TS 29.274 vk00 | GTPv2-C Control Plane Protocol | Rel-20 read |
| TS 36.300 vj20 | E-UTRAN Radio Interface Protocol Architecture | Rel-19 read |
| TS 36.302 vj00 | E-UTRA Physical Layer Services | Rel-19 read |
| TS 36.410 vj00 | S1 Interface: General Aspects and Principles | Rel-19 read |