Updated on 2022-02-24 GMT+08:00

Registration

Register a device on the IoT platform and define device parameters. Then the device can connect to the IoT platform if authentication succeeds.

The IoT platform supports individual registration and batch registration. NAs can also call the registration API to register an individual device on the IoT platform. Currently, batch device registration by using an API is not supported.

NOTE:

After the registration API is called to register a device or a batch device registration task is created on the Management Portal, the IoT platform automatically deletes a device if it does not connect to the IoT platform within a specified duration.

  • When the registration API is used, the duration is specified by the timeout parameter. If the parameter is set to 0, the registered device information is permanently valid. If the parameter is not set, the default value is used.
  • For individual device registration on the Management Portal, the registered device information is permanently valid.

Registering an Individual Device

  1. Choose Devices > Registration.
  2. Click the Individual Registration tab, and then click Register. In the dialog box displayed, set the parameters based on Table 1, and click Confirm.

    Table 1 Individual device registration parameters

    Parameter

    Configuration Rule

    Product

    Select a product.

    You can select a product only after it is defined on the Product Models page. If the product model has not been uploaded, upload or create it first.

    Node ID

    Specify the unique physical identifier of a device, such as its IMEI or MAC address. This parameter is carried during device access and used by the IoT platform to authenticate the device.

    • For a native MQTT device, the device ID (corresponding to the node ID) and secret generated after the registration are used for IoT platform connection.

    • For an NB-IoT device or a device integrated with the AgentLite SDK, the node ID and pre-secret entered during the registration are used for IoT platform connection.

    Pre-secret

    • For an NB-IoT device, the pre-secret is used to encrypt the transmission channel between it and the IoT platform.
    • For a device integrated with the AgentLite SDK, the pre-secret is used by the IoT platform to authenticate its access.
    • A native MQTT device does not require a pre-secret.

    Confirm Pre-secret

    Enter the pre-secret again.

Registering a Batch of Device

  1. Choose Devices > Registration.
  2. Click the Batch Registration tab page, and then click Create. In the dialog box displayed, enter the task name, select a product, upload the batch registration file, and click Submit.

    Table 2 Parameters in the batch registration file template

    Parameter

    Value

    Product

    Select a product.

    You can select a product only after it is imported on the Product Models page. If the product model has not been uploaded, upload or create it first.

    nodeId

    Specify the unique physical identifier of a device, such as its IMEI or MAC address. This parameter is carried during device access and used by the IoT platform to authenticate the device.

    • For a native MQTT device, the device ID (corresponding to the node ID) and secret generated after the registration are used for IoT platform connection.

    • For an NB-IoT device or a device integrated with the AgentLite SDK, the node ID and pre-secret entered during the registration are used for IoT platform connection.

    preSecret

    • For an NB-IoT device, the pre-secret is used to encrypt the transmission channel between it and the IoT platform.
    • For a device integrated with the AgentLite SDK, the pre-secret is used by the IoT platform to authenticate its access.
    • A native MQTT device does not require a pre-secret.