QUIC (RFC 9000) is the underlying transport protocol of the next-generation Internet protocol HTTP/3, which provides connectivity for the modern mobile internet with less connection overhead and message latency compared to TCP/TLS protocols. Based on the advantages of QUIC, which make it highly suitable for IoT messaging scenarios, EMQX 5.0 introduces QUIC support (MQTT over QUIC) and designs a unique messaging mechanism and management approach.
We will discuss MQTT over QUIC in detail to show the advantages and value of this leading technology implementation for IoT scenarios. You will be able to leverage EMQX 5.0’s support for QUIC through this article and make the IoT data transfer more efficient, stable, and low-cost in various MQTT application scenarios.
“Based on the advantages of QUIC, which make it highly suitable for IoT messaging scenarios, EMQX 5.0 introduces QUIC support (MQTT over QUIC) and designs a unique messaging mechanism and management approach.”-EMQ Technologies Inc.
What is QUIC?
QUIC is a common transport layer network protocol built on top of UDP, originally proposed by Google as an alternative to TCP+TLS to improve end-to-end user experience. QUIC has many advantages over existing TLS over TCP implementation:
- High-performance low latency of connection handshake with one round trip or zero round trip: QUIC reduces the overhead during connection setup. As most of the network connections will demand TLS, QUIC exchanges the TLS keys in the initial handshake process. When the client opens a connection, the response contains the data needed for further encryption. This eliminates the need to set up the TCP connection and then negotiate the security protocol over TLS. And most importantly, it saves round trips during connection setup and thus reduces the overall connection setup latency.
- QUIC runs over UDP: QUIC runs over UDP not TCP. QUIC stream is separately flow controlled and lost data is retransmitted at the level of QUIC, not UDP. This means that if an error occurs in one stream would not affect the other streams in the same connection. For the application over the QUIC layer, data processing will not be blocked due to some error in a single multiplexed stream thus improving the parallelization and overall performance.
- End-to-end encryption, handshake authentication via TLS 1.3
- Multiplexed connections: Allowing one connection carries multiple streams for parallelization.
- Improved congestion control, pluggable congestion control policies: Application over QUIC, runs closely to QUIC stack can do flow control on its own and also get involved for congestion control. This makes the Application very flexible for priority traffic, rate-limiting, and managing overloaded situations.
- Multipath support for smooth connection migration: QUIC supports connection migrations on both the server and client side, which makes the connection be kept alive even as the lower layer network is switched as the client is moving from Wifi to a cellular network (4G, 5G).
- Existing networks can be supported without retrofitting or upgrading: QUIC has become the underlying transport protocol for the next-generation Internet protocol, HTTP/3.
Introduction to HTTP/3 Protocol
In October 2018, the IETF’s HTTP and QUIC Working Group jointly decided to name HTTP mapping over QUIC as HTTP/3 in order to accelerate its adoption as a global standard. On June 6, 2022, the IETF standardized HTTP/3 to RFC.
The goal of HTTP/3 is to provide fast, reliable, and secure web connections on all types of devices by solving the transport-related problems of HTTP/2. HTTP/3 uses similar semantics to the HTTP/2 version, including the same request methods, status codes, and message fields. The fundamental difference is that HTTP/2 uses TCP/TLS as the underlying protocol, whereas HTTP/3 uses QUIC. According to W3Techs, at least 40 percent of Internet traffic is over QUIC, and 25 percent of the top 10 million websites already support the HTTP/3 protocol, including top-streaming sites such as Google, YouTube, Facebook, and more.
QUIC in MQTT Communication Scenarios
MQTT is a connection-based IoT communication protocol with a compact message structure that enables stable transmission over severely constrained hardware devices and low-bandwidth, high-latency networks. The keep-alive mechanism will message QoS and many other features can cope with various IoT scenarios. Nevertheless, the MQTT protocol has inherent drawbacks in certain complex network environments due to underlying TCP transport protocol limitations.
- Frequent connection interruptions due to network switching.
- Difficult to re-establish connection after disconnection: the operating system is slow to release resources after disconnection, and the application layer cannot sense the disconnection status in time, and the Server/Client overhead is high when reconnecting.
- In a weak spotty network environment, data transmission is blocked by congestion, packet loss, and retransmission.
For example, connected vehicle users usually face similar problems: vehicles may run in mountainous areas, mines, tunnels, etc., which can cause connection interruptions when entering signal dead zones or passively switching base stations (also referred to as spotty networks). Frequent connection interruptions and slow connection establishment can lead to poor user experience. In some services with high requirements for real-time data transmission and stability, such as the L4 driverless vehicle, it costs a lot for customers to mitigate this problem.
In these scenarios, the low connection overhead and multi-path support of QUIC shows its strengths. After deeper exploration, we believe that MQTT over QUIC is a great solution to this dilemma – based on QUIC’s 0 RTT/1 RTT reconnect/new capability and migration support, it can effectively improve user experience in weak networks and irregular network paths.
MQTT over QUIC Implementation of EMQX 5.0
The current implementation of EMQX replaces the transport layer with a QUIC Stream, where the client initiates the connection and creates a bi-directional Stream. EMQX and the client interact on it. Considering the complex network environment, if for some reason the client fails to complete the QUIC connection handshake, it is recommended that the client automatically fall back to a traditional TCP connection to ensure connectivity.
MQTT protocol can benefit from using QUIC as its transport as follows:
- Keep connection alive even after network switch, NAT rebinding.
- Fast connection establishment, reduces handshake latency.
- Mitigating frequent connect/reconnect.
- Quick connection recovery.
- More advanced congestion control: Effectively reduces packet loss and enables continuous and stable data transmission despite network fluctuations in tests.
- Operationally and maintenance-friendly: Reduce overhead (time overhead, client/server performance overhead) caused by massive reconnection and reduce system overload caused by unnecessary application layer state migration (0 RTT).
- More flexible architectural innovations: e.g., Direct server return (DSR, direct server return mode), where only ingress/request traffic passes through the LB and egress and response traffic bypasses the LB and goes directly back to the client, reducing bottlenecks in the L.
- Multi-path support for smooth connection migration: Handover from 4G to WIFI, or if the quintet changes due to NAT Rebinding, QUIC can maintain a connection on the new quintet, especially for mobile devices where the network changes frequently.
- More agile development and deployment: It is suggested to implement the QUIC protocol stack in the user space, enabling fast iterations, quick bugfix rollout, and reducing the lead time from PoC to production.
- End-to-end encryption: QUIC packet leaves minimal information unencrypted in the headers to make communication secure and imperceptible by middleboxes.
There are also more opportunities to be explored:
- Streams with different topics: We could use parallel streams in the same connection to carry different topics to make sending/receiving process parallelized with different priorities and mitigate the HOL (Head Of Line) blocking issue.
- Streams with different QoS: For example, in “Flow Control”, QoS 0 messages should give way to high QoS messages.
- Separate control messages into different streams: MQTT control messages can be sent in one or two directions. For example, the client can send UNSUBSCRIBE requests asynchronously through a short-lived unidirectional stream to request the server to stop sending data that is no longer of interest.
- Finer-grained send and receive collaborative flow control: Flow control is performed on a per-flow basis or across the entire connection, enabling finer-grained flow control.
QUIC vs TCP/TLS
We simulated the performance of QUIC and TCP/TLS under different scenarios based on EMQX v5.0 in the lab environment.
- Test platform: EMQX 5.0 with a single node
- Server specification: AWS EC2 M4.2xlarge (8 cores 32GB)
- Operating system: Ubuntu 20.04
- Number of clients: 5000
- loadgen parallel number: 8
- latency measurements: P95 (percentile)
Client Connection Latency
This is to compare the handshake performance, MQTT connection setup establishment, and subscription completion at different network latencies(ping roundtrip). With 1ms roundtrip time, QUIC and TLS do not show that many differences in latency performance. As the latency grows, 30ms roundtrip time, QUIC outperforms TLS a lot. We could conclude that MQTT over QUIC fits well in a network that has high latency.
0 RTT Reconnection Latency
This is to test the latency required to reinitiate a connection and resume reconnection after a disconnection. After the 1-RTT scenario, EMQX would send NST (new session ticket) to the client for reentering, client could use this session ticket to reestablish the connection to the server by encrypting the first packet it is sending. this is what we called the 0-RTT scenario. QUIC can also carry the application layer packet on the first packet in the 0 RTT scenario. The application layer could exchange data much earlier while the TCP/TLS requires at least two roundtrips to finish the handshake and then start exchanging application data.
The benefit of 0 RTT is that it effectively reduces the handshake overhead and improves performance (handshake latency) for both the client and the server. EMQX sends NST packets to the client by default, with a validity of two hours. However, since 0 RTT early data is not protected against replay attacks, QUIC recommends not carrying data on 0 RTT that would change the application state. EMQX does not support early data by default, and this test is only used for comparison and verification. The test results show that QUIC outperforms pure TCP after the first handshake if the MQTT layer protocol is properly designed.
Server Resource Usage
This test is for the resource usage comparisons in the scenario of massive client connect, disconnect, and then reconnect. The results show that QUIC outperforms TLS in terms of CPU and memory usage, but reconnection consumes more bandwidth than TLS. Due to different implementations, here we compare the performance of two implementations (TCP/TLS and QUIC) in EMQX.
|CPU (first connection)||~60%||~80%|
|CPU (reconnect)||~65% ¹||~75%|
|Maximum memory usage||9 GB||12 GB|
|Network bandwidth usage (Trans+Recv)||Peak value 100Mb ²||Peak value 30Mb|
Note 1: Mainly refer to the additional overhead of MQTT clearing sessions and kicking off old connections.
Note 2: Mainly refer to the large number of QUIC initial handshake packets due to transport path MTU validation.
Client Address Migration
This test simulates the changes in business layer messaging during large-scale client address migration. When the client source address (address and port) is changed, traditional TCP/TLS clients must detect a disconnect, failure of routing, or packet loss at the application layer before reconnecting.
This process is very slow due to various timers and involves many unnecessary retransmissions, loss recovery, etc. The application over TLS runs into the blocking state, and before it starts to clean the state and reestablish the connection, the application data exchange is blocked.
QUIC’s processing is smoother, keeping connections alive when the address is switched without requiring reconnections and leaving the application to no perception (however the application layer can subscribe to address changes if needed). This result shows that QUIC is well suited for environments where networks are frequently switched.
Network Packet Loss Test
This is to test the data transmission in the weak network condition. We did three separate tests: EMQX terminated TCP/TLS, QUIC, and Ngnix terminated TCP/TLS.
Test scenario: EMQX publishes QoS 1 messages at the rate of 20K/s and network errors are injected during the process: 20 percent out of order (inconsistent order of packets at the sender and receiver side), 10 percent packet loss. Additional network switching interferences are added every 30 seconds in the QUIC test. In this case, the data received by the QUIC server is slightly jittery, but no messages are lost; while TLS shows congestion and packet loss due to a poor network environment. This result shows that QUIC can provide reliable transmission in a weak spotty network environment.
When we removed the network error, we can see in the yellow circle that TLS sending and receiving is back to normal, the number of packets is consistent without stacking, while the QUIC has only gone from slightly jittery to smoother.
Easier to Use: MQTT Over QUIC SDK
NanoSDK 0.6.0 has released the first C language MQTT over QUIC SDK based on the MsQuic project. NanoSDK provides a better IoT connectivity experience by adding QUIC support to the transport layer of NNG, enabling protocols such as MQTT and nanomsg to move from TCP to UDP. It internally binds QUIC Stream to MQTT connection mapping and has a built-in function of 0 RTT fast handshake reconnection. For a message code example, please refer to NanoSDK QUIC Demo.
We will also release SDKs for Python, Go, and other languages based on the NanoSDK in the near future, so that more users can experience the advantages of MQTT over QUIC as soon as possible. At the same time, the relevant SDK will support QUIC to TCP fallback. When QUIC is not available, the connection layer will automatically switch to TCP/TLS 1.2, ensuring that services can operate normally in all types of network environments.
NanoSDK and EMQX send and receive messages through QUIC.
Future EMQX QUIC
Combining QUIC features with IoT scenarios, we have planned many features for MQTT over QUIC, such as topic prioritization by differentiating control channels, non-reliable real-time streaming for high-frequency data transfer scenarios, and flexible topic and data channel (Stream) mapping to reduce interference between topics. These will may be presented in future releases depending on the feedback from the community and our customers.
EMQ is also actively promoting the standardization of MQTT over QUIC. We are preparing a draft proposal about MQTT over QUIC after becoming the only Chinese company with voting rights in the OASIS MQTT Technical Committee in 2018 and participating in the 5.0 protocol standard development. We believed that shortly, the underlying protocol of MQTT will support both TCP and QUIC, benefiting the entire IoT industry.
It’s quite obvious that QUIC is very suitable for the weak, lossy, spotty IoT network environment where the UDP MTU size of the traditional TCP/IP network can be guaranteed or the environment where the network is frequently switched. QUIC has great potential for IoT scenarios where the devices are constantly on the move (such as the Internet of Vehicles, mobile collection, etc.), or the device wants to keep a long living MQTT session while having to sleep periodically.