How Tencent’s TQUIC Stack Boosts Mobile App Performance in Weak Networks

Introduction

Tencent’s core‑business users saw login time reduced by 30% and download success rates rise from 60% to 90% within 500 ms on weak and cross‑network scenarios. These gains come from the TQUIC network protocol stack built by the sTGW team, which is deployed in real‑time communication, audio‑video, online gaming, and advertising services.

1. QUIC/HTTP3 Protocol Overview

QUIC (Quick UDP Internet Connection) is a UDP‑based reliable transport protocol proposed by Google. It implements loss recovery, congestion control, and sliding‑window mechanisms at the application layer and provides forward‑secure encryption. HTTP/3 is the IETF’s next‑generation HTTP built on top of QUIC.

2. Core Advantages of QUIC

0‑RTT connection establishment.

Head‑of‑line‑blocking‑free multiplexing.

Connection migration using a 64‑bit ConnectionID.

Unlike TCP, QUIC’s multiplexed streams are independent, eliminating head‑of‑line blocking. Connection migration allows a session to survive network changes (e.g., Wi‑Fi to cellular) without interrupting data transfer.

3. Stack Selection

QUIC requires both client and server stacks to support the protocol. As of now, only iOS 15’s NSURLSession supports HTTP/3 under specific conditions; other platforms and mainstream libraries lack QUIC support.

4. Engineering Practice – Using Chromium Cronet

To accelerate adoption, the team chose the open‑source Chromium Cronet stack as a foundation. Cronet provides a complete QUIC implementation together with HTTP/2, WebSocket, FTP, and SOCKS support, and it offers both gQUIC and iQUIC versions.

Full protocol suite (QUIC, HTTP/2, WebSocket, FTP, SOCKS).

Support for both gQUIC and iQUIC, continuously updated.

Excellent cross‑platform compatibility.

5. Reducing Code Size and Improving Integration

Cronet’s codebase contains ~850 k lines and >2 800 classes, most of which are unrelated to QUIC. By removing browser‑specific logic, unused protocols (FTP, WebSocket), and non‑QUIC modules (TCP connection pool), the team compressed the critical workflow from 21 steps to 5 and reduced functions from 146 to 24.

6. Enhancing Usability

Even after shrinking the binary, Cronet remained hard to use. The team identified common pain points and introduced:

Socket‑level UDP APIs for direct IP‑level QUIC requests.

Unified configuration and performance‑metric interfaces.

7. Advanced Features – Private Protocols and Plaintext Transmission

To support custom protocols (e.g., gaming, audio‑video) that do not require HTTP, the team allowed streams to send raw data directly. For plaintext transmission, they hooked the encryption suite in

QuicFramer

with

FakeEncrypt/FakeDecrypt

, enabling optional unencrypted traffic while preserving the handshake negotiation.

8. Weak‑Network Optimizations – Connection Migration

The team built a cross‑platform connection‑migration mechanism that works without OS‑specific notifications. They also added a heuristic weak‑network detection model that proactively triggers migration when packet loss is detected, ensuring seamless data flow during network switches.

9. Weak‑Network Optimizations – Full 0‑RTT Handshake & Forward Security

Standard GQUIC performs a 1‑RTT handshake on cold start, then uses the ServerConfig (SCFG) as a non‑forward‑secure key for the first data burst. The team introduced two enhancements:

Achieve 100 % successful 0‑RTT handshakes for latency‑sensitive workloads.

Force forward‑secure key generation (1‑RTT) for security‑critical services such as finance.

10. Real‑Time Transmission (Unreliable Datagram)

QUIC’s draft real‑time extension allows unreliable data frames that skip the sliding‑window limit and are not retransmitted, suitable for audio‑video and interactive gaming. The implementation provides configurable retransmission strategies, from no retransmission to selective key‑frame retransmission, driven by the weak‑network model.

Conclusion

Through continuous investment, Tencent’s TQUIC stack is now deployed in real‑time communication, audio‑video, online gaming, and advertising services, delivering measurable improvements in login success rate, latency, handshake time, and download speed. Cloud customers using CLB with HTTP/3 see latency reductions exceeding 20 percentage points.