Definition
QUIC (Quick UDP Internet Connections) is a UDP-based transport layer protocol proposed by Google in 2012 and later standardized by IETF (RFC 9000). QUIC integrates transport control, congestion control, encryption, and multiplexing into a single protocol stack and is the underlying protocol for HTTP/3. Compared with the traditional TCP + TLS layered model, QUIC eliminates the cumulative delay from handshakes and head-of-line blocking, significantly reducing the first packet round-trip time (RTT), making it suitable for latency-sensitive web and real-time communication scenarios in weak network environments.
Core Features
- Based on UDP: implemented in user space without kernel modifications, making rapid iteration and deployment easier; avoids interference from TCP intermediate network devices (such as NATs and firewalls) with connection states
- Built-in TLS 1.3: Encryption is coupled with the transport layer, handshake and connection establishment are combined, supports 0-RTT and 1-RTT connection resumption, reducing latency during reconnection.
- Multiplexing without head-of-line blocking: Each stream has independent congestion control, packet loss in one stream does not affect other streams; in contrast to HTTP/2's TCP-layer head-of-line blocking.
- Connection migration: Connection ID is independent of IP, supports maintaining the connection during WiFi and cellular switches, suitable for mobile networks.
Protocol stack and frame structure
The QUIC protocol stack includes: Packet layer (UDP encapsulation), QUIC frame layer (STREAM, ACK, CRYPTO, etc.), encryption layer (TLS 1.3), application layer (HTTP/3). Each QUIC connection is uniquely identified by a 64-bit connection ID and supports multipath transmission (MP-QUIC). Frame types include STREAM (data stream), ACK (acknowledgment), RST_STREAM (stream reset), CONNECTION_CLOSE, etc., enabling streaming transmission and reliable delivery.
Typical Use Cases
QUIC/HTTP/3 is widely used in web browsing, video streaming (such as YouTube, Netflix), CDN acceleration, real-time audio and video (WebRTC), IoT devices and cloud data synchronization, vehicular networks V2X communication, and other scenarios sensitive to latency and packet loss. In weak network and high packet loss environments, QUIC can significantly improve first-screen loading and interactive response speed.
SimtoLink's IoT devices communicate with cloud servers via cellular networks, transmitting data through protocols such as HTTP/HTTPS or MQTT. If the cloud deploys HTTP/3 (QUIC), the connection between the device and the cloud can benefit from QUIC's low latency, connection migration, and resistance to weak networks. When selecting and integrating IoT platforms, SimtoLink assesses the platform's support for QUIC/HTTP/3 to provide better connection solutions for applications requiring high real-time performance and mobile scenarios.