US20120147184A1

US20120147184A1 - Wireless Network Camera Systems

Info

Publication number: US20120147184A1
Application number: US13/397,715
Authority: US
Inventors: Jon Siann; Dennis James Espey
Original assignee: MICROPOWER Tech Inc
Current assignee: MICROPOWER Tech Inc
Priority date: 2006-11-20
Filing date: 2012-02-16
Publication date: 2012-06-14
Also published as: WO2008064270A3; EP2100454A2; US11962941B2; US20160127700A1; US11589009B2; US20170301201A1; EP2100454A4; US10326965B2; US20150130935A1; US20210314529A9; US9640053B2; US8121078B2; US20190246072A1; US9589434B2; US10834362B2; US20110134243A1; US20230199150A1; US20210051302A1; US20100141762A1; WO2008064270A2

Abstract

Apparatus, systems and techniques associated with battery powered wireless camera systems. One aspect of the subject matter described in this specification can be embodied in a system that includes a battery powered wireless camera including an internal battery to provide energy and a burst transmission unit to transmit information during burst periods. The system includes a base station, separated from the battery powered wireless camera, in wireless communication with the battery powered wireless camera to receive information from the battery powered wireless camera. The base station is configured to process the received information and includes a web server to transmit the processed information to a client. Other embodiments of this aspect include corresponding systems, apparatus, and computer program products.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 13/022,644, filed Feb. 8, 2011, which is a continuation of U.S. patent application Ser. No. 12/515,691, filed Feb. 19, 2010, now issued as U.S. Pat. No. 8,050,206 on Nov. 1, 2011, which is a national stage application of and claims the benefit of International Application No. PCT/US2007/085308, filed on Nov. 20, 2007, which claims priority to U.S. Provisional application Ser. No. 60/896,158, filed on Mar. 21, 2007 and U.S. Provisional Application Ser. No. 60/866,587, filed Nov. 20, 2006. The disclosure of the entire prior listed patent applications is considered part of the disclosure of this application and is incorporated by reference.

BACKGROUND OF THE INVENTION

This disclosure generally relates to providing battery powered wireless network camera systems.
Network camera systems can be based on the Internet protocol (IP) and use Ethernet based networking technology. In some applications, network camera systems are replacing analog closed circuit television (CCTV) due to various factors, such as accessibility, ease-of-use, cabling scalability, and lower cost of deployment and operation. With the ubiquity of wireless networks such as WiFi networks (based on IEEE 802.11 standards) and the emerging WiMAX networks (based on IEEE 802.16 standards), wireless network camera systems are gaining popularity and are expected to become the dominant platform for video surveillance applications.
In an IP surveillance environment, the network camera system can include IP cameras connected via twisted pair cabling to a network switch. Alternatively, the network connection can be achieved using wireless local area networking (LAN) technology; e.g., the IEEE 802.11b standard. In various applications, IP cameras can include a web-server capability and remote clients or observers connected to the camera via standard TCP/IP interface standards such as FTP or HTTP. IP based network camera systems can be designed using commercial off-the-shelf (COTS) components from a diverse number of suppliers.

BRIEF SUMMARY OF THE INVENTION

This specification describes various aspects relating to battery powered wireless network camera systems, apparatus and methods of providing such systems. For example, the systems, apparatus and techniques described herein can be implemented in ways that provide wireless IP video systems that require no power cable and can potentially operate on standard off-the-shelf battery solutions for over a year. In addition, the systems, apparatus and techniques described herein can be implemented in ways to resolve the interference, interoperability and reliability problems currently associated with existing wireless camera systems.
One aspect of the subject matter described in this specification can be embodied in a system that includes a battery powered wireless camera including an internal battery to provide energy and a burst transmission unit to transmit information during burst periods. The system also includes a base station, separated from the battery powered wireless camera, in wireless communication with the battery powered wireless camera to receive information from the battery powered wireless camera. The base station is configured to process the received information and includes a web server to transmit the processed information to a client. Other embodiments of this aspect include corresponding methods, apparatus, and computer program products.
Another aspect of the subject matter described in this specification can be embodied in a wireless camera system which includes a battery powered wireless camera including an internal battery to provide energy and a burst transmission unit to transmit information during burst periods. The system also includes a base station, separated from the battery powered wireless camera, in wireless communication with the battery powered wireless camera to receive information from the battery powered wireless camera. The base station is configured to process the received information and including a web server to transmit the processed information to a client, and the base station is powered by a power cable connected to an external power source. The burst periods are determined based on at least one of a wireless link channel average bandwidth capacity, a fidelity of images transmitted, and a latency of establishing and terminating a wireless connection between the battery powered wireless camera and the base station.
A further aspect of the subject matter described in this specification can be embodied in a system that includes a base station which includes a first receiver configured to receive information in a first wireless network and a second transmitter configured to transmit information in a second wireless network. The system also includes a remote node which includes a first transmitter configured to transmit information in the first wireless network and a second receiver configured to receive information in the second wireless network. The second transmitter is further configured to transmit control information from the base station to the remote node via the second wireless network and the first transmitter is further configured to transmit compressed video information from the remote node to the base station via the first wireless network. Additionally, the second receiver in the remote node is further configured to operate for substantially longer period of time than the first transmitter in the remote node. Furthermore, the second receiver in the remote node can be configured to operate continuously for periods of time exceeding 5 hours while drawing less than 10 mW of power.
Yet another aspect of the subject matter described in this specification can be embodied in a method that includes transmitting information, by one or more battery powered wireless cameras having internal batteries in a wireless link. The transmitting of information during burst periods. The method also includes receiving information by a base station, and the base station includes a web server. The method further includes processing the received information in the base station, and transmitting, by the web server, the processed information to a client.
In another aspect, a wireless camera system includes a battery powered wireless camera having an internal battery to provide energy and a burst transmission unit to transmit information during burst periods. The system also includes a base station, separated from the battery powered wireless camera, in wireless communication with the battery powered wireless camera to receive information from the battery powered wireless camera. The base station is configured to process the received information and the burst periods are determined based on at least one of a wireless link channel average bandwidth capacity, a fidelity of images transmitted, and a latency of establishing and terminating a wireless connection between the battery powered wireless camera and the base station.
In a further aspect, a wireless camera system includes a solar powered wireless camera that includes at least one solar cell. The system also includes a base station, separated from the solar powered wireless camera, in wireless communication with the solar powered wireless camera and configured to receive information from the solar powered wireless camera. The base station is further configured to process the received information and includes a web server to transmit the processed information to a client.
In one aspect, a wireless camera system includes a battery powered wireless camera that includes a power unit for energy source and a burst transmission unit to transmit information during burst periods. The system also includes means for determining the burst periods for transmission of information. The system further includes a base station configured to receive information from the battery powered wireless camera and to process the received information. The base station includes a web server to transmit the processed information to a client. The system additionally includes a first wireless link configured to connect the battery powered wireless camera and the base station.
In another aspect, a network camera includes a networking module configured to communicate with a network. The network camera also includes an image capturing module configured to capture images. The network camera further includes an image compression circuit configured to compress the captured images. The network camera additionally includes a privacy lens cap or a visible shutter configured to enhance privacy and prevent the image capturing module from capturing images. The network camera can be a wired or a battery powered wireless camera that includes an internal battery.
In yet another aspect, a network camera includes a burst transmission unit configured to transmit information during burst periods and a networking module configured to communicate with a network. The network camera also includes an image capturing module configured to capture images. The network camera further includes an image compression circuit configured to compress the captured images. The network camera additionally includes a privacy lens cap or a visible shutter configured to enhance privacy and prevent the image capturing module from capturing images. The network camera can be a wired or a battery powered wireless camera that includes an internal battery.
These and other embodiments can optionally include one or more of the following features. For example, a plurality of cameras can be associated with one base station. A plurality of cameras can be associated with two base stations to provide redundancy in case one of the base stations fails. Furthermore, a plurality of cameras can be associated with a plurality of base stations in a mesh architecture to maximize redundancy, resiliency and low power operation. The internal battery can be configured to provide energy without a power cable connected to an external power source that is external to the camera.
The base station configured to receive information from the one or more battery powered wireless cameras can include scanning one or more communication channels for channel availability between the base station and the one or more battery powered wireless cameras; obtaining an available channel for data transmission based on the scanning of channel availability; and associating the available channel with a specific one of the one or more battery powered wireless cameras. The associating of the available channel can include reserving the available channel for a predetermined period of time, and assigning the reserved available channel to the specific one of the one or more battery powered wireless cameras. In addition, during the predetermined period of time, the available channel can appear to the other one or more battery powered wireless cameras as unavailable for wireless communication.
Each of the one or more battery powered wireless cameras can include a scanning circuitry configured to scan the one or more communication channels for channel availability and to determine available channels for data transmission. Each of the one or more battery powered wireless cameras can also include a storage device configured to store data when there are no available channels for data transmission. The wireless network camera system can also include a network connecting the base station and the client, and the client can include a video surveillance application to display video images. The network can be one of a wired Ethernet network, or a wireless network such as a WiFi network or a WiMAX network. The transmitted information can include compressed video signals or digitally encoded video signals.
Each of the one or more battery powered wireless cameras can include an image sensor configured to produce an image; an image compression circuit configured to compress a digital file of the image produced by the image sensor; and a substrate configured to monolithically integrate the image sensor and the image compression circuit. The burst periods can be determined based on at least one of a wireless link channel average bandwidth capacity, the fidelity of images transmitted, and a latency of establishing and terminating the wireless link. The burst periods can be further determined based on a trigger event caused by one of a sound detection, an infrared motion detection, an ultrasonic detection, a radio signaling circuitry, and a channel availability for data transmission.
The wireless network camera system can include a first wireless network configured to communicate between the one or more wireless cameras and the base station via one or more high-bandwidth channels. The wireless network camera system can also include a second wireless network configured to communicate between the one or more wireless cameras and the base station via one or more low-bandwidth channels. The second wireless network can be configured to be more reliable and/or more available (e.g., operates for a longer period of time) than the first wireless network.
Both the first and second wireless networks can be one of a wireless Ethernet network, a WiFi network, and a WiMAX network. In addition, both the first and the second wireless networks can be based on Multiple In Multiple Out (MIMO) technology. The second wireless network can be configured to operate for an extended period of time to facilitate one or more of set-up, installation, and troubleshooting activities. The second wireless network can also be used to signal to the one or more wireless cameras that one of the one or more high-bandwidth channels is available for data transmission. The channel availability information of the one or more high-bandwidth channels can be determined by processing in the base station.
The base station can include a transmitter configured to transmit via the second wireless network information that includes one or more of positional, zoom, and tilt commands to each of the one or more wireless cameras. The base station can also include a transmitter configured to transmit via the second wireless network a command to flush information and data stored on each of the one or more wireless camera through the first wireless network. Each of the one or more battery powered wireless cameras can include a high-bandwidth transceiver and a low-bandwidth transceiver.
The high-bandwidth transceiver can be configured to receive information via the first wireless network and the low-bandwidth transceiver can be configured to receive information via the second wireless network. The low-bandwidth transceiver can be configured to consume less than 4 mW of power in constant operation or operate in a polling mode that reduces an average energy consumption of the camera. The base station can include timing circuits configured to be synchronized with the cycle of the polling mode in the receiver.
Each of the one or more battery powered wireless cameras can include a storage device configured to store the information at a first fidelity. The information can be transmitted to the base station at a second fidelity, and the first fidelity is different from the second fidelity. The one or more wireless cameras can be configured to be powered up to obtain information in response to a trigger event caused by one of a sound detection, an infrared motion detection, an ultrasonic detection, a video processing based movement detection, a relay switch, a micro switch, and a radio signaling circuitry. Each of the one or more wireless cameras can further include a storage device configured to store captured information for a predetermined period of time. The stored captured information can be transmitted to the base station in response to a trigger event.
Each of the one or more wireless cameras can include a first switch configured to control one or more of operation in darkness, operation based on sound detection, operation based on infrared motion detection, operation based on ultrasonic detection, and operation by triggers; and a second switch configured to indicate operation duration of the one or more wireless cameras. A frame rate can be obtained based on the operation duration so that the internal battery can last substantially for the operational duration indicated by the switch.
Each of the one or more battery powered wireless cameras can further include an uncompressed image capture module configured to operate based on periods that are different from the burst periods. The image capture rate and the burst transmission rate can be based on motion detection, and further wherein when motion is detected in the captured images, the image capture frame rate is increased, and when motion is not detected in the captured images, the image capture frame rate is decreased.
The internal battery of the wireless camera can be based on one or more of solar cells, fuel cells, galvanic cells, flow cells, kinetic power generators, and environmental energy sources. The internal battery output voltage can be boosted or regulated by an active power management circuitry. The internal battery can be recharged by one or more of solar cells, fuel cells, galvanic cells, flow cells, kinetic power generators, and environmental energy sources. The internal battery can include an array of rechargeable battery cells configured to extend the useable lifetime of the rechargeable array to be greater than a lifetime of a single rechargeable battery cell, and less than the entire array of rechargeable battery cells are used at a given time.
The useable lifetime of the internal battery can be extended by controlling the current withdrawal of the rechargeable battery cells to within a predetermined current limit. The controlling of current withdrawal from the internal battery can be performed through a high efficiency regulation circuit that includes a switching regulator for drawing a limited current flow from the battery cells, and a capacitor for temporary storage of energy. The internal battery can be replaced by a high capacity capacitor and a charging circuitry associated with the capacitor. The internal battery can include at least a high capacity capacitor and a rechargeable battery.
Each of the one or more battery powered wireless cameras can include a compression module configured to operate based on periods that are different from the burst periods. Each of the one or more battery powered wireless cameras can capture and transmit audio information and sensor information. Each of the one or more battery powered wireless cameras can be surface mountable and can include a housing that has a solar panel configured to recharge the internal battery.
Particular aspects can be implemented to realize one or more of the following potential advantages. An architectural change in the wireless camera can be implemented to obtain significant power savings in wireless network camera systems. Such a design change can offer substantial power savings over commonly understood power-reducing techniques such as using more efficient electronic components in the radio transceivers, image capture, and compression integrated circuits.
An ultra-low power wireless camera can be obtained without compromising the ability of new and existing client system to access data using standard IP connections and standard or de-facto application programming interfaces (APIs). In particular, the base station code can comply with well established IP camera API's. Additionally, even though the wireless camera can operate at an ultra-low average power, during the burst period when the camera is transmitting data to the base station, the camera can allow for power consumption in excess of 100 mW. This is in contrast to existing wireless sensors which will typically consume less than 100 mW of power when transmitting data.
Multiple wireless cameras (e.g., up to 16 wireless cameras) can be assigned to a single base station. The base station and wireless camera combination can deliver all the intelligence and features expected for a commercial grade IP camera solution. The solution integrates into existing IP networks and exposes standard video monitoring application interfaces so that popular video surveillance data applications can be used. This makes for rapid, seamless and pain free deployment. From the network perspective, the combo processing ensures that all wireless cameras appear to be 100% compatible IP cameras. Video can be delivered compressed to industry standard format such as MJPEG or MPEG-4, ready to be accessed and managed by industry standard software.
The base station can connect to a regular wired Ethernet LAN and on to the Internet, just like any IP surveillance system. A seamless integration can occur over a standard 802.11b/g/n wireless Ethernet network. Since it can be wireless to the Internet access point, the distance range of the wireless network camera system can be as wide as today's wireless systems. The user can perform a walk-through wizard once, and begin installing multiple security cameras anywhere within the range of the base station.
Further, a battery powered wireless camera operation can be achieved using well established components. Battery powered wireless network camera systems can be achieved without additional external power source or cabling. These systems can have standard web server capability for client access to the captured data. Because no power cabling is needed, these battery powered wireless network camera systems can be deployed in locations where previously difficult to service. Camera operation for extended periods of time can be obtained using small battery packs.
By using modified media access techniques, unreliable or inconsistent connectivity associated with the standard IEEE 802.11 wireless links can be avoided. Additionally, the erratic set-up and/or operation of a wireless link due to interference or other environmental factors can be minimized. The drawbacks of the IEEE 802.11 MAC standards in poor connection conditions can be overcome by observing interference and also using techniques to reserve and hold a connection for data transmission. For example, by implementing a second low-bandwidth radio/transceiver in the wireless camera, the modified media access techniques can be triggered and controlled through the second radio. The low-bandwidth radio can establish a link in conditions where the high-bandwidth radio/transceiver cannot.
By incorporating more functionality in the base station of the wireless network camera system, the base station can detect and correct link problems by requesting retransmission of the captured data. Such request can be sent via the low-bandwidth radio which can be more reliable and use lower power than the high-bandwidth radio. This retransmission can be hidden and transparent to the client surveillance application through the virtual web server or relay server in the base station. In addition, image and video analytical functions such as object recognition, people counting, and license recognition can be implemented in the base station rather than the camera. These analytical functions can be implemented in a hidden way so that it logically appears to the client that these functions are occurring in the camera. Furthermore, in applications where privacy of the image or audio data needs to be protected, the data transmitted wirelessly can be encrypted.
The specific aspects may be implemented using a system, method, or a computer program, or any combination of systems, methods, and computer programs. The details of one or more embodiments are set forth in the accompanying drawings and the description below. Other features, aspects, and advantages will be ascertained from the description, the drawings, and the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

These and other aspects will now be described in detail with reference to the following drawings.

FIG. 1 is a block diagram of a battery powered wireless camera.

FIG. 2 shows a battery powered wireless network camera system for remote surveillance applications.

FIG. 3 shows another battery powered wireless network camera system for remote surveillance applications.

FIG. 4 is a diagram showing a burst data transmission.

FIG. 5A shows a flow chart of a MAC algorithm that can be used by the wireless camera.

FIG. 5B is a flow chart showing a process that can be used to implement the CTS-to-Self algorithm.

FIG. 6 shows a block diagram of a battery current limiting circuit that can be used to connect to the camera power input.

FIG. 7 is a block diagram of computing devices and systems.

Like reference symbols in the various drawings indicate like elements.

DETAILED DESCRIPTION OF THE INVENTION

The systems, apparatus and techniques described herein relate to providing wireless network camera systems. For example, the wireless network camera systems described herein can operate for an extended period, e.g., months or even years without maintenance in certain applications. By looking at the energy requirements of the system over time, the systems and techniques described herein use a time-sliced energy cycling technology to distribute processing needed over time and location. Furthermore, the systems and techniques described herein are combined with modern, available wireless technologies (such as the modulation schemes deployed in systems like WiFi 802.11) and off-the-shelf advanced semiconductor components. As a result, an overall reduction in the camera power of two or more orders of magnitude can be achieved. For example, the wireless camera described herein can potentially operate on less than 10 mW of power on a sustained basis, and the wireless camera can run over 12 months using 10 AA Lithium batteries.
Connection from the base station to other IP security video cameras and network can be done via wired or wireless links. Each wireless camera connected to the base station can be assigned an IP address from the Ethernet router through the regular DHCP or other standard Ethernet methods. Further, each wireless camera in the network behaves like a regular IP camera to any existing client or application on the LAN. In this way, each wireless camera can be addressable through industry standard APIs so that each video stream and each wireless camera can be viewed, recorded, and manipulated individually without any modifications to existing applications and hardware.
The wireless network camera systems described herein can be used in numerous applications, such as alarm verification and surveillance applications for constructions sites, mobile transportation, and border patrol.
Construction Sites
Construction theft is widespread and nothing new, but the amount of theft is increasing. Construction thefts, which are rarely solved, can lead to construction delay, higher costs and insurance rates, and higher home prices. The National Association of Home Builders estimates that the construction theft problem costs the US building industry $4 billion annually and increases the cost of the average home by 1.5 percent. Some builders try to protect themselves by using bind tools and materials into heavy heaps or block driveways. Most install temporary locks on windows and doors and wait until the last minute to install appliances.
Installing traditional video security cameras can be difficult because power is unlikely to be available at the location best served by the video camera. Most builders are unwilling to invest the dollars for a temporary installation. In addition, cabling for a network camera system can be impractical at the construction site. The wireless network camera systems described herein can offer a solution to this problem. Wireless cameras can be quickly added and moved during the construction phase, and theft activity can be identified in real-time. Since the cameras are temporary, the builder can re-use the cameras at other new construction site, decreasing the initial investment for a total security system to cover all construction projects.
Mobile Transportation
Without proper measures, public transit vehicles, school buses, light rail cars, and trains can be affected by security issues involving passengers and operators. Problems such as vandalism, assault and even suspicious liability claims can affect or disrupt an operation. While there are mobile surveillance systems, they require an on-board DVR which can be cumbersome and difficult to retrofit into an existing transportation vehicle. In addition, the existing system may not provide real-time information to a central monitoring station. The wireless network camera systems described herein can alleviate this problem with a low installation cost, and very little additional equipment to install.
With protected dome cameras at multiple locations on the transportation vehicle, a broad coverage can be enabled, while providing an avenue for central monitoring through a 3G IP based data network. The base station can store images temporarily should an interruption occur through the 3G network preventing immediately transfer of images. With the temporary storage at the base station, a near real-time video security monitoring can still be obtained with a very cost effective system. Video recording can be done at the central location, providing the benefits of immediate access to security officials, elimination of daily video transfer for historical recordkeeping and leveraging lower storage costs at the central facility.
Military and Border Patrol
In a war zone, there is no time and too much risk to install video surveillance systems. In terms of security, there is no greater need than in military applications for quick, reliable and secure mobile video security systems that can be centrally monitored. Lives can be saved in identifying rogue activity and quickly responding to potentially dangerous scenarios before an enemy can act. In most regions of interest, there is no power availability and the lack of a surveillance capability can be detrimental to securing the perimeter. If a security threat cannot be identified and responded to before it is too late, then the effort for enforcing barriers and preventing unauthorized access can be severely hampered. Using the wireless network camera systems described herein, the perimeter can be visually monitored without risk to military personnel.
With the vast expanses that a border patrol monitors, it is impossible to visually monitor all activity using border patrol agents. Using the wireless network camera systems described herein, remote monitoring of border regions can be achieved. A larger number of vital regions of the border can be monitored for unauthorized access using the same number of border agents, providing cost savings while improving efficiency. By integrating internal video analytics software, dynamic frame and bit rate control (e.g., allowing for slower frame and bit rates when nothing is happening, but switching to faster frame and bit rates for improved video quality during critical events), and satellite IP access into the base station, border regions can be covered.
Mining and Underground Applications
Underground mine safety has emerged as a pressing issue worldwide. Various countries and states have begun using communication technologies to improve mine safety. One primary objective is to maintain and ascertain the health and well-being of mining personnel during normal and emergency conditions. New technologies are applied to address voice communications, however, video surveillance and monitoring can provide additional avenues to increase safety. Furthermore, video surveillance can be used to gather information and improve the efficiency and reduce down time for mining production. However, the inherent nature of mining is not conducive to wired camera deployment. The wireless camera system described herein can be implemented to monitor underground and mining by video surveillance.
Difficult Environments
In many environments (e.g., near or under water or hazardous chemical environments), access to wired power supplies can be difficult if not impossible. One example can be the environment in and around swimming pools. In such environment, wireless camera systems described herein can be implemented to monitor pool safety by video surveillance. Additionally, in a chemical plant or processing plants where caustic or hazardous material conditions may not allow power cabling to exist or where the installation of power cabling may be impractical, the wireless camera system described herein can be implemented to monitor plant safety by video surveillance.
Alarm Verification
Due to the number of false alarms created by security systems, many police departments are reluctant to respond to alarms unless there has been “visual verification” that the situation merits a response. The wireless network camera systems described herein can provides an easy to install (no power needed) camera system to allow for remote visual alarm verification
FIG. 1 is a block diagram of a battery powered wireless camera 100 for a wireless network camera system. One energy-saving feature of the battery powered wireless camera 100 is that the web server has been removed from the camera 100 itself By not having the web server functionality in the wireless camera 100, the camera 100 need not constantly be ready to respond to access from remote clients, which access the web server to initiate data transmission. In one implementation, the wireless network camera 100 can be powered for many months using an internal battery 102. The battery 102 can include, e.g., solar cells, galvanic cells, flow cells, fuel cells, kinetic power generators, or other environmental energy sources.
Battery powered wireless network camera operation can be achieved, for example, at full-motion frame rates in excess of 10 frames per second at a resolution of 320×240 pixels. The wireless camera 100 can be connected through a wireless network 150 with a base station 160. The wireless camera 100 includes a high-bandwidth radio frequency (RF) transceiver 104 and a low-bandwidth RF transceiver 106 for communicating with the base station 160 through the wireless link 150. The wireless camera 100 also includes a central processing unit (CPU) 110 for controlling various functionalities associated with the camera.
In certain implementations, the CPU 110 can be replaced by a simplified micro-coded engine or state machine, or a hard-coded state machine. For example, the micro-coded engine or state machine can be similar to that of an RF ID tag with limited response to input. This is because the wireless camera 100 can perform a limited number of predefine functions and those functions can be programmed into the micro-coded engine or hard-coded state machine. In this manner, the power requirement and the cost of the camera can be reduced. In an alternative implementation, various components of the CPU 110 can be combined into a single ASIC, which integrates the entire active and some passive components and memory in order to achieve power savings. Flash memory or other memory components can be the only exceptions to this integration.
The CPU 110 includes a general purpose microcontroller 112 running a light real time operating system. Alternatively, in order to reduce overhead the microcontroller 112 may not use an operation system. The microcontroller 112 can execute programs from an external memory such as a flash memory 114 external to the microcontroller 112 or from memory internal to the microcontroller 112. The CPU 110 also includes an image/video compression engine 116, which can perform proprietary compression algorithms or a standard algorithms such as MPEG2, MPEG4, MJPEG, JPEG, and JPEG2000, and the like. Memory contained in the CPU 110 (e.g., flash memory 114 or other memory devices) can store both compressed and uncompressed video.
In one implementation, the compression algorithm can generate data that relates to the relative visual importance of the compressed data bits. This data can be utilized by the forward error correction (FEC) section of the wireless radio (e.g. the high-bandwidth radio 104). The FEC section of the wireless radio can provide “un-equal protection” (UEP) to the transmission of the compressed data as dictated by its importance. The complementary decoder can be implemented in the base station 160. This transmission scheme can achieve increased efficiency for the transmission of the image data. One example of such transmission scheme is a publication by Yanjun Hu, et al. entitled “An Efficient Joint Dynamic Detection Technique for Wireless Transmission of JPEG2000 Encoded Images.”
The CPU 110 also includes an audio compression engine 118. Memory contained in the CPU 110 can store both compressed and uncompressed video, as well as compressed and uncompressed audio. Under low battery or poor data radio channel bandwidth conditions, a relatively large amount of energy can be saved by disabling the bulk high-bandwidth radio 104 and not transferring the image, audio or other data to the base station 160. In this mode, the flash memory 114 can be used to hold a significant amount of data up to many hours until the data is retrieved.
In conditions where the radio transmissions are interrupted or jammed; for example, by an intruder, an alarm can be initiated silently from the base station 160 to the external network or can be externally indicated by visual or audible transducers activated on the base station 160 or wireless camera 100. In one implementation, alarms can be triggered if data transmissions fail for a specified amount of time. This failure in data transmission can be caused by an intentional jamming by an intruder or by a failure to establish a transmission link. In such situation, the wireless camera 100 can store images and/or audio data in a storage element, such as a flash memory 114, for transmission or retrieval at a later time.
Data retrieval at a later time can be achieved by manually removing the camera 100 or storage element from the camera 100 and connecting to a Windows, Linux or Macintosh based computer via a Universal Serial Bus (USB). The storage unit can appear to the computer to be a standard mass storage device with files of the captured data. In another implementation, when there is a failure in data transmission, the system can use an alternative wireless connection to transfer data, for example, such as operating on a different frequency, using different modulation methods, or by increasing the output power of the wireless transmitter.
The compression engines 116 and 118 can operate on captured data output from the sensors connected to the CPU 110. Alternatively, the compression engines 116 and 118 can operate on captured data temporarily stored inside the flash memory 114. In this manner, the compression and capture processes can operate on independent cycles. This independence can also help maximize energy efficiency. For example, the image capture may be occurring 5 times a second, but the compression engine may operate at very high speed on multiple images every 3 seconds. In this fashion, the energy requirements of starting up the compression engines 116 and 118 can be amortized over a large amount of data. In one example, the flash memory 114 can hold approximately 15 uncompressed images before the compression engine is activated.
In some implementations, most or all components of the compression engines 116 and 118 can be integrated into the microcontroller 112 and peripheral blocks. In this way, the compression can be achieved in the microcontroller 112 using a hybrid software and hardware acceleration for computational intensive processing. Other alternatives for the compression engines 116 and 118 can include a separate application specific integrated circuit (ASIC) or a field programmable gate array (FPGA). An example FPGA can be one based on flash technology such as Actel Corporation's Fusion product line, where the “instant on” allows for rapid start-up capabilities reducing energy wastage during the cycling process. Alternatively, the image capturing module 120 can have an integrated compression engine and output compressed data directly to the CPU 110.
The CPU 110 can also perform the burst transmission store/control MAC process needed to transfer the data transmission from the bulk high-bandwidth radio 104. The high-bandwidth radio 104 can be power cycled based on the physical layer characteristics of the radio and sustained bandwidth needed to maintain certain fidelity of the images and audio transmitted. The power cycling of the high-bandwidth radio 104 is further described in more detail below.
In general operation, the microcontroller 112 can be started from a deep power save mode by the clock 111, which can be, e.g., an ultra low power real time clock. The timing of this can vary depending on the aggregate needs of the multiple processes as they cycle. Therefore, once powered up the software can be used to initiate or manage one or more processes including image capture, data transmission, and image compression. In some instances, the clock 111 can be replaced by a microcontroller with integrated low power real time clock capability. An example of such a microcontroller is the Texas Instruments MSP43O family of products.
In one implementation, most or all of the timing required for the wireless camera 100 can originate from the base station 160 and be communicated to the wireless camera 100 through a secondary receiver (e.g., the low-bandwidth radio 106), as will be described in more detail below. This configuration can act as an alternative to using the clock 111 described above, and allow for more of the processing complexity to reside in the base station 160. Additionally, the wireless camera 100 can be simplified, cheaper, and more robust. Furthermore, the wireless camera 100 can consume less power because very little timing processing would be needed in the wireless camera 100. In this way, the wireless camera 100 can act as a “slave” unit and the commands for the processing elements described below can be issued directly from the base station 160.
In general, all the processing can operate on cycles independent of each other to maintain maximum efficiency. Memory can be used to buffer data between processes to allow for this. This buffering memory can be used to ensure that data overrun or data under-run does not occur during operation. This buffering memory can be designed to operate at an extremely low power during non active or retention modes that can occur between processing cycles. This buffering memory can be distributed between some or all of various integrated circuits that constitute the wireless camera 100. Alternatively, a portion of the buffering can be concentrated in specialized memory components. An example of this kind of memory component can be the Cypress Semiconductor Corporation's 16 Mbit SRAM memory product CY62167EV18.
As shown in FIG. 1, a number of modules can interface to the CPU 110. The image capturing module 120 can include a low power imager such as a CMOS based sensor. Alternatively, a CCD can be used, but typically these devices use more energy than CMOS devices for a given frame rate, resolution and fidelity. The circuitry supporting the sensor can include memory to temporarily hold uncompressed images. In one implementation, image capturing module 120 can also include an image compression engine and memory that stores both compressed and uncompressed images. In some CMOS imagers, so called “active pixel” technology can be used to allow the imager to power up and respond very rapidly to an image exposure command and then automatically power down.
In some implementations, the imager can have a number of active circuits per pixel (such as analog to digital converters) to enable for rapid operation for brief periods of time, followed by very low power standby energy consumption. This also means that the instantaneous power consumption of the imager can be relatively large during the frame capture and transfer process. In an alternative energy saving implementation, the compression circuitry including the required memory can be integrated directly onto the image capturing module 120 or even directly onto the image sensor die. This further integration can reduce the energy needed to transfer data and control information between integrated circuits.
The sound detection module 122 can generate compressed or uncompressed audio data. If uncompressed data is generated from module 122 then the CPU 110 can perform the compression. The sound detection module 122 can also operate at low power, e.g., in the order of tens of micro watts and provide a trigger output based on the noise level. The noise-level triggering event can be detection of a shock wave, detection of breaking or shattering glass detection or other similar acoustic detection techniques. In some implementations, the sound detection module 122 can operate continuously and a positive noise trigger output can be used to activate the wireless camera 100 from a standby mode. Once activated, the wireless camera 100 can initiate the various processing sections to start cycling and, for example, start sending the surveillance data to the base station 160.
In another noise-level triggering mode the sound detection module 122 and the image capturing module 120 can continuously capture and store an on-going window of surveillance data of the immediately previous seconds, minutes or hours. During this time the bulk high-bandwidth radio 104 can be inactive in order to save power. However, once motion is detected some or all of the previously stored information can be transmitted to the base station or retrieved in other ways. This allows the activities that occurred in the area under surveillance prior to a trigger event to be investigated.
In a derivative behavior in this mode, different video compression algorithms operating at different rates can be used before and after the triggering event. For example, JPEG, MJPEG or JPEG2000 type compression algorithms can be used during the pre-trigger period and MPEG2 or MPEG4 type compression algorithms can be used during the post trigger period. This can avoid losing critical captured information on the activities in the surveillance area in a time period leading up to the triggering event.
The infrared detection module 124 can operate at low power, in the order of tens of micro watts, and provide a trigger output that indicates motion has been detected. For example, the infrared detection module 124 can be implemented with a pyroelectric infrared sensor with a Fresnel lens. In some implementations, the infrared detection module 124 can operate continuously and a positive noise trigger output will activate the wireless camera 100 from a standby mode. Once activated, the wireless camera 100 can initiate the various processing sections to start cycling and, for example, start sending the surveillance data to the base station 160.
The ultrasonic detection module 126 can operate at low power, in the order of tens of micro watts, and provide a trigger output that indicates motion has been detected. For example, the ultrasonic detection module 126 can be implemented with a ultrasonic transmitter that sets up a specific sound wave pattern that is received by an ultrasonic receiver. Motion of objects in the field of the sound pattern can affect the received ultrasonic pattern by the receiver. These changes can be detected by the ultrasonic receiver circuitry in the ultrasonic receiver and this event can be used to activate the wireless camera 100 from a standby mode. Once activated, the wireless camera 100 can initiate the various processing sections to start cycling and, for example, start sending the surveillance data to the base station 160.
In another noise-level triggering mode the infrared detection module 124 and/or the ultrasonic detection module 126 and the compression and/or capture processing engine can continuously capture and store an on-going window of surveillance data of the immediately previous seconds, minutes or hours. During this time the bulk high-bandwidth radio 104 can be inactive in order to save power. However, once motion is detected some or all of the previously stored information can be transmitted to the base station or retrieved in other ways. This allows the activities that occurred in the area under surveillance prior to a trigger event to be investigated. In addition, other detection methods can be implemented in a manner similar to that described above for the infrared or ultrasonic detection, but the triggering events can be initiated by other sensors including magnetic sensors, relay or micro switches and window screen wired detectors.
The bulk high-bandwidth radio 104 can be a radio frequency and baseband chipset that implements the physical layer of the 802.11 standard. A key purpose of this radio transceiver is to transfer the bulk of the captured and compressed surveillance data to the base station 160. The MAC and other circuitry may or may not comply with 802.11 standards. The chipset transceiver activities can be power cycled based on methods which will be discussed in further detail below.
Implementations of the techniques described here can be used to achieve efficient use of the high-bandwidth radio 104 in terms of energy per bit per unit of range (distance between transmitter and receiver) transferred. When active the radio can draw or dissipate relatively large amounts of power, however, due to the power cycling techniques, the power consumption of the wireless camera 100 can still be substantially low. In particular, modulation techniques that use broad frequency channels in the order of 5 MHz can be used. This is because these techniques exhibit low energy per bit (of data) per distance of transmission. In one implementation, a multi-carrier modulation technique such as orthogonal frequency division modulation (OFDM) can be used. In another implementation, a spread spectrum modulation scheme such as code division, multiple access (CDMA) can be used.
The low-bandwidth radio 106 can be, e.g., a low-overhead, long-range radio transceiver. The low-bandwidth radio 106 can be a radio frequency and baseband chipset that implements any low power, low-bandwidth technique that will likely have longer reach and higher reliability than the bulk high-bandwidth radio 104. One purpose of the low-bandwidth radio 106 is to transfer status, control and alarm information to and from the base station 160. In receive mode, the power consumption can be extremely low in comparison to the bulk radio 104 and can be low enough to allow the low-bandwidth radio 106 to operate continuously. For example, the power consumption can be in of the order of tens of micro watts.
Using this approach, the low-bandwidth radio 106 has a low power mode where the radio 106 can be activated to respond to a short duration, beacon transmission that originates from the base station 160. The bit stream information contained in the beacon transmission can identify the correct camera and can also have other command/status information. In another implementation, the low-bandwidth radio 106 can be used as a backup when the bulk radio 104 fails or is disable, e.g., due to jamming signals. In this manner, reliability of the wireless camera 100 can be increased because there are a primary high-bandwidth radio 104 and secondary low-bandwidth radio 106 for redundancy. In certain implementations, the high-bandwidth radio 104 and the low-bandwidth radio 106 can be in the same transceiver block.
Additionally, errors in the bit stream of the beacon during transmission can be corrected by using forward error correction (FEC) techniques, such as hamming codes. Details of the forward error correction and its associated timing and phasing techniques will be described below. The bit stream can serve as a “wake-up” function, allowing the base station 160 to activate the correct wireless camera to wake-up and perform certain tasks during times when many components of the wireless camera may be in the shut down mode. In one implementation, this low-bandwidth radio 106 can be achieved using “multi-standard” radio design, which may share portions or components used in the bulk radio 104. The sharing of “multi-standard” components can lead to lower cost or power from an overall system perspective.
As noted above, the wireless camera 100 includes an internal battery 102, which can be a standard non-rechargeable battery or a battery pack. In one implementation, a combination of rechargeable and non-rechargeable batteries can be used. In another implementation, the rechargeable battery can be replaced or augmented by so called super capacitors. Such capacitors are readily available, e.g., from companies like Maxwell Technologies Inc. The sources for the recharging energy can include, e.g., solar cells, fuel cells, galvanic cells, flow cells, kinetic power generators, and environmental energy sources. These energy sources will be describe in more detail below.
The wireless camera 100 can make use of extensive active, high efficiency, power regulation and boaster circuitry to optimize the use of the energy available from various sources. Some or all of electronic processing and memory elements can be integrated into a single ASIC to reduce cost and power, creating a single chip wireless camera. In addition to the components shown in FIG. 1, a Pan, Tilt and Zoom mechanism and control can also be included for user control of the wireless camera 100.
FIG. 2 shows a battery powered wireless network camera system 200 for video surveillance applications. In this example, the wireless network camera system 200 includes a wireless camera 210, a base station 220, a wireless link 240 connecting the wireless camera 210 and the base station 220, and a remote client 250. The system 200 can further include a network 260 connecting the base station 220 and the remote client 250. The network 260 can be a LAN or wide area network (WAN), a wireless network (e.g., WiFi, WiMax, or cellular networks), or power over ethernet network (e.g., based on the IEEE 802.a3f standard). In other implementations, this network connection can be replaced by a universal serial bus (USB) interconnect directly connected to a computing device. From the client 250 or network 260 perspective, the wireless network camera system 200 can support extensive ethernet protocols including IP, HTTP, HTTPS, 802.1x, TCP, ICMP, UDP, SMTP, FTP, DHCP, UPnP™, Bonjour, ARP, DNS, DynDNS, and NTP. In particular, the base station code can comply with well established IP camera API's from companies such as Axis communication's “VAPIX” API or similar API's.
A suitable wireless camera in FIG. 2 can be implemented in various configurations, including the wireless camera 100 described in FIG. 1. The base station 220 can receive information (e.g., video and audio information) from the wireless camera 210 through the wireless link 240 and process the received information. The base station 220 can also be one or more computers performing similar functions as a wireless base station 220 and running a surveillance application. Hence, the computers can function as the base station 220 and the client 250. For example, FIG. 3 shows another battery powered wireless network camera system 300 for remote surveillance applications, where the surveillance client runs on the same system as the base station 220, and the virtual web server in the base station 220 can be eliminated.
Referring back to FIG. 2, the base station 220 includes a virtual web server 222 for relaying or transmitting processed information to a remote client. The web server 222 can act as a virtual/proxy web camera server. Further, the web server 222 can shield the remote client 250 (running a surveillance application) from the burst transmission mechanism (which will be discussed in further detail below) of the wireless camera 210. In addition, the web server 222 can act as a virtual web server or relay server for a number of wireless cameras, aggregating the video streams but appearing to the surveillance remote client 250 as multiple separate virtual IP cameras. The web server 222 can therefore transmit the camera data to the surveillance client 250 using standard network means such as IP, HTTP, HTTPS, TCP, ICMP, UDP, SMTP, FTP, DHCP, UPnP™, Bonjour, ARP, DNS, DynDNS, 802.1X, and NTP.
As described above, by removing the web server for a network camera system out of the wireless camera 250, the wireless camera can achieve ultra-low power consumption. However, unlike the wireless camera 210, the base station 220 requires a relatively robust external power supply to allow for continuous operation of the web server 222. This power supply can have a battery back-up to enable operation for periods of hours to days during main power loss. It may also be possible to power the base station 220 from a large battery which is charged by a relatively large solar cell panel. In another implementation, the base station 220 can obtain some or all of its power through a power over Ethernet (POE) methods, such as the IEEE 802.3af standard. In this case also the unit may have battery back-up capabilities.
Furthermore, the base station 220 can be a self-contained unit with no keyboard or monitor to enable a small form factor. For example, the base station 220 can have a form factor similar to that of a “wall wart,” which is a small power-supply brick with integral male plug, designed to plug directly into a wall outlet. Additionally, the wallwart style base station 220 can use the Power over Ethernet methods for communications with the client device. In this manner, the base station 220 can be easy to install because it can be readily plugged in to a power socket. The base station 220 can also use flash memory or rotation media to store captured data.
As noted above, audio/video data can be requested by the client application system through the network 260 and serviced by a virtual web server 222 in the base station 220. Typically, the remote client 250 consists of computer running a software application that analyzes and/or stores data for security and surveillance purposes. Multiple cameras can be connected to a base station 220 via the wireless link 240. The client computer can in turn run a surveillance application to access the connected cameras. The client application can query the virtual web server 222 in the base station 220 using standard or de-facto APIs such as those available from Axis communications. In particular, the base station code can comply with well established IP camera API's from companies such as Axis communication's “VAPIX” API or similar APIs.
In one implementation, the base station 220 can be connected to the Internet through a cable modem or a DSL modem. In this manner, the IP address of the cable modem or DSL modem can be dynamically assigned. The constant changing of the IP address can make it more complicated to build a virtual web server on the base station 220 and provide accessibility to clients on the Internet. A dynamic domain name server (DDNS) service can be used to allow users anywhere on the Internet to “find” the base station web server 222, even if its IP address is constantly changing. A DDNS function can be provided to enable a fixed name for the web server so that remote users on the Internet can find the IP address of the web server.
In certain implementations, the base station 220 can include software that determines the dynamically changing IP address and forwards a new IP address to the DDNS. This can occur every time a new IP address is assigned by the local Internet Service Provider (ISP). The software can send the necessary updates to all of the DDNS host names that need it. The user or remote client software can use a specifically constructed “domain name” and this would be setup in the DDNS hosting site. Therefore, if the IP address is changed by the local ISP then the DDNS updates the DNS records and sets the TTL (time to live) to a value that will cause a propagation of the updated DNS record throughout the Internet. There are many common providers that provide hosting services, such as dyndns.org. Alternatively, domain names can be purchased or free ones can be obtained, but many of the free ones can have usage restrictions.
Additionally, the remote client 250 can run on a handheld or wireless device, such as a mobile phone, a personal digital assistance (PDA), a smartphone, or the like. In one implementation, the base station 220 can include image optimization processing software or hardware for relaying or transmitting the captured images to the remote client via a wireless application protocol (WAP). For example, the base station 220 can perform image formatting, coding and communication in order to optimize the image quality and behavior to the characteristics of the network link and the constrained nature (bandwidth/size) of the handheld device that is running the client viewing software.
This image optimization processing can enable the base station 220 to only send portions of the image at a time or only send zoomed-in image information (to best fit to the smaller screen and lower network bandwidth of the handheld device), or send images with lower resolution or at lower frame rates. For example, this feature can allow an end user to remotely view the output of the wireless cameras from the convenience of a handheld device, such as a mobile phone. Remote viewing of the wireless camera output from a handheld mobile device can be offered as an additional service to the user from the mobile network carrier company (e.g., AT&T). This can create an attractive revenue generation opportunity for the mobile network carriers.
The base station 220 can also include a low-bandwidth, low-power radio beacon 230 for communication with the wireless camera 210 via a second wireless link. The secondary radio 230 can be low power, however, the timing of this secondary radio 230 needs to be accurate in order to use the bulk, high-bandwidth radio transmission efficiently. The predictability of the secondary radio coming on and transmitting information may need to be in the order of less than one millisecond response time in order to avoid wasting the channel time of the high-bandwidth bulk radio.
The wireless link 240 can include one or more wireless links. For example, a first wireless link can be a high-bandwidth wireless link and a second wireless link can be a low-bandwidth wireless link. In addition, the wireless link 240 can be an RF connection, a low complexity LF, UHF or VHF connection with a baud rate of a few to tens of kilobits, a Bluetooth connection, a cellular network, a wireless Ethernet network, a WiFi network, or a WiMAX network. One example of receiver is the Texas Instrument's semi-passive RFID product TMS37122-TR. Another implementation for this type of radio can be seen in, e.g., “Low-power, super regenerative receiver targets 433-MHz ISM band”, as described in page 78 of the February-2006 issue of Electronic Design News. The network 260 connecting the base station 220 with the remote client 250 can be a wireless network (e.g., a Bluetooth connection, a cellular network, a wireless Ethernet network, a WiFi network, or a WiMAX network) or a wired network (e.g., LAN/WAN network, or POE network).
Several power saving techniques can be used individually or in combination to reduce the overall battery energy consumption in the wireless camera. These techniques are listed and explained in further detail below:
1. Move the camera web server to the base station and re-deploy it as a virtual web server.
2. Cycle the image/sensor bulk, high-bandwidth data transmission radio based on the needs of the data rate and channel capacity.
3. Cycle the image capture module (hardware or software) based on the most efficient use of the module vs. latency, start-up/shut down time and storage capacity needs.
4. Cycle the compression module (hardware or software) based on the most efficient use of the module vs. latency, start-up/shut down time and storage capacity needs.
5. Use of a secondary low-bandwidth radio with a longer range than the bulk radio for camera control and status report and triggering signals.
6. Activation of the camera functions based on various triggering events.
7. Use of environmental energy sources.
8. Use of pulsed high efficiency light emitting diode (LED) devices to illuminate the field of view.
Energy Saving Technique 1: Move the camera web server to the base station and re-deploy it as a virtual web server.
One notable feature of the wireless camera described in this specification is that the wireless camera does not directly service requests for data received via a web server or a relay server mechanism. This is because there is no need for a web server to be running in the wireless camera. Instead, data transmission can be initiated and controlled by the burst transmission store/control block of the wireless camera. A substantial power saving can be achieved through this technique because it eliminates the need for web server functionality to be present in the camera and allows the link radio to power down until sensor and image data has to be transferred, not when the client application needs data. (See power saving technique 2 below for further discussion.). However, through the use of the web server mechanism the camera data can be available to client applications using standard network means such as IP, HTTP, HTTPS, TCP, ICMP, UDP, SMTP, FTP, DHCP, UPnP™, Bonjour, ARP, DNS, DynDNS, 802.1X, and NTP.
Energy Saving Technique 2: Cycle the image/sensor data transmission radio based on the needs of the data rate and channel capacity.
Technique 2 cycles a high-bandwidth radio bursting data on a periodic basis determined by a burst period. Between the burst transmissions the high-bandwidth radio can be powered down. On average, the energy needed to transfer data can be optimized In one implementation, an 802.11 based physical layer technology can be used to transfer the bulk data. The physical layer technology used can include broadband high efficiency OFDM modulation architectures. The OFDM modulation technique can exhibit low energy per bit transferred per unit of range vs. other commonly used radio link architectures, such as the 802.15.4 OOC/FSK modulation techniques.
The wireless camera can include a high-bandwidth radio transceiver, which can operate under a steady state communication condition. For example, the wireless camera media access control (MAC) for the high-bandwidth radio can be programmed to setup/tear down connections as determined by the Transmission Store/Control Block. This allows the high-bandwidth bulk data transmission radio to power down completely for extended periods of time.
When the radio is switched on it can be instantly assumed to be logically linked with the base station. A primitive MAC layer can be used, but this may not be the preferred implementation. Thus, the radio can avoid the usual discovery period, and advance to the authentication request and reply, followed by the associated request and reply messages in a three-way handshaking process. This differs from the regular beacon behavior of 802.11 when operating in a rendezvous mode. Discovery sequences can be suppressed except during initialization/installation conditions. A very light OS can run on the wireless camera to bring up the MAC with the minimal configuration. This can reduce the need for the power and time consuming mechanisms associated with current wireless link technologies. In certain implementations, the MAC layer can almost be entirely eliminated from the camera and a rudimentary slave response can be implemented which responds to control signals received from a secondary, low-power, low-bandwidth radio channel.
The algorithm for the burst transmission processing is a timing loop where data is transmitted based on the data rate used and the available channel characteristics. A calculation is done to determine the optimum timing for the burst transmission and the system is then set up to match this as closely as possible. During non-transmission periods the high-bandwidth radio can be completely powered down. This can be different from “doze” or “standby” modes often provided by commercial integrated circuits. These modes often dissipate energy at levels that can defeat the possibility of extremely long term battery life. During this non transmission time the high-bandwidth radio can use less than tens of micro watts of power.
The timing to transmit for the burst transmission is based on the following parameters: Average Maximum Channel Bandwidth is represented by Bm in M bits per second (Mbps). Channel bandwidth is the average bandwidth that can be achieved by the high-bandwidth link. Average sustained Data Rate is represented by Bs in Mbps, which is the data rate of captured audio/video data. The higher the rate, the better the fidelity and frame rate of the transmitted information.
FIG. 4 is a diagram showing the burst data transmission, according to some implementations. To take advantage of the fact that the sustained data rate Bs is much smaller than the capability of the bulk radio; the transmission will be on for a brief period of time to burst the data. This period can be designated by Tx (sec), and the time period between bursts can be represented by Tc (sec).
Hence
Tx.Bm
Tc=Bs
Referring to the bottom of FIG. 4, there can be a time associated with setting up the link and terminating the link. For example, the time to set up link is represented by Tsu (see), and the time to tear down link is represented by Ttd (sec). Therefore the aggregate time to set-up and tear down link Tw=Tsu+Ttd (sec). To obtain maximum power saving efficiency on the bulk, high-bandwidth radio, ideally the ratio of the transmit time Tx to power down time should be equal to the ratio between Bs and Bm.
During the Tx period, the power drawn by the high-bandwidth radio can be very high relative to the power down periods. For example, the wireless camera in the 802.1 in transmitter which is operating using diversity or multiple transmitters can use between 100 mW to 1.5 W during the Tx period instead of a few hundred microwatts in other periods. This level of power consumption during the transmission of data can be a distinguishing feature of this system compared to existing low power remote sensor systems.
In the image transmission operation, various battery operated camera systems which transmit data intermittently, can have a transmitter-off to transmitter-on ratio of 10 or less. As such, the transmitter in these wireless camera systems is on most of the time. In contrast, of the transmitter in the present systems can be designed to have a high-bandwidth radio for transmission and such a high-bandwidth-ratio transmitter is on only for a short period of time. In this manner, the burst transmission of the current wireless cameras systems can have a transmitter-off to transmitter-on ratio of much greater than 10 and thus provide significant saving in power consumption.
However, the system timing needs to take into account the “wasted” time necessary to setup and tear down the link during which the radio is active, which is Tw. In order to approach the ideal efficiency, period Tw needs to be amortized across a relatively long period of active data transmission time (Tx). This means that the time in-between bursting the radio, as represented by Tc, can be extended as Tw increases to maintain the same efficiency level. Hence the efficiency (E, in percentage) can be determined by
$E = \frac{Tx}{(Tx + Tw)} \cdot 100 %$
Given the above, the average optimum time between transmission of the burst of audio/video (Tc) data for a given efficiency E, can be determined as follows:
$Tc = \frac{Bm}{Bs} \cdot Tw \cdot \frac{E}{E (1 - E)}$
The following example can better illustrate the equation above:
Tw=3 ms (highly optimized system)
Bin=54 M bits/sec (ideal 802.11g data rate)
Bs=192 k bits/sec (5 frames/sec with 0.5 bits/pixel at 320×240, no audio)
E=75%
Then the best cycle time to set-up and burst transmission is, Tc=2.53 seconds.
System latency (or lag) can be greater than or equal to Tc. If latency is too high an unacceptable lag can occur between the capturing of audio/video information to its availability to serve a surveillance application. To reduce latency without negatively impacting energy consumption, significant optimizations need be made to the MAC behavior in order to reduce Tw. In order to reduce time period Tw during steady state conditions (i.e. not during discovery or initialization states) certain modifications can be made. For example, a modification to the regular beacon behavior of 802.11 can be made. When the high-bandwidth radio is switched on for transmission, it can be assumed to be synchronized with the base station. Thus, the usual discovery period can be avoided and the high-bandwidth radio can advance immediately to the authentication request and reply, followed by the associated request and reply messages. Further, when the high-bandwidth radio is switched on, communication can be made for data transfer only.
The above scheme can be implemented to provide a significant improvement because the wireless camera communication can operate on a time frame determined by the need to transmit data of interest, and not on a time frame determined by the client surveillance software application. Also, when multiple cameras are connected to the network using this method, the transmission burst cycle for each camera can be set so as not to interfere which each other. For example, this can be done at initialization time by the burst reception store/control processing module of the base station.
In one implementation, a timestamp can be inserted in the captured images based on the time that the images were captured by the wireless video camera. In this manner, any latency between the time of data capture and the time of viewing or manipulating the images at the client device can be accommodated. For example, suppose that a series of images were captured at 12:00 a.m., however, due to a temporary failure or delay in the transmission the client device does not receive the images until 12:10 a.m. The inserted timestamps in the captured images can be used as the reference point for image processing or manipulation. The insertion of the timestamps can occur at the camera or at the base station.
The base station's high-bandwidth radio MAC firmware can take advantage of “knowing” for long extended periods of time what specific wireless camera radios are associated with it. This can allow set-up and tear down of connections without discovery sequences, by only requiring connection via authentication request and reply followed by the associated request and reply messages. The base station can be implemented in various configurations. In one implementation, a base station implementing standard 802.11 protocols can be used by the system.
Non Clear Channel Environments
In a non-clear channel environment (e.g., during interference from other transmitters which may be using the channel) the high-bandwidth radio transmission period can be “skipped” and the data that was to be transmitted can be temporarily stored and transmitted on the next available cycle. In these conditions, the period and timing of transmission bursts can vary based on channel conditions.
For example, in one implementation, the camera can include a separate low power circuitry to determine if a high-bandwidth radio transmission channel is open or not prior to a transmission cycle. This information can be used to determine if the high-bandwidth radio in the camera is activated from a power down mode or that transmission period is “skipped” by the camera. Using standard 802.11 MAC protocol, if the channel is open the camera can initiate the transmission process by sending a Request to Send (RTS) frame. The base station can then reply with a Clear To Send (CTS) frame. As specified by the standard, any other node receiving the CTS frame should refrain from sending data for a given time.
FIG. 5A shows a flow chart of a MAC algorithm 500 that can be used by the wireless camera. At 505, the wireless camera is initialized, e.g., by going through a discovery mode. At 510, the wireless camera scans for the base station. At 515, the system configures the wireless camera to synchronize with the base station. Once the wireless camera has been initialized and synchronized with a base station, the camera can then enter a power down or standby mode, at 520, when the camera is inactive. On the other hand, based on a triggering event as described above, at 530, the camera can be powered on and enter active mode.
Once the camera is powered on, at 535, the camera transmits an RTS frame to the base station. If a channel is available, the base station can then reply with a CTS frame. At 540, the system determines whether a CTS frame is received from the base station. If the CTS frame is received, at 565, the camera starts to transmit captured or stored image data. On the other hand, if the CTS is not received from the base station, at 560, the camera stores the captured data in the storage device, and periodically transmits an RTS frame to the base station.
In addition, once the RTS frame has been received by the base station, the base station scans for available channels, at 545. At 550, the base station determines whether there are available channels to establish connection with the wireless camera. If there is an available channel, at 555, the base station reserves the channel and then sends a CTS frame to the camera. On the other hand, if there is no available channel, the base station keeps scanning for available channels.
In another implementation, the base station can include processing circuitries or operating modes that can determine if a high-bandwidth radio transmission channel is open or not on a regular basis. This channel availability information can be transferred to the camera using the secondary low-bandwidth radio connection. One benefit of providing this processing on the base station can be a significant power reduction in the camera, since the processing does not occur using the camera's power. Also, the incorporation of the channel availability processing circuitry or operating mode in the base station can allow for complex and power-intensive processing to be executed for system operation.
The base station can then emulate a standard 802.11 CTS/RTS handshaking operation. In this manner, both the primary and the secondary radios of the base station can be used to establish handshaking. Here the base station itself generates the RTS signal which would normally be expected from the camera. This RTS signal can cause surrounding nodes to stay off the channel. This can also eliminate the need for the camera to generate the RTS signal and allow the camera to shut down between time periods of actual data transmission. As noted above, the camera can be activated by the secondary radio operation to transmit more data, or from an internal timer. The whole sequence of emulated CTS/RTS handshakes of data transmission can be pre-determined.
In one further implementation, if a high-bandwidth radio transmission channel is open, the base station can reserve and hold the channel. It can do this by using standard 802.11 MAC channel accessing techniques. During this sequence, the base station can signal the camera using the second wireless link that the bulk channel is open. The base station can then immediately stop transmitting and can “release” the channel. The timing can be configured so that the high-bandwidth radio in the camera can then be activated from a power down and transmission begins such that, from an external observing radio, the channel was never released for any material length of time.
Additionally, the above method of “reserving” and “holding” of the channel for a period of time can be implemented in the base station using the “CTS-to-self” signaling method in the 802.11 standard. This way, an association between the base station and the camera can be established prior to the base station entering the CTS/self mode. FIG. SB is a flow chart showing a process 500B that can be used to implement the CTS-to-Self algorithm. Initially, at 570, the base station scans for available bulk, high-bandwidth radio channels. At 572, the base station determines whether the bulk, high-bandwidth radio channel is available. If the bulk radio channel is available, at 574, the base station sends a CTS/Self signal to reserve the available channel. In this manner, the CTS/Self signaling technique available in the 802.11 standard can be used to keep surrounding 802.11 nodes quiet for a period of time, thereby reserving the available channel. On the other hand, if the bulk radio channel is not available, process 500B iterates at 570 and the base station continues to scan for available channels.
Once the channel has been successful reserved by the base station, at 576, the base station can then send rapidly, with low latency, a proprietary “wake-up/CTS” signal (somewhat similar to the CTS signal) to the camera via the secondary or low-power radio channel. This differs from existing 802.11 MAC procedures where the CTS information is sent once through the primary (or bulk) radio on the camera. At 578, the camera receives the CTS signal from the base station using the secondary (low-power) radio on the camera. The secondary radio on the camera, at 580, then rapidly trigger a “wake-up” signal to the primary bulk transmission radio in the knowledge that the bulk (primary) transmission channel has been reserved and should be clear. At 582, the camera transmits the image data to the base station via bulk transmission channel reserved by the base station. At 584, this image data is received by the base station via the high-bandwidth channel.
One advantage of using the above CTS-to-self signaling technique is that the bulk transmission (primary) channel can be held open according to 802.11 standards for a relatively long period of time. This period can be relatively long to allow for backward compatibility with much older (slower) bandwidth modulation schemes such as 1 Mbit/sec. In the standard, the time reserved by a CTS-to-self can be determined by the duration field in the CTS frame. In this method, the CTS is sent by the base station with usual contention period rules (i.e. after the DIFS quiet air time), and it can be honored by any device close enough to correctly demodulate it.
The above described methods, that of having the base station do the work of reserving the channel and only alerting the camera when the channel is known to be clear and signaling this through the low-power secondary radio, can significantly lower the overall power requirement in the camera. This is because the camera does not have to power up a power hungry bulk transmission receiver radio to determine if the channel is clear. Instead, the camera powers up the high-bandwidth transmitter when the channel is likely to be clear of other WiFi compatible nodes in the network.
In addition, the secondary (low-power and low-bandwidth) radio can implement a hierarchy of up-power modes to provide sustained ultra low power operation. For example, a “carrier sense” mode can be available where only the front-end section of the radio is powered-up to detect if a carrier of a certain narrowband frequency is present. This carrier sense mode can be designed to be extremely low power and can be operational for extended periods of time. In this method of operation, if the front-end section of the secondary radio detects a likely carrier signal, then further demodulation can be triggered to search for a specific leading signature bit sequence. This sequence can be used to determine if the signal is a valid transmission from the base station. If the sequence is valid, then further bits are decoded, if not then the secondary radio can revert back to the low power carrier sense mode.
The method described above, i.e., that of using a low-power secondary radio to receive control, to “wake-up” and to receive other information about the status of a primary high-bandwidth transmission channel is different from various wireless schemes in other wireless camera systems. For example, one of the differences between the present technique and others is using one modulation scheme for the transmission of control information and a different modulation scheme for the transmission of data (e.g., captured image data) information. This can allow the receiver to be low-bandwidth and be design to consume very low power. Another difference from existing wireless schemes can be that the demodulation and/or carrier detection of the secondary radio can be on for extended periods of time in order to listen for the secondary channel and/or demodulate the control/status information.
Furthermore, operational benefits can be achieved by having the secondary radio on at all times when compared to a secondary radio that uses polling (i.e. comes on at intervals to poll for a transmission). For example, this can reduce the need to have timing synchronization with a base station, and can make the system design simpler and more robust. In addition, this can reduce primary channel (high-bandwidth channel) airtime consumption. The is because a polled secondary radio can, on average, add half the polling interval time to the time needed by the camera to transmit the video images on the primary channel. This additional airtime consumption can impact the overall efficiency of the primary channel. This can affect other nodes sharing the channel in a significant way by reducing their overall throughput. With careful design techniques, this constantly on secondary radio can consume power on average in the order of under 1 mW in power during extended operation. This can further allow the secondary radio to be available for many months to years using the energy from a small battery or a fraction of the energy from a larger battery pack.
Legacy Compatibility Advantages
A further benefit of the above approaches to implementing 802.11 MAC compliant protocol processing (but in a novel way using the secondary radio) is that the arrangement is a “good citizen” in a WiFi compatible environment and will behave well with legacy standard 802.11a/b/g nodes. This can allow the deployment to be widespread and by not affecting normal operation of any legacy compatible network. In the above methods the latency to “wake-up” the camera through the secondary radio and set-up the link after this trigger can be designed to be as low as possible and is the same parameter as described above as Tsu. The accuracy of the secondary radio to wake up external circuitry may need to be predictable and should ideally in the order of microseconds to avoid wasting bandwidth on the primary (bulk) channel.
Newer 802.11e Systems with QoS Schemes
In another implementation, the transmission cycles can adhere to standardized system wide quality of service (QoS) schemes, such as that of the IEEE 802.11e standard. The base station can implement a Point Coordination Function (PCF) between these beacon frames. The PCF defines two periods: the Contention Free Period (CFP) and the Contention Period (CP). In CP, the DCF is simply used. In CFP, the base station can send a Contention Free-Poll (CF-Poll) to each camera via the primary (bulk)) or secondary radio, one at a time, to give the camera the permission to send a packet.
In another implementation, the IEEE 802.11e standard using the Hybrid Coordination Function (HCF) can be used. Within the HCF, there are two methods of channel access, similar to those defined in the legacy 802.11 MAC: HCF Controlled Channel Access (HCCA) and Enhanced Distributed Channel Access (EDCA). Both EDCA and HCCA define Traffic Classes (TC). The captured data transmission can be assigned a high priority using this scheme. Using the EDCA method, the base station can assign a specific Transmit Opportunity (TXOP) to a specific camera. A TXOP is a bounded time interval during which a specific camera can send as long as it is within the duration of the pre-assigned TXOP value. Additionally, Wi-Fi Multimedia (WMM) certified nodes need to be enabled for EDCA and TXOP.
Alternatively, the system can also use the HCCA scheme to allow for CFPs being initiated at almost anytime during a CP. This kind of CFP is called a Controlled Access Phase (CAP) in 802.11 e. A CAP is initiated by the base station, whenever it wants to send a frame to a remote node, or receive a frame from a node, in a contention free manner. In fact, the CFP is a CAP too. During a CAP, the base station, which can act as the Hybrid Coordinator (HC), controls the access to the medium. During the CP, all stations function in EDCA. The other difference with the PCF is that Traffic Class (TC) and Traffic Streams (TS) are defined. This means that the base station (implementing the HC function) is not limited to per-camera queuing and can provide a kind of per-session service.
Furthermore, the HC can coordinate these streams or sessions in any fashion it chooses (e.g., not just round-robin). Moreover, the stations give information about the lengths of their queues for each Traffic Class (TC). The HC can use this information to give priority to one station over another, or better adjust its scheduling mechanism based on the captured data burst transmission needs as described above. Another difference is that cameras are given a TXOP: they may send multiple packets in a row, for a given time period selected by the HC. During the CP, the HC allows stations to send data by sending CF-Poll frames. With the HCCA, QoS can be configured with great precision. QoS-enabled cameras can have the ability to request specific transmission parameters and timing as determined by the burst transmission needs described above.
Energy Saving Technique 3: Cycle the image capture module (hardware or software) based on the most efficient use of the module vs. latency, start-up/shut down time, frame rate and storage capacity needs.
For example, in a possible power saving method, after the exposure process, the pixel read out for the image captured from the sensor may occur at the maximum clock output rates allowed by the sensor. This rate may be many times the sustained data rate. This allows the sensor and associated circuitry to power down for significant periods between frame exposures. The image capture engine/processing sections of the camera can also power up and down on a periodic basis independent of other sections of the camera. When operating in the capture mode, uncompressed image can be loaded into an SRAM memory, which temporarily holds the data until it can be processed by the other main sections of the camera. When operating in the power-down mode this section can retain the data in SRAM or some other memory in a low power standby mode.
This cycling can allow the image capturing module to operate independently of other sections. Therefore, each section can cycle on a periodic basis most efficiently to save energy with respect to latency, start-up/shut down time, and storage capacity needs. Further, this cycling technique can offer power savings over that of a simple power down mode where the whole camera except for a “wake-up” section is powered down.
Energy Saving Technique 4: Cycle the compression module (hardware or software) based on the most efficient use of the module vs. latency, start-up/shut down time and storage capacity needs.
The image compression engine/processing sections of the camera can also power up and down on a periodic basis independent of other sections of the camera. When operating in the capture mode, compressed image is loaded into an SRAM memory, which temporarily holds the data until it can be processed by the other main sections of the camera. When operating in the power-down mode this section can retain the data in SRAM or other memory in a low power standby mode.
This cycling can allow the compression module to operate independently of other sections. Therefore each section can cycle on a periodic basis most efficiently to save energy with respect to latency, start-up/shut down time and storage capacity needs. Further, this cycling technique can offer power savings over that of a simple power down mode where the whole camera except for a “wake-up” section is powered down.
The image compression algorithm in the wireless camera does not need to be the same as the compression algorithm used in the base station for sending image information to the client application. For example, a non-standard, proprietary compression algorithm, which can be cheaper and/or consume lower power, can be used on the camera. The compressed data from the camera can be transcoded to a well-know standard (e.g., a JPEG standard) by the base station; and therefore, the proprietary image compression algorithm of the camera can be “transparent” to the client applications. Alternatively, the compressed data can be transmitted directly to the client without transcoding by the base station, if the client can process the compressed data from the camera.
Energy Saving Technique 5: Use of a low-bandwidth transceiver with a longer range than the high-bandwidth data transmission transceiver for camera control and status report.
Low-bandwidth, low power transceivers can be expected to draw only microwatts of power in receive mode. The modulation techniques and frequency band of the low-bandwidth radio can be different from the high-bandwidth data transmission radio. As noted above, the high-bandwidth and the low-bandwidth radios can be integrated together into a single transceiver block having dual radios.
The function of the low-bandwidth radio can be for side band communication without having to power up the high-bandwidth radio. It can allow the camera to be “listening” for instructions during deep sleep mode configurations without needing relatively large power drain. The specifications of the low-bandwidth radio can have longer range but much lower bandwidth than the high-bandwidth radio. Thus, under situations where the high-bandwidth radio cannot establish a link with the base station, the low-bandwidth radio can operate as a back-up radio and effectively communicate with the base station.
The low-bandwidth radio can further reduce its “listening” energy consumption by operating in a polling mode. In the polling mode, the radio section of the low-bandwidth radio can cycle from active to standby. During the active mode, the low-bandwidth radio listens for burst transmission from the base station, captures the data and then goes back to stand-by. In one implementation, this cycle timing information can be accurately known and determined by the base station.
Furthermore, the low-bandwidth radio can be used to receive Pan/Tilt/Zoom (PTZ) information and other commands. These other commands can be triggering operations such as transmission, capture and compression or shut down for long periods of time. The low-bandwidth radio can further be used to send status information to the base stations regarding the health of various components on the wireless camera (e.g., the high-bandwidth radio). Because the low-bandwidth radio can have lower latency than the high-bandwidth radio, the low-bandwidth radio can be used for two way audio communications.
Energy Saving Technique 6: Activation of the camera functions based on various triggering events.
As described above, the camera operation can be triggered by one or more external conditions such as availability of light, motion sensing, passive infrared (PIR) detector, sound or time of day, week or month. In one implementation, the triggering event can occur through the processing of the captured image data.
Energy Saving Technique 7: Use of environmental energy sources. As described in more detail above, various environmental energy sources, such as solar cells, fuel cells, kinetic power generators and other environmental energy sources can be used to power the camera.
Since the average power consumption of the wireless camera can be relatively small, a solar cell or solar cell array can be used as a power source for the camera. This solar cell or solar cell array can be used to recharge a battery or a high capacity capacitor which can power the camera during night time or low light conditions. Further, since the solar cell can be small, it can be attached to a side of the housing of the wireless camera. A suction cap (e.g., a vacuum, push-on sucker) can be mounted on the solar panel side of the housing. This can allow the camera to be quickly mounted on the inside surface of a window pane of a building or a vehicle, such that the solar cell faces the outside to capture light energy, while the imager lenses conveniently faces inside or outside the vehicle or building to capture images.
Additionally, the entire wireless camera can be recharged on a charging station or can have interchangeable battery packs that can fit into a charging station. For example, the interchangeable battery packs can be similar to the batteries used for cordless phones or mobile phones. The interchangeable battery pack can also use non-rechargeable batteries. Furthermore, the wireless camera can be adhered to a surface with a mounting mechanism. This mounting mechanism can be separate from the wireless camera. This mounting will have means that allow the cameras to attached to the mounting quickly and easily while keeping camera's field of view constant. In another embodiment the camera may be mounted on a window pane using suction-cups.
In one implementation where a solar cell is used to charge a rechargeable battery during hours of light, there can be wear-out of the rechargeable battery. Typically re-chargeable cells can have a limited number of charge, recharge cycles. For example, if the rechargeable cell is good for 365 cycles, the cell can only be usable for approximately one year of day/night recycles, thus limiting the camera life to approximately one year. To avoid this problem, an array of cells can be used by the camera. By selecting from a limited set of cells inside the array that will be used for a given number of cycles, the charge/discharge cycle burden can be distributed over the array.
In one implementation, an array of 12 rechargeable battery cells can be used. The 12 cells can be grouped in groups of three battery cells. One group of three cells can be selected for a 12 month operation of charge and recharge cycles. After 12 months, the next group of three cells can be used, and during the third year the next set of three cells can be used and so on. In this way, overall usable lifetime of the rechargeable battery cell array can significantly exceed that of a single cell. Alternatively, the division of the charge/recharge cycle burden can be achieved by a specialized circuitry that alternates charging between cells or cell groups and on a varying timing cycle other than the 12 month cycle as described above.
During the transmission periods of the high-bandwidth radio, the energy consumption can be significant. Drawing a high current from a small battery cell directly connected to the camera power input can cause accelerated wear out of the battery. Therefore, a high efficiency circuit can be used to avoid the wear out of the battery by limiting the maximum current draw from the battery. FIG. 6 shows a block diagram of a battery current limiting circuit that can be used to connect to the camera power input. Other implementation can use alternative energy sources (instead of the battery) such as solar cells, galvanic cells, fuel cells, kinetic power generators, or other environmental sources. The battery current limiting circuit can also help maintain efficient operation in these types of alternative energy sources.
As shown in FIG. 6, a regulator 600 is used to control the maximum amount of current drawn from a battery 602 (or alternative energy source as described above). This regulated current draw is then used to charge a holding capacitor sub-circuit 610. This sub-circuit can be a capacitor, a super capacitor, or other high reliability charge holding device capable of handling current surges better than the battery (or alternative source). The current regulator 600 can include a switched regulator 604 (e.g., a buck regulator) or other active type regulator to maximize efficiency in charging the holding capacitor 610. A current sensor feedback loop can be implemented to monitor the current applied to the holding capacitor 610. For example, one monitoring circuitry can be achieved by amplifying the voltage across a low value sense resistor connected in series with the supply current.
Additionally, a second regulator can be used as a voltage regulator to supply a controlled voltage source to the camera power input. This voltage regulator can be implemented as a switched regulator 612 (e.g., a buck regulator), or other active regulator to maximize efficiency in supplying a voltage source to the camera input. In one implementation, the power regulation circuit can have the ability to adjust the level of current drawn from the energy source under programming control. For example, this can be achieved by adjusting the gain in a sense feedback loop or the set-point in the feedback voltage. This capability can allow for a variety of alternative energy sources (or modes of operation of those sources) to be used.
To make the wireless camera easy to use, the camera can have the certain switches/settings available to the user. For example the camera can include features for operation in darkness (on/off), operation based on sound detection, operation based on infrared detection, and operation based on other triggers. The camera can further include an option for the user to choose the duration of operation (time period the camera needs to operate, e.g., 3 months, 6 months, 1 year or other similar durations). Software can be used to calculate frame rate that need to be used so that the batteries can last for the indicated time.
During set-up mode the camera's wireless link can be powered up continuously (not cycling) for an extended period of time to enable, for example camera focus and field of view set-up to be configured simply and easily. In applications where system latency may cause the period Tc to become unacceptable, the signaling to the low-bandwidth radio can be used to trigger faster cycling and reduce Tc. However, this can reduce energy efficiency. Also, to make the base station easier to install, it can be powered through the Ethernet cable using power over Ethernet by implementing the IEEE802.3af standard or similar methods.
The characteristics of standard 802.11 wireless links can often lead to unreliable or inconsistent connectivity. This is usually due to interference or other environmental factors. This can make set-up and/or operation erratic. These issues can be addressed through the following methods:
a) The media access techniques used by the system need not be the same as the MAC standards of 802.11. Therefore, in poor connection conditions specific and more restrictive channel access techniques can be used by ignoring other radios and forcing and holding a connection. If the secondary low-bandwidth radio is implemented in the camera, these techniques can be triggered and controlled through the secondary radio since it can establish a link in conditions where the high-bandwidth radio cannot. For example, the base station can include circuitry that determines if a channel is available for the primary radio (bulk high-bandwidth radio).
b) Since the base station has information about the transmission behavior and expected state of the camera, it can detect and correct link problems by requesting retransmission of the data. This request can be sent via the secondary low-bandwidth radio which can be more reliable than the high-bandwidth channel. This retransmission can be hidden and transparent to the client surveillance application through the virtual web server in the base station.
c) A highly asymmetrical radio link can be implemented for the high-bandwidth radio where the antennae and processing in the base station uses high gain techniques such as multi antenna (MIMO) and high sensitivity RF front-end processing to help reliably capture the transmission data from the camera.
Energy Saving Technique 8: Use of pulsed high efficiency light emitting diode (LED) devices to illuminate the field of view
In applications where there is little light, or light has been disrupted by a disaster or a failure condition (e.g., an electrical failure), the camera may operate in the dark and the image sensor may not capture useful data. In conventional camera systems, this situation is addressed by attaching an auxiliary light source near or on the camera. Light sources operating continually to illuminate an observation area during video surveillance can consume significant energy. In one implementation, the wireless camera system described in this specification can save energy by pulsing a high efficient infrared or visible light LED, synchronized to the image capture frequency and phase. The operational duration of this scene illumination light pulse from the LED can be minimized by a careful calculation of the sensitivity and exposure time needed by the image sensor to successfully capture images. In addition, scene illumination using the LED devices need be implemented only when necessary to capture an image, and overall energy consumption of the camera can be reduced.
Camera Shutdown and Privacy Enhancements
In applications where users would like to shut down (or deactivate) certain cameras, various enhancements can be used. In one implementation, for example, all or some camera may need to be shut down in situations where recording is not needed or is preferred to be deactivated. This can include situations where an authorized resident is present such as inside the residence or premises. Another example can be a camera installation in a locker room or changing room for use when these facilities are expected to be empty. This can be due to privacy reasons, or simply that the system operator would prefer certain cameras to be off.
In the deactivated (i.e., non-recording) mode, the secondary, low-bandwidth radio can still be on, giving the camera the ability to be reactivated when necessary. Furthermore, this ability to shut down the camera except for the operation of the low power secondary radio, can also allow for longer batter life. Therefore, each camera can be individually deactivated based on control information received via the primary or secondary radio link.
The camera activation or deactivation can also be manually set by an operator, or be linked to an existing alarm system or to a pre-set timing cycle. Deactivation can be overridden under certain circumstances either automatically (such as an alarm trigger), or manually (locally or remotely). Activation periods of the wireless cameras can be manually overridden. In addition, these periods of override can themselves be timed to last a specific period of time, for example minutes or hours. Furthermore, for ease of use and convenience reasons, the setting, initiating and overriding of the modes of activation/deactivation of cameras can be operated from a hand-held remote control.
A visual indication can be made available on the camera using intermittent flashing LED. For example, a red LED can be used to indicate that the camera is in active recording operation. However, some observers or personnel in the camera's field of view may not believe that the camera image recording or viewing capability is truly “off”. In one implementation, to address this concern, the camera can have a mechanically operated, privacy lens cap or an easy-to-observe, visible shutter that obscures the camera lens in an obvious way to make it clear to the observer that the camera cannot be recording or capturing images.
For example, the material of the privacy lens cap can be an opaque material such as a solid sliding window that covers the entire front of the lens surface. To make the fact that the lens is obscured very clear to any observer, the privacy lens cap or visible shutter should be visually clear. For example, if the casing of the camera is white, and since the lens of the camera appears block, the privacy lens cap can be an opaque material such as a solid white sliding window. This way, an observer will not see the darkness of the lens iris or any dark holes on the camera that might indicate an image capturing capability.
A further mechanism to obscure the lens and achieve privacy enhancement can be implemented by causing the lens to retract or roll back into the camera case in such a manner that the lens is no longer pointing into the observation area. For example, in a Pan/Tilt/Zoom (PTZ) type camera this can be implemented by altering the design of the camera to extend the rotational range of the PTZ mechanism beyond the usually implemented range. Therefore, when privacy enhancement is initiated in such an altered PTZ type camera, the visual confirmation to an observer can be somewhat akin to an “eyeball rolling back in its socket”.
This mechanical privacy lens cap, shutter or mechanism can be activated or deactivated automatically or manually, and locally or remotely. For example, in some implementations, the user can manually (e.g., using their hands on the camera) initiate activation (closing or obscuring the lens) and deactivation (opening or making the lens visible) of the privacy lens cap or shutter. Furthermore, this privacy lens cap or shutter system can be used on both wired and wireless cameras for privacy enhancement purposes.
FIG. 7 is a block diagram of computing devices and systems 700, 750. Computing device 700 is intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. Computing device 750 is intended to represent various forms of mobile devices, such as personal digital assistants, cellular telephones, smartphones, and other similar computing devices. The components shown here, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant to limit implementations of the inventions described and/or claimed in this document.
Computing device 700 includes a processor 702, memory 704, a storage device 706, a high-speed interface 708 connecting to memory 704 and high-speed expansion ports 710, and a low speed interface 712 connecting to low speed bus 714 and storage device 706. Each of the components 702, 704, 706, 708, 710, and 712, are interconnected using various busses, and may be mounted on a common motherboard or in other manners as appropriate. The processor 702 can process instructions for execution within the computing device 700, including instructions stored in the memory 704 or on the storage device 706 to display graphical information for a GUI on an external input/output device, such as display 716 coupled to high speed interface 708. In other implementations, multiple processors and/or multiple buses may be used, as appropriate, along with multiple memories and types of memory. Also, multiple computing devices 700 may be connected, with each device providing portions of the necessary operations (e.g., as a server bank, a group of blade servers, or a multi-processor system).
The memory 704 stores information within the computing device 700. In one implementation, the memory 704 is a computer-readable medium. In one implementation, the memory 704 is a volatile memory unit or units. In another implementation, the memory 704 is a non-volatile memory unit or units.
The storage device 706 is capable of providing mass storage for the computing device 700. In one implementation, the storage device 706 is a computer-readable medium. In various different implementations, the storage device 706 may be a floppy disk device, a hard disk device, an optical disk device, or a tape device, a flash memory or other similar solid state memory device, or an array of devices, including devices in a storage area network or other configurations. In one implementation, a computer program product is tangibly embodied in an information carrier. The computer program product contains instructions that, when executed, perform one or more methods, such as those described above. The information carrier is a computer- or machine-readable medium, such as the memory 704, the storage device 706, memory on processor 702, or a propagated signal.
The high speed controller 708 manages bandwidth-intensive operations for the computing device 700, while the low speed controller 712 manages lower bandwidth-intensive operations. Such allocation of duties is exemplary only. In one implementation, the high-speed controller 708 is coupled to memory 704, display 716 (e.g., through a graphics processor or accelerator), and to high-speed expansion ports 710, which may accept various expansion cards (not shown). In the implementation, low-speed controller 712 is coupled to storage device 706 and low-speed expansion port 714. The low-speed expansion port, which may include various communication ports (e.g., USB, Bluetooth, Ethernet, wireless Ethernet) may be coupled to one or more input/output devices, such as a keyboard, a pointing device, a scanner, or a networking device such as a switch or router, e.g., through a network adapter.
The computing device 700 may be implemented in a number of different forms, as shown in the figure. For example, it may be implemented as a standard server 720, or multiple times in a group of such servers. It may also be implemented as part of a rack server system 724. In addition, it may be implemented in a personal computer such as a laptop computer 722. Alternatively, components from computing device 700 may be combined with other components in a mobile device (not shown), such as device 750. Each of such devices may contain one or more of computing device 700, 750, and an entire system may be made up of multiple computing devices 700, 750 communicating with each other.
Computing device 750 includes a processor 752, memory 764, an input/output device such as a display 754, a communication interface 766, and a transceiver 768, among other components. The device 750 may also be provided with a storage device, such as a microdrive or other device, to provide additional storage. Each of the components 750, 752, 764, 754, 766, and 768, are interconnected using various buses, and several of the components may be mounted on a common motherboard or in other manners as appropriate.
The processor 752 can process instructions for execution within the computing device 750, including instructions stored in the memory 764. The processor may also include separate analog and digital processors. The processor may provide, for example, for coordination of the other components of the device 750, such as control of user interfaces, applications run by device 750, and wireless communication by device 750.
Processor 752 may communicate with a user through control interface 758 and display interface 756 coupled to a display 754. The display 754 may be, for example, a TFT LCD display or an OLED display, or other appropriate display technology. The display interface 756 may comprise appropriate circuitry for driving the display 754 to present graphical and other information to a user. The control interface 758 may receive commands from a user and convert them for submission to the processor 752. In addition, an external interface 762 may be provide in communication with processor 752, so as to enable near area communication of device 750 with other devices. External interface 762 may provide, for example, for wired communication (e.g., via a docking procedure) or for wireless communication (e.g., via Bluetooth or other such technologies).
The memory 764 stores information within the computing device 750. In one implementation, the memory 764 is a computer-readable medium. In one implementation, the memory 764 is a volatile memory unit or units. In another implementation, the memory 764 is a non-volatile memory unit or units. Expansion memory 774 may also be provided and connected to device 750 through expansion interface 772, which may include, for example, a SIMM card interface. Such expansion memory 774 may provide extra storage space for device 750, or may also store applications or other information for device 750. Specifically, expansion memory 774 may include instructions to carry out or supplement the processes described above, and may include secure information also. Thus, for example, expansion memory 774 may be provide as a security module for device 750, and may be programmed with instructions that permit secure use of device 750. In addition, secure applications may be provided via the SIMM cards, along with additional information, such as placing identifying information on the SIMM card in a non-hackable manner.
The memory may include for example, flash memory and/or MRAM memory, as discussed below. In one implementation, a computer program product is tangibly embodied in an information carrier. The computer program product contains instructions that, when executed, perform one or more methods, such as those described above. The information carrier is a computer- or machine-readable medium, such as the memory 764, expansion memory 774, memory on processor 752, or a propagated signal.
Device 750 may communicate wirelessly through communication interface 766, which may include digital signal processing circuitry where necessary. Communication interface 766 may provide for communications under various modes or protocols, such as GSM voice calls, SMS, EMS, or MMS messaging, CDMA, TDMA, PDC, WCDMA, CDMA2000, or GPRS, among others. Such communication may occur, for example, through radio-frequency transceiver 768. In addition, short-range communication may occur, such as using a Bluetooth, WiFi, or other such transceiver (not shown). In addition, GPS receiver module 770 may provide additional wireless data to device 750, which may be used as appropriate by applications running on device 750.
Device 750 may also communication audibly using audio codec 760, which may receive spoken information from a user and convert it to usable digital information. Audio codex 760 may likewise generate audible sound for a user, such as through a speaker, e.g., in a handset of device 750. Such sound may include sound from voice telephone calls, may include recorded sound (e.g., voice messages, music files, etc.) and may also include sound generated by applications operating on device 750.
The computing device 750 may be implemented in a number of different forms, as shown in the figure. For example, the device 750 may be implemented as a cellular telephone 780. The device 750 may also be implemented as part of a smartphone 782, personal digital assistant, or other mobile device.
Where appropriate, the systems and the functional operations described in this specification can be implemented in digital electronic circuitry, or in computer software, firmware, or hardware, including the structural means disclosed in this specification and structural equivalents thereof, or in combinations of them. The techniques can be implemented as one or more computer program products, i.e., one or more computer programs tangibly embodied in an information carrier, e.g., in a machine readable storage device or in a propagated signal, 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 (also known as a program, software, software application, or code) 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 alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program does not necessarily correspond to a file. A program can be stored in a portion of a file that holds other programs or data, in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub programs, or portions of code). 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 communication network.
The processes and logic flows described in this specification can be performed by one or more programmable processors executing one or more computer programs to perform the described functions by operating on input data and generating output. The processes and logic flows can also be performed by, and apparatus can be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) 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, the processor will receive instructions and data from a read only memory or a random access memory or both. The essential elements of a computer are a processor for executing instructions and one or more memory 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 mass storage devices for storing data, e.g., magnetic, magneto optical disks, or optical disks. Information carriers suitable for embodying computer program instructions and data include all forms of non volatile memory, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto optical disks; and CD ROM and DVD-ROM disks. The processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.
To provide for interaction with a user, aspects of the described techniques can be implemented on a computer having a display device, e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor, for displaying information to the user and a keyboard and a pointing device, e.g., a mouse or a trackball, by which the user can provide input to the computer. Other kinds of devices can be used to provide for interaction with a user as well; for example, feedback provided to the user can be any form of sensory feedback, e.g., visual feedback, auditory feedback, or tactile feedback; and input from the user can be received in any form, including acoustic, speech, or tactile input.
The techniques can be implemented in a computing system that includes a back-end component, e.g., as a data server, or that includes a middleware component, e.g., an application server, or that includes a front-end component, e.g., a client computer having a graphical user interface or a Web browser through which a user can interact with an implementation, or any combination of such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication, e.g., a communication network. Examples of communication networks include point-to-point connections such as universal serial bus (USB) devices or USB hubs, a local area network (“LAN”), and a wide area network (“WAN”), e.g., the Internet.
The computing system can include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.
While this specification contains many specifics, these should not be construed as limitations on the scope of the invention or of what may be claimed, but rather as descriptions of features specific to particular embodiments of the invention. Certain features that are described in this specification in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination.
Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Moreover, the separation of various system components in the embodiments described above should not be understood as requiring such separation in all embodiments, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products.
A number of embodiments have been described. Nevertheless, it will be understood that various modifications may be made without departing from the spirit and scope of the described embodiments. For example, the triggering events (e.g., motion, sound, infrared detection) described above can be used to further lower the power consumption of the wireless camera. In many situations video surveillance cameras are placed in areas where there is very little motion for many hours. In these cases, significant energy savings can be gained by reducing the rate of any or all of the following functions: image capture, image compression, image transmission, based on a determination that motion has ceased.
In certain implementations, the motion detection can use an external sensor or can be achieved by an algorithm that carries out an analysis of changes between captured images. The algorithm can be implemented in the camera, or in the base station. In some cases, the motion detection processing can be distributed between the camera and the base station. In the case where parts or the entire algorithm is implemented in the base station, information regarding the motion sensing processing can be transferred to the camera by a secondary, low bandwidth radio link. An example of such an algorithm can be found in “Bayesian Illumination-Invariant Motion Detection” by Til Aach and Lutz Dumbgen and Rudolf Mester and Daniel Toth, as described in Vol. III pages 640-643 of Proceedings IEEE International Conference on Image Processing (ICIP).
For example, suppose that a wireless video surveillance camera, as described above, is in a fast image capturing mode. This means that the wireless camera is capturing, compressing, and transmitting images at a high capture rate. A motion detection algorithm can be used to processes the captured image data to determine if there has been motion in the field of view. If at any time the motion detection algorithm determines that there is no motion in the field of view (based on a certain threshold level of probability and criteria), then the camera can enter a slow capture mode and a period of slower capture rate can be initiated.
On the other hand, if the motion detection algorithm determines that motion persists in the field of view, the wireless network camera system continues to capture images at the higher rate. Similarly, during a slow capture mode, the motion detection algorithm can be used to initiate a fast capture mode if motion has been detected.
The amount of energy saving based on the motion detection can be illustrated by analyzing a specific example camera system. Suppose that for a specific camera system, during the fast capture mode the camera operates at 3 frames per second (fps) and consumes 2 mJ per frame. Therefore, the average power dissipation during this fast capture mode is 3 frs×2 mJ per frame=6 mW. Suppose that during the slow capture mode the camera captures one frame every 5 seconds (0.2 Ibs) and consumes 1.5 mJ per frame. Therefore, the average power dissipation during this slow capture mode is 0.2 fps×1.5 mJ per frame=0.3 mW.
Further suppose that motion is detected 20% of the time overall. Then the sustained average power consumption of the camera in operation will be (20%×6+80%×0.3)=1.44 mW. This is clearly lower power then if the camera were operating in the fast capture mode continuously, which can lead to a sustained average power dissipation of 6 mW during camera operation.
Motion, Activity and Object Detection Processing by the Base Station
In some implementations, the motion detection algorithm can be performed in the base station, and significant power saving benefits can be achieved because the camera is not used to carry out potentially power-intensive and complex algorithms. In addition, complex and comprehensive algorithms or video analytics can be performed because the base station can have access to more power and more computational resources. In this manner, detection of additional triggering events beyond simple motion and other categories such as object recognition can be achieved. These more comprehensive and complex algorithms can have the potential benefit of increasing the accuracy and reliability of the triggering event detection and reducing probability of false detections or missing activity, objects or events. Examples of these types of algorithms can be seen in, for example, software products like Xprotect™ from the Milestone Systems A/S Corporation.
User Alerts
In other implementations, the base station can initiate automated cellular phone text messages, phone calls, emails and other textual, visual, or auditory alerts to the user based on a triggering event. The triggering event can be initiated as a result of motion detection through ultrasonic, infrared, acoustic or electrical switch/relay tripping. The triggering event can also be based on the video image processing described above. This message alert capability can avoid the need for the user to constantly monitor the video stream for a triggering event.
Base Station Control or End User Control of Image Capture Rate
In further implementations, the base station can alter the image capture rate in response to information or control data from a client device which is pulling images from the base station. For example, the client may distinguish between “active user observation” mode or “automatic/passive image capture” mode. During the “active user observation mode,” the base station can receive information from a client based on the fact that a user (human observer) is actively monitoring or wishes to monitor the video stream. This information or control data can be communicated to the base station and cause the base station to increase the frame capture rate. During the “automatic/passive image capture mode,” the base station can receive information or control data from the client because a network digital video recording or other process is responsible for requesting images. Additionally, the base station can automatically determine the image capture rate based on activity or triggers detected by the camera or the base station itself This detection of motion, or an object of interest, or a trigger activity can cause the base station to decrease the rate of image capture. Accordingly, other embodiments are within the scope of the following claims.

Claims

1. A wireless camera system comprising:

a wireless camera; and

a base station, separated from the wireless camera, in wireless communication with the wireless camera and configured to receive information from the wireless camera, the base station further configured to process the received information and including a web server to transmit the processed information to a client.

2. The system of claim 1, wherein the received information is video data from the wireless camera.

3. The system of claim 1 comprising a network connecting the base station and the client, the client including a video surveillance application to display video images.

4. The system of claim 1, wherein the transmitted information comprises compressed video signals.

5. The system of claim 1, wherein the wireless camera is configured to be powered up or to obtain information in response to a trigger event caused by one of a sound detection, an infrared motion detection, an ultrasonic detection, a video processing based movement detection, a relay switch, a micro switch, and a radio signaling circuitry.

6. The system of claim 1, wherein the wireless camera is solar powered.

7. The system of claim 1, where the wireless camera is a network camera comprising:

an internal battery;

a networking module configured to communicate with a network;

an image capturing module configured to capture images; and

an image compression circuit configured to compress the captured images.

8. The system of claim 1, wherein the wireless camera includes a privacy lens cap configured to enhance privacy and prevent the image capturing module from capturing images.

9. The system of claim 1, wherein the received information is transmitted to the base station during burst periods.

10. A wireless camera system comprising:

a wireless camera; and

a computer running a software application that analyzes and stores information from the wireless camera for a security or surveillance purpose;

wherein the computer is located away from the wireless camera.

11. The system of claim 10, wherein the computer is located at a remote client site or a base station.

12. The system of claim 10, further comprising:

a burst transmission unit to transmit information during burst periods; and

a base station, separated from the wireless camera, in wireless communication with the wireless camera and configured to receive the information from the wireless camera;

wherein the base station is configured to process the information; and

wherein the burst periods are determined based on at least one of a wireless link channel average bandwidth capacity, a fidelity of images transmitted, and a latency of establishing and terminating a wireless connection between the wireless camera and the base station.

13. The system of claim 10, wherein a first wireless link is configured to connect the wireless camera and a base station.

14. The system of claim 10, wherein a base station is configured to receive the information from the wireless camera to perform operations comprising:

scanning one or more communication channels for channel availability between the base station and the one or more wireless cameras;

obtaining an available channel for data transmission based on the scanning of channel availability; and

associating the available channel with the wireless camera.

15. The system of claim 14, wherein the associating comprises:

reserving the available channel for a predetermined period of time; and

assigning the reserved available channel to the wireless camera.

16. The system of claim 15, wherein during the predetermined period of time, the available channel appears to other wireless cameras as unavailable for wireless communication.

17. The system of claim 12, wherein the wireless camera includes an uncompressed image capture module configured to operate based on periods that are different from the burst periods.

18. The system of claim 12, wherein the wireless camera includes a compression module configured to operate based on periods that are different from the burst periods.

19. The system of claim 10, further comprising an internal battery, wherein an output voltage of the internal battery is boosted or regulated by an active power management circuitry.

20. The system of claim 10, further comprising;

an internal battery coupled to the wireless camera and providing power to the wireless camera; and

a solar panel coupled to the internal battery and configured to recharge the internal battery.