In this demo we present a surveilance scenario composed by several IP video cameras, one surveilance terminal and the FTT-Enabled switch as the communication backbone. Each video stream is assigned to an asynchronous service inside the switch and sent to the surveilance terminal where it is displayed. By default all of the asynchronous services are configured with low QoS (low budget and period) however, they can be dynamically reconfigured with high QoS by the system upon a pre-defined event trigger (e.g object of interest detected). The following figure describes the used setup :
The following video shows the recorded demo. The recorded view is that from the surveilance terminal in which we can see the windows displaying the received video streams (one for each stream) and a monitoring window. The monitoring window shows the current bandwidth and framerate for each stream. When movement is detected by a camera, a reconfiguration is triggered and the service associated with its stream is reconfigured with high QoS.
NOTE : The IP cameras stream the video using the TCP protocol. Due to the TCP protocol nature, some stuttering and "fast-forward effect" can be observed during the reconfiguration of a service from a low QoS to a high QoS (caused by the log of old video frames). The movement detection algorithm runs on the surveilance terminal and makes use of the received streams to detect movement. When the framerate of a stream is very low (around 5 fps) the detection takes some time (we need to receive several complete frames to compare and analyse them). This detection should be run inside the cameras to make the reconfigurations snappier, however they do not have the required processing power for it nor do we have access to the firmware source code.
Asynchronous Services Parameters :
|Budget [bytes]||Period [ms]|