Overview
Private deployment is implemented by setting up a new message server [Broker].
This method offers excellent flexibility and scalability.
Broker is a key component in the Internet of Things (IoT). It is primarily responsible for message transmission and routing.
It enables communication between applications and devices, and handles the Publish/Subscribe (Pub/Sub) mechanism for messages.
It enables communication between applications and devices, and handles the Publish/Subscribe (Pub/Sub) mechanism for messages.
Working Mechanism
Connection Between Device and Broker:
1 Bootstrapping
After the device is powered on, it starts connecting to the configured network
The device will enter the working mode assigned by the platform.
2 Registration
Obtains the username and password required for MQTT connection
The device will send an HTTP request to the configured registration (reg) interface.
3 Subscription
Connects to MQTT and subscribes to topics
The device will receive and send messages under the corresponding topics.
Considerations
When using the self-hosted Broker method for private deployment, the following points need attention:
| Item | Description |
| Communication Protocol | Your Broker must support the MQTT 3.1.1 protocol for device compatibility. |
| Network | The device maintains a persistent connection with the Broker during normal operation. Therefore, the device and the Broker must be on the same network (network segment) or have interconnected networks; otherwise, the device will fail to connect to your Broker. The Broker can be deployed in either internal or external networks, as long as the device and Broker networks are interconnected. |