Geutebrueck

This section provides information on how to integrate QbProtect with Geutebrueck G-Core. Please refer to the ONVIF section beforehand for general information on using ONVIF with QbProtect.

The following Geutebrück components have been used in the examples below:

  • G-Core Server, G-Set, G-View and G-PLC Simulator - Versions 8.2.0.870

Add Device

The G-Set tool is used to add QbProtect into Geutebrück G-Core VMS.

The procedure includes the following steps:

  1. Launch G-Set and connect to the active G-Core server instance

  2. Navigate to Media channels/Hardware → Hardware → Hardware module list → Add device → ONVIF IPC IP camera plugin settings

  3. Navigate to Module channel → Hardware settings → give a distinguishable name to the QbProtect device, e.g. QbProtect

  4. Navigate to the Connection Tab → enter the FQDN or IP of QbProtect in the Hostname field and Username/Password in the corresponding credential fields.

    Please refer to the User Authentication (ONVIF/RTSP) subsection to find out how to obtain valid ONVIF credentials required for QbProtect VMS integrations.
    800
    Figure 1. Adding QbProtect into Geutebrück G-Core: G-Set hardware configuration

  5. Navigate to Media channels/Hardware → Media channels → Live Streaming → select QbProtect as a media channel source

  6. Send these configuration settings to the G-Core server using the corresponding button in the top left conner

  7. The live preview of the point cloud should be available in the preview window of G-Set

    800
    Figure 2. Adding QbProtect into Geutebrück G-Core: G-Set media channel configuration

  8. Launch G-View and connect to the active G-Core server instance

  9. QbProtect should be available as a video channel source → Drop it into the G-View viewer

    800
    Figure 3. Adding QbProtect into Geutebrück G-Core: G-View live video stream

The live video stream of the QbProtect point cloud can be accessed and observed in Geutebrück G-View after succesfully completing the required steps above.

Events

Configure Events Handling

The example below shows how QbProtect events can be used to trigger alarms in Geutebrück G-Core VMS. After QbProtect has been added to the G-Core, it can be configured to use QbProtect events for alarm generation. In this example, a single security zone called Security Zone 1 has been configured using QbProtect WebGUI as shown in the Figure below.

800
Figure 4. QbProtect WebGUI viewer and Geutebrück G-View: single zone in the security scene

The events configuration procedure includes the following steps:

  1. Launch G-Set and connect to the active G-Core server instance (optional)

  2. Navigate to Media channels/Hardware → Hardware → Hardware module list → QbProtect → Module channel

  3. Navigate to the Event handling tab → Toggle Enable Event Handling with…​ → select WS-BaseNotification

  4. Toggle Send unkown events as…​ → select OnvifNotificationMessage Action

  5. Send these configuration settings to the G-Core server using the corresponding button in the top left conner

  6. Trigger the Get event info! button to get the list of supported QbProtect events

  7. The configured Security Zone 1 topic should be displayed in the list of available events

    800
    Figure 5. Geutebrück G-Set: configuration of events handling and the list of supported QbProtect events

  8. Launch G-PLC Simulator and connect to the active G-Core server instance

  9. Server logs should now contain OnvifNotificationMessage payloads corresponding to the list of supported QbProtect events

    800
    Figure 6. Geutebrück G-PLC: incoming OnvifNotificationMessages with events payload

Events originating from dynamic event sources (e.g., intrusion events from a particular security zone) have to be correctly exposed to the VMS each time when a new zone configuration is introduced via WebGUI. Please re-toggle Enable Event Handling with…​ to re-expose new events from dynamic sources.

Configure Rule Chain

The Geutebrück G-Core Events can be used to configure simple rules chains, while Behaviour rules targeting the more sophisticated configurations. In this example, we will consider the simple event rule chain configuration. The Geutebrück event rule chain consists of event source (StartBy and StopBy hooks) and event action (OnStart and OnStop hooks). It allows to map a dedicated action (e.g., manual alarm action, adding entry log, .etc) to the event of the particular type (e.g., motion, zone intrusion).

The event rule chain configuration procedure includes the following steps:

  1. Navigate to Events/Behaviour rules → Events → 'Event List' → 'Add new event'

  2. Navigate to Event tab → give a meaningful name to the event in the Name field, e.g. Security Zone 1 Intrusion → toggle this event to be Active

    800
    Figure 7. Geutebrück G-Set: event name configuration and activation

  3. Navigate to Alarm tab → give a meaningful name to alarm in the Alarm Name field, e.g. Security Zone 1 Intrusion Alarm → toggle this alarm to be Active

  4. Navigate to Media channels tab of the Alarm tab → Add QbProtect as media channel source

    800
    Figure 8. Geutebrück G-Set: alarm name configuration and activation

  5. Right click StartBy hook → Add → Onvif Notification Message → Select QbProtect as a channel source → Set topic name to tnsblickfeld:ZoneIntrusionSecurityZone1 → Set Data name and Data value to State and True correspondingly

    800
    Figure 9. Geutebrück G-Set: event source start trigger configuration

  6. Right click StopBy hook → Add → Onvif Notification Message → Select QbProtect as a channel source → Set topic name to tnsblickfeld:ZoneIntrusionSecurityZone1 → Set Data name and Data value to State and False correspondingly

    800
    Figure 10. Geutebrück G-Set: event source stop trigger configuration

  7. Right click OnStart hook → Add → Viewer show alarm by type → Select Security Zone 1 Intrusion as an Alarm Type → Assign ID to the Viewer

    800
    Figure 11. Geutebrück G-Set: event action configuration

  8. Send these configuration settings to the G-Core server using the corresponding button in the top left conner

  9. Launch G-View to observe raised alarms and alarm history

  10. Make sure that server alarm processing is enabled in G-View. Navigate to Options → User Options → switch to tabs Alarms → toggle `Process Server alarms'

    800
    Figure 12. Geutebrück G-View: enable alarm processing

The zone intrusion event in the Security Zone 1 from QbProtect and the configured intrusion event rule chain will be generating an alarm in G-View as shown in the Figure below.

800
Figure 13. Geutebrück G-View: intrusion event in the security zone raises alarm