Overview
A device can connect to and communicate with the platform. The device reports data to the platform using custom topics or product models. After the subscription/push configuration on the console is complete, the platform pushes messages about device lifecycle changes, reported device properties, reported device messages, device message status changes, device status changes, and batch task status changes to the application.
The platform supports three subscription modes: HTTP/HTTPS, AMQP, and MQTT.
- HTTP/HTTPS subscription/push: An application calls the platform APIs for creating a rule triggering condition, creating a rule action, and modifying a rule trigger condition to configure and activate rules. The platform pushes the changed device service details and management details to the application with a specified URL. (Service details include device lifecycle management, device data reporting, device message status, and device status. Management details include software/firmware upgrade status and result.)
- AMQP subscription/push: Data can be forwarded without interconnecting with other Huawei Cloud services. An application calls the platform APIs Creating a Rule Trigger Condition, Creating a Rule Action, and Modifying a Rule Trigger Condition to configure and activate rules. After a connection is established between the AMQP/MQTT client and the platform, the platform pushes the changes to a specified AMQP/MQTT message queue based on the type of data subscribed. For details about AMQP, see AMQP Subscription/Push. For details about MQTT, see MQTT Subscription/Push.
Subscription/Push |
Application Scenario |
Advantage |
Restrictions |
---|---|---|---|
HTTP/HTTPS subscription/push |
An application functions as the server and passively receives messages from the platform. |
- |
The traffic control limit is 800 TPS per second. HTTP/HTTPS is not recommended for large-traffic push. |
AMQP subscription/push |
An application functions as the client and proactively pulls messages from the platform or passively receives messages from the platform by means of listening. |
Data can be obtained proactively. |
For details, see Connection Specifications. |
MQTT subscription/push |
An application functions as a client and can receive messages from IoT cloud services through subscription. |
- |
For details, see Restrictions. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot