Data is exchanged between the IoT Platform cloud and devices through message reporting and delivery. This topic describes the fees and billing details for message communication.
Background
The billing plan for message communication on IoT Platform is being upgraded. To ensure the average daily message volume per device does not exceed the platform's cost limits, fees will be charged for certain message communication scenarios.
Message communication billing
Billing for message communication is based on different scenarios. The following table describes the billable scenarios and billing methods.
Devices such as photovoltaic inverters, robotic vacuum cleaners, and gateway devices have special requirements for message quotas. To obtain a quote, contact the platform's business team by email at livinglink@service.alibaba.com.
Scenario | Description | Billable scenario |
Message reporting | All types of messages generated when a device reports data to the server-side, such as API calls and Thing Specification Language (TSL) model data reports. |
Important Billing example: Purchase a non-Bluetooth basic package that includes 100 messages. For more information about activation code specifications for different devices, see Activation code billing.
|
Message delivery | All types of messages generated when the server-side sends data to a device, such as device control instructions. | |
Server-side information | All types of messages generated when the server-side calls device-related APIs, such as TSL model APIs. |
Message package billing rules
Supplemental message packages cannot be purchased separately at this time.
Activation codes and message packages are used together. If the default message package included with an activation code expires or is no longer sufficient for your device, you can use a supplemental message package for additional resources. In addition to the primary message reporting quota, these packages can renew resources such as device connection services, message log storage service (7 days), device Over-the-Air (OTA) service, device control panel, scheduled and countdown timer services, SDK capabilities, and official app access, including ecosystem device filter interaction.
For a single product within a project, purchase value-added message packages based on the number of active devices. Message packages take effect immediately upon purchase and cannot be deactivated. Because they are virtual goods, message packages are non-returnable, non-exchangeable, or non-refundable.
Message package specification | Specification description | Fee |
100 messages/day/device package | Includes 100 messages. The package is valid for one year from the date of purchase. | CNY 1.50/device |
300 messages/day/device package | Includes 300 messages. The package is valid for one year from the date of purchase. | CNY 2.70/device |
500 messages/day/device package | Includes 500 messages. The package is valid for one year from the date of purchase. | CNY 3.75/device |
1,000 messages/day/device package | Includes 1,000 messages. The package is valid for one year from the date of purchase. | CNY 6.75/device |
2,000 messages/day/device package | Includes 2,000 messages. The package is valid for one year from the date of purchase. | CNY 12.00/device |
Message reporting specifications
You can use the SDK provided by the platform to develop a custom format for device message reporting. Ensure that your message reporting development follows the platform's specifications. For more information, see Device property settings and reporting specifications and On-demand device status reporting from devices.