Private Deployment Configuration_Private document_Privatization

Private Deployment Configuration

Regardless of the private deployment method used, it is necessary to send the private deployment configuration information to the device and save it.

There are three methods to configure private deployment for the device:

· Direct Configuration Method Suitable for a small number of devices

· Platform Registration Method Suitable for batch configuration

· Private Deployment Hotspot Method Suitable for custom configuration

Comparison of the Three Configuration Methods

Detailed introductions to each configuration method are provided in the corresponding private deployment method sections; only a brief description is given here.

Configuration Method	Description
Direct Configuration Method	Suitable for a small number of devices Modify the private deployment configuration items directly on the device's configuration page. After restarting the device, it will enter the corresponding private deployment mode.
Platform Registration Method	Suitable for batch configuration Register the corresponding "message server" or "gateway" in the console, and specify information such as the scope of use. After the device goes online and connects to the platform, the platform will deliver the private deployment information to the device. After restarting the device, it will enter the corresponding private deployment mode.
Private Deployment Hotspot Method	Suitable for custom configuration Enable the "Private Deployment Configuration Hotspot" at the device location. The hotspot name follows the format: pvt-interface-IP-address-interface-port-number. The device will prioritize connecting to this hotspot and read the private deployment configuration information. It can also read and save the device's network information.