Manage topologies

Add topologies for sub-devices

You can use a topic to send a request for adding a topology between a gateway and sub-device. If the topology is added, the information of the sub-device is returned.

Upstream data

• Request topic: /sys/{productKey}/{deviceName}/thing/topo/add
• Response topic: /sys/{gw_productKey}/{gw_deviceName}/thing/topo/add_reply

Alink request format

{
  "id": "123",
  "version": "1.0",
  "params": [
    {
      "deviceName": "deviceName1234",
      "productKey": "1234556554",
      "sign": "xxxxxx",
      "signmethod": "hmacSha1",
      "timestamp": "1524448722000",
      "clientId": "xxxxxx"
    }
  ],
  "method": "thing.topo.add"
}

Alink response format

{
  "id": "123",
  "code": 200,
  "data": [
    {
      "deviceName": "deviceName1234",
      "productKey": "1234556554"
    }
  ]
}

Request parameters

sign= hmac_md5(deviceSecret, clientId123deviceNametestproductKey123timestamp1524448722000)

Response parameters

Error codes

Delete topologies of sub-devices

You can use a topic to send a request for deleting a topology between a gateway and sub-device. If the topology is deleted, the information of the sub-device is returned.

Upstream data

• Request topic: /sys/{productKey}/{deviceName}/thing/topo/delete
• Response topic: /sys/{gw_productKey}/{gw_deviceName}/thing/topo/delete_reply

Alink request format

{
  "id": "123",
  "version": "1.0",
  "params": [
    {
      "deviceName": "deviceName1234",
      "productKey": "1234556554"
    }
  ],
  "method": "thing.topo.delete"
}

Alink response format

{
  "id": "123",
  "code": 200,
  "data": [
    {
      "deviceName": "deviceName1234",
      "productKey": "1234556554"
    }
  ]
}

Request parameters

Response parameters

Error codes

Query topologies of sub-devices

Upstream data

• Request topic: /sys/{productKey}/{deviceName}/thing/topo/get
• Response topic: /sys/{gw_productKey}/{gw_deviceName}/thing/topo/get_reply

You can use a topic to send a request for querying a topology between a gateway and sub-device.

Alink request format

{
  "id": "123",
  "version": "1.0",
  "params": {},
  "method": "thing.topo.get"
}

Alink response format

{
  "id": "123",
  "code": 200,
  "data": [
    {
      "deviceName": "deviceName1234",
      "productKey": "1234556554"
    }
  ]
}

Request parameters

Response parameters

Error codes

Submit a list of new discovered devices

Upstream data

• Request topic: /sys/{productKey}/{deviceName}/thing/list/found
• Response topic: /sys/{productKey}/{deviceName}/_thing/diag/post_reply

In certain scenarios, a gateway can discover new sub-devices. The gateway submits information of new sub-devices to IoT Platform. IoT Platform forwards the information to third-party applications, and the third-party applications choose the sub-devices to connect to the gateway.

Alink request format

{
  "id": "123",
  "version": "1.0",
  "params": [
    {
      "deviceName": "deviceName1234",
      "productKey": "1234556554"
    }
  ],
  "method": "thing.list.found"
}

Alink response format

{
  "id": "123",
  "code": 200,
  "data":{}
}

Request parameters

Response parameters

Error message

Notify gateways to add topologies for sub-devices

Downstream data

• Request topic: /sys/{productKey}/{deviceName}/thing/topo/add/notify
• Response topic: /sys/{productKey}/{deviceName}/thing/topo/add/notify_reply

IoT Platform can use a topic to notify a gateway to add a topology for a sub-device. This applies after the gateway discovers new sub-devices and submits sub-device information to IoT Platform. IoT Platform can subscribe to the following data forwarding topic to receive the response from the gateway: /{productKey}/{deviceName}/thing/downlink/reply/message.

Alink request format

{
  "id": "123",
  "version": "1.0",
  "params": [
    {
      "deviceName": "deviceName1234",
      "productKey": "1234556554"
    }
  ],
  "method": "thing.topo.add.notify"
}

Alink response format

{
  "id": "123",
  "code": 200,
  "data": {}
}

Request parameters

Response parameters

Notify gateways of topology changes

Sub-devices can notify gateways of topology changes.

Gateways need to subscribe to the following topic: /sys/{productKey}/{deviceName}/thing/topo/change

Alink format of downstream data

{
    "id":"123",
    "version":"1.0",
    "params":{
        "status":0, // 0-create 1-delete 2-resume disabling 8-disable
        "subList":[{
            "productKey":"a1hRrzD****",
            "deviceName":"abcd"
        }]
    }, 
  "method":"thing.topo.change"  
}

Parameters

Alink response format

{
    "id":"123",
    "code":200,
    "message":"success",
    "data":{}
}