目录

Message Frequency Control

Push Kit's message frequency control includes scenario-based, device-based, and test message frequency control, as well as the push rate control. Upon the violation of any frequency control rule, a corresponding receipt status code will be returned (see Receipt Status Codes for details).

The message count used in a frequency control rule is based on the number of push requests sent by an app, regardless of whether the device successfully displays the message. If a message is not displayed as expected, you are advised to troubleshoot the issue before sending more push requests.

Scenario-Specific Message Frequency Control

To provide better user experience, Push Kit provides different frequency control rules for various push scenarios.

If scenario-specific messages exceed the limits specified by frequency control rules, Push Kit will return result code 256 to your message receipt server. For details, please refer to Receipt Status Codes.

The following table lists the frequency control rules.

Scenario

Frequency Control Rule

Notification message

1. Apps are punished for violations based on the number of violations. For details, please refer to Push Notification Violation Penalty Criteria.

2. When the message category is set to MARKETING, the marketing message sending frequency control rule is applied. For details, please refer to Notification Message Frequency Control Rules.

3. Authorized subscription messages can be sent at most 30 times every 5 minutes to each device. When the upper limit is reached, frequency control takes effect and subscription requests cannot be sent to the same device in 5 minutes. After the 5-minute duration expires, the subscription count is cleared.

Widget update message

The update frequency is limited for each app per widget.

Default frequency: For a released app, up to two messages can be pushed to each widget per device per day. For an unreleased app, up to five messages can be pushed to each widget per device per day.

Live view message

The messages of a single live view can be updated for up to 10 times every 5 minutes and 60 times every hour per device.

In the ride hailing and live score scenarios, the messages of a single live view can be updated for up to 30 times every 5 minutes and 180 times every hour per device.

Device-based Message Frequency Control

In addition to the scenario-specific message frequency control, Push Kit limits the total number of messages that can be received by a single device per day.

Currently, Push Kit allows a single app to push a maximum of 3000 messages to a single device per day. If your app sends more than 3000 scenario-specific messages to a single device on a single day, message throttling will be implemented until the next day, and Push Kit will return result code 102 to your message receipt server. For details, please refer to Receipt Status Codes.

Test Message Frequency Control

To facilitate message testing, you can set pushOptions.testMessage to true to send test messages.

A total of 1000 test messages (shared by all devices) can be pushed for each project per day and are not subject to scenario-specific message frequency control. If more than 1000 test messages are sent for a project on a single day, message throttling will be implemented until the next day, and Push Kit will return result code 256 to your message receipt server. For details, please refer to Receipt Status Codes.

Message Push Rate Control

Message push rate refers to the QPS of an app, that is, the number of devices to which an app sends messages per second. If the QPS of an app exceeds the threshold, HTTP response code 503 is returned. The QPS varies depending on the app type and increases with the number of monthly active users of the app on Huawei devices. To query the QPS threshold of an app, sign in to AppGallery Connect, find and click your project, go to Grow > Push Kit > Settings, select the app, and check the QPS threshold.

  • When the network traffic is high, system-level flow control will be implemented, causing requests to be rejected with HTTP response code 503.