This disclosure relates generally to security systems and, more specifically, to garage door status and control via a security system.
Security systems are widely used to protect property and for personal safety. Security systems generally include a control panel, which controls the overall operation of the system, one or more keypads for user access to the system, and various detectors and sensors.
Security systems may generate an alarm in response to any number of events, such as unauthorized entry, fire, a medical emergency, or manual alarm activation. Further, a security system may be associated with a service that remotely monitors the status of the security system. Thus, if the security system generates an alarm, a notification signal may be transmitted via a wired and/or wireless communications link to a central station. Upon receiving the notification signal, security service personnel at the central station may attempt to contact the property owner (i.e., the party at the secured location) to verify the alarm. If it is appropriate to do so, the security service personnel may, upon confirmation of the alarm, contact an emergency response agency (e.g., the police department, the fire department, or an emergency medical team, etc.).
Security systems have therefore enhanced the ability of homeowners and businesses to monitor their premises and to protect against break-ins and the crimes that can accompany them (e.g., theft, damage to property, assault and battery, stalking, intrusion into privacy, etc.).
In one embodiment, a centralized garage door control and management method is described. At least one of a garage door status query request or a garage control command is sent to a garage door control peripheral. At least one of the garage door status query request or the garage control command is received at the garage door control peripheral. A garage door status may be transmitted to a controller.
In one example, the garage door status may be transmitted to the controller at pre-defined intervals. In one configuration, the garage door control peripheral may be associated with a legacy garage door opener. A change of state of the garage door may be sensed. In one example, a signal indicative of a garage door status change may be detected. A relay control device may be toggled from a first position to a second position in response to the detected signal.
At least one of an audible alert or a visual alert may be conveyed proximate the garage door at least one of prior to, during, or after a garage door change of state. One or more garage control commands may be convened from the controller to the peripheral garage control unit. One or more of the garage door commands may be converted.
A centralized garage door control and management system is also described. The system may include a controller, and a garage door control peripheral. The garage door control peripheral may be configured to receive at least one of a garage door status query request or a garage door command from the controller, and transmit a garage door status to the controller. The system may further include a garage door system control and a garage door system.
A computer program product for a centralized garage door control and management system is also described. The computer program product may include a non-transitory computer readable medium storing instructions executable by a processor to send at least one of a garage door status query request or a garage control command to a garage door control peripheral, receive at a garage door control peripheral at least one of the garage door status query request or the garage control command, and transmit the garage door status to a controller.
A centralized garage door control and management system is further described. The system may include means for sending at least one of a garage door status query request or a garage control command to a garage door control peripheral, means for receiving at a garage door control peripheral at least one of the garage door status, query request, or the garage control command, and means for transmitting the garage door status to a controller.
In one embodiment, a garage door system may include one or more garage doors and at least one sensor configured to sense data indicative of a status of a garage door of the one or more garage doors. The sensor may also be configured to convey the sensed data to an alarm system controller.
In yet another specific embodiment, an alarm system comprises a garage door system including a sensor for detecting a garage door status change and conveying a signal indicative thereof. The alarm system may also include an alarm system controller including a relay control device configured for toggling from one position to another position upon receipt of the signal from the sensor. According to another specific embodiment, the alarm system controller may also include a module to receive a signal indicative of a status of a garage door and an interface configured to transmit one or more commands for controlling the garage door.
Of course, methods of operating an alarm system are also within the scope of the present systems and methods. Such a method may include sensing a status of a garage door and conveying sensed data indicative of the status of the garage door to an alarm system controller.
In another specific embodiment, a method may include querying a garage door system for a status of a garage door and receiving sensed data indicative of the status of a garage door at an alarm system controller.
The foregoing has outlined rather broadly the features and technical advantages of examples according to the disclosure in order that the detailed description that follows may be better understood. Additional features and advantages will be described hereinafter. The conception and specific examples disclosed may be readily utilized as a basis for modifying or designing other structures for carrying out the same purposes of the present disclosure. Such equivalent constructions do not depart from the spirit and scope of the appended claims. Features which are believed to be characteristic of the concepts disclosed herein, both as to their organization and method of operation, together with associated advantages will be better understood from the following description when considered in connection with the accompanying figures. Each of the figures is provided for the purpose of illustration and description only, and not as a definition of the limits of the claims.
A further understanding of the nature and advantages of the embodiments may be realized by reference to the following drawings. In the appended figures, similar components or features may have the same reference label. Further, various components of the same type may be distinguished by following the reference label by a dash and a second label that distinguishes among the similar components. If only the first reference label is used in the specification, the description is applicable to any one of the similar components having the same first reference label irrespective of the second reference label.
While the embodiments described herein are susceptible to various modifications and alternative forms, specific embodiments have been shown by way of example in the drawings and will be described in detail herein. However, the exemplary embodiments described herein are not intended to be limited to the particular forms disclosed. Rather, the instant disclosure covers all modifications, equivalents, and alternatives falling within the scope of the appended claims.
Referring in general to the accompanying drawings, various embodiments of the present systems and methods are illustrated to show the structure and methods for installing a component within a system, such as a security system. Common elements of the illustrated embodiments are designated with like numerals. It should be understood that the figures presented are not meant to be illustrative of actual views of any particular portion of the actual device structure, but are merely schematic representations which are employed to more clearly and fully depict embodiments of the present systems and methods.
The following provides a more detailed description of the present systems and methods and various representative embodiments thereof. In this description, functions may be shown in block diagram form in order not to obscure the present systems and methods in unnecessary detail. Additionally, block definitions and partitioning of logic between various blocks is exemplary of a specific implementation. It will be readily apparent to one of ordinary skill in the art that the present systems and methods may be practiced by numerous other partitioning solutions. For the most part, details concerning timing considerations and the like have been omitted where such details are not necessary to obtain a complete understanding of the present systems and methods and are within the abilities of persons of ordinary skill in the relevant art.
In this description, some drawings may illustrate signals as a single signal for clarity of presentation and description. It will be understood by a person of ordinary skill in the art that the signal may represent a bus of signals, wherein the bus may have a variety of bit widths and the present systems and methods may be implemented on any number of data signals including a single data signal.
As noted above, a security system may include one or more sensors linked to a controller, which may include an interface that can be used by a user. It is noted that a “controller” may also be referred to herein as a “control unit” or a “control panel.” Further, it is noted that the term “security system” as used herein may also include “automation systems.” Thus, although the present systems and methods is described with reference to “security systems,” the systems and methods is not so limited. Rather, the present systems and methods may include any security, alarm, or automation (e.g., home or business) systems.
Via a controller, a user may arm (e.g., when leaving their residence) and disarm (e.g., when entering their residence) the security system. The controller may provide other functionality, such as a physical duress alarm, two-way voice communication, a siren, etc. Security sensors may be configured to monitor for various events. For example, a door/window sensor may be configured to detect when a door/window has been opened, a motion detector may be configured to detect motion. Other sensors may be configured to detect breaking of glass.
In addition to a local controller, which monitors sensor activity on premises, a security system may include a central monitoring system. For residential security systems, a remote central monitoring system may be a third party vendor. For commercial and industrial security systems, security or other personnel may monitor the premises. In commercial and industrial settings, the controller can be integrated into a larger security system. In any event, when sensor monitoring is activated and a sensor indicates a physical disturbance, the controller can activate an alarm. In response to an alarm, the controller can activate an audible siren and/or send an indication of the alarm to a central monitoring entity via a security event signal. The central monitoring entity can then initiate a response, such as contacting the owner of the premises, sending security personnel, contacting authorities, or a combination thereof.
Generally, sensors 101 include any of a variety of different types of sensors, such as door and window sensors, motion sensors, glass break sensors (e.g., detecting a physical break or detecting the sound of a glass break), etc. Generally, controller 102 is configured to monitor sensors 101 for alarm conditions via communication links 104 and relay alarms to monitoring system 103 via communication link 106.
Controller 102 includes sensor monitoring module 111, user interface 112, and alarm module 113. Sensor monitoring module 111 is configured to monitor sensors 101. Sensors 101 can sense and/or indicate a change in their physical surroundings (e.g., a normally closed connection becomes open, a signal indicating that the sound of breaking glass was detected, etc.), which may be indicative of an unauthorized access, on communication links 104. For example, a circuit connected to a door sensor can transition from closed to open (or at least to a resistance exceeding a pre-determined resistance threshold) indicating that a door has been opened. A motion sensor can send an electrical signal indicative of detected motion. Sensor monitoring module 111 may monitor communication links 104 for indications and signals sent from sensors 101. Upon sensor monitoring module 111 receiving an indication or signal of a change in physical surroundings, sensor monitoring module 111 may send the indication or signal to alarm module 113. When appropriate, alarm module 113 can treat a monitored indication or signal from a sensor as an alarm condition.
User interface 112 can include an input interface and an output interface. The input interface can comprise a physical input interface or virtual input interface that includes one or more of a numeric key pad (e.g., for entering a disarm code, etc.), sensor activation buttons, physical duress buttons, etc. The input interface can also include a condenser for receiving audio input and/or communicating with monitoring system 103. The output interface includes an output display device that displays system status, such as armed, disarmed, sensors/zones that have detected change in physical surroundings, etc. The output interface can also include a speaker that audibly outputs information similar to that displayed on the output display device. The speaker can also be used by monitoring system 103 to communicate with a user of controller 102.
As depicted in
Whereas conventional garage door controls are exclusively managed using one or more dedicated controls (e.g., remote unit, keypad, and/or wall console), garage door control system 300 integrates a conventional garage door control 302 with controller 306, and manages one or more garage doors of garage door system 302a through controller 306. Managing garage doors systems centrally using controller 306 integrates garage door management into a larger home automation scheme.
Garage door system control 302 can, in one or more embodiments, comprise a conventional garage door system control that controls operation of one or more garage doors. Thus, garage door control system 300 can be built around existing garage door controls without replacing garage door control hardware. As will be appreciated, conventional garage door systems may require physical presence of an operator at, or near, the garage door system to interact with the garage door controllers, and/or determine a status (i.e., closed or open) of one or more garage doors. One or more embodiments of the disclosure address these deficiencies by integrating a control peripheral 304 with garage door system control 302 and controller 306. As indicated by the double-ended arrow, the control peripheral 304 is configured to communicatively interface with garage door system control 302. The particular manner in which control peripheral 304 interfaces with garage door system control 302 can vary depending on the architecture of garage door system control 302. For instance, in some implementations, control peripheral 304 may communicatively interface with garage door system control 302 via a hard-wired serial interface (e.g., RS-232, I2C, SPI, etc.). Any other appropriate communicative interface is also within the scope of the present systems and methods.
Control peripheral 304 includes a hardware and/or software-based garage door system interface 304a configured to send commands to the garage system control 302, and to receive garage door status information from garage door system control 302. In some embodiments, garage door system interface 304a can be configured to supplement existing functionality of garage door system control 302. Control peripheral 304 may also include an interface 304b configured to communicate with a corresponding interface 306b of controller 306. According to one embodiment of the present disclosure, interface 304b and interface 306b may each comprise a wireless interface. According to another embodiment, interface 304b and interface 306b may each comprise a wired interface. Thus, control peripheral 304 is configured to transmit garage door status 310a to controller 306, and to receive garage door commands 310b from controller 306. Control peripheral 304 can be configured to send garage door status 310a at pre-defined intervals or in response to a particular request by controller 306 (as part of garage door commands 310b, for example). Garage door status 310a can include any combination of status information available from garage door system control 302.
As mentioned, control peripheral 304 is configured to receive garage door commands 310b from controller 306 via interface 304b. Garage door commands 310b can then be passed, via garage door system interface 304a, to garage door system control 302. Garage door system interface 304a can perform any conversion appropriate to facilitate communications between garage door system control 302 and controller 206 (e.g., converting garage door status 310a and/or garage door commands 310b).
In one or more embodiments, garage door system control 302 and control peripheral 304 can be combined as a single unit. Thus, instead of control peripheral 304 taking over or supplementing functionality of garage door system control 302, garage door system control 302 can itself be configured to communicate with controller 306 (e.g., by including a wireless interface, etc.) to send garage door status 310a to controller 306 and to receive garage door commands 310b from controller 206. Such an embodiment may be useful when initially installing a garage door system control 302 that integrates with the control panel 306, instead of adding this functionality to an already existing garage door system control.
Using control peripheral 304, controller 306 can centrally manage and control garage door system control 302. Controller 306 can comprise functionality typical of an alarm system controller. As shown, for instance, controller 306 is configured to interface with one or more alarm sensors 306d which can detect physical disturbances on the premises, such as those that would signal possible break-in attempts. Alarm sensors 306d can also detect other potentially dangerous situations, such as fire, flood, etc.
Controller 306 includes a hardware and/or software-based garage door module 306a, which is configured to intelligently and dynamically manage operation of garage door system control 302. At a basic level, garage door module 306a processes received garage door status 310a and sends garage door commands 310b to control peripheral 304. The status can include, for example, a state of one or more garage doors (i.e., whether the garage doors are open or closed). The garage door commands can comprise commands that directly instruct garage door system control 302 to change a state of one or more garage doors (i.e., open or close).
Furthermore, in addition to controlling and monitoring garage door status locally (e.g., at the garage door system control 302 and/or at controller 306), a user (e.g., a home or business owner, etc.) can use garage door control system 300 to manage and monitor one or more garage doors remotely over a network 314 using a remote computing device 308. For instance, as illustrated in
As illustrated, controller 306 is configured to communicate bi-directionally with one or more remote computing devices 308 through network 314, by sending garage door system related data 312b to each remote computing device 308, and by receiving remote garage door commands 312a from one or more remote computing devices 308. For example, a remote computing device 308 (e.g., a web client, a mobile client, etc.) can receive garage door system related data 312b regarding, for example only, present garage door status. Remote computing device 308 can then present this information to a user via one or more user interfaces. The user interfaces can present the information in any appropriate form. Thus, controller 306, by communicating with remote computing device(s) over network 314, can enable a user to access garage door system related data from virtually any location.
Further, the user interface at remote computing device 308 can be configured to enable remote user input. Thus, a user can enter, or cause to be generated, remote garage door commands 312a. Thus, alarm system controller 306, by interfacing with network 314 and exchanging garage door system related data 312b and remote garage door commands 312a, enables users to interact with their garage door system from remote computing devices 308, where they may view status and/or manually operate garage door system 302.
In one or more embodiments, garage door module 306a and/or remote computing device 308 can send a user alerts or other garage door system-related information. For instance, a user may be notified (e.g., via an e-mail, a SMS message, or other alert) when a status of a garage door has change, when the garage door system has malfunctioned, etc. It will be appreciated that these are only a few of the alerts that may be sent, and that any garage door system-related alert falls within this disclosure.
Further, garage door system 400 may include an alert device 408, which may comprise, for example, a speaker and/or a light. Alert device 408 may be configured to convey an alert after receipt of a command and prior to and/or during a change of state of garage door 402. Thus, upon receipt of a command to open or close a garage door at, for example, garage door controller 404, alert device 408 may convey an alert proximate garage door 402. Further, controller 306 may convey an alert via user interface 112 (e.g., see
It is noted that sensor events (e.g., events detected by sensor 406) may be sent to monitoring system 103 (e.g., see
While the foregoing disclosure sets forth various embodiments using specific block diagrams, flowcharts, and examples, each block diagram component, flowchart step, operation, and/or component described and/or illustrated herein may be implemented, individually and/or collectively, using a wide range of hardware, software, or firmware (or any combination thereof) configurations. In addition, any disclosure of components contained within other components should be considered exemplary in nature since many other architectures can be implemented to achieve the same functionality.
The process parameters and sequence of steps described and/or illustrated herein are given by way of example only and can be varied as desired. For example, while the steps illustrated and/or described herein may be shown or discussed in a particular order, these steps do not necessarily need to be performed in the order illustrated or discussed. The various exemplary methods described and/or illustrated herein may also omit one or more of the steps described or illustrated herein or include additional steps in addition to those disclosed.
Furthermore, while various embodiments have been described and/or illustrated herein in the context of fully functional computing systems, one or more of these exemplary embodiments may be distributed as a program product in a variety of forms, regardless of the particular type of computer-readable media used to actually carry out the distribution. The embodiments disclosed herein may also be implemented using software modules that perform certain tasks. These software modules may include script, batch, or other executable files that may be stored on a computer-readable storage medium or in a computing system. In some embodiments, these software modules may configure a computing system to perform one or more of the exemplary embodiments disclosed herein.
The foregoing description, for purpose of explanation, has been described with reference to specific embodiments. However, the illustrative discussions above are not intended to be exhaustive or to limit the systems and methods to the precise forms disclosed. Many modifications and variations are possible in view of the above teachings. The embodiments were chosen and described in order to best explain the principles of the present systems and methods and their practical applications, to thereby enable others skilled in the art to best utilize the present systems and methods and various embodiments with various modifications as may be suited to the particular use contemplated.
Unless otherwise noted, the terms “a” or “an,” as used in the specification and claims, are to be construed as meaning “at least one of.” In addition, for ease of use, the words “including” and “having,” as used in the specification and claims, are interchangeable with and have the same meaning as the word “comprising.” In addition, the term “based on” as used in the specification and the claims is to be construed as meaning “based at least upon.”
The present Application is a continuation of U.S. Provisional patent application Ser. No. 14/179,312, titled: “GARAGE DOOR STATUS AND CONTROL VIA A SECURITY SYSTEM,” filed on Feb. 12, 2014, which claims priority to U.S. Provisional Patent Application No. 61/792,399, titled: “GARAGE DOOR STATUS AND CONTROL VIA A SECURITY SYSTEM,” filed on Mar. 15, 2013. The disclosures of each of which are included herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
4338526 | Martin | Jul 1982 | A |
5565843 | Meyvis | Oct 1996 | A |
5780987 | Fitzgibbon | Jul 1998 | A |
5781107 | Ji | Jul 1998 | A |
6184787 | Morris | Feb 2001 | B1 |
6192282 | Smith | Feb 2001 | B1 |
6310548 | Stephens, Jr. et al. | Oct 2001 | B1 |
6392560 | Stuehling | May 2002 | B1 |
7468676 | Styers et al. | Dec 2008 | B2 |
7602283 | John | Oct 2009 | B2 |
20020180600 | Kirkland | Dec 2002 | A1 |
20050174250 | Dierking | Aug 2005 | A1 |
20050253710 | Eskildsen | Nov 2005 | A1 |
20060158339 | Brundula | Jul 2006 | A1 |
20060187034 | Styers | Aug 2006 | A1 |
20060202815 | John | Sep 2006 | A1 |
20060220834 | Maeng | Oct 2006 | A1 |
20080062000 | Styers | Mar 2008 | A1 |
20080079570 | Fineman et al. | Apr 2008 | A1 |
20100171588 | Chutorash et al. | Jul 2010 | A1 |
20100289618 | Crucs | Nov 2010 | A1 |
20100289661 | Styers | Nov 2010 | A1 |
20120260575 | Monaco | Oct 2012 | A1 |
20130321127 | Wilder | Dec 2013 | A1 |
Number | Date | Country | |
---|---|---|---|
61792399 | Mar 2013 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 14179312 | Feb 2014 | US |
Child | 15707694 | US |