Multi-Path QUIC

Description

Multi-Path QUIC (MPQUIC) is an extension of the QUIC transport protocol, standardized by the IETF and adopted by 3GPP. It allows a single QUIC connection to utilize multiple distinct network paths concurrently. This is achieved by establishing multiple subflows within a single connection, each bound to a different 5-tuple (source IP, source port, destination IP, destination port, transport protocol). Each subflow operates independently, with its own congestion control and packet numbering, but they share a common cryptographic and connection context. The protocol intelligently schedules packets across available paths based on real-time path characteristics like latency, loss, and available bandwidth. A key architectural component is the path manager, which discovers, validates, and monitors the viability of each potential path. MPQUIC also handles path migration seamlessly; if one path fails, traffic is immediately rerouted to other active paths without breaking the application-layer connection. This multi-path capability is integrated into the 5G system architecture, where it can leverage multiple PDU sessions, multiple access technologies (e.g., 3GPP and non-3GPP access), or different user plane functions. The 5G core network, through entities like the SMF and UPF, supports the establishment and policy control for connections that can exploit MPQUIC. From an endpoint perspective, devices with multiple radio interfaces (e.g., 5G NR and Wi-Fi) can use MPQUIC to bond these links, presenting a single, robust, high-performance pipe to the application layer.

Purpose & Motivation

MPQUIC was created to address the limitations of single-path transport protocols in increasingly heterogeneous and multi-connected network environments. Traditional TCP and even single-path QUIC are bound to one network path per connection, making them susceptible to the performance bottlenecks or failures of that single path. With the proliferation of devices equipped with multiple radios (e.g., 5G, LTE, Wi-Fi), there was a clear opportunity to improve performance, reliability, and user experience by utilizing all available links simultaneously. The primary problems MPQUIC solves are: 1) Inefficient resource utilization, where only one network interface is used at a time despite others being available; 2) Latency spikes and connection interruptions during handovers or path failures; and 3) Inability to aggregate bandwidth from disparate links to meet the high-throughput demands of modern applications like ultra-HD video, cloud gaming, and massive file transfers. Historically, solutions like MPTCP existed but faced deployment challenges due to middlebox interference and complex network integration. QUIC, being a UDP-based protocol encrypted by default, is more resilient to middlebox manipulation. Extending it with multi-path capabilities (MPQUIC) provided a cleaner, more deployable solution that aligns with the 5G architecture's native support for concurrent access and network slicing. Its adoption in 3GPP Rel-18 was motivated by the need for enhanced transport flexibility to support new service requirements for immersive media, industrial IoT, and reliable vehicular communications.

Key Features

• Concurrent multi-path transmission over heterogeneous accesses (e.g., 5G and Wi-Fi)
• Seamless path migration and failover without breaking the application connection
• Per-path congestion control for efficient bandwidth utilization
• Aggregated throughput and reduced latency through intelligent packet scheduling
• Enhanced connection resilience and robustness against single-path failures
• Tight integration with 5G system architecture and PDU session management

Evolution Across Releases

Defining Specifications