Tencent sTGW TQUIC: Reducing Login Latency by 30% and Boosting 500 ms Success Rate to 90%

In this article the Tencent sTGW team presents the TQUIC network protocol stack and its impact on core business services. By leveraging a QUIC‑based implementation the team achieved a 30% reduction in user login latency and increased the success rate of 500 ms download requests from 60% to 90% in weak‑network and cross‑network scenarios.

QUIC (Quick UDP Internet Connections) is a UDP‑based transport protocol originally proposed by Google. It provides reliable transmission, congestion control, forward‑secure encryption and, when combined with HTTP/3, replaces the traditional TCP+TLS+HTTP stack. The article explains the QUIC/HTTP3 layered model and compares it with HTTP/2.

The TQUIC stack builds on HTTP/3/QUIC and adds several key capabilities: 0‑RTT handshakes, connection migration, real‑time transmission, private‑protocol support and plaintext transmission. These features enable seamless user experience when the network changes (e.g., Wi‑Fi to cellular) and allow custom protocols (such as game or audio‑video streams) to bypass the HTTP layer.

Engineering highlights include a thorough code‑size analysis of the Chromium Cronet library (≈850 k lines, 2 800 classes) and aggressive pruning of unused browser‑related logic, FTP/WebSocket modules, and TCP‑related components. After slimming, the dynamic library size on Android dropped to ~3 MB, making the stack suitable for mobile apps.

To support private protocols and plaintext transmission the team hooked the QuicFramer encryption suite, injecting FakeEncrypt/FakeDecrypt modules. This approach adds negligible code intrusion while allowing optional encryption based on business needs.

Real‑time transmission, an IETF draft extension, is also integrated. It shares the underlying QUIC transport but uses unreliable frames, optional retransmission, and separate congestion control, making it ideal for low‑latency audio/video or interactive gaming.

Weak‑network optimizations include a heuristic model that triggers early connection migration based on packet loss detection, and two handshake variants: a 100% successful 0‑RTT handshake for latency‑critical workloads, and a forced forward‑secure 1‑RTT handshake for security‑sensitive scenarios such as finance.

Deployment results show that TQUIC has been rolled out to multiple Tencent services—real‑time communication, audio/video, online gaming, and advertising—delivering measurable improvements in login success rate, latency, handshake time, and download speed. Tencent Cloud CLB customers using HTTP/3 report more than 20% latency reduction.

References: RFC 9000 (QUIC), IETF QUIC‑Datagram draft, internal design documents, and related ACM research.