About the RTSP Stream Distribution Structure of the VMS Server

Answered

IanKwon

November 05, 2024 01:33

Hi, I have a question that came up while I was testing the performance of the Nx Plugin.

We are assigning an RTSP Stream using the VMS Client GUI, and I would like to clarify:

Does this assignment allocate the RTSP Stream directly to the VMS Server only, or does it also allocate it to the client?

I assume that it would make more sense to allocate the RTSP Stream directly to the VMS Server, due to the scalability of the RTSP Stream. However, I would like to confirm this. From my understanding, there are two possible scenarios:

1. The RTSP Stream is assigned to both the VMS Server and Client. The client then requests metadata for the stream, and the VMS Server responds with the metadata only. The client then overlays this metadata on top of the RTSP Stream that it already has.

2. The RTSP Stream is assigned to the VMS Server only. The VMS Server then redistributes the RTSP Stream with the metadata to the client.

Could you please clarify which one is correct?

 

Additionally, I would also like to know if the VMS Client renders graphics such as bounding boxes and captions directly, or if the client itself generates these graphics using metadata retrieved from the VMS Server response.

0

• 

  Ichiro

  • Network Optix team

  November 07, 2024 02:25

  Hi Kwon,

  Thank you for your question!

  The RTSP stream is distributed through the Nx Mediaserver. Since this is a “server-client” system, all data—including streams and metadata—flows from the Nx Mediaserver. There is no redistribution of streams or metadata through the desktop clients.

  Coordinates of bounding boxes are generated by external systems, such as analytics or cameras. Then the Mediaserver stores those metadata, including coordinates, or object types which the desktop client retrieves to display and render the boxes accordingly.

  Thank you!

  0

Please sign in to leave a comment.