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

Glossary term · Protocol

QRT

QUIC RTP Tunnelling

Protocol →

QRT is a Rel-17 mechanism for carrying RTP media over QUIC transport, combining RTP media semantics with QUIC multiplexing, encryption, and congestion control for low-latency real-time media delivery over 5G networks.

Introduced
Rel-17
Where
Services › Codecs
Specifications
2 specs
QRT Description Purpose What changed Neighbours Specifications

Description

QUIC RTP Tunnelling (QRT) is a protocol mechanism introduced in 3GPP Release 17 for transporting Real-time Transport Protocol (RTP) media streams over QUIC (Quick UDP Internet Connections). It is documented in the media handling specifications TR 26.804 and TR 26.805, which study media transport and handling for 5G and immersive services. QRT addresses the challenge of delivering real-time media — such as conversational video, live streaming, and immersive content — using QUIC as the underlying transport instead of, or alongside, traditional UDP and TCP.

RTP has long been the standard protocol for real-time media, providing payload type identification, sequence numbers, timestamps, and synchronization source (SSRC) identifiers that enable media reconstruction, jitter buffering, and lip synchronization. However, RTP over UDP lacks built-in congestion control, encryption, and multiplexing, which are typically provided by companion protocols such as RTCP, SRTP, and ICE. QUIC, by contrast, provides stream multiplexing, integrated TLS 1.3 encryption, connection migration, and modern congestion control (such as NewReno or BBR) within a single transport. QRT bridges the two worlds: it tunnels RTP packets inside QUIC streams so that media applications can retain RTP semantics while benefiting from QUIC's transport features.

The architecture of QRT involves an encapsulation layer that maps RTP flows onto QUIC streams. Each RTP stream, or group of related streams, can be carried over a dedicated QUIC stream, allowing independent delivery and head-of-line-blocking avoidance across streams. Because QUIC encrypts all payloads by default, QRT inherits confidentiality and integrity protection without requiring a separate SRTP layer, although the interaction between QUIC encryption and any RTP-level security must be carefully specified. The tunnelling approach also allows the use of QUIC's connection migration, which is valuable for mobile users whose network path changes as they move between cells or access technologies.

QRT is particularly relevant for 5G media services because it can improve latency and reliability compared to RTP over UDP in challenging network conditions. QUIC's congestion control and loss recovery mechanisms are more sophisticated than those of plain UDP, and its stream multiplexing avoids the head-of-line blocking that can occur when multiple media flows share a single TCP connection. For immersive media, where multiple synchronized streams (video tiles, audio objects, metadata) must be delivered together, QRT's ability to map different flows onto separate streams provides flexibility in prioritization and error handling.

Key components of a QRT implementation include the RTP-to-QUIC encapsulation function, the QUIC transport stack with its TLS handshake and congestion controller, and the media application that consumes the reconstructed RTP stream. Signalling for session setup may leverage existing 3GPP media streaming APIs and architectures, such as 5G Media Streaming, while the transport-level negotiation of QUIC parameters follows IETF specifications. The 3GPP studies in TR 26.804 and TR 26.805 evaluate the performance of QRT against alternative transports and define how it integrates with the broader 5G media delivery ecosystem.

In the overall protocol landscape, QRT represents part of the industry's exploration of QUIC as a universal transport for media. While HTTP/3 and WebTransport use QUIC for web-based delivery, QRT targets scenarios where RTP semantics are required, such as conversational services and low-latency live streaming. Its standardization in 3GPP ensures that 5G media services can adopt QUIC transport in an interoperable manner.

Purpose & Motivation

QRT exists to reconcile two distinct protocol worlds: RTP, which provides the media-specific semantics needed for real-time audio and video, and QUIC, which provides a modern, secure, and congestion-controlled transport. Traditional RTP over UDP requires separate mechanisms for encryption (SRTP), congestion control (often via RTCP feedback and application-level adaptation), and multiplexing, leading to complex protocol stacks. QRT simplifies this by tunnelling RTP inside QUIC, inheriting QUIC's built-in security and congestion control while preserving RTP's media framing.

The motivation for QRT grew out of the broader adoption of QUIC across the internet and the desire to apply its benefits to real-time media in 5G networks. As 5G enabled low-latency and high-throughput services, the limitations of UDP-based RTP in areas such as loss recovery, path migration, and multiplexing became more apparent. QUIC's design — with stream-level flow control, connection migration, and TLS 1.3 — offered solutions to these problems.

Previous approaches either accepted the limitations of RTP over UDP or moved media entirely to HTTP-based delivery, which introduced latency due to TCP or HTTP/3 buffering. QRT provides a middle path: it retains RTP for media semantics while gaining QUIC's transport advantages. The 3GPP studies in Rel-17 evaluate this trade-off and define how QRT can be used for 5G media services, particularly for low-latency and immersive applications where both responsiveness and reliability matter.

What changed in its specifications

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

TS 26.804Rel-18 → Rel-19

Rel-19 adds CMCD reporting, multi-source media delivery, content steering, QoS enhancements, and QUIC-based streaming.

Full comparison in TS 26.804 →

Release Timeline

Evolution Across Releases

An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.

Rel-17 Initial

QRT was introduced in Rel-17 as part of the media transport studies in TR 26.804 and TR 26.805. The initial work defined the tunnelling of RTP over QUIC, examined performance benefits for 5G media services, and outlined integration with 5G media streaming architectures.

The definition text for QRT is unchanged in Rel-19 compared to Rel-17; the term carried over with the same meaning, with continued reference in the media handling specifications.

The definition text for QRT is unchanged in Rel-20; the term remains as defined in Rel-17, with ongoing relevance to media transport studies.

Defining Specifications

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

SpecificationTitleRelease
TS 26.804 vk10 5G Media Delivery Architecture Extensions Rel-20 read
TR 26.805 vh01 Study on Media Production over 5G NPN Systems Rel-17 read