Description
GTP-U is the user plane protocol within the GTP family, responsible for encapsulating and forwarding user data traffic between network elements in 3GPP mobile networks. It operates over UDP port 2152 and is used from 3G to 5G systems to tunnel IP packets between entities like the Radio Network Controller (RNC) and Serving GPRS Support Node (SGSN) in UMTS, or the eNodeB and Serving Gateway (SGW) in LTE, and the (R)AN and User Plane Function (UPF) in 5G. GTP-U adds a header to each user data packet, which includes a Tunnel Endpoint Identifier (TEID), sequence number, and optional extension headers. The TEID is a unique identifier assigned during control plane signaling (via GTP-C) that determines the tunnel endpoint, allowing the receiving node to decapsulate the packet and forward it to the correct destination, such as another network node or the external packet data network.
Architecturally, GTP-U creates point-to-point tunnels that logically connect user plane entities, forming a virtual pipeline for subscriber data. These tunnels are established and managed by the control plane (GTP-C or other protocols like PFCP in 5G) but are used exclusively for data transfer. The protocol supports both IPv4 and IPv6 payloads and can transport any IP-based traffic, including web browsing, video streaming, and IoT data. Key mechanisms include sequence numbering for detecting packet loss or out-of-order delivery, though retransmission is typically handled by higher-layer protocols like TCP. GTP-U also supports path management messages, such as Echo Request/Response, to verify tunnel liveness between nodes.
In operation, when a user equipment (UE) sends an IP packet, it is encapsulated by the first GTP-U node (e.g., eNodeB) with a GTP header containing the TEID corresponding to the UE's bearer. This encapsulated packet is then routed over the IP backbone to the next GTP-U node (e.g., SGW), which uses the TEID to identify the associated bearer, strips the GTP header, and forwards the original IP packet toward its destination, possibly through further tunneling. During handovers, GTP-U tunnels are dynamically re-routed to new endpoints to maintain session continuity without dropping packets. In 5G, GTP-U remains the primary user plane protocol between the (R)AN and UPF, with enhancements to support new features like network slicing, where tunnels may be associated with specific slice identifiers, and integration with the Packet Forwarding Control Protocol (PFCP) for session management.
Purpose & Motivation
GTP-U was created to provide an efficient and standardized method for tunneling user data across the mobile packet core, solving the challenge of transporting IP packets between distributed network nodes while supporting subscriber mobility. Before GTP-U, early GPRS systems used a combined GTP protocol that lacked optimization for high-speed data forwarding. The separation of GTP-U allowed for a lightweight, dedicated user plane protocol that minimizes overhead and latency, critical for real-time services and high-throughput applications. It addressed the need for a scalable tunneling mechanism that could handle millions of simultaneous data sessions across evolving radio access technologies.
The motivation for GTP-U stemmed from the transition to all-IP networks in 3GPP Release 4 and beyond, where efficient data transport became paramount. By encapsulating user IP packets within GTP-U headers, the core network can route traffic based on TEIDs rather than subscriber IP addresses, simplifying mobility management and enabling features like seamless handovers. This tunneling approach also provides a layer of abstraction, allowing the internal network topology to remain hidden from external packet data networks, enhancing security and flexibility. GTP-U's design over UDP/IP ensures low processing overhead and compatibility with existing IP infrastructure, making it suitable for high-volume data planes.
Historically, GTP-U has evolved to meet increasing demands for data rates and low latency, particularly with the advent of LTE and 5G. It solves limitations of earlier tunneling methods by supporting features like header compression extensions, enhanced sequence numbering for integrity, and integration with quality of service (QoS) mechanisms. In 5G, GTP-U continues to be essential for user plane tunneling, even as the control plane shifts to new protocols, due to its proven reliability and efficiency. Its purpose extends to enabling advanced network architectures, such as edge computing, where user plane functions can be deployed closer to the radio access, and GTP-U tunnels facilitate low-latency data paths.
Protocol Stack
Classification
Release Timeline
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (16 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 15, the GTP-U protocol was enhanced for 5GS with the introduction of new extension headers, specifically for the PDU Session Container. It also defined procedures for handling these extension headers and for receiving GTP-U Error Indications from the 5G Access Network. Furthermore, the release addressed endpoint management by covering the description of GTP-U tunnel endpoints and the scenario of receiving packets from multiple remote endpoints.
- GTP-U Error Indication received from 5G-AN TS 23.527CR0003
- GTP-U Extension Header Handling TS 29.281CR0083
- New GTP-U extension header for 5GS TS 29.281CR0086
- New GTP-U Extension Header for the PDU Session Container TS 29.281CR0089
- Unpredictability of GTP TEID for PGW GTP-U TS 29.281CR0088
- GTP-U Tunnel Endpoint Description TS 29.281CR0097
+ 1 more changes
In Release 16, the GTP-U function was updated with clarifications on the handling of a GTP-U Error Indication when it is received by the 5G Access Network (5G-AN). Furthermore, the release implemented the specific conclusions and recommendations from the Technical Report TR 29.892 directly into the GTP-U specification.
In Release 17, the GTP-U protocol was enhanced with new capabilities for detecting and reporting the restart of a GTP-U entity to improve reliability. It was also extended to support tunneling for the N3mb and N19mb interfaces, enabling new architectural deployments. Furthermore, the protocol's extensibility was addressed by reserving some Information Element (IE) types for future use.
In Release 18, GTP-U was enhanced with two specific features. A new restoration procedure was defined for the NG-RAN when it receives a GTP-U Error Indication message. Furthermore, the protocol was extended with a new GTP-U Extension Header specifically designed to carry PDU Set Information.
In Release 19, enhancements were made to the GTP-U protocol by fixing specific Information Elements (IEs). The work focused on correcting the definition and handling of the GTP-U Tunnel Status Information and Recovery Time Stamp IEs to improve protocol robustness and data integrity.
- Fixing the GTP-U Tunnel Status Information and Recovery Time Stamp IEs TS 29.281CR0134
Explore further
Broader topics and technologies where GTP-U plays a role.
Defining Specifications
3GPP specifications that define or reference GTP-U, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj00 | 3GPP Technical Terms and Definitions | Rel-19 |
| TS 23.527 vj50 | 5G System Restoration Procedures | Rel-19 |
| TS 25.410 vj00 | Iu Interface Introduction for UTRAN | Rel-19 |
| TS 27.060 vj00 | TE-MT Interworking for Packet Domain | Rel-19 |
| TS 29.060 vj00 | GPRS Tunnelling Protocol (GTP) version 1 | Rel-19 |
| TS 29.061 vj00 | Packet Domain Interworking for PLMN | Rel-19 |
| TS 29.281 vj20 | GTPv1-U Protocol Specification | Rel-19 |
| TS 29.532 vj30 | MB-SMF Service Based Interface Protocol | Rel-19 |
| TS 36.410 vj00 | S1 Interface: General Aspects and Principles | Rel-19 |
| TS 37.470 vj00 | W1 Interface Introduction for ng-eNB | Rel-19 |
| TS 38.401 vj10 | NG-RAN Architecture Specification | Rel-19 |
| TS 38.470 vj10 | F1 Interface Introduction | Rel-19 |