- What's New
- Service Overview
-
Billing
- Billing Items
- Basic Service Billing
- Value-added Service Billing
- Billing Modes
- Changing the Billing Option
- Bills
- Arrears
- Billing Termination
-
Billing FAQs
-
Common Cases
- What Do I Need to Pay?
- Do I Need to Buy the CDN Service Before Using Live?
- How Do I Change the Billing Option?
- Do I Need to Delete Resources If I Don't Want to Use Live Any More?
- How Do I View the Usage and Expenditure of Pay-per-Use Live Resources?
- Is Downstream Traffic or Upstream Traffic Billed?
- Will I Be Billed for URL Validation?
- How Is Transcoding Billed?
- Does the Daily Peak Bandwidth Mean the Upstream Bandwidth or Downstream Bandwidth?
- Why Is a Recording Fee Deducted on the First Day of Each Month?
- Arrears
-
Common Cases
- Cloud Live
-
Media Live
- Overview
- Scenarios
- Functions
- Product Advantages
- Constraints
- Getting Started
-
Console Operations
- Prerequisites
- Functions
- Permissions Management
- Domain Name Management
- Channels
- Live Transcoding
- Service Monitoring
- Cloud Resource Authorization
- Tools
- Best Practices
-
Cloud Live API Reference
- Before You Start
- API Overview
- Calling APIs
- Examples
-
Domain Name Management
- Creating a Domain Name
- Deleting a Domain Name
- Modifying a Domain Name
- Querying a Domain Name
- Mapping Domain Names
- Deleting a Domain Name Mapping
- Configuring the Domain Name IPv6 Function
- Querying IP Address Information
- Modifying the Streaming Domain Name Delay
- Querying the Streaming Domain Name Delay
- Modifying the HLS Configuration of a Domain Name
- Querying HLS Configurations of Domain Names
- Modifying Origin Pull Settings
- Querying Origin Pull Settings
- Notification Management
-
Authentication Management
- Configuring a Referer Validation ACL
- Deleting a Referer Validation ACL
- Querying Referer Validation ACLs
- Querying IP Address ACLs
- Modifying an IP Address ACL
- Generating a Signed URL
- Querying Supported Areas of a Streaming Domain Name
- Modifying Supported Areas of a Streaming Domain Name
- Querying the URL Validation Configuration of a Specified Domain Name
- Modifying the URL Validation Configuration of a Specified Domain Name
- Deleting the URL Validation Configuration of a Specified Domain Name
- Snapshot Management
- Recording Management
- Recording Callback Management
- HTTPS Certificate Management
- OBS Bucket Management
- Transcoding Template Management
- Stream Management
-
Statistics Analysis
- Querying Peak Bandwidth
- Querying Total Traffic
- Querying HTTP Status Codes for Pulling Live Streams
- Querying the Duration of Transcoded Outputs
- Querying Recording Channels
- Querying the Number of Snapshots
- Querying Upstream Bandwidth
- Querying the Number of Stream Channels
- Querying the Historical Stream List
- Querying the Playback Profile
- Querying the Distribution of Live Streaming Metrics by Region
- Stream Analytics
- Appendix
- Change History
-
Media Live API Reference
- Before You Start
- API Overview
- Calling APIs
- Examples
-
OTT Channel Management
- Creating an OTT Channel
- Querying Channel Information
- Deleting Channel Information
- Modifying Channel Packaging Information
- Modifying Channel Input Stream Information
- Modifying Channel Recording Information
- Modifying General Channel Information
- Changing the Channel Status
- Modifying Channel Transcoding Template Information
- Appendix
- Change History
- Cloud Live Server SDK Reference
- Low Latency Live Client SDK Reference
- Troubleshooting
Overview
Cloud Live is an easy-to-use livestreaming service that provides diverse live acceleration capabilities for entertainment, e-commerce, and education scenarios.
It includes the following subservices:
- Cloud Stream Live improves the stability and efficiency of high-concurrency livestreaming and provides powerful real-time media processing capabilities.
- Low Latency Live (LLL), which is built on cutting-edge technologies such as transmission protocol optimization, dynamic routing, and low-latency transcoding, slashes live latency to milliseconds in latency-sensitive scenarios and delivers an unrivaled experience even when there are a massive number of concurrent requests.
Service Architecture (for Cloud Stream Live)
Process of livestreaming:
- A streaming tool is used to push a livestream to an origin server with uplink acceleration enabled.
- The origin server transcodes the livestream in real time.
- The processed livestream is distributed to viewers with downlink acceleration enabled.
- Live records the livestream to Object Storage Service (OBS).
Service Architecture (for LLL)
Features
Global acceleration
2,800+ nodes are deployed worldwide and provide a bandwidth reserve of more than 100 Tbit/s.
Ultimate experience
Supports tens of millions of concurrent requests. Huawei-developed congestion control algorithm and intelligent scheduling policy secure ultra-HD and smooth livestreaming, with a frame freezing rate lower than 1%. Low-bitrate HD transcoding is more suitable to human eyes-based subjective rate-distortion decision model and reduces the bitrate by 30% to 40% whereas the video subjective quality does not deteriorate.
High stability & reliability
Provides multi-center and cross-region cluster disaster recovery and 24/7 service support. The livestreaming architecture is built on Huawei's 20 years of Cloud Native 2.0 experience. It is an agile and intelligent architecture that combines enhanced security and reliability with fast scaling to safeguard your livestreaming.
Statistical analysis
Provides statistics about livestreaming, value-added services, and stream playback profiles. All access logs can be downloaded, facilitating service analysis and service development.
Demo
A multi-terminal demo is provided for you to try out LLL.
To obtain the app demo and source code, contact Huawei Cloud technical engineers by submitting a service ticket.
Pricing
By default, the fee is charged by downlink playback traffic. Currently, you can pay by traffic, daily peak bandwidth, or 95th percentile bandwidth. For details, see Billing.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
