Selective use of cameras in distributed surveillance systems

By adopting a distributed architecture and dynamic camera node configuration in the video surveillance system, the communication connection is adjusted according to the camera priority value, the problem of insufficient processing and storage capabilities of the existing system is solved, and efficient video data management and scalability is achieved.

CN113938640BActive Publication Date: 2024-11-08SEAGATE TECH LLC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202110702234.0
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2020-06-29
Filing Date
2021-06-24
Publication Date
2024-11-08
Estimated Expiration
2041-06-24

AI Technical Summary

Technical Problem

Existing video surveillance systems face difficulties in data management and access when processing and storing large amounts of video data, especially the limited processing capacity and poor scalability of the equipment, resulting in limitations in the processing and storage capacity of the system.

Method used

Using a distributed video surveillance system, by processing and storing video data at multiple camera nodes, and dynamically adjusting the communication connection between the camera and nodes according to the camera priority value, load balancing and resource optimization are achieved, allowing flexibility between camera nodes. Reconfigure and extension.

Benefits of technology

It improves the scalability and robustness of the video surveillance system, can effectively manage and store a large amount of video data, reduces the system's computing load, and supports flexible video data processing and storage strategies, enhancing the reliability and economics of the system.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN113938640B_ABST
    Figure CN113938640B_ABST
Patent Text Reader

Abstract

The present application discloses the selective use of cameras in a distributed surveillance system. A distributed video management system that allows surveillance camera allocation parameters and dynamically reallocates video cameras to available camera nodes in response to detecting changes in the allocation parameters, the reallocation comprising selectively discarding the camera from the system based on the priority of at least one camera. The change in the allocation parameter can be attributed to many potential contexts, including changes in the availability of camera nodes, changes in the nature of the captured video data, changes in computational load, or other changes that cause the allocation parameter to change. The disconnection or "discarding" of a camera can be temporary in response to an increase in computational load on the system. The use of priority values ​​for the cameras can allow the system to provide sufficient camera coverage while maintaining processing of video data from higher priority cameras.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application is related to U.S. Patent Application No. _____ filed on [Docket No. STL 074916.00] and entitled “PARAMETER BASED LOADBALANCING IN A DISTRIBUTED SURVEILLANCE SYSTEM”, U.S. Patent Application No. _____ filed on [Docket No. STL 074921.00] and entitled “LOW LATENCY BROWSER BASED CLIENT INTERFACE FOR ADISTRIBUTED SURVEILLANCE SYSTEM”, U.S. Patent Application No. _____ filed on [Docket No. STL074922.00] and entitled “DISTRIBUTED SURVEILLANCE SYSTEM WITH ABSTRACTED FUNCTIONAL LAYERS”, U.S. Patent Application No. _____ filed on [Docket No. STL 074923.00] and entitled “DISTRIBUTED SURVEILLANCE SYSTEM WITH DISTRIBUTED VIDEO ANALYSIS" all of which are filed concurrently and are specifically incorporated by reference for all that they disclose or teach. Background Art

[0003] Video surveillance systems are a valuable security resource for many facilities. In particular, advances in camera technology have made it possible to install video cameras in an economically viable manner to provide robust video coverage for facilities, thereby assisting security personnel in maintaining on-site security. Such video surveillance systems may also include recording features that allow video data to be stored. The stored video data may also help entities provide more robust security, thereby allowing valuable analysis or assisting in investigations. Live video data feeds may also be monitored in real time at the facility as part of facility security.

[0004] While advances in video surveillance technology have increased the capabilities and popularity of such systems, many drawbacks that limit the value of these systems remain. For example, while camera technology has improved significantly, the amount of data generated by such systems continues to grow. This raises the question of how to effectively store large amounts of video data in a way that is easily retrieved or otherwise processed. As a result, effective management of video surveillance data has become increasingly difficult.

[0005] Proposed methods for managing video surveillance systems include using network video recorders to capture and store video data, or using enterprise servers for video data management. As will be explained in more detail below, such methods each present unique challenges. Therefore, a need remains for improved video surveillance systems with robust video data management and access. Summary of the invention

[0006] The present disclosure generally relates to a distributed video surveillance system that includes distributed processing resources capable of processing and / or storing video data from multiple video cameras at multiple camera nodes. A particular aspect of the present disclosure includes reallocating multiple video cameras from a first camera allocation configuration to a second camera allocation configuration to camera nodes in the distributed video management system, such that the second camera allocation configuration includes selectively disconnecting or "dropping" the camera's communications with any camera node. That is, cameras can be selectively removed from the system based on a priority value assigned to each camera (e.g., to reduce the computational load on the camera nodes of the system when the collective system computing capacity has been exceeded). The disconnected camera can then be re-added by associating the disconnected camera with the camera node (e.g., in response to the computing capacity being below a threshold).

[0007] Thus, a first aspect of the present disclosure includes a method for processing video data in a video surveillance system. The method includes capturing video data at a plurality of video cameras, and transmitting the video data from the plurality of video cameras to at least one camera node over a communication network according to a first camera allocation configuration. The method also includes executing a video processing module at the at least one camera node to process the video data received at the at least one camera node from at least two or more cameras in a subset of the plurality of video cameras. The method includes monitoring a camera allocation parameter at the at least one camera node. The camera allocation parameter is based at least in part on a priority value assigned to each video camera in the subset of the plurality of video cameras. The method also includes modifying the first camera allocation configuration to a second camera allocation configuration different from the first camera allocation configuration in response to the camera allocation parameter. The second camera allocation includes disconnecting the disconnected camera from the subset of the video cameras based on the priority value of at least one disconnected camera.

[0008] Another aspect of the present disclosure includes a video surveillance system. The system includes: a plurality of video cameras operable to capture video data; at least one camera node operable to receive video data from one or more of the plurality of video cameras according to a first allocation configuration; and a video processing module executed at the at least one camera node to process the video data received at the at least one camera node. The system also includes a master node operable to communicate with the at least one camera node to monitor camera allocation parameters based at least in part on a priority assigned to each of the plurality of video cameras, and in response to the camera allocation parameters, modify the first camera allocation configuration to a second camera allocation configuration, wherein the second camera allocation includes disconnecting the disconnected camera from a subset of the video cameras based on a priority value of at least one disconnected camera.

[0009] This Summary is provided to introduce some concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.

[0010] Other implementations are also described and described herein. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] Figure 1 Two examples of prior art video surveillance systems are depicted.

[0012] Figure 2 An example of a distributed video surveillance system according to the present disclosure is depicted.

[0013] Figure 3 A schematic diagram depicting an example master node of a distributed video surveillance system.

[0014] Figure 4 A schematic diagram depicting an example camera node of a distributed video surveillance system.

[0015] Figure 5 Depicts an example of an abstract camera layer, processing layer, and storage layer for a distributed video surveillance system.

[0016] Figure 6 An example of a client in operable communication with a distributed video surveillance system to receive real-time data for presentation in a native browser interface of the client is depicted.

[0017] Figure 7 An example of distributed video analytics for a distributed video surveillance system is depicted.

[0018] Figure 8 An example of a first camera allocation configuration for multiple video cameras and camera nodes of a distributed video management system is depicted.

[0019] Fig. 9 An example of a second camera allocation configuration for a plurality of video cameras and camera nodes of a distributed video management system in response to detecting that a camera node is unavailable is depicted.

[0020] Fig.10 An example of a second camera allocation configuration for a plurality of video cameras and camera nodes of a distributed video management system in response to a change in an allocation parameter at one of the camera nodes is depicted.

[0021] Fig.11 An example of a second camera allocation configuration for a plurality of video cameras and camera nodes of a distributed video management system is depicted in which a video camera is disconnected from any camera node based on a priority of the video camera.

[0022] Fig.12 Depicted are example operations for reallocating cameras in a distributed video management system, wherein at least one camera is selectively disconnected based on a priority value of the camera.

[0023] Fig.13 A processing device is depicted that can facilitate aspects of the present disclosure. DETAILED DESCRIPTION

[0024] Although the examples in the following disclosure are susceptible to various modifications and alternative forms, specific examples are shown in the drawings and described in detail herein. However, it should be understood that it is not intended to limit the scope of the present disclosure to the specific forms disclosed, but the present disclosure will cover all modifications, equivalents and alternatives within the scope defined by the claims.

[0025] Figure 1 Two prior art approaches to system architecture and management of video surveillance systems are described. These two approaches include Figure 1 The top portion of the device-based system 1 and Figure 1 20. In the device-based system 1, a video camera 10 is in operative communication with a network 15. A device 12 is also in communication with the network 15. The device 12 receives video data from the video camera 10 and displays the video data on a monitor 14 connected to the device 12.

[0026] Given the simplicity of the hardware required to implement the system 1, the device-based system 1 generally provides a relatively low-cost solution. However, due to the limited processing power of most devices 12, the number of cameras supported by the device-based system may be limited, because all video cameras 10 only provide video data to the device 12 for processing and display on the display 14. In addition, the system is not scalable, because once the processing power of the device 12 is reached (e.g., due to the number of cameras in the system 1), expansion of additional cameras cannot be provided. Instead, in order to supplement the system 1, a completely new device 12 must be implemented as a separate stand-alone system without integration with the existing device 12. In addition, due to the relatively limited processing power of the device 12, the device-based system 1 provides limited capabilities for video data analysis or storage capacity. In addition, such systems 1 generally facilitate viewing and / or storing a limited number of real-time video data feeds from the video camera 10 at any given time, and generally allow such videos to be presented only on a single monitor 14 or a limited number of monitors connected to the device 12. That is, in order to review real-time or archived video data, a user must be physically present at the location of the device 12 and monitor 14.

[0027] The enterprise server-based system 20 typically includes a plurality of video cameras 10 in operable communication with a network 15. A server instance 16 also communicates with the network 15 and receives all video data from all cameras 10 for processing and storing the data. The server 16 typically includes a storage array and acts as a digital video recorder (DVR) to store the video data received from the cameras 10. Clients 18 may be connected to the network 15. The clients 18 may allow a physical location remote from the server 16 to view the video data from the server 16 (e.g., as opposed to the device-based system 1 in which the monitor 14 is directly connected to the device 12). However, the server 16 typically includes platform-dependent proprietary software for digesting the video data from the cameras 10 for storage in the storage array of the server 16.

[0028] Additionally, the server 16 and the clients 18 include platform-dependent proprietary software to facilitate communications between the server 16 and the clients 18. Thus, a user or enterprise must purchase and install a platform-dependent client software package on any client 18 that it desires to use to access video data and / or control the system 20. This limits the ability of users to access video data from the system 20 because any user must have access to a pre-configured client 18 equipped with the appropriate platform-dependent proprietary software, which requires additional costs to license such software.

[0029] Compared to the appliance-based system 1, the enterprise server-based system 20 is typically a relatively expensive implementation that can be installed for large enterprises. For example, when a single server 16 handles all processing and storage of all video data from the system, such a system 20 typically requires a very powerful server 16 to facilitate the management of video data from the cameras 10. In addition, the platform of the server 16 and the client 18 relies on proprietary software that requires the payment of licensing fees, which can be based on the number and / or features (e.g., data analysis features) of the cameras 10 available to the user. Further, the proprietary software that enables the functionality of the client 18 must be installed and configured as a separate software package. In turn, installing and maintaining the software at the client 18 may increase the complexity of the system 1. Further, if a user wishes to use different client 18 devices, the software resources required for operation must first be provided to any such device. Therefore, the ability to access and manage the system 1 is limited.

[0030] While such an enterprise server-based system 20 can be scaled, the capital cost of expansion of the system 20 is high. Specifically, while the server 16 does have a limit on the number of cameras 10 it can support relative to the increased computational complexity of the device 12, this limit is typically higher than the number of cameras 10 that the device 12 can support. In any respect, once the maximum number of cameras 10 is reached, any additional cameras 10 actually require the use of additional servers 16 or the purchase of new systems 20 by increasing the capacity of the server 16 and paying for license fees to increase the additional servers 16 or capacity. In addition, the proprietary software that needs to be installed at the client 18 is typically platform dependent and is required for any client 18 that wishes to interact with the system 20. This increases the complexity and cost of any client 18 and limits the functionality of the system 20. Further, the enterprise server-based system 20 includes a static camera-to-server mapping such that in the event of a server unavailability or failure, all cameras 10 mapped to the server 16 become unavailable for real-time video streaming or storage of video data, thereby rendering the system 20 ineffective in the event of such a failure.

[0031] Therefore, the present disclosure is directed to a distributed video management system (VMS) 100 including a distributed architecture. An example of such a VMS 100 is depicted in Figure 2. The distributed architecture of the VMS 100 helps achieve many benefits over the device-based system 1 or server-based system 20 described above. In general, the VMS 100 includes three functional layers that can be abstracted relative to each other to provide the ability to dynamically reconfigure the mapping between the video camera 110, the camera node 120 for processing video data, and the storage capacity 150 / 152 within the VMS 100. Although this is discussed in more detail below, the abstraction of the functional layers of the VMS 100 promotes a highly dynamic and configurable system that is easy to expand, robust to component failures, adaptable to given events, and can be installed and operated cost-effectively. Because the functional layers are abstract, there is no need to utilize static component-to-component mapping. That is, any one or more video cameras 110 can be associated with any one of a plurality of camera nodes 120, and the plurality of camera nodes can receive video data from the associated video camera 110 to process video data from the associated video camera 110. The camera node 120 then processes the video data (e.g., for storage in the storage volume 150 / 152 or for real-time streaming to the client device 130 for real-time viewing of the video data). The camera node 110 is operable to perform video analytics on the video data of the associated camera 110 or on stored video data from (e.g., of the associated video camera 100 or of a non-associated video camera 110). Further, when storage resources of the system 100 are also drawn from the camera node 120, the video data can be stored in a flexible manner that allows retrieval by any camera node 120 of the system.

[0032] In this regard, upon failure of any given node in the system, the camera assigned to the failed camera node can be reassigned (e.g., automatically) to another camera node so that processing of video data is virtually uninterrupted. In addition, the association of cameras to nodes can be dynamically modified in response to actual processing conditions at the node (e.g., a camera can be associated from a node performing complex video analysis to another node). Similarly, because the camera nodes 120 can be relatively inexpensive hardware components, additional camera nodes 120 can be easily added (e.g., in a plug-and-play manner) to the system 100 to provide highly granular scalability (e.g., relative to having to deploy entirely new server instances in the case of a server-based system 20 that only provides low granular scalability).

[0033] The flexibility of the VMS system 100 extends to the client 130 in the system. The client 130 may refer to a client device or software delivered to a device to be executed at the device. In any respect, the client 130 may be used to view the video data of the VMS 100 (e.g., in real time or from the storage device 150 / 152 of the system 100). Specifically, the present disclosure contemplates the use of a standard web browser application that is generally available and executable on various computing devices. As described in more detail below, the VMS 100 may utilize the processing power at each camera node 120 to process the video data into an appropriate transmission mechanism, which may be based at least in part on the context of the request for the video data. As an example, a request from a client 130 for viewing real-time video data from a camera 110 in real time may cause the camera node 120 to process the video data of the camera 110 into a real-time, low-latency format to be delivered to the client 130. Specifically, such a low-latency protocol may include a transport mechanism that allows data to be received and presented at the client using a standard web browser, using only the native functionality of a standard web browser, or through executable instructions provided by a web page sent to the client 130 for presentation in a standard web browser (e.g., without the need to install external software at the client in the form of a third-party application, browser plug-in, browser extension, etc.). Subsequently, any computing device that executes a standard web browser can be used as a client 130 to access the VMS 100, without requiring any proprietary or platform-dependent software, and without requiring any pre-configuration of the client 130. This can allow access by any computing system operating any operating system, as long as the computing device is capable of executing a standard web browser. Thus, a desktop computer, laptop computer, tablet computer, smart phone, or other device can act as a client 130.

[0034] The abstract architecture of the VMS 100 may also allow for flexible processing of data. For example, the camera node 120 of the VMS 100 may apply an analysis model to video data processed at the camera node 120 to perform video analysis on the video data. The analysis model may generate analysis metadata about the video data. Non-limiting examples of analysis methods include object detection, object tracking, face recognition, pattern recognition / detection, or any other appropriate video analysis technology. Given the abstraction between the video camera 110 and the camera node 120 of the VMS 100, the configuration of the processing of the video data may be flexible and adaptable, which may allow even relatively complex analysis models to be applied to some or all of the video data, thereby being dynamically preconfigured in response to peak analysis loads.

[0035] Continue to refer Figure 2, schematically depicts a VMS 100 for managing edge monitoring devices in a monitoring system according to the present disclosure. The VMS 100 includes a plurality of cameras 110, each of which is operatively in communication with a network 115. For example, Figure 2 As shown, cameras 110a to 110g are shown. However, it should be understood that additional or fewer cameras may be provided in the VMS 100 according to the present disclosure without limitation.

[0036] The camera 110 may be an Internet Protocol (IP) camera capable of providing packetized video data from the camera 110 for transmission over a network 115. The network 115 may be a local area network (LAN). In other examples, the network 115 may be any suitable communications network, including a public switched telephone network (PSTN), an intranet, a wide area network (WAN) such as the Internet, a digital subscriber line (DSL), a fiber optic network, or other suitable networks without limitation. The video cameras 110 may each independently be associated with (e.g., may be assigned to) a given one of the plurality of camera nodes 120.

[0037] Therefore, the VMS 100 further includes a plurality of camera nodes 120. For example, Figure 2 , three camera nodes 120 are shown, including a first camera node 120a, a second camera node 120b, and a third camera node 120c. However, it should be understood that additional or fewer camera nodes 120 may be provided without departing from the scope of the present disclosure. In addition, camera nodes 120 may be added to or removed from the system 100 at any time, in which case the assignment or mapping of cameras to nodes may be automatically reconfigured. Each camera node 120 may also be in operative communication with the network 115 to facilitate receiving video data from one or more of the cameras 110 associated with each respective node 120.

[0038] The VMS 100 also includes at least one master node 140. The master node 140 is operable to manage the operation and / or configuration of the camera nodes 120 to receive and / or process video data from the cameras 110, coordinate storage resources of the VMS 100, generate and maintain a database related to captured video data of the VMS 100, and / or facilitate communication with the clients 130 for accessing video data of the system 100.

[0039] Although a single master node 140 is shown and described, the master node 140 may include camera nodes 120 that are responsible for certain system management functions. Not all management functions of the master node 140 need to be performed by a single camera node 120. In this regard, although a single master node 140 is described for simplicity, it is understood that the master node functions described herein with respect to a single master node 140 may actually be distributed among different camera nodes in the camera nodes 120. Thus, a given camera node 120 may act as a master node 140 for coordinating camera assignments of the camera nodes 120, while another camera node 120 may act as a master node 140 for maintaining a database of video data about the system. Thus, as will be described in more detail below, the various management functions of the master node 140 may be distributed among various camera nodes in the camera nodes 120. Thus, although a single given master node 140 is shown, it is understood that any of the camera nodes 120 may act as a master node 140 for different corresponding functions of the system 100.

[0040] In addition, the various management functions of the master node 140 can be subject to dominant selection to distribute such functions to different ones of the camera nodes 120 to perform the master node functions. For example, the role of the master node 140 can be assigned to a given camera node 120 using the dominant selection technique, so that all management functions of the master node 140 are assigned to the given camera node 120. Alternatively, individual ones of the management functions can be individually assigned to one or more camera nodes 120 using dominant selection. This provides a robust system in which even the unavailability of a master node 140 or camera node 120 that performs some management functions can be easily corrected by applying dominant selection to select a new master node 140 in the system or to reallocate management functionality to a new camera node 120.

[0041] The hardware of the camera nodes 120 and the master nodes 140 may be identical. In other examples, a dedicated master node 140 may be provided that may have different processing capabilities (e.g., more or less powerful hardware in terms of processor and / or memory capacity) than other camera nodes 120. In addition, not all camera nodes 120 have the same processing capabilities. For example, some camera nodes 120 may include increased computing specifications relative to other camera nodes 120, including, for example, increased memory capacity, increased processor capacity / speed, and / or increased graphics processing capabilities.

[0042] As can be appreciated, the VMS 100 can store video data from the video camera 110 in a storage resource of the VMS 100. In one embodiment, storage capacity can be provided in one or more different example configurations. Specifically, in one example, each camera node 120 and / or master node 140 can have an attached storage device 152 at each respective node. In this regard, each respective node can store the video data metadata processed by the node and any metadata generated at the node at the corresponding attached storage device 152 at each respective node for video data processed at the node 120. In an alternative arrangement, the storage device 152 locally attached at each camera node 120 and the master node 140 may include a physical drive abstracted into a logical storage unit 150. In this regard, it is possible that the video data processed at a first node in the node can be at least partially transmitted to another node in the node for storing data. In this regard, the logical storage unit 150 can be presented as an abstract storage device or storage resource accessible by any node 120 of the system 100. The actual physical form of the logical storage unit 150 may take any suitable form or combination of forms. For example, the physical drives associated with each node may include a storage array, such as a RAID array, which forms a single virtual volume that can be addressed by any camera node 120 or master node 140. Additionally or alternatively, the logical storage unit 150 may be in operative communication with a network 115 with which the camera nodes 120 and master node 140 also communicate. In this regard, the logical storage unit 150 may include a network attached storage (NAS) device capable of receiving data from any camera node 120. The logical storage unit 150 may include a storage device local to the camera node 120, or may include a remote storage device, such as a cloud-based storage resource, etc. In this regard, although both the logical storage unit 150 and the locally attached storage device 152 are shown in Figure 2 , but the locally attached storage device 152 may include at least a portion of the logical storage unit 150. In addition, the VMS 100 does not necessarily include two types of storage devices, which is only for illustration purposes. Figure 2 Shown in.

[0043] Further references Figure 3, a schematic diagram illustrating an example of a master node 140 is shown. The master node 140 may include multiple modules for managing the functionality of the VMS 100. As described above, although a single master node 140 including a master node module is shown, it should be understood that any camera node 120 can act as a master node 140 for any individual functionality of the master node module. That is, the role of the master node 140 for any one or more of the master node functionalities can be distributed between the camera nodes 120. In any aspect, the modules corresponding to the master node 140 may include a web server 142, a camera distributor 144, a storage manager 146, and / or a database manager 148. In addition, the master node 140 may include a network interface 126, which facilitates communication between the master node 140 of the VMS 100 and the video camera 110, the camera node 120, the storage device 150, the client 130, or other components.

[0044] The web server 142 of the master node 140 can coordinate communications with the client 130. For example, the web server 142 can transmit a user interface (e.g., HTML code that defines how the browser renders the user interface) to the client 130, which allows the client 130 to render the user interface in a standard browser application. The user interface may include design elements and / or code for retrieving and displaying video data from the VMS 100 in a manner described in more detail below.

[0045] With respect to the camera distributor 144, the master node 140 can facilitate camera allocation or assignment, so that the camera distributor 144 creates and executes a camera-to-node mapping to determine which camera node 120 is responsible for processing video data from the video camera 110. That is, a subset of the video cameras 110 of the VMS 100 can be assigned to different camera nodes 120 compared to the device-based system 1 or the enterprise server-based system 50. For example, the camera distributor 144 is operable to communicate with the camera 110 to provide the video camera 110 with instructions about the camera node 120 to which the video camera 110 will send its video data. Alternatively, the camera distributor 144 can instruct the camera node 120 to establish communication with and receive video data from a specific video camera in the video cameras 110. The camera distributor 144 can create such a camera-to-node association and record the association in a database or other data structure. In this regard, the system 100 can be a distributed system because any one of the camera nodes 120 can receive and process video data from any one or more of the video cameras 110.

[0046] In addition, the camera distributor 144 is operable to dynamically reconfigure the mapping of cameras to nodes during the load balancing process. In this regard, the camera distributor 144 can monitor the allocation parameters at each camera node 120 to determine whether to modify the mapping of the camera to the node. In this regard, changes in the VMS 100 can be monitored, and the camera distributor 144 can respond to modify the camera allocation from a first camera allocation configuration to a second camera allocation configuration to improve or maintain system performance. The allocation parameters can be any one or more of a plurality of parameters that are monitored and used to determine the camera allocation. Therefore, the allocation parameters can change in response to many events that may occur in the VMS 100, as described in more detail below.

[0047] For example, in the case of a failure, power loss, or another event that causes a camera node 120 to be unavailable, the camera distributor 144 may detect or otherwise be notified that the camera node is unavailable. Subsequently, the camera distributor 144 may reassign the video camera previously associated with the unavailable node to another node 120. The camera distributor 144 may communicate with the reassigned camera 110 to update the instructions for communicating with the new camera node 120. Alternatively, the newly assigned camera node may assume the role of establishing contact with and processing video data from the video camera 110, which previously communicated with the unavailable camera node 120 to update the instructions and establish a new camera-to-node assignment based on the new assignment provided by the camera distributor 144. In this regard, the system 100 provides increased redundancy and flexibility related to processing video data from the camera 100. Further, even in the absence of a camera node 120 failure, the video data feed of the camera 110 may be load balanced to the camera node 120 to allow different analysis models, etc. to be applied.

[0048] A given camera node 120 may be paired with a subset of cameras 110, the subset including one or more of the cameras 110. As an example, in Figure 2 , cameras 110a-110c may be paired with camera manager 120a such that camera manager 120a receives video data from cameras 110a-110c. Cameras 110d-110f may be paired with camera manager 120b such that camera manager 120b receives video data from cameras 110d-110f. Camera 110g may be paired with camera manager 120c such that camera manager 120c receives video data from camera 110g. However, this configuration may change in response to load balancing operations, failure of a given camera node, network conditions, or any other parameter.

[0049] For example, refer to Figure 8 , showing a first camera allocation configuration. Two camera nodes, camera node 120a and camera node 120b, can process data from video cameras 110a - 110e via network 115 . Fig. 9 is a schematic representation for illustration. Thus, although camera 110 is shown as communicating directly with node 120, camera 110 may communicate with node 120 via a network connection. Similarly, although master node 140 is shown as communicating directly with camera node 120, such communication may also be via network 115 ( Figure 8 In any respect, Figure 8 In the first camera allocation configuration shown, video camera 110a, video camera 110b, and video camera 110c transmit video data to first camera node 120a for processing and / or storing the video data by first camera node 120a. In addition, video camera 110d and video camera 110e transmit video data to second camera node 120b for processing and / or storing the video data by first camera node 120b. The first camera allocation can be established by camera distributor 144 of master node 140 in a manner that distributes the mapping of video cameras 110 among available camera nodes 120 to balance the allocation parameters among camera nodes 120.

[0050] Upon detecting a change in the allocation parameter, the camera allocator 144 may modify the first camera allocation in response to detecting the change in the monitored allocation parameter. For example, such a change may be in response to adding or removing a camera node 120 from the VMS 100 when the computational load at the camera node 120 changes, when the video data from the video camera 110 changes, or when any other change causes a change in the allocation parameter. For example, further reference Fig. 9 , depicting a scenario in which camera node 120b becomes unavailable (e.g., due to a loss of communications at camera node 120b, a loss of power at camera node 120b, or any other failure or condition that causes camera node 120b to lose the ability to process and / or store video data). In response, master node 140 may detect such a change and change the first camera allocation configuration from Figure 8 The camera allocation configuration shown is modified to a second camera allocation configuration, such as Fig. 9 shown.

[0051] exist Fig. 9 In the second camera allocation configuration shown, all cameras 110a-110e are mapped to communicate with camera node 120a. However, it should be understood that other camera nodes 120( Fig. 9100) may also have one or more of the video cameras 110d and the video cameras 110e assigned to any available node 120 in the VMS 100. Thus, only two camera nodes 120a and 120b are shown for simplicity of explanation. In this regard, the modification of the camera allocation configuration may be based at least in part on the allocation parameters. That is, the camera allocation parameters may be used to load balance the system based on the video data of the camera 110 on all available camera nodes 120 (e.g., based on the allocation parameters). Thus, although all video cameras 110 may be reallocated to any available node 120, the camera allocation parameters may be used to load balance the system based on the video data of the camera 110 on all available camera nodes 120. Fig. 9 The first camera node 120a is used in the example embodiment, but cameras 110d and 110e may be allocated to alternative camera nodes in other ways to balance the computational load and storage load or other allocation parameters across all available nodes 120.

[0052] In addition, although the camera node 120 is Fig. 9 Another scenario that is shown as unavailable in FIG. 1 , but in which load balancing may occur, is that one or more camera nodes 120 are added to the system, so that one or more additional camera nodes may become available. In this scenario, a new camera allocation configuration may be generated to balance the video data processing of all cameras 110 in the VMS 100 with respect to allocation parameters based on the video data generated by the cameras 110. In this regard, it is understood that changes in the allocation parameters monitored by the camera distributor 144 of the master node 140 may occur in response to any number of conditions, and such changes may result in modifications to the existing camera allocation configuration.

[0053] Thus, the allocation parameters may be related to the video data of the camera node 110 being allocated. For example, the allocation parameters may be related to time-based parameters, the spatial coverage of the camera, the computational load of processing the video data of the camera, the assignment category of the camera, and the assignment priority of the camera. The allocation parameters may be at least partially affected by the nature of the video data of a given camera. For example, a given camera may present video data that is more computationally demanding than another camera. For example, a first camera may be facing the main entrance of a building. A second camera may be located in an internal corridor with little traffic. Video analysis may be applied to two sets of video data from the first camera and the second camera to perform face recognition. The video data from the first camera may have higher computational requirements for the camera node than the video data from the second camera, simply because the nature / location of the first camera is located at the main entrance and includes many faces compared to the second camera. In this regard, the camera allocation parameters may be based at least in part on the video data of a specific camera to be allocated to the camera node.

[0054] in this regard, Fig.10Another scenario is depicted in which a change in a camera allocation parameter is detected, and the camera allocation configuration is modified in response to the change. Fig.10 You can Figure 8 The first camera allocation configuration is changed to Fig.10 The second camera allocation configuration shown in . Fig.10 , video camera 110e may begin capturing video data that causes the computational load on camera module 120b to increase beyond a threshold. Subsequently, camera allocator 144 of master node 140 may detect this change and modify the first camera allocation configuration to a second camera allocation configuration such that camera 110d is associated with camera node 120a. That is, camera node 120b may be dedicated to processing video data from camera 110e in response to a change in the video that increases the computational load for processing this video data. An example may be video data that includes a significant increase in detected objects (e.g., additional faces to be processed using face recognition) or motion to be processed. In Fig.10 In the example shown, camera node 120a may have sufficient capacity to process video data from camera 110d.

[0055] Fig.11 An example is further shown in which the total computing capacity of the VMS 100 based on the available camera nodes 120 is exceeded. Fig.11In the depicted scenario, camera 110d may be disconnected from any camera node 120 so that the video data of camera 110d may not be processed by VMS 100. That is, if the total VMS 100 capacity is exceeded, the camera may be selectively "abandoned". The camera may have an assigned priority value, which may be based in part on the allocation parameters described above. For example, if two cameras with overlapping spatial coverage are provided (e.g., one camera monitors an area from a first direction, and the other camera monitors the same area from a different direction), one of the cameras with overlapping spatial coverage may have a relatively low priority. Then, when one of the cameras is disconnected, the continuity of monitoring the area covered by the camera may be maintained while reducing the computational load of the system. When the available computational load is restored (e.g., due to changes in the computational load of other cameras or by adding another node to the system), the disconnected camera may be reallocated to the camera node using a load balancing method. In other cases, other allocation parameters may be used to determine priorities, including establishing camera categories. For example, a camera may be assigned to an "internal camera" category or a "surrounding camera" category based on whether the camera's location / field of view is inside or outside the facility. In this case, one type of camera may be prioritized over another type of camera based on a specific scenario occurring, which may be related to the VMS 100 (e.g., computing capacity / load of the VMS 100) or an external event (e.g., an alarm at the facility, a shift change at the facility, etc.).

[0056] The master node 140 may also include a storage manager 146. The video data captured by the camera 110 is processed by the camera node 120 and once processed can be stored in a persistent storage device. The video data generated by the VMS 100 may include a relatively large amount of data for storage. Therefore, the VMS 100 can generally implement a storage strategy for capturing and / or storing video data by the VMS 100. As will be described in more detail below, the abstract storage resources of the VMS 100 facilitate the camera node 120 to persistently store the video data in a manner that any camera node 120 may be able to access the stored video data regardless of the camera node 120 that processes the video data. Therefore, any camera node 120 may be able to retrieve and reprocess the video data according to the storage strategy.

[0057] For example, the storage policy may indicate that video data of a predefined currency (e.g., video data captured within the last 24 hours of VMS 100 operation) may be stored in its entirety at the original resolution of the video data. However, long-term storage of such video data at full resolution and full frame rate may be impractical or infeasible. Therefore, the storage policy may include an initial period of full data retention, wherein all video data is stored at full resolution, and subsequent processing of the video data after the initial period to reduce the size of the video data on disk.

[0058] To this end, the storage policy may specify other parameters that control how video data is stored or whether such data is retained. The storage manager 146 may execute the storage policy based on the parameters of the storage policy regarding the stored video data. For example, based on the parameters defined in the storage policy, the video data may be deleted or stored at a reduced size (e.g., by reducing the video resolution, frame rate, or other video parameters to reduce the overall size of the video data on disk). Reducing the size of the video data stored on disk may be referred to as "pruning." One such parameter that governs the pruning of video data may be related to the amount of time that has passed since the video data was captured. For example, the size of data older than a given period (e.g., greater than 24 hours) may be deleted or reduced. Further, multiple pruning stages may be performed so that as the video becomes less recent, the size of the data is further reduced or deleted.

[0059] Furthermore, since any camera node 120 is operable to retrieve any video data from storage for reprocessing, video data may be reprocessed (e.g., truncated) by a camera node different from the camera node that originally processed and stored the video data from the video camera. Thus, the reprocessing or truncating may be performed by any camera node 120. Reprocessing of video data by a camera node may be performed during idle periods of a camera node 120 or when it is determined that a camera node 120 has spare computing capacity. This may occur at different times for different camera nodes, but may occur during times of low processing load, such as after business hours or during times when a facility is closed or activity is reduced.

[0060] Further, the parameters for deletion can be related to the analysis metadata of the video data. As described in more detail elsewhere in this application, the camera node 120 may include an analysis model to apply video analysis to the video data processed by the camera module. Such video analysis may include generating analysis metadata about the video. For example, the analysis model may include object detection, object tracking, face recognition, pattern detection, motion analysis, or other data extracted from the video data when the analysis model is used for analysis. The analysis metadata may provide parameters for data deletion. For example, any video data without motion may be deleted after the initial retention period. In another example, only video data including specific analysis metadata may be retained (e.g., only video data in which a given object is detected may be stored). Further, only data from a specific camera 110 may be retained beyond the initial retention period. Therefore, very valuable video data feeds (e.g., video data related to key locations such as building entrances or highly secure areas of facilities) may be maintained without reducing size. In any aspect, the storage manager 146 may manage the application of such storage strategies to video data stored by the VMS 100.

[0061] The master node 140 may also include a database manager 148. As described above, the video camera 110 may be associated with any camera node 120 for processing and storing video data from the video camera 120. In addition, the video data may be stored in an abstract manner in a logical storage unit 150, which may or may not be physically co-located with the camera node 120. Therefore, the VMS 100 may advantageously maintain a record of the video data captured by the VMS 100 to provide important system metadata about the video data. In addition to other potential information, such system metadata may also include: which video camera 110 captured the video data, the time / date when the video data was captured, which camera node 120 processed the video data, which video analysis was applied to the video data, resolution information about the video data, frame rate information about the video data, the size of the video data, and / or the location where the video data is stored. Such information may be stored in a database generated by the database manager 148. The database may include correlations between the video data and the system metadata related to the video data. In this regard, the provenance of the video data may be recorded by the database manager 148 and captured into the resulting database. The database may be used to manage video data and / or track the flow of video data through the VMS 100. For example, as described above, the storage manager 146 may utilize the database to apply storage policies to the data. In addition, a request for data from a client 130 may include a reference to a database to determine the location of video data to be retrieved for a given parameter (such as any one or more of the metadata portions described above). The database may be generated by the database manager 148, but the database may be distributed among all camera nodes 120 to provide redundancy to the system in the event that a master node 140 executing the database manager 148 fails or is unavailable. Database updates corresponding to any given camera node 120 may be driven by a particular event, or may occur at predetermined time intervals.

[0062] The database may also associate the video data with analytical metadata about the video data. For example, as described in more detail below, the analytical metadata may be generated by applying video analytics to the video data. Such analytical metadata may be embedded in the video data itself, or provided as a separate metadata file associated with a given video data file. In either aspect, the database may associate such analytical metadata with the video data. This may be helpful in pruning activities or searching for video data. With respect to the former, as described above, pruning according to a storage policy may include processing video data based on analytical metadata (e.g., based on the presence or absence of a moving or detected object). In addition, a search performed by a user may request all video data in which a particular object or similar situation is detected.

[0063] Further references Figure 4, shows an illustrative example of a camera node 120. As can be understood from the foregoing, the camera node 120 may include an instance of a database 132 provided by a master node 140 executing a database manager 148. In this regard, the camera node 120 may reference the database for retrieving and / or providing video from a logical storage volume of the VMS 100 and / or for reprocessing video data (e.g., according to a storage policy).

[0064] The camera node 120 may include a video analytics module 128. The video analytics module 128 may be operable to apply an analytics model to video data processed by the camera node 120 upon receipt from the camera 110. The video analytics module 128 may apply a machine learning model to the video data processed at the camera node 120 to generate analytics metadata. For example, as described above, the video analytics module 128 may apply a machine learning model to detect objects, track objects, perform face recognition, or other analysis of the video data, which in turn may result in the generation of analytics metadata about the video data.

[0065] The camera node 120 may also include a module suitable for processing video data into an appropriate transmission mechanism based on the nature of the data or the intended use of the data. In this regard, the camera node 120 includes a codec 122 (i.e., an encoder / decoder) that can decode the received data and re-encode the data into a different encoded video format. The encoded video format may include packetized data so that each data packet is encoded according to the selected encoded video format. The camera node 120 may also include a container formatter 124 that can package the encoded video packets into an appropriate container format. The camera module 120 also includes a network interface 126 that is operable to determine a communication protocol for transmitting the encoded video packets in the digital container format.

[0066] Formatting the video data into an appropriate transport mechanism can allow for optimized delivery and / or storage of the video data. For example, the video data can be delivered from the camera 110 to the camera node 120 using a real-time streaming protocol (RTSP). However, RTSP may not be the best protocol for storing and / or delivering the video data to the client 130 (e.g., RTSP is not typically supported by standard web browsers, and therefore, typically requires specific software or plug-ins (such as a specific video player) to present the video in the browser display). The camera node 120 can reformat the video data into an appropriate transport mechanism based on the context in which the video data is requested.

[0067] After selecting the appropriate communication protocol, the network interface 126 can use the communication protocol to transmit the encoded video packets to a standard web browser of the client device. In one example, the client 130 can request to view the video data from a given video camera 110 in real time. Therefore, the codec 122, the container formatter 124 and the network interface 126 can respectively select the appropriate encoded video format, container format and communication protocol to facilitate the transmission mechanism to provide the video data to the client 130 in real time. In contrast, the client 130 can alternatively request the video data from the logical storage unit of the VMS 100. As can be understood, the circulation of such data is not as important as in the case of real-time data. Different one or more of the encoded video format, container format and communication protocol can be selected. For example, in this case where the circulation of data is not too important, a more flexible or more bandwidth-efficient encoded video format, container format and communication protocol can be selected, which has a higher delay in providing video to the client 130.

[0068] For purposes of illustration and not limitation, the transport mechanism may include any combination of encoded video formats, container formats, and communication protocols. Example transport mechanisms include JSMpeg, HTTP Live Streaming (HLS), MPEG-1, and WebRTC. JSMpeg utilizes MPEG-1 encoding (e.g., MPEG-TS splitter, WebAssembly MPEG-1 video decoder, and MPEG-2 audio decoder). In this regard, the JSMpeg transport mechanism uses a transport stream (TS) container format and a WebSocket communication protocol. Subsequently, the JSMpeg transport mechanism may be decoded at the client 130 using a JSMpeg program, which may be included in a web page (e.g., HTML code sent to a browser, etc.), and does not require the use of plug-ins or other applications other than native web browsers. For example, the JSMpeg transport mechanism may use a WebGL&Canvas2D rendering program and WebAudio sound output. The JSMpeg transport mechanism may provide extremely low latency for video data, but utilizes slightly higher bandwidth consumption relative to other transport mechanisms described herein.

[0069] Another transport mechanism may be WebRTC, which may utilize H.264 encoding, VP8, or another encoding. WebRTC may utilize container formats including MPEG-4 or WebM. The communication protocol of WebRTC may include an RTC peer connection to provide signal transmission. Video may be delivered using WebSocket. In the WebRTC transport mechanism, a standard browser may include a native decoder for decoding encoded video data. WebRTC provides extremely low latency for video data, but increases the complexity of the system by using a signaling server in the form of an RTC peer connection. However, the bandwidth utilization of WebRTC is relatively low.

[0070] Another transport mechanism that can be utilized includes HLS or MPEG-DASH. The encoded video format of HLS / MPEG-DASH can be MPEG-2, MPEG-4, or H.264. The container format can be MPEG-4, and the communication protocol can be HTTP. In this regard, the decoder can natively decode the encoded video data. The HLS / MPEG-DASH transport mechanism has higher latency than the other transport mechanisms described, but has robust browser support and lower network bandwidth usage.

[0071] As described above, VMS 100 may include an abstraction system that allows the capture of video data, the processing of video data, and the storage of video data to be abstracted between the various components of VMS 100. For example, further reference is made to Figure 4 , schematically depicting three "layers" of functionality of the VMS 100. Specifically, an acquisition layer 310, a processing layer 320, and a storage layer 330 are shown. The camera 110 may include the acquisition layer 310. The camera node 120 and the master node 140 may include the processing layer 320. In addition, the logical storage volume may include a storage device 150 of the storage layer 330. These layers are referred to as abstraction layers because the specific combination of hardware components that acquire, process, and store video data of the VMS system 100 may be variable and dynamically associated. That is, network communications between the hardware components of the VMS 100 may allow for abstraction of each of the acquisition, processing, and storage functions. Thus, for example, any of the cameras 110 may provide video data to any of the camera nodes 120, which may store the video data in the logical storage volume of the storage device 150 without restriction.

[0072] As described above, the VMS 100 also includes a client 130 that can be operatively communicated with the network 115. The client 130 is operable to communicate with the VMS 100 to request and receive video data from the system 100. In this regard, the VMS 100 can not only store video data from the video camera 110, but also provide a real-time stream of video data for one or more users to observe. For example, video surveillance cameras are often monitored in real time by security personnel. By "real-time" or "near real-time", it is expected that the data provided has sufficient currency for security operations. In this regard, real-time or near real-time does not require instantaneous delivery of video data, but can include delays that do not affect the effectiveness of monitoring video data, such as delays of less than 5 seconds, less than 3 seconds, or less than about 1 second.

[0073] One goal of the present disclosure is to help the client 130 to use a standard web browser application to present real-time video data to the user in a convenient manner. It is particularly noteworthy that it is particularly beneficial to allow the client 130 to execute common and low-cost applications for accessing video data (e.g., compared to requiring pre-installation and pre-configuration of the platform to rely on proprietary software to interact with the management system). In this regard, it is expected that the specific application type used at the client 130 is a standard web browser. Examples of such browsers include Google Chrome, Firefox, Microsoft Edge, Microsoft IE, Opera and / or Apple. Such standard web browsers can natively process certain data received via the network to generate a user interface on a client device. For example, such standard web browsers typically include native application programming interfaces (APIs) or other default functions to allow a web browser to present a user interface, facilitate interaction between a user and a website, etc., and establish communication between a client and a server.

[0074] The client 130 may include a standard Internet browser capable of communicating with one or more of the web server 142 and / or the camera manager 120 to access the video data of the VMS 100. Compared to the previously proposed system that relies on proprietary client software to be executed to communicate with the server for retrieving video data, the client 130 of the VMS 100 can use any standard web browser application to access the video data. The standard Internet browser application means that the browser application may not require any plug-ins, add-ons, or other programs that the browser application will install or execute, except for the functions provided natively in the browser. It should be noted that although certain functions regarding the user interface for searching, retrieving and displaying videos can be delivered to the web browser as code, etc. by the web server 142, any such functions can be provided without user interaction or pre-configuration of the web browser. Therefore, any such functions are still considered to be native functions of the web browser. In this regard, the client 130 can receive all necessary data from the web page served by the VMS 100 to facilitate access to the video data of the VMS 100 without having to download programs, install plug-ins, or otherwise modify or configure the browser application from the native configuration. That is, all necessary information and / or instructions required to receive and display a user interface and / or video data from the VMS 100 may be provided locally with a standard browser or delivered from the VMS system 100 to allow execution of the client 130. Any suitable computing device capable of executing a standard web browser application that operably communicates with the network 115 may be used as a client 130 to access the video data of the VMS 100. For example, any laptop computer, desktop computer, tablet computer, smartphone device, smart television, or another device capable of executing a standard Internet browser application may function as a client 130.

[0075] Further references Figure 6, depicting an example of VMS 100 providing video data to client 130. In this case, a reverse proxy 200 can be utilized to facilitate communication with client 130. Specifically, reverse proxy 200 can be facilitated by web server 142 of master node 140, as described above. That is, web server 142 can act as reverse proxy 200. In this regard, client 130 can be connected to reverse proxy 200. A user interface 400 including HTML or other web page content can be provided from reverse proxy 200. For example, user interface 400 provided by reverse proxy 400 can include a list 404 or searchable index of available video data from camera 110 of VMS 100. This can include a list of available real-time video data feeds for real-time delivery to client 130, or can allow access to stored video data. In the latter aspect, a search function that allows performing a search (e.g., using any video metadata, including acquisition date / time, camera identification, facility location, and / or analysis metadata, including objects identified from video data, etc.). In this regard, the web server 142 can act as a signaling server to provide information about available video data. After selecting a given portion of the video data, a request for specific video data can be issued from the client 130 to the reverse proxy 200. Then, the reverse proxy 200 can communicate with a given one of the camera nodes 120 to retrieve the requested video data. The user interface 400 may also include a video display 402. The video data can be requested by the web server 142 from the appropriate camera node 120, formatted in an appropriate transport mechanism, and delivered to the client 130 by the web server 142 acting as a reverse proxy 200 to decode and display the video data in the video display 402. Therefore, the use of the reverse proxy 200 allows all data delivered to the client 130 to be provided from a single server, which may have an appropriate security certificate that meets many security requirements of the browser.

[0076] In one example, the transmission mechanism of the camera node 120 processing data can be based at least in part on the characteristics of the request from the client 130. In this regard, the reverse proxy 200 can determine the characteristics of the request. Examples of such characteristics include the nature of the video data (e.g., real-time or archived video data), the identity of the camera 110 that captured the video data, the network location of the client 130 relative to the reverse proxy 200 or the camera node 120 that will provide the video data, or other characteristics. Based on the characteristics, the encoding video format, container format, and communication protocol are appropriately selected for processing the video data by the camera node 120. The camera node 120 can provide the video data to the reverse proxy 200 for transmission to the client 130. As described above, in at least some cases, the video data provided to the client 130 can be real-time or near real-time video data, which can be presented by the client 130 in the form of a standard web browser without the need to install a plug-in or other application at the client 130.

[0077] The user may wish to change the video data displayed in the user interface 400. The user may then select a new source of video data. In one embodiment, the transport mechanism may be configured such that new video data may be requested from the appropriate camera node 120 by the network server 142 and delivered to the user interface 400 without requiring a page reload. That is, the data in the video display 402 may typically be changed without requiring a reload of the user interface 400. This may allow for greater utility for users attempting to monitor multiple video data sources using a standard web browser.

[0078] The video data provided to the client 130 for presentation in the video display 402 may include metadata, such as analytical metadata. As described above, such analytical metadata may be related to any appropriate video analysis applied to the video data, and may include, for example, highlighting detected objects, object recognition, individual recognition, object tracking, etc. Therefore, the video data may be annotated to include some analytical metadata. The analytical metadata may be embodied in the video data, or may be provided via a separate data channel. In an example where the analytical metadata is provided via a separate channel, the client 130 may receive the analytical metadata and annotate the video data in the video display 402 when presented in the user interface 400. Further, it is understood that different types of data including the user interface 400 may be delivered to the client 130 using different transmission mechanisms. For example, the above examples of transmission mechanisms may be used to deliver video data for display in the video display 402. However, the user interface itself may communicate over a standard TCP / IP connection using HTML and a secure TLS security protocol. Further, metadata (e.g., analytical metadata) may be provided as embedded data in the video data, or may be provided as a separate data stream to be presented in the user interface 130, as described above. Where a separate data stream is used to deliver metadata, the metadata may be delivered via a different transport mechanism than the video data itself.

[0079] Return to reference Figure 5 , abstracting the functionality of the VMS 100 into various functional layers can also provide advantages related to the analysis of video data by the camera nodes 120. Specifically, the application of analytical models (e.g., machine learning modules) may be relatively computationally heavy for the camera nodes 120. Although the camera nodes 120 may be equipped with a graphics processing unit (GPU) or other specially adapted hardware to assist in performing computational loads, there may be certain instances where the processing power of a given camera node 120 may not be able to apply the analytical model to all video data from a given video camera 110. For example, in some cases, video data from a given camera 110 may be advantageously divided into different portions of the data, which may be provided to different camera nodes 120 for separate processing of different portions of the data. By "slicing" the data in this manner, analysis of different portions of the video data can be performed simultaneously at different camera nodes in the camera nodes 120, which can increase the speed and / or throughput of performing analysis on the video data.

[0080] Therefore, if Figure 7As shown, the camera 110 of the VMS 100 can be in operative communication with the network 115. At least the first node 120a and the second node 120b can also communicate with the network 115 to receive video data from the camera 110. The first node 120a can include a first analysis model 210a, and the second node 120b can include a second analysis model 210b. The first analysis model 210a can be the same as or different from the second analysis model 210b.

[0081] The video data from the video camera 110 may be divided into at least a first video portion 212 and a second video portion 214. Although referred to as video data portions, it should be understood that as little as a single frame of video data may include respective portions of video data 212 and 214. The first portion 212 of the video data may be provided to the first camera node 120a, and the second portion 214 of the video data may be provided to the second camera node 120b.

[0082] The second portion 214 of the video data may be provided to the second camera node 120b in response to a trigger detected by any one of the master node, the camera node 120a, the camera node 120b, or the camera 110. The trigger may be based on any number of conditions or parameters. For example, a periodic trigger may be established so that the second portion 214 of the video data is provided to the second camera node 120b in a periodic manner based on time, the amount of camera data, or other periodic triggers. In this regard, the first analysis model 210a may require relatively low computational complexity relative to the second analysis model 210b. Therefore, it may not be computationally efficient to provide all video data to the second camera node 120b for processing using the second analysis model 210b. However, each Nth portion (e.g., including a fixed duration, a video size on disk, or a given number of frames) may be provided from the camera 110 to the second camera node 210b, where N is a positive integer. In this regard, every hundredth of a second of video data may include the second portion 214 of video data, every thousandth of a frame of video data may include the second portion 214 of video data, and so on.

[0083] In another case, the second portion 214 of the video data may be provided to the second camera node 120b based on the system video metadata or the analytical video metadata of the first portion 212 of the video data. For example, after a given object is detected from the first portion 212 of the video data, subsequent frames of the video data including the second portion 214 of the video data may be provided to the second camera node 120b. As an example of this operation, the first camera node 120a may detect a person from the first video data portion 212 using the first analytical model 210a. Subsequently, the second portion 214 of the video data may be directed to the second camera node 120b for processing by the second analytical model 210b, which may be particularly suitable for face recognition. In this regard, the video data from the camera 110 may be directed to a specific node for processing to allow different analytical models to be applied, etc.

[0084] refer to Fig.12 , an example operation 1200 is shown according to one aspect of the present disclosure. Operation 1200 may include a capture operation 1202, in which video data is captured at a plurality of video cameras. As described above, the video cameras may be in operative communication with a network. Subsequently, operation 1200 may also include a transmission operation 1204 to transmit the video data to a plurality of camera nodes. As described above, any one or more of the plurality of cameras may transmit 1204 their respective video data to any one or more of the camera nodes. Specifically, the cameras and the camera nodes may establish communication based on a first camera allocation configuration provided by a camera distributor of a system master node (e.g., to load balance video data processed across the camera nodes based on an allocation parameter).

[0085] Operation 1200 may include processing operation 1206 to process the video data received by each respective camera node. Specifically, as described above, in at least one example, processing operation 1206 may include encoding the video data into encoded video packets, packaging the encoded video packets into a transport container, and selecting a communication protocol for transmitting the video packets. Further, processing operation 1206 may include storing the video data in a storage device of the VMS.

[0086] The monitoring operation 1208 may monitor camera allocation parameters at one or more camera nodes. The monitoring operation 1208 may include, for example, receiving status information from one or more camera nodes, monitoring system resource usage at the camera nodes, and / or monitoring network traffic. In any aspect, the operation 1200 may also include a detection operation 1210, wherein the camera allocator may detect a change in camera allocation parameters across one or more of the camera nodes. As described above, a change in camera allocation parameters at one or more camera nodes may be caused by any of a number of events, including, for example, a camera node becoming unavailable, a new camera node becoming available, an increase in computational load at a camera node, a decrease in computational load at a camera node, a change in the nature of video data received from a video camera at a camera node, a change in video analysis applied to the video data, and the like.

[0087] In response to the detection operation 1210, a modification operation 1212 can be performed to modify the first camera allocation configuration to a second camera allocation configuration different from the first camera allocation configuration. Specifically, the modification operation 1212 can be performed to balance the allocation parameters at the camera nodes in response to the changes detected in the detection operation 1210. The changes in the allocation parameters may result in exceeding the computing capacity of the system including each camera node. That is, the changes in the allocation parameters (e.g., in response to a camera node becoming unavailable or the computing load increasing) may result in exceeding the collective system resources of the system.

[0088] Furthermore, in modification operation 1212, at least one camera may be disconnected from any camera node of the system to reduce the computational load of the system. That is, in response to detecting a change in detection operation 1210, a camera may be selectively "discarded." The one or more cameras selected to be disconnected may be selected based on a priority value assigned to each camera. As described above, the priority value may be based at least in part on an allocation parameter of each camera. For example, if two cameras cover a common area in a facility, one camera may be a lower priority camera that may be selectively discarded, while the other camera may continue to provide surveillance coverage to the aforementioned area.

[0089] Furthermore, the process may be iterative, such that monitoring operations 1208, detection operations 1210, and modification operations 1212 may be performed periodically during operation of the VMS system. For example, such monitoring may be performed at a frequency sufficient to detect any changes (e.g., unavailability of a camera node) without significantly interrupting video data processing of video data from cameras assigned to the camera nodes. For example, such monitoring may be performed at a rate of at least 1 Hz, but higher frequencies may be employed without limitation.

[0090] Fig.13 An example simplified diagram of a processing device 1300 suitable for implementing various aspects of the disclosed technology is shown. For example, the processing device 1300 can generally describe the architecture of the camera node 130, the master node 140, and / or the client 130. The processing device 1300 includes one or more processor units 1302, a memory 1304, a display 1306, and other interfaces 1308 (e.g., buttons). The memory 1304 typically includes both volatile memory (e.g., RAM) and non-volatile memory (e.g., flash memory). An operating system 1310, such as Microsoft An operating system, Apple macOS operating system, or Linux operating system, resides in memory 1304 and is executed by processor unit 1302, but it will be appreciated that other operating systems may be employed.

[0091] One or more applications 1312 are loaded into the memory 1304 and executed by the processor unit 1302 on the operating system 1310. The application 1312 may receive input from various input local devices such as a microphone 1334, an input accessory 1335 (e.g., a keypad, a mouse, a stylus, a touchpad, a joystick, an instrument mounted input, etc.). Additionally, the application 1312 may be connected to a wired or wireless network (e.g., a mobile phone network, a wireless ... ) to communicate with such devices to receive input from one or more remote devices, such as remotely located smart devices. The processing device 1300 may also include various other components, such as a positioning system (e.g., a global positioning satellite transceiver), one or more accelerometers, one or more cameras, an audio interface (e.g., a microphone 1334, an audio amplifier and speaker, and / or an audio jack), and a storage device 1328. Other configurations may also be used.

[0092] Processing device 1300 also includes a power supply 1316 that is powered by one or more batteries or other power sources and provides power to other components of processing device 1300. Power supply 1316 may also be connected to an external power source (not shown) that recharges or recharges the internal batteries or other power sources.

[0093] Example implementations may include hardware and / or software embodied by instructions stored in memory 1304 and / or storage 1328 and processed by processor unit 1302. Memory 1304 may be memory of a host device or an accessory coupled to a host.

[0094] The processing system 1300 may include various tangible processor-readable storage media and intangible processor-readable communication signals. Tangible processor-readable storage may be embodied by any available media accessible by the processing system 1300 and includes both volatile and non-volatile storage media, removable and non-removable storage media. Tangible processor-readable storage media do not include intangible communication signals and include volatile and non-volatile, removable and non-removable storage media implemented in any method or technology for storing information such as processor-readable instructions, data structures, program modules or other data. Tangible processor-readable storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CDROM, digital versatile disk (DVD) or other optical disk storage, magnetic cassettes, magnetic tapes, magnetic disk storage or other magnetic storage devices, or any other tangible media that can be used to store desired information and can be accessed by the processing system 1300. In contrast to tangible processor-readable storage media, intangible processor-readable communication signals may embody processor-readable instructions, data structures, program modules or other data residing in a modulated data signal such as a carrier wave or other signal transmission mechanism. The term "modulated data signal" means an intangible communication signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, intangible communication signals include signals propagated over wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media.

[0095] Some embodiments may include articles of manufacture. Articles of manufacture may include tangible storage media for storing logic. Examples of storage media may include one or more types of processor-readable storage media capable of storing electronic data, including volatile or non-volatile memory, removable or non-removable memory, erasable or non-erasable memory, writable or rewritable memory, etc. Examples of logic may include various software elements, such as software components, programs, applications, computer programs, applications, system programs, machine programs, operating system software, middleware, firmware, software modules, routines, subroutines, operating segments, methods, processes, software interfaces, application program interfaces (APIs), instruction sets, computing codes, computer codes, code segments, computer code segments, words, values, symbols, or any combination thereof. In one embodiment, for example, articles of manufacture may store executable computer program instructions that, when executed by a computer, cause the computer to perform methods and / or operations in accordance with the described embodiments. Executable computer program instructions may include any suitable type of code, such as source code, compiled code, interpreted code, executable code, static code, dynamic code, etc. Executable computer program instructions can be implemented according to a predefined computer language, manner or syntax to instruct a computer to perform a certain operation segment. Instructions can be implemented using any suitable high-level, low-level, object-oriented, visual, compiled and / or interpreted programming language.

[0096] A general aspect of the present disclosure includes a method for processing video data in a video surveillance system. The method includes capturing video data at a plurality of video cameras, and transmitting the video data from the plurality of video cameras to at least one camera node over a communication network according to a first camera allocation configuration. The method includes executing a video processing module at the at least one camera node to process the video data received at the at least one camera node from at least two or more cameras in a subset of the plurality of video cameras. The method also includes monitoring a camera allocation parameter at the at least one camera node. The camera allocation parameter is based at least in part on a priority value assigned to each video camera in the subset of the plurality of video cameras. The method also includes modifying the first camera allocation configuration to a second camera allocation configuration different from the first camera allocation configuration in response to the camera allocation parameter. The second camera allocation includes disconnecting the camera from the subset of the video cameras based on the priority value of the disconnected at least one camera.

[0097] Implementations may include one or more of the following features. For example, the modification may be in response to the computational power of the camera node exceeding a threshold in response to an increased computational load associated with performing video analytics on video data by the camera node.

[0098] In one example, the method includes operating a plurality of camera nodes. In a first camera allocation configuration, each camera node in the plurality of camera nodes is operable to receive video data from a respective subset of a plurality of video cameras. The modification may be responsive to exceeding a collective computing capacity threshold of a system including the plurality of camera nodes.

[0099] In one example, the method further includes operating a plurality of camera nodes. In a first camera allocation configuration, each camera node in the plurality of camera nodes is operable to receive video data from a respective subset of the plurality of cameras, and the method may include detecting a decrease in the number of available camera nodes in the video surveillance system. A second camera allocation configuration may include, after detecting a decrease in the number of available camera nodes, allocating the plurality of video cameras to the reduced number of available camera nodes.

[0100] In one example, the priority can be based at least in part on a field of view of each of the plurality of cameras. For example, at least one disconnected video camera can share at least a partially overlapping field of view with another video camera associated with the camera node. The priority can be based at least in part on a location of the video camera.

[0101] Another general aspect of the present disclosure includes a video surveillance system. The system includes a plurality of video cameras operable to capture video data; and at least one camera node operable to receive video data from one or more of the plurality of video cameras according to a first allocation configuration. The system includes a video processing module executed at the at least one camera node to process the video data received at the at least one camera node. The system also includes a master node operable to communicate with the at least one camera node to monitor camera allocation parameters based at least in part on a priority assigned to each of the plurality of video cameras, and in response to the camera allocation parameters, modify the first camera allocation configuration to a second camera allocation configuration. The second camera allocation includes disconnecting the disconnected camera from the subset of the video cameras based on a priority value of at least one disconnected camera.

[0102] Implementations may include one or more of the following features. For example, the master node may be operable to modify the first camera allocation to the second camera allocation in response to the computing power of the camera node exceeding a threshold value, the computing power of the camera node exceeding the threshold value in response to an increased computing load associated with performing video analysis on the video data by the camera node.

[0103] In one example, the system may include a plurality of camera nodes. In this regard, in a first camera allocation configuration, each camera node in the plurality of camera nodes is operable to receive video data from a respective subset of the plurality of video cameras, and the master node is operable to modify the first camera allocation to a second camera allocation in response to exceeding a collective computing capacity threshold of the system including the plurality of camera nodes. In another example, the master node is operable to detect a decrease in the number of available camera nodes in the video surveillance system. Thus, the second camera allocation configuration may include allocating the plurality of video cameras to the reduced number of available camera nodes upon detecting a decrease in the number of available camera nodes.

[0104] In one example, the priority can be based at least in part on a field of view of each of the plurality of cameras. For example, at least one of the disconnected video cameras shares at least a partially overlapping field of view with another video camera associated with the camera node. Additionally or alternatively, the priority can be based at least in part on a location of the video camera.

[0105] Another general aspect of the present disclosure includes one or more tangible processor-readable storage media, which are embodied with instructions for executing a process for processing video data in a video surveillance system on one or more processors and circuits of a device. The process includes capturing video data at a plurality of video cameras, and transmitting the video data from the plurality of video cameras to at least one camera node over a communication network according to a first camera allocation configuration, and executing a video processing module at the at least one camera node to process the video data received from at least two or more cameras in a subset of the plurality of video cameras at the at least one camera node. The process also includes monitoring a camera allocation parameter at the at least one camera node. The camera allocation parameter is based at least in part on a priority value assigned to each video camera in the subset of the plurality of video cameras. The method also includes modifying the first camera allocation configuration to a second camera allocation configuration different from the first camera allocation configuration in response to the camera allocation parameter. The second camera allocation includes disconnecting the disconnected camera from the subset of the video cameras based on the priority value of at least one disconnected camera.

[0106] Implementations may include one or more of the following features. For example, the modification may be in response to the computational power of the camera node exceeding a threshold in response to an increased computational load associated with performing video analytics on video data by the camera node.

[0107] In one example, the process may further include operating the plurality of camera nodes such that in a first camera allocation configuration, each of the plurality of camera nodes is operable to receive video data from a respective subset of the plurality of cameras. The modification may be responsive to exceeding a collective computing capacity threshold of a system including the plurality of camera nodes. Further, the process may include detecting a decrease in the number of available camera nodes in the video surveillance system, and the second camera allocation configuration may include, after detecting the decrease in the number of available camera nodes, allocating the plurality of video cameras to the reduced number of available camera nodes.

[0108] In one example, the priority can be based at least in part on a field of view of each of the plurality of cameras. For example, at least one of the disconnected video cameras shares at least a partially overlapping field of view with another video camera associated with the camera node.

[0109] The embodiments described herein are implemented as logical steps in one or more computer systems. Logical operations can be implemented (1) as a sequence of processor-implemented steps executed in one or more computer systems and (2) as interconnected machines or circuit modules within one or more computer systems. The implementation is a matter of choice, depending on the performance requirements of the computer system utilized. Therefore, the logical operations that make up the embodiments described herein are variously referred to as operations, steps, objects, or modules. In addition, it should be understood that unless otherwise explicitly claimed or the claim language inherently requires a specific order, the logical operations can be performed in any order.

[0110] Although the present invention has been shown and described in detail in the drawings and the foregoing description, such illustration and description should be regarded as exemplary rather than restrictive. For example, certain embodiments described above may be combined with other described embodiments and / or arranged in other ways (e.g., process elements may be performed in other sequences). Therefore, it should be understood that only preferred embodiments and variations thereof are shown and described, and it is desired to protect all changes and modifications within the spirit and scope of the present invention.

[0111] Further examples

[0112] Example 1. A method for processing video data in a video surveillance system, comprising:

[0113] capturing video data at a plurality of video cameras;

[0114] transmitting the video data from the plurality of video cameras to at least one camera node via a communication network according to a first camera allocation configuration;

[0115] executing a video processing module at the at least one camera node to process the video data received at the at least one camera node from at least two or more cameras of the subset of the plurality of video cameras;

[0116] monitoring a camera allocation parameter at the at least one camera node, wherein the camera allocation parameter is based at least in part on a priority value assigned to each video camera of the subset of the plurality of video cameras; and

[0117] In response to the camera allocation parameters, the first camera allocation configuration is modified to a second camera allocation configuration different from the first camera allocation configuration, wherein the second camera allocation includes disconnecting the camera from the subset of the video cameras based on a priority value of at least one disconnected camera.

[0118] Example 2. A method as described in Example 1, wherein the modification is in response to the computing power of the camera node exceeding a threshold, and the computing power of the camera node exceeding the threshold is in response to an increased computing load associated with video analysis performed by the camera node on the video data.

[0119] Example 3. The method of Example 2 further includes:

[0120] operating a plurality of camera nodes, wherein in the first camera allocation configuration, each camera node of the plurality of camera nodes is operable to receive video data from a respective subset of the plurality of video cameras; and

[0121] Wherein the modification is in response to exceeding a collective computing capacity threshold of the system including the plurality of camera nodes.

[0122] Example 4. The method of Example 1 further includes:

[0123] operating a plurality of camera nodes, wherein in the first camera allocation configuration, each camera node of the plurality of camera nodes is operable to receive video data from a respective subset of the plurality of video cameras; and

[0124] detecting a decrease in the number of available camera nodes in the video surveillance system; and

[0125] Wherein the second camera allocation configuration includes allocating the plurality of video cameras to a reduced number of available camera nodes after the detection of the reduction in the number of the available camera nodes.

[0126] Example 5. The method of Example 1, wherein the priority is based at least in part on a field of view of each of the plurality of cameras.

[0127] Example 6. The method of Example 5, wherein the at least one disconnected video camera shares at least a partially overlapping field of view with another video camera associated with the camera node.

[0128] Example 7. The method of Example 1, wherein the priority is based at least in part on a location of the video camera.

[0129] Example 8. A video surveillance system comprising:

[0130] a plurality of video cameras operable to capture video data;

[0131] at least one camera node operable to receive video data from one or more of the plurality of video cameras according to a first distribution configuration;

[0132] a video processing module executed at the at least one camera node to process the video data received at the at least one camera node; and

[0133] and a master node in operable communication with the at least one camera node to monitor a camera allocation parameter based at least in part on a priority assigned to each of the plurality of video cameras, and in response to the camera allocation parameter, to modify the first camera allocation configuration to a second camera allocation configuration, wherein the second camera allocation includes disconnecting at least one disconnected camera from a subset of the video cameras based on a priority value of the disconnected camera.

[0134] Example 9. A system as described in Example 8, wherein the master node is operable to modify the first camera allocation to the second camera allocation in response to the computing power of the camera node exceeding a threshold, wherein the computing power of the camera node exceeds the threshold in response to an increased computing load associated with video analysis performed by the camera node on the video data.

[0135] Example 10. The system of Example 9, further comprising:

[0136] a plurality of camera nodes, wherein in the first camera allocation configuration, each camera node of the plurality of camera nodes is operable to receive video data from a respective subset of the plurality of video cameras; and

[0137] Wherein the master node is operable to modify the first camera allocation to the second camera allocation in response to exceeding a collective computing capacity threshold of the system including the plurality of camera nodes.

[0138] Example 11. The system of Example 8, further comprising:

[0139] a plurality of camera nodes, wherein in the first camera allocation configuration, each camera node of the plurality of camera nodes is operable to receive video data from a respective subset of the plurality of video cameras; and

[0140] The master node is operable to detect a reduction in the number of available camera nodes in the video surveillance system, and the second camera allocation configuration includes allocating the multiple video cameras to a reduced number of available camera nodes after detecting the reduction in the number of available camera nodes.

[0141] Example 12. The system of Example 8, wherein the priority is based at least in part on a field of view of each of the plurality of cameras.

[0142] Example 13. The system of Example 12, wherein the at least one disconnected video camera shares at least a partially overlapping field of view with another video camera associated with the camera node.

[0143] Example 14. The system of Example 8, wherein the priority is based at least in part on a location of the video camera.

[0144] Example 15. One or more tangible processor-readable storage media embodied with instructions for executing, on one or more processors and circuits of a device, a process for processing data in a video surveillance system, the process comprising:

[0145] capturing video data at a plurality of video cameras;

[0146] transmitting the video data from the plurality of video cameras to at least one camera node via a communication network according to a first camera allocation configuration;

[0147] executing a video processing module at the at least one camera node to process the video data received at the at least one camera node from at least two or more cameras of the subset of the plurality of video cameras;

[0148] monitoring a camera allocation parameter at the at least one camera node, wherein the camera allocation parameter is based at least in part on a priority value assigned to each video camera of the subset of the plurality of video cameras; and

[0149] In response to the camera allocation parameters, the first camera allocation configuration is modified to a second camera allocation configuration different from the first camera allocation configuration, wherein the second camera allocation includes disconnecting at least one disconnected camera from the subset of video cameras based on a priority value of the disconnected camera.

[0150] Example 16. One or more tangible processor-readable storage media as described in Example 15, wherein the modification is in response to the computing power of the camera node exceeding a threshold, and the computing power of the camera node exceeding the threshold is in response to an increased computational load associated with video analysis performed by the camera node on the video data.

[0151] Example 17. The one or more tangible processor-readable storage media of Example 16, wherein the process further comprises:

[0152] operating a plurality of camera nodes, wherein in the first camera allocation configuration, each camera node of the plurality of camera nodes is operable to receive video data from a respective subset of the plurality of video cameras; and

[0153] Wherein the modification is in response to exceeding a collective computing capacity threshold of the system including the plurality of camera nodes.

[0154] Example 18. The one or more tangible processor-readable storage media of Example 15, wherein the process further comprises:

[0155] operating a plurality of camera nodes, wherein in the first camera allocation configuration, each camera node of the plurality of camera nodes is operable to receive video data from a respective subset of the plurality of video cameras; and

[0156] detecting a decrease in the number of available camera nodes in the video surveillance system; and

[0157] Wherein the second camera allocation configuration includes allocating the plurality of video cameras to a reduced number of available camera nodes after the detection of the reduction in the number of the available camera nodes.

[0158] Example 19. One or more tangible processor-readable storage media as described in Example 15, wherein the priority is based at least in part on a field of view of each camera of the plurality of cameras.

[0159] Example 20. One or more tangible processor-readable storage media as described in Example 19, wherein the at least one disconnected video camera shares at least a partially overlapping field of view with another video camera associated with the camera node.

Claims

1. A method for processing video data in a video surveillance system, comprising: capturing video data at a plurality of video cameras; transmitting the video data from the plurality of video cameras to at least one camera node via a communication network according to a first camera allocation configuration; executing a video processing module at the at least one camera node to process the video data received at the at least one camera node from at least two or more cameras of the subset of the plurality of video cameras; monitoring a camera allocation parameter at the at least one camera node, wherein the camera allocation parameter is based at least in part on a priority value assigned to each video camera of the subset of the plurality of video cameras; as well as In response to the camera allocation parameters, the first camera allocation configuration is modified to a second camera allocation configuration different from the first camera allocation configuration, wherein the second camera allocation configuration includes disconnecting the camera from the subset of the video cameras based on a priority value of at least one disconnected camera to reduce computing load.

2. A method as claimed in claim 1, wherein the modification is in response to the computing power of the camera node exceeding a threshold, and the computing power of the camera node exceeding the threshold is in response to an increased computing load associated with video analysis performed by the camera node on the video data.

3. The method of claim 2, further comprising: operating a plurality of camera nodes, wherein in the first camera allocation configuration, each camera node of the plurality of camera nodes is operable to receive video data from a respective subset of the plurality of video cameras; as well as Wherein the modification is in response to exceeding a collective computing capacity threshold of the system including the plurality of camera nodes.

4. The method of claim 1, further comprising: operating a plurality of camera nodes, wherein in the first camera allocation configuration, each camera node of the plurality of camera nodes is operable to receive video data from a respective subset of the plurality of video cameras; as well as detecting a decrease in the number of available camera nodes in the video surveillance system; as well as Wherein the second camera allocation configuration includes allocating the plurality of video cameras to a reduced number of available camera nodes after the detection of the reduction in the number of the available camera nodes.

5. The method of claim 1, wherein the priority is based at least in part on a field of view of each of the plurality of cameras.

6. The method of claim 5, wherein the at least one disconnected video camera shares at least a partially overlapping field of view with another video camera associated with the camera node.

7. The method of claim 1, wherein the priority is based at least in part on a location of the video camera.

8. A video surveillance system, comprising: a plurality of video cameras operable to capture video data; at least one camera node operable to receive video data from one or more video cameras of the plurality of video cameras according to a first camera allocation configuration; a video processing module executed at the at least one camera node to process the video data received at the at least one camera node; as well as A master node in operable communication with the at least one camera node to monitor a camera allocation parameter based at least in part on a priority assigned to each of the plurality of video cameras, and in response to the camera allocation parameter, to modify the first camera allocation configuration to a second camera allocation configuration, wherein the second camera allocation configuration includes disconnecting at least one disconnected camera from a subset of the video cameras based on a priority value of the disconnected camera to reduce a computational load.

9. The system of claim 8, wherein the master node is operable to modify the first camera allocation configuration to the second camera allocation configuration in response to the computing power of the camera node exceeding a threshold in response to an increased computing load associated with video analysis performed by the camera node on the video data.

10. The system of claim 9, further comprising: a plurality of camera nodes, wherein in the first camera allocation configuration, each camera node of the plurality of camera nodes is operable to receive video data from a respective subset of the plurality of video cameras; and Wherein the master node is operable to modify the first camera allocation configuration to the second camera allocation configuration in response to exceeding a collective computing capacity threshold of the system including the plurality of camera nodes.

11. The system of claim 8, further comprising: a plurality of camera nodes, wherein in the first camera allocation configuration, each camera node of the plurality of camera nodes is operable to receive video data from a respective subset of the plurality of video cameras; and The master node is operable to detect a reduction in the number of available camera nodes in the video surveillance system, and the second camera allocation configuration includes allocating the multiple video cameras to a reduced number of available camera nodes after detecting the reduction in the number of available camera nodes.

12. The system of claim 8, wherein the priority is based at least in part on a field of view of each of the plurality of cameras.

13. The system of claim 12, wherein the at least one disconnected video camera shares at least a partially overlapping field of view with another video camera associated with the camera node.

14. The system of claim 8, wherein the priority is based at least in part on a location of the video camera.

15. One or more tangible processor-readable storage media embodied with instructions for executing on one or more processors and circuits of a device a process for processing video data in a video surveillance system, the process comprising: capturing video data at a plurality of video cameras; transmitting the video data from the plurality of video cameras to at least one camera node via a communication network according to a first camera allocation configuration; executing a video processing module at the at least one camera node to process the video data received at the at least one camera node from at least two or more cameras of the subset of the plurality of video cameras; monitoring a camera allocation parameter at the at least one camera node, wherein the camera allocation parameter is based at least in part on a priority value assigned to each video camera of the subset of the plurality of video cameras; as well as In response to the camera allocation parameters, the first camera allocation configuration is modified to a second camera allocation configuration different from the first camera allocation configuration, wherein the second camera allocation configuration includes disconnecting the disconnected camera from the subset of video cameras based on a priority value of at least one disconnected camera to reduce computing load.

16. One or more tangible processor-readable storage media as described in claim 15, wherein the modification is in response to the computing power of the camera node exceeding a threshold, and the computing power of the camera node exceeding the threshold is in response to an increased computing load associated with video analysis performed by the camera node on the video data.

17. The one or more tangible processor-readable storage media of claim 16, the process further comprising: operating a plurality of camera nodes, wherein in the first camera allocation configuration, each camera node of the plurality of camera nodes is operable to receive video data from a respective subset of the plurality of video cameras; as well as Wherein the modification is in response to exceeding a collective computing capacity threshold of the system including the plurality of camera nodes.

18. The one or more tangible processor-readable storage media of claim 15, the process further comprising: operating a plurality of camera nodes, wherein in the first camera allocation configuration, each camera node of the plurality of camera nodes is operable to receive video data from a respective subset of the plurality of video cameras; as well as detecting a decrease in the number of available camera nodes in the video surveillance system; and Wherein the second camera allocation configuration includes allocating the plurality of video cameras to a reduced number of available camera nodes after the detection of the reduction in the number of the available camera nodes.

19. The one or more tangible processor-readable storage media of claim 15, wherein the priority is based at least in part on a field of view of each camera of the plurality of cameras.

20. The one or more tangible processor-readable storage media of claim 19, wherein the at least one disconnected video camera shares at least a partially overlapping field of view with another video camera associated with the camera node.