Settings

Restart Module

Note the following about the Restart Module operation:

• Only the NB-IoT module can be restarted.
• The device must support remote module restart. Software Upgrade or Firmware Upgrade on the Maintenance Capability Configuration tab page of the product details (Product Models) corresponding to the device must be set to Supported.
• When you click Restart, the IoT platform sends the restart instruction to the device only after the device reports data.

After a module restart task is executed, you can view the task status on the Operations tab page. The module restart task has the following possible states:

• Waiting: The task is in the waiting state. After the task is created, the system sets a 10-second timer. After 10 seconds, the state changes to Processing.
• Processing: The IoT platform is processing the task. If the device reports no data for 25 consecutive hours, the IoT platform changes the state to Fail. Otherwise, the IoT platform delivers the module restart instruction to the device. After restarting the module, the device returns the processing result to the IoT platform, which then changes the state to Success or Fail.
• Success: The module has restarted. If the device returns a result indicating that the module is restarted, the state changes to Success.
• Fail: The module failed to be restarted. The state changes to Fail if the IoT platform does not deliver the module restart instruction to the device within 25 hours, the IoT platform delivers the module restart instruction to the device but does not receive a processing result from the device within 30 minutes, or the device returns the result indicating that the module restart failed.

Collect Log

Note the following about the Collect Log operation:

• Log collection applies only to NB-IoT devices.
• The device must support remote log collection. Software Upgrade or Firmware Upgrade on the Maintenance Capability Configuration tab page of the product details (Product Models) corresponding to the device must be set to Supported.
• When you click Collect, the IoT platform sends the log collection instruction to the device only after the device reports data.

After a log collection task is delivered, you can click Download to download and view the collected log files. The log collection task has the following possible states:

• Waiting: The task is in the waiting state. After a task is created, the state changes to Processing only after the IoT platform delivers the log collection instruction to the device. If the device reports no data for 25 consecutive hours, the state changes to Fail.
• Processing: The log collection instruction has been delivered to the device and is waiting for the device to return the log collection result. According to the returned result, the IoT platform changes the state to Success or Fail. If no result is received within 30 minutes, the state changes to Fail.
• Success: The log collection is successful. If the device returns a result indicating that the log collection succeeded, the state changes to Success.
• Fail: The log collection fails. The state changes to Fail if the IoT platform does not deliver the log collection instruction to the device within 25 hours, the IoT platform delivers the log collection instruction to the device but does not receive a processing result from the device within 30 minutes, or the device returns the result indicating that the log collection failed.

Reset Pre-secret

The pre-secret is used for authentication when a device connects to the IoT platform. It is used to encrypt the transmission channel between NB-IoT devices and the IoT platform, and to authenticate devices integrated with the AgentLite SDK when they attempt to access the IoT platform. After the pre-secret is reset, the new pre-secret must be updated on the device, and the device must carry the new pre-secret for authentication during IoT platform connection.

Reset Secret

The secret is used for authentication when devices call the MQTT interface to connect to the IoT platform. After the secret is reset, the new secret must be updated on the device, and the device must carry the new secret for authentication during IoT platform connection.

Move Between Applications

You can migrate the device to other authorized applications. For example, you can move device A from application X to application Y.

The following conditions must be met to ensure that a device can be migrated and services on the migrated device are normal:

• If the device has been registered with the IoT platform, the device to be migrated is an NB-IoT device.
• The source and target applications belong to the same user.
• The source application has been authorized to the target application.
• The target application has the profile file corresponding to the device.
• The power saving mode of the target application is the same as that of the source application.

Add Device Mode (NWI)

This function is used to connect a device to the IoT platform through a gateway. This function applies only to the Agent access mode. Only one device can be added each time. After this function is enabled, it is automatically disabled if no device is added within 180 seconds. If a device is added within 180 seconds, you can manually disable the function. Then you can enable the function to add another device.

You can view the added devices on the Sub Devices tab page.

Connect to Platform

This function displays access information about the bootstrap service and can be enabled by the IoT platform operations administrator. The bootstrap service enables the bootstrap server to automatically assign the IoT platform's IP address to an NB-IoT device so that the device can register with the IoT platform for unified management.

• IoT platform IP: IPv4 or IPv6 address for the device to connect to the IoT platform.
• Service Server ID: index of the bootstrap server.
• Security Connection Mode

  • PSK: Devices connect to the IoT platform in DTLS mode.

  • Non-secure: Devices connect to the IoT platform in non-encrypted mode.

  • Optimized PSK: Devices connect to the IoT platform in DTLS+ mode.

• Device Registration Lifecycle (s): time at which an NB-IoT device needs to re-register with the IoT platform. The bootstrap server delivers the information to the device. When the time expires, the device sends a reregistration request to the IoT platform. The IoT platform does not process this parameter.