The present invention relates generally to security systems. More particularly, the present invention relates to systems and methods for responding to an abnormal event in a region monitored by a security system.
Security systems and methods that communicate alarm events to a central monitoring station are known in the art. However, these known systems and methods suffer from several known issues. First, such known systems and methods utilize expensive proprietary equipment instead of widely available smart home and internet of things devices. Second, such known systems and methods can be slow in responding to an abnormal event in a monitored region. Third, such known systems are susceptible to tampering by savvy burglars who can deactivate local alarm sounders and/or prevent transmission of alarm signals to the central monitoring station. Fourth, such known systems and methods can be overly sensitive, which can result in sending unnecessary alarms to the central monitoring station.
In view of the above, there is a continuing, ongoing need for improved systems and methods.
While this invention is susceptible of an embodiment in many different forms, there are shown in the drawings and will be described herein in detail specific embodiments thereof with the understanding that the present disclosure is to be considered as an exemplification of the principles of the invention. It is not intended to limit the invention to the specific illustrated embodiments.
Embodiments disclosed herein can include systems and methods for responding to an abnormal event in a region monitored by a security system. Such systems and methods can include a cloud server that can periodically receive a heartbeat signal from the security system in the region and that can receive a notification signal of an occurrence of the abnormal event in the region from the security system. Responsive to failing to receive the heartbeat signal after receiving the notification signal of the occurrence of the abnormal event, the cloud server can transmit an alarm signal to a central monitoring station.
In some embodiments, prior to receiving the notification signal of the occurrence of the abnormal event, the cloud server can periodically receive the heartbeat signal from the security system at a first predetermined rate, and responsive to the occurrence of the abnormal event, the cloud server can periodically receive the heartbeat signal from the security system at a second predetermined rate. In some embodiments, the second predetermined rate can be faster than the first predetermined rate, and in some embodiments, the first predetermined rate and the second predetermined rate can be configured based on specific performance parameters of the cloud server and components of the security system. In some embodiments, the first predetermined rate can be 10 minutes, and the second predetermined rate can be 10 seconds.
In some embodiments, one or more sound annunciation devices located proximate to the region can be activated. For example, in some embodiments, the cloud server and/or a control panel of the security system can transmit an instruction signal to the sound annunciation devices directing the sound annunciation devices to emit an alarm sound into the region or an area proximate to the region responsive to the cloud server transmitting the alarm signal to the central monitoring station. Additionally or alternatively, in some embodiments, the cloud server and/or the control panel can transmit the instruction signal to the sound annunciation devices responsive to the cloud server failing to receive the heartbeat signal after receiving the notification signal of the occurrence of the abnormal event and prior to the cloud server transmitting the alarm signal to the central monitoring station.
In some embodiments, the sound annunciation devices can be smart home appliances, internet connected music systems, or other internet of things devices that include a speaker and are connected to the internet, the cloud server, and/or the control panel. The sound annunciation devices can be integrated with the security system and/or can be separate from the security system. In some embodiments, the sound annunciation devices can be preregistered with the cloud server or the control panel as being located proximate to or within the region.
In some embodiments, responsive to failing to receive the heartbeat signal after receiving the notification signal of the occurrence of the abnormal event, the cloud server can use a location of a registered device associated with a user of the security system to verify whether a potential alarm is real or false, for example, by determining whether the registered device is present in the region. When the cloud server determines that the registered device is present in the region, the cloud server can determine that the potential alarm is false and refrain from transmitting the alarm signal to the central monitoring station, but when the cloud server fails to determine that registered device is present in the region, the cloud server can determine that the potential alarm is real and transmit the alarm to the central monitoring station. In some embodiments, the cloud server can use the location of the registered device to verify whether the potential alarm is real or false only when an alarm state of the security system indicates that the user is away from the region (e.g. the security system is in an arm away state). Checking the location of the registered device in this manner prior to transmitting the alarm signal to the central monitoring station can minimize and/or prevent the cloud server from transmitting false alarms to the central monitoring station because security events requiring intervention from the central monitoring station while the security system is in the arm away state are most likely to occur when the user is not present in the region.
In some embodiments, the registered device can be a smart phone or a key-fob with location tracking capabilities. Accordingly, in some embodiments, the cloud server can determine the location of the registered device by using GPS or other location tracking technology and/or geofencing techniques.
In some embodiments, the control panel can periodically transmit the heartbeat signal to the cloud server at the first predetermined rate or the second predetermined rate, and in some embodiments, the control panel can transmit the notification signal of the occurrence of the abnormal event to the cloud server based on first or second home devices of the security system in the region. For example, in some embodiments, the first home device can detect a first alert condition associated with the first home device, and the second home device can detect a second alert condition associated with the second home device. In these embodiments, responsive to receiving a notification signal of the first or second alert condition, the control panel can transmit the notification signal of the occurrence of the abnormal event to the cloud server. Additionally or alternatively, in these embodiments, the control panel can refrain from transmitting the heartbeat signal to the cloud server when the first home device is offline and/or when the second home device is offline.
One or both of the first and second home devices can include a known surveillance device, such as a camera, an intrusion panel, a door or window sensor, or a door lock sensor, among others, and one or both of the first and second alert conditions can be a specific parameter monitored by a respective one of the first and second home devices based on a respective type of the respective one of the first and second home devices. For example, the first or second alert condition can include, but is not limited to a motion alert, a special sound pattern alert, a device tampering alert, a negative faced ID recognition alert, a delayed door open alert, or a door open alert, among others. The second home device can have a type that is the same or different from the first home device.
In some embodiments, systems and methods disclosed herein can omit the control panel. Accordingly, the first or second home device can periodically transmit the heartbeat signal directly to the cloud server at the first predetermined rate or the second predetermined rate. In such embodiments, the first or second home device can detect the first or second alert condition and, responsive thereto, can transmit the notification signal of the occurrence of the abnormal event to the cloud server. In some embodiments, the first and second home devices can communicate with each other via a mesh network or similar infrastructure and can refrain from transmitting the heartbeat signal to the cloud server when one or more of the first or second home devices or another home device of the security system is offline. For example, the first home device can refrain from transmitting the heartbeat signal to the cloud server when the first home device is offline and/or when the second home device is offline.
However, when the cloud server 24 determines that the notification signal of the occurrence of the abnormal event has been received, as in 205, the method 200 can include the cloud server 24 determining whether a disarm event for the security system 22 has occurred, as in 206. When the cloud server 24 determines that the disarm event has occurred, as in 206, the method 200 can include the cloud server 24 determining that the abnormal event did not occur, as in 210, and the method 200 can terminate, as in 208, or include the cloud server 24 continuing to wait for the notification signal of the occurrence of the abnormal event, as in 204.
However, when the cloud server 24 determines that the disarm event has not occurred, as in 206, the method 200 can include the cloud server 24 determining whether the heartbeat signal has been received from the security system 22, as in 212. When the cloud server 24 determines that the heartbeat signal has been received, as in 212, the method 200 can terminate, as in 208, or include the cloud server 24 continuing to determine whether the heartbeat signal has been received, as in 212.
However, when the cloud server 24 determines that the heartbeat signal has not been received, as in 212, the method 200 can include the cloud server 24 determining whether the registered device 29 is located proximate to the region R, as in 216. When the cloud server 24 determines that the registered device 29 is located proximate to the region R, as in 216, the method 200 can include the cloud server 24 refraining from transmitting a false alarm to the central monitoring station 26, as in 218. Then, the method 200 can terminate, as in 208, or include continuing to wait for the notification signal of the occurrence of the abnormal event, as in 204.
However, when the cloud server 24 determines that the registered device 29 is not located proximate to the region R, as in 216, the method 200 can include the cloud server 24 sending an alarm signal to the central monitoring station 26, as in 220, and sending an instruction signal to the sound annunciation device 27 to broadcast an audible alarm in the region R, as in 222. Then, the method 200 can terminate, as in 208, or include continuing to wait for the notification signal of the occurrence of the abnormal event, as in 204.
Although a few embodiments have been described in detail above, other modifications are possible. For example, the logic flows described above do not require the particular order described or sequential order to achieve desirable results. Other steps may be provided, steps may be eliminated from the described flows, and other components may be added to or removed from the described systems. Other embodiments may be within the scope of the invention.
From the foregoing, it will be observed that numerous variations and modifications may be effected without departing from the spirit and scope of the invention. It is to be understood that no limitation with respect to the specific system or method described herein is intended or should be inferred. It is, of course, intended to cover all such modifications as fall within the spirit and scope of the invention.
Number | Name | Date | Kind |
---|---|---|---|
7619512 | Trundle et al. | Nov 2009 | B2 |
8395494 | Trundle et al. | Mar 2013 | B2 |
9384655 | Nye et al. | Jul 2016 | B2 |
9860677 | Agerstam | Jan 2018 | B1 |
20070257790 | Hershkovitz | Nov 2007 | A1 |
20110037593 | Foisy | Feb 2011 | A1 |
20120188072 | Dawes | Jul 2012 | A1 |
20130212945 | Lanham | Aug 2013 | A1 |
20140104048 | De Kock | Apr 2014 | A1 |
20170136989 | Haber | May 2017 | A1 |
20180025617 | Hesford | Jan 2018 | A1 |
20190123904 | Ackerman | Apr 2019 | A1 |
Number | Date | Country | |
---|---|---|---|
20200226894 A1 | Jul 2020 | US |