IoT Platform uses upstream and downstream messages to exchange information between the cloud and devices. This topic describes message throttling, the throttling exemption period, allocation rules, the alert mechanism, the effects of throttling, and how to avoid it.
Background
IoT Platform has commercially upgraded its message communication service. To ensure service quality and help you control daily message costs, the platform dynamically allocates the total number of available messages for a product each day based on the number of active devices from the previous day. The platform also counts the total number of messages reported by the product on the current day. If the number of reported messages exceeds the number of available messages, the platform throttles messages for that product. This can prevent devices from reporting messages normally.
Total available messages for a product
The total number of available messages for a product on the IoT Platform comes from two sources:
Activation code messages
When you purchase activation codes for standard devices (non-video devices), each code includes a quota of 100 upstream messages per device per day. This quota becomes effective 90 days after the product enters mass production and is valid for three years. The platform dynamically allocates the total available messages for the product based on the number of active devices from the previous day. The total number of available messages for the current day is not a static field. Inactive devices do not contribute to the total number of available messages.
Purchasing message packages
Billing for message communication is based on different scenarios. Message packages are valid for one year from the date of purchase. For more information about message package specifications and billing rules, see Message communication billing.
If all devices for a product are active in a single region, the total number of available messages is allocated entirely to that region. If the devices are active in multiple regions, such as China, Germany, Singapore, and US East, the total available messages are distributed according to regional allocation rules. This creates a separate total of available messages for each region.
Total messages actually reported by a product
The total number of messages reported by a product on the IoT Platform is the sum of all messages sent to the cloud by all devices for that product. The platform counts this total daily from 00:00:00 to 23:59:59. The count resets at 00:00:00 the next day.
Message throttling explained
IoT Platform throttles upstream messages from devices if the total number of reported messages for a product exceeds the total available messages, or if the total reported messages in a region exceed the available messages for that region. To avoid the impact of immediate throttling, the platform provides a 48-hour processing time. During this period, you can purchase a message package to increase the number of available messages. This prevents throttling from stopping devices from reporting messages.
Example 1: Product 01 has all its devices active in the China region.
On August 1, 2024, the total number of reported messages (10,500) exceeds the total available messages (10,000).
In the early morning of August 2, 2024, the platform notifies you by email that the message quota has been exceeded. It also provides a 48-hour processing time (from August 2 to August 3, 2024). During this 48-hour period, you can purchase a message package to increase the total available messages. This prevents the platform from throttling device messages after the 48-hour processing time.
Example 2: Product 02 has devices active in the China, Germany, and Singapore regions.
On August 1, 2024, the number of reported messages in the Germany and Singapore regions does not exceed their available message quotas. However, the number of reported messages in the China region (20,050) exceeds its available message quota (20,000).
In the early morning of August 2, 2024, the platform notifies you by email that the message quota for the China region has been exceeded. It also provides a 48-hour processing time (from August 2 to August 3, 2024). During this 48-hour period, you can purchase a message package to increase the total available messages. This prevents the platform from throttling devices in the China region after the 48-hour processing time. The Germany and Singapore regions have not exceeded their quotas. If they exceed their quotas later, the platform will also provide a 48-hour processing time for those regions.
Throttling exemption period
To facilitate factory testing of devices, the platform does not throttle messages during the testing phase before a product enters mass production.
Regional quota allocation rules
By default, the platform allocates the total available messages for a region based on the percentage of active devices in that region.
You can customize the percentage of available messages allocated to each region. After you switch to custom percentage allocation, you cannot revert to the default allocation rule. You should monitor the number of reported messages and active devices in each region. This helps you adjust the custom percentages promptly to ensure a reasonable allocation. For more information, see View device messages.
Message throttling alerts
IoT Platform provides a message throttling alert feature. You should promptly configure a recipient mailbox in the notification settings. If the total number of reported messages for a product reaches the alert threshold or exceeds the total available messages, the platform sends an email alert on the following day. Message throttling alerts use a T+1 mechanism, which means alerts are not sent in real-time.
On the Message Notification Management page, you can set the alert threshold (default: 80%) and configure the recipient mailbox. For more information, see Message Notification Management.
Effects of message throttling
If the total number of reported messages for a product exceeds the total available messages, or if the reported messages in a region exceed the regional quota, and you do not purchase a message package within the 48-hour processing time, the platform will enforce strict throttling based on the daily total of available messages. During subsequent use:
If the total number of reported messages does not exceed the total available messages, devices can report messages normally.
If the total number of reported messages exceeds the total available messages, devices that send messages beyond the quota cannot report them normally. You must purchase a message package to increase the total number of available messages.
How to avoid message throttling
You can optimize the device message reporting mechanism by reducing the number of reported messages or lowering the reporting frequency. For more information, see Device property settings and reporting specifications and On-demand device status reporting.
You should closely monitor data changes and maintain a sufficient account balance. This lets you purchase message packages promptly and ensure you have enough available messages for your product.
During the 48-hour processing time provided by the platform, you can purchase a message package to increase the total number of available messages.