Resource package deduction rules
This topic explains when resource package deductions start, the order in which multiple resource packages are deducted, and the rules that limit what a package can cover.
Deduction time
A resource package takes effect immediately after you purchase it.
Deductions do not occur in real time. Each hourly billing period is deducted when its bill is generated, about three to four hours after the period ends. For example, you purchase a 1 TB outbound data transfer resource package for the Chinese mainland at 10:30:30 on August 12, 2024, with a validity period of one month. Deductions do not start until about 14:00:00, when the system generates the data transfer bill for the 10:00:00 to 11:00:00 period and deducts the data transfer consumed during that hour.
Deduction order
You can stack resource packages. If you hold several resource packages of the same type, they are deducted in the following order:
The resource package with the earliest expiration time is deducted first. For example, you purchase two outbound data transfer resource packages for the Chinese mainland that expire on July 1, 2024 and August 1, 2024. The package that expires on July 1, 2024 is deducted first.
If a resource package expires or its quota is used up, billing automatically switches to pay-as-you-go, and any excess usage is charged based on actual usage.
Scope of application
A resource package of a given type covers only the matching fees generated while you use DCDN. It does not cover every fee. For example, an outbound data transfer resource package covers outbound data transfer only. You cannot use it to cover other billable items, such as the number of
HTTPSrequests.Outbound data transfer resource packages: the package applies only when the billing method is Pay-by-data-transfer. The package is also limited by region, and packages bought for different acceleration regions cannot cover each other. For example, an outbound data transfer resource package for the Chinese mainland covers only outbound data transfer generated in the Chinese mainland. It does not cover outbound data transfer fees generated in China (Hong Kong), China (Macao), China (Taiwan), or other countries and regions.
WebSocket data transfer resource packages: the package applies only when the billing method is Pay-by-data-transfer. The package is also limited by region, and packages bought for different acceleration regions cannot cover each other. For example, a WebSocket data transfer resource package for the Chinese mainland covers only WebSocket outbound data transfer generated in the Chinese mainland. It does not cover WebSocket data transfer fees generated in China (Hong Kong), China (Macao), China (Taiwan), or other countries and regions.
IP application acceleration (
TCP/UDP) data transfer resource packages: the package applies only when the billing method is Pay-by-data-transfer, and it covers requests in the Chinese mainland only.