IoTIoT

Compute
Elastic Cloud Server
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
Domain Name Service
VPC Endpoint
Cloud Connect
Enterprise Switch
Security & Compliance
Anti-DDoS
Web Application Firewall
Host Security Service
Data Encryption Workshop
Database Security Service
Advanced Anti-DDoS
Data Security Center
Container Guard Service
Situation Awareness
Managed Threat Detection
Compass
Cloud Certificate Manager
Anti-DDoS Service
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GaussDB NoSQL
GaussDB(for MySQL)
Distributed Database Middleware
GaussDB(for openGauss)
Developer Services
ServiceStage
Distributed Cache Service
Simple Message Notification
Application Performance Management
Application Operations Management
Blockchain
API Gateway
Cloud Performance Test Service
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
DevCloud
ProjectMan
CodeHub
CloudRelease
CloudPipeline
CloudBuild
CloudDeploy
Cloud Communications
Message & SMS
Cloud Ecosystem
Marketplace
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP License Service
Support Plans
Customer Operation Capabilities
Partner Support Plans
Professional Services
enterprise-collaboration
Meeting
IoT
IoT
Intelligent EdgeFabric
DeveloperTools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Help Center> IoT> API Reference> MQTT Interface Reference> Overview> Flow Description> Service Process (One-Device-One-Secret)
Updated at: Feb 24, 2022 GMT+08:00

Service Process (One-Device-One-Secret)

  1. The application sends a device registration request to the IoT platform.
  2. The registration is successful, and deviceId and secret are returned. If the registration fails, the failure cause is returned.
  3. After the device is powered on, it sends a connection authentication request containing clientId, username, and password to the IoT platform. For details, see MQTT Connection Authentication Through CONNECT Messages.
  4. After the authentication is successful, the IoT platform returns a success response. The device is connected to the IoT platform.
  5. The device sends a SUBSCRIBE message carrying the topic that contains deviceId to the IoT platform.
  6. The IoT platform returns the subscription result.
  7. The device sends a PUBLISH message carrying data and the topic to the IoT platform.
  8. The IoT platform decodes the data by using the corresponding codec plug-in.
  9. The IoT platform sends the decoded data to the corresponding application based on the topic.
  10. The application delivers a command to the IoT platform.
  11. The IoT platform encodes the data by using the corresponding codec plug-in.
  12. The IoT platform sends the encoded data to the device.
  13. The device responds to the command and returns a response to the IoT platform.
  14. The IoT platform sends the command execution result to the application.
    NOTE:

    For details about the APIs used for the interaction between applications and the IoT platform, see the API reference document.

Did you find this page helpful?

Failed to submit the feedback. Please try again later.

Which of the following issues have you encountered?







Please complete at least one feedback item.

Content most length 200 character

Content is empty.

OK Cancel