- Release Notes and Announcements
- Product Introduction
- Purchase Guide
- Description of 14-day Trial Plan Experience Benefits
- Billing Overview
- Basic Service Fees
- Value-added Service Fees
- Related Tencent Cloud Services
- Extra Package Description (Prepaid)
- Subscriptions
- Renewals
- Overdue and Expiration Policies
- Refund Policy
- Usage Cap Policy
- EdgeOne Plan Upgrade Guide
- Comparison of EdgeOne Plans
- Billing Usage
- About "clean traffic" billing instructions
- Getting Started
- Domain Service
- Site Acceleration
- Origin Configuration
- Edge Functions
- Overview
- Getting Started
- Operation Guide
- Runtime APIs
- Sample Functions
- Example Overview
- 301 Redirect
- Obtaining Client URL Information
- Customization Based on Client Geo Location
- Obtaining Client Geo Location Information
- Batch Redirect
- Returning an HTML Page
- Returning a JSON Object
- Fetch Remote Resources
- Authenticating a Request Header
- Modifying a Response Header
- Performing an A/B Test
- Setting Cookies
- Performing Redirect Based on the Request Location
- Using the Cache API
- Caching POST Requests
- Responding in Streaming Mode
- Merging Resources and Responding in Streaming Mode
- Protecting Data from Tampering
- Rewriting a m3u8 File and Configuring Authentication
- Adaptive Image Resize
- Image Adaptive WebP
- Customize Referer restriction rules
- Remote Authentication
- HMAC Digital Signature
- Naming a Downloaded File
- Obtaining Client IP Address
- Practical Tutorial
- Security Protection
- Overview
- DDoS Protection
- DDoS Protection Overview
- Exclusive DDoS Protection Usage
- Configuration of Exclusive DDoS protection Rules
- Web Protection
- Rules Template
- IP Groups
- Origin Protection
- Custom Response Page
- Alarm Notification
- Rule Engine
- L4 Proxy
- Data Analysis&Log Service
- Tool Guide
- Practical Tutorial
- Configuring EdgeOne Security Event Alarms via TCOP
- EdgeOne Resource Abuse Prevention
- EdgeOne Implementation of Session Persistence Based on Client IP Addresses
- EdgeOne Implementation of Origin-Pull Based on Client's Geo Location
- EdgeOne Hotlink Protection Practical Tutorial
- EdgeOne initiates Automatic Warm-up
- EdgeOne Automatic Cache Purge
- Cross-regional Secure Acceleration (Oversea Sites)
- Scheduling Traffic to EdgeOne by Performing Canary Switching
- Quickly Enabling HTTPS Access with EdgeOne Free Certificate
- Through traffic orchestration to multiple service providers
- EdgeOne facilitate APKs.s dynamic packaging of Android
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- Site APIs
- Acceleration Domain Management APIs
- Site Acceleration Configuration APIs
- Edge Function APIs
- Alias Domain APIs
- Security Configuration APIs
- Layer 4 Application Proxy APIs
- CreateL4Proxy
- ModifyL4Proxy
- ModifyL4ProxyStatus
- DescribeL4Proxy
- DeleteL4Proxy
- CreateL4ProxyRules
- ModifyL4ProxyRules
- ModifyL4ProxyRulesStatus
- DescribeL4ProxyRules
- DeleteL4ProxyRules
- CreateApplicationProxy
- ModifyApplicationProxy
- ModifyApplicationProxyStatus
- DescribeApplicationProxies
- DeleteApplicationProxy
- CreateApplicationProxyRule
- ModifyApplicationProxyRule
- ModifyApplicationProxyRuleStatus
- DeleteApplicationProxyRule
- Content Management APIs
- Data Analysis APIs
- Log Service APIs
- Billing APIs
- Certificate APIs
- Load Balancing APIs
- Diagnostic Tool APIs
- Custom Response Page APIs
- Version Management APIs
- Data Types
- Error Codes
- FAQs
- Agreements
- TEO Policy
- Contact Us
- Glossary
- Release Notes and Announcements
- Product Introduction
- Purchase Guide
- Description of 14-day Trial Plan Experience Benefits
- Billing Overview
- Basic Service Fees
- Value-added Service Fees
- Related Tencent Cloud Services
- Extra Package Description (Prepaid)
- Subscriptions
- Renewals
- Overdue and Expiration Policies
- Refund Policy
- Usage Cap Policy
- EdgeOne Plan Upgrade Guide
- Comparison of EdgeOne Plans
- Billing Usage
- About "clean traffic" billing instructions
- Getting Started
- Domain Service
- Site Acceleration
- Origin Configuration
- Edge Functions
- Overview
- Getting Started
- Operation Guide
- Runtime APIs
- Sample Functions
- Example Overview
- 301 Redirect
- Obtaining Client URL Information
- Customization Based on Client Geo Location
- Obtaining Client Geo Location Information
- Batch Redirect
- Returning an HTML Page
- Returning a JSON Object
- Fetch Remote Resources
- Authenticating a Request Header
- Modifying a Response Header
- Performing an A/B Test
- Setting Cookies
- Performing Redirect Based on the Request Location
- Using the Cache API
- Caching POST Requests
- Responding in Streaming Mode
- Merging Resources and Responding in Streaming Mode
- Protecting Data from Tampering
- Rewriting a m3u8 File and Configuring Authentication
- Adaptive Image Resize
- Image Adaptive WebP
- Customize Referer restriction rules
- Remote Authentication
- HMAC Digital Signature
- Naming a Downloaded File
- Obtaining Client IP Address
- Practical Tutorial
- Security Protection
- Overview
- DDoS Protection
- DDoS Protection Overview
- Exclusive DDoS Protection Usage
- Configuration of Exclusive DDoS protection Rules
- Web Protection
- Rules Template
- IP Groups
- Origin Protection
- Custom Response Page
- Alarm Notification
- Rule Engine
- L4 Proxy
- Data Analysis&Log Service
- Tool Guide
- Practical Tutorial
- Configuring EdgeOne Security Event Alarms via TCOP
- EdgeOne Resource Abuse Prevention
- EdgeOne Implementation of Session Persistence Based on Client IP Addresses
- EdgeOne Implementation of Origin-Pull Based on Client's Geo Location
- EdgeOne Hotlink Protection Practical Tutorial
- EdgeOne initiates Automatic Warm-up
- EdgeOne Automatic Cache Purge
- Cross-regional Secure Acceleration (Oversea Sites)
- Scheduling Traffic to EdgeOne by Performing Canary Switching
- Quickly Enabling HTTPS Access with EdgeOne Free Certificate
- Through traffic orchestration to multiple service providers
- EdgeOne facilitate APKs.s dynamic packaging of Android
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- Site APIs
- Acceleration Domain Management APIs
- Site Acceleration Configuration APIs
- Edge Function APIs
- Alias Domain APIs
- Security Configuration APIs
- Layer 4 Application Proxy APIs
- CreateL4Proxy
- ModifyL4Proxy
- ModifyL4ProxyStatus
- DescribeL4Proxy
- DeleteL4Proxy
- CreateL4ProxyRules
- ModifyL4ProxyRules
- ModifyL4ProxyRulesStatus
- DescribeL4ProxyRules
- DeleteL4ProxyRules
- CreateApplicationProxy
- ModifyApplicationProxy
- ModifyApplicationProxyStatus
- DescribeApplicationProxies
- DeleteApplicationProxy
- CreateApplicationProxyRule
- ModifyApplicationProxyRule
- ModifyApplicationProxyRuleStatus
- DeleteApplicationProxyRule
- Content Management APIs
- Data Analysis APIs
- Log Service APIs
- Billing APIs
- Certificate APIs
- Load Balancing APIs
- Diagnostic Tool APIs
- Custom Response Page APIs
- Version Management APIs
- Data Types
- Error Codes
- FAQs
- Agreements
- TEO Policy
- Contact Us
- Glossary
Extra Package Description
EdgeOne extra packages are divided into security acceleration traffic packages, security acceleration request packages, and Value-Added Service Usage Unit (VAU) packages, which can be used to deduct overage fees outside the plan. Compared to the pay-as-you-go method, the unit price of EdgeOne extra packages is more favorable. You can choose to buy suitable extra packages according to the actual business consumption.
Note：
1. Please make sure you have purchased the EdgeOne plan. After purchasing the plan, the extra package can be effective.
2. Extra packages are only applicable to the deduction of usage generated by prepaid personal edition/basic/standard plan, and not applicable to the deduction of usage generated by enterprise plan.
3. Security acceleration traffic packages are only used to deduct L7 (Application layer) traffic and are not applicable to deduct L4 (Transport layer) traffic and exclusive DDoS protection traffic.
4. Security acceleration request packages are only used to deduct HTTP/HTTPS requests and are not applicable to deduct smart acceleration requests, QUIC requests, and other request fees.
5. VAU packages are only used to deduct the usage-based VAU fee (pay-as-you-go). They are applicable to the deduction of the consumption generated by smart acceleration, QUIC requests, and BOT requests, but are not applicable to the deduction of the precise matching policy quotas in custom rules, rate limiting rule quotas, site quotas, and L4 acceleration instance quotas.
6. The priority of EdgeOne usage deduction is: In-package quota usage > Extra package usage > Closer expiration time of extra package > Smaller specs of extra package > Post-payment.
Billing Description
Payment method: Prepaid. Purchase first and then deduct.
Validity period: Valid within 1 year. For example, if purchased on July 9, 2023, 21:30:00, the valid time is from July 9, 2023, 21:30:00 to July 9, 2024, 21:29:59.
Deduction type: According to the deduction type, extra packages can be divided into two types:
Security acceleration traffic package: Used to deduct L7 (Application layer) traffic generated by EdgeOne.
Security acceleration request package: Used to deduct HTTP/HTTPS requests generated by EdgeOne.
VAU package: Used to deduct the VAU fee (pay-as-you-go) generated by EdgeOne.
Note：
1. Expiration description: After the extra package expires, it does not support extension, and the unconsumed traffic or requests will be automatically cleared and cannot be restored, and cannot be used continuously.
2. Notification reminder: A reminder will be sent when the extra package expires or is exhausted.
3. Excess post-payment: The service will not be automatically stopped after the extra package is exhausted or expired, and the usage beyond the extra package will be settled according to the corresponding post-payment price of the service.
4. Refund description: Unexpired and unused extra packages support refunds, and other situations do not support refunds. For details, please refer to the Refund Description.
Security Acceleration Traffic Package
The security acceleration traffic package is used to deduct L7 (Application layer) traffic generated by EdgeOne. The traffic package does not distinguish between countries and regions, and is deducted globally at different proportions:
Assuming that the customer actually consumes 1 GB in each billing region, different regions will deduct the in-package traffic separately according to the following proportions: | ||||||||
Chinese mainland CN | North America NA | Europe EU | Asia-Pacific 1 AP1 | Asia-Pacific 2 AP2 | Asia-Pacific 3 AP3 | Middle East ME | Africa AA | South America SA |
1 GB | 1.71 GB | 1.71 GB | 2.49 GB | 2.68 GB | 2.78 GB | 2.91 GB | 2.91 GB | 2.91 GB |
Note：
The billing region is divided according to the actual service user's client access to the EdgeOne node in the region, and the mapping relationship between the billing region and the country is detailed in the Billing Region.
Example description:
Security Acceleration Traffic Package Deduction Example
Assuming that the user purchases a 50 GB security acceleration traffic package on July 9, 2023, 00:00:00, and the in-package security acceleration traffic has been exhausted.
From 00:00:00 to 00:05:00 on July 9, 2023, 30 GB of traffic was generated in the Chinese mainland region, and the remaining usage of the security acceleration traffic package is 50 GB - 30 * 1 GB = 20 GB;
From 00:05:00 to 00:10:00 on July 9, 2023, 10 GB of traffic was generated in the North America region, and the remaining usage of the security acceleration traffic package is 20 GB - 10 * 1.71 GB = 2.9 GB;
From 00:10:00 to 00:15:00 on July 9, 2023, 1 GB of traffic was generated in the Europe region and Asia-Pacific 1 region, respectively. According to the deduction rule, the Europe region and Asia-Pacific 1 region should deduct 1.71 GB and 2.49 GB, respectively, with a total deduction of 4.2 GB. However, the remaining usage of the security acceleration traffic package is only 2.9 GB. At this time, the remaining usage of the security acceleration traffic package is allocated according to the deduction ratio:
The Europe region deducts the remaining usage of the security acceleration traffic package 2.9 * 1.71 / (1.71 + 2.49) = 1.18 GB, and the out-of-package excess traffic generated in the Europe region is (1.71 - 1.18) / 1.71 = 0.31 GB;
The Asia-Pacific 1 region deducts the remaining usage of the security acceleration traffic package 2.9 * 2.49 / (1.71 + 2.49) = 1.72 GB, and the out-of-package excess traffic generated in the Asia-Pacific 1 region is (2.49 - 1.72) / 2.49 = 0.31 GB.
Security Acceleration Traffic Package Price
The rate card price for a single purchase of a security traffic package is as follows:
Validity Period | Specification | List Price | Discounted Price |
12 months | 50 GB | $ 2.20 | $1.55 |
| 100 GB | $ 4.40 | $3.00 |
| 500 GB | $ 22.00 | $14.90 |
| 1 TB | $ 44.00 | $28.60 |
| 5 TB | $ 211.00 | $138.00 |
| 10 TB | $ 422.00 | $276.00 |
| 50 TB | $ 1,995.00 | $1,275.00 |
| 200 TB | $ 7,040.00 | $3,300.00 |
| 1 PB | $ 30,600.00 | $16,500.00 |
| 5 PB | $ 153,000.00 | $78,000.00 |
| 10 PB | $ 306,000.00 | $150,000.00 |
| 50 PB | $ 1,530,000.00 | $750,000.00 |
Security acceleration request package
Security acceleration request package is used to deduct the HTTP/HTTPS requests generated by EdgeOne Service. The request package does not distinguish between countries and regions, and is deducted globally at a 1:1 ratio.
Security acceleration request package price
The list price for a single purchase of a security request package is as follows:
Validity Period | Specification | List Price | Discounted Price |
12 months | 10 million times | $ 5.70 | $4.845 |
| 100 million times | $ 51.00 | $43.35 |
| 1 billion times | $ 457.00 | $388.45 |
| 10 billion times | $ 4,000.00 | $3,400.00 |
| 100 billion times | $ 28,571.00 | $24,285.35 |
Security acceleration request package deduction example
Assuming you purchased a security acceleration request package of 10 million times on July 9, 2023, 00:00:00, and the security acceleration requests in the package have been used up.
From 00:00:00 to 00:05:00 on July 9, 2023, 5 million requests were generated in the Chinese mainland region, and the remaining usage of the security acceleration request package is 10 million times - 5 million times = 5 million times;
From 00:05:00 to 00:10:00 on July 9, 2023, 3 million requests were generated in the North America region, and the remaining usage of the security acceleration request package is 5 million times - 3 million times = 2 million times;
From 00:10:00 to 00:15:00 on July 9, 2023, 3 million requests and 2 million requests were generated in the Europe region and Asia-Pacific 1 region, respectively. According to the deduction rule, a total of 5 million times need to be deducted, but the remaining usage of the security acceleration request package is only 2 million times. At this time, the remaining usage of the security acceleration request package is allocated according to the deduction ratio:
The Europe region deducts the remaining usage of the security acceleration request package by 200 * 300 / (300 + 200) = 1.2 million times, and the Europe region generates an excess of 3 million - 1.2 million = 1.8 million times outside the package;
The Asia-Pacific 1 region deducts the remaining usage of the security acceleration request package by 200 * 200 / (300 + 200) = 800,000 times, and the Asia-Pacific 1 region generates an excess of 2 million - 800,000 = 1.2 million times outside the package.
VAU Package
The VAU package is used to deduct the VAU fee (pay-as-you-go). The VAU package does not distinguish between countries and regions, and is deducted globally at a 1:1 ratio.
VAU Package Price
The list price for a single purchase of a VAU package is as follows:
Validity Period | Specification | List Price | Discounted Price |
12 months | 500 units | $ 7.15 | $4.845 |
| 2,500 units | $ 35.75 | $23.2375 |
| 5,000 units | $ 71.50 | $43.35 |
| 20,000 units | $ 286.00 | $171.60 |
| 50,000 units | $ 715.00 | $388.45 |
| 250,000 units | $ 3,575.00 | $1,787.50 |
| 500,000 units | $ 7,150.00 | $3,400.00 |
| 5,000,000 units | $ 71,500.00 | $24,285.35 |
VAU Package Deduction Example
Assume that you purchased a VAU package of 2,500 units at 00:00:00 on July 9, 2023.
From 00:00:00 to 00:05:00 on July 9, 2023, 40 million QUIC requests were generated in the Chinese mainland region. According to the settlement rules of the VAU Fee (Pay-as-You-Go), each 10,000 requests are converted to 100 units, so 2,000 units were consumed. The remaining usage of the VAU package is 2,500 units - 2,000 units = 500 units.
From 00:05:00 to 00:10:00 on July 9, 2023, 3 million smart acceleration requests were generated in the North America region. According to the settlement rules of the VAU Fee (Pay-as-You-Go), each 10,000 requests are converted to 100 unit, so 300 units were consumed. The remaining usage of the VAU package is 500 units - 300 units = 200 units.
From 00:10:00 to 00:15:00 on July 9, 2023, 3 million BOT requests and 200 million times of smart acceleration were respectively generated in the Europe region and Asia-Pacific 1 region. According to the settlement rules of the VAU Fee (Pay-as-You-Go), 300 units and 200 units were consumed respectively, but the remaining usage of the VAU package is only 200 units. At this time, the remaining usage of the VAU package is allocated according to the deduction ratio:
The remaining usage of the VAU package deducted for the Europe region is 200 * 300/(300 + 200) = 120 units, so the excess VAUs generated in the Europe region are 300 - 120 = 180 units.
The remaining usage of the VAU package deducted for the Asia-Pacific 1 region is 200 * 200/(300 + 200) = 80 units, so the excess VAUs generated in the Asia-Pacific 1 region are 200 - 80 = 120 units.
Extra package deduction description
Effective time
Deduction effective time: The effective time of the EdgeOne extra package is the integer moment 5 minutes before the purchase, and the expiration time is the effective time plus the validity of the extra package, which can only deduct the usage generated after the extra package takes effect.
Extra package effective time example
Assuming you generated 10 GB of traffic consumption between 13:05:00 and 13:10:00 on July 9, 2023, and 20 GB of traffic consumption between 13:10:00 and 13:15:00. You purchased a 100 GB security acceleration traffic package with a validity of 12 months at 13:13:07 on July 9, 2023. The effective time of the security acceleration traffic package is: July 9, 2023, 13:10:00, and the expiration time is July 9, 2024, 13:09:59, which can deduct the 20 GB usage generated between 13:10:00 and 13:15:00.
Deduction order
Deduction range: The purchased extra package can deduct the usage of all sites under the personal plan, basic plan, and standard plan of the current account using the EdgeOne Service.
1. Billing usage will be deducted first from the quota usage in the package, and the extra package usage will be deducted only after the package quota usage is exhausted.
2. The deduction order of EdgeOne usage is package quota usage > extra package usage > extra package with closer expiration time > extra package with smaller specs > postpaid.
3. Extra packages are deducted in order of expiration time from near to far. When the expiration time is the same, they are deducted according to the size of the specs, from small to large. When the expiration time and specs are the same, no further distinction is made.
Extra package deduction order example
Assuming you currently have 3 security acceleration traffic packages:
A: The specs are 1 TB, the effective time is July 8, 2023, 00:00:00, and the expiration time is July 7, 2024, 23:59:59;
B: The specs are 50 GB, the effective time is July 8, 2023, 00:00:00, and the expiration time is July 7, 2024, 23:59:59;
C: The specs are 100 GB, the effective time is July 6, 2023, 00:00:00, and the expiration time is July 5, 2024, 23:59:59.
The deduction priority of the three traffic packages is: C > B > A.
Yes
No
Was this page helpful?