The present invention relates towards alarm and security system monitoring. In particular, the present invention is directed toward alarm system monitoring over the Internet, and more specifically with a technique for allowing alarm system monitoring companies that do not have Internet alarm monitoring capabilities to monitor alarm systems that communicate over the Internet, by providing a telephone output for conventional alarm monitoring equipment.
In recent years, alarm systems are moving toward monitoring over the Internet, and the present inventors, as evidenced by the number of patents previously incorporated by reference, have developed a number of techniques relating to Internet monitoring of alarm systems, including devices for converting conventional alarm systems to IP protocols, using VoIP and other techniques. Other alarm systems may be configured to interface directly with the Internet, through a wireless (WiFi) or network connection (e.g., plugging into a router, cable modem, DSL modem, or the like).
One problem with Internet monitoring of alarm systems is that there are a number of such IP alarm systems or converters (such as developed by the present inventors) on the market, and each may have its own particular format and central station monitoring hardware or software. If an alarm monitoring company wishes to monitor signals from a number of different brands or formats of equipment, it must invest in different hardware and software for each brand and type of equipment. Moreover, since such alarm monitoring systems may be “stand alone”, the alarm monitoring company may have to maintain and monitor such separate systems, meaning that the monitoring personnel have to monitor and respond to multiple screens of data, each in a different format and using a different command and menu structure—and each requiring separate training.
Many smaller monitoring companies may not want to invest in new IP-based alarm equipment, but instead prefer to use their older POTS (Plain Old Telephone Service) or PSTN (Public Switched Telephone Network) interface. Such smaller alarm companies may find themselves unable to compete with larger companies, particularly as more and more customers switch to VoIP or IP based alarm protocols.
Thus, it remains a requirement in the art to provide a means for monitoring centers to be able to receive IP based alarm signals using existing equipment, and receive alarm signals on a single type of alarm monitoring equipment, without having to purchase and operate separate alarm monitoring systems for each equipment type and brand.
Alarm customers on VoIP may now use an adapter developed by the present inventors, for conversion to IP (Internet Protocol) as disclosed in Applicant's previous patent applications previously incorporated by reference. In the present invention, IP signals from customers can go to any monitoring center—those with corresponding servers on IP directly and those without corresponding servers, using the central server (middleware provider) of the present invention to dial on POTS (Plain Old Telephone Service) to the monitoring center or by communicating directly with the monitoring center over an IP link. IN this manner, the middleware server can take a number of alarm signals from disparate alarm system types, formats and paths (IP or POTS) and output them in a single format, which may be used by the alarm monitoring company. In one particular embodiment of the present invention, IP signals are translated back into POTS signals, such that an alarm monitoring company using POTS equipment can monitor IP alarm signals.
Traditionally, IP signals from alarm systems using IP conversion equipment (or IP based alarm systems) could only be sent to monitoring centers with specialized receiving equipment specific to the type of transmitting equipment in use at the customer's premise. There is a pool of customers, whose dealers would convert to IP and stay with the current monitoring center if the center invested in receiving equipment.
For the many small centers who will not or cannot invest in receiving equipment, the present invention takes IP signals from any or all brands of IP transmitting equipment, to a central server at a middleware provider which may then retransmit to any center over POTS or other format. The middleware server may also provide a suite of notification services also editable by the customer or dealer using a customer portal.
Thus, it is one objective of the present invention to convert non-standard and varied format IP signals to single standard signal, including a POTS signal, for delivery to a monitoring center, including a Prior Art POTS-type monitoring center.
Alarm system manufacturers are producing alarm equipment designed to transmit alarm data over the Internet. While there is a standard protocol available it is rarely used. Consequently there are several systems in use each requiring specialized server receiving equipment at the alarm monitoring center. Many smaller alarm monitoring centers will not purchase or cannot afford the servers for the different systems. The present invention allows IP transmissions from many different systems to be decoded at our server farm and the transmitted to alarm monitoring centers in one format, including via POTS.
This allows any alarm monitoring center to accept signals from all protocols that the server farm has available. The decoding servers essentially become a shared resource. The current VoIP Alarm platform which provides a user portal with SMS, IVR, email notifications and alarm history may also be provided to users.
The alarm translation system of the present invention is discussed below in connection with
One key to understanding the present invention is that in the alarm monitoring business, alarm monitoring companies and the company providing the alarm services may be two different entities. Thus, for example, if a customer contracts with ACME Alarm Systems Company for alarm services, ACME may in turn subcontract out the actual day-to-day monitoring of the customer's alarm system to a third party—perhaps even offshore—where operating costs are lower. The Alarm company may provide a branded identity (ACME) to the customer, as well as service (installation, repair) of the physical alarm system, billing services, and also middleware services, as described elsewhere in applicant's previous applications incorporated by reference.
However, Prior Art alarm systems use a number of formats to generate and transmit alarms, from early POTS (Plain Old Telephone Service) systems which would “dial out” on a PSTN (Public Switched Telephone Network) line, to newer systems, which may connect directly to the Internet or be configured to connect to the Internet as follows.
As previously noted, alarm systems may be modified or designed to send alarm signals over an IP link to an alarm monitoring center or to a middleware provider.
At a server 3, an IP to PSTN translator receives the IP protocol alarm signals from the internet connection 2 and looks up the correct monitoring company or station to call (based on a look-up table or database having alarm system identification information, to correlate alarm identification information with the correct monitoring station or company). The server then picks up a PSTN line and dials the receiver of a traditional central station and conveys the alarm signal using standard PSTN protocols. A receiver at the central station (monitoring company) receives the signals at a receiver 5 and decodes the PSTN alarm signal and conveys it to a dispatch system 5. Dispatch system 5 may comprise a Prior Art PSTN based alarm monitoring system which may be monitored by an individual. The individual may then see the alarm system codes and identification and take the normal steps in dispatching the alarm (calling the consumer to confirm false alarms, dispatching Police or Fire or Emergency personnel, and the like) as in the Prior Art.
In this manner, a Prior Art alarm monitoring company may receive alarm signals even from modern IP-based or converted alarm systems. The server 3 may be located at a middleware provider, who contracts with the consumer to provide alarm monitoring services, and in turn sub-contracts out the alarm monitoring services to the alarm monitoring company housing central station 5. Alternately, an Alarm monitoring company housing central station 5 may employ a middleware provider with server 3, in order to offer IP Alarm customers their monitoring services, without having to invest in new monitoring equipment.
In an alternative embodiment of the present invention, server 3 may receive IP signals from various alarm panels 1, which are in a number of different IP Alarm system formats and coding. Server 3 may then convert these codes into a standard format which in turn may be communicated to an alarm monitoring center 5 via PSTN connection 4, as illustrated in
In the preferred embodiment of the present invention, the alarm panel is an IP enabled alarm panel, meaning that it generates an IP signal directly to the middleware server, as illustrated by the connection to step 830. Alternately, the alarm panel may convert a POTS signal to an IP signal using a VoIP technique or other conversion technique 820 such as disclosed in the present application or applicant's previous applications incorporated by reference. This converted IP signal may then be sent to the middleware server in step 830. In addition, the middleware server may be configured to accept POTS signals directly through an input POTS line, although this is not the preferred embodiment of the present invention. However, the overall idea behind the present invention, as illustrated in
In step 840, the alarm signals, having been received in different formats, are reformatted at the middleware server. Applicant's middleware server and processes have been described in more detail in the applications incorporated by reference and the details are not described here for the purposes of brevity and clarity. Data from incoming signals (e.g., alarm panel serial number, incoming phone number, IP address or other indicia) are used to identify the customer and the alarm system type. From this data, the alarm signal may be reformatted into a common, single format. Thus, for example, IP signals from a number of different manufacturers may be reformatted to an industry standard alarm signal format or a single proprietary format. The desired output format may be determined by the format desired by the monitoring company, which may possess equipment accepting one or more particular formats.
This form a may include a legacy POTS format favored by older alarm companies and monitoring companies. If an IP format is selected, this signal may be sent via Internet directly the monitoring company in step 870. In step 850, middleware functions may be performed. Again, these functions have been described in applicant's previous applications incorporated by reference. These functions include, but are not limited to, notifying a customer directly via cell phone, SMS, Internet, or other means, and allowing the customer to cancel the alarm at the middleware stager, or otherwise interface and interact with the alarm system. These middleware functions may be optional, depending on the nature of the alarm company and also whether the customer paid for such services, which may be offered a la carte or as part of an alarm monitoring package.
If the alarm monitoring center accepts IP signals, these signals may be sent directly to the center via internet as illustrated by the connection between step 850 and 870. In step 860, if the alarm signals are to be sent in POTS format over a PSTN, the middleware server may dial out to the alarm center and transmit the alarm signals in POTS format using one of the known POTS alarm formats known in the art, or a format accepted by the monitoring center.
In step 870, the alarm signals are received by the monitoring center in a format acceptable to the monitoring center's existing equipment. Regardless of whether the monitoring centers uses antiquated POTS equipment, or modern IP-based equipment, the present invention is capable of interfacing with both types (and the several varieties of each). In this manner, a middleware provider can offer alarm monitoring services and then contract out the actual alarm monitoring to the alarm monitoring service that is most cost-effective, without having to force the alarm monitoring center to upgrade its equipment or change formats. For the middleware provider, changing alarm monitoring centers is simply a matter of reprogramming the output to the desired input format of the monitoring center. In this manner, the middleware provider can offer a central, branded, alarm service, and change monitoring centers in a seamless manner that is transparent to the end user.
In step 880, the alarm monitoring center receives the alarm messages in the usual manner. To the alarm monitoring center technicians and monitoring staff, the entire process is transparent—the incoming signals appear to be in the same format as all other incoming alarm signals, and the brand and type of alarm system used by the customer is irrelevant—as is the mode of communication of alarm signals—IP or POTS.
The alarm monitoring center may then perform its usual functions—calling fire, police, or other emergency services, or calling the customer to confirm whether a false alarm has been triggered. From both the customer and alarm center monitoring point of view, the entire transaction is transparent and works as if the customer's alarm was tailored to the alarm monitoring center's equipment. However, since the present invention provides middleware translation, neither the customer nor the alarm monitoring center need purchase new equipment, unless desired.
Thus, the present invention allows an alarm service provider (middleware provider) to achieve greater customer penetration and more conquest sales, as they can now offer to monitor a customer's alarm system with little or no alteration in the hardware used by the customer. And the alarm service provider can provide superior service and lower prices by being able to choose among a variety of alarm monitoring companies to do the actual alarm monitoring—and be able to switch from one to another at will (or use multiple companies) without having to swap out hardware at either end. In this manner, the middleware provider is not married to one company and thus cannot subject to arbitrary price hikes or the like by the monitoring company. In addition, the middleware provider can change alarm monitoring companies if the service from the alarm monitoring company is less expected.
While the preferred embodiment and various alternative embodiments of the invention have been disclosed and described in detail herein, it may be apparent to those skilled in the art that various changes in form and detail may be made therein without departing from the spirit and scope thereof.
The present application is also a Continuation-In-Part (CIP) of co-pending U.S. patent application Ser. No. 13/004,917 filed on Jan. 12, 2011 and incorporated herein by reference; application Ser. No. 13/004,917 is a Continuation-In-Part application of U.S. patent application Ser. No. 12/018,724, filed on Jan. 23, 2008 and incorporated herein by reference, which in turn is a Continuation-In-Part of U.S. patent application Ser. No. 11/517,025, filed on Sep. 7, 2006, and incorporated herein by reference; which in turn is a Continuation-In-Part of U.S. patent application Ser. No. 11/226,857 filed on Sep. 14, 2005 and incorporated herein by reference; application Ser. No. 11/226,857 in turn claims priority from Provisional U.S. Patent Application Ser. No. 60/651,662 filed on Feb. 11, 2005 and incorporated herein by reference; application Ser. No. 11/226,857 is also a Continuation-In-Part (CIP) of co-pending application Ser. No. 10/861,790, filed on Jun. 7, 2004, and incorporated herein by reference; application Ser. No. 11/226,857 is in turn a Continuation-In-Part of U.S. patent application Ser. No. 10/840,280 filed on May 7, 2004, and incorporated herein by reference, which in turn is Continuation-In-Part of U.S. patent application Ser. No. 10/462,708 filed on Jun. 17, 2003, (now U.S. Pat. No. 7,245,705) and incorporated herein by reference, which in turn claims priority from Provisional U.S. Patent Application Ser. No. 60/389,960, also incorporated herein by reference; The present application is also a Continuation-In-Part (CIP) of co-pending U.S. patent application Ser. No. 12/504,709 filed on Jul. 17, 2009 and incorporated herein by reference; application Ser. No. 12/504,709 is also a Continuation-In-Part (CIP) of U.S. patent application Ser. No. 11/348,291 filed on Feb. 6, 2006, now U.S. Pat. No. 7,734,020 and incorporated herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
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 |
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 | 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 |
8456293 | Trundle et al. | Jun 2013 | B1 |
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 |
20020103898 | Moyer | Aug 2002 | A1 |
20020147892 | Naidoo et al. | Oct 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 |
20060176167 | Dohrmann | Aug 2006 | A1 |
20060212793 | Marejka et al. | Sep 2006 | A1 |
20060239250 | Elliot et al. | Oct 2006 | A1 |
20070115930 | Reynolds et al. | May 2007 | A1 |
20070143838 | Milligan | Jun 2007 | A1 |
20070155412 | Kalsukis | Jul 2007 | A1 |
20080084291 | Campion, Jr. | Apr 2008 | A1 |
20080117029 | Dohrmann | 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 | 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 |
20110319071 | Beppler et al. | Dec 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 |
20130215266 | Trundle | Aug 2013 | A1 |
20130234840 | Trundle | Sep 2013 | A1 |
Entry |
---|
U.S. Appl. No. 13/939,460, Harvey Elliot et al. |
U.S. Appl. No. 14/039,573, Michael Gregory. |
U.S. Appl. No. 14/039,821, Michael Gregory. |
U.S. Appl. No. 14/050,655, Harvey Elliot et al. |
Number | Date | Country | |
---|---|---|---|
20120027010 A1 | Feb 2012 | US |
Number | Date | Country | |
---|---|---|---|
60651662 | Feb 2005 | US | |
60389960 | Jun 2002 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 13004917 | Jan 2011 | US |
Child | 13194912 | US | |
Parent | 12018724 | Jan 2008 | US |
Child | 13004917 | US | |
Parent | 11517025 | Sep 2006 | US |
Child | 12018724 | US | |
Parent | 11226857 | Sep 2005 | US |
Child | 11517025 | US | |
Parent | 10861790 | Jun 2004 | US |
Child | 11226857 | US | |
Parent | 10840280 | May 2004 | US |
Child | 10861790 | US | |
Parent | 10462708 | Jun 2003 | US |
Child | 10840280 | US | |
Parent | 13194912 | US | |
Child | 10840280 | US | |
Parent | 12504709 | Jul 2009 | US |
Child | 13194912 | US | |
Parent | 11348291 | Feb 2006 | US |
Child | 12504709 | US |