This topic describes how requests and WebSocket are billed.
Billing of HTTPS and HTTP requests for dynamic content
Dynamic Route for CDN (DCDN) caches static content that is stored on your server to DCDN nodes. When users request the static content, they do not need to access the origin server. Instead, they can retrieve the requested content from the nearest DCDN nodes. This way, content delivery is accelerated and the load on the origin server is reduced.
Dynamic content refers to the content that is delivered on a per-request basis. The server delivers different contents for different requests. Dynamic content includes ASP, JSP, PHP, Perl and CGI files, API requests, and database interactive requests on websites.
Users must access your server each time they retrieve dynamic content. Your server dynamically generates the requested content and returns the content to the users. Alibaba Cloud Content Delivery (CDN) accelerates content delivery based on the caching mechanism. It cannot cache dynamic content or accelerate the delivery of dynamic content. When a CDN node receives a request for dynamic content, it forwards the request to the origin server without acceleration. To accelerate delivery of dynamic content, you can use DCDN.
A bill is issued at the end of each billing cycle. In most cases, a bill is issued about 3 hours after a billing cycle ends. The time when bills are issued is determined by the system. The amount due is then automatically deducted from your account balance.
In this example, the dynamic and static content on the origin server is requested for 100,000 times. DCDN identifies whether the requested content is static or dynamic each time it receives a request.
- If DCDN receives a request for dynamic content, it forwards the request to the origin server to retrieve the requested content. When DCDN returns the requested content to the user, you are charged based on the type of the request URL.
- If DCDN receives a request for static content and the requested content is cached on DCDN nodes, you are charged based on the type of the request URL. You are charged when DCDN returns the requested content to the user. Only HTTPS requests are charged.
If a total of 100,000 requests contain 10,000 HTTP requests for static content, 20,000 HTTPS requests for static content, 30,000 HTTP requests for dynamic content, and 40,000 HTTPS requests for dynamic content, the fee is calculated based on the following formula:
Fee = 2 × 0.05 + 3 × 0.15 +4 × 0.15 = CNY 1.15.
You can purchase subscription resource plans based on your business requirements. For more information, see Resource Plan.
Billing of QUIC requests
After you enable QUIC in the DCDN console, you are charged for QUIC requests that request static content.
Billing of WebSocket
Beginning January 8, 2021, the WebScoket feature uses the pay-by-data-transfer metering method by default. If you want to switch to the pay-by-daily-peak-bandwidth metering method, submit a ticket or contact your sales manager. Billable regions include regions inside mainland China and regions outside mainland China. For more information, see DCDN Pricing - Pay by WebSocket.
- A bill is issued at the end of each billing cycle.
- In most cases, a data transfer bill is issued within 3 hours after a billing cycle ends. The time when bills are issued is determined by the system. The amount due is then automatically deducted from your account balance.
- The bandwidth bill of the current day is issued after 00:00 (UTC+8) on the next day. The time when bills are issued is determined by the system. The amount due is then automatically deducted from your account. If you use the pay-by-traffic billing method, the bandwidth cap is 10 Gbit/s. To request a higher bandwidth value, submit a ticket.