Bypass stream pushing billing

更新时间:
复制 MD 格式

This topic describes the billing rules for bypass stream pushing.

Introduction

The bypass stream pushing service of ApsaraVideo Real-time Communication (RTC) mixes your real-time audio and video streams, converts them into a standard live stream, and pushes the stream to a specified CDN provider. By default, the service is billed based on the processing duration. The billable duration is the total processing time for the day, measured in minutes. When you use the bypass stream pushing service, Alibaba Cloud RTC calculates the total fees by summing the durations for each specification used on that day. For more information, see Bypass stream pushing.

Billing details

Bypass stream pushing fee = Unit price of the specification × Billable duration

  • Unit price of the specification: The specification is determined by the value of the TaskProfile parameter, which you set when you call the StartMPUTask operation to start a bypass stream pushing task. This value specifies the maximum number of streams that can be mixed and the output resolution for the task, regardless of whether the task pushes an audio or a video stream. For more information, see Pricing of ApsaraVideo Real-time Communication.
  • Billable duration: The billable duration begins when a bypass stream pushing task is started and ends when the task is stopped. The duration is measured in minutes. Durations are calculated in seconds and then rounded up to the next minute. If only one bypass stream pushing task is started in a channel, the billable duration for the channel is the total duration of that task. If multiple bypass stream pushing tasks are started in a channel at the same time, the billable duration is the sum of the durations of all tasks.
Note
  • The Alibaba Cloud RTC service generates and settles bills for the previous day at approximately 02:00 (UTC+8) each day. The actual time when a bill is generated may vary.
  • Real-Time Communication resource plans can be used to offset only communication fees, not bypass stream pushing fees.

Billing examples

The prices in the following examples are for reference only. For the actual prices, see Pricing of ApsaraVideo Real-time Communication.

  • Example 1:

    Two users join a channel for a voice call that lasts 2,100 seconds. A bypass stream pushing task is started at the same time as the call and is stopped when the call ends.

    Usage calculation:

    • One bypass stream pushing task is required to mix the two audio streams and push the mixed stream.
    • Because only audio is pushed, the bypass stream pushing specification (TaskProfile) is Mixed_Audio (audio-only).
    • The duration of the bypass stream pushing task is 2,100 seconds, which is 35 minutes.

    Fee calculation:

    Bypass stream pushing fee = Unit price of the specification (CNY 0.0500/minute) × Billable duration (35 minutes)

  • Example 2:

    Three users join a channel for an audio and video call that lasts 3,700 seconds. The video resolution is 360 × 640. A bypass stream pushing task is started at the same time as the call and is stopped when the call ends.

    Usage calculation:

    • One bypass stream pushing task is required to mix the three audio and video streams and push the mixed stream.
    • The task pushes video streams from three users (a maximum of three mixed streams) with an output resolution of 360p (360 × 640). Therefore, the bypass stream pushing specification (TaskProfile) is 4IN_360P. If a specification that exactly matches the number of mixed streams is not available, select a specification for a larger number of streams. For example, if the maximum number of mixed streams is 3, select the 4IN specification.
    • The duration of the bypass stream pushing task is 3,700 seconds, which is 62 minutes.

    Fee calculation:

    Bypass stream pushing fee = Unit price of the specification (CNY 0.1400/minute) × Billable duration (62 minutes)