Uplink/Downlink

The flow provides 4 injector sample nodes allowing a better understanding of the UPLINK and DOWNLINK message formats.

This flow uses MQTT protocol and relies on the internal MQTT broker built-in in ThingPark Enterprise All-in-One.

• UL Sample: reception of an UPLINK message (simulated)

  • Raw: UPLINK that was not decoded by the driver engine, the "payload_hex" field is a hexadecimal string.
  • Clear: UPLINK that was decoded by the driver engine, the payload_hex field is present, a DriverCfg field gives the driver configuration used to decode the message, a "payload" field is added that gives the decoded JSON document.

• DL Sample: injection of a DOWNLINK towards a device

  • Raw: DOWNLINK message contains only a "payload_hex" field which is a hexadecimal string.
  • Clear: DOWNLINK message contains a "payload" field which is a json document, and a "DriverCfg" field that gives the driver configuration for the encoding engine.

note

To learn more about the message content exchanged between ThingPark Enterprise All-in-One and third-party Application Servers (also called LRC/AS tunnel interface), see the interface documentation.

Note that Multicast & Location reports are not supported by ThingPark Enterprise All-in-One.

For testing purposes, you may change the payloads and click on the injector node button to inject a new message on the flow: