tencent cloud

Cloud Streaming Services

Release Notes and Announcements
Announcements
User Guide
Product Introduction
Overview
CSS Products
Concepts
Features
Use Cases
Strengths
Use Limits
Purchase Guide
Billing Overview
Basic Service Fee
Value-Added Service Fee
Prepaid plan
Purchase Process
Changing Billing Modes
Refund Policy
Viewing Bills
Renewal
Processing for Overdue Payments
Billing FAQs
Live Video Broadcasting (LVB)
Overview
Use Cases
Getting Started
SDK Integration
Live Event Broadcasting (LEB)
Overview
LEB Versus LVB
Use Cases
Getting Started
SDK Integration
Live Video Caster
Overview
Application Scenarios
Feature Area Introduction
Managing Live Video Caster
General Cloud Director
Configuring Program Lists and Automated Broadcasting
Console Guide
Console Overview
Overview
Domain Management
Stream Management
Package Management
AI Features
Feature Configuration
Relay
Billing Usage Statistics
Monitoring
Toolkit
OOTB live
CAM-Based Access Control
Feature Guide
Push and Playback
Features
Practices in Typical Scenarios
Cloud Native Recording
Live Streaming Security
Global CSS Service
Callback Notifications
User Guides for Common Third-Party Tools
SDK Guide
0. SDK Integration Guide
1. Stream Push
2. Playback
3. Advanced Features
API Documentation
History
Introduction
API Category
Making API Requests
Live Pad APIs
Live Stream Mix APIs
Time Shifting APIs
Monitoring Data Query APIs
Billing Data Query APIs
Live Transcoding APIs
Delayed Playback Management APIs
Domain Name Management APIs
Watermark Management APIs
Certificate Management APIs
Stream Pulling APIs
Recording Management APIs
Live Callback APIs
Screencapturing and Porn Detection APIs
Authentication Management APIs
Live Stream Management APIs
Data Types
Error Codes
Ops Guide
Video Stuttering
Troubleshooting Push Failure
Troubleshooting Playback Failure
CLS Assists in Live Stream Troubleshooting
Troubleshooting High Latency
Troubleshooting Poor Quality of Pulled Video
Authorizing CSS to Store Screenshots in a COS Bucket
Troubleshooting
Live Stream Mixing Error `InvalidParameter.OtherError`
About Pushing
Generating Push URLs
PC Push
Playing Method
Web Player
Live Streaming Quiz
FAQs
Service Region
Live Streaming Basics
Push and Playback
CSS Billing
Global CSS Service
Live Recording
On-Cloud Stream Mix
Domain Configuration
Related to Live Video Caster
Compatibility with Apple ATS
Difference Between Stream Interruption and Stream Suspension
SLA
CSS Service Level Agreement
CSS Policy
Privacy Policy
Data Processing And Security Agreement
Glossary

Use Limits

PDF
Focus Mode
Font Size
Last updated: 2024-10-14 14:31:19
Before using CSS, you need to know the following use limits:
Item
Description
CSS domain name
Multiple playback and push domain names can be created under an account. If the acceleration region of a domain name is the Chinese mainland or global, the domain name must have an ICP filing from MIIT, and the filing information must be currently valid and available.
You can manage up to 100 domain names under one account by default. If your business scale is large, you can submit a ticket to apply for increasing the maximum number of domain names.
We recommend you keep the length of a domain name no more than 45 characters. If you want a longer domain name, you need to submit a ticket for assistance.
A domain name managed by CSS can be used to push or play back live streams normally only after the domain name is resolved. For more information, see Configuring CNAME for Domain Name.
Live push
The CSS service does not limit the push bitrate and supports common resolutions and corresponding bitrates.
To avoid push lag, we recommend you keep the bitrate below 4 Mbps.
The length limit for StreamName is 255 characters.
Live playback
A stream can be played back only when the StreamName of the playback address is the same as that of the push address.
The default bandwidth limit is 20Gbps. If there is a need to lift this limit, you can submit a ticket for application.
If you need additional support for a large-scale surge in live streaming traffic, you need to submit a ticket or contact your Tencent Cloud rep three business days in advance for assistance. Such surges mainly include the following two types:
The sudden daily peak bandwidth exceeds 200 Gbps, and the surge is 200% of the daily peak.
The sudden daily peak bandwidth exceeds 500 Gbps.
Template configuration
After a template is successfully bound, it takes 5–10 minutes for it to take effect.
Daily billing mode switch
You can select bill-by-traffic or bill-by-bandwidth for daily billing. You can switch the billing mode only once per day, and the switch will take effect on the next day.
Supported push protocols
Support RTMP, SRT, and WebRTC protocols. For detailed information, see Live Streaming Basics.
When using the WebRTC protocol for push streaming, each push domain has a default limit of 1,000 concurrent streams.
Supported playback protocols
Standard Live Video Broadcasting (LVB) supports the RTMP, FLV, and HLS playback protocols. For more information, see Live Streaming Basics.
Live Event Broadcasting (LEB) supports the WebRTC playback protocol.
LVC
5 LVC instances can be created for each account. You can add new LVC instances after deleting old LVC instances. If you need more LVCs, please submit a ticket for application.
The VOD input playlist supports up to 5 VOD files.
Relaying to third parties supports up to three streams. One stream relays to the current Tencent Cloud CSS account by default, while the other two can relay to third parties.
Relay
A maximum of 200 relay tasks can be created. If your relay business requires a larger number of tasks, please contact us by submit a ticket, or contact your account manager for assistance.
The relay feature only provides content pulling and pushing services. Please ensure that the content is authorized and complies with relevant laws and regulations regarding content distribution. If there are copyright issues or content violations, CSS will stop the related services and reserve the right to pursue legal responsibilities.
To use the relay recording function, you can bind it with the CSS recording template, which will incur recording fees. The recording template bound to the relay task only supports templates that record the original stream. To modify the recording template during the ongoing pull task, you need to stop the current pull task for 30 seconds, then restart the pull task for the new recording template to take effect.

Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback