Combined security and video camera control system

Abstract

A solution which targets perimeter infrastructure. The solution comprises a plugin which integrates a dedicated security video camera management system with a comprehensive security system management system. A foundation is thereby provided which utilizes many advantages that are found in the security system management system, such as the creation of entities, Event-to Actions, and role fail-over. Use of the plugin results in an overall system where operators of the security system can imbed their own images and branding on the video streams. Users can effectively brand their edge devices without having to interface with the devices directly.

Description

BACKGROUND

The present invention generally relates to security systems and video camera control systems, and more specifically relates to a novel and inventive system which effectively combines security and security video camera management.

Currently, companies and organizations use one set of products and services for video camera management such as Axis Vapix, and a totally different set of products and services to manage security systems (i.e., access control, etc.), such as the Genetec Security Center. Using two different systems complicates matters.

Security video management systems do not provide the creation of entities, Event-to Actions, and role fail-over.

The availability and ability to interface with security infrastructure is a powerful addition to an organizations tool set. The BCD Vapix plugin targets perimeter infrastructure by integrating the Axis Vapix platform with Genetec's Security Center software.

The BCD Vapix plugin is a full Genetec plugin that integrates with the core Security Center platform. Built on the Genetec SDK platform, the BCD Vapix plugin builds a foundation to utilize many advantages that are found in Security Center such as the creation of native interfaces, entity management, and role failover.

All organizations have the need to monitor, maintain, and react to their critical perimeter infrastructure. Edge device interaction is vital to success in all market verticals. However, security system management systems do not allow users to brand their edge devices without having to interface with the devices directly. Conventional security system management systems do not allow security system managers the ability to imbed their own images and branding on video streams using the video camera management system. As such, images are not applied at the area level, and speed and productivity is not maximized.

SUMMARY

One object of an embodiment of the present invention is to provide a combined security system and security camera management system.

Another object of an embodiment of the present invention is to provide a user interface that allows users to brand their edge devices without having to interface with the devices directly.

Another object of an embodiment of the present invention is to provide a security system that interfaces with a video camera management system and allows users to imbed their own images and branding on video streams using the video camera management system.

Another object of an embodiment of the present invention is to allow users to apply security camera images at the area level.

Briefly, an embodiment of the present invention provides a solution which targets perimeter infrastructure by integrating a dedicated security video camera management system with a comprehensive security system management system. As such, a foundation is provided which utilizes many advantages that are found in the security system management system, such as the creation of native interfaces, entity management, and role failover. Security system operators can imbed their own images and branding on the video streams, and users can brand their edge devices without having to interface with the devices directly.

BRIEF DESCRIPTION OF THE DRAWINGS

The organization and manner of the structure and operation of the invention, together with further objects and advantages thereof, may best be understood by reference to the following description taken in connection with the accompanying drawings wherein like reference numerals identify like elements in which:

FIGS. 1-8, collectively, illustrate an overview of the client;

FIGS. 9A through 9E and FIGS. 10 through 38, collectively, illustrate the overlay configuration of the client;

FIGS. 39A-1, 39A-2, 39B, 39C, 39D, 39E, 39F-1, 39F-2, 39F-3, 39G-1, 39G-2, 39G-3, 39H-1, 39H-2, 39I-1, 39I-2, 39I-3, 39J-1, 39J-2, 39J-3, 39K-1, 39K-2, 39L-1, 39L-2, 39M, 39N, 39O, 40-139 and 140 through 160, collectively, illustrate helpers of the security camera management system;

FIGS. 161-169, collectively, illustrate an overview of the plugin;

FIGS. 170A through 170F, and FIGS. 171 through 199, collectively, illustrate request handlers of the plugin;

FIGS. 200A through 200P, FIG. 200Q-1, FIG. 200Q-2, FIGS. 200R through 200Z and FIGS. 201 through 312, collectively, illustrate the security video management system manager; and

FIG. 313 illustrates, generally, the architecture of the resulting system.

DESCRIPTION

While this invention may be susceptible to embodiment in different forms, there is shown in the drawings and will be described herein in detail, a specific embodiment with the understanding that the present disclosure is to be considered an exemplification of the principles of the invention and is not intended to limit the invention to that as illustrated.

All organizations have the need to monitor, maintain, and react to their critical perimeter infrastructure. Edge device interaction is vital to success in all market verticals. An embodiment of the present invention comprises a plugin which targets perimeter infrastructure by integrating a security camera management system, such as the Axis Vapix platform, with a comprehensive security system management system, such as Genetec's Security Center software, thereby providing a plugin that builds a foundation to utilize many advantages that are found in Security Center such as the creation of native interfaces, entity management, and role failover. As a result, the overall system allows users to brand their edge devices without having to interface with the devices directly and allows images to be applied at the area level.

Due to the sizing of letters, some Figures had to be broken up into multiple Figures. In this case, letters were used in the Figure numbering. For example, FIGS. 9A, 9B, 9C, 9D and 9E collectively form FIG. 9. Likewise, FIGS. 39A through 39O collectively form FIG. 39, and so on.

FIGS. 1-8, collectively, illustrate an overview of the client. As shown in those Figures, when a user opens the Genetec client, the plugin (BCD Vapix Plugin) checks to see if the Client is the Config Tool. If the client is Config Tool, the user is able relay commands and configuration to Axis Cameras' Vapix framework though the Genetec interface.

FIGS. 9A through 9E and FIGS. 10 through 38, collectively, illustrate the overlay configuration of the client. As shown in those Figures, when a user opens the Genetec Client, BCD Vapix checks to see if the client is Config tool. If it is, the plugin initializes the data model and retrieves the Plugin ID from the Genetec server. It also deserializes an object model from the Genetec server. When a user attempts to upload a file, a Dialog window is presented. The plugin filters the uploaded file by checking its file type. Only .PNG and .BMP are acceptable file formats. The file is the converted to a 24-bit .BMP. The height and width are serialized along with file and stored in the plugin. The image is then displayed. When an image is displayed, the plugin converts the stored serialized image into an image object. The correct overlay configuration is selected. If data is not being loaded, then the user is prompted to save the current configuration. When a user prompts to save a configuration, all data is serialized and stored in the base plugin role. The UI is reset to default values. When a user prompts to delete an overlay, the image is no longer rendered, deleted from the configuration, and the configuration is serialized into the plugin role.

FIGS. 39A-1, 39A-2, 39B, 39C, 39D, 39E, 39F-1, 39F-2, 39F-3, 39G-1, 39G-2, 39G-3, 39H-1, 39H-2, 39I-1, 39I-2, 39I-3, 39J-1, 39J-2, 39J-3, 39K-1, 39K-2, 39L-1, 39L-2, 39M, 39N, 39O, 40-139 and 140 through 160, collectively, illustrate helpers of the security camera management system. These Figures display the process and functions of the BCD Vapix Helper class. As shown, an image file gets converted into a string that can be serialized and a string is converted to a byte array that can be consumed as an image. When an Update Overlay function is invoked, the old overlay is removed. If the request is to delete an overlay, return. The Overlay is enabled if needed and then the API version is determined.

Old Firmware:

• • 1. Upload file to camera
  • 2. If successful, Save and convert the overlay
  • 3. If successful, Set the overlay
  • 4. Restart the cameraNew Firmware:
  • 1. Upload file to camera using new vapix call
  • 2. Translate the position of the image
  • 3. Restart the cameraDynamic Overlays:
  • 1. Upload file to camera using new vapix call
  • 2. Add the Dynamic IMage
  • 3. Restart the camera

The Remove Overlay Function determines the API version.

Old Firmware:

• • 1. Delete OverlayNew Firmware:
  • 1. New Delete Overlay Vapix function
  • 2. If not successful, call old Delete Overlay FunctionDynamic Overlays:
  • 1. Get Listed dynamic overlays
  • 2. Remove the BCD overlay

Check Firmware Version determines which version of the Vapix API to use. If the firmware is older than version 7, use the old API. If the firmware is version 8 or newer, use Dynamic overlays. If the firmware is newer than 7.10 but older than version 8, use the newer Vapix API. Otherwise default to the old API.

Use Dynamic overlays looks at the processor chip of the Camera. If the chip type is of “Artpec-7” use Dynamic Overlays when making API calls.

Enable Overlay also looks at the processor chip of the Camera. If the chip type is of “Artpec” enable Overlays when making API calls.

Is Amberella Chip looks that the processor chip of the Camera if the chip type is of “Amberella”.

Is Camera Valid determines if the camera is in the correct state to accept Vapix call. The camera must be manufactured by Axis and be online.

Determine API version is an inclusive function that utilizes several of the ones listed above to determine the API version to use. It first checks for the Amberella chip, then if to use Dynamic overlays, and finally calls Check Firmware Version.

Vapix Helper sends the following Vapix commands

• • 1. Delete Overlay
  • 2. Restart Camera
  • 3. Upload File to new Camera
  • 4. Translate Overlay on new Camera
  • 5. Check Processor Chip
  • 6. Add Dynamic Image
  • 7. Set Dynamic Image

FIGS. 161-169, collectively, illustrate an overview of the plugin. A shown in these Figures, the BCD Vapix Plugin server component initializes with the Genetec service. When loaded, the Vapix Manager Class is created and instantiated. As shown, the manager is also responsible for handling any commands or requests initiated by users from the Security Desk client.

FIGS. 170A through 170F, and FIGS. 171 through 199, collectively, illustrate request handlers of the plugin. As shown in these Figures, the plugin creates and registers request handlers for communication and user interaction The request handlers handle the following requests commands from the client application. Update Overlay gets the plugin role and its configuration. All configured overlays are iterated over to see if there is a change requested. If so, the function Update Cameras is invoked. Update Cameras iterates through the cameras found in the overlay configuration. Each camera is sent to the Async Add Handler function. Async Add Handler gets the camera and its corresponding video unit. If the camera is valid, the appropriate API version is called from Vapix Helper followed by the Update Overlay function.

FIGS. 200A through 200P, FIG. 200Q-1, FIG. 200Q-2, FIGS. 200R through 200Z and FIGS. 201 through 312, collectively, illustrate the security video management system manager. In effect, these Figures review the Vapix Manager class. As shown in these Figures, on Initialization, subscribes to Genetec's Entity Added, Invalidated, and removed events. It then creates a collection of all Genetec Areas that have had a Vapix overlay configured. The Add Overlay function gets a configured overlay and the list of cameras it applies to. If the overlay has an image configured, invoke Delete Overlay Override, otherwise invoke Async Add.

Async Add identifies if the function requires a chip check and performs one if needed. It then checks if the camera is valid and its required API version. Update Overlay is invoked followed by a reboot.

Delete Overlay Override gets a list of cameras and invokes Async Delete on each camera.

Async Delete gets the camera and the corresponding video unit. If the camera is valid, the processor chip and API version are determined. Remove Any Overlay is invoked followed by a reboot.

Get Plugin Config gets the role and its configuration.

Get Vapix Role gets the plugin role.

Prefetch Areas Async gets all areas and updates a collection of Area IDs

Add Update Collection gets an Area using the supplied ID. If it is not already cached in the collection, store the area ID and corresponding camera IDs.

Get Configured Overlay gets the plugin role and its configuration followed by retrieving the requested Overlay Configuration.

Get Alternate IP gets the plugin role and creates a Genetec System Configuration object. Next a Genetec custom field is identified, and its value retrieved on the specified video unit. If the value of the custom field is null, return the video unit's IP address otherwise return the value of the custom field.

Engine Entities Added is the method subscribed to the Genetec Entity Added Event. Iterate through the collection of Entities that were added. Any Entities of type Area are passed to the Add Update Collection.

Engine Entities Invalidated is the method subscribed to the Genetec Entity Invalidated Event. Iterate through the collection of Entities that were modified. With a Configured Overlay, if there were cameras added invoke Add Overlay. If a camera was removed, invoke Remove Overlay. The collection is then updated.

Engine Entities Removed is the method subscribed to the Genetec Entity Removed Event. Iterate through the collection of Entities that were removed. If the Entity is of type Area, Check if it is the collection. If so, the plugin role and overlay configuration are retrieved. The overlay configuration is deleted and then the collection is reserialzed into the plugin role.

A plugin in accordance with an embodiment of the invention allows for users to brand their edge devices (i.e., video cameras) without having to interface with the devices directly. The plugin presents the ability to upload and position custom image overlays on network cameras while never having to enter the camera's own interface or be within physical proximity of the device. Typically, a user must have knowledge of a video camera's network address and authentication credentials in order to interact with the camera's direct interface. This interaction would require the user to leave prior engagements in order to facilitate this interaction. The plugin in accordance with an embodiment of the invention provides a solution by automating this and providing commands that the VMS invokes to create an environment that reduces this burden to the operator.

FIG. 313 illustrates, generally, the architecture of the resulting system. The plugin enhances the Video Management system by further evolving its “Management” capabilities. A plugin in accordance with an embodiment of the invention introduces the ability to modify the incoming video streams as opposed to merely bringing them into the VMS.

While the foregoing description was specific to the integration of Axis Vapix and Genetec's Security Center, an embodiment of the present invention can be configured to effectively merge the functionality of two other systems while still staying within the scope of the present invention.

While a specific embodiment of the invention has been shown and described, it is envisioned that those skilled in the art may devise various modifications without departing from the spirit and scope of the present invention.

Claims

1. A security management system comprising at least one video camera; and a user interface that is configured to provide that a user can use the user interface to upload and position a custom image overlay comprising an image on the at least one video camera while never having to enter the at least one video camera's own interface, wherein the security management system is configured to convert a stored serialized image into the image, display the image, and wherein when a user uses the user interface to save a configuration, the security management system displays a list of video cameras to which the image will be applied, applies the image to the video cameras in the list, and reboots the video cameras in the list.

2. A security management system as recited in claim 1, further comprising a plugin that integrates a dedicated security video camera management system with a comprehensive security system management system.

3. A security management system as recited in claim 1, wherein the security management system is configured to provide the creation of entities, Event-to Actions, and role fail-over.

4. A security management system as recited in claim 2, wherein the plugin initializes a data model and retrieves a Plugin ID from a server of the security system management system, wherein when the user attempts to upload a file, a Dialog window is presented, and the plugin filters the uploaded file by checking its file type.

5. A security management system as recited in claim 4, wherein the plugin converts the file, serializes the height and width of an image contained in the file, and then displays the image.

6. A security management system as recited in claim 1, wherein when the user prompts to delete an overlay, the image is no longer rendered, is deleted from the configuration, and the configuration is serialized into a plugin role.

7. A security management system as recited in claim 6, wherein an image file gets converted into a string that can be serialized and a string is converted to a byte array that can be consumed as an image.

8. A security management system as recited in claim 7, wherein when an Update Overlay function is invoked, an old overlay is removed.

9. A security management system as recited in claim 8, wherein the plugin creates and registers request handlers for communication and user interaction.

10. A security management system as recited in claim 9, wherein the request handlers handle request commands.

11. A security management system as recited in claim 10, wherein the request commands comprise a request to update an image displayed relating to the at least one video camera.

12. A plugin that integrates a dedicated security video camera management system with a comprehensive security system management system, wherein there is a user interface that is configured to provide that a user can use the user interface to upload and position a custom image overlay comprising an image on the at least one video camera while never having to enter the at least one video camera's own interface, wherein the plugin converts a stored serialized image into the image, displays the image, and wherein when a user uses the user interface to save a configuration, the plugin displays a list of video cameras to which the image will be applied, applies the image to the video cameras in the list, and reboots the video cameras in the list.

13. A plugin as recited in claim 12, wherein the plugin initializes a data model and retrieves a Plugin ID from a server of the security system management system, wherein when the user attempts to upload a file, a Dialog window is presented, and the plugin filters the uploaded file by checking its file type.

14. A plugin as recited in claim 13, wherein the plugin converts the file, serializes the height and width of an image contained in the file, and then displays the image.

15. A plugin as recited in claim 14, wherein when the user prompts to delete an overlay, the image is no longer rendered, is deleted from the configuration, and the configuration is serialized into a plugin role.

16. A plugin as recited in claim 15, wherein an image file gets converted into a string that can be serialized and a string is converted to a byte array that can be consumed as an image.

17. A plugin as recited in claim 16, wherein when an Update Overlay function is invoked, an old overlay is removed.

18. A plugin as recited in claim 17, wherein the plugin creates and registers request handlers for communication and user interaction, wherein the request handlers handle request commands, wherein the request commands comprise a request to update an image displayed relating to the at least one video camera.