Prevent the broadcasting of non-compliant content

Download
Focus Mode
Font Size
Last updated: 2026-05-22 17:34:47
Solution Background
For critical live streaming events, it is imperative to strictly prevent the broadcast of non-compliant content to mitigate regulatory or legal risks, and to avoid potential streaming disruptions or public relations crises arising from violations.
Such activities encompass live broadcasting scenarios including television networks, OTT platforms, significant conferences, online training sessions, top-tier live streamers, and corporate executive broadcasts. For these scenarios, the industry typically employs manual review mechanisms. Upon detection of any visual or auditory risks during the review process, the live stream will be promptly terminated.
The most straightforward approach involves monitoring live streams in real time, yet this method presents an inherent flaw: audiences may inadvertently view inappropriate content before violations are detected and the stream is terminated.  
A more secure alternative is to implement delayed stream monitoring (time-shifted streams). This solution effectively prevents viewers from being exposed to prohibited material. However, interrupting the stream in this scenario can significantly disrupt the live broadcast, potentially causing technical failures during critical events or even triggering public incidents.
Solution Overview
To rigorously prevent the dissemination of non-compliant content during live streaming while minimizing impact on the broadcast, we have designed a comprehensive solution: "Delayed Playback + Standby Stream + Content Moderation." This approach not only effectively blocks inappropriate content from being aired but also prevents scenarios of black screens or abrupt stream termination, thereby delivering superior live streaming performance. The implementation procedure is as follows:
Step 1: Delayed Playback Configuration
First, configure the delayed playback feature for the live stream. Delayed playback means setting the live stream to play with a delay. For example, if you set a 90-second delay, the viewer will see the video 90 seconds later. This delay provides sufficient time for reviewers to review the content.
The configuration methods for delayed playback primarily encompass the following three approaches:
Method 1: Configure delayed playback settings in the CSS console. For detailed operations, please refer to the documentation.
Method 2: Configure delayed playback by invoking Cloud APIs. For detailed operations, please refer to Configuring Delayed Live Streaming.
Method 3: By appending the txDelayTime parameter to the streaming URL, you can swiftly enable the Delayed Playback feature. For detailed implementation, please refer to the Delayed Playback documentation.
Step 2: Standby Stream Configuration
Furthermore, configure the Standby Stream functionality for the live stream. The Standby Stream serves as a failover mechanism that automatically switches the broadcast signal to a predefined backup source in the event of an unexpected interruption, thereby preventing streaming failures or blank screen incidents. The Standby Stream content can be configured as either an image or a video file. In this solution, upon detection of non-compliant content during the review process, the system can promptly switch the broadcast feed to the Standby Stream.
The configuration methods for standby streams are as follows:
Method 1: Configure the Standby Stream via the CSS console. For detailed operations, please refer to the documentation.
Method 2: Configure Standby Streams by invoking Cloud APIs. First, create a Standby Stream template, then establish Standby Stream rules.
After configuring Delayed Playback and Standby Stream, the workflow for live streaming and playback proceeds as illustrated in the following diagram:
﻿
Live Streaming + Time-Shifted Playback Viewing Process
Viewers are watching a time-delayed stream, where the displayed content lags behind the broadcaster's live feed by a predetermined interval. This delay duration corresponds precisely to the value configured in the aforementioned "Delayed playback configuration" section, typically set to 90 seconds as an example.
Reviewers can promptly identify issues by playing the live stream. To play the live stream, append the parameter &txPlayNoDelay=true to the viewer's playback URL. To prevent URL leakage or unauthorized parameter addition, this parameter can be incorporated into the generation logic of the playback signature txSecret. Any modification, addition, or deletion of this parameter will result in playback failure. This method requires submitting a ticket in advance to apply for configuration activation before it can be used. Once activated,the generation method is as follows: txSecret = MD5(KEY + StreamName + txPlayNoDelaytrue + txTime).
Step 3: Content Review and Standby Stream Switching
After configuring the aforementioned Delayed Playback and Standby Streams features, moderators can conduct real-time review of designated live streaming rooms as needed.
Upon identifying any issues, the reviewer shall promptly switch the audience feed to standby streams, which can be accomplished through either of the following methods:
Method 1: On the Live Streams page of the CSS console, click to Enable Standby Stream. For detailed operations, please refer to Standby Streams Management.
﻿
Method 2: Accessing Standby Streams via Cloud API calls. For detailed operations, please refer to Initiating Standby Streams.
Upon switching to the Standby Stream, the streaming and playback processes undergo adjustments. During this transition, viewers are presented with the Standby Stream content, thereby avoiding exposure to potentially non-compliant footage from the delayed stream. The live broadcast room continues to operate normally after the switch, ensuring uninterrupted viewing without black screens or abrupt terminations. Given that the Standby Stream content remains contextually relevant to the live broadcast (such as advertisements), it effectively prevents any significant broadcasting incidents.
﻿
Live Streaming + Standby Stream Viewing Process
Review personnel can still monitor the live stream for content verification to determine whether the violating material has ceased. To access the live stream, append the parameter &txNoSwitchInput=1 to the viewer's playback URL. To prevent URL leakage or unauthorized parameter manipulation, integrate this parameter into the playback signature txSecret generation logic—any addition, deletion, or modification of this parameter will result in playback failure. This method requires submitting a ticket in advance to apply for configuration activation before it can be used. Once activated, the generation method follows: txSecret = MD5(KEY + StreamName + txPlayNoDelaytrue + txNoSwitchInput1 + txTime). 
Upon confirmation that the violation has ceased, you may proceed to switch the audience's viewing stream back to the previous Delayed Playback feed. The following two methods are available for this operation:
Method 1: On the CSS console's Live Streams page, click to Disable Standby Stream. For detailed operations, please refer to Standby Stream Management.
Method 2: Deactivate the standby stream by invoking the Cloud API. For detailed procedures, please refer to Terminating Standby Stream Access.
After disabling the standby stream, the live streaming process reverts to the standard workflow depicted in the "Live Streaming + Time-Shifted Playback Viewing Process" diagram.
Note:
After disabling the standby stream, to prevent exposure of non-compliant content, the system will wait until the delayed playback duration concludes before switching the audience view from the standby stream to the delayed playback stream.
Further Inquiries
Should you encounter any issues during the operation process, please submit a ticket to contact us, and we will provide comprehensive assistance throughout the resolution process.                              