Last update：2022-03-30 15:11:58
QUIC (Quick UDP Internet Connection) is a UDP-based Internet transmission protocol which is developed by Google and is of lower latency. It is a new-round integration and utilization of the existing network transmission technologies between the application layer and the network layer, to improve the transmission efficiency and minimize latency. The core technologies of QUIC include: HTTP/2, TLS 1.3, TCP FAST OPEN and UDP.
QUIC protocol is originally used in the Chrome browser and YouTube video website. With the establishment of the IETF QUIC project team, and the IETF’s announcement in 2018 that QUIC protocol is going to be promoted as HTTP/3.0, QUIC has become widely discussed, applied and developed.
The development of CDNetworks QUIC is based on Google QUIC (gQUIC for short hereafter) version 39, 43 and 44, and it well solves the problems of bad access quality under weak network environments such as cross-ISP and cross-region network.
QUIC improves the performance of web application and streaming, especially under a weak network, it is applicable to the customers who have rigorous requirements on the quality and stability, such as real-time web application, cross-region live streaming, mobile live streaming/VoD customers.
Standard gQUIC is functionally equivalent to HTTP/2 + TLS 1.3 + TCP, but implements on the top of UDP. It provides stream management equivalent to HTTP/2, security connection equivalent to TLS, and re-transmission, orderly transfer and traffic control mechanisms equivalent to TCP.
Figure 1 gQUIC architecture
On the basis of the gQUIC protocol, CDNetworks developed the gQUIC scheme as below.
Figure 2 CA/DWA/MA gQUIC architecture
Figure 3 MALB gQUIC architecture
In last mile, end-users can establish Quic connection with CDN edge PoPs, and there is no need for origin to change any configuration, CDN will go back to origin via TCP as normal.
gQUIC for live stream pushing uses an agent scheme of RTMP over QUIC, in which QUIC Agent plays the role of TCP agent to establish connection with client (Ingester) QUIC SDK, switches UDP to TCP and transfers the live-stream data transparently to the CDNetworks Media Center.
When using this scheme, customers need to use the port 1935/UDP to initiate push-stream requests.
QUIC SDK can be customer’s self-developed SDK or can be provided by CDNetworks. Customer’s self-developed QUIC SDK needs to be in compliance with standard QUIC protocol so as to work with CDNetworks QUIC feature.
gQUIC live stream pulling scheme is available in two modes, which are RTMP over QUIC mode and HTTP over QUIC mode:
For Quic configuration of CA,DWA,MA, CSE/SRE can enable QUIC by changing domain configuration on CONF.
For HTTP over QUIC mode of MALB, CSE/SRE can enable QUIC by changing domain configuration on CONF.
For RTMP over QUIC mode of MALB, CSE will need to send an email with required info to product team for application. No extra CONF configurations are needed.