[go: up one dir, main page]

HK1201368B - Security system and method - Google Patents

Security system and method Download PDF

Info

Publication number
HK1201368B
HK1201368B HK15101835.0A HK15101835A HK1201368B HK 1201368 B HK1201368 B HK 1201368B HK 15101835 A HK15101835 A HK 15101835A HK 1201368 B HK1201368 B HK 1201368B
Authority
HK
Hong Kong
Prior art keywords
control unit
lifestyle
feature
safety
user interface
Prior art date
Application number
HK15101835.0A
Other languages
Chinese (zh)
Other versions
HK1201368A1 (en
Inventor
S.夏皮罗
R.诺斯
T.A.雷德
J.柏多莫
A-M.罗斯
J.T.布拉克
Original Assignee
Adt美国控股股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Adt美国控股股份有限公司 filed Critical Adt美国控股股份有限公司
Priority claimed from PCT/US2012/048645 external-priority patent/WO2013019659A1/en
Publication of HK1201368A1 publication Critical patent/HK1201368A1/en
Publication of HK1201368B publication Critical patent/HK1201368B/en

Links

Description

Security system and method
Technical Field
The present invention relates to security systems, and more particularly to security system control using wireless communication.
Background
As more and more homeowners and business owners attempt to protect their building power supplies from various hazards and threats, there is an increasing need for security systems that monitor home and business alarm conditions. Such hazards and threats include intrusions, fires, carbon monoxide and floods, and other hazards that may be monitored and reported to a monitoring station.
Conventional security systems typically use wall-mounted control panels (typically installed in less-entry areas of the home) that receive information from various sensors, and may trigger an alarm based on the received information. These triggered alarms are then reported by the control panel to the monitoring center via Plain Old Telephone Service (POTS) lines, Digital Subscriber Lines (DSL), or cellular wireless means so that the monitoring center can take appropriate action. However, the installation and maintenance complexity associated with these systems is high because the installer must physically mount the control panel to the wall and configure the various sensors. These systems also typically include manufacturer specific technology designed for the manufacturer's security applications and as such are limited to use with only certain life safety type devices, such as door and window contacts, smoke detectors, motion detectors, and the like.
The same is true for the more recent all-in-one (AIO) security systems in which a control panel and a user interface, such as a keypad, are combined in a single unit. To reduce some of the costs associated with installing such systems, portable AIO systems are implemented so that units can be relocated around building power supplies without permanent installation. For example, the unit may be placed on a desktop or on a floor, but communicate with the life safety sensors in a similar manner to a wall-mounted safety panel.
Although the complexity of portable AIO systems is less than conventional security panel installations, portable AIO systems may be more susceptible to damage and tampering. For example, portable AIO systems are often located near an entrance or exit, even when the sensor is activated, a chirp or a reminder to the homeowner to remove the system announcing its location. A thief may break into a home protected by the portable AIO, who can damage/disable the portable AIO system and prevent the AIO system from triggering an alarm. The phenomenon of a thief intruding and disabling the control board of a portable AIO system is known as "intrusion and vandalism" and is an increasing problem.
Although homeowners may take steps to prevent "break-in and damage" by hiding the portable AIO system in a remote closet or back room, such a location is often not practical because the homeowner or business owner still needs to access the portable AIO system to arm/disarm or otherwise control the system through the embedded keypad. For example, a business owner may be forced to start arming a portable AIO system located in a backroom and then exit the building power supply before arming the system. In other words, although portable AIO systems may not be as complex as conventional wall-mounted security panels, they are also relatively easy to tamper with and disable.
Another problem associated with some portable AIO systems is that these systems are designed to operate using only an embedded user interface. If the control panel is damaged, the system may become inoperable due to weather or tampering by a thief. In addition, a single control point on the building's power supply makes configuration of the system more difficult, as the installer often has to walk back and forth between the control panel and the various sensors during installation to configure the sensors.
In addition, portable AIO security systems and conventional security panels are typically limited to controlling and monitoring life safety, such as intrusion and fire detection. Today, however, homeowners or business owners desire to use additional lifestyle functions (such as lighting control, temperature control, and remote viewing of video). Such lifestyle systems operate in a manner that is formed substantially independently of life safety systems. For example, lifestyle devices provide different types of event information and are typically operated and managed by different providers and/or remote systems than those used to monitor life safety. Thus, to add this lifestyle functionality, the user must have completely separate hardware/software/services related to controlling and monitoring these additional features, with a separate user interface dedicated only to controlling the separate system.
Disclosure of Invention
The present invention advantageously provides a method and system for security control management.
According to one embodiment, a safety control device is provided. The security control device includes a wireless communication element that supports a plurality of wireless communication protocols. The wireless communication element is configured to provide wireless communication with the user interface device and the at least one building-based device. The safety control device includes a remote communication element configured to provide remote communication with a monitoring center. The security control device includes a processor in communication with a local wireless communication element and a remote communication element. The processor is configured to use the wireless communication element to communicate with the user interface device to receive local control and configuration data. The processor is also configured to use the remote communication element to communicate data associated with at least one of the life safety feature and the lifestyle feature with the monitoring center.
According to another embodiment, a system is provided that includes a user interface device configured to communicate local control data and configuration data, and a security control device in communication with the user interface device. The security control device includes a communication subsystem providing a plurality of communication protocols and configured to provide wireless communication with the user interface device and the building-based device. The communication subsystem is further configured to provide for remote communication with a remote monitoring center. The security control device includes a processor configured to communicate with the user interface device using the communication subsystem to receive local control and configuration data. The processor is further configured to communicate data associated with at least one of the life safety feature and the lifestyle feature with a remote monitoring center using the communication subsystem.
According to yet another embodiment, a portable user interface device for use with a safety control unit is provided. The user interface device includes an alarm configured to provide an audible alert. The user interface device also includes a power source configured to power the portable user interface device. The user interface device also includes a processor configured to trigger an alarm upon the occurrence of a triggering condition.
According to yet another embodiment, a method for controlling features of a security system is provided. The security system includes a security control device in communication with a user interface device, wherein the security control device includes a communication subsystem that provides a plurality of communication protocols. The communication subsystem is configured to provide wireless communication with the user interface device and to provide remote communication with a remote monitoring center. A communication subsystem is used to communicate with the user interface device to receive local control and configuration data. Communicating data associated with at least one of a life safety feature and a lifestyle feature with a remote monitoring center using a communication subsystem.
Drawings
The invention, together with the attendant advantages and features, will be best understood from the following detailed description when read with the accompanying drawings in which:
FIG. 1 is a block diagram of a security control system for security control management constructed in accordance with the principles of the present invention;
FIG. 2 is a block diagram of a safety control unit constructed in accordance with the principles of the present invention;
FIG. 3 is a block diagram of a user interface device constructed in accordance with the principles of the present invention;
FIG. 4 is a block diagram of the software architecture of a safety control unit constructed in accordance with the principles of the present invention;
FIG. 5 is a flow chart of an exemplary safety control unit power management process of the present invention constructed in accordance with the principles of the present invention; and
FIG. 6 is a flow chart of an exemplary user interface device power management process of the present invention constructed in accordance with the principles of the present invention.
Detailed Description
The present invention advantageously provides a system, apparatus and method for security control management. Accordingly, the system and method components have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the embodiments of the present invention so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein
As used herein, relational terms such as "first" and "second," "top" and "bottom," and the like may be used solely to distinguish one entity or element from another entity or element without necessarily requiring or implying any physical or logical relationship or order between such entities or elements.
Referring now to the drawings in which like reference designators refer to like elements from that shown in FIG. 1, there is shown in FIG. 1 a safety control system constructed in accordance with the principles of the present invention and designated generally as "10". The system 10 may include one or more user interface devices 12 a-12 n (collectively, "user interface devices 12"), one or more building devices 14 a-14 n (collectively, "building devices 14"), a security control unit 16, one or more networks 18 a-18 n (collectively, "networks 18"), and one or more remote monitoring centers 20 a-20 n (collectively, "remote monitoring centers 20") in communication with each other.
The user interface device 12 may be a wireless device that enables a user to communicate with the security control unit 16. The user interface devices 12 may be a portable control keypad/interface 12a, a computer 12b, a mobile telephone 12c and a tablet 12n, among other devices that enable a user to interface with the security control unit 16. The user interface device 12 may communicate with at least the security control unit 16 using one or more wireless communication protocols known to those skilled in the art. For example, the portable control keypad 12a may communicate with the security control unit 16 via a ZigBee-based communication link 22, e.g. a network based on the Institute of Electrical and Electronics Engineers (IEEE)802.15.4 protocol, and/or a Z-wave based communication link 24, or via a local area network of building power, e.g. a network based on the Institute of Electrical and Electronics Engineers (IEEE)802.11 protocol. The user interface device 12 is discussed in detail with reference to fig. 3.
The building equipment 14 may include one or more types of sensors, control and/or image capture devices. For example, the types of sensors may include various life safety related sensors such as motion sensors, fire sensors, carbon monoxide sensors, flood sensors, and tactile sensors, as well as other sensor types known in the art. The control devices may include, for example, one or more lifestyle-related devices configured to adjust at least one building power setting, such as lighting, temperature, energy usage, door lock and power settings, and other settings associated with the building power supply or devices on the building power supply. The image capture device may include a digital camera and/or a video camera, among other well-known image capture devices. The building equipment 14 may communicate with the security control unit 16 via a proprietary wireless communication protocol, and may also use Wi-Fi, both of which are well known. Those skilled in the art will also appreciate that various additional sensors and control and/or image capture devices may be related to life safety or lifestyle, depending on what the sensors, control and image capture devices do and how these sensors, control and image devices are used by the system 10. One of the advantages of the present invention is that it enables the use of any of these devices, whether they be life-safe or life-style.
The security control unit 16 may provide management functions such as power management, building equipment management, and alarm management, among other functions. In particular, the security control unit 16 may manage one or more life safety and lifestyle features. Life safety features may correspond to safety system functions and settings associated with building power conditions that may cause harm to human life, such as carbon monoxide detection and intrusion detection. The lifestyle features may correspond to security system functions and settings such as lighting and thermostat functions associated with non-life threatening conditions of the video capture device and the building power supply. Exemplary safety control unit 16 components and functions will be described in detail with reference to fig. 2.
The security control unit 16 may communicate with the network 18 via one or more communication links. In particular, the communication link may be a broadband communication link, such as a wired cable modem or ethernet communication link 26, and a digital cellular communication link 28, such as a Long Term Evolution (LTE) based link, among other broadband communication links known in the art. Broadband, as used herein, may refer to a communication link other than Plain Old Telephone Service (POTS) lines. The ethernet communication link 26 may be an IEEE 802.3 based communication link. The network 18 may be a wide area network, a local area network, a wireless local area network, and a metropolitan area network, among others known in the art. The network 18 provides communication between the security control unit 16 and the remote monitoring center 20.
The system 10 may include a remote monitoring center 20 capable of performing monitoring, configuration, and/or control functions associated with the safety control unit 16. For example, the remote monitoring center 20 may include a remote life safety monitoring center that monitors life safety features associated with the safety control unit 16, wherein the remote monitoring center 20 receives life safety data from the safety control unit 16. For example, for fire and carbon monoxide detectors/sensors, the life safety data may include at least one of carbon monoxide readings, smoke detection readings, sensor location and time of reading, and other readings related to these detectors that may be in communication with the remote monitoring center 20. In yet another example, for a door contact detector, the life safety data may include at least one of sensor location and time to detect data, and other data related to door contact detection that may be communicated to the remote monitoring center 20.
Alarm event data from the building power supply may be used by the operating remote monitoring center for various life safety response processes to notify the owner of the building power supply, to determine if an actual alarm event has occurred in the building power supply, and to notify any appropriate response agencies (e.g., police, fire, emergency response).
The same or a separate remote monitoring center 20 may also include a lifestyle system/service that allows for various lifestyle features associated with the safety control unit 16. The remote lifestyle system may receive lifestyle data from the security control unit 16. For example, for temperature control, the life safety data may include thermostat readings. In yet another example, for a video capture device, the lifestyle data can include at least one of captured images, video, time of video capture, and video location, as well as other data related to the video capture device that can communicate with the remote monitoring center 20. The remote monitoring center 20 may also provide updates to the security control unit 16, such as updates to features associated with the life safety and/or lifestyle operating systems. Those skilled in the art will appreciate that video and other data may also be used by the life safety monitoring center.
An exemplary security control unit 16 for managing a building power security system will be described with reference to fig. 2. The security control unit 16 may include a communication subsystem 30 configured to provide communication with the user interface device 12, the building devices 14, and the network 18. In particular, the communication subsystem 30 may include a wireless communication element 32 and a remote communication element 34. The wireless communication element 32 provides wireless communication with the user interface device 12 and the building device 14. The wireless communication element 32 may support one or more wireless communication protocols, such as ZigBee, Z-wave, and Wi-Fi, e.g., IEEE 802.11, among other wireless communication protocols that support wireless data transmission.
The wireless communication element 32 may be comprised of one or more hardware components, wherein each hardware component is configured to provide wireless communication using a particular protocol. For example, the wireless communication element 32 may include a ZigBee hardware component configured to provide ZigBee-based communication and a Z-wave hardware component configured to provide Z-wave-based communication. The hardware components associated with the wireless communication element 32 may be internal components within the security control unit 16 such that these features are embedded or standard features. Alternatively, any one or more of the hardware components associated with the wireless communication element 32 may be external components that may be replaced by a user, homeowner, or installer. For example, ZigBee and Z-wave hardware component modules may be internal components, while Wi-Fi hardware components may be external components that allow upgrades. The wireless communication element 32 may broadcast a wireless signal so that the user interface device 12 may be directly connected to the security control unit 16. For example, the wireless communication element 32 may provide a Wi-Fi encrypted Service Set Identifier (SSID) and a path for communicating with multiple user interface devices 12.
By supporting multiple wireless communication protocols, the wireless communication element 32 enables the security control unit 16 to be used with various user interface devices 12 and building devices 14 that are designed to only operate using a particular wireless communication protocol. Supporting multiple wireless communication protocols allows for convenient upgrades to existing user interface devices 12 and building equipment 14, with the security control unit 16 integrated with various equipment vendors that may include different wireless protocols. The wireless communication element 32 may provide two-way voice communication with the user interface device 12, which the user interface device 12 then communicates with the remote monitoring center 20. For example, the wireless communication element 32 may support voice over internet protocol (VoIP) communications. In one embodiment, the constituent components of the wireless communication element 32, such as the IEEE 802.11 communication module, may also be part of the remote communication element such that a wireless communication protocol, such as the IEEE 802.11 protocol, may be used to communicate with the remote monitoring center 20. In other words, one or more particular communication modules of the wireless communication element 32 may also be part of the remote communication element 34.
The remote communication element 34 is configured to provide broadband communication with the remote monitoring center 20 over the network 18. For example, the remote communication element 34 may be an ethernet-based hardware component that provides communication with the network 18. Alternatively or in addition to the ethernet-based hardware components, the remote communication element 34 may include Wi-Fi (IEEE 802.11) hardware components that provide communication with a home or other building network, e.g., a home wireless network, and may use some of the same components as the wireless communication element 32. The remote communication element 34 may also include cellular wireless hardware components that provide communication with at least one cellular network, such as an LTE-based cellular network. The security control unit 16 may use the ethernet communication link 26 as the primary communication link so that when the ethernet or primary communication link is not functioning properly, the cellular communication link is used for broadband communication, such as during a power outage, the home network is unavailable, i.e., the home network router has no power supply.
The safety control unit 16 may include a building power supply 36 configured to provide power to the safety control unit 16. For example, the building power supply 36 may provide power to the security control unit 16 through a household Alternating Current (AC) power outlet or other power outlets known in the art. The building power supply 36 may be a main power supply such that the safety control unit 16 operates using power from the building power supply 36 (when available). The safety control unit 16 may also include a backup power source 38 that provides power during a building power failure. The backup power source 38 may include one or more single use or rechargeable batteries configured to provide sufficient power to operate the safety control unit 16 for a first predetermined amount of time and activate the alarm 40 for a second predetermined amount of time, e.g., a user may access the safety system for at least twenty-four hours when the safety control unit 16 is powered by the backup power source 38 and the alarm may be activated and operated after twenty-four hours.
The alarm 40 may be an eighty-five decibel (dB) alarm, as well as other audible devices known in the art. The alarm 40 may be an optional component in the safety control unit 16 so that an audible warning is generated by the user interface device 12, e.g., the portable control keypad/interface 12a, rather than the safety control unit 16. In addition, the security control unit 16 may include at least one universal serial bus port (USB) to receive power from a laptop computer or other device using a USB interface. Other port types capable of providing power to the safety control unit 16 may be used based on design requirements.
The input element 42 may be configured to receive input data from a user. For example, input element 42 may be a ten digit keypad that enables a user to arm and disarm system 10. The input element 42 provides an alternative or backup way of arming and disarming the system when no user interface device 12 is available to the user. Other input elements known in the art may also be used. The safety control unit 16 may include one or more indicators, such as Light Emitting Diodes (LEDs), that may indicate the status of the safety control unit 16. For example, a first LED may be on when the security control panel is powered on, a second LED may be on when the system is armed or disarmed, a third LED may be on when connected to an internet protocol connection, a fourth LED may be on when the cellular connection is of sufficient strength, the first LED may blink under low power conditions, other LEDs and LEDs may be used on/off based on design needs. Processor 44 may be a Central Processing Unit (CPU) that executes computer program instructions stored in memory 46 to perform the functions described herein.
The memory 46 may include both non-volatile and volatile memory. For example, the non-volatile memory may include a hard drive, memory stick, flash memory, and the like. In addition, volatile memory may include random access memory and other memory known in the art. Memory 46 may store a power management module 48, a life safety operating system 50, and a lifestyle operating system 52, as well as other data and/or modules. Power management module 48 includes instructions that, when executed by processor 44, cause processor 44 to perform processes described herein, such as the power management process discussed in detail with reference to fig. 5. The life safety operating system is configured to provide life safety features associated with system 10. Lifestyle operating system 52 is configured to provide lifestyle features associated with system 10. In particular, processor 44 is configured to run life safety operating system 50 and lifestyle operating system 52 such that a separate processor is not required to run both operating systems. This single processor configuration reduces costs while still providing life safety and lifestyle features.
Memory 46 may include a Wi-Fi hijacking module (not shown) that changes security control unit 16 when the processor determines that an unauthorized person is connected to security control unit 16 through Wi-Fi. For example, the Wi-Fi hijacking module may turn off Wi-Fi and/or move to low power RF so that the user interface device 12 and/or the building device 14 may still communicate with the security control panel. The memory 46 may include an auto-registration module (not shown) configured to cause the processor 44 to wirelessly search for building devices 14 located within or near the building's power source. The auto-registration module may cause the processor 44 to forward information associated with the discovered devices 12 and 14 to the remote monitoring center 20 so that the remote monitoring center 20 may push registration data to the security control unit 16 to facilitate configuration. The security control unit 16 may use the registration data configured in the security system so that the system operates using the discovered devices 12 and/or 14. The auto-registration module reduces installation time because the devices 12 and/or 14 are automatically discovered and registered for use by the security control unit 16.
An exemplary user interface device 12 for providing local control and configuration data will be described with reference to fig. 3. The user interface devices 12 may include a portable control keypad/interface 12a, a personal computer 12b, a mobile device 12c, and a tablet 12n, among other devices. The user interface device 12 includes a communication element 54, the communication element 54 being configured to communicate with the security control unit 16 via at least one wireless communication protocol such as ZigBee, Z-wave, and Wi-Fi, among other protocols known in the art. The user interface device 12 may include a processor 56 and memory 58 corresponding to the components of the safety control unit 16, sized and capable based on design requirements. Processor 56 performs the functions described herein for user interface device 12.
Memory 58 may include a power management module 60, where power management module 60 includes instructions that, when executed by processor 56, cause processor 56 to perform processes described herein, such as the power management process discussed with reference to fig. 6. The memory 58 may store other modules and data based on design needs. The interface 62 may be a user interface configured to receive user input. For example, the interface 62 may receive local control and configuration data input from a user.
The user interface device 12 may include an alarm 64 such as an eighty-five dB alarm or other audible device known in the art. User interface device 12 may include a power supply 66 for providing power to user interface device 12. The power source 66 may include one or more rechargeable and/or disposable batteries, as well as other types of well-known batteries. In addition, the user interface device 12 may be powered by a Universal Serial Bus (USB), have an interface that allows for the connection of an external power adapter/charger, and/or other connection types.
An exemplary software architecture 68 of the safety control unit 16 will be described with reference to fig. 4. In particular, the software architecture 68 may include the life safety operating system 50, the lifestyle operating system 52, and the boot loader 54, as well as other software components related to the management and operation of the security features of the security control unit 16. Life safety operating system 50 and life style operating system 52 are configured to run in safety control unit 16, where life safety operating system 50 and life style operating system 52 run in a virtual machine configuration. The virtual machine configuration enables a single processor, such as processor 44, to separately run life safety operating system 50 while updating life style operating system 52 without negatively impacting life safety operating system 50 and associated features, i.e., life safety features remain operational when life style features are updated. The reverse is also possible. The boot loader 54 is used to load the runtime environment of the operating systems 50 and 52.
An exemplary power management process is shown in fig. 5. The power management process involves managing a security system based at least in part on monitoring the building power supply 36 and the backup power supply 38. Processor 44 determines whether building power supply 36 is malfunctioning (block S100). For example, the processor 44 may monitor the power provided by the building power supplies 36 using methods known in the art to determine if a power failure has occurred. A power failure may occur when the voltage supplied by the building power supply 36 is below a predefined voltage threshold. If processor 44 determines that a power failure has not occurred, the determination of block S100 may be repeated.
If it is determined that the building power source 36 is in a power failure condition, the processor 44 disables non-life safety features, such as life style features, while keeping life safety features enabled (block S102). For example, temperature control features associated with the lifestyle operating system may be disabled while intrusion detection, fire detection, and carbon monoxide detection features associated with life safety operating system 50 remain enabled. Power management module 48 advantageously disables non-life safety features, such as life style features associated with life style operating system 50, without interrupting life safety features associated with life safety operating system 52. This configuration helps ensure that life safety features will remain enabled during a building power supply 36 failure while reducing power consumed by disabling non-lifestyle features. For example, certain lifestyle features may require or attempt to initiate communication with the user interface device 12 and/or the remote monitoring center 20, wherein such communication may consume power, i.e., may consume limited back-up power. Other non-lifestyle features that may be disabled include turning off any safety control device LEDs and/or ending communication with the user interface device 12 while maintaining communication with the building power device. Thus, disabling at least one non-live safety feature reduces the amount of electrical energy consumed by the safety control unit 16, wherein the more non-live safety features are disabled, the greater the power savings.
The processor 44 determines whether to restore the building power supply 36 based at least in part on the monitoring of the building power supply 36 (block S104). For example, the processor 44 may constantly or periodically monitor the power level of the building power supply 36 to determine whether the power level is at or above a predetermined voltage threshold. If the processor 44 determines that the building power supply 36 has been restored, the processor 44 may restore or enable the previously disabled non-life safety feature (block S106). In other words, once the security control unit 16 is being powered by the building power supply 36, the power management process enables non-life safety features, such as lifestyle features, that may consume more power so that the non-life safety features consume minimal power from the backup power supply 38.
If it is determined that power is not restored to the building power supply 36, it is determined whether an alarm, such as an audible alarm, is triggered (block S108). Specifically, the audible alarm may be triggered after processor 44 determines that safety control unit 16 has been operating backup power supply 38 for a predetermined amount of time (e.g., twenty-four hours). The predetermined amount of time may be based on design needs and/or regulatory requirements. If it is determined that an alarm is to be triggered, either alarm 40 or alarm 64 may be triggered for a predetermined amount of time (block S116). In one embodiment, processor 44 uses communication subsystem 30 to send an alarm trigger message to user interface device 12 to trigger alarm 64 in user interface device 12. For example, the alarm 64 may be triggered for at least four minutes to alert a user of the safety control unit 16 status (such as loss of all power). The predetermined amount of time that the alarm is triggered may be based on design needs and/or regulatory requirements. Other criteria may be used to trigger an audible alarm based on design needs. After triggering the alarm 64, the safety control unit 16 may be shut down (block S118). For example, when the backup power source 38 reaches a predefined threshold, such as 10% of the charge remaining, the safety control unit 16 may perform a smooth shut down according to a shut down routine.
Referring back to block S108, if processor 44 makes a determination not to trigger an alarm, processor 44 determines whether the available charge threshold has been reached (block S110). The charge threshold may correspond to a level of backup power 38 at which another non-life safety feature may be turned off in order to reduce power consumption. For example, the different non-life safety feature may be ended each time the power level drops by a predetermined amount, such as 5% or 10%, or to a predetermined level. Further, one or more non-live safety features may be ended at a time. If the determination does not reach the feature threshold, the determination of block S104 may be repeated.
If it is determined that the charge threshold has been reached, processor 44 determines whether at least one other non-life safety feature, such as a lifestyle feature, is enabled (block S112). For example, the lighting lifestyle feature may have been previously disabled in block S102, but the temperature lifestyle feature remains enabled. If it is determined that at least one other non-life safety feature is not enabled, the determination of block S104 may be repeated. If processor 44 determines that at least one other non-live safety feature is enabled, processor 44 disables the at least one other non-live safety feature so that the non-live safety feature consumes less power from backup power source 38 (block S114). The order in which non-life safety features are disabled may vary based on design needs and power consumption of individual features or other criteria. After disabling at least one other non-life safety feature, the determination of block S104 may then be repeated. The power management process helps ensure that less important features, such as lifestyle features, remain powered by ending or disabling them. Alternatively, processor 44 may disable more than one or all non-life safety features at a time.
Fig. 6 illustrates an exemplary power management process for user interface device 12. The power management process involves managing user interface device 12 features based at least in part on monitoring of the power supply 66. For example, the processor 56 may monitor the power provided by the power supply 66 using methods known in the art. The processor 56 determines whether the power supplied by the power source 66 falls below a predefined threshold, i.e., whether the power source 66 voltage or power level is less than a threshold, based at least in part on the monitoring (block S120). The threshold may be a power and/or voltage level determined based on design requirements and/or other factors. If the processor 56 determines that the power source 66 is not below, i.e., greater than or equal to, the predetermined threshold, the determination of block S120 may be repeated.
If it is determined that the power source 66 is below the predetermined threshold, the processor 56 disables at least one non-safety feature while the life safety feature remains enabled in the user interface device 12 (block S122). For example, processor 56 may disable a lifestyle feature so that less power may be consumed by not having to perform processing, communication, and/or other functions associated with the disabled feature. Other non-security features may include a backlit keypad and/or display features. Thus, disabling at least one non-live safety feature reduces the amount of electrical energy consumed by user interface device 12 such that the more non-live safety features are disabled, the greater the power savings.
After disabling the at least one non-live safety feature, processor 56 may determine whether power source 66 is still below the threshold based at least in part on the monitoring (block S124). For example, the processor 56 may constantly or periodically monitor the voltage level of the power supply 66. If it is determined that the power source 66 is not below the threshold (i.e., greater than or equal to the threshold), the processor 56 may resume the previously disabled or terminated non-safety feature (block S126). In other words, once power source 66 is greater than or equal to the threshold, the power management process of FIG. 6 enables or executes the previously disabled non-life safety feature that may consume more power, such that the non-life safety feature consumes minimal power from power source 66. The power source 66 may rise back to the predetermined threshold level when the power source 66 is being recharged and/or when the user interface device 12 is being powered by USB, and in other instances where the power source 66 is no longer below the predetermined threshold. Alternatively, blocks S124 and S126 may be skipped or eliminated from the power management process of fig. 6 based on design needs, i.e., the process moves directly from block S122 to block S128.
If the power source 66 is determined to be below the threshold, the processor 56 determines whether an alarm, such as an audible alarm, is triggered (block S128). In particular, an audible alarm may be triggered after the processor 56 determines that the power source 66 has reached a lower predetermined threshold. For example, a lower predetermined threshold may correspond to a minimum level of power required to trigger the alarm 64 for a predetermined amount of time and/or shut down the user interface device 12. The lower predetermined threshold may be based on design requirements. If it is determined that an alarm is to be triggered, either alarm 64 or alarm 40 may be triggered for a predetermined amount of time (block S136). For example, the alarm 64 may be triggered for at least four minutes to alert the user of the user interface device 12 status (such as a lost all power state). The predetermined amount of time that the alarm is triggered may be based on design needs and/or regulatory requirements. Other criteria may be used to trigger an audible alarm based on design needs. After triggering the alarm 64, the user interface device 12 may be turned off (block S138). For example, the safety control unit 16 may perform a smooth shutdown according to a shutdown routine.
Referring back to block S128, if it is determined that an alarm is not triggered, the processor 56 determines whether a characteristic threshold has been reached (block S130). The characteristic threshold may correspond to a level of backup power 38 at which another characteristic may be turned off to reduce power consumption. For example, the difference feature may be ended each time the charge occurrence fails to reach another predetermined amount, e.g., 5% or 10%. Further, more than one feature may be disabled or ended at a time. If it is determined that the characteristic threshold value is not reached, the determination of step S124 may be repeated. Alternatively, if block S124 is skipped or excluded from the process and it is determined that the characteristic threshold has not been reached, the determination of block S128 may be performed.
If the determination reaches the feature threshold, the processor 56 determines whether at least one other non-life safety feature is enabled (block S132). If it is determined that at least one other non-life safety feature is not enabled, the determination of block S124 may be repeated. Alternatively, if block S124 is skipped or excluded from the process and it is determined that at least one other non-lifestyle feature is not enabled, the determination of block S128 may be repeated, i.e., the process moves from block S132 to block S128. If processor 56 determines that at least one other non-life safety feature is enabled, processor 56 disables the at least one other life style feature such that the non-life safety feature consumes less power from power source 66 (block S134). The order in which non-life safety features are disabled may vary based on design needs and power consumption of individual features or other criteria.
After disabling at least one other non-lifestyle feature, the determination of block S124 may then be repeated. Alternatively, if block S124 is skipped or excluded from the process and other non-life safety features have been disabled at block S134, the determination of block S128 may be repeated, i.e., the process moves from block S134 to block S128. The power management process helps ensure that more important or security-relevant features remain operational by ending or disabling less important features such as lifestyle features or other non-security features on the user interface device 12. Alternatively, processor 56 may disable more than one or all of the lifestyle features at a time. In one embodiment, power management is configured and power source 66 is sized such that processor 56 may still trigger and sound alarm 64 for four minutes twenty-four hours after a triggering condition (e.g., low battery, sensor trigger detection, receipt of a triggering message from safety control unit 16, etc.) occurs.
The present invention can be realized in hardware, software, or a combination of hardware and software. Any kind of computing system or other apparatus adapted for carrying out the methods described herein is suited to perform the functions described herein. A typical combination of hardware and software could be a specialized or general-purpose computer system having one or more processing elements and a computer program stored on a storage medium that, when loaded and executed, controls the computer system such that it carries out the methods described herein. The present invention can also be embedded in a computer program product, which comprises all the features enabling the implementation of the methods described herein, and which, when loaded in a computing system is able to carry out these methods. Storage medium refers to any volatile or non-volatile memory device.
A computer program or application in the present context means any expression, in any language, code or notation, of a set of instructions intended to cause a system having an information processing capability to perform a particular function either directly or after either or both of the following: a) conversion to another language, code or notation; b) reproduced in different material forms.
It will be appreciated by persons skilled in the art that the present invention is not limited to what has been particularly shown and described hereinabove. Moreover, unless indicated to the contrary, it should be noted that all of the accompanying drawings are not to scale. Various modifications and changes may be made without departing from the scope and spirit of the present invention, which is limited only by the following claims.

Claims (8)

1. A safety control unit (16) comprising:
a wireless communication element (32) supporting a plurality of wireless communication protocols, the wireless communication element (32) configured to provide wireless communication with a user interface device (12) and at least one building device (14);
a remote communication element (34) configured to provide remote communication with a remote monitoring center (20); and
a building power supply (36), the building power supply (36) configured to provide power to the security control unit (16);
a backup power source (38), the backup power source (38) configured to provide power to the safety control unit (16) during the building power failure; and
a processor (44) in communication with the wireless communication element and the remote communication element (34), the processor configured to:
using the wireless communication element (32) to communicate with the user interface device (12) to receive local control and configuration data;
using the remote communication element (34) to communicate data associated with at least one of a life safety feature and a lifestyle feature with the remote monitoring center (20);
executing at least one life safety feature and at least one lifestyle feature;
monitoring the building power supply (36); and
disabling the at least one lifestyle feature being performed and keeping the at least one life safety feature enabled when the monitoring indicates a power failure of the building power source (36).
2. The safety control unit of claim 1, wherein the at least one performed lifestyle feature comprises performing a plurality of lifestyle features; and
the disabling of the at least one lifestyle feature occurs selectively from the plurality of lifestyle features based at least in part on a duration of the power failure.
3. The safety control unit of claim 1, further comprising a memory (46) configured to:
storing a life safety operating system configured to provide functionality associated with the life safety feature;
storing a lifestyle operating system configured to provide functionality associated with the lifestyle feature; and
the processor (44) is further configured to run the life safety operating system and the life style operating system in a virtual machine configuration.
4. The security control unit of claim 1, wherein the plurality of wireless communication protocols comprise at least one of a ZigBee protocol, a Z-Wave protocol, and a Wi-Fi protocol.
5. The security control unit of claim 1, wherein the remote communication is provided by at least one of an ethernet communication link, a Wi-Fi communication link, and a cellular communication link.
6. The security control unit of claim 5, wherein the cellular communication link is used for remote communication when at least one of the ethernet communication link and the Wi-Fi communication link is unavailable.
7. The security control unit of claim 1, wherein the user interface device (12) is at least one of a keypad, a mobile phone, a tablet, a personal computer, and a laptop computer.
8. The safety control unit of claim 1, wherein the building equipment (14) is at least one of a sensor, a video camera, and a thermostat.
HK15101835.0A 2011-07-29 2012-07-27 Security system and method HK1201368B (en)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US201161513003P 2011-07-29 2011-07-29
US61/513,003 2011-07-29
PCT/US2012/048645 WO2013019659A1 (en) 2011-07-29 2012-07-27 Security system and method

Publications (2)

Publication Number Publication Date
HK1201368A1 HK1201368A1 (en) 2015-08-28
HK1201368B true HK1201368B (en) 2018-04-20

Family

ID=

Similar Documents

Publication Publication Date Title
CA2843272C (en) Security system and method
US9691264B2 (en) Security system health monitoring
US9898168B2 (en) Security system access profiles
US9898921B2 (en) Security system installation
EP3343314B1 (en) Handling power failures in a mains powered gateway
EP2974151B1 (en) Security system having segregated operating software
HK1201368B (en) Security system and method