Path Protocol

Description

The Path Protocol is a foundational transport protocol in 3GPP packet-switched core networks, defined in specifications 29.060 and 29.119. It serves as the bearer for GTP (GPRS Tunnelling Protocol) messages between GPRS Support Nodes (GSNs) — including SGSNs and GGSNs — or between a GSN and a Radio Network Controller (RNC). In essence, the Path Protocol provides the underlying transport mechanism over which GTP control-plane and user-plane packets are carried. It is not a single protocol in itself but rather a role fulfilled by an underlying transport protocol, typically UDP/IP or, in some cases, TCP/IP, depending on the specific interface and release.

Architecturally, the Path Protocol operates at the transport layer, sitting below GTP. On the Gn/Gp interfaces between GSNs, GTP relies on UDP/IP as the Path Protocol for both signalling (GTP-C) and user data (GTP-U). On the Iu-PS interface between the SGSN and the RNC, the Path Protocol is also UDP/IP, carrying GTP-U tunnels for user plane data. The term "path" refers to the logical communication path between two GTP endpoints. Each path is identified by a pair of IP addresses and UDP port numbers. The Path Protocol ensures that GTP Protocol Data Units (PDUs) are delivered between these endpoints, handling fragmentation, reassembly, and error detection as provided by the underlying IP layer.

The Path Protocol is closely tied to the concept of a GTP path. A GTP path is a bidirectional logical connection between two nodes that exchange GTP messages. The path is established when the first GTP message is sent and is maintained as long as the nodes need to communicate. The Path Protocol provides the transport for path management messages, such as Echo Request and Echo Response, which are used to detect path failures and measure round-trip time. These messages are part of GTP-C but are carried over the Path Protocol. If the Path Protocol fails (e.g., due to IP routing issues or UDP port unreachability), the GTP path is considered down, and the nodes may tear down associated PDP contexts or bearers.

In terms of operation, when a GSN or RNC needs to send a GTP message, it encapsulates the GTP PDU into a UDP datagram (or TCP segment, though UDP is far more common) and sends it to the destination IP address and port. The Path Protocol (UDP/IP) then routes the datagram through the IP network. At the receiving end, the Path Protocol delivers the datagram to the GTP layer, which processes the message. The Path Protocol does not provide reliability; that is handled by GTP itself for control messages (via retransmissions) or by higher layers for user data. The Path Protocol's main role is to provide a best-effort, connectionless transport service.

Over successive releases, the Path Protocol definition has remained essentially unchanged, reflecting its stable role in the 3GPP architecture. Even as networks evolved from GPRS to UMTS, LTE, and 5G, the Path Protocol concept persists for legacy interfaces. In 5G, GTP-U is still used on the N3 interface between the gNB and UPF, and the Path Protocol (UDP/IP) continues to serve as its bearer. Thus, the Path Protocol remains a relevant, if low-level, component of modern packet core networks.

Purpose & Motivation

The Path Protocol exists to provide a standardized transport bearer for GTP, enabling communication between GSNs and between GSNs and RNCs in GPRS and UMTS networks. Before its definition, early GPRS implementations used proprietary or non-standard transport mechanisms, which hindered interoperability between equipment from different vendors. The Path Protocol, by leveraging widely deployed UDP/IP, ensures that GTP messages can traverse IP networks reliably and efficiently, regardless of the underlying link-layer technology.

Another motivation was the need for a clear separation between the GTP protocol itself and the transport layer. By defining the Path Protocol as a distinct concept, 3GPP allowed GTP to focus on tunnelling and session management, while the Path Protocol handles addressing, routing, and multiplexing. This modularity simplified the specification and implementation of GTP, and it enabled the reuse of existing IP infrastructure. Furthermore, the Path Protocol supports path management procedures that are essential for detecting failures and maintaining robust connections in a dynamic network environment.

Historically, the Path Protocol emerged from the need to support both signalling and user data over the same transport in a cost-effective manner. As networks grew, the Path Protocol's reliance on UDP/IP proved scalable and flexible, accommodating the increasing volume of mobile data traffic. Even with the advent of new architectures like 5G, the Path Protocol remains relevant for legacy and interworking scenarios, demonstrating its enduring design.