GTP encapsulated user Plane Data Unit

Description

The G-PDU is a specific packet format defined within the GPRS Tunnelling Protocol (GTP) suite, standardized in 3GPP TS 29.281 for the GTP-U protocol and referenced in TS 29.274 for the control plane. It represents the encapsulated payload of user plane data that is tunneled between GTP-U endpoints, such as between an eNodeB/gNB and a Serving Gateway (SGW), or between gateways (SGW and PGW) in the Evolved Packet Core (EPC). The encapsulation process involves taking the original user data packet (e.g., an IP packet from a UE) and adding a GTP-U header and, typically, a UDP/IP transport layer header. The GTP-U header includes critical fields like a Tunnel Endpoint Identifier (TEID), which uniquely identifies the GTP tunnel for a specific user's bearer, sequence numbers for loss detection, and message type indicators. This structure allows multiple user data flows to be multiplexed over the same transport network connection, separated logically by their TEIDs.

In the network architecture, G-PDUs are the workhorse of the user plane, carrying the actual subscriber data. When a UE establishes a PDN connection or a PDU Session, one or more EPS bearers or QoS Flows are set up, each associated with a specific GTP tunnel identified by a TEID pair. As data packets arrive from the UE at the base station, they are encapsulated into G-PDUs and forwarded to the appropriate gateway based on the TEID. The receiving GTP-U endpoint decapsulates the G-PDU by stripping off the GTP-U header and forwards the original payload to its next destination, either within the core network or to an external packet data network. This tunneling mechanism is transparent to the user data and provides a consistent method for data transport that is independent of the underlying radio access technology (e.g., LTE, NR, or even non-3GPP access).

The role of the G-PDU extends beyond simple tunneling. It supports path management procedures like Echo Requests/Responses to verify peer aliveness. The inclusion of sequence numbers in the header (optional for some interfaces) enables in-order delivery and loss detection mechanisms, which are particularly important for inter-node interfaces where packet reordering might occur. In 5G systems, while the core network protocol between the (R)AN and the UPF is still GTP-U (N3 interface) or potentially other protocols, the fundamental concept of a tunneled user plane data unit persists. The G-PDU format ensures backward compatibility and interworking between 4G and 5G network elements, forming a stable backbone for mobile broadband and other services.

Purpose & Motivation

The G-PDU was created to provide a standardized, efficient, and scalable method for transporting user plane data across the packet-switched core network in 3GPP systems. Prior to its formal definition within GTP, early GPRS systems required a mechanism to separate and route individual user data streams through network nodes that serve millions of subscribers. The G-PDU, as part of GTP, solves the problem of user data multiplexing and mobility management by introducing a tunneling paradigm. It allows the core network to establish logical pipes (tunnels) for user data that are separate from the control signaling, enabling independent scaling and management of the data plane.

Its creation was motivated by the shift towards all-IP networks in 3GPP, starting with GPRS and evolving through UMTS to EPS and 5GS. The G-PDU provides the necessary abstraction layer between the user's IP packets and the transport network (IP network) connecting core network nodes. This abstraction is crucial for supporting subscriber mobility; as a user moves, the GTP tunnels can be re-routed (e.g., during handover or path switch procedures) without affecting the user's IP session. The TEID in the G-PDU header acts as a local routing label, allowing nodes to forward packets without inspecting the inner IP payload, which improves processing efficiency and supports various traffic types, including IPv4, IPv6, and Ethernet frames.

Furthermore, the G-PDU standardizes the interface between different vendors' equipment, ensuring interoperability in multi-vendor networks. By defining a common packet format, it allows an SGW from vendor A to exchange user data seamlessly with a PGW from vendor B. This was a key enabler for the competitive ecosystem in mobile core networks. The continued evolution and use of the G-PDU format across releases, including in 5G, underscore its effectiveness in solving the fundamental problem of agile, tunnel-based user plane transport in mobile networks.

Key Features

• Encapsulates user IP packets or Ethernet frames within a GTP-U header
• Uses a Tunnel Endpoint Identifier (TEID) for logical tunnel multiplexing and routing
• Supports optional sequence numbers for in-order delivery and loss detection
• Transport-independent, typically carried over UDP/IP networks
• Enables mobility by allowing tunnel endpoints to be updated during handovers
• Provides a standardized format for multi-vendor interoperability across core network interfaces

Evolution Across Releases

Defining Specifications