Emergency video camera system

CLAIM OF PRIORITY

This application claims priority under 35 U.S.C. §119(e) to provisional U.S. Patent Application 61/973,962, filed on Apr. 2, 2014, entitled: “Wireless Sensor Network”, and provisional U.S. Patent Application 61/946,054, filed on Feb. 28, 2014, entitled: “Wireless Sensor Network”, the entire contents of which are hereby incorporated by reference.

BACKGROUND

This description relates to operation of security and surveillance systems.

It is common for businesses and homeowners to have a security system for detecting alarm conditions at their premises and signaling the conditions to a monitoring station or to authorized users of the security system. Security systems often include an intrusion detection panel that is electrically or wirelessly connected to a variety of sensors. Those sensors types typically include motion detectors, cameras, and proximity sensors (used to determine whether a door or window has been opened).

SUMMARY

Traditional surveillance video camera systems have been designed for normal modes of operation within a building when power is available. In a typical traditional video surveillance system the components of the video camera system draw power from the building power. This is normally not a problem because building power is generally very reliable and can even be backed up by back-up generators.

During emergency situations, particularly when it involves fire or the chance of explosions, emergency responders generally turn off the building power. Fire Detection systems are designed to provide building power to the emergency evacuation system that provides occupants notification of the emergency, emergency lighting and notification appliances that provide audible instructions for evacuation.

One of the major limitations of traditional video systems that are not on battery back-up is that as soon as the building power is shut off, there is no availability of video images (still or continuous) to “look-in” to help monitor the state of an evacuation, to look for smoke or fire, or to look into areas where people may be trapped.

According to an aspect, a camera system includes a camera including optical components to capture and process optical energy to produce images, camera processing circuitry that receives the optical energy and processes the optical energy into electrical signals and encodes the signals into a defined format and power management circuitry to power the camera system. The power management system includes a first power interface, a second, different power interface, and circuitry to switch from the first power interface to the second power interface upon detection of loss or imminent toss of power from the first interface.

The following are some embodiments within the scope of the aspect.

The system includes a video local storage device. The system includes a local power storage device. The first power interface is a normal power operation interface that is configured to connect to normal building power and the second power interface is an emergency power input interface that is configured to connect to a fire panel. The system includes a first video output interface and a second different video output interface.

According to an additional aspect, a camera system includes a camera comprising optical components to capture and process light to produce video, camera processing circuitry that receives the light and processes the light into electrical signals and encodes the signals into a defined format and power management circuitry to manage power for the camera system. The power management system includes a first video output interface and a second different video output interface.

The following are some embodiments within the scope of the aspect.

The system includes a video local storage device. One of the first and second output interfaces comprises circuitry for providing a wireless network connection. The first video output interface is a normal video output interface and the second video output interface is an emergency video output interface.

According to an aspect, a surveillance system includes one or more camera systems at least some of the camera systems including a camera element including optical components to capture and process light to produce images, camera processing circuitry that receives the light and processes the light into electrical signals and encodes the signals into a defined format and power management circuitry to power the camera system. The power management system includes a first power interface, a second, different power interface; and circuitry to switch from the first power interface to the second power interface upon detection of loss or imminent loss of power from the first interface. The system also includes a first video output interface and a second different video output interface.

The following are some embodiments within the scope of the aspect.

The first interface is a normal power operation interface that is configured to connect to normal building power and the second interface is an emergency power input interface that is configured to connect to a fire panel. The first output interface is an emergency output interface and the second output interface is a normal output interface. The first interface is a local power storage element that supplies power to the camera only during emergencies. The local power storage element is fed by a power harvesting element that supplies power to the local storage element. The local power storage element is fed by building power. The system includes sensor nodes and a wireless sensor network to couple the one or more video cameras to monitors and the sensor nodes to monitoring units.

Described is a video surveillance system including an emergency video camera and system that allows access to video information for operation during a power and communication outage by use of a backup power network provided by a fire notification system.

The details of one or more embodiments of the invention are set forth in the accompanying drawings and the description below. Other features, objects, and advantages of the invention is apparent from the description and drawings, and from the claims.

DESCRIPTION OF DRAWINGS

<figref idref="DRAWINGS">FIG. 1</figref> is a block diagram of an emergency camera element.

<figref idref="DRAWINGS">FIGS. 2-5</figref> are block diagrams of a camera system incorporating the emergency camera element of <figref idref="DRAWINGS">FIG. 1</figref>.

<figref idref="DRAWINGS">FIG. 6</figref> is a block diagram of components of an example networked security system.

DETAILED DESCRIPTION

Described herein are examples of emergency cameras having features that may be used in various contexts including, but not limited to, security/intrusion and alarm systems. Example security systems may include an intrusion detection panel that is electrically or wirelessly connected to a variety of sensors. Those sensors types may include motion detectors, cameras, and proximity sensors (used, e.g., to determine whether a door or window has been opened). Typically, such systems receive a relatively simple signal (electrically open or closed) from one or more of these sensors to indicate that a particular condition being monitored has changed or become unsecure.

For example, typical intrusion systems can be set-up to monitor entry doors in a building. When a door is secured, a proximity sensor senses a magnetic contact and produces an electrically closed circuit. When the door is opened, the proximity sensor opens the circuit, and sends a signal to the panel indicating that an alarm condition has occurred (e.g., an opened entry door).

Data collection systems are becoming more common in some applications, such as home safety monitoring. Data collection systems employ wireless sensor networks and wireless devices, and may include remote server-based monitoring and report generation. As described in more detail below, wireless sensor networks generally use a combination of wired and wireless links between computing devices, with wireless links usually used for the lowest level connections (e.g., end-node device to hub/gateway). In an example network, the edge wirelessly-connected) tier of the network is comprised of resource-constrained devices with specific functions. These devices may have a small-to-moderate amount of processing power and memory, and may be battery powered, thus requiring that they conserve energy by spending much of their time in sleep mode. A typical model is one where the edge devices generally forma single wireless network in which each end-node communicates directly with its parent node in a hub-and-spoke-style architecture. The parent node may be, e.g., an access point on a gateway or a sub-coordinator which is, in turn, connected to the access point or another sub-coordinator.

Referring now to <figref idref="DRAWINGS">FIG. 1</figref>, an emergency video camera <b>10</b> includes a lens <b>12</b>, a camera body or case <b>13</b>, optics <b>14</b>, video encoder <b>16</b>, power management circuitry <b>18</b>, camera block circuitry for imaging and picture quality control, <b>20</b> and a video local storage device <b>22</b>. The video camera <b>10</b> also includes local power storage <b>24</b>, e.g., battery backup power. The emergency video camera element operates in a conventional manner with respect to the video encoder, optics, and a camera block circuitry for imaging and picture quality. The emergency video camera element can also include a normal mode power input interface <b>26</b> and a normal mode video output interface <b>28</b>. The emergency video camera element also includes an emergency power input interface <b>30</b> and an emergency video output interface <b>32</b>.

The emergency video output interface <b>32</b> is used to convey video data to a central system and can be either wired or wireless (or both). The emergency power input interface is coupled to a source of emergency power and supplies power to the emergency video camera <b>10</b> at least during emergency situations, when for example normal building supplied power is shut-off. The emergency video camera <b>10</b> includes depending on a specific configuration the normal input power input interface <b>26</b>, i.e., powered by building power and used during normal operation, and a normal video output interface <b>28</b> used during normal operation. The emergency video camera <b>10</b> includes a local power storage device to provide a source of power during situations where the building power is unavailable.

Within the emergency video camera <b>10</b> either the power management circuitry <b>18</b> or other circuitry <b>19</b> detects the absence of normal building power (either from the interface <b>26</b> or from a signal that is transmitted from a server, indicating that normal building power was lost. The power management circuitry <b>18</b> or other circuitry causes the emergency video camera <b>10</b> to automatically switch to obtain power from the emergency power input <b>30</b> and provide video to emergency video output <b>32</b>. Alternatively, the emergency video camera <b>10</b> senses via a message from the sensor network the loss or imminent loss of power and switches tp emergency power and emergency video output as discussed above.

Referring now to <figref idref="DRAWINGS">FIG. 2</figref>, in one implementation <b>40</b>, the emergency video camera <b>10</b> contains certain ones of the elements discussed in <figref idref="DRAWINGS">FIG. 1</figref> that allow the emergency video camera <b>10</b> to be connected to a traditional surveillance system for a normal mode of operation using the building communication network and the building power source <b>41</b>. In this configuration, the emergency video camera element is connected to the Internet, for example, via a site video storage and transport recorder (DVR) <b>42</b>, a local building network <b>44</b>, and a firewall and/or router and/or modem <b>46</b> out to the Internet or another wide area network (not shown). Within this implementation <b>40</b> of the emergency video camera <b>10</b>, either the power management circuitry <b>18</b> or other circuitry detects the absence of normal building power and switches to emergency power and emergency video output or senses via a message from the sensor network the loss or imminent loss of power and switches to emergency power and emergency video output.

The emergency video camera <b>10</b> also has an alternate power source to power the camera <b>10</b> during a power outage as well as a separate, alternate video transport, transcoding <b>52</b> and communications channel <b>54</b>. The emergency power input interface <b>30</b> is coupled to a fire panel network <b>56</b> that is fed by a battery backup <b>58</b>, and the emergency video output interface <b>32</b> is coupled to a separate video transport and transcode over a separate network (not shown) that is separate from the local building network <b>44</b>, i.e., an emergency communications network <b>54</b> to the Internet (not shown). The emergency communication network <b>54</b> may comprise a number of traditional technologies including wired or wireless communication paths, but physically the emergency communications network <b>54</b> is different from the building network <b>44</b>. The fire panel network <b>56</b> also provides power for the video transport and transcode <b>52</b>, as well as, power for the emergency communication network <b>54</b> for communication of video to external monitor devices, e.g., display devices (not shown). Thus, the emergency video camera <b>10</b> is configurable for a normal mode of operation using the building network <b>44</b> and power <b>41</b> but has an alternate configuration that provides the emergency video camera <b>10</b> power from the building fire panel <b>56</b> and an alternate video transport, transcoding <b>52</b> and communications channel <b>54</b>.

Referring now to <figref idref="DRAWINGS">FIG. 3</figref>, a second implementation <b>60</b> has the emergency video camera <b>10</b> connected to operate only during emergency conditions. In this implementation <b>60</b>, the camera <b>10</b> is powered by the fire panel network <b>56</b> that also provides power for the video transport and transcode <b>52</b> as well as power for the emergency communication network <b>54</b> for communication of video to the external monitors, via the Internet (or other network, e.g., a wide area network). The emergency communication network <b>54</b> may be a number of traditional technologies including wired or wireless communication paths. Within this implementation <b>60</b>, the emergency video camera <b>10</b> will either continuously operate from power from the fire panel or be awaken in absence normal building power and will use emergency power from the fire panel fed to the power interface <b>30</b> and emergency video output <b>32</b> provide video to the video transport and transcoder <b>52</b>.

Referring now to <figref idref="DRAWINGS">FIG. 4</figref>, a third implementation <b>70</b> has the emergency video camera <b>10</b> powered by the building power grid and with the internal, local power storage <b>24</b> (e.g., a rechargeable high capacity storage battery or, a supercapacitor, i.e., an electrical double-layer capacitor or pseudocapacitor used for energy storage) to operate for a period of time during a building power outage. This implementation also has a wireless connection <b>61</b> to a wireless gateway <b>63</b> powered by the fire panel <b>56</b> and with battery backup <b>58</b>. The gateway <b>63</b> feeds video transport and transcoder <b>52</b> and network <b>54</b> to provide video for the external monitors via the Internet.

Referring now to <figref idref="DRAWINGS">FIG. 5</figref>, a fourth implementation <b>70</b> has the emergency video camera <b>10</b> powered by a local energy harvesting element <b>73</b> such as a photovoltaic cell that collects energy and stores the energy in local energy storage <b>24</b>, e.g., a rechargeable high capacity storage battery or by a supercapacitor, i.e., an electrical double-layer capacitor or pseudocapacitor used for energy storage. During an emergency, the emergency video camera <b>10</b> is activated, and powered by the energy storage element <b>24</b>. In this implementation <b>70</b>, the emergency video camera <b>10</b> powered by the local energy harvesting technique that will power the camera <b>10</b> during a power outage. Exemplary local energy harvesting techniques include a photovoltaic cell that collects energy and stores energy during normal operation in a rechargeable battery or a supercapacitor <b>24</b>. This implementation also has a wireless connection <b>61</b> to a wireless gateway <b>63</b> powered by the fire panel <b>56</b> and with battery backup <b>58</b>. The gateway <b>63</b> feeds video transport and transcoder <b>52</b> and network <b>54</b> to provide video for monitors via the Internet.

The emergency camera system <b>10</b> is implemented using any appropriate type of camera optical system and computing device or any other type of intelligent device capable of executing instructions, connecting to a network, and forwarding data packets through the network. Each of processes discussed above may be stored on one or more non-transitory machine-readable media, such as computer memory persistent or non-persistent to store executable instructions. Each of these devices may also include one or more processing devices (e.g., microprocessors, programmable logic, application-specific integrated circuits, and so forth) for executing the instructions to perform all or part of the functions described herein.

<figref idref="DRAWINGS">FIG. 6</figref> shows an example of a security system on a Wireless Sensor Network (WSN). In the WSN, the distributed network <b>10</b> is logically divided into a set of tiers or hierarchical levels <b>12</b><i>a</i>-<b>12</b><i>c</i>. In an upper tier or hierarchical level <b>12</b><i>a </i>of the network are disposed servers and/or virtual servers <b>14</b> running a “cloud computing” paradigm that are networked together using well-established networking technology such as Internet protocols or which can be private networks that use none or part of the Internet. Applications that run on those servers <b>14</b> communicate using various protocols such as for Web Internet networks XML/SOAP, RESTful web service, and other application layer technologies such as HTTP and ATOM. The distributed network <b>10</b> has direct links between devices (nodes) as shown and discussed below.

The distributed network <b>10</b> includes a second logically divided tier or hierarchical level <b>12</b><i>b</i>, referred to here as a middle tier that involves gateways <b>16</b> located at central, convenient places inside individual buildings and structures. These gateways <b>16</b> communicate with servers <b>14</b> in the upper tier whether the servers are stand-alone dedicated servers and/or cloud based servers running cloud applications using web programming techniques. The middle tier gateways <b>16</b> are also shown with both local area network <b>17</b><i>a </i>(e.g., Ethernet or 802.11) and cellular network interfaces <b>17</b><i>b. </i>

The distributed network topology also includes a lower tier (edge layer) <b>12</b><i>c </i>set of devices that involve fully-functional sensor nodes <b>18</b> (e.g., sensor nodes that include wireless devices, e.g., transceivers or at least transmitters, which in <figref idref="DRAWINGS">FIG. 6</figref> are marked in with an “F”) as well as constrained wireless sensor nodes or sensor end-nodes <b>20</b> (marked in the <figref idref="DRAWINGS">FIG. 6</figref> with “C”). In some embodiments wired sensors (not shown) can be included in aspects of the distributed network <b>10</b>.

Constrained computing devices <b>20</b> as used herein are devices with substantially less persistent and volatile memory other computing devices, sensors in a detection system. Currently examples of constrained devices would be those with less than about a megabyte of flash/persistent memory, and less than 10-20 kbytes of RAM/volatile memory). These constrained devices <b>20</b> are configured in this manner; generally due to cost/physical configuration considerations. These types of constrained devices <b>20</b> generally have a static software image (i.e., the logic programmed into the constrained device is always the same).

In a typical network, the edge (wirelessly-connected) tier of the network is comprised of highly resource-constrained devices with specific functions. These devices have a small-to-moderate amount of processing power and memory, and often are battery powered, thus requiring that they conserve energy by spending much of their time in sleep mode. A typical model is one where the edge devices generally form a single wireless network in which each end-node communicates directly with its parent node in a hub-and-spoke-style architecture. The parent node may be, e.g., an access point on a gateway or a sub-coordinator which is, in turn, connected to the access point or another sub-coordinator.

Each gateway is equipped with an access point (fully functional node or “F” node) that is physically attached to that access point and that provides a wireless connection point to other nodes in the wireless network. The links (illustrated by lines not numbered) shown in <figref idref="DRAWINGS">FIG. 6</figref> represent direct (single-hop network layer) connections between devices. A formal networking layer (that functions in each of the three tiers shown in <figref idref="DRAWINGS">FIG. 6</figref>) uses a series of these direct links together with routing devices to send messages (fragmented or non-fragmented) from one device to another over the network.

The WSN <b>10</b> implements a state machine approach to an application layer that runs on the lower tier devices <b>18</b> and <b>20</b>. Discussed below is an example of a particular implementation of such an approach. States in the state machine are comprised of sets of functions that execute in coordination, and these functions can be individually deleted or substituted or added to in order to alter the states in the state machine of a particular tower tier device.

The WSN state function based application layer uses an edge device operating system (not shown, but such as disclosed in the above mentioned provisional application) that allows for loading and execution of individual functions (after the booting of the device) without rebooting the device (so-called “dynamic programming”). In other implementations, edge devices could use other operating systems provided such systems allow for loading and execution of individual functions (after the booting of the device) preferable without rebooting of the edge devices.

As shown in <figref idref="DRAWINGS">FIG. 6</figref>, correlation processing receives inputs from certain constrained nodes (although these can also be fully functional nodes). These inputs may include credential information and video information, and the correlation processing may produce correlated results that are sent over the network. Context management processing receives inputs from certain constrained nodes (although these can also be fully functional nodes) e.g., credential information and video and grouping information, and performs context processing with results sent over the network. The network supports operation of emergency exit indicators; emergency cameras as well as distributed rule processing and rule engine/messaging processing. Range extenders are used with e.g., gateways, and a real time location system receives inputs from various sensors (e.g., constrained type) as shown. Servers interface to the WSN via a cloud computing configuration and parts of some networks can be nm as sub-nets.

The sensors provide in addition to an indication that something is detected in an area within the range of the sensors, detailed additional information that can be used to evaluate what that indication may be without the intrusion detection panel being required to perform extensive analysis of inputs to the particular sensor.

For example, a motion detector could be configured to analyze the heat signature of a warm body moving in a room to determine if the body is that of a human or a pet. Results of that analysis would be a message or data that conveys information about the body detected. Various sensors thus are used to sense sound, motion, vibration, pressure, heat, images, and so forth, in an appropriate combination to detect a true or verified alarm condition at the intrusion detection panel.

Recognition software can be used to discriminate between objects that are a human and objects that are an animal; further facial recognition software can be built into video cameras and used to verify that the perimeter intrusion was the result of a recognized, authorized individual. Such video cameras would comprise a processor and memory and the recognition software to process inputs (captured images) by the camera and produce the metadata to convey information regarding recognition or lack of recognition of an individual captured by the video camera. The processing could also alternatively or in addition include information regarding characteristic of the individual in the area captured/monitored by the video camera. Thus, depending on the circumstances, the information would be either metadata received from enhanced motion detectors and video cameras that performed enhanced analysis on inputs to the sensor that gives characteristics of the perimeter intrusion or a metadata resulting from very complex processing that seeks to establish recognition of the object.

Sensor devices can integrate multiple sensors to generate more complex outputs so that the intrusion detection panel can utilize its processing capabilities to execute algorithms that analyze the environment by building virtual images or signatures of the environment to make an intelligent decision about the validity of a breach.

Memory stores program instructions and data used by the processor of the intrusion detection panel. The memory may be a suitable combination of random access memory, and read-only memory, and may host suitable program instructions (e.g. firmware or operating software), and configuration and operating data and may be organized as a file system or otherwise. The stored program instruction may include one or more authentication processes for authenticating one or more users. The program instructions stored in the memory of the panel may further store software components allowing network communications and establishment of connections to the data network. The software components may, for example, include an internet protocol (IP) stack, as well as driver components for the various interfaces, including the interfaces and the keypad. Other software components suitable for establishing a connection and communicating across network will be apparent to those of ordinary skill.

Program instructions stored in the memory, along with configuration data may control overall operation of the panel.

The monitoring server includes one or more processing devices (e.g., microprocessors), a network interface and a memory (all not illustrated). The monitoring server may physically take the form of a rack mounted card and may be in communication with one or more operator terminals (not shown) that include display devices (not shown). An example monitoring server is a SURGARD™ SG-System III Virtual, or similar system.

The processor of each monitoring server acts as a controller for each monitoring server, and is in communication with, and controls overall operation, of each server. The processor may include, or be in communication with, the memory that stores processor executable instructions controlling the overall operation of the monitoring server. Suitable software enable each monitoring server to receive alarms and cause appropriate actions to occur. Software may include a suitable Internet protocol (IP) stack and applications/clients.

Each monitoring server of the central monitoring station may be associated with an IP address and port(s) by which it communicates with the control panels and/or the user devices to handle alarm events, etc. The monitoring server address may be static, and thus always identify a particular one of monitoring server to the intrusion detection panels. Alternatively, dynamic addresses could be used, and associated with static domain names, resolved through a domain name service.

The network interface card interfaces with the network to receive incoming signals, and may for example take the form of an Ethernet network interface card (NIC). The servers may be computers, thin-clients, or the like, to which received data representative of an alarm event is passed for handling by human operators. The monitoring station may further include, or have access to, a subscriber database that includes a database under control of a database engine. The database may contain entries corresponding to the various subscriber devices/processes to panels like the panel that are serviced by the monitoring station.

All or part of the processes described herein and their various modifications (hereinafter referred to as “the processes”) can be implemented, at least in part, via a computer program product, i.e., a computer program tangibly embodied in one or more tangible, physical hardware storage devices that are computer and/or machine-readable storage devices for execution by, or to control the operation of, data processing apparatus, e.g., a programmable processor, a computer, or multiple computers. A computer program can be written in any form of programming language, including compiled or interpreted languages, and it can be deployed in any form, including as a stand-atone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program can be deployed to be executed on one computer or on multiple computers at one site or distributed across multiple sites and interconnected by a network.

Actions associated with implementing the processes can be performed by one or more programmable processors executing one or more computer programs to perform the functions of the calibration process. All or part of the processes can be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) and/or an ASIC (application-specific integrated circuit).

Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer. Generally, a processor will receive instructions and data from a read-only storage area or a random access storage area or both. Elements of a computer (including a server) include one or more processors for executing instructions and one or more storage area devices for storing instructions and data. Generally, a computer will also include, or be operatively coupled to receive data from, or transfer data to, or both, one or more machine-readable storage media, such as mass storage devices for storing data, e.g., magnetic, magneto-optical disks, or optical disks.

Tangible, physical hardware storage devices that are suitable for embodying computer program instructions and data include all forms of non-volatile storage, including by way of example, semiconductor storage area devices, e.g., EPROM, EEPROM, and flash storage area devices; magnetic disks, e.g., internal hard disks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks and volatile computer memory, e.g., RAM such as static and dynamic RAM, as well as erasable memory, e.g., flash memory.

In addition, the logic flows depicted in the figures do not require the particular order shown, or sequential order, to achieve desirable results. In addition, other actions may be provided, or actions may be eliminated, from the described flows, and other components may be added to, or removed from, the described systems. Likewise, actions depicted in the figures may be performed by different entities or consolidated.

Elements of different embodiments described herein may be combined to form other embodiments not specifically set forth above. Elements may be left out of the processes, computer programs, Web pages, etc. described herein without adversely affecting their operation. Furthermore, various separate elements may be combined into one or more individual elements to perform the functions described herein.

Other implementations not specifically described herein are also within the scope of the following claims.