Method and system for automatically altering security level configuration of security system of facility based on received event configuration file of event to be held at facility

Abstract

An event profile associated with an event to be held at a facility is received. A predetermined security level configuration of a plurality of predetermined security level configurations is selected based at least in part on the received event profile. A security level of at least a portion of the security system is automatically altered based on a selected one or more of the plurality of predetermined security level configurations.

Description

Technical Field

[0001] The present disclosure generally relates to security systems, and more particularly to event-based changes to security settings within a security system that are automatically generated. Background Art

[0002] Many facilities have security systems. In some cases, the security configuration of a facility may change daily or may vary depending on the different areas and regions of the facility. For example, assume that a vendor arrives at a particular building on a given day. This may involve making the security settings in the lobby and meeting rooms less strict while making the security settings in the server room more strict. For example, variable security settings may include changing how individuals enter and exit specific areas and regions of the facility. These configuration changes can be difficult to implement because security personnel need to manually consider various security aspects and determine appropriate configurations based on the available equipment and current security situation in the facility. This may require extensive operator expertise. Moreover, manually identifying and changing security configurations based on dynamic changes to the security situation of a facility can be time-consuming, tedious, and error-prone. What is desired are methods and systems for automatically identifying and / or implementing security system configuration changes based on dynamic security situations occurring in a facility. Summary of the Invention

[0003] The present disclosure generally relates to security systems, and more particularly to event-based changes to security settings within a security system that are automatically generated. An example may reside in a method for controlling the security level of a security system of a facility. The exemplary method includes: receiving an event profile associated with an event to be held at the facility; selecting, at least in part based on the received event profile, one or more of a plurality of predetermined security level configurations; and automatically changing the security level of at least a portion of the security system based on the one or more of the plurality of predetermined security level configurations that are selected.

[0004] Another example may reside in a security system for a facility. The exemplary security system includes a plurality of security system sensors and a controller operatively coupled to the security system sensors. The controller is configured to store a plurality of predetermined security level configurations. The controller is configured to: identify an event profile associated with an event to be held at the facility; select, at least in part based on the identified event profile, one or more of the plurality of predetermined security level configurations; and automatically change the security level of at least a portion of the security system based on the one or more of the plurality of predetermined security level configurations that are selected.

[0005] Another example may reside in a non-transitory computer-readable medium storing instructions that, when executed by one or more processors, cause the one or more processors to: identify an event profile associated with an event to be held at a facility; automatically select, at least in part based on the identified event profile, one or more of a plurality of predetermined security level configurations; and automatically change the security level of at least a portion of a security system of the facility based on the one or more of the plurality of predetermined security level configurations that are selected.

[0006] The foregoing Summary is provided to facilitate an understanding of some of the innovative features unique to the present disclosure and is not intended as a complete description. A full understanding of the present disclosure can be obtained by viewing the entire specification, claims, drawings, and abstract as a whole. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] The present disclosure can be more fully understood in connection with the following description of various examples, in the drawings:

[0008] Figure 1 is a schematic block diagram showing an illustrative security system;

[0009] Figure 2 is shown in connection with Figure 1 is a schematic block diagram showing an illustrative architecture that can be implemented in combination with the illustrative security system shown;

[0010] Figure 3 is shown by Figure 2 is a flowchart showing an illustrative data flow of an analysis engine;

[0011] Figure 4 is shown for controlling Figure 1 is a flowchart showing an illustrative method for controlling the security level of an illustrative security system;

[0012] Figure 5 is shown for controlling Figure 1 is a flowchart showing an illustrative method for controlling the security level of an illustrative security system; and

[0013] Figure 6 is a flowchart showing an illustrative method for self-learning.

[0014] While the present disclosure is subject to various modifications and alternative forms, details thereof have been shown by way of example in the drawings and will be described in detail. It should be understood, however, that the intention is not to limit the present disclosure to the particular examples described. On the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the present disclosure. DETAILED DESCRIPTION

[0015] The following description should be read with reference to the accompanying drawings, in which like elements in different drawings are numbered in the same manner. The drawings are not necessarily to scale and depict examples that are not intended to limit the scope of the present disclosure. Although examples of various elements are illustrated, those skilled in the art will recognize that many of the examples provided have suitable alternatives that can be utilized.

[0016] It is assumed herein that all numerical values are modified by the term "about" unless the context clearly dictates otherwise. The recitation of a numerical range by endpoints includes all numbers subsumed within that range (e.g., 1 to 5 includes 1, 1.5, 2, 2.75, 3, 3.80, 4, and 5).

[0017] As used in this specification and the appended claims, the singular forms "a," "an," and "the" include plural referents unless the context clearly dictates otherwise. As used in this specification and the appended claims, the term "or" is generally employed in its sense including "and / or" unless the context clearly dictates otherwise.

[0018] It should be noted that the recitation of "one embodiment," "some embodiments," "other embodiments," etc., in the specification is meant to indicate that the described embodiments may include a particular feature, structure, or characteristic, but each embodiment may not necessarily include that particular feature, structure, or characteristic. Moreover, these phrases do not necessarily refer to the same embodiment. Additionally, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is contemplated that the feature, structure, or characteristic is described in connection with one embodiment and that, whether or not explicitly described, the feature, structure, or characteristic may be applicable to other embodiments unless there is a clear contrary indication.

[0019] Figure 1is a schematic block diagram showing an exemplary security system 10. The exemplary security system 10 can be installed within a facility for protecting the facility. The security system 10 includes a plurality of security system sensors 12, labeled 12a, 12b, and 12c respectively. Although a total of three security system sensors 12 are shown, it should be understood that the security system 10 can include any number of security system sensors 12, and in some instances, can include substantially more than three security system sensors 12. Each security system sensor 12 can represent any one of a variety of different types of sensors. For example, each security system sensor 12 can be an intrusion sensor such as a door sensor, a window sensor, a glass break sensor, a motion sensor such as a PIR (passive infrared) sensor, a camera, and / or any other type of security system sensor. The security system 10 includes a controller 14 operatively coupled to the security system sensors 12. The controller 14 can be located within the facility and can communicate with the security system sensors 12 via a wired or wireless facility network. In some instances, the controller 14 can be located at a remote location and can communicate with the security system sensors 12, for example, via a gateway.

[0020] In some instances, the security system 10 can further include an access control system 16 configured to regulate access to a secure portion of the facility. The exemplary access control system 16 includes a plurality of access control devices 18, labeled 18a, 18b, and 18c respectively. It should be understood that the access control system 16 can include any number of access control devices 18, and in some cases can include substantially more than three access control devices 18, specifically access control devices in a large facility. The access control devices 18 can be access card readers, door unlock switches, and / or any other access control devices. For example, in some instances, the access control device 18 can include a video camera that performs facial recognition to determine whether a particular individual should be allowed access to a particular space. In some instances, the access control system 16 can be controlled by the controller 14. In some instances, the access control system 16 can include its own controller (not shown).

[0021] In the illustrated example, the controller 14 is configured to store a plurality of predetermined security level configurations that can be used to control the security system 10. The controller 14 can be configured to identify an event profile associated with an event to be held at the facility. The event profile can include, for example, a visitor profile that identifies one or more characteristics of one or more visitors who will attend the event. In some cases, at least a portion of the event profile can be extracted from a meeting schedule event having a list of meeting attendees who will attend the event, and at least a portion of the visitor profile can be extracted from the list of meeting attendees. In some instances, one or more characteristics of one or more visitors who will attend the event can include a threat level associated with one or more visitors to the facility. For example, a higher threat level can be associated with a controversial visitor relative to a more regular visitor. Similarly, a higher threat level can be associated with a high-level executive relative to a more regular visitor. These are just examples. In some instances, the event profile can include a confidentiality level associated with the event. For example, the associated confidentiality level of a high-level board meeting held at the facility can be higher than that of an open event. In some instances, at least a portion of the visitor profile can be extracted based on a visitor swiping a card at an access card reader of the security system 10, such as one of the access control devices 18. For example, when a senior executive swipes a card at the facility, the security level of the facility can be increased.

[0022] In some cases, the controller 14 is configured to select one or more of the plurality of predetermined security level configurations based at least in part on the identified event profile. In some instances, the controller 14 can be configured to automatically select a security level configuration without operator input. In some cases, the controller can be configured to automatically suggest a particular one of the plurality of predetermined security level configurations to the operator and give the operator the option to select. In some cases, the controller 14 is configured to automatically change the security level of at least a portion of the security system based on one or more of the plurality of predetermined security level configurations that are selected.

[0023] In some instances, multiple pre-determined security level configurations may define what an individual must do to gain access to a particular space. For example, in a lower security level configuration, an individual may only need to swipe an access card to gain access to a secure area. In a higher security level configuration, an individual may need to perform a two-part verification (e.g., multi-factor authentication), such as including swiping an access card and entering a PIN number. In some cases, the two-part verification may include facial recognition instead of entering a PIN number, or may include facial recognition in addition to entering a PIN number. The lower security level configuration may enable fewer security system sensors 12 and / or lower one or more security thresholds associated with certain security system sensors 12, while the higher security level configuration may enable additional security system sensors 12 and / or raise one or more security thresholds associated with certain security system sensors 12.

[0024] Figure 2 is a schematic block diagram showing an exemplary architecture 20 that may be implemented in combination with the security system 10. The exemplary architecture 20 includes a host system 22 that provides a user profile to an analysis engine 24 and receives a security profile from the analysis engine 24. In some instances, the analysis engine 24 may be implemented within the controller 14. In some instances, the analysis engine 24 may be cloud-based. The host system 22 provides a security dashboard to a client 26 (e.g., a security operator). The host system 22 applies the security profile by communicating with each of a plurality of gateways 28 labeled 28a and 28b, respectively. The gateways 28 in turn communicate with edge devices 30 labeled 30a and 30b, respectively. In some instances, the controller 14 may be an example of one of the edge devices 30. An aggregator engine 32 may receive data from various data sources 34, including a database 34a, an API (application programming interface 34b, or an SDK (software development kit) 34c. The aggregator engine 32 may receive information from external systems 36, including an HRMS (human resources management system) 36a, an ERP (SAP) (enterprise planning resource software) 36b, a calendar 36c, or a PSIM (physical security information management) 36d. The HRMS 36a may be used to identify users associated with card swipes, meeting requests, and / or any other events. The calendar 36c may identify scheduled events at the facility and, in some cases, may identify the participants in the events. The PSIM 36d may report card swipe details, facial recognition details, motion events, and / or any other events reported by the facility's security system. The aggregator engine 32 collects this information and provides it to the host system 22. The host system 22 uses this information to determine which users are currently at or expected to be at the facility and provides the corresponding user profile to the analysis engine 24.

[0025] Figure 3 is a flowchart showing an exemplary data flow 38 of the analytics engine 24( Figure 2 ). The change sniffer 40 detects changes such as changes made to the normal daily operation of the facility and reports to the change storage 42. Changes can include, for example, card swipe events, motion events, facial recognition events, scheduled events, and / or any other changes that occur while the facility is operating. The configuration box 44, the user profile box 46, and the rule definition box 48 each provide information to the analytics rule engine 50. The analytics rule engine 50 outputs a security decision 52 and provides an output 54, wherein the security profile is implemented by changing one or more security level configurations of a security system (such as security system 10).

[0026] Figure 4 is a flowchart showing an exemplary method 56 for controlling the security level of a security system (such as security system 10) of a facility. The exemplary method 56 includes receiving an event profile associated with an event to be held at the facility, as shown in block 58. In some instances, the event profile may include a visitor profile, where the visitor profile identifies one or more characteristics of one or more visitors who will attend the event. In some cases, at least a portion of the event profile may be extracted from a calendar event having a list of meeting attendees (e.g., from calendar 36c), and wherein at least a portion of the visitor profile may be extracted from the list of meeting attendees. In some instances, at least a portion of the visitor profile may be extracted based on a visitor swiping a card at an access control reader of the security system. One or more characteristics of one or more visitors who will attend the event may include a threat level associated with the one or more visitors. Alternatively or in addition, the event profile may include a confidentiality level associated with the event.

[0027] Select one or more of a plurality of predetermined security level configurations, as shown in block 60, at least in part based on the received event profile. Automatically change the security level of at least a portion of the security system based on one or more of the selected predetermined security level configurations of the plurality of predetermined security level configurations, as shown in block 62. In some instances, one or more of the selected predetermined security level configurations of the plurality of predetermined security level configurations may be automatically selected at least in part based on the received event profile without operator input. In some cases, one or more of the selected predetermined security level configurations of the plurality of predetermined security level configurations may be manually selected by an operator based on one or more security level configurations automatically suggested by the system.

[0028] In some instances, automatically changing a security level of at least a portion of a security system, at least in part based on a received event profile, may include enabling one or more security features of the security system that were previously disabled and / or changing one or more sensitivity thresholds of one or more security features of the security system. For example, one or more security features may include enabling one or more video analysis algorithms that were previously disabled. As another example, one or more security features may include enabling one or more security system sensors and / or changing one or more sensitivity thresholds of one or more of the security system sensors. These are merely examples.

[0029] In some instances, method 56 may also include accessing timestamped security system data, as shown at block 64, and accessing timestamped security level configuration changes implemented by an operator of the security system, as shown at block 66. Method 56 may include automatically recommending one or more predetermined security level configurations, as shown at block 68, at least in part based on the timestamped security system data and the timestamped security level configuration.

[0030] Figure 5 FIG. is a flow diagram of an illustrative method 70 for controlling a security level of a security system (such as security system 10) of a facility. Illustrative method 70 includes receiving an event profile associated with an event to be held at the facility, as shown at block 72. In some instances, the event profile may include a visitor profile that identifies one or more characteristics of one or more visitors who will attend the event. In some cases, at least a portion of the event profile may be extracted from a meeting calendar event having a list of meeting attendees, and wherein at least a portion of the visitor profile may be extracted from the list of meeting attendees. In some instances, at least a portion of the visitor profile may be extracted based on a visitor swiping a card at an access card reader of the security system. One or more characteristics of one or more visitors who will attend the event may include a threat level associated with the one or more visitors. The event profile may include a confidentiality level associated with the event.

[0031] Select one or more of a plurality of predetermined security level configurations, at least in part based on the received event profile, as shown in block 74. Method 70 includes automatically changing the security level of at least a portion of the security system based on one or more of the selected predetermined security level configurations of the plurality of predetermined security level configurations, including changing the security level for obtaining access to an event-associated area of the facility in the access control system, as shown in block 76. For example, changing the security level for obtaining access to an event-associated area of the facility in the access control system may include changing the security protocol from single-factor authentication to multi-factor authentication for obtaining access to an event-associated area of the facility. In some instances, method 70 also includes automatically changing the security level for obtaining access to an area of the facility not associated with the event in the access control system. In some cases, when reducing the security level for obtaining access to an event-associated area of the facility in the access control system, increasing the security level for obtaining access to an area of the facility not associated with the event in the access control system, as shown in block 78. For example, when an open event is held in the lobby of a facility, the security level of the access control system for obtaining access to the lobby (door-opening policy) may be reduced during the event, while the security level of the access control system for obtaining access to other areas of the facility such as a server room or a laboratory may be increased during the event (e.g., multi-factor authentication).

[0032] Figure 6 is a flowchart showing an exemplary method 80 for self-learning a security profile of a facility based on a security system and other available data. Store a library of security profiles generated over time based on the security system and other available data at block 88. Make the library of security profiles available for use by an analysis engine 90 (which may be a representation of the analysis engine 24 shown). Provide information such as a schedule and planned events from block 92 to a host system 94 (which may be Figure 2 shown as the analysis engine 24). Provide information such as a schedule and planned events from block 92 to a host system 94 (which may be Figure 2Characterization of the host system 22 shown). The host system 94 can access the analysis engine 90 and generate a security profile. The generated security profile can be provided to block 96. Block 96 searches the library of security profiles for a matching security profile. If a matching security profile is found, control passes to block 86, where the matching security profile is applied. If no matching security profile is found, control passes to block 82, and a new proposed security profile is sometimes created based on the improvement content of one or more security profiles from the library of security profiles. The proposed new security profile is presented to the security operator 84, and if approved by the security operator 84, the proposed new security profile is added to the security profile library at 88. Each security profile defines multiple predetermined security level configurations for the security system. Over time, the library of security profiles accumulates more and more approved security profiles, which can quickly and easily adapt the security system to the increasing number of event changes occurring in the facility.

[0033] Although several illustrative embodiments of the present disclosure have been so described, those skilled in the art will readily understand that other embodiments can be made and used within the scope of the appended claims herein. However, it should be understood that the present disclosure is illustrative in many respects. Changes can be made to the details, especially those related to the shape, size, arrangement of parts, and the exclusion and order of steps, without exceeding the scope of the present disclosure. Of course, the scope of the present disclosure is defined by the language of the appended claims.

Claims

1. A method for controlling the safety level of a safety system of a facility, the method comprising: receiving an event profile associated with an event to be held at the facility; selecting a selected one or more predetermined security level configurations of a plurality of predetermined security level configurations based at least in part on the received event profile; as well as The security level of at least a portion of the security system is automatically altered based on the selected one or more predetermined security level configurations from a plurality of predetermined security level configurations.

2. The method according to claim 1, wherein: The event profile includes a visitor profile, wherein the visitor profile identifies one or more characteristics of one or more visitors who will attend the event.

3. The method according to claim 2, wherein: At least a portion of the event profile is extracted from a meeting calendar event having a roster of meeting attendees, and wherein at least a portion of the visitor profile is extracted from the roster of meeting attendees.

4. The method according to claim 2, wherein: At least a portion of the visitor profile is extracted based on the visitor swiping a card at an access authorization reader of the security system.

5. The method according to claim 2, wherein: The one or more characteristics of the one or more visitors who will attend the event include a threat level associated with the one or more visitors to the facility.

6. The method according to claim 1, wherein: The event profile includes a privacy level associated with the event.

7. The method according to claim 1, wherein: The selected one or more predetermined security level configurations of the plurality of predetermined security level configurations are automatically selected based at least in part on the received event profile without operator input.

8. The method according to claim 1, wherein: The security system includes an access control system, and wherein automatically changing the security level of at least a portion of the security system includes changing the security level of the access control system for gaining access to an area of ​​the facility associated with the event.

9. The method according to claim 8, wherein: Changing the security level of the access control system for gaining access to the area of ​​the facility associated with the event includes changing the security protocol from single-factor authentication to multi-factor authentication for gaining access to the area of ​​the facility associated with the event.

10. The method of claim 8, further comprising automatically modifying the security level of the access control system for gaining access to areas of the facility not associated with the incident, wherein: When the security level of the access authorization control system for obtaining access to the area of ​​the facility associated with the event is lowered, the security level of the access authorization control system for obtaining access to the area of ​​the facility not associated with the event is increased.

Images