Some questions about message broker in deepstream

[LoveNvidia]

• Hardware Platform (Jetson / GPU) : Jetson
• DeepStream Version : 5.0 GA
• JetPack Version (valid for Jetson only) : 4.4
• TensorRT Version : 7.x

Q1- When we use ones of deepstream message broker like AMQP, this broker send all of metadata to server? also image?
Q2- How we can decode the message in the server side?
Q3- The iot zure broker is only for iot zure devices ? or it’s possible to send message into any server or devices?

[Amycao]

@LoveNvidia

Q1- When we use ones of deepstream message broker like AMQP, this broker send all of metadata to server? also image?

→ nvmsgconv plugin uses NVDS_EVENT_MSG_META type of metadata from the buffer and generates the “DeepStream Schema” payload in Json format. Static properties
of schema are read from configuration file in the form of key-value pair. Check dstest4_msgconv_config.txt for reference. Generated payload is attached as NVDS_META_PAYLOAD type metadata to the buffer.
nvmsgbroker plugin extracts NVDS_META_PAYLOAD type of metadata from the buffer and sends that payload to the server.
You can change the sample to send image using “extMsg” and “extMsgSize” fields. refer generate_event_msg_meta() how to use “extMsg” and “extMsgSize” fields for custom objects and how to provide copy/free function and attach that
object to buffer as metadata.

Q2- How we can decode the message in the server side?
→ depends on the broker protocol you used, you can check the official website for how it receive the message.

Q3- The iot zure broker is only for iot zure devices ? or it’s possible to send message into any server or devices?

→ We support direct messaging from device to cloud (using the Azure device client adapter) and through Azure IoT Edge runtime (using the Azure module client adapter). details you can check documentaion,
Gst-nvmsgbroker — DeepStream 6.3 Release documentation

Azure MQTT Protocol Adapter Libraries

See inline