GTP-U

GPRS Tunnelling Protocol for User Plane

Protocol
Introduced in Rel-4
The user plane component of the GTP protocol suite, used to tunnel actual user data packets between network nodes such as RAN and core gateways. It encapsulates IP packets within GTP headers for transport over the mobile backbone, enabling efficient data forwarding and mobility support.

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.

Key Features

  • User plane tunneling for encapsulating and forwarding IP packets over mobile networks
  • Uses UDP port 2152 for transport, providing low-latency data forwarding
  • Relies on Tunnel Endpoint Identifiers (TEIDs) for dynamic tunnel routing
  • Supports sequence numbers for packet loss detection and in-order delivery
  • Compatible with IPv4 and IPv6 payloads and network protocols
  • Includes path management messages (e.g., Echo Request) for tunnel monitoring

Evolution Across Releases

Rel-4 Initial

Introduced GTP-U as a separate user plane protocol, splitting from the earlier combined GTP. Defined for tunneling user data between UTRAN (RNC) and core network (SGSN/GGSN) in UMTS, supporting enhanced data rates and real-time services with reduced overhead.

Enhanced GTP-U for LTE/EPC, defining tunneling between eNodeB and SGW, and SGW and PGW. Added support for EPS bearers, improved sequence number handling, and integration with new mobility procedures for seamless handovers within LTE and between 3GPP technologies.

Adapted GTP-U for 5G user plane between (R)AN and UPF, maintaining backward compatibility with LTE. Supported new 5G features like network slicing integration, enhanced QoS flows, and low-latency optimizations, while continuing as the primary data tunneling protocol in 5GC.

Defining Specifications

SpecificationTitle
TS 21.905 3GPP TS 21.905
TS 23.527 3GPP TS 23.527
TS 25.410 3GPP TS 25.410
TS 27.060 3GPP TS 27.060
TS 29.060 3GPP TS 29.060
TS 29.061 3GPP TS 29.061
TS 29.281 3GPP TS 29.281
TS 29.532 3GPP TS 29.532
TS 36.410 3GPP TR 36.410
TS 37.470 3GPP TR 37.470
TS 38.401 3GPP TR 38.401
TS 38.470 3GPP TR 38.470