Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Protocol

GTP-C

GPRS Tunnelling Protocol for Control Plane

Protocol →

GTP-C is the control plane component of the GTP protocol suite, responsible for signaling procedures like tunnel establishment and management between core network nodes to enable dynamic user plane path management.

Introduced
R99
Where
Core Network › Evolved Packet Core
Specifications
3 specs
GTP-C Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

GTP-C is the control plane variant of the GPRS Tunnelling Protocol, specifically designed to handle signaling messages between core network elements for session management, mobility management, and tunnel management. It operates over UDP port 2123 and is used in networks from 3G to 5G, though its role has evolved with architectural changes. In 3G UMTS networks, GTP-C communicates between the Serving GPRS Support Node (SGSN) and Gateway GPRS Support Node (GGSN) to manage Packet Data Protocol (PDP) contexts. In LTE/EPC, it is used between the Mobility Management Entity (MME), Serving Gateway (SGW), and Packet Data Network Gateway (PGW) to manage EPS bearers and handle mobility events like handovers and tracking area updates. The protocol employs a request-response model, where initiating nodes send messages like Create Session Request, and responding nodes reply with corresponding response messages, conveying parameters such as Tunnel Endpoint Identifiers (TEIDs), QoS profiles, and charging identifiers.

Architecturally, GTP-C messages are encapsulated within GTP headers that include a version field, message type, sequence number, and TEID for control plane tunnels. Key procedures include session management (activation, modification, deactivation), bearer management (establishment and teardown of data radio bearers), and mobility management (updating tunnel endpoints during inter-node handovers). For example, during an initial attach procedure in LTE, the MME uses GTP-C to send a Create Session Request to the SGW, which forwards it to the PGW, resulting in the establishment of a default EPS bearer and the assignment of user plane TEIDs for GTP-U tunnels. GTP-C also supports error handling and recovery mechanisms, with cause codes indicating success or failure of operations.

In 5G networks, the control plane architecture shifted towards a Service-Based Interface (SBI) using HTTP/2, reducing the reliance on GTP-C for core network signaling. However, GTP-C may still be used in certain interworking scenarios or legacy interfaces. The protocol includes multiple versions, with GTPv2-C being prominent in LTE and beyond, offering enhanced features like support for multiple PDN connections, improved mobility between 3GPP and non-3GPP access, and better error reporting. GTP-C is critical for maintaining session continuity and efficient resource utilization, as it dynamically manages the user plane paths based on subscriber mobility and service requirements.

Purpose & Motivation

GTP-C was developed to provide a standardized control signaling mechanism for managing GTP tunnels in packet-switched mobile networks, addressing the need for dynamic session and mobility management. Prior to its formalization, early GPRS implementations used combined GTP for both control and user plane, which lacked scalability and clear separation of concerns. The creation of GTP-C as a distinct protocol allowed for optimized signaling procedures, enabling efficient establishment, modification, and teardown of user plane tunnels as subscribers move or change services. It solved the problem of coordinating multiple network elements (e.g., SGSN, GGSN, MME, SGW) to maintain consistent session state and ensure seamless handovers.

The motivation for GTP-C stemmed from the evolution towards all-IP core networks in 3GPP Release 8 with the System Architecture Evolution (SAE) and LTE. As networks became flatter and more distributed, a robust control plane protocol was needed to manage the increased complexity of bearer management and mobility across multiple gateways. GTP-C provided a reliable, connectionless signaling mechanism over UDP, balancing efficiency with the ability to handle numerous simultaneous sessions. It also introduced enhancements over earlier versions, such as support for dual-addressing (IPv4 and IPv6), improved charging correlation, and better interworking with non-3GPP accesses like Wi-Fi.

Historically, GTP-C addressed limitations of proprietary or less flexible signaling methods by offering a uniform interface that could evolve with network generations. While 5G has moved to HTTP/2-based control plane interfaces for most core functions, GTP-C's legacy remains important in 4G networks and during migration phases. Its purpose extends to enabling advanced features like quality of service (QoS) differentiation, where control messages carry QoS parameters to configure user plane tunnels appropriately, ensuring that services like video streaming or VoIP receive the necessary network resources.

What changed in its specifications

The latest release-to-release comparison of specifications that define GTP-C. Each summary describes the whole specification, not only this term.

TS 29.060Rel-18 → Rel-19

Rel-19 brings only minor changes to TS 29.060: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TS 29.060 →
TS 29.281Rel-18 → Rel-19

Rel-19 added PDU session user plane protocol support over N9, N3mb and N19mb, and changed PDU Session Container determination to also consider ARP priority level.

Full comparison in TS 29.281 →

Protocol Stack

Technology family

Core signalling protocols · Core Network

  1. Phase 1 MAP
  2. Phase 2 ISUP
  3. R96 CAP
  4. R99 GTP-C, GTP-U, GTPv1-C
  5. Rel-4 BICC
  6. Rel-5 Diameter, SIP
  7. Rel-8 GTPv2-C
  8. Rel-14 PFCP
  9. Rel-15 HTTP/2 SBI

Also in this family (introduction release not pinned to a single defining specification): INAP, M2PA, SIGTRAN

  • GTP-C used together with GTP-U
    “GTP-PDU: GTP Protocol Data Unit is either a GTP-C message or a GTP-U message” TS 29.060

Members and relations were proposed independently by several models and kept only where at least two agree; quotes are verified verbatim against the specifications. Release = first approved version of the defining specification.

Release Timeline

Detected Changes Across Releases

verified against 3GPP sources

Documented changes in 13 releases, each verified against the text of 3GPP specifications or approved change requests and shown with the exact wording. The release timeline above shows the same releases. A release without an entry has no documented change for this term.

R99 introduced

TS 29.060 first specifies GTP-C as the control plane protocol used to establish, manage and release tunnels between GSNs, with its own UDP port 2123 and message exchange.

  • “GTP-C shall be the means by which tunnels are established, used, managed and released.” TS 29.060 v3.19.0
  • “The UDP Destination Port number for GTP-C request messages is 2123.” TS 29.060 v3.19.0
  • “GTP specifies a tunnel control and management protocol (GTP-C) which allows the SGSN to provide packet data network access for an MS.” TS 29.060 v3.19.0
Rel-5 1 CR

GTP-C handling changed: responses to messages about unknown PDP contexts must carry an all-zero TEID, and the Sequence Number rules now also cover the RAN Information Relay message.

  • “The Tunnel Endoint Identifier used in the response message shall be set to all zeroes.” TS 29.060 v5.14.0
  • TEID for GTP-C messages related to unknown PDP Contexts TS 29.060CR395r3
  • “For GTP-C messages not having a defined response message for a request message, i.e. for messages Version Not Supported, RAN Information Relay” TS 29.060 v5.14.0
Rel-6 1 CR

GTP-C was extended for MBMS: GTP-C tunnels are now defined per MBMS service, a Create MBMS Context Request creates a GTP-C tunnel, and more information elements may repeat.

  • “A GTP tunnel in the GTP-C plane is defined for all PDP Contexts with the same PDP address and APN” TS 29.060 v6.21.1
  • “a valid request creates a GTP tunnel in the GTP-C plane, however no GTP-U tunnel is created at this step.” TS 29.060 v6.21.1
  • GTP-C tunnel for MBMS broadcast TS 29.060CR524
Rel-8 specification text

TS 29.274 GTPv2-C is specified for the first time in Rel-8, defining the GTP-C header, message exchange roles, piggybacking, UDP port 2123 and version 2 for EPC.

  • “GTP-C Message: GTP control plane message type of a GTP-PDU. GTP-C message consists of GTP-C header, which is followed by zero or more information elements.” TS 29.274 v8.12.0
  • “The UDP Destination Port number for GTPv2 Initial messages shall be 2123. It is the registered port number for GTP-C.” TS 29.274 v8.12.0
  • “Bits 8 to 6, which represent the GTP-C version, shall be set to decimal 2 ("010").” TS 29.274 v8.12.0
Rel-9 1 CR

GTP-C was extended in Rel-9: GTPv1-C now also supports roaming and inter-access mobility between Gn/Gp SGSNs and MMEs, with MME-side requirements and new GTP-C interfaces (Sm, Sn).

  • “GTP-C is also used for roaming and inter access mobility between Gn/Gp SGSNs and MMEs as specified in Annex D of 3GPP TS 23.401 [47].” TS 29.060 v9.14.0
  • “The requirements specified in this clause for SGSN also apply to MME if the MME supports GTP-C (v1)” TS 29.060 v9.14.0
  • Scope of GTP-C protocol TS 29.274CR0253
Rel-10 1 CR

GTP-C gained a mechanism for notifying and discovering supported features between peer GTP-C entities, plus S2b GTP-C interface types and TEID=0 handling rules for the new interface.

  • “A GTP-C entity should verify that a backward incompatible feature is supported by its peer GTP entities before starting to use it.” TS 29.274 v10.15.0
  • “A GTP-C entity may discover the features supported by a peer GTP-C entity with which it is in direct contact” TS 29.274 v10.15.0
  • GTP-C Information Elements for GTP based S2b interface TS 29.274CR0767
Rel-11 1 CR

GTP-C behaviour changed in Rel-11: TEID exchange now includes Iu-PS messages, new S2a TWAN/PGW GTP-C interface types were added, and old S3 GTP-C TEIDs are released during inter-RAT handover with ISR active.

  • “The Tunnel Endpoint Identifier is set by the sending entity in the GTP header of all control plane messages” TS 29.274 v11.14.0
  • “35: S2a TWAN GTP-C interface” TS 29.274 v11.14.0
  • Release of old S3 GTP-C TEIDs during I-RAT HO with ISR active TS 29.274CR1199
Rel-12 specification text

Rel-12 added GTP-C load and overload control mechanisms, with Load Control Information piggybacked in GTP-C messages and a new GTP-C Entity Congestion cause, specified in TS 29.274 and TS 23.401.

  • “GTP-C Load Control feature is an optional feature which allows a GTP control plane node to send its Load Control Information to a peer” TS 23.401 v12.11.0
  • “"GTP-C Entity Congestion" is used to indicate that the GTP-C entity has detected node level congestion” TS 29.274 v12.15.0
  • “the Load Control Information shall be piggybacked in GTP-C request or response messages such that the exchange of Load Control Information does not trigger extra signalling;” TS 29.274 v12.15.0
Rel-13 1 CR

GTP-C procedures in TS 29.274 changed: overload control gained sequence-number handling and was extended to TWAN/ePDG, with Maximum Wait Time retransmission behaviour and piggybacking extended to non-3GPP handover.

  • “the receiving entity shall update its overload control information, only if the Overload-Sequence-Number received in the new overload control information is larger” TS 29.274 v13.13.0
  • “a Handover from Trusted or Untrusted Non-3GPP IP Access to E-UTRAN” TS 29.274 v13.13.0
  • GTP-C overload control from TWAN/ePDG to PGW TS 29.274CR1546
Rel-14 specification text

GTP-C gained a Message Priority field in the header, with rules for setting and using priority in overload handling, plus GTP-C extensions for SGW-U/PGW-U selection with CUPS.

  • “Bits 8 to 5 of octet 12 shall indicate the relative priority of the GTP-C message, if the "MP" flag is set to 1 in Octet 1.” TS 29.274 v14.8.0
  • “Message prioritization may be performed by an overloaded node, when handling incoming messages during an overloaded condition, based on the relative GTP-C message priority” TS 29.274 v14.8.0
  • “A GTP-C entity should set the same message priority in a Triggered message or Triggered Reply message as received” TS 29.274 v14.8.0
Rel-15 1 CR

GTP-C was extended in Rel-15 to the N26 interface (AMF GTP-C interface, GTP-C tunnel per UE) and gained unpredictable TEID assignment for PGW interfaces and CUPS-related selection extensions.

  • “The TEID value shall be assigned in a non-predictable manner for PGW S5/S8/S2a/S2b interfaces” TS 29.274 v15.9.0
  • “40: N26 AMF GTP-C interface” TS 29.274 v15.9.0
  • GTP-C tunnel per UE over the N26 interface TS 29.274CR1853
Rel-16 1 CR

GTP-C in TS 29.274 changed: PDN connection collision handling on Create Session Request now covers RLOS-attached UEs without UICC, and a CR addressed IP addressing for IPv4/IPv6 capable GTP-C entities.

  • “TAC and SNR part of ME Identity for emergency or RLOS attached UE without UICC or authenticated IMSI” TS 29.274 v16.13.0
  • IP addressing with IPv4/IPv6 capable GTP-C entities TS 29.274CR1956
Rel-20 1 CR

GTP-C messages in TS 29.274 gain new UHRR Support Indication and UHRR Enabled Indication information, extending the control-plane signalling content.

  • “UHRR Support Indication and UHRR Enabled Indication in GTP-C Message” TS 29.274 v20.0.0
  • UHRR Support Indication and UHRR Enabled Indication in GTP-C Message TS 29.274CR2137

Defining Specifications

3GPP specifications that define or reference GTP-C, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 29.060 vj00 GPRS Tunnelling Protocol (GTP) version 1 Rel-19 read
TS 29.281 vj20 GTPv1-U Protocol Specification Rel-19 read
TS 33.117 vk20 Catalogue of Security Requirements and Tests Rel-20 read