tencent cloud

masukan

Resource Pack Overview

Terakhir diperbarui:2024-04-24 11:19:37

    Overview

    Resource packages (prepaid) are discounted packages offered by COS for different billable items. You can purchase different resource packages for deduction of the usage of billable items such as storage, requests, and traffic. Compared with pay-as-you-go billing, resource packages are cheaper and available only in public cloud regions (not in finance cloud regions), and you can choose to purchase them on your own.
    This document describes resource packages (prepaid). A resource package consists of one or multiple billable items. Compared with pay-as-you-go billing, resource packages are cheaper. Currently, available types of resource packages cover most billable items of COS, and you can purchase them based on your business needs.

    Pricing

    For the pricing details of resource packages, see Pricing | Cloud Object Storage.

    Purchase Entrance

    You can purchase the resource package you need on the resource pack purchase page.

    Purchase Notes

    1. Resource packages are available only in public cloud regions, not in finance cloud regions. For more information on regions, see Regions and Access Endpoints.
    2. Resource packs can only be used to deduct resource costs generated by storage buckets in the same general region (such as a public cloud region in the Chinese mainland, not a finance cloud region). Therefore, be sure to select a resource pack in the same region as your bucket.
    3. Resource packs are prepaid and can be configured to take effect immediately or at a specified time based on your actual use case. If a resource pack is configured to take effect immediately, it will take effect immediately on the day of purchase without any operation required. If a resource pack is configured to take effect at a specified time, it will take effect at the specified time, and your usage will be billed on a pay-as-you-go model before the resource pack takes effect.
    4. For resource packages purchased or renewed before December 1, 2021, the period of one month is calculated as 30 days. For resource packages purchased or renewed on or after December 1, 2021, the period of one month is calculated from the effective date and will expire on the same day of the following month. Special cases are described as follows:
    If a resource package takes effect on the last day of the current month, it will expire on the last day of the target month.
    If the effective date of the resource pack exceeds the total number of days in the target month, it will expire on the last day of the target month.. For example, if a resource package with 1-month period takes effect on January 30, it will expire on February 28 or 29.
    5. Resource packs can be purchased for multiple cycles, and in such cases, the resource pack resetting date will be applicable. For more information, see Validity Period.
    6. The unused portion of a resource package in a cycle does not carry over to the next cycle.
    7. A self-service refund is supported for resource packs. If you purchase an inappropriate resource pack by mistake, you can request a self-service refund refund if the refund conditions are met.
    8. Multiple resource packs can be used together. If you purchase multiple resource packs at a time, their specifications can be combined, but their validity periods will not. For more information on the validity period, see Validity Period.
    9. After a resource package expires or is used up, you don't need to migrate the data in your bucket, and pay-as-you-go billing will be adopted.
    10. While a resource package is effective, bills will be settled in the following sequence: free tier > resource package > pay-as-you-go. Usage beyond the free tier and the resource package's quota will be billed using the pay-as-you-go model.
    11. If an account has overdue payments (the account's balance is below 0), COS service will be suspended after 24 hours, regardless of whether the resource package is still effective.
    12. Currently, resource packages are available only for certain billable items (such as storage and requests). During the use of COS, other fees (such as data retrieval fees and management feature fees) may be incurred and will be charged based on your actual usage.
    Note:
    1. Storage capacity and resource packs are billed in GB units, with a conversion factor of 1,024. For example, 1 TB of STANDARD storage usage equals 1,024 GB, and a 1 TB STANDARD storage package can be used to deduct 1,024 GB of STANDARD storage usage.
    2. The traffic billable item and traffic packages are billed in GB units, with a conversion factor of 1,000. For example, 1 TB of public network downstream traffic equals 1,000 GB, and a 1 TB public network downstream traffic package can be used to deduct 1,000 GB of public network downstream traffic.
    3. The billing unit for read and write requests, as well as request packages, is 10,000 requests, with each request representing 10,000 units. For example, 10,000 STANDARD storage write requests are equivalent to 10,000 requests. A package of 100,000 STANDARD storage requests would be converted to 100,000 STANDARD storage requests.

    Applicable Regions

    Resource packages are classified into resource packages for regions in the Chinese mainland and resource packages for regions outside the Chinese mainland by region.
    Resource packages for regions in the Chinese mainland are available in public cloud regions in the Chinese mainland, not in finance cloud regions.
    Resource packages for regions outside the Chinese mainland apply to regions outside the Chinese mainland.

    Types and Deduction Rules

    The resource packages are classified by type in the following table:
    Note: For more information on the billable items described in the table, see Billable Items.
    When a resource package is used up or expires, the billing mode will be automatically switched to pay-as-you-go billing. To avoid incurring additional fees, we recommend that you promptly upgrade or renew the resource package.
    Resource Package Type
    Resource Package Description
    Resource Package Deduction Rules
    Storage package
    The following types of storage packages are available:
    STANDARD storage package: Applies to deduction of STANDARD storage usage, not MAZ_STANDARD storage usage.
    STANDARD_IA storage package: Applies to deduction of STANDARD_IA storage usage, not MAZ_STANDARD_IA storage usage.
    The average storage usage of the day is deducted every day, and the quota is reset every day.
    For example, if you purchased a STANDARD storage package of 20 GB on the 1st day of the month, and your bucket used 10 GB, 20 GB, and 30 GB of STANDARD storage on the 1st, 2nd, and 3rd day respectively, then 10 GB, 20 GB, and 20 GB could be deducted from the storage package of 20 GB on the 1st, 2nd, and 3rd day respectively, and the excess usage of 10 GB on the 3rd day would be billed on a pay-as-you-go model.
    Request package
    The following types of request packages are available:
    STANDARD request package: Applies to deduction of STANDARD read/write requests.
    STANDARD_IA request package: Applies to deduction of STANDARD_IA read/write requests.
    The total number of requests of the day is deducted every day, and the quota is reset every month.
    For example, if you purchased a STANDARD request package of 1,000,000 requests on the 1st day of the month, and your bucket generated 100,000 requests every day from the 1st day to the 3rd day, then 100,000 requests would be deducted from the request package every day from the 1st day to the 3rd day, and there would still be 700,000 requests available on the 4th day.
    Public network downstream traffic package
    Applies to deduction of public network downstream traffic
    The total amount of traffic of the day is deducted every day, and the quota is reset every month.
    For example, if you purchased a public network downstream traffic package of 100 GB on the 1st day of the month, and your bucket generated 10 GB of public network downstream traffic every day from the 1st day to the 3rd day, then 10 GB of traffic would be deducted from the traffic package every day from the 1st day to the 3rd day, and there would still be 70 GB of traffic available on the 4th day.
    Global acceleration traffic package
    Applies to deduction of global acceleration traffic. Global acceleration traffic packages are divided into the following categories according to the data transfer acceleration direction:
    For regions in the Chinese mainland: Applies to deduction of global acceleration traffic (upstream and downstream) generated by transfer between regions in the Chinese mainland, not finance cloud regions.
    For regions outside the Chinese mainland: Applies to global acceleration traffic (upstream and downstream) generated by transfer between regions in the Chinese mainland and outside the Chinese mainland or between regions outside the Chinese mainland.
    The total amount of traffic of the day is deducted every day, and the quota is reset every month.
    For example, if you purchased a global acceleration traffic package of 100 GB, and your bucket generated 10 GB of global acceleration traffic every day from the 1st day to the 3rd day, then 10 GB of traffic would be deducted from the traffic package every day from the 1st day to the 3rd day, and there would still be 70 GB of traffic available for deduction on the 4th day.
    

    Specifications

    Different types of resource packages have different specifications. For more information, see Resource Package Purchase Page.

    Validity Period Options

    COS resource packages have eight validity period options: 1 month, 3 months, 6 months, 1 year, 2 years, 3 years, 4 years, and 5 years.

    Validity Period

    Important note

    Note:
    The validity period of COS resource packages is adjusted as follows:
    For resource packages purchased or renewed before December 1, 2021, the validity period of one month is calculated as 30 days. For your benefits, such resource packages support renewal, and the renewal period is calculated according to the new validity period policy.
    For resource packages purchased or renewed after December 1, 2021, the validity period of one month is calculated from the effective date and will expire on the same day of the following month. Special cases are described as follows:
    If a resource package takes effect on the last day of the current month, it will expire on the last day of the target month.
    If the effective date of the resource pack exceeds the total number of days in the target month, it will expire on the last day of the target month.. For example, if a resource package with 1-month period takes effect on January 30, it will expire on February 28 or 29. For more information, see the validity period calculation logic below.
    Since March 7, 2022, the operation of extending a COS resource package has been renamed as a renewal operation.
    

    Definition

    1. Validity period: A period of time from the effective time to the expiration time of a resource package.
    2. Reset date: The date on which the quota of a resource package is reset, after which you will get the same amount of usage as the quota.
    Storage pack: The usage of a resource pack is reset every day during its validity period. The resetting date is subject to the validity period, not the purchase date.
    Read/Write request pack and traffic pack: The usage of a resource pack is reset every cycle during its validity period. The resetting date is subject to the validity period, not the purchase date. If you purchase a resource pack with a validity period of three months, and one month is a cycle by default, then the resource pack has two resetting dates.
    3. Cycle: The validity period of a resource package is divided into several cycles, and one month is a cycle by default. If you purchase a resource pack with a validity period of three months, the resource pack has three cycles.
    Viewing how many cycles a resource package has: In the COS console, select Resource Packages > Purchased > Operation and click Usage details to view the cycles of the resource package as well as its usage details in the current and historical cycles.
    Viewing the resetting date of a resource pack: In the COS console, select Resource Packages > Purchased > Usage description to view the resetting date of the resource pack.
    For example:
    1. If you purchased a STANDARD storage package of 10 GB with a 1-month period on December 1, 2021, then:
    Validity period: From 00:00:00 on December 1, 2021 to 23:59:59 on January 1, 2022.
    Resetting date: The resource package will be reset to 10 GB every day during its validity period, that is, 10 GB of STANDARD storage usage can be deducted every day.
    Cycle: The resource package has only one cycle, i.e., from December 1, 2021 to January 1, 2022.
    2. If you purchased a public network downstream traffic package of 10 GB with a 3-month period on December 1, 2021, then:
    Validity period: From 00:00:00 on December 1, 2021 to 23:59:59 on March 1, 2022.
    Resetting date: The resource package has two reset dates, that is, 24:00:00 on January 1, 2022 (i.e., 00:00:00 on January 2, 2022) and 24:00:00 on February 1, 2022 (i.e., 00:00:00 on February 2, 2022). You can get 10 GB of public network downstream traffic on each reset date for deduction of the public network downstream traffic generated in the current cycle.
    Cycle: The resource package has three cycles: From December 1, 2021 to January 1, 2022, from January 2, 2022 to February 1, 2022, and from February 2, 2022 to March 1, 2022.

    Calculation logic

    Validity period and reset date of a purchased resource package

    Note: If you purchased a traffic package or read/write request package with a period of N month(s) on a day (B) in a month (A), then the resource package would expire on the same day (B) in the month (A+N) and be reset at 24:00:00 on the same day (B) every month, and have (N-1) reset dates and N cycles.
    Logic:
    1. If the resource package takes effect on the last day of the current month, it will expire on the last day of the target month.
    2. If the effective date of the resource pack exceeds the total number of days in the target month, it will expire on the last day of the target month. For example, if a resource package with 1-month period takes effect on January 30, it will expire on February 28 or 29. For more information, see the validity period calculation logic below.
    Examples:
    Resource Package Type
    Operations
    Validity Period
    Purchase Date
    Effective Time
    Expiration Time
    Reset Time
    Public network downstream traffic package
    Purchase
    1 month
    December 1, 2021
    00:00:00 on December 1, 2021
    23:59:59 on January 1, 2022
    -
    Public network downstream traffic package
    Purchase
    2 months
    December 1, 2021
    00:00:00 on December 1, 2021
    23:59:59 on February 1, 2022
    24:00:00 on January 1, 2022
    Public network downstream traffic package
    Purchase
    3 months
    December 1, 2021
    00:00:00 on December 1, 2021
    23:59:59 on March 1, 2022
    24:00:00 on January 1, 2022 and 24:00:00 on February 1, 2022
    Public network downstream traffic package
    Purchase
    1 month
    December 15, 2021
    00:00:00 on December 15, 2021
    23:59:59 on January 15, 2022
    -
    Public network downstream traffic package
    Purchase
    2 months
    December 15, 2021
    00:00:00 on December 15, 2021
    23:59:59 on February 15, 2022
    24:00:00 on January 15, 2022
    Public network downstream traffic package
    Purchase
    3 months
    December 15, 2021
    00:00:00 on December 15, 2021
    23:59:59 on March 15, 2022
    24:00:00 on January 15, 2022 and 24:00:00 on February 15, 2022
    Public network downstream traffic package
    Purchase
    1 month
    December 29, 2021
    00:00:00 on December 29, 2021
    23:59:59 on January 29, 2022
    -
    Public network downstream traffic package
    Purchase
    2 months
    December 29, 2021
    00:00:00 on December 29, 2021
    23:59:59 on February 28, 2022
    24:00:00 on January 29, 2022
    Public network downstream traffic package
    Purchase
    3 months
    December 29, 2021
    00:00:00 on December 29, 2021
    23:59:59 on March 29, 2022
    24:00:00 on January 29, 2022 and 24:00:00 on February 28, 2022
    

    Validity period of a renewed resource package: the same as a purchased resource package

    Note: If you purchased a traffic package or read/write request package with a period of N month(s) on a day (B) in a month (A) and renewed it for M month(s), the resource package would expire on the same day (B) in the month (A+N+M) and be reset at 24:00:00 on the same day (B) every month, and have (N+M-1) reset dates and (N+M) cycles.
    Logic:
    1. If the resource package takes effect on the last day of the current month, it will expire on the last day of the target month.
    2. If the effective date of the resource pack exceeds the total number of days in the target month, it will expire on the last day of the target month. For example, if a resource package with 1-month period takes effect on January 30, it will expire on February 28 or 29. For more information, see the validity period calculation logic below.
    Examples:
    Resource Package Type
    Operation
    Validity Period
    Purchase Date
    Effective Time
    Expiration Time Before Renewal
    Renewal Period
    Expiration Time After Renewal
    Reset Time
    Public network downstream traffic package
    Purchase and renewal before expiration
    1 month
    December 1, 2021
    00:00:00 on December 1, 2021
    23:59:59 on January 1, 2022
    1 month
    23:59:59 on February 1, 2022
    24:00:00 on January 1, 2022
    Public network downstream traffic package
    Purchase and renewal before expiration
    1 month
    December 1, 2021
    00:00:00 on December 1, 2021
    23:59:59 on January 1, 2022
    2 months
    23:59:59 on March 1, 2022
    24:00:00 on January 1, 2022 and 24:00:00 on February 1, 2022
    Public network downstream traffic package
    Purchase and renewal before expiration
    1 month
    December 15, 2021
    00:00:00 on December 15, 2021
    23:59:59 on January 15, 2022
    1 month
    23:59:59 on February 15, 2022
    24:00:00 on January 15, 2022
    Public network downstream traffic package
    Purchase and renewal before expiration
    1 month
    December 15, 2021
    00:00:00 on December 15, 2021
    23:59:59 on January 15, 2022
    2 months
    23:59:59 on March 15, 2022
    24:00:00 on January 15, 2022 and 24:00:00 on February 15, 2022
    Public network downstream traffic package
    Purchase and renewal before expiration
    1 month
    December 29, 2021
    00:00:00 on December 29, 2021
    23:59:59 on January 29, 2022
    1 month
    23:59:59 on February 28, 2022
    24:00:00 on January 29, 2022
    Public network downstream traffic package
    Purchase and renewal before expiration
    1 month
    December 29, 2021
    00:00:00 on December 29, 2021
    23:59:59 on January 29, 2022
    2 months
    23:59:59 on March 29, 2022
    24:00:00 on January 29, 2022 and 24:00:00 on February 28, 2022
    

    Examples

    Deduction example

    Assume that you purchased two STANDARD storage packages of 200 GB for regions in the Chinese mainland with a period of three months and two public network downstream traffic packages of 200 GB for regions in the Chinese mainland with a period of three months on January 15, 2019, then:
    Resource Package Type
    Deduction Description
    Validity Period
    Two STANDARD storage packages
    Within the validity period, they could be applied to deduction of 400 GB of STANDARD storage used by buckets in public cloud regions in the Chinese mainland (not finance cloud regions).
    January 15, 2019 to April 14, 2019
    Two public network downstream traffic packages
    Every month (30 days), they could be applied to deduction of 400 GB of public network downstream traffic generated by buckets in public cloud regions in the Chinese mainland (not finance cloud regions).
    January 15, 2019 to April 14, 2019
    

    Deduction order example

    Assume that you purchased a STANDARD storage package of 500 GB for regions in the Chinese mainland, and the resource package was within the validity period. The following describes the deduction order of resource packages in different use cases:
    Use case involving different unit prices
    If 700 GB of STANDARD storage data is uploaded to the Guangzhou bucket and 300 GB of STANDARD storage data is uploaded to the Chengdu bucket on the same day, then in line with the principle of higher unit price, first deduct, the STANDARD storage package of 500 GB would be first applied to deduction of the STANDARD storage used by the bucket in Guangzhou.
    Use case involving the same unit price
    If 700 GB of STANDARD storage data is uploaded to the ‌Guangzhou‌ bucket and 300 GB of STANDARD storage data is uploaded to the ‌Beijing bucket on the same day, then the STANDARD storage package of 500 GB would be applied to deduction in the following order: Shanghai > Guangzhou > Beijing-1 > Singapore > Chengdu > Hong Kong (China) > Toronto > Frankfurt > Beijing > Seoul > Mumbai > Virginia > Silicon Valley > Bangkok > Tokyo > Nanjing > Jakarta > São Paulo > Chongqing.

    Examples of deduction items and regions

    Assume that you purchased a STANDARD storage package of 200 GB for regions in the Chinese mainland with a period of three months on January 15, 2019.
    If, from January 15 to January 31, your bucket in Guangzhou region used 100 GB of STANDARD storage, 50 GB of STANDARD_IA storage, and 1 million read/write requests and downloaded 10 GB of data over the public network, and your bucket in Singapore region used 50 GB of STANDARD storage, then:
    Generated Billable Item
    Whether the Resource Pack is Effective
    100 GB of STANDARD storage usage in Guangzhou region
    Yes. The resource pack would be applied to deduction of 100 GB of STANDARD storage usage every day during the validity period.
    50 GB of STANDARD_IA storage usage in Guangzhou region
    No. The resource pack could not be applied to deduction of STANDARD_IA storage usage, which would be billed on a pay-as-you-go basis.
    1 million read/write requests in Guangzhou region
    No. The resource pack could not be applied to deduction of read/write requests, which would be billed on a pay-as-you-go basis.
    10 GB of public network downstream traffic in Guangzhou region
    No. The resource pack could not be applied to deduction of public network downstream traffic, which would be billed on a pay-as-you-go basis.
    50 GB of STANDARD storage usage in Singapore region
    No. The resource pack could not be applied to deduction of your usage in Singapore region, which would be billed on a pay-as-you-go basis.
    Note:
    For more information on COS fee calculation and billing in different scenarios, see Billing Examples.
    

    Purchase/Renewal/Upgrade/Refund

    For detailed directions, see the following documents: Purchasing a Resource Pack

    FAQs

    If you have any questions about the billing of resource packages, see Billing.
    Hubungi Kami

    Hubungi tim penjualan atau penasihat bisnis kami untuk membantu bisnis Anda.

    Dukungan Teknis

    Buka tiket jika Anda mencari bantuan lebih lanjut. Tiket kami tersedia 7x24.

    Dukungan Telepon 7x24