MQ push

Usage notes

Both the MQ push feature and automation rules monitor the status changes and traffic usage of IoT SIM cards. The main difference is that automation rules push messages within the Alibaba Cloud console and do not require custom development. The MQ push feature pushes messages directly to your system and requires custom development.

Prerequisites

The MQ push feature uses the Message Queue service. You must activate the Message Queue service before you use this feature.

For more information, see Activate Message Queue service.

Procedure

1. Log on to the IoT SIM Service console.

2. In the navigation pane on the left, choose MQ Push.

3. On the MQ Push page, click Message Queue Service.

4. In the Message Queue Service dialog box, click Authorize.

5. On the Cloud Resource Access Authorization page, click OK.

   Note

   For more information about the role for service authorization, see Service-linked Role.

6. On the MQ Push page, click Message Queue Service and configure the parameters for upstream messages.

   Note

   If you have not activated the Message Queue service, click Go to Settings next to Region. You are redirected to the Message Queue for Apache RocketMQ page where you can activate and configure the service. For more information, see What is Message Queue for Apache RocketMQ?.

   • Region: Select the region where the Message Queue instance is located.

   • Instance: Select the Message Queue instance.

   • Upstream Topic: Select the topic for pushing messages.

7. Select the I agree to allow IoT Mobile Connection Package to write data to the selected Message Queue topic check box, and then click OK.

8. Next to Message Push Type, click the Push Settings button, and enable the message types that you want to push.

   Message push type	Description
   CARD_STATUS_CHANGE	Triggers a push when the status of a card changes.
   FLOW_USAGE_PER_MONTH	When the traffic usage of a card changes, a push is sent every 60 minutes.
   INTERFACE_INVOKE	API call push. A push is triggered after a request to a management API (that is, a non-query API) is complete.
   POOL_REST	A push is sent for every 10 GB decrease in traffic for data pools of the same tier and unified payment data pools.
   SAME_FLOW_USAGE_PERCENT	A push is sent for every 1% decrease in traffic for data pools of the same tier.