Tunnel Endpoint Identifier, control plane

Description

The TEID-C (Tunnel Endpoint Identifier, control plane) is a specialized 32-bit identifier used within the GPRS Tunneling Protocol for the Control plane (GTP-C). It operates on the same fundamental principle as the general TEID but is strictly reserved for signaling tunnels between control plane entities in the Evolved Packet Core (EPC) and 5G Core network. Architecturally, GTP-C tunnels are established between nodes like the MME and SGW (S11 interface), SGW and PGW (S5/S8 interface for control), and between SGSNs for inter-system mobility (S3/S4/S16). The TEID-C uniquely identifies the local endpoint of such a signaling tunnel at the receiving node.

Its operation is central to session and bearer management procedures. When a control plane entity (e.g., an MME) needs to initiate signaling with another (e.g., an SGW), it uses the peer's TEID-C as the destination in the GTP-C message header. This TEID-C value was previously exchanged during initial node setup or during a previous procedure. For instance, during an LTE Attach procedure, the MME sends a Create Session Request to the SGW. This message contains the MME's TEID-C for control plane on the S11 interface, which the SGW stores. The SGW's response includes its own TEID-C, allowing bidirectional communication. All subsequent messages for that specific PDN connection (e.g., Modify Bearer Request, Delete Session Request) will use these mutually agreed TEID-C values to instantly associate the signaling with the correct UE context.

The role of TEID-C is distinct from the user plane TEID (often called TEID-U). While TEID-U identifies tunnels for user data packets, TEID-C identifies tunnels for signaling that creates, modifies, and deletes those user plane tunnels. This separation of control and user plane identifiers provides clear demarcation, simplifies protocol processing, and enhances security and reliability. In 5G Core, while the control plane primarily uses HTTP/2-based service-based interfaces, GTP-C and TEID-C are still used on certain interfaces like N4 (between SMF and UPF) for PFCP session management, demonstrating its enduring utility for direct control of the user plane.

Purpose & Motivation

TEID-C was created to address the need for a dedicated, reliable, and context-aware signaling channel between control plane nodes in the packet core. As mobile networks evolved to support complex IP session management with multiple bearers and stringent QoS requirements, the signaling load increased significantly. A generic signaling transport was insufficient; signaling messages needed to be directly and unambiguously associated with a specific UE's session context for efficient processing.

The introduction of TEID-C within GTP-C solved this by providing an in-band addressing mechanism for control messages. This was motivated by the limitations of using out-of-band correlation methods or inspecting the contents of every signaling message. TEID-C allows a control plane node to immediately identify the relevant session database entry upon receiving a GTP-C packet, enabling fast processing of handovers, bearer modifications, and charging events. It ensures the scalability of the control plane by allowing a single network interface to manage signaling for millions of sessions through simple TEID-based de-multiplexing, a design crucial for the performance of high-throughput, low-latency 4G and 5G networks.

Key Features

• 32-bit identifier used exclusively in GTP-Control (GTP-C) protocol
• Uniquely identifies the endpoint of a control plane signaling tunnel
• Exchanged during session establishment procedures (e.g., Create Session)
• Enables direct association of signaling messages with a specific UE session context
• Separates control plane addressing from user plane (TEID-U) addressing
• Essential for session management, bearer modification, and mobility signaling

Evolution Across Releases

Defining Specifications