RTMP Streaming Over QUIC for Low-Latency Live Media
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing live streaming protocols such as RTMP, HLS, and HTTP-FLV fail to meet high user requirements for low latency and real-time performance in media streaming.
Innovation Solution
Implementing a QUIC transport protocol for establishing connections with RTMP servers by using a QUIC identifier in the uniform resource identifier, allowing for QUIC and RTMP connections to be established, with optional fallbacks to TCP connections when necessary, and utilizing protocol stacks to encapsulate and parse data.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional protocols (RTMP, HLS, HTTP-FLV) are used for live streaming, then compatibility and ease of operation are maintained, but real-time performance and latency are insufficient
Solution Approach 1:
The patent changes the transport protocol parameter from traditional TCP-based protocols (RTMP, HLS, HTTP-FLV) to QUIC protocol, which operates over UDP. This parameter change enables lower latency and improved real-time performance while maintaining compatibility through the RTMPQ protocol layer that encapsulates RTMP commands within QUIC packets.
2Loss of time
If QUIC protocol is adopted for improved real-time performance, then latency is reduced and security is enhanced, but device complexity and protocol compatibility challenges arise
Solution Approach 1:
The patent implements nesting by encapsulating RTMP protocol commands and data within QUIC protocol packets. The RTMPQ protocol stack nests RTMP application layer messages inside QUIC transport layer packets, allowing the system to leverage QUIC's low-latency transport capabilities while maintaining RTMP's application layer compatibility, thus reducing the perceived complexity for legacy applications.
Solution Approach 2:
The RTMPQ protocol stack serves as an intermediary layer between the QUIC transport protocol and the RTMP application protocol. This mediator translates and adapts between the two protocols, handling packet encapsulation, decryption, and command reconstruction, thereby shielding application developers from QUIC's complexity while enabling improved real-time performance.
3Reliability
If QUIC connection is established for enhanced security and mobility, then network connectivity and security are improved, but compatibility with existing RTMP infrastructure may be compromised
Solution Approach 1:
The RTMPQ protocol stack provides multi-functionality by supporting both QUIC and traditional TCP transport modes. It can encapsulate RTMP commands in QUIC packets for enhanced security and mobility, or fall back to traditional RTMP over TCP for maximum compatibility, making the system universally adaptable to different network environments and server configurations.
Data Source
AI summary
The present application provides a media streaming method. The method is applied to user equipment, and includes: obtaining a uniform resource identifier for accessing an RTMP server; determining whether the uniform resource identifier carries a QUIC identifier; establishing a QUIC connection with the RTMP server based on a QUIC transport protocol in response to determining that the uniform resource identifier carries the QUIC identifier, and establishing a target RTMP connection that is based on the QUIC connection. In the present application, the QUIC connection and the target RTMP connection that is based on the QUIC connection are established based on the uniform resource identifier carrying the QUIC identifier. In this way, an RTMP packet is encapsulated into a QUIC packet, and data is transmitted through the QUIC connection. Therefore, real-time performance of transmission is improved.