DTI

Direct Tunnel Indication

Core Network
Introduced in Rel-7
Direct Tunnel Indication (DTI) is a parameter used in the GTP-C protocol to signal the capability and request for establishing a direct user plane tunnel between the Serving Gateway (SGW) and the Packet Data Network Gateway (PGW), bypassing the SGW for user data transfer. This optimizes the data path in the Evolved Packet Core (EPC).

Description

Direct Tunnel Indication (DTI) is a flag or information element within the GPRS Tunneling Protocol for the control plane (GTP-C), specified in 3GPP TS 29.060 and TS 23.060. It is used during the bearer activation or modification procedures, such as in the Create Session Request, Modify Bearer Request, or Create PDP Context Request messages. The primary function of the DTI is to indicate whether the sending node (typically the MME in EPS or the SGSN in GPRS/UMTS) supports and/or desires the establishment of a "direct tunnel" for the user plane. A direct tunnel refers to a GTP-U tunnel for user data that is set up directly between the Serving Gateway (SGW) and the Packet Data Network Gateway (PGW) in the EPC, or between the GGSN and the RNC in the context of UMTS, effectively allowing the user plane to bypass the SGW's forwarding role for certain traffic.

How it works involves negotiation during session management signaling. When an MME that supports direct tunnel functionality initiates a Create Session Request toward the SGW, it may include the DTI set to a value indicating "Direct Tunnel possible." The SGW, upon receiving this, understands that it may be instructed to establish a GTP-U tunnel directly with the PGW, rather than having the user plane data flow from PGW to SGW and then to the eNodeB. If all conditions are met (e.g., the SGW and PGW also support it, and there are no specific legal interception or charging requirements that mandate SGW anchoring), the SGW will proceed to create the direct tunnel. The SGW then includes its own DTI in the message to the PGW. The resulting architecture reduces latency and removes unnecessary processing load on the SGW for the data path.

Its role in the network is one of optimization. In standard operation without a direct tunnel, all user plane packets traverse the SGW, which performs tasks like lawful interception, charging data collection, and downlink packet buffering. By using the DTI to enable a direct tunnel, the data path is streamlined for efficiency, which is particularly beneficial for high-throughput, low-latency services. The SGW remains in the control path, managing bearer contexts and handling mobility events, but is removed from the real-time user data forwarding plane for the indicated bearer, leading to a more distributed and efficient EPC architecture.

Purpose & Motivation

The DTI was introduced to address the need for a more efficient and lower-latency user plane architecture within the 3GPP packet core, particularly with the evolution toward the Evolved Packet System (EPS) in Release 8 and the optimization of earlier GPRS systems. The problem it solves is the suboptimal "tromboning" or "hairpinning" of user data through the SGW in all scenarios. In the baseline architecture, every packet between the UE and the internet would travel PGW<->SGW<->eNodeB, even when the UE is stationary and the SGW's functions like mobility anchoring are not actively required. This adds unnecessary latency and load.

The motivation for its creation, especially noted from its introduction in Rel-7 for UMTS and enhancement in EPS, was to optimize the data path for specific traffic types or states, such as when a UE is in a stable, active state without immediate mobility needs. It allowed operators to design networks where the SGW could be bypassed for certain high-performance data sessions, reducing both capital expenditure (through reduced SGW processing requirements) and operational expenditure (through lower transport costs and improved service quality). The DTI provided a standardized, negotiated mechanism to enable this optimization, moving beyond proprietary solutions and ensuring multi-vendor interoperability for direct tunnel deployments.

Key Features

  • A GTP-C information element used to signal support and request for a direct user plane path.
  • Enables establishment of a direct GTP-U tunnel between SGW and PGW (or GGSN and RNC in UMTS).
  • Negotiated during session management procedures like Create Session or PDP Context Activation.
  • Optimizes the user plane by bypassing the SGW for data forwarding, reducing latency and load.
  • Maintains the SGW in the control plane for bearer and mobility management.
  • Specified in core 3GPP protocols (GTP-C) ensuring standardized implementation across network elements.

Evolution Across Releases

Rel-7 Initial

Initially introduced for UMTS/GPRS networks to optimize the user plane path between the GGSN and RNC, bypassing the SGSN. The DTI parameter was defined in the GTP-C protocol to allow the SGSN to indicate to the GGSN that a direct tunnel could be established, forming the basis for this optimization concept in 3GPP standards.

Enhanced and adapted for the Evolved Packet System (EPS) as part of the SAE architecture. The DTI concept was carried over and applied to the S5/S8 interface between the Serving Gateway (SGW) and Packet Data Network Gateway (PGW), enabling a direct tunnel that bypasses the SGW's user plane, a key optimization for the new flat IP architecture of LTE.

Further refinements and clarifications on the usage of DTI in conjunction with other EPS features, ensuring compatibility with mobility scenarios and multi-access PDN connections. Support for DTI was assumed for network elements supporting optimized user plane architectures.

Continued inclusion in specifications as a foundational optimization feature. Enhancements related to bearer management and interactions with new features like Dedicated Bearers and Traffic Offload potentially referenced DTI capabilities.

Maintained as a core protocol element. Specifications ensured DTI procedures worked correctly with introduced features such as enhanced inter-RAT mobility and further SGW architectural enhancements.

DTI remained a stable part of the GTP protocol. Its role was considered in the context of network densification and small cell architectures where user plane optimization is critical for performance.

No major changes to the DTI parameter itself. It continued to be a supported mechanism for user plane path optimization in the evolving core network.

Continued support within GTP-C specifications. The focus on latency reduction for new services like critical communications reinforced the value of direct tunnel optimizations signaled by DTI.

DTI was carried forward into the 5G System specifications where applicable, though the 5GC uses different protocols (PFCP). The concept influenced the design of efficient user plane paths in 5G, such as the N9 interface between UPFs.

As part of the continued evolution of 4G EPS, DTI remained a supported feature in the GTP-based EPC, ensuring backward compatibility and optimization for LTE networks coexisting with 5G.

Maintained in relevant 3GPP specifications. Its principles are reflected in ongoing work for integrated access and backhaul, and further user plane simplifications.

DTI persists as a legacy but functional parameter in 4G specifications, supporting the large installed base of EPC networks. Its design philosophy continues to inform user plane separation in advanced architectures.

Expected to remain unchanged in its technical definition, ensuring stability for deployed networks. The optimization it enables remains relevant for efficient 4G network operation within a 5G era.

Defining Specifications

SpecificationTitle
TS 23.060 3GPP TS 23.060
TS 29.060 3GPP TS 29.060
TS 32.406 3GPP TR 32.406
TS 43.129 3GPP TR 43.129