Multi-Path QUIC proxying Ethernet in HTTP

Description

MPQUIC-E, short for Multi-Path QUIC proxying Ethernet in HTTP, is a Release 19 feature that enables the transport of Ethernet frames over HTTP using the Multi-Path QUIC (MPQUIC) protocol. It is part of 3GPP's efforts to support non-3GPP access to the 5G core network, particularly for devices that use Ethernet as their link-layer technology. The feature is specified in TS 24.193 (Access traffic steering, switching, and splitting), TS 24.501 (Non-Access-Stratum protocols for 5G system), and TS 29.244 (Interface between the Control Plane and the User Plane of the 5G System).

In a 5G network, non-3GPP access (e.g., Wi-Fi, wired Ethernet) can be integrated via the N3IWF (Non-3GPP InterWorking Function) or the TNGF (Trusted Non-3GPP Gateway Function). MPQUIC-E extends this by allowing Ethernet frames to be encapsulated in HTTP/3 messages, which are then carried over MPQUIC. MPQUIC is an extension of QUIC that supports simultaneous use of multiple network paths, providing benefits such as increased bandwidth, reduced latency, and improved resilience through path redundancy. By proxying Ethernet in HTTP, MPQUIC-E enables Ethernet devices to connect to the 5G core without requiring IP-level tunneling, simplifying deployment and leveraging web-based protocols.

The architecture involves a client (the device or a proxy) and a server (the TNGF or N3IWF). The client encapsulates Ethernet frames into HTTP/3 data streams, which are multiplexed over one or more QUIC connections. MPQUIC manages the multiple paths, scheduling packets across them based on policies. The server decapsulates the Ethernet frames and forwards them to the 5G core via the appropriate interface (e.g., N2/N3). This approach allows for seamless mobility and multi-access aggregation, as the device can use multiple access networks simultaneously.

Key components include the MPQUIC-E client, the MPQUIC-E server, and the underlying QUIC transport. The client is typically integrated into the device's operating system or a dedicated application. The server resides in the TNGF or N3IWF. The feature relies on HTTP/3, which uses QUIC as its transport, and on MPQUIC for path management. 3GPP specifies the encapsulation format, the signaling for path establishment and teardown, and the interaction with the 5G core's session management functions.

MPQUIC-E is particularly useful for industrial IoT and fixed wireless access scenarios where Ethernet is prevalent. It allows Ethernet devices to benefit from 5G's reliability and performance without requiring complex IP configuration. By using HTTP, it also aligns with web technologies, potentially simplifying integration with cloud services. The feature is part of Rel-19's broader work on enhancing non-3GPP access and multi-path support, and it is expected to be further refined in future releases.

Purpose & Motivation

MPQUIC-E was created to address the need for efficient and reliable transport of Ethernet traffic over non-3GPP access in 5G networks. Traditional methods for integrating Ethernet devices into 5G, such as using IPsec tunnels or GTP-U, can be complex and may not fully leverage the capabilities of modern transport protocols. MPQUIC-E solves this by using Multi-Path QUIC, which provides multiplexing, low-latency connection establishment, and multi-path support, all within an HTTP/3 framework.

The motivation comes from the growing demand for Ethernet-based services in industrial environments, where devices often communicate via Ethernet and require deterministic, high-reliability connectivity. By proxying Ethernet in HTTP, MPQUIC-E allows these devices to connect to the 5G core through a web-friendly protocol, enabling easier integration with application servers and cloud platforms. It also supports multi-path operation, which can improve reliability by using multiple access networks simultaneously, and increase throughput by aggregating bandwidth.

Historically, 3GPP has defined various non-3GPP access mechanisms, but they were primarily IP-centric. With the rise of Ethernet-based industrial IoT and the need for seamless integration, Rel-19 introduced MPQUIC-E to provide an Ethernet-over-HTTP solution. This complements existing features like ATSSS (Access Traffic Steering, Switching, and Splitting) and extends them to Ethernet traffic. The feature is expected to simplify deployments and enhance performance for Ethernet devices in 5G networks.