This type of message is used in the following two cases:

  1. For devices with class C: to immediately send a downlink message to the device.
  2. For devices with class A: to schedule downlink message for the next available time slot.

Messages of type downlink_claim allows you to notify NS about availability of downlink data on the AS side (AS ready to send some device). In other words downlink_claim initiates transmission of downlink_request message from NS to AS.

Let's walk through these sequence diagrams to understand better how downlink_claim message works:

For class A

Sequence looks like following:

  • AS sends downlink_claim message to NS
  • NS prepares downlink_request and sends it to AS
  • AS processing downlink_request
  • AS generates downlink payload and sends downlink_response to NS
  • NS receives downlink payload and saves it
  • End device sends uplink message to NS.
  • NS gets saved downlink payload and immediately generate downlink message and send it to the end device
  • NS generates downlink message to AS and send it.
For class C

Sequence looks like following:

  • AS send downlink_claim message to NS
  • NS prepares downlink_request and sends it to AS
  • AS processing downlink_request
  • AS generates downlink payload and sends downlink_response to NS
  • NS generates downlink message and sends it to the end device
  • NS generates downlink message to AS and send it.

Metadata

You should specify the following fields in downlink_claim metadata in order to emit message of this type:

  • device - device identifier

It is possible to specify a gateway and network as an option to ask NS downlink optimization engine to use a specific gateway to send downlink message. If this gateway is not active then request will not be sent.

Params

Parameters list is empty.

Example

{
    "meta": {
        "network": "1a3f34a3",
        "gateway": "",
        "device": "ba27356cb8a25961"
    },
    "type": "downlink_claim"
}

results matching ""

    No results matching ""