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.
What changed in its specifications
The latest release-to-release comparison of specifications that define GTP-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 added procedures for UDR restoration during subscriber data migration, AMF resynchronization indication, and multicast MBS session restoration for N3mb path failure.
Full comparison in TS 23.527 →Protocol Stack
Technology family
Core signalling protocols · Core Network
- Phase 1 MAP
- Phase 2 ISUP
- R96 CAP
- R99 GTP-C, GTP-U, GTPv1-C
- Rel-4 BICC
- Rel-5 Diameter, SIP
- Rel-8 GTPv2-C
- Rel-14 PFCP
- Rel-15 HTTP/2 SBI
Also in this family (introduction release not pinned to a single defining specification): INAP, M2PA, SIGTRAN
- GTP-U used together with GTP-C
“GTP-PDU: GTP Protocol Data Unit is either a GTP-C message or a GTP-U message” TS 29.060
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 13 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.
Introduced in R99 (release dating of the term; no individual change cited).
TS 29.281 first appears in Rel-8, specifying GTP-U: UDP port 2152, tunnels identified by TEID, GTP-U protocol entity, and sequence number handling.
- “The UDP Destination Port number for GTP-U request messages is 2152. It is the registered port number for GTP-U.” TS 29.281 v8.5.0
- “GTP-U Tunnels are used to carry encapsulated T-PDUs and signalling messages between a given pair of GTP-U Tunnel Endpoints.” TS 29.281 v8.5.0
- “There is a GTP-U protocol entity per IP address.” TS 29.281 v8.5.0
GTP-U multicast tunnels now use a Common TEID (C-TEID) signalled via GTPv1-C, RANAP, GTPv2-C and S1-AP, and message applicability for MBMS in GTP-U was added.
- “The Common Tunnel Endpoint ID (C-TEID) which is present in the GTP header shall indicate which tunnel a particular T-PDU belongs to.” TS 29.281 v9.3.0
- Message applicability of MBMS in GTP-U TS 29.281CR0028
GTP-U was extended to the ePDG and the S2b interface, with the TEID being signalled instead of negotiated, and End Marker messages now required to use the same UDP ports and IP addresses as the tunnel.
- Addition of GTP-U interface over S2b TS 29.281CR0031
- “The GTP-U protocol entity provides packet transmission and reception services to user plane entities in the RNC, SGSN, GGSN, eNodeB, SGW, ePDG and PGW.” TS 29.281 v10.3.0
- “The UDP Destination Port and UDP Source Port shall be the same as those of the corresponding GTP-U tunnel for which the End Marker message is sent.” TS 29.281 v10.3.0
GTP-U gained TWAN as a peer, added a C-TEID definition, a new extension header for SIRIG, clarified S2a support, and allowed UDP source port to be allocated statically or dynamically.
- “New extension header in GTP-U for SIRIG” TS 29.281 v11.6.0
- “Clarification on support of GTP-U over the S2a interface” TS 29.281 v11.6.0
- “the UDP Source Port (except as specified for the Echo Response message) may be allocated either statically or dynamically by the sending GTP-U entity” TS 29.281 v11.6.0
End Marker handling for GTP-U tunnels was extended: it is sent after the last G-PDU or on receiving an End Marker Indication, with special handling during E-UTRAN initiated E-RAB modification.
- “The End Marker message(s) shall be sent for each GTP-U tunnel, except for the case of an E-UTRAN Initiated E-RAB modification procedure.” TS 29.281 v12.1.0
- “the SGW shall send End marker message(s) to the eNodeB on the old S1-U tunnel for the tunnel(s) that are switched” TS 29.281 v12.1.0
GTP-U now also applies to the S11-U interface, and the MME is added as a node hosting a GTP-U protocol entity.
- “Iu, Gn, Gp, S1-U, S11-U, S2a, S2b, S4, S5, S8, S12, X2, M1 and Sn.” TS 29.281 v13.3.0
- “eNodeB, SGW, ePDG, PGW, TWAN and MME.” TS 29.281 v13.3.0
TS 29.281 GTP-U gains support for transport level packet marking over GTP-U interfaces, and TS 29.244 first specifies GTP-U encapsulation for Sx user plane forwarding between CP and UP functions.
- “Support for transport level packet marking over GTP-U interfaces” TS 29.281 v14.1.0
- “User plane packets shall be forwarded between the CP and UP functions by encapsulating the user plane packets using GTP-U encapsulation” TS 29.244 v14.8.0
GTP-U was extended to 5GS: new peers (gNB, N3IWF, UPF), N3/N9/Xn/Sn interfaces, relaxed TEID uniqueness allowing multiple remote endpoints per tunnel endpoint, and GTP-U handling over N4.
- “The GTP-U protocol supports the possibility for one GTP-U tunnel endpoint to receive packets from multiple remote GTP-U endpoints.” TS 29.281 v15.7.0
- “GTP-U defines a set of messages between the two ends of the user plane of the interfaces Iu, Gn, Gp, S1-U, S11-U, S2a, S2b, S4, S5, S8, S12, X2, M1, Sn, Xn, N3 and N9.” TS 29.281 v15.7.0
- New GTP-U extension header for 5GS TS 29.281CR0086
GTP-U gained new behaviour in Rel-16: dynamic UDP source port or IPv6 flow label for load balancing, IPv6 UDP zero-checksum rules, N19 interface support, redundant transmission on N3/N9, and GTP-U path QoS monitoring.
- “the UDP Source Port or the Flow Label field (see IETF RFC 6437 [37]) should be set dynamically by the sending GTP-U entity” TS 29.281 v16.2.0
- “the UDP checksum shall not be set to zero by the sending GTP-U entity unless it is ensured that the peer GTP-U entity” TS 29.281 v16.2.0
- “the PSA UPF replicates the packet and assigns the same GTP-U sequence number to them for the redundant transmission” TS 23.501 v16.20.0
In Rel-17 GTP-U gained a Tunnel Status message with a Start Pause of Charging indication, multicast tunnels for MBS (N3mb/N19mb), dummy GTP-U packets for QoS monitoring, and peer GTP-U restart detection and reporting.
- “The Tunnel Status message is optional. A GTP-U entity, if it supports the message, may send one or more Tunnel Status message to the peer GTP-U entity” TS 29.281 v17.5.0
- “When using IP multicast transport, GTP-U Multicast Tunnels shall be used for unidirectional transfer of the encapsulated T-PDUs” TS 29.281 v17.5.0
- Detecting of the restart of a GTP-U entity TS 29.281CR0116
Rel-18 adds a new GTP-U extension header for the PDU Set Information Container and new GTP-U handling for ECN/L4S reporting, GTP-U path monitoring and Error Indication restoration.
- “New GTP-U Extension Header for the PDU Set Information Container” TS 29.281 v18.4.0
- “UPF uses information sent by NG-RAN in GTP-U header extension to perform ECN marking for L4S for the corresponding direction.” TS 23.501 v18.12.0
- NG-RAN indicates to SMF when a GTP-U Error Indication is received TS 38.413CR1114
GTP-U gained new roles in Rel-19: GTP-U path QoS monitoring (GTPUPM flag) and UPF marking Data Burst Size and PDU Set information in the downlink GTP-U header towards NG-RAN.
- “the SMF shall indicate that QoS monitoring is performed based on GTP-U path monitoring by setting the GTPUPM flag to 1” TS 29.244 v19.6.0
- “The UPF sends the identified Data Burst size to NG-RAN in the downlink GTP-U header of the first PDUs of the data burst.” TS 23.501 v19.9.0
- Identification and marking of Data Burst Size in DL GTP-U packets TS 29.244CR0892
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 vj20 | 3GPP Terminology and Definitions | Rel-19 read |
| TS 23.527 vk00 | 5G Restoration Procedures for N4 Interface | Rel-20 read |
| TS 25.410 vj00 | Iu Interface Introduction for UTRAN | Rel-19 read |
| TS 27.060 vj00 | TE-MT Interworking for Packet Domain | Rel-19 read |
| TS 29.060 vj00 | GPRS Tunnelling Protocol (GTP) version 1 | Rel-19 read |
| TS 29.061 vk10 | Packet Domain Interworking Requirements | Rel-20 read |
| TS 29.281 vj20 | GTPv1-U Protocol Specification | Rel-19 read |
| TS 29.532 vk00 | Nmbsmf Service Based Interface Specification | Rel-20 read |
| TS 36.410 vj00 | S1 Interface: General Aspects and Principles | Rel-19 read |
| TS 37.470 vj00 | W1 Interface Introduction for ng-eNB | Rel-19 read |
| TS 38.401 vj30 | NG-RAN Architecture Description | Rel-19 read |
| TS 38.470 vj20 | F1 Interface Specification for NG-RAN | Rel-19 read |