Tunnel Endpoint Identifier, user plane

Description

The Tunnel Endpoint Identifier for the user plane (TEID-U) is a fundamental component within the GPRS Tunneling Protocol (GTP) architecture, specifically defined for the user plane (GTP-U). It is a 32-bit field that uniquely identifies a GTP tunnel endpoint on a network node for a specific user's data traffic. When a user equipment (UE) establishes a data session, the network creates GTP tunnels to carry the user's IP packets. For example, in the LTE EPC, a GTP-U tunnel exists between the Serving Gateway (SGW) and the Packet Data Network Gateway (PGW), and another between the SGW and the eNodeB. Each endpoint of these tunnels is assigned a TEID-U by the receiving node. This TEID-U is then communicated to the sending node via control plane signaling (GTP-C), so that when the sender encapsulates user IP packets into a GTP-U header, it populates the TEID field with the receiver's assigned TEID-U. This allows the receiving node to correctly de-multiplex incoming packets and forward them to the appropriate bearer context for the target UE.

The TEID-U operates in conjunction with the user's IP address and the UDP port number for GTP-U (typically 2152). This combination creates a unique socket for tunneled traffic. The TEID-U's primary role is to distinguish between multiple simultaneous GTP tunnels that may share the same transport network layer (IP address and UDP port) between two nodes. For instance, a single SGW may handle thousands of UEs, each with potentially multiple bearers (e.g., default and dedicated bearers). Each bearer requires its own GTP-U tunnel, and thus its own pair of TEID-Us (one for uplink, one for downlink). The local TEID-U value is chosen by the receiving entity and must be unique within the context of that receiving node for the given IP address and UDP port.

Architecturally, the TEID-U is managed by the control plane. During procedures like bearer establishment or modification, the GTP-C messages (e.g., Create Session Request/Response) carry TEID-U information elements. The node initiating the tunnel (e.g., SGW for the S5-U interface towards the PGW) includes its own TEID-U for the uplink direction in the request. The peer node (e.g., PGW) stores this TEID-U for sending downlink packets and generates its own TEID-U for the uplink direction, which it sends back in the response. This bidirectional exchange establishes the tunnel identifiers for both directions. The TEID-U is critical for mobility events like handovers. During an X2-based handover in LTE, the source eNB sends the TEID-U(s) of the data radio bearers to the target eNB in the HANDOVER REQUEST message, allowing the target eNB to begin receiving downlink data from the SGW immediately after the handover, minimizing data loss.

Purpose & Motivation

The TEID-U was created to solve the fundamental problem of multiplexing and routing user data packets within a tunnel-based packet core network, specifically within the 3GPP GPRS and later Evolved Packet System (EPS). Prior to standardized tunneling protocols, alternative packet routing mechanisms might have relied solely on IP routing tables or complex layer 2 circuits, which are inefficient for managing millions of simultaneous, mobile user sessions with specific quality-of-service (QoS) requirements. The GTP protocol, and the TEID-U within it, provides a lightweight, session-oriented overlay that abstracts the user's IP flow from the underlying transport IP network.

Its creation was motivated by the need for scalable and efficient user plane management. By using a simple 32-bit identifier locally scoped to a tunnel endpoint, the network can avoid inspecting the inner IP headers of user packets for forwarding decisions at every hop, improving performance. It enables seamless mobility and session continuity; as a user moves, the network can simply update the TEID-U mapping at the anchoring gateway (e.g., PGW) to point to a new SGW or access node, without disrupting the user's IP session. This design is central to the 'tunnel-based' mobility concept in 3GPP networks, separating the user's stable IP anchor point from the changing radio access points.