The present technology relates generally to alarm systems and more particularly to detecting when someone is tampering with an alarm system.
A typical alarm system can monitor a home, business, or other property for fire, burglary, break-in, or other event that may warrant raising an alarm. However, alarm systems can be susceptible to tampering, whereby someone intentionally interferes the ability of the alarm system to raise an alarm or otherwise suppresses the alarm system's defenses. Accordingly, there are needs in the art for technologies that can detect and combat alarm system tampering.
Many aspects of the technology can be better understood with reference to the above drawings. The elements and features shown in the drawings are not necessarily to scale, emphasis being placed upon clearly illustrating the principles of exemplary embodiments of the present technology. Moreover, certain dimensions may be exaggerated to help visually convey such principles.
An embodiment of a computer-based system and process for detecting and reporting tampering of an alarm system will be discussed in further detail below with reference to the figures. However, the present technology can be embodied in different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the technology to those having ordinary skill in the art. Furthermore, all “examples,” “embodiments,” “example embodiments,” or “exemplary embodiments” given herein are intended to be non-limiting and among others supported by representations of the present technology.
Certain embodiments comprise or involve processes that will be discussed below. Some process steps may naturally need to precede others to achieve intended functionality or results. However, the technology is not limited to the order of the steps described to the extent that reordering or re-sequencing does not render the processes useless or nonsensical. Thus, it is recognized that some steps may be performed before or after other steps or in parallel with other steps without departing from the scope and spirit of this disclosure.
The alarm panel 110 communicates with a remote, off-premises server 120 that functions as an alarm gateway for multiple other alarm systems at other premises (not illustrated) and provides connectivity to a central monitoring station 125. The central monitoring station 125 monitors the alarm systems and is staffed with people who can dispatch emergency services, such as police and fire responders, on an as-needed basis.
As discussed above, the alarm system 100 includes one or more sensors for detecting various types of alarm events, such as fire, burglary, or medical emergency. Such sensors may include wired and/or wireless magnetic window and door sensors (e.g. the front door sensor 115 illustrated in
The alarm panel 110 typically includes a display providing a current status of the alarm system 100 and a keypad including buttons and/or other controls to configure and interface with the alarm system 100. A user of the alarm system 100 is able to determine a current status of the alarm system 100 by viewing the display of the alarm panel 110, and may arm and disarm the system through the panel 110. The user may also call for fire, police, and medical emergency personnel using the keypad of the alarm panel 110. The alarm system 100 further includes other wiring and associated circuitry typical of alarm systems.
The alarm panel 110 typically comprises a communication module (not illustrated) for providing a wireless or wired transceiver with circuitry and associated software for establishing data and voice channels. Particularly, the communication module can be configured to establish data and voice channels with the server 120 via a communication path. In operation, the alarm system 100 can detect an alarm event using one or more of the sensors and communicates associated alarm event data to the server 120 using a wired or wireless data channel. The alarm system 100 may also utilize a voice channel between the alarm system 100 and the central alarm monitoring station 125.
The alarm panel 110 comprises a processor 155 that typically includes one or more microprocessors or microcontrollers and associated memory 160. Example embodiments of the memory 160 can comprise volatile and nonvolatile memory, such as random access memory (RAM) and flash memory for example. In an example embodiment, the memory 160 can comprise firmware for executing management and control functions. For example, the memory 160 can comprise persistent memory that stores program code, including a monitoring engine 165. An embodiment of the monitoring engine 165 comprises computer executable instructions for making alarm decisions based on input from the front door sensor 115 and other sensors, such as code for the appropriate portions of process 200 and process 260 that are illustrated in flowchart form in
As discussed above, the server 120 provides a gateway between multiple alarm systems 100 and the central monitoring station 125. More specifically, the server 120 provides and facilitates alarm monitoring services for multiple alarm systems at various homes and businesses in addition to the illustrated alarm system 100. The server typically comprises a communication module (not illustrated) that establishes data and voice channels with the alarm panel 110 via a bidirectional communication link that may be wired or wireless. In operation, the server 120 receives alarm event data representative of an alarm event from the alarm system 100 and forwards the alarm event data along with associated information to the central monitoring station 125.
The server 120 comprises a processor 179 that typically includes one or more microprocessors or microcontrollers and associated memory 180. Example embodiments of the memory 175 can comprise volatile and nonvolatile memory, such as random access memory (RAM) and flash memory for example. In an example embodiment, the memory 175 can comprise firmware for executing management and control functions. For example, the memory 175 can comprise persistent memory that stores program code, including a tamper detection engine 180. An embodiment of the tamper detection engine 180 comprises computer executable instructions for identifying and acting on tamper events, such as code for appropriate portions of processes 200 and 260 that are illustrated in flowchart form in
The central monitoring station 125 typically includes at least one agent console and associated communications and computing gear. Personnel, including agents, staff the central monitoring station 125. In a typical operation, each agent is able to view an agent console, which displays information associated with received alarm event data from alarm systems. After receiving alarm event data and associated information from the alarm system 100 and the server 120, the agent console may display details related to an alarm event occurring at the home 105 where the alarm system 100 is installed. For example, based on alarm event data received from the alarm system 100, the agent console may indicate that a fire, panic, burglary, or medical emergency is occurring where the alarm system 100 is installed. Additionally, the agent console may display a street address or geographic coordinates of the home 105 and contact information for fire, police, and medical services. Based on the display, the agent is able to assess the event where the alarm system 100 is installed. Thus, the central monitoring station 125 facilitates monitoring alarm systems installed at multiple locations by agents who assess alarm events, and when deemed appropriate, may contact service personnel based upon alarm event data received from the alarm systems. For example, agents monitoring the alarm system 100 at the central monitoring station 125 may call for fire, police, or medical service personnel to be dispatched to the home 105.
At step 205 of process 200, the homeowner arms the alarm panel 110, for example as the homeowner exits the home 105 on the way to work in the morning.
At step 210 of process 200, the alarm panel 110 notifies the server 120 that the alarm system 100 is armed. Accordingly, the server 120 monitors for any alarm data transmissions originating at the home 105.
At step 215, someone opens the front door and triggers the front door sensor 115. The person opening the front door might be the legitimate homeowner or an intruder.
At step 220, the front door sensor 115 transmits to the alarm panel 110 a front-door-open signal or other security-zone-open signal.
At step 225, the alarm panel 110 receives the front-door-open signal and forwards the signal to the server 225.
At step 230, in response to receipt of the front-door-open signal, the alarm panel 110 starts expecting entry of the disarming code within the specified delay, which is typically in a range of about 30 to about 120 seconds, as discussed above. Thus, receipt of the front-door-open signal starts an alarm panel timer.
Receipt of the front-door-open signal at the alarm panel 100 further initiates a tamper detection process at step 260 that
At inquiry step 235, the alarm panel 110 checks for user entry of the disarming code. If the alarm panel 110 has received the disarming code, then process 200 branches to step 240.
At step 240, the alarm panel 110 notifies the server 120 that the alarm system 100 has been disarmed and thus that all is clear. Process 200 then ends.
If the alarm panel 110 has not received the disarming code at inquiry step 235, then process 200 executes inquiry step 245 rather than step 240.
At inquiry step 245, the alarm panel 110 determines whether the time delay has elapsed. In other words, the alarm panel 110 determines whether the timer started at step 230 has reached the time delay and thus expired. If the timer is still timing towards the delay, then execution of process 200 loops back to step 235. Steps 235 and 245 iterate until the alarm panel 110 is disarmed or the time delay expires.
If the time delay expires before the alarm panel 110 is disarmed, then process 200 executes step 250 from inquiry step 245.
At step 250, the alarm panel 110 deems the opening of the front door as an intrusion and raises an alarm. The alarm panel 110 transmits the intrusion alarm to the server 120.
At step 255, the server 120 receives the intrusion alarm from the alarm panel 110 and forwards the alarm to the central station 125. The central station 125 can act on the alarm by dispatching emergency personnel, opening a bidirectional voice channel to the alarm panel 110, or taking other action as deemed appropriate. Process 200 ends from step 255.
At step 305 of sub-process 260, the alarm panel 110 has received the front-door-open signal (or other security-zone-open signal that may have an associated time delay). In response to that signal receipt, the alarm panel begins transmitting a series of packets to a communication interface of the server 120 using user datagram protocol (UDP) or other high-speed, one-way (i.e. unidirectional) communication schema that has low overhead for efficiency. Thus, the server 120 comprises a communication interface configured for the unidirectional communication. Accordingly, the communication layer operates without needing to transmit a packet-receipt acknowledgement back to the alarm panel 110. The alarm panel 110 typically transmits the packets on a uniform time period, for example one packet every three seconds. Thus, the alarm panel 110 typically intends consistent time intervals between packet transmissions.
The alarm panel 110 continues the series of packet transmissions until the alarm delay expires or the alarm panel 110 receives a proper disarming code. As discussed above with reference to
At step 310 of sub-process 260, the server 120 receives the first incoming packet in the series transmitted by the alarm panel 110. The first packet received by the server 120 is often the first packet sent by the alarm panel 110. However, the order of packet receipt may differ from the order of packet transmission, for example due to packet switching that occurs in the network, between transmission and receipt. In other words, the individual packets in the series may transmit over different network routes and thus experience different propagation delays.
At step 315 of sub-process 260, the server 120 transitions to a sleep mode with respect to detecting the incoming packets transmitted by the alarm panel 110 at step 305. This sleep mode continues for a specified period of time, for example 25 seconds. Thus, the server 120 responds to receipt of the first incoming packet by ignoring any packets that may arrive during a time period of 25 seconds. Ignoring packets frees the computing/processing resources of the server 120 to perform other tasks that may include servicing a larger number of other alarm systems at other premises.
As an alternative to sleeping for a predetermined amount of time, the server 110 may utilize a sleep time that is random. The processor 170 may utilize a random number generator to provide sleep times that vary randomly within a range, for example a random amount of time that is between 20 and 30 seconds.
Inquiry step 320 of sub-process 260 determines whether the sleep time period has expired. If the sleep time period has not expired, then the sleep mode is maintained at step 325 and step 320 repeats. Accordingly, sub-process 260 iterates steps 320 and 325 until the sleep time period is complete. When the sleep time period is over, step 330 executes from step 320.
At step 330 of sub-process 260, the server 120 wakes up with respect to monitoring for packets from the alarm panel 110. The server 120 stays awake for a predetermined period of time, for example between 10 and 20 seconds, and monitors for a packet arrival during that time. As discussed below with reference to steps 335 and 340, the first packet arrival during that wake time causes the server 120 to revert to the sleep mode.
As an alternative to waking for a predetermined amount of time, the server 110 may utilize a time period that is random. The processor 170 may utilize a random number generator to provide wake times that vary randomly within a range, for example a random amount of time that is between 10 and 20 seconds.
At inquiry step 335, sub-process 260 branches according to whether the server 120 has received a packet from the alarm panel 110. If the server 120 has received a packet, then sub-process 260 loops back to step 315. If the server 120 has not received a packet, then inquiry step 340 executes.
If the wake period has not expired, then step 350 executes, the wake mode continues, and steps 335, 340, and 350 iterate until the wake period expires without receipt of a packet.
When the wake period expires without receipt of a packet, then inquiry step 355 executes from step 340. Step 355 inquires as to whether the sever 120 has received a disarm notification or an intrusion alarm per steps 240 and 255 respectively of process 200. If the inquiry is negative, then the server 120 determines that an intruder or other person has tampered with the alarm system 100 and issues a panel tamper alarm for transmission to the central monitoring station 125 via a communication interface. The central monitoring station 125 may open a voice channel to the alarm system 100, dispatch police, or take other action as appropriate.
If execution of step 335 results in a determination that an intrusion alarm has been triggered or that the alarm panel 110 has been properly disarmed, then at step 365, the sub-process 260 returns to process 200 as discussed above. Return similarly occurs following execution of step 360. In both cases, the alarm panel 110 ceases transmitting the series of packets.
Technology for tamper detection has been described. From the description, it will be appreciated that embodiments of the present technology overcome limitations of the prior art. Those skilled in the art will appreciate that the present technology is not limited to any specifically discussed application or implementation and that the embodiments described herein are illustrative and not restrictive. From the description of the exemplary embodiments, equivalents of the elements shown therein will suggest themselves to those skilled in the art, and ways of constructing other embodiments of the present technology will appear to practitioners of the art.
Number | Name | Date | Kind |
---|---|---|---|
4032916 | Galvin | Jun 1977 | A |
4465904 | Gottsegen et al. | Aug 1984 | A |
4692742 | Raizen et al. | Sep 1987 | A |
4918717 | Bissonnette et al. | Apr 1990 | A |
5134644 | Garton et al. | Jul 1992 | A |
5195126 | Carrier et al. | Mar 1993 | A |
5365568 | Gilbert | Nov 1994 | A |
5400011 | Sutton | Mar 1995 | A |
5463595 | Rodhall | Oct 1995 | A |
5568475 | Doshi et al. | Oct 1996 | A |
5736927 | Stebbins et al. | Apr 1998 | A |
5796633 | Burgess et al. | Aug 1998 | A |
5808547 | Carney | Sep 1998 | A |
5838223 | Gallant et al. | Nov 1998 | A |
5877684 | Lu | Mar 1999 | A |
5923731 | McClure | Jul 1999 | A |
5940474 | Ruus | Aug 1999 | A |
6075451 | Lebowitz et al. | Jun 2000 | A |
6215404 | Morales | Apr 2001 | B1 |
6243373 | Turock | Jun 2001 | B1 |
6272212 | Wulforst et al. | Aug 2001 | B1 |
6288642 | Dohrmann | Sep 2001 | B1 |
6311072 | Barclay et al. | Oct 2001 | B1 |
6369705 | Kennedy | Apr 2002 | B1 |
6381307 | Jeffers et al. | Apr 2002 | B1 |
6400265 | Saylor et al. | Jun 2002 | B1 |
6438124 | Wilkes et al. | Aug 2002 | B1 |
6452490 | Garland et al. | Sep 2002 | B1 |
6493435 | Petricoin | Dec 2002 | B1 |
6553100 | Chen et al. | Apr 2003 | B1 |
6574480 | Foladare et al. | Jun 2003 | B1 |
6577234 | Dohrmann | Jun 2003 | B1 |
6603845 | Jensen et al. | Aug 2003 | B2 |
6661340 | Saylor et al. | Dec 2003 | B1 |
6683526 | Bellin | Jan 2004 | B2 |
6829478 | Layton et al. | Dec 2004 | B1 |
6831557 | Hess | Dec 2004 | B1 |
6870906 | Dawson | Mar 2005 | B2 |
6928148 | Simon et al. | Aug 2005 | B2 |
6965313 | Saylor et al. | Nov 2005 | B1 |
6973165 | Giacopelli et al. | Dec 2005 | B2 |
7002462 | Welch | Feb 2006 | B2 |
7009519 | Leonard et al. | Mar 2006 | B2 |
7103152 | Naidoo et al. | Sep 2006 | B2 |
7113090 | Saylor et al. | Sep 2006 | B1 |
7119609 | Naidoo et al. | Oct 2006 | B2 |
7245703 | Elliot et al. | Jul 2007 | B2 |
7262690 | Heaton et al. | Aug 2007 | B2 |
7406710 | Zellner et al. | Jul 2008 | B1 |
7429921 | Seeley et al. | Sep 2008 | B2 |
7440554 | Elliot et al. | Oct 2008 | B2 |
7542721 | Bonner et al. | Jun 2009 | B1 |
7558379 | Winick | Jul 2009 | B2 |
7593512 | Elliot et al. | Sep 2009 | B2 |
7593513 | Muller | Sep 2009 | B2 |
7613278 | Elliot et al. | Nov 2009 | B2 |
7619512 | Trundle et al. | Nov 2009 | B2 |
7633385 | Cohn et al. | Dec 2009 | B2 |
7653186 | Hosain et al. | Jan 2010 | B2 |
7734020 | Elliot et al. | Jun 2010 | B2 |
7751540 | Whitfield et al. | Jul 2010 | B2 |
7778394 | Small et al. | Aug 2010 | B2 |
7820841 | Van Toor et al. | Oct 2010 | B2 |
7848505 | Martin et al. | Dec 2010 | B2 |
7853200 | Blum et al. | Dec 2010 | B2 |
7855635 | Cohn et al. | Dec 2010 | B2 |
7911341 | Raji et al. | Mar 2011 | B2 |
7920841 | Martin et al. | Apr 2011 | B2 |
7920842 | Martin et al. | Apr 2011 | B2 |
7920843 | Martin et al. | Apr 2011 | B2 |
7961088 | Watts et al. | Jun 2011 | B2 |
8022807 | Martin et al. | Sep 2011 | B2 |
8073931 | Dawes et al. | Dec 2011 | B2 |
8116724 | Peabody | Feb 2012 | B2 |
8214494 | Slavin | Jul 2012 | B1 |
8335842 | Raji et al. | Dec 2012 | B2 |
8350694 | Trundle et al. | Jan 2013 | B1 |
8395494 | Trundle et al. | Mar 2013 | B2 |
8456293 | Trundle et al. | Jun 2013 | B1 |
8473619 | Baum et al. | Jun 2013 | B2 |
8478844 | Baum et al. | Jul 2013 | B2 |
8493202 | Trundle et al. | Jul 2013 | B1 |
8520072 | Slavin et al. | Aug 2013 | B1 |
8525665 | Trundle et al. | Sep 2013 | B1 |
8626151 | Beppler et al. | Jan 2014 | B2 |
20020103898 | Moyer | Aug 2002 | A1 |
20020147982 | Naidoo et al. | Oct 2002 | A1 |
20020176581 | Bilgic | Nov 2002 | A1 |
20020177428 | Menard et al. | Nov 2002 | A1 |
20030027547 | Wade | Feb 2003 | A1 |
20030071724 | D'Amico | Apr 2003 | A1 |
20030128115 | Giacopelli et al. | Jul 2003 | A1 |
20040005044 | Yeh | Jan 2004 | A1 |
20040086088 | Naidoo | May 2004 | A1 |
20040086093 | Schranz | May 2004 | A1 |
20050099893 | Jyrinki | May 2005 | A1 |
20060023848 | Mohler et al. | Feb 2006 | A1 |
20060103520 | Clark | May 2006 | A1 |
20060176167 | Dohrmann | Aug 2006 | A1 |
20060239250 | Elliot et al. | Oct 2006 | A1 |
20070115930 | Reynolds et al. | May 2007 | A1 |
20070155412 | Kalsukis | Jul 2007 | A1 |
20080084291 | Campion, Jr. | Apr 2008 | A1 |
20080117029 | Dohrmann et al. | May 2008 | A1 |
20080191863 | Boling | Aug 2008 | A1 |
20090017757 | Koga | Jan 2009 | A1 |
20090077622 | Baum et al. | Mar 2009 | A1 |
20090213999 | Farrand | Aug 2009 | A1 |
20090248967 | Sharma et al. | Oct 2009 | A1 |
20090264155 | Nakayama et al. | Oct 2009 | A1 |
20090274104 | Addy | Nov 2009 | A1 |
20100007488 | Sharma et al. | Jan 2010 | A1 |
20100052890 | Trundle | Mar 2010 | A1 |
20100121948 | Procopio | May 2010 | A1 |
20100277271 | Elliot et al. | Nov 2010 | A1 |
20100289643 | Trundle | Nov 2010 | A1 |
20100289644 | Slavin | Nov 2010 | A1 |
20110065414 | Frenette | Mar 2011 | A1 |
20110169628 | Elliot | Jul 2011 | A1 |
20120027010 | Elliot | Feb 2012 | A1 |
20120139718 | Foisy et al. | Jun 2012 | A1 |
20120250833 | Smith et al. | Oct 2012 | A1 |
20120250834 | Smith | Oct 2012 | A1 |
20120275588 | Gregory | Nov 2012 | A1 |
20130189946 | Swanson | Jul 2013 | A1 |
20130194091 | Trundle | Aug 2013 | A1 |
20130207802 | Wu | Aug 2013 | A1 |
20130215266 | Trundle | Aug 2013 | A1 |
20130234840 | Trundle | Sep 2013 | A1 |
20130321150 | Koenig | Dec 2013 | A1 |
Number | Date | Country | |
---|---|---|---|
20160117916 A1 | Apr 2016 | US |