GTP-U

GPRS Tunnelling Protocol for User Plane

Protocol →
Introduced in Rel-4 Also in: Radio Access Network

GTP-U is the user plane component of the GTP protocol suite that tunnels user data packets between network nodes by encapsulating IP packets for transport over the mobile backbone.

Category
Protocol
Introduced
Rel-4
Where
Core Network › 5G Core
Also touches
1 segments
Specifications
12 specs
GTP-U Description Purpose Related Classification Detected Changes Specifications

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.

Classification

Part ofGTP-C
Related approachesUPFTEID

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (23 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Studied in Rel-4, normative work from Rel-15.

Rel-15 10 changes

In Release 15, GTP-U was enhanced to support the new 5G System architecture by introducing a new GTP-U Extension Header for the PDU Session Container and for 5GS operation over the N9 interface. The release also addressed GTP-U tunnel endpoint management, including the handling of multiple remote endpoints and the unpredictability of Tunnel Endpoint Identifiers (TEIDs). Furthermore, procedures were specified for GTP-U Error Indication handling from the 5G Access Network.

  • GTP-U Error Indication received from 5G-AN TS 23.527CR0003
  • Alternative GGSN addresses for control Plane and user traffic TS 29.060CR1061
  • GGSN control plane and user plane addresses TS 29.060CR1062
  • 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

+ 4 more changes

Rel-16 3 changes

In Release 16, the GTP-U function was updated with clarifications on handling the GTP-U Error Indication when received by the 5G Access Network (5G-AN). Furthermore, the release implemented conclusions from a technical report (TR 29.892) and introduced specifications for the N19 user plane interface to support 5G Virtual Network (VN) group communication.

  • Clarifications on GTP-U Error Indication received by 5G-AN TS 23.527CR0013
  • Implementing the conclusions of TR 29.892 for GTP-U TS 29.281CR0109
  • N19 user plane interface for 5G VN group communication TS 29.281CR0107
Rel-17 7 changes

In Release 17, key enhancements for GTP-U included the introduction of a new procedure for the detection and reporting of a GTP-U entity restart and enhanced handling mechanisms for user plane path failures. Furthermore, the release defined GTP-U tunneling support for new interfaces, specifically N3mb and N19mb, and reserved certain Information Element (IE) types for future protocol extensions. These updates provided improved reliability and new architectural capabilities for the user plane tunneling protocol.

  • Detection and reporting of the restart of a GTP-U entity TS 23.527CR0039
  • Enhanced handling at user plane path failure TS 23.527CR0040
  • GTP-U tunneling for N3mb and N19mb TS 29.281CR0115
  • Detecting of the restart of a GTP-U entity TS 29.281CR0116
  • Correction on protocol stack for IAB TS 38.401CR0242
  • Reserve some IE types for GTP-U TS 29.060CR1068

+ 1 more changes

Rel-18 2 changes

In Release 18, GTP-U was enhanced with a new restoration procedure for the NG-RAN when it receives a GTP-U Error Indication. Furthermore, the protocol was extended to include a new GTP-U Extension Header specifically designed to carry PDU Set Information.

  • Restoration procedure for NG-RAN receiving a GTP-U Error Indication TS 23.527CR0067
  • New GTP-U Extension Header for the PDU Set Information Container TS 29.281CR0128
Rel-19 1 change

In Release 19, the GTP-U protocol was updated to address specific information elements. The release introduced fixes for the GTP-U Tunnel Status Information and Recovery Time Stamp Information Elements (IEs). These corrections ensure the protocol data units containing these IEs are correctly formatted and processed within the user plane transport layer.

  • 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.

SpecificationTitleRelease
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