IoT Platform allows you to send device messages to Message Service (MNS). Cloud applications can obtain the device messages by listening to MNS queues. This article describes how to configure an MNS server-side subscription.


If you use a RAM user, the RAM user must have the AliyunIOTAccessingMNSRole permission.


  1. In the IoT Platform console, configure an MNS server-side subscription for a product. IoT Platform automatically forwards messages to MNS queues.
    1. Log on to the IoT Platform console.
    2. In the left-side navigation pane, choose Rules > Server-side Subscription.
    3. On the Subscriptions tab of the Server-side Subscription page, click Create Subscription.
    4. In the Create Subscription dialog box, set the following parameters and click OK.
      Parameter Description
      Products Select the product to which the devices belong. The messages submitted by these devices are pushed to consumers.
      Subscription Type Select MNS.
      Message Type Select the types of messages. You can subscribe to the following types of device messages:
      • Device Upstream Notification: the messages in the topics whose Allowed Operations parameter is set to Publish.

        This type of messages includes custom data and Thing Specification Language (TSL) data that is submitted by devices. The upstream TSL data includes property data, event data, responses to property setting requests, and responses to service calling requests. The TSL data that is pushed to user servers is processed by IoT Platform. For more information about data formats, see Data formats.

        For example, the following three topics are defined for a product:
        • /${YourProductKey}/${YourDeviceName}/user/get. The Allowed Operations parameter of this topic is set to Subscribe.
        • /${YourProductKey}/${YourDeviceName}/user/update. The Allowed Operations parameter of this topic is set to Publish.
        • /sys/${YourProductKey}/${YourDeviceName}/thing/event/property/post. The Allowed Operations parameter of this topic is set to Subscribe.

        IoT Platform pushes messages in the following topics: /${YourProductKey}/${YourDeviceName}/user/update and /sys/${YourProductKey}/${YourDeviceName}/thing/event/property/post.

      • Device Status Change Notification: the notifications that devices send when the online or offline status changes.
      • Gateway's sub-devices discovery report: the sub-device data that gateways submit when these gateways detect new sub-devices. The gateways must have the applications that can be used to detect sub-devices. This message type is specific to gateways.
      • Device Topological Relation Changes: the notifications that gateways send when topological relationships between sub-devices and the gateways are created or deleted. This message type is specific to gateways.
      • Device Changes Throughout Lifecycle: the notifications that devices send when the devices are created, deleted, enabled, or disabled.
      • TSL Historical Data Reporting: The historical properties and events that are submitted by devices.
      • OTA Update Status Notification: the notifications that devices send during firmware verification and batch update. When a device update succeeds or fails, a notification is pushed.
    5. In the message that appears, click Confirm.
      IoT Platform automatically creates an MNS message queue in the format of aliyun-iot-${yourproductkey}. When you configure a queue listener, you must specify this message queue.

      You are charged for using MNS resources. For more information about billing methods, see MNS billing.

      Note If you delete the MNS server-side subscription, the related MNS queue is automatically deleted.
  2. Configure an MNS client and listen to the MNS queue.

    In this example, the MNS SDK for Java is used to listen to the MNS queue.

    For more information about how to download the MNS SDK, see MNS documentation.

    1. To install the MNS SDK for Java, add the following dependencies to the pom.xml file:
    2. Specify the following parameters when you configure the MNS SDK:
      CloudAccount account = new CloudAccount( $AccessKeyId, $AccessKeySecret, $AccountEndpoint);
      • Replace $AccessKeyId and $AccessKeySecret with the AccessKey ID and AccessKey secret of your Alibaba Cloud account. These parameters are required when you call API operations. To create or view an AccessKey pair, log on to the IoT Platform console, move the pointer over your profile picture, and then click AccessKey Management.
      • Replace $AccountEndpoint with the MNS endpoint. In the MNS console, click Get Endpoint.
    3. Specify the logic to receive device messages.
      MNSClient client = account.getMNSClient(); 
      CloudQueue queue = client.getQueueRef("aliyun-iot-a1wmrZPO8o9"); //Specify the automatically created queue.
          while (true) { 
          //Retrieve messages. 
          Message popMsg = queue.popMessage(10);  //The timeout period of long polling requests is 10 seconds.      
          if (popMsg ! = null) { 
              System.out.println("PopMessage Body: "+ popMsg.getMessageBodyAsRawString()); //Obtain raw messages. 
              queue.deleteMessage(popMsg.getReceiptHandle()); //Delete the messages from the queue. 
          } else { 
              System.out.println("Continuing"); } }
    4. Run the program to listen to the MNS queue.
  3. Start a device and send a message from the device to IoT Platform.

    For more information about how to develop a device-side SDK, see the Link SDK documentation.

  4. Check whether your cloud application retrieves the message. The following code shows the format of a retrieved message:
    "messageid":" ",
    "payload":" ", 
    "timestamp": " "
    Parameter Description
    messageid The ID of the message. The message ID is generated by IoT Platform.
    messagetype The type of the message. Valid values:
    • upload: submitted device data
    • status: device status changes
    • topo_listfound: the detection of sub-devices by a gateway
    • topo_lifecycle: device topology changes
    • device_lifecycle: device lifecycle changes
    • thing_history: historical TSL data
    • ota_event: firmware update status
    topic The IoT Platform topic from which the message is forwarded.
    payload The base64-encoded message payload.

    For more information about data formats, see Data formats.

    timestamp The timestamp. It is the number of seconds that have elapsed since the epoch time January 1, 1970, 00:00:00 UTC.