GTP Signalling Message

Description

GTP signalling messages constitute the control-plane component of the GPRS Tunnelling Protocol (GTP), which is the fundamental tunnelling protocol used in 3GPP core networks for packet data transport. These messages are exchanged between pairs of GPRS Support Nodes (GSNs) — specifically between SGSNs and GGSNs in the packet core, or between other GSN pairs — over a communication path established between them. The signalling messages serve two primary purposes: they transfer GSN capability information between peer nodes, and they manage the lifecycle of GTP tunnels by creating, updating, and deleting them as subscriber sessions are established, modified, or torn down.

Architecturally, GTP signalling operates over the control plane, distinct from the user plane that carries actual subscriber payload data. In GTPv1, the control plane is known as GTP-C (GTP Control), while the user plane is GTP-U (GTP User). GTP-C messages are carried over UDP, typically on port 2123, and include message types such as Create PDP Context Request/Response, Update PDP Context Request/Response, and Delete PDP Context Request/Response. These messages carry Information Elements (IEs) that convey parameters such as Tunnel Endpoint Identifiers (TEIDs), Quality of Service (QoS) profiles, Access Point Names (APNs), and cause codes. The signalling path between two GSNs is identified by the pair of IP addresses and UDP ports used by the peers.

The protocol operates in a request-response paradigm. When an SGSN needs to establish a PDP context for a mobile subscriber, it sends a Create PDP Context Request to the GGSN, which allocates resources and responds with a Create PDP Context Response containing the TEID and IP address for the user-plane tunnel. Subsequent modifications, such as QoS changes or handovers between SGSNs, trigger Update PDP Context messages. When the session ends, Delete PDP Context messages release the tunnel resources. Path management messages — Echo Request and Echo Response — are periodically exchanged to detect path failures and to exchange node restart counters and capability information.

In the Evolved Packet Core (EPC) introduced from Rel-8, GTP-C evolved to GTPv2-C, which is used on the S11, S5/S8, S10, and other interfaces. GTPv2-C introduced new message types such as Create Session Request/Response, Modify Bearer Request/Response, and Delete Session Request/Response, reflecting the bearer-centric architecture of EPS. Despite the architectural shift, the fundamental role of signalling messages remained the same: capability exchange and tunnel lifecycle management. The signalling messages are defined across multiple specifications, including 29.060 (GTPv1-C and GTPv1-U), 29.274 (GTPv2-C), 29.281 (GTP-U), and 29.119 (GTP prime, used for charging data transfer).

Signalling messages are critical to network operation because they coordinate state between distributed core network nodes. Without reliable signalling, tunnels cannot be established, subscriber sessions cannot be maintained across mobility events, and charging records cannot be accurately generated. The protocol includes reliability mechanisms such as retransmission timers, sequence numbers, and path failure detection to ensure robust operation. Security considerations include the use of IPsec for signalling protection on certain interfaces, particularly in roaming scenarios where signalling traverses untrusted networks.

Purpose & Motivation

GTP signalling messages exist to solve the fundamental problem of coordinating tunnel state between distributed packet core nodes in GPRS, UMTS, and LTE networks. When a mobile subscriber initiates a data session, multiple network elements must agree on tunnel endpoints, QoS parameters, and routing information. Without a dedicated signalling protocol, each node would have no reliable way to inform its peers about tunnel creation, modification, or deletion, leading to orphaned resources, failed data delivery, and inconsistent state across the core network.

The protocol was motivated by the need for a standardized, vendor-interoperable mechanism for GSN-to-GSN communication. In early GPRS deployments, the ability to roam between SGSNs and to access external packet data networks through GGSNs required a well-defined control protocol. GTP signalling provided this by defining a common message set and information element structure that all vendors could implement, ensuring multi-vendor interoperability. It also enabled capability negotiation, allowing nodes from different vendors or different release versions to discover each other's supported features.

Over time, the signalling messages evolved to support increasingly complex scenarios: secondary PDP contexts for differentiated QoS, network-initiated bearer modifications, and inter-RAT handovers. In the EPC era, GTPv2-C signalling became the backbone of session management, interfacing with MME, SGW, PGW, and PCRF to enforce policy and charging. The persistent need for signalling messages reflects the inherently distributed nature of mobile core networks, where no single node holds all state, and coordination is achieved through explicit message exchange.