Not applicable
Not applicable
Not applicable
1. Field of the Invention
The field of the invention relates to perimeter security networks, and in particular, to processing event signals to evaluate threat events.
2. Description of the Prior Art
Recently, many enterprises have become increasingly concerned with the issue of perimeter security. For example, military, municipal, and corporate enterprises desire to secure the perimeters of a wide variety of installations, such as airports, military bases, and corporate campuses.
Typically, perimeter security systems are arranged with multiple sensors arrayed along a boundary and in communication with a central control system. Often times, the sensors are mounted on a barrier, such a fence. In general, the sensors monitor the boundary for event signals, such as vibration and heat signals. Upon sensing an event signal, an alert signal is communicated from the sensors to a central control system.
In one example, the central control system alerts personnel to the occurrence of the event. The personnel are then tasked with investigating the event to evaluate whether or not the event is a security threat. One problem associated with this approach is that dispatching personnel to investigate non-threatening events wastes time and resources.
In a prior art solution to the problem of dispatching personnel to evaluate events, threat evaluation is performed at the central control system. In this manner, personnel will only be dispatched once an accurate threat evaluation has been performed by the central control system. However, many modern large scale perimeter security systems include thousands of sensors. In such an environment, the resources required to perform threat evaluation at a central control system and the resources required to link thousands of sensors to a central control system can be prohibitive.
An embodiment of the invention helps solve the above problems and other problems by distributing threat evaluation to the sensor systems of a perimeter security network, rather than relying upon a central control system to perform threat evaluation tasks. In this manner, the processing resources required of a central control system are reduced. In addition, the occurrence of false alarms generated by non-threat events is reduced. Furthermore, distributing threat evaluation to the sensors systems of a perimeter security system allows for improved scalability and efficiency of operation.
In an embodiment, a security system comprises a barrier, a sensor system, and a control system. The sensor system is coupled to the barrier and is configured to receive a plurality of event signals for an event, process the plurality of event signals to determine if the event is a threat, and, responsive to determining that the event is a threat, generate and transmit a threat message identifying the event. The control system is configured to receive and process the threat message to determine a response to the event.
In an embodiment, the security system further comprises a user interface system wherein the response comprises a threat notification and wherein the control system is configured to transfer the threat notification to the user interface system and wherein the user interface system is configured to display the threat notification.
In an embodiment, a first event signal of the plurality of event signals comprises an acceleration signal.
In an embodiment, a first event signal of the plurality of event signals comprises a vibration signal.
In an embodiment, a first event signal of the plurality of event signals comprises a heat signal.
In an embodiment, a method of operating a security system comprises receiving a plurality of event signals for an event into a sensor system coupled to a barrier, in the sensor system, processing the plurality of event signals to determine if the event is a threat, responsive to determining that the event is a threat generating and transmitting a threat message identifying the event from the sensor system to a control system, and in the control system, receiving and processing the threat message to determine a response to the event.
In an embodiment, a sensor system comprises a signal sensor configured to receive a plurality of event signals for an event, a processing system coupled to the signal sensor and configured to process the plurality of event signals to determine if the event is a threat and responsive to determining that the event is a threat generate a threat message identifying the event, and an interface system coupled to the processing system and configured to transmit the threat message to a control system.
In an embodiment, the control system is remote from the sensor system.
In an embodiment, a method of operating a sensor system comprises receiving a plurality of event signals for an event, processing the plurality of event signals to determine if the event is a threat, generating a threat message identifying the event responsive to determining that the event is a threat, and transmitting the threat message to a control system.
The same reference number represents the same element on all drawings.
Configuration and Operation—
Sensor systems 171-173 and 191-192 could be any sensor systems capable of performing remote threat evaluation of event signals generated by potential threat events. In an example, sensor systems 171-173 and 191-192 could be capable of receiving event signals for events, processing the event signals to determine whether or not the events are threats to a perimeter, and communicating with control system 110 over communication links 141 and 142 if the events are threats.
Control system 110 could be any system or collection of systems capable of communicating with sensor systems 171-173 and 191-192 and UIS 120. In an example, control system 110 could be capable of receiving threat messages from sensor systems 171-173 and 191-192 identifying threats and processing the threat messages to determine responses to the threats. For example, control system 110 could provide notification to UIS 120 of a threat, whereby UIS 120 could display the threat notification to a user. In another example, control system 110 could log threat messages for later security analysis.
UIS 120 could be any system capable of communicating with control system 110 and interfacing with a user. UIS 120 could be any type of device capable of interfacing to a user, such as a personal computer, work station, mobile work station, handheld device, phone, or pager, as well as other types of devices.
It should be understood sensor system 202 could be coupled to barrier segment 201 in a manner well known in the art. As illustrated in
In an example, the event signal processed by sensor system 202 could indicate a pattern. It should be understood that sensor system 202 could determine whether the event is a threat based on the pattern contained in the signal. For instance, signal patterns caused by weather factors, such as wind or rain, could differ significantly from signal patterns caused by a person attempting to climb barrier segment 201. Sensor system 202 could compare, contrast, or otherwise process the event signal to discriminate between non-threat events, such as wind or rain, and threat events, such as intruders scaling a fence.
Interface system 420 could comprise a network interface card, modem, port, or some other communication device. Processing system 430 could comprise a computer microprocessor, logic circuit, or some other processing device. Processing system 430 could be distributed among multiple processing devices. Storage system 440 could comprise a disk, integrated circuit, or some other memory device. Storage system 440 could be distributed among multiple memory devices. Signal sensor 410 could comprise any sensor capable of sensing or receiving event signals, such as an accelerometer, a vibrometer, or an infra-red sensor. It should be understood that sensor system 400 could include multiple signal sensors.
Processing system 430 retrieves and executes software 450 from storage system 440. Software 450 may comprise an operating system, utilities, drivers, networking software, and other software typically loaded onto a general-purpose computer. Software 450 could also comprise an application program, firmware, or some other form of machine-readable processing instructions. When executed by the processing system 430, software 450 directs processing system 430 to operate as described for sensor system 202 and sensor systems 171-173 and 191-192.
Perimeter Security Example
The following describes for exemplary purposes a perimeter security system and the operation thereof in an embodiment of the invention.
In this example, a perimeter security system could comprise multiple sensor systems arrayed along a perimeter, such as a border, boundary, or the like. The sensor systems could be coupled to a barrier, such a fence or a wall. For instance, the sensor systems could be mounted to a fence. Optionally, the sensor systems could be independent from a barrier, such as in the case of a video camera or infra-red sensor positioned distant from the perimeter, but directed to the perimeter. The sensor systems could be in communication with a central control system over a communication link. The communication link could be a wired or wireless communication link, or any combination thereof. An example of a wired communication link is an RS-485 link. The control system could be coupled to a user interface system, such as a work station. Personnel could monitor the user interface system for threat events occurring at the perimeter.
In operation, events will typically occur in a continuous fashion at the perimeter. For instance, in a case wherein a fence is positioned along a perimeter, weather, animal, or other environmental events will cause disturbances along the fence. For example, wind gusts could cause a disturbance to the fence. Likewise, small animals could disturb the fence, such as in the case of birds or other small animals climbing or resting on the fence. Such environmental events could be considered non-threat events.
Further in operation, events could occur that are not in accordance with non-threat events. Such non-environmental events could be considered threat events. For example, an intruder could attempt to enter the perimeter, such as by climbing a fence. In another example, an intruder could attempt to cut a fence.
Regardless of the type of event, a sensor system could detect, sense, measure, or otherwise receive signals created by an event. For example, disturbances translated to a fence by a threat or non-threat event could be measured in terms of vibration or acceleration, as well as by other factors.
In the prior art, a sensor system could transmit data corresponding to the event signals to a central control system for threat evaluation. In contrast, the present embodiment provides for evaluating data corresponding to the event signals at the sensor system. Upon receiving an event signal, the signal is converted to data in a digital form. The data is processed in the sensor system to determine whether the data contains a pattern consistent with non-threat environmental factors, such as wind, or consistent with threats, such as an intruder scaling a fence.
The evaluation result can then be provided to the central control system. The central control system can further provide the result to the user interface system. It should be understood that the central control system could optionally be combined with the user interface system in a single system.
Advantageously, embodiments of the invention provide for distributing threat evaluation to the sensor systems of a perimeter security network. In an advantage, the processing resources required of a central control system are reduced. In addition, the time and effort required of personnel for non-threat events is reduced. In yet another advantage, distributing threat evaluation to the sensors systems of a perimeter security system allows for improved scalability and efficiency of operation.
Number | Name | Date | Kind |
---|---|---|---|
4326272 | Rittenbach et al. | Apr 1982 | A |
4365239 | Mongeon | Dec 1982 | A |
4450434 | Nielsen et al. | May 1984 | A |
4562428 | Harman et al. | Dec 1985 | A |
4609909 | Miller et al. | Sep 1986 | A |
4684932 | Kupec et al. | Aug 1987 | A |
4800366 | Hussman | Jan 1989 | A |
4857912 | Everett, Jr. et al. | Aug 1989 | A |
6209395 | Kristensen | Apr 2001 | B1 |
6288640 | Gagnon | Sep 2001 | B1 |
6512478 | Chien | Jan 2003 | B1 |
6621947 | Tapanes et al. | Sep 2003 | B1 |
6664894 | Pakhomov | Dec 2003 | B2 |
6778469 | McDonald | Aug 2004 | B1 |
6778717 | Tapanes et al. | Aug 2004 | B2 |
6816073 | Vaccaro et al. | Nov 2004 | B2 |
6937151 | Tapanes | Aug 2005 | B1 |
6956478 | Oyagi et al. | Oct 2005 | B2 |
6980483 | McDonald | Dec 2005 | B2 |
7049952 | Kulesz et al. | May 2006 | B2 |
7119681 | Eskildsen | Oct 2006 | B2 |
7161483 | Chung | Jan 2007 | B2 |
20030198425 | Tapanes et al. | Oct 2003 | A1 |
20040071382 | Rich et al. | Apr 2004 | A1 |
20050147340 | Tapanes | Jul 2005 | A1 |
Number | Date | Country |
---|---|---|
4114293 | Nov 1992 | DE |
2404480 | Feb 2005 | GB |
2409085 | Jun 2005 | GB |