Billing overview
This topic describes the billable items, billing methods, and pricing for IoT Internet Device ID.
Billing details
IoT Internet Device ID is available in two sales models on the public cloud:
Software-only: A software authorization that you can use immediately after you purchase it online.
Software and hardware bundle: A physical product that is shipped through our logistics service after you purchase it online.
Sales model | Deliverable type | Purchase method | Sales unit |
Software-only | Software authorization | Unit | |
Software and hardware bundle | Physical items (ID² security chips/security modules) | Package |
Model: NXP A71CL package (6,000 units per package).
The billing methods and pricing for different sales models are as follows:
Sales model | Applicable region | Billing method | Authorization validity period | Pricing |
Software-only | China (Shanghai) | Subscription | 1 year | CNY 1/device |
3 years | CNY 2.1/device | |||
5 years | CNY 3/device | |||
Software and hardware bundle | China (Shanghai) | Subscription | 5 years |
IoT Internet Device ID also supports offline deployments, such as on Apsara Stack, IoT security all-in-one machines, and bare metal servers. For more information and a quote, contact us.
Authorization consumption
The following scenarios consume ID² authorizations. To view authorization usage records, log on to the console and go to the System Administration > Authorization Details page.
Scenario | Triggering action | ID² authorizations consumed | Expiration date calculation |
New device | First use of an ID² service | 1 per device | Time of first successful authentication + ID² authorization validity period |
After an existing device's ID² expires | Calling the ID² authentication, encryption, or decryption service | 1 per device | Expiration date + ID² authorization validity period |
After a device's ID² expires, automatic renewal is triggered only if the device continues to use ID² services. If the device no longer uses ID² services, automatic renewal is not triggered.
When an automatic renewal is triggered, authorizations are consumed in a specific order. Authorizations allocated to the product are used first, followed by the authorizations under your account. The system prioritizes consuming authorizations with shorter validity periods first, in the order of 1-year, 3-year, and then 5-year.
On the System Administration > Authorization Details page, you can customize the Auto-renewal Policy. By default, auto-renewal is enabled for all products.
For example, if a device's ID² expires on June 10, 2023, and the device calls an ID² service again on July 10, 2023, an automatic renewal is triggered. This renewal consumes one 1-year ID² authorization, and the new expiration date for the device's ID² is set to June 10, 2024.