Overview

Features

RTS builds on standard live streaming with end-to-end latency monitoring, optimized transmission protocols, and UDP-based transport. Integrated with ApsaraVideo Player SDK, RTS supports tens of millions of concurrent streams at millisecond-level latency, compared to the 3–6 seconds typical of conventional live streaming.

Industry recognition

Alibaba Cloud co-authored Grading Model for the Performance and Quality of Ultra-low-latency Livestreaming Services and Capability Standards for Transmission and Distribution Networks Facing Real-time Communication with CAICT. ApsaraVideo Live was among the first evaluated under these standards and received the highest "Excellent" rating for interactive live streaming. For more information, see Alibaba Cloud RTS is awarded the "Excellence Grade" certification from CAICT.

Architecture

To enable RTS, add an RTS streaming domain to your existing standard live streaming setup for multi-protocol playback.

Note

Ingest can use standard RTMP. End-to-end latency depends on ingest network quality, GOP size, and player-side buffer settings.
Standard live streaming playback (RTMP, FLV, HLS) uses rtmp:// and http:// URLs, while RTS playback uses the artc:// format.

RTS vs. standard live streaming

Enable RTS alongside standard live streaming for a seamless upgrade. If RTS playback fails, the system falls back to standard streaming.

Usage notes

For RTS stream ingest and playback, use the Push SDK and the ApsaraVideo Player SDK.

Solution comparison

Solution	RTS	Standard live streaming
Ingest protocol	RTMP, ARTC	RTMP
Playback protocol	ARTC (based on WebRTC)	RTMP, FLV, HLS
Performance in poor network conditions	Maintains smooth playback with up to 30% packet loss.	Limited resilience in poor network conditions.
Compatibility	Native: Compatible with major operating systems. Web: Over 98% compatibility rate across devices.	HLS: Good compatibility. RTMP: Poor compatibility, not recommended for playback. FLV: Poor compatibility on mobile web (H5).
Coverage	Global	Global
End-to-End latency	400–800 ms with RTMP ingest. 200–400 ms with ARTC ingest.	3–6 seconds for RTMP and FLV. ≥10 seconds for HLS.
Best practices	Reduce e-commerce live streaming latency to 400-800 ms Reduce streaming latency to 200–400 ms	Get started with ApsaraVideo Live

Use case comparison

Solution	Use case
RTS	High-interaction scenarios: e-commerce, group streaming, online education, and enterprise webcasts where low latency drives engagement and conversion. Synchronized viewing: live sports and gaming events where all viewers see the action simultaneously.
Standard live streaming	Low-interaction scenarios: one-way broadcasts where minor playback timing differences between viewers are acceptable.

Demonstration

This video compares RTS and standard live streaming latency:

Use cases

Use case	Description
Online education	Large-scale classes where students interact with the instructor in real time.
E-commerce	Real-time Q&A and product discussions between sellers and buyers.
Live sports	Sports and esports broadcasts where viewers experience the action as it happens.
Interactive entertainment	Hosts respond instantly to viewer interactions such as virtual gifts.

Billing

RTS uses a separate pricing model from standard live streaming:

RTS billing is independent of standard live streaming charges.
RTS can be billed by data transfer (traffic).
Changes to your standard live streaming billing method also apply to RTS.

RTS billing

Try the demo

Scan this QR code with DingTalk to download and install the RTS demo.

001

FAQ

Contact us

For technical questions, join DingTalk group 44533142. For product issues or quality investigations, submit a ticket to contact Alibaba Cloud technical support.