POWER OUTLET CAMERAS

BACKGROUND
Field

Various embodiments disclosed herein relate to devices and methods that enable people to observe remote locations. Certain embodiments relate to cameras that send images to remote computing devices.

Description of Related Art

Video cameras can record images of various events that are viewable by remotely located people. Video cameras can be supported by objects such as tripods. Video cameras often require electrical power. Some video cameras receive electrical power from batteries and/or power outlets.

Installing videos cameras inside of buildings can be expensive and time consuming. Thus, there is a need for easily installed video cameras that send images to remotely located people.

SUMMARY

Security systems can be used to take videos of visitors and to send the videos to remote computing devices. Security systems can be attached to a power outlet by inserting prongs that protrude from a backside of the security system into electrical ports of the power outlet.

Security systems can include, among other things, an outwardly facing portion, an inwardly facing portion, and a detection system. The security system can be configured to mount to a power outlet. The outwardly facing portion may be configured to face away from the power outlet. The inwardly facing portion may have a first electrical prong and a second electrical prong that protrude into the power outlet to mount the security system to the power outlet. The detection system may be coupled to the outwardly facing portion. The detection system can include a camera and a motion detector.

In several embodiments, the security system may be communicatively coupled to a remote computing device. The security system may be arranged and configured to send an alert to the remote computing device in response to the motion detector detecting a first motion. The security system may be arranged and configured to send the alert to the remote computing device in response to the motion detector detecting the first motion during a first predetermined time of day. The security system can be arranged and configured to not send the alert to the remote computing device in response to the motion detector detecting a second motion during a second predetermined time of day. The security system may be arranged and configured to exit a sleep mode and enter a live view mode in response to the motion detector detecting the first motion. When the camera is in the sleep mode, the camera may not capture images. When the camera is in the live view mode the camera may capture images. The camera may be arranged and configured to exit a sleep mode and enter a live view mode in response to receiving a wireless request from the remote computing device. When the camera is in the sleep mode the camera may not capture images. When the camera is in the live view mode the camera may capture images.

In some embodiments, the camera may be configured to record images in response to receiving the wireless request from the remote computing device. The detection system may comprise a microphone and a speaker. The microphone may be arranged and configured to record noise in response to the motion detector detecting a motion. The microphone may be arranged and configured to record noise in response to the occurrence of at least one of the security system sending an alert to the remote computing device and the security system receiving a wireless request from the remote computing device. The first electrical prong and the second electrical prong may be arranged and configured to receive electrical power from the power outlet to power the security system. The security system may include a fisheye lens coupled to the outwardly facing portion. The fisheye lens may be arranged and configured to create a broader field of view for the camera.

In some embodiments a security system may include an outwardly facing portion, an inwardly facing portion, and a detection system. The security system may be configured to mount to a power outlet. The outwardly facing portion may be configured to face away from the power outlet. The inwardly facing portion may have a first electrical prong and a second electrical prong that protrude into the power outlet to mount the security system to the power outlet. The detection system may be coupled to the outwardly facing portion. The detection system may include a camera and a microphone.

In some embodiments, a remote computing device may be communicatively coupled to the security system. The security system may be arranged and configured to send an alert to the remote computing device in response to the microphone detecting a first noise. The security system may be arranged and configured to send the alert to the remote computing device in response to the microphone detecting the first noise during a first predetermined time of day. The security system may be arranged and configured to not send the alert to the remote computing device in response to the microphone detecting a second noise during a second predetermined time of day.

In several embodiments, the camera may be arranged and configured to exit a sleep mode and enter a live view mode in response to the microphone detecting the first noise. When the camera is in the sleep mode the camera may be configured to not capture images. When the camera is in the live view mode the camera may be configured to capture images. The microphone may be configured to record noise in response to receiving a wireless request from the remote computing device.

The embodiments described above include many optional features and aspects. Features and aspects of the embodiments can be combined.

BRIEF DESCRIPTION OF THE DRAWINGS

These and other features, aspects, and advantages are described below with reference to the drawings, which are intended to illustrate, but not to limit, the invention. In the drawings, like reference characters denote corresponding features consistently throughout similar embodiments.

FIG. 1 illustrates a front view of a communication system, according to some embodiments.

FIG. 2 illustrates a computing device running software, according to some embodiments.

FIG. 3 illustrates an embodiment in which a security system is connected to a building, according to some embodiments.

FIG. 4 illustrates a communication system that includes a security system, a doorbell button, a wireless router, a server, and users, according to some embodiments.

FIG. 5 illustrates a front view of a security system, according to some embodiments.

FIG. 6 illustrates a perspective view of the security system from FIG. 5, according to some embodiments.

FIG. 7 illustrates a side view of the security system from FIG. 5, according to some embodiments.

FIG. 8 illustrates a perspective view of a camera assembly, according to some embodiments.

FIG. 9 illustrates a partial, perspective, cross-sectional view along line 9-9 from FIG. 5, according to some embodiments.

FIG. 10 illustrates a perspective, cross-sectional view along line 9-9 from FIG. 5, according to some embodiments.

FIG. 11 illustrates a back view of the security system from FIG. 5 without a mounting bracket, according to some embodiments.

FIG. 12 illustrates a back view of the security system from FIG. 5 with a mounting bracket, according to some embodiments.

FIG. 13 illustrates a perspective view of the outer housing from FIG. 5, according to some embodiments.

FIG. 14 illustrates a front view of a mounting bracket coupled to a wall, according to some embodiments.

FIG. 15 illustrates a partial, side view of the mounting bracket, according to some embodiments.

FIGS. 16 and 17 illustrate methods of using a security system, according to some embodiments.

FIG. 18 illustrates data prioritization methods, according to some embodiments.

FIGS. 19 and 20 illustrate a visitor in two locations within a camera's field of view, according to some embodiments.

FIGS. 21 and 22 illustrate methods of displaying a visitor, according to some embodiments.

FIG. 23 illustrates several devices that can communicate with a security system, according to some embodiments.

FIG. 24 illustrates an embodiment of a security system with multiple buttons, according to some embodiments.

FIG. 25 depicts an illustrative embodiment of a security system with hardware and software components, according to some embodiments.

FIG. 26 depicts an illustrative embodiment of a system or architecture 2600 in which a security system for allowing communication may be implemented, according to some embodiments.

FIG. 27 depicts a flow diagram showing methods of operating a doorbell communication system, according to some embodiments.

FIG. 28 depicts an illustrative embodiment of several features that can be implemented in a mobile application, according to some embodiments.

FIG. 29 depicts an illustrative embodiment of a user being provided with the ability to record a message via a remote computing device, according to some embodiments.

FIG. 30 depicts an illustrative embodiment of emergency functionality, according to some embodiments.

FIG. 31 depicts an illustrative embodiment of a menu for selecting notification settings, according to some embodiments.

FIG. 32 depicts an illustrative embodiment of a menu for selecting volume settings for a security system, according to some embodiments.

FIG. 33 depicts an illustrative embodiment of a menu for selecting sound settings for the security system, according to some embodiments.

FIG. 34 depicts an illustrative embodiment of a menu for selecting notification settings for the security system, according to some embodiments.

FIG. 35 depicts an illustrative embodiment of a menu for selecting which users receive notifications for the security system, according to some embodiments.

FIG. 36 depicts an illustrative embodiment of a menu for viewing multiple security systems, according to some embodiments.

FIG. 37 depicts an illustrative embodiment of a menu for viewing settings of the security system, according to some embodiments.

FIG. 38 illustrates a user interface configured to enable a user to adjust the field of view of a camera, according to some embodiments.

FIG. 39 illustrates a top view of a camera orientation embodiment, according to some embodiments.

FIG. 40 illustrates a side view of the camera orientation embodiment from FIG. 39, according to some embodiments.

FIGS. 41 and 42 illustrate perspective views of the camera orientation embodiment from FIG. 39, according to some embodiments.

FIG. 43 illustrates a front view of a security system, according to some embodiments.

FIGS. 44A and 44B illustrate methods of using a security system, according to some embodiments.

FIG. 45 illustrates a perspective view of a security system with a locking assembly, according to some embodiments.

FIGS. 46A and 46B illustrate side views with a partial cross section of the locking assembly shown in FIG. 45, according to some embodiments.

FIG. 47 illustrates a diagrammatic view of an electrical power configuration, according to some embodiments.

FIG. 48 illustrates a diagrammatic view of a security system configured to wirelessly communicate with a sound output device, according to some embodiments.

FIG. 49 illustrates a diagrammatic view of a security system located inside of a building, according to some embodiments.

FIG. 50 illustrates a diagrammatic view of a security system used to monitor a pool area, according to some embodiments.

FIG. 51 illustrates a communication system with two wireless networks, according to some embodiments.

FIG. 52 illustrates methods of using a security system, according to some embodiments.

FIG. 53 illustrates scanning barcodes on a package to enable notifying a user regarding the delivery of the package, according to some embodiments.

FIG. 54 illustrates a front view of a dashboard of a vehicle, according to some embodiments.

FIG. 55 illustrates a perspective view of glasses, according to some embodiments.

FIG. 56 illustrates a perspective view of a camera assembly coupled directly to a printed circuit board, according to some embodiments.

FIGS. 57-60 illustrate front views of a display screen or portions thereof with graphical user interfaces, according to some embodiments.

FIG. 61 illustrates a front view of the security system just before the security system is mounted to a power outlet, according to some embodiments.

FIG. 62 illustrates a front view of the security system after the security system is mounted to a power outlet, according to some embodiments.

FIG. 63 illustrates a side perspective view of the security system just before the security system is mounted to a power outlet, according to some embodiments.

FIG. 64 illustrates a front view of a security system configured to mount to a power outlet, according to some embodiments.

FIG. 65 illustrates a front, side, and top perspective view of the security system embodiment shown in FIG. 64, according to some embodiments.

FIG. 66 illustrates a back view of the security system embodiment shown in FIG. 64, according to some embodiments.

FIG. 67 illustrates a back, side, and top perspective view of the security system embodiment shown in FIG. 64, according to some embodiments.

FIG. 68 illustrates a side view of a security system separated into multiple portions, according to some embodiments.

FIG. 69 illustrates a side, front, and bottom perspective view of a security system separated into multiple portions, according to some embodiments.

FIG. 70 illustrates a side and front perspective view in which an outwardly facing portion is mounted in a location away from a power outlet while an inwardly facing portion is attached to the power outlet, according to some embodiments.

FIG. 71 illustrates a side and front perspective view in which an outwardly facing portion is mounted to an inwardly facing portion while the inwardly facing portion is attached to the power outlet, according to some embodiments.

FIG. 72 illustrates a side and top perspective view of a security system that includes a 360-degree camera assembly, according to some embodiments.

FIG. 73 illustrates a side and front perspective view of a security system and a dock configured to hold the security system, according to some embodiments.

FIGS. 74, 75, and 76 illustrate methods of using a security system, according to some embodiments.

DETAILED DESCRIPTION

Although certain embodiments and examples are disclosed below, inventive subject matter extends beyond the specifically disclosed embodiments to other alternative embodiments and/or uses, and to modifications and equivalents thereof. Thus, the scope of the claims appended hereto is not limited by any of the particular embodiments described below. For example, in any method or process disclosed herein, the acts or operations of the method or process may be performed in any suitable sequence and are not necessarily limited to any particular disclosed sequence. Various operations may be described as multiple discrete operations in turn, in a manner that may be helpful in understanding certain embodiments; however, the order of description should not be construed to imply that these operations are order dependent. Additionally, the structures, systems, and/or devices described herein may be embodied as integrated components or as separate components.

For purposes of comparing various embodiments, certain aspects and advantages of these embodiments are described. Not necessarily all such aspects or advantages are achieved by any particular embodiment. Thus, for example, various embodiments may be carried out in a manner that achieves or optimizes one advantage or group of advantages as taught herein without necessarily achieving other aspects or advantages as may also be taught or suggested herein.

The following patent is incorporated herein by reference: U.S. Pat. No. 7,583,191, entitled SECURITY SYSTEM AND METHOD FOR USE OF SAME, and filed Nov. 14, 2006.

Introduction

Communication systems can provide a secure and convenient way for a remotely located individual to see and/or communicate with a person who is within the field of view of a camera and/or within the range of a microphone. Communication systems can include a camera that is plugged directly into a power outlet to mount the camera on a wall. Communication systems can also include cameras that are integrated into doorbells and/or are located in other areas in, on, and/or near a building.

Some communication systems can allow an individual to hear, see, and talk with visitors. For example, communication systems can use a computing device to enable a remotely located person to see, hear, and/or talk with visitors. Computing devices can include computers, laptops, tablets, mobile devices, smartphones, cellular phones, and wireless devices (e.g., cars with wireless communication). Example computing devices include the iPhone, iPad, iMac, MacBook Air, and MacBook Pro made by Apple Inc. Communication between a remotely located person and a visitor can occur via the Internet, cellular networks, telecommunication networks, and wireless networks.

Referring now to FIG. 1, communication systems 200 can be a portion of a smart home hub. Communication systems 200 can facilitate home automation. In some cases, cameras 208 plugged into power outlets 228 are integrated into a holistic home automation system and/or home security system. Various systems described herein enable home surveillance and/or complete home automation. Cameras 208 plugged into interior power outlets 228 can enable a remote user to see events inside of a building 300 (shown in FIG. 3). Cameras 208 plugged into exterior power outlets 228 can enable a remote user to see events outside of a building 300.

Power outlets 228 can be located in an electrical box and partially concealed by a plastic plate with holes to enable the power outlets 228 to be accessible to people. For example, people can plug an appliance into a power outlet 228. Two power outlets 228 can be grouped together in an electrical duplex 266. In some embodiments, many power outlets 228 are grouped together. As illustrated in FIG. 1, the security system 202 is attached to a power outlet 228 that is hidden behind the security system 202, although other portions of the electrical duplex 266 are still visible.

In some embodiments, the security system 202 controls various electrical items in a home (e.g., lights, air conditioners, heaters, motion sensors, garage door openers, locks, televisions, computers, entertainment systems, pool monitors, elderly monitors). In some embodiments, the computing device 204 controls the security system 202 and other electrical items in a home (e.g., lights, air conditioners, heaters, motion sensors, garage door openers, locks, televisions, computers, entertainment systems, pool monitors, elderly monitors).

Communication systems can provide a secure and convenient way for a remotely located individual to communicate with a person who is approaching a sensor, such as a proximity sensor or motion sensor, or with a person who rings a doorbell, which can be located in a doorway, near an entrance, or within 15 feet of a door. FIG. 1 illustrates the security system 202 in the context of being electrically and mechanically coupled to a power outlet 228, but alternatively, the security system 202 can also be electrically coupled to existing doorbell wiring and can be used as a doorbell (see FIG. 5 of this application and FIG. 1 of U.S. Nonprovisional patent application Ser. No. 14/589,830; filed Jan. 5, 2015; and entitled DOORBELL COMMUNICATION SYSTEMS AND METHODS).

FIG. 1 illustrates a front view of a communication system embodiment. The communication system 200 can include a security system 202 (e.g., a camera assembly) and a computing device 204. Although the illustrated security system 202 includes many components in one housing, several security system embodiments include components in separate housings. The security system 202 can include a camera assembly 208. The camera assembly 208 can include a video camera, which in some embodiments is a webcam. The camera assembly 208 can be configured to take videos of a surrounding area for viewing via the Internet.

The security system 202 can include a diagnostic light 216 and a power indicator light 220. In some embodiments, the diagnostic light 216 is a first color (e.g., blue) if the security system 202 and/or the communication system 200 is connected to a wireless Internet network and is a second color (e.g., red) if the security system 202 and/or the communication system 200 is not connected to a wireless Internet network. In some embodiments, the power indicator 220 is a first color if the security system 202 is connected to a power source. The power source can be power supplied by the building to which the security system 202 is attached. The security system 202 can receive electricity via the power outlet 228 to which the security system 202 is mounted. In some embodiments, the power indicator 220 is a second color or does not emit light if the security system 202 is not connected to the power source.

The security system 202 (e.g., a camera assembly) can include an outer housing 224, which can be water resistant and/or waterproof. The outer housing can be made from metal or plastic, such as molded plastic with a hardness of 60 Shore D. In some embodiments, the outer housing 224 is made from brushed nickel or aluminum. The outer housing 224 can be rigid. Rubber seals can be used to make the outer housing 224 water resistant or waterproof.

The security system 202 can be electrically coupled to a power source, such as wires electrically connected to a building's electrical power system. In some embodiments, the security system 202 includes a battery for backup and/or primary power.

The security system 202 can include lights 246, which can be infrared lights. The lights 246 can illuminate an area in front of the camera assembly's 208 field of view to enable the camera assembly 208 to capture easily viewable and high-quality video. Infrared light can be suitable for nighttime video recording.

The security system 202 can include a communication module 262 configured to enable wireless communication with the computing device 204. The communication module 262 can include a WiFi antenna and can be configured to enable the security system 202 to connect to a wireless network 308 of a building 300 (shown in FIG. 3).

Wireless communication 230 can enable the security system 202 (e.g., a camera assembly) to communicate with the computing device 204. Some embodiments enable communication via cellular and/or WiFi networks. Some embodiments enable communication via the Internet. (Several embodiments enable wired communication between the security system 202 and the computing device 204.) The wireless communication 230 can include the following communication means: radio, WiFi (e.g., wireless local area network), cellular, Internet, Bluetooth, telecommunication, electromagnetic, infrared, light, sonic, and microwave. Other communication means are used by some embodiments. In some embodiments, such as embodiments that include telecommunication or cellular communication means, the security system 202 can initiate voice calls or send text messages to a computing device 204 (e.g., a smartphone, a desktop computer, a tablet computer, a laptop computer).

Several embodiments use near field communication (NFC) to communicate between the computing device 204 and the security system 202. The security system 202 and/or the computing device 204 can include a NFC tag. Some NFC technologies include Bluetooth, radio-frequency identification, and QR codes.

Several embodiments include wireless charging (e.g., near field charging, inductive charging) to supply power to and/or from the security system 202 and the computing device 204. Some embodiments use inductive charging (e.g., using an electromagnetic field to transfer energy between two objects).

Software

Some embodiments include computer software (e.g., application software), which can be a mobile application designed to run on smartphones, tablet computers, and other mobile devices. Software of this nature is sometimes referred to as “app” software. Some embodiments include software designed to run on desktop computers and laptop computers.

The computing device 204 can run software with a graphical user interface. The user interface can include icons or buttons. In some embodiments, the software is configured for use with a touch-screen computing device such as a smartphone or tablet.

FIG. 2 illustrates a computing device 204 running software. The computing device 204 in FIG. 2 is a cellular telephone, but embodiments can use diverse types of computing devices. The software includes a user interface 240 displayed on a display screen 242. The user interface 240 can include a security system indicator 244, which can indicate the location of the security system that the user interface is displaying. For example, a person can use one computing device 204 to control and/or interact with multiple security systems, such as one security system located at a front door and another security system located at a back door. Selecting the security system indicator 244 can allow the user to choose another security system (e.g., the back door security system rather than the front door security system).

The user interface 240 can include a connectivity indicator 248. In some embodiments, the connectivity indicator can indicate whether the computing device is in communication with a security system, the Internet, and/or a cellular network. The connectivity indicator 248 can alert the user if the computing device 204 has lost its connection with the security system 202; the security system 202 has been damaged; the security system 202 has been stolen; the security system 202 has been removed from its mounting location; the security system 202 has lost electrical power; and/or if the computing device 204 cannot communicate with the security system 202. In some embodiments, the connectivity indicator 248 alerts the user of the computing device 204 by flashing, emitting a sound, displaying a message, and/or displaying a symbol.

Referring now to FIG. 1, in some embodiments, if the security system 202 loses power, loses connectivity to the computing device 204, loses connectivity to the Internet, and/or loses connectivity to a remote server, a remote server 206 sends an alert (e.g., phone call, text message, image on the user interface 240) regarding the power and/or connectivity issue. In several embodiments, the remote server 206 can manage communication between the security system 202 and the computing device 204. In some embodiments, information from the security system 202 is stored by the remote server 206. In several embodiments, information from the security system 202 is stored by the remote server 206 until the information can be sent to the computing device 204, uploaded to the computing device 204, and/or displayed to the remotely located person via the computing device 204. The remote server 206 can be a computing device that stores information from the security system 202 and/or from the computing device 204.

In some embodiments, the remote server 206 is located in a data center. In some embodiments, the computing device 204 and/or the remote server 206 attempts to communicate with the security system 202. If the computing device 204 and/or the remote server 206 is unable to communicate with the security system 202, the computing device 204 and/or the remote server 206 alerts the remotely located person via the software, phone, text, a displayed message, and/or a website. In some embodiments, the computing device 204 and/or the remote server 206 attempts to communicate with the security system 202 periodically; at least every five hours and/or more than every 10 minutes; at least every 24 hours and/or more than every 60 minutes; or at least every hour and/or more than every second.

In some embodiments, the server 206 can initiate communication to the computer device 204 and/or to the security system 202. In several embodiments, the server 206 can initiate, control, and/or block communication between the computing device 204 and the security system 202.

In several embodiments, a user can log in to an “app,” website, and/or software on a computing device (e.g., mobile computing device, smartphone, tablet, desktop computer) to adjust the security system settings discussed herein.

In some embodiments, a computing device can enable a user to watch live video and/or hear live audio from a security system due to the user's request rather than due to actions of a visitor. Some embodiments include a computing device initiating a live video feed (or a video feed that is less than five minutes old).

Referring now to FIG. 2, in some embodiments, the user interface 240 displays an image 252 such as a still image or a video of an area near and/or in front of the security system 202. The image 252 can be taken by the camera assembly 208 and stored by the security system 202, server 206, and/or computing device 204. The user interface 240 can include a recording button 256 to enable a user to record images, videos, and/or sound from the camera assembly 208, microphone of the security system 202, and/or microphone of the computing device 204.

In several embodiments, the user interface 240 includes a picture button 260 to allow the user to take still pictures and/or videos of the area near and/or in front of the security system 202. The user interface 240 can also include a sound adjustment button 264 and a mute button 268. The user interface 240 can include camera manipulation buttons such as zoom, pan, and light adjustment buttons. In some embodiments, the camera assembly 208 automatically adjusts between Day Mode and Night Mode. Some embodiments include an infrared camera and/or infrared lights to illuminate an area near the security system 202 to enable the camera assembly 208 to provide sufficient visibility (even at night).

In some embodiments, buttons include diverse means of selecting various options, features, and functions. Buttons can be selected by mouse clicks, keyboard commands, or touching a touch screen. Many embodiments include buttons that can be selected without touch screens.

In some embodiments, the user interface 240 includes a quality selection button, which can allow a user to select the quality and/or amount of data transmitted from the security system 202 to the computing device 204 and/or from the computing device 204 to the security system 202. For example, if the data transmission capability of the wireless communication is insufficient to transmit high-resolution video from the security system 202 to the computing device 204, the user might select a lower resolution video setting. In some cases, the user might select a still image rather than video or a single still image every period of time where the period of time can be more than 0.1 seconds and/or less than 60 seconds; more than 0.5 seconds and/or less than 30 seconds; or more than 1 second and/or less than 15 seconds. In some cases, the security system 202 might only send a single still image to the computing device 204.

Many embodiments utilize the visitor identification abilities of the person using the remote computing device 204 (shown in FIG. 1). Various technologies, however, can be used to help the user of the remote computing device 204 to identify the visitor. Some embodiments use automated visitor identification that does not rely on the user, some embodiments use various technologies to help the user identify the visitor, and some embodiments display images and information (e.g., a guest name) to the user, but otherwise do not help the user identify the visitor.

Referring now to FIG. 1, the camera assembly 208 can be configured to visually identify visitors through machine vision and/or image recognition. For example, the camera assembly 208 can take an image of the visitor. Software run by any portion of the system can then compare select facial features from the image to a facial database. In some embodiments, the select facial features include dimensions based on facial landmarks. For example, the distance between a visitor's eyes; the triangular shape between the eyes and nose; and the width of the mouth can be used to characterize a visitor and then to compare the visitor's characterization to a database of characterization information to match the visitor's characterization to an identity (e.g., an individual's name, authorization status, and classification). Some embodiments use three-dimensional visitor identification methods.

Some embodiments include facial recognition such that the camera assembly 208 waits until the camera assembly 208 has a good view of the person located near the security system 202 and then captures an image of the person's face. Facial recognition can be used to establish a visitor's identity.

Several embodiments can establish a visitor's identity by detecting a signal from a device associated with the visitor (e.g., detecting the visitor's smartphone). Examples of such a signal include Bluetooth, WiFi, RFID, NFC, and/or cellular telephone transmissions.

In some embodiments, video can be sent to and/or received from the computing device 204 using video chat protocols such as FaceTime (by Apple Inc.) or Skype (by Microsoft Corporation). In some embodiments, these videos are played by videoconferencing apps on the computing device 204 instead of being played by the user interface 240.

Referring now to FIG. 2, the user interface 240 can include a termination button 276 to end communication between the security system 202 and the computing device 204. In some embodiments, the termination button 276 ends the ability of the person located near the security system 202 (i.e., the visitor) to hear and/or see the user of the computing device 204, but does not end the ability of the user of the computing device 204 to hear and/or see the person located near the security system 202.

In some embodiments, a button 276 is both an answer button (to accept a communication request from a visitor) and a termination button (to end communication between the security system 202 and the computing device 204). The button 276 can include the word “Answer” when the system is attempting to establish two-way communication between the visitor and the user. Selecting the button 276 when the system is attempting to establish two-way communication between the visitor and the user can start two-way communication. The button 276 can include the words “End Call” during two-way communication between the visitor and the user. Selecting the button 276 during two-way communication between the visitor and the user can terminate two-way communication. In some embodiments, terminating two-way communication still enables the user to see and hear the visitor. In some embodiments, terminating two-way communication causes the computing device 204 to stop showing video from the security system and to stop emitting sounds recorded by the security system.

In some embodiments, the user interface 240 opens as soon as the security system detects a visitor (e.g., senses indications of a visitor). Once the user interface 240 opens, the user can see and/or hear the visitor even before “answering” or otherwise accepting two-way communication, in several embodiments. The security system 202 can include a microphone 234 and a speaker 236 to enable the user to hear the visitor and to enable the visitor to hear the user. Thus, the security system 202 can enable the user to communicate with the visitor.

Some method embodiments include detecting a visitor with a security system. The methods can include causing the user interface 240 (shown in FIG. 2) to display on a remote computing device 204 due to the detection of the visitor (e.g., with or without user interaction). The methods can include displaying video from the security system and/or audio from the security system before the user accepts two-way communication with the visitor. The methods can include displaying video from the security system and/or audio from the security system before the user accepts the visitor's communication request. The methods can include the computing device simultaneously asking the user if the user wants to accept (e.g., answer) the communication request and displaying audio and/or video of the visitor. For example, in some embodiments, the user can see and hear the visitor via the security system before opening a means of two-way communication with the visitor.

In some embodiments, the software includes means to start the video feed on demand. For example, a user of the computing device might wonder what is happening near the security system 202. The user can open the software application on the computing device 204 and instruct the application to show live video and/or audio from the security device 202 even if no event near the security system 202 has triggered the communication.

In several embodiments, the security device 202 can be configured to record video, images, and/or audio when the security device 202 detects movement and/or the presence of a person. The user of the computing device 204 can later review all video, image, and/or audio records when the security device 202 detected movement and/or the presence of a person.

Some embodiments include a media roll or other means to record a certain amount of data and then record over some of the data, such as the oldest data or low-priority data. For example, some systems record over data that is older than seven days, 14 days, or one month. Some security systems can be configured to continuously record video and/or audio to a media roll, which can be viewed on a remotely located computing device.

In several embodiments, the system (e.g., software, computing device 204, security system 202 in FIG. 1) can be configured to allow user customization of where, when, and/or how notifications (e.g., doorbell communication requests) are received on one or more computing devices (e.g., 204 in FIG. 3). In some embodiments, the system can be configured to only notify a user's smartphone at certain times of day or night. In some embodiments, the system can be configured to only notify a user's smartphone when the smartphone is in a predetermined proximity to the building (e.g., within 10 feet, within 50 feet, within 100 feet). In some embodiments, the system can be configured to only notify a user's smartphone when the smartphone is at or near a specified location. In some embodiments, the system can be configured to only notify a user's smartphone when the smartphone is connected to a home network. In some embodiments, the system can be configured to only notify a first user's smartphone when a second user's smartphone is present or absent. In some embodiments, the system can be configured to send only text messages at certain times of day (rather than sending other types of notifications, such as launching an app and then displaying an image). In some embodiments, the system can be configured to send one-way audio or one-way video (rather than two-way audio and/or two-way video) if the user is away from home. In some embodiments, the system can be configured to block notifications during certain times, when the user is in certain places (e.g., in a meeting, in the building to which the security system is attached), and/or if the user prefers not to receive notifications.

Referring now to FIGS. 1 and 2, in several embodiments, software, the computing device 204, and/or the user interface 240 enables a user to control the doorbell's features and functions. In some embodiments, the software, the computing device 204, and/or the user interface 240 enables a user to turn the security system 202 off and/or turn the ringing function off such that pressing the doorbell button 212 (shown in FIG. 5) will not emit a sound, such as a chime, inside the building. Example chimes include sounds emitted from door chimes made by HeathCo LLC under the brand Heath Zenith. Turning the security system 202 off and/or turning the ringing function off can be helpful when the user does not want people inside the building to be bothered by doorbell sounds (e.g., chimes). For example, people might be sleeping inside the home.

The user interface 240 can include a button to silence the doorbell sound and to place the security system 202 in Silent Mode. In some embodiments of Silent Mode, pressing the doorbell button 212 (shown in FIG. 5) will not send a signal to a chime located inside the building for the chime to emit a sound. In some embodiments, the chime is a speaker (such as a speaker made by Bose Corporation) located inside of the building, which can be a home, office, warehouse, or other structure.

In some embodiments, a security system 202 and/or a computing device 204 communicates with a baby monitor. If the baby monitor detects indicators that a baby is sleeping (e.g., the presence of a baby that is not moving, as sensed by an IR motion detector) the communication system can disable the doorbell sound to avoid disturbing the baby's sleep. Some embodiments work the same way except that the baby is replaced by a person, such as an adult.

Several embodiments include a motion detector 218. The motion detector 218 can sense whether a visitor is located near an entryway.

Several embodiments include sending a notification to the user regarding the presence of the visitor even if the visitor has not pressed the doorbell button 212 (shown in FIG. 5) to “ring” the doorbell (e.g., to sound a chime inside of the building). In several embodiments, if motion is detected by the doorbell for five seconds and the doorbell button 212 has not been pressed (e.g., within the last five seconds, within the last 30 seconds, within the last 60 seconds), then the doorbell automatically sends a notification to the user regarding the presence of the visitor. The notification can be sent to a remotely located computing device 204 and/or via a chime 302 (shown in FIG. 3).

In several embodiments, if the doorbell button 212 has been pressed (e.g., within the last 5 seconds, within the last 30 seconds, within the last 60 seconds), then motion alerts are canceled for three minutes. For example, methods can include blocking notifications based on motion detection for three minutes (or for at least 60 seconds, at least three minutes, and/or less than ten minutes) from the time the doorbell button 212 has been pressed.

In some embodiments, the user interface 240 has a button to make the doorbell ring (e.g., make the chime emit a sound inside of the building). The user can ring the doorbell by pressing a button on the computing device 204.

Some embodiments include administrative privileges. These privileges can include administrative abilities and the ability to alter settings. The administrative privileges can be password protected. The administrator can add and remove notification recipients and/or computing devices 204. For example, a user who sets up the communication system 200 by initially pairing a computing device 204 with a security system 202 can be given administrative privileges and the highest priority (as explained herein). This administrative user can give permissions and priorities to other users and computing devices 204 (e.g., as explained in the context of FIG. 17). This administrative user can choose settings (e.g., as explained in the context of FIG. 18). This administrative user can give or transfer administrative rights to another user and/or computing device 204.

Several embodiments include a mode to address overly frequent notifications. This mode is called Peaceful Mode. For example, on Halloween, the security system 202 may sense doorbell button 212 (shown in FIG. 5) presses, motion, proximity, and/or sound more frequently than the user wants to be notified. Some embodiments include a maximum notification setting (e.g., the maximum number of notifications that will be communicated to the user per unit of time). If the maximum number of notifications is exceeded, then the system can enter Peaceful Mode. In several embodiments, the maximum number of notifications is three notifications per hour; four notifications per hour; five notifications per hour; seven notifications per hour; ten notifications per hour; four notifications per day; seven notifications per day; seven notifications per 24 hours; or fifteen notifications per 24 hours. In some embodiments, the user can set the maximum number of notifications and/or the time period over which the notifications are counted towards a maximum number. In some embodiments, the user can set the maximum number of notifications via the software, a website configured to communicate with the server 206, and/or a user interface 240.

In some embodiments of Peaceful Mode, the system stops alerting the user via the computing device 204. For example, a visitor pressing the doorbell button 212 (shown in FIG. 5) could cause a sound (e.g., a chime) to be emitted inside or near the building but would not cause the computing device 204 to notify the user.

In some embodiments of Peaceful Mode, the system stops alerting the user via the chime located inside of the building. For example, a visitor pressing the doorbell button 212 could cause the computing device 204 to notify the user, but would not cause a sound (e.g., a chime) to be emitted inside or near the building.

In some embodiments of Peaceful Mode, the system stops alerting the user via the chime located inside of the building and via the computing device 204. For example, a visitor pressing the doorbell button 212 would not cause a sound (e.g., a chime) to be emitted inside or near the building and would not cause the computing device 204 to notify the user.

In some embodiments of Peaceful Mode, the system does not automatically stop alerting the user via the computing device and does not automatically stop alerting the user via the chime, but instead, once the maximum number of notifications is exceeded, the software, computing device 240, and/or user interface 240 asks the user if the user wants to enter Peaceful Mode, turn off notifications via the computing device 240, and/or turn off notifications via the sounds emitted inside and/or near the building (e.g., chimes). In several embodiments, the software, computing device 240, and/or user interface 240 asks the user how long the user wants to turn off notifications via the computing device 240, and/or turn off notifications via the sounds emitted inside and/or near the building. In some embodiments, notifications are turned off for at least 15 minutes and/or less than 4 hours; at least 5 minutes and/or less than one hour; or at least 30 minutes and/or less than 24 hours.

In some embodiments of Peaceful Mode, Peaceful Mode does not turn off notifications, but instead reduces the volume, frequency, and/or intensity of notifications. In some embodiments of Peaceful Mode, the chime volume can be reduced by at least 30 percent, at least 50 percent, or at least 70 percent. In some embodiments of Peaceful Mode, the alerts to the computing device 204 switch to Non-auditory Mode such that the computing device 204 does not ring or send auditory alerts, but instead sends alerts such as vibrations (with little or no sound) and/or visual alerts (e.g., messages on the user interface 240).

Referring now to FIG. 2, in several embodiments, software of the computing device includes a snapshot feature, which enables a user to take an image or short video (e.g., less than five seconds, less than 10 seconds) of the visitor. The image and/or short video is stored in the computing device 204 and/or in a remote location and is retrievable by the computing device.

In some embodiments, an image and/or video of each visitor is automatically stored in a visitor log retrievable by the user. The image and/or video of each visitor can be automatically triggered by the security system detecting a visitor.

Data sent between a security system and a computing device can be secured via encryption, transport layer security, secure sockets layer, and/or cryptographic protocols. Data regarding a security system that is sent from one computing device to another computing device can be secured via encryption, transport layer security, secure sockets layer, and/or cryptographic protocols.

Many security system embodiments and method embodiments are configured to work with any computing device (e.g., a cellular phone, tablet, laptop, desktop computer). Software applications can be configured to work with particular operating systems. In some cases, making software applications compatible with all operating systems and computing devices can be challenging. Some embodiments open a website (e.g., on the display screen 242 shown in FIG. 2) in response to a user accepting a push notification (e.g., regarding the presence of a visitor detected by a doorbell).

A simple software application can be used to launch the website in response to the user accepting a push notification. Many diverse computing devices are capable of opening websites, which can enable a website-based system to be compatible with a broad range of computing devices.

Website-based systems can be used for pool monitoring and elderly monitoring applications. For example, a security system 202 can be used to monitor a pool 5030 (shown in FIG. 50). An unwanted visitor into the pool 5030 (or into a zone 5034 around the pool 5030) can trigger a push notification to a computing device 204 (shown in FIG. 51). The user can respond to the push notification by accepting communication with the security system 202, which can result in opening a website in response to the user accepting the push notification. The website 5558 can show an image taken by a camera of the security system 202 and can be configured to enable the user to hear the visitor and talk with the visitor.

Server Interaction

Referring now to FIG. 1, in some embodiments, the server 206 controls communication between the computing device 204 and the security system 202, which can include a camera, a microphone, and a speaker. In several embodiments, the server 206 does not control communication between the computing device 204 and the security system 202.

Server 206 control can prevent unwanted communication between the computing device 204 and the security system 202. For example, if the computing device 204 is stolen from a user, the user can contact a server administrator to block communication between the security system 202 and the computing device 204. The user can provide an authentication means, such as a password or user information, so the server administrator knows the user is in fact authorized to make changes. In some embodiments, the server 206 can update any of the settings and options described herein. In some embodiments, the user can update any of the settings and options described herein via a website. The server 206 can be used to register users and update settings of the computing device 204, the security system 202, and/or the communication system 200.

In some embodiments, data captured by the security system and/or the computing device 204 (such as videos, pictures, and audio) is stored by another remote device such as the server 206. Cloud storage, enterprise storage, and/or networked enterprise storage can be used to store video, pictures, and/or audio from the communication system 200 or from any part of the communication system 200. The user can download and/or stream stored data and/or storage video, pictures, and/or audio. For example, a user can record visitors for a year and then later can review the visits from the last year. In some embodiments, remote storage, the server 206, the computing device 204, and/or the security system 202 can store information and statistics regarding visitors and usage.

In some embodiments, this information can be transferred, forwarded, and/or sent to other computing devices and/or servers. A user can record a communication (e.g., video and audio) with a visitor and then can forward the communication to another person. The forwarded information can include additional information from the user such as a recorded message and/or a text message. For example, if one user talks with a visitor via a security system 202, the user can forward the conversation to the person that the visitor was seeking.

High-Level System Overview

FIG. 3 illustrates an embodiment in which a security system 202 is connected to a building 300, which can include an entryway 310 that has a door 254. Electrical wires 304 can electrically couple the security system 202 to the electrical system of the building 300 such that the security system 202 can receive electrical power from the building 300.

A wireless network 308 can allow devices to wirelessly access the Internet. The security system 202 can access the Internet via the wireless network 308. The wireless network 308 can transmit data from the security system 202 to the Internet, which can transmit the data to remotely located computing devices 204. The Internet and wireless networks can transmit data from remotely located computing devices 204 to the security system 202. In some embodiments, a security system 202 connects to a home's WiFi.

As illustrated in FIG. 3, one computing device 204 (e.g., a laptop, a smartphone, a mobile computing device, a television) can communicate with multiple security systems 202. In some embodiments, multiple computing devices 204 can communicate with one security system 202.

In some embodiments, the security system 202 can communicate (e.g., wirelessly 230) with a television 306, which can be a smart television. The television 306 can display any of the items shown in FIGS. 28 to 38, although many other types of computing devices (e.g., smart phones, tablets, laptops) can also display any of the items shown in FIGS. 28 to 38. Users can view the television 306 to see a visitor and/or talk with the visitor.

Joining a Wireless Network

Although some security system embodiments include using electricity from electrical wires 304 of a building 300, many security system embodiments communicate with computing devices 204 via a wireless network 308 that allows security systems 202 to connect to a regional and sometimes global communications network. In some embodiments, the security system 202 communicates via a wireless network 308 with a router that enables communication with the Internet, which can enable communication via diverse means including telecommunication networks. In this way, a security system 202 can communicate with computing devices 204 that are desktop computers, automobiles, laptop computers, tablet computers, cellular phones, mobile devices, and smart phones.

In some embodiments, a security system (e.g., a doorbell) needs to know which wireless network to join and needs to know the wireless network's password. A computing device, such as a smartphone, can provide this information to the security system.

The following method is used in some embodiments. (Some embodiments include orders that are different from the following order.) First, the computing device (e.g., a smartphone) creates an ad hoc wireless network. Second, the user opens software (such as an app) on the computing device. When the security system is in Setup Mode, the security system can automatically join the computing device's ad hoc network. Third, the user can utilize the software to select the wireless network that the security system should join and to provide the password of the wireless network (e.g., of the router) to the security system.

Diverse methods can be used to connect a security system (e.g., a doorbell) to a wireless network (such as a wireless network of a home). Several embodiments include transmitting an identifier (e.g., a name) to a security system, wherein the identifier enables the security system to identify the wireless network to which the security system should connect. Several embodiments include transmitting a password of the wireless network to the security system, wherein the password enables the security system to connect to the network. In some embodiments, a computing device (e.g., a smartphone) transmits the identifier and password.

In several embodiments, methods of connecting a security system (e.g., a doorbell) to a wireless network (e.g., a wireless network of a home or building) can include placing the security system in Setup Mode. Some security systems automatically go into Setup Mode upon first use, first receiving electrical power, first receiving electrical power after a reset button is pushed, first receiving electrical power after being reset, and/or when a reset button is pushed.

In some embodiments, a Setup Mode comprises a Network Connection Mode. Methods can comprise entering the Network Connection Mode in response to pressing the button for at least eight seconds. The Network Connection Mode can comprise detecting a first wireless network having a name and a password. The Network Connection Mode can comprise inputting a doorbell identification code into the remotely located computing device. The doorbell identification code can be associated with the doorbell. The Network Connection Mode can comprise using the doorbell identification code to verify whether the remotely located computing device is authorized to communicate with the doorbell. The Network Connection Mode can comprise the remotely located computing device creating a second wireless network (e.g., that emanates from the remotely located computing device). The Network Connection Mode can comprise transmitting the name and the password of the first wireless network directly from the remotely located computing device to the doorbell via the second wireless network to enable the doorbell to communicate with the remotely located computing device via the first wireless network. Methods can comprise the remotely located computing device directly communicating with the doorbell via the second wireless network prior to the doorbell indirectly communicating with the remotely located computing device via the first wireless network. For example, the wireless communication from the remotely located computing device can travel through the air directly to the doorbell. The wireless communication from the remotely located computing device can travel indirectly to the doorbell via a third electronic device such as a server.

FIG. 51 illustrates a communication system with two wireless networks 5556, 5560. The first wireless network 5560 can emanate from a router 5550. The second wireless network can emanate from the computing device 204 (e.g., a cellular telephone). The first wireless network 5560 can enable indirect wireless communication 5552 between the computing device 204 and the security system 202 via the router 5550 or via a server 206 (shown in FIG. 1). The second wireless network 5556 can enable direct wireless communication 5554 between the computing device 204 and the security system 202. The computing device 204 can send a password and a name of the first wireless network 5560 to the security system 202 via the second wireless network 5556. In some embodiments, the second wireless network 5556 does not require a password.

In some embodiments, a security system creates its own wireless network (e.g., WiFi network) with a recognizable network name (e.g., a service set identifier). Software can provide setup instructions to the user via a computing device, in some cases, upon detecting a new wireless network with the recognizable network name. The instructions can inform the user how to temporarily join the security system's wireless network with the computing device. The user can select and/or transmit the name and password of a target wireless network to the security system from the computing device. The security system can join the target wireless network (e.g., the wireless network of the building to which the security system is attached) and can terminate its own wireless network.

In some cases, the computing device can capture the name and password of the target network before joining the network of the security system. In some cases, the user enters the name and password of the target network into the computing device to enable the computing device to provide the name and password of the target network to the security system.

In some cases, the computing device recognizes the name of the network of the security system, automatically joins the network of the security system, and transmits the name and password of the target network to the security system. In some cases, these steps are preceded by launching software (on the computing device) configured to perform these steps and/or capable of performing these steps.

Methods can include the security system trying to joint an ad hoc network (or other wireless network) with a fixed network name or a network name based on an identifier of the security system (e.g., the serial number of the security system, the model number of the security system). The computing device can provide instructions to the user to temporarily setup the network (e.g., the ad hoc network) via the computing device. The network can have the fixed network name or the name based on the identifier. The security system can recognize the name and join the network. The computing device can use the network to transmit the name and password of a target network (e.g., the wireless network of the building to which the security system will be coupled) to the security system. The security system can use the name and password of the target network to join the target network.

In some embodiments, the computing device displays an image (e.g., a quick response code) that contains or communicates the name and password of the target network. The security system can use its camera and onboard software to scan and decode the image (to determine the name and password of the target network). The security system can use the name and password of the target network to join the target network.

The computing device can generate and display pulses of light (e.g., by flashing black and white images on the screen of the computing device). The security system can use its camera and software to analyze and decode the pulses of light. The pulses of light can contain the name and/or password of the wireless network. The security system can use the name and password of the target network to join the target network.

In some embodiments, only the password of the target network is given to the security system. The security system can use the password to test each detected wireless network until it identifies a wireless network to which it can connect using the password.

The computing device can generate and emit an audio signal that corresponds to the name and/or password of the target network. The security system can use its microphone and software to analyze and decode the audio signal to receive the name and/or password of the target network. The security system can use the name and password of the target network to join the target network.

In some embodiments, the computing device transmits the name and password of the target network to the security system via Morse code (e.g., using the doorbell button, using light pulses, using sound pulses).

In some embodiments, the security system can pair with the computing device via Bluetooth. The computing device can transmit the name and password of the target network to the security system (e.g., via Bluetooth). The security system can use the name and password of the target network to join the target network.

In several embodiments, the computing device transmits the name and/or password of the target network via infrared (“IR”) communication (e.g., IR light) to the security system. The computing device can emit the IR communication via IR LEDs or IR display emissions. An infrared emission device (e.g., with an IR LED) can be electrically coupled to the computing device to enable the computing device to send IR communications. The security system can detect the IR communication via IR sensors. The security system can use the name and password of the target network to join the target network.

The remotely located computing device 204 can be placed very close to the doorbell (e.g., security system 202) to configure the doorbell 202, but then can communicate with the doorbell 202 from remote locations (e.g., from another portion of the building to which the doorbell is attached, from across a city, from across a country, from across the globe). In some embodiments, the remotely located computing device 204 is communicatively coupled to the doorbell 202 via a wire to enable the remotely located computing device 204 to help configure the doorbell. In several embodiments, the remotely located computing device 204 creates a wireless network 5556 to help configure the doorbell 202 while the doorbell 202 is within a communication range of the wireless network 5556. Once the doorbell 202 is configured, the wireless network 5556 created by the remotely located computing device 204 may no longer be necessary because the doorbell 202 can communicate with the remotely located computing device 204 via another wireless network 5560, which can include the Internet and cellular networks.

Some embodiments include using a doorbell 202 that is configurable to wirelessly communicate with a remotely located computing device 204. Embodiments can include obtaining the doorbell 202 that comprises a speaker, a microphone, a camera, and a button. The doorbell 202 can be configurable to enable a visitor to sound a chime. Several embodiments include detecting a first indication of the visitor; using the doorbell 202 to send a wireless notification to the remotely located computing device 204 regarding the visitor; and entering a network connection mode prior to sending the wireless notification. The first indication (and other indications) can be detected using the doorbell (e.g., via a sensor of the doorbell, via data sent to the doorbell).

In several embodiments, the network connection mode comprises using the doorbell 202 to detect a first wireless network 5560. Using the doorbell 202 to detect the first wireless network 5556 can include the doorbell 202 sensing the first wireless network (e.g., by searching for wireless networks that are within range of the doorbell). The doorbell 202 can also detect the first wireless network 5560 via data sent to the doorbell 202 (e.g., from the remotely located computing device 204). In some embodiments, the doorbell 202 detects the first wireless network 5556 when the doorbell 202 connects to the first wireless network 5560. Thus, the term “detect” is used herein in a very broad sense and can include direct detection and indirect detection (e.g., via another computer).

The first wireless network 5560 can comprise a first name and a first password. The network connection mode can comprise the remotely located computing device 204 creating a second wireless network 5556. In some embodiments, the network connection mode comprises the remotely located computing device 204 transmitting the first password of the first wireless network 5560 directly from the remotely located computing device 204 to the doorbell 202 via the second wireless network 5556 to enable the doorbell 202 to communicate with the remotely located computing device 204 via the first wireless network 5560. The doorbell 202 can directly communicate with the remotely located computing device 204 via the second wireless network 5556 prior to the doorbell 202 indirectly communicating with the remotely located computing device 204 via the first wireless network 5560. In some embodiments, the doorbell 202 indirectly communicates with the remotely located computing device 204 via a server, the Internet, a cellular communication network, and/or a wireless router 5550 that is not physically coupled to the doorbell or to the remotely located computing device.

Some embodiments include using the doorbell 202 to detect a proximity indication of the remotely located computing device 204; determining if the proximity indication meets a predetermined proximity threshold such that the proximity indication indicates that the remotely located computing device 204 is sufficiently close to the doorbell 202; and connecting the doorbell 202 to the second wireless network 5556 in response to the proximity indication meeting the predetermined proximity threshold. The proximity threshold can be a certain value or characteristic. In several embodiments, a proximity indication can meet a predetermined proximity threshold if the remotely located computing device 204 is within a predetermined distance of the doorbell 202. The distance can be 100 feet, 50 feet, 20 feet, 10 feet, and/or 5 feet.

Referring now to FIG. 51, in several embodiments, the remote computing device 204 is connected via a cable 246 (shown in FIG. 1) to the security system 202. For example, a user can plug the cable 246 into the back or side of the security system 202 to setup the security system 202. Once connected by the cable 246, the remote computing device 204 can provide a password for the first wireless network 5560 to the security system 202 and/or can perform the functions described herein in the context of the second wireless network 5556. For example, in several embodiments, the data transmission via the cable 246 replaces the second wireless network 5556.

Initiating Communication

Referring now to FIG. 3, in some embodiments, multiple computing devices are candidates to receive information from a security system. For example, a person might initiate a communication request by pressing the doorbell button 212 (shown in FIG. 5) or triggering a motion or proximity sensor. The security system can notify multiple remotely located computing devices at once. The security system might simultaneously notify a smartphone of a first homeowner, a tablet of a housekeeper, and a laptop located inside the building to which the security system is connected. In some embodiments, once the doorbell ring is answered by one computing device, communication between the security system and the other computing devices is terminated, maintained, or kept open so another user can also participate in the communication. For example, if a housekeeper answers the communication request initiated by the doorbell ring, the homeowner might be unable to join the communication because communication with her computing device was terminated or might have the option to join the communication. In some embodiments, computing devices are assigned a priority and computing devices with a higher priority can terminate the communication of lower priority devices. For example, the homeowner could answer the communication request later than the housekeeper, but the homeowner could terminate the communication between the security device and the housekeeper's computing device. In some embodiments, users can forward communication requests from one computing device to another computing device.

In some embodiments, multiple computing devices are notified in series regarding a communication request. For example, the communication request might initially go to a first remote computing device, but if the communication request is not answered within a certain period of time, the communication request might go to a second remote computing device. If the communication request is not answered, the communication request might go to a third remote computing device.

FIG. 4 illustrates a communication system 310 that includes a security system 320, a doorbell button 324, a WiFi router 328, a server 332, and users 336. In step 340, a visitor initiates a communication request by pressing the doorbell button 324 or triggering a motion or proximity sensor. The visitor can trigger the motion or proximity sensor by approaching the security system 320. In step 350, the security system 320 connects or otherwise communicates with a home WiFi router 328. In step 360, the server 332 receives a signal from the WiFi router 328 and sends video and/or audio to the users 336 via a wireless network 364. In step 370, the users see the visitor, hear the visitor, and talk with the visitor. Step 370 can include using a software application to see, hear, and/or talk with the visitor. The visitor and users 336 can engage in two-way communication 374 via the internet or other wireless communication system even when the visitor and the users 336 are located far away from each other. Some embodiments enable users to receive communication requests and communicate with visitors via diverse mobile communication standards including third generation (“3G”), fourth generation (“4G”), long term evolution (“LTE”), worldwide interoperability for microwave access (“WiMAX”), and WiFi.

In some cases, the users 336 utilize the communication system 310 to communicate with visitors who are in close proximity to the users 336. For example, a user 336 located inside her home can communicate with a visitor located just outside the home via the communication system 310.

Referring now to FIG. 3, some embodiments include a location detection system (e.g., GPS) to determine if the computing device 204 is located inside the home, near the home, within 100 feet of the home, within 100 feet of the security system 202, within 50 feet of the home, and/or within 50 feet of the security system 202, in which case the computing device 204 is considered in Close Mode. In some embodiments, the computing device 204 is considered in Close Mode if the computing device 204 is connected to a wireless network 308 of the building to which the security system 202 is coupled. In several embodiments, the computing device 204 is considered in Close Mode if the computing device 204 and the security system 202 are connected to the same wireless network 308. If the computing device 204 is not in Off Mode and not in Close Mode, then the computing device 204 is in Away Mode, in which the computing device 204 is considered to be located remotely from the building 300.

In several embodiments, the computing device 204 can behave differently in Close Mode than in Away Mode. In some embodiments, the computing device 204 will not notify the user of visitors if the computing device 204 is in Close Mode. In several embodiments, Close Mode silences alerts, which can include precluding and/or eliminating the alerts. Instead, the user might have to listen for typical indications of a visitor such as the ring of a traditional doorbell. Once the computing device 204 enters Away Mode, the computing device 204 can notify the user of the visitor. In some embodiments, the computing device 204 notifies the user regarding the visitor if the computing device 204 is in Close Mode or Away Mode.

In several embodiments, the building's 300 doorbell chime is silenced when the computing device 204 is configured to alert the user. In some embodiments, the building's 300 doorbell chime emits sound and the computing device 204 is configured to alert the user.

In several embodiments, the user can decline a communication request by selecting via the user interface 240 a pre-recorded message to be played by the security system 202. The pre-recorded message can include audio and/or video content. Some embodiments can provide the user with options for playing a pre-recorded message on demand, and/or automatically playing a pre-recorded message under user-specified conditions. Examples of conditions that can be specified include time of day, user location, facial recognition or non-recognition of visitors, and/or number of recent visitors. In some embodiments, a pre-recorded message can interrupt two-way communications, which can resume after delivery of the message. In some embodiments, a pre-recorded message can be delivered without interrupting two-way communications.

In some embodiments, the security system 202 includes a memory 492 (shown in FIG. 11). If the security system 202 cannot communicate with the computing device 204 and/or with the server 206 (shown in FIG. 1), the memory 492 of the security system 202 can store a recorded message and/or video from the visitor. Once the security system 202 can communicate with the computing device 204 and/or the server 206, the security system 202 can communicate the recorded message and/or video to the computing device 204 and/or the server 206.

In several embodiments, the security system 202 can ask a visitor to record a message and/or can record pictures (e.g., video, still pictures) when the security system 202 cannot communicate via the wireless network 308. The security system 202 can include a Network Enabled Mode and a Network Disabled Mode. In the Network Enabled Mode, the security system 202 can communicate via the wireless network 308 with a remote server and/or computing device 204. In the Network Disabled Mode, the security system 202 cannot communicate via the wireless network 308 with a remote server and/or computing device 204.

In the Network Enabled Mode, the security system 202 can send video and/or audio from the visitor to the user instantaneously; nearly instantaneously; immediately; within 15 seconds of capturing the video and/or audio; and/or within 60 seconds of capturing the video and/or audio. In the Network Enabled Mode, the security system 202 can preferentially send data (e.g., video, audio, traits, identification) regarding the visitor to the computing device 204 rather than storing the data in the memory of the security system 202. In the Network Disabled Mode, the security system 202 can act as a typical doorbell by, for example, causing a chime inside the building 300 to emit a sound. In some embodiments of the Network Disabled Mode, the security system 202 emits a visible error signal (e.g., flashing light, red light); records images and audio to the security system's memory; asks the visitor to leave a message for the user; and/or alerts the user regarding the lack of wireless communication.

In some embodiments, the security system 202 can maintain a visitor log, which can capture information such as the date, time, audio, video, and/or images of the visitor. The user interface 240 can display this information in a “guest book” format; as a timeline or calendar; as a series of images, videos, and/or audio files; or as a log file.

Several embodiments include the ability to automatically record every visitor who comes to the door (e.g., even if the visitors do not “ring” the doorbell). Each visitor can be logged and “time stamped.” Visitor information can be stored in the cloud (e.g., a 15 second video of each visit can be stored remotely). The stored visitor information can also include recorded conversations and whether the visitor notification was “answered” by the user. Some methods include charging a periodic (e.g., monthly) subscription fee for storing and retrieving visitor history information. The visitor history information can include statistical analyzes and other high-level visitor metrics (e.g., average visits per month, average age of visitors, average visit duration, percentage of notifications that were answered, percentage of welcome visitors, percentage of solicitors).

The user can accept or decline a communication request from a visitor. In some embodiments, the user can push a button (e.g., 276) on the user interface 240 (shown in FIG. 2) to decline a communication request or accept a communication request. The user can decline a communication request without the visitor knowing that the user received the communication request. Prior to accepting a communication request, the computing device 204 can allow the user to click a button, such as an icon on a graphical user interface on a touch screen, to see and/or hear the visitor. In some embodiments, accepting a communication request includes opening a two-way line of communication (e.g., audio and/or video) between the visitor and the user to enable the user to speak with the visitor.

A visitor can initiate a communication request by ringing the doorbell of the security system 202, triggering a motion sensor of the security system 202, triggering a proximity sensor of the security system 202, and/or triggering an audio alarm of the security system 202. In some embodiments, the audio alarm includes the microphone of the security system 202. The security system 202 can determine if sounds sensed by the microphone are from a knocking sound, a stepping sound, and/or from a human in close proximity to the security system 202. The security system 202 can detect important sounds such as knocking, talking, and footsteps by recording the sounds and then computing features that can be used for classification. Each sound class (e.g., knocking) has features that enable the security system 202 to accurately identify the sound as knocking, talking, stepping, or extraneous noise. Features can be analyzed using a decision tree to classify each sound. For example, in some embodiments, a visitor can trigger an audio alarm (and thus, initiate a communication request) by knocking on a door located within hearing range of a microphone of the security system 202. In several embodiments, a visitor can trigger an audio alarm (and thus, initiate a communication request) by stepping and/or talking within hearing range of a microphone of the security system 202.

Hardware

FIG. 5 illustrates a front view of the security system 202, according to some embodiments. The security system 202 can include a camera assembly 208, which can be a fisheye camera and/or a camera located inside of a dome or spherical holder. The camera assembly 208 can be configured to allow the user or installer to adjust the orientation of the camera assembly 208 by moving an orientation feature 400. Adjusting the orientation of the camera assembly 208 can include inserting a manipulation tool, such as a pin, paperclip, or needle, into an orientation feature 400, which can be a hole, a cylindrical hole, a lumen, and/or a shaft. Once the manipulation tool is coupled to the orientation feature 400, the user or installer can move the camera assembly 208 like an eye can move in an eye socket.

A doorbell identification code 222 can be associated with the security system 202 (e.g., a doorbell) such that the code 222 is correlated with the doorbell. The code 222 can be used as an electronic key to unlock access to the doorbell. A Network Connection Mode can comprise using the doorbell identification code 222 to verify whether a computing device 204 (shown in FIG. 2) is authorized to communicate with the doorbell.

FIG. 6 illustrates a perspective view of the security system 202 from FIG. 5. The camera assembly 208 can include a fisheye lens 210, which can produce a visual distortion to create a wide panoramic or hemispherical image. The fisheye lens 210 can create a broader field of view than would be possible without a fisheye lens.

In some embodiments, a sensor 226 is hidden under the cover 404 (e.g., a light filter). The sensor 226 can be a motion sensor. In several embodiments, the sensor 226 is a proximity sensor. A light 1042 (e.g., a laser system), shown in FIG. 53, can be hidden under the cover 404.

In some embodiments, the camera assembly 208 is not configured to rotate and is not spherical. In several embodiments, the fisheye lens 210 can provide a sufficient field of view without moving the camera assembly 208. The fisheye lens 210 can be oriented directly outward from the outer housing 224 (e.g., perpendicular to an outward face of the outer housing 224) as shown in FIG. 7.

FIG. 56 illustrates a perspective view of a camera assembly 534 coupled directly to the PCB 450. Flexible conductors 438 (shown in FIG. 9) are not used to couple the camera assembly 534 to the PCB 450 in the embodiment illustrated in FIG. 56. The camera assembly 534 does not include a ball shape (e.g., a spherical shape) but can be cylindrical. The cylinder can include a front side that comprises a fisheye lens 536. The cylinder can include a backside that is coupled to the PCB.

The fisheye lens 536 can be a wide-angle lens configured to create a wider field of view than would result from a flat lens. The fisheye lens 536 can include a convex outer surface. The fisheye lens 536 can include a focal length of 2 millimeters to 16 millimeters. The fisheye lens 536 can include a horizontal field of view and/or a vertical field of view of at least 90 degrees, at least 100 degrees, at least 130 degrees, at least 160 degrees, and/or less than 190 degrees. In some embodiments, the fisheye lens 536 can include a horizontal field of view and/or a vertical field of view of at least 180 degrees. In several embodiments, the horizontal field of view is at least 30 degrees greater than the vertical field of view.

The PCB 450 can include a microphone 540, which can be mounted on a lower section of the PCB 450. In some embodiments, the PCB 450 includes an upper half that comprises the camera assembly 534, and the PCB 450 includes a lower half that comprises the microphone 540.

FIG. 7 illustrates a side view of the security system 202 from FIG. 5. The domed shape of the camera assembly 208 is visible in FIG. 7, although some embodiments include non-domed camera assemblies. The security system 202 can be a doorbell with a camera, microphone, speaker, and/or doorbell button coupled together in a single unit (e.g., at least partially inside an outer housing 224).

FIG. 8 illustrates a perspective view of the camera assembly 208. The camera assembly 208 can include a domed enclosure 430 and the orientation feature 400, which can be a hole. The camera assembly 208 can also include a lens 434, which can be transparent and/or translucent glass or plastic. The camera assembly 208 can be electrically coupled to other parts of the security system 202 by a flex circuit, wires, cables and/or flexible conductors 438. In some embodiments, the camera assembly 208 can be mounted directly to the PCB 450 (shown in FIG. 9) such that flexible conductors 438 are not used to electrically couple the camera assembly 208 to the PCB 450.

FIG. 9 illustrates a partial, perspective, cross-sectional view along line 9-9 from FIG. 5. The camera assembly 208 is secured between a cover 404 and a printed circuit board (“PCB”) 450. A front portion of the camera assembly 208 fits in a hole in the cover 404 and a back portion of the camera assembly 208 fits in a hole in the PCB 450. In some embodiments, a remote computing device can adjust the camera's viewing angle and zoom settings.

In some embodiments, the cover 404 (e.g., a light filter) is translucent to allow infrared (“IR”) light from IR light emitting diodes 458 (“LED”) to exit the security system 202 to illuminate visitors to enable nighttime video. In several embodiments, the cover 404 appears opaque or semi-opaque, but allows IR light to pass. In some embodiments, the cover 404 has a visible light transmission of at least 10% and/or less than 90%; at least 25% and/or less than 80%, or at least 35% and/or less than 75%. In some embodiments, the cover 404 has an IR light transmission of at least 30% and a visible light transmission of less than 90%; an IR light transmission of at least 40% and a visible light transmission of less than 80%; or an IR light transmission of at least 50% and a visible light transmission of less than 50%. In some embodiments, the cover 404 allows IR light to exit the security system but does not allow people to view into the security system in normal lighting conditions (i.e., 50 foot-candles).

Light sources, such as IR LEDs 458, can be located in an interior portion of a security system. The light sources can be oriented to within 30 degrees of the viewing orientation of the camera assembly 208 such that the light sources are configured to illuminate the camera's field of view and/or objects located in front of the camera assembly 208. The translucent or semi-translucent cover 404 can be located between the light sources and objects in front of the camera assembly 208. The cover 404 can be configured to obscure visibility into the interior portion of the security system 202. The cover 404 can be configured to enable light from the light sources to illuminate the camera's field of view and/or objects located in front of the camera assembly 208.

In some embodiments, a security system includes an outer housing and the outer housing includes a translucent or semi-translucent cover 404 configured to allow light from light sources to travel from an interior portion of the security system to an area in front of the security system (e.g., to an area outside of the security system). Light sources can be located beneath the cover 404 and can be oriented to emit light through the cover 404. In some embodiments, the cover 404 couples a camera assembly with the outer housing.

In some embodiments, a tube 454 leads from the orientation feature 400 (e.g., a hole in the outer surface of the camera assembly dome) to a microphone 452, 456 located inside of the security system 202 (e.g., on a printed circuit board). The microphone 456 can be located outside of the camera assembly on a printed circuit board. The microphone 452 can be located inside of the camera assembly (e.g., inside of the spherical assembly that houses at least a portion of the camera). The tube 454 can be configured to conduct sound and/or direct sound to a microphone 452, 456 located inside of the security system 202. The tube 454; microphones 452,456; and the orientation feature 400 are not included and/or indicated in some figures in the interest of clarity.

FIG. 10 illustrates a perspective, cross-sectional view along line 9-9 from FIG. 5. The security system 202 can include a battery 462, which can be rechargeable. Some embodiments include alkaline or lithium batteries. In some embodiments, the battery 462 can be a 3,500 mAh battery and/or a battery between 1,000 mAh and 5,000 mAh.

The lens 408 can allow light, such as IR light, to enter the security system 202 to enable an IR detector 470 to sense and/or detect the IR light. Several embodiments include the IR detector 470. The IR detector 470 can be used to determine if a visitor is near the security system 202 due to the unique IR signature and/or characteristics of people compared to non-living objects. The IR detector 470 can be a thermal or photonic IR detector. The system (e.g., 200 in FIG. 1) can be configured to distinguish between the IR characteristics of people and background IR characteristics. Thus, the system can determine if a visitor is in an entryway (e.g., in front of a door). The IR detector 470 can be a motion sensor.

In several embodiments, the IR detector 470 is a light detector, which can be used to distinguish day (i.e., light hours) from night (i.e., dark hours). In some embodiments, day versus night is distinguished based on time rather than light. The communication system 200 can have a Day Mode and a Night Mode, wherein Night Mode reduces, alters, or precludes alerts to the user.

Pressing the doorbell button 212 can activate a switch 474, which can cause a chime inside the building to emit a sound and/or can initiate a communication request to the user. In some embodiments, pressing the doorbell button 212 can trigger the system to record a fingerprint of the visitor. The lens 408 can be large enough to enable the security system 202 to take a picture (e.g., an IR image) of the visitor's finger. In some embodiments, the fingerprint is compared against a database of fingerprints to identify the visitor and/or to classify the visitor. Visitors in a welcome class (e.g., family, a person with permission to enter) can cause a door to open (e.g., the security system can unlock the door). In some embodiments, the button 212 is a fingerprint reader that can optically scan fingerprints when visitors touch a glass imaging window.

FIG. 11 illustrates a back view of the security system 202 from FIG. 5 without a mounting bracket 420. Security systems 202 can include a chip 480 (e.g., integrated circuits, microprocessor, computer) and a memory 492. Security systems 202 can also include a microphone 484 and a speaker 488. The speaker 488 can comprise a flat speaker and a sound chamber 460 configured to amplify an emitted sound. The flat speaker can be located in the sound chamber. Some security system embodiments include a proximity sensor 500. In several embodiments, security systems 202 include a wireless communication module 504, such as a WiFi module. The communication module 504 can have an integrated antenna. In some embodiments, an antenna is contained within the outer housing 224.

FIG. 12 illustrates a back view of the security system 202 from FIG. 5 with a mounting bracket 420. In some embodiments, the mounting bracket 420 is molded from plastic or machined from metal, such as aluminum. The mounting bracket 420 can include screw holes 412, which can be slots configured to allow a threaded portion of a screw to pass, but not allow the head of the screw to pass. A wire hole 416 can be located in the center of the mounting bracket 420. Referring now to FIGS. 3 and 12, electrical wires 304 from the building 300 can pass through the wire hole 416 and couple to electrical connectors 510 (shown in FIG. 11).

FIG. 13 illustrates a perspective view of the outer housing 224 from FIG. 5. The outer housing 224 can include grooves 514 that extend radially outward from the central axis of the outer housing 224. The grooves 514 can be located on an inner diameter and/or inner surface of the outer housing 224, which can be part of a doorbell. Some embodiments include one continuous groove along an inner surface while other embodiments include separate grooves (such as the grooves illustrated in FIG. 13). Separate grooves can help control the angular orientation of the doorbell when it is mounted to a wall.

FIG. 14 illustrates a front view of the mounting bracket 420 coupled (e.g., screwed) to a wall. Screws 522 can be used to couple the mounting bracket 420 to a wall of a building, structure, and/or enclosure.

The mounting bracket 420 can have protrusions 518 that can extend radially outward from the mounting bracket 420. The protrusions 518 can be configured to fit inside the grooves 514 as shown in the dashed box of FIG. 9. Flex zones 526 (e.g., holes, open areas, slots, flexible material) can be located radially inward from the protrusions 518. The flex zones 526 can allow the protrusions 518 to moves radially inward as the outer housing 224 is pushed onto the bracket 420 (e.g., when the bracket is mounted to a wall).

Referring now to FIGS. 13 and 14, moving radially inward can help the protrusions 518 clear lips 530 associated with the grooves 514. The lips 530 can be located closer to the back side of the outer housing 224 or doorbell than the grooves 514 such that, in some embodiments, the lip 530 moves past the protrusion 518 before the protrusion 518 reaches the groove 514. The lips 530 can extend further radially inward than the grooves 514. In some embodiments, the outer housing 224 is configured to flex radially outward (e.g., at least in areas within 1 centimeter of the lips 530 and/or grooves 514) to enable the lips 530 to clear (e.g., snap over, move beyond) the protrusions 518.

FIG. 15 illustrates a partial, side view of the mounting bracket 420. The protrusions 518 can have a first side 550, which can be a front side (i.e., configured to be mounted facing away from a wall of a building). The protrusions 518 can have a second side 554, which can be a back side (i.e., configured to be mounted facing towards a wall of a building). In some embodiments, the first side 550 of the protrusion 518 includes a rounded or chamfered edge to facilitate pushing the outer housing 224 onto the bracket 420 to create a snap fit.

In some embodiments, the outer housing 224 includes protrusions that extend radially inward and the bracket 420 includes grooves and/or indentations that extend radially inward to capture the protrusions of the outer housing 224. In some embodiments, the outer housing 224 snaps onto the bracket 420. In several embodiments, the outer housing 224 is coupled to the bracket by threads (e.g., screws with threads, threads along the outer perimeter of the bracket).

Referring now to FIGS. 13-15, the outer housing 224 can lock onto the bracket 420 to reduce the likelihood of theft. The outer housing 224 and bracket 420 can be configured such that mounting means (e.g., protrusions 518, screws 522) are hidden when the outer housing 224 is coupled to the bracket 420. In some embodiments, the outer housing 224 covers coupling members (e.g., protrusions 518, screws 522) when the outer housing 224 is coupled to the bracket 420.

Methods of Use

FIG. 16 illustrates a method of using a security system, according to some embodiments. The illustrated method includes optional steps. In some embodiments, the steps can be performed in orders different than the order illustrated. In at least one embodiment, at least some of the steps are performed in the order illustrated in FIG. 16.

Step 600 can include removing a first doorbell from a wall (e.g., the wall of a building). The first doorbell can be a traditional doorbell without a camera. Step 604 can include decoupling electrical wires (e.g., 304 in FIG. 3) from the first doorbell. Step 608 can include passing the electrical wires through a hole (e.g., 416 in FIG. 14) in a bracket or mounting device. Step 612 can include coupling (e.g., screwing, fastening) the bracket to the wall. Step 616 can include electrically coupling a second doorbell (e.g., 202 in FIG. 1) to the electrical wires. The second doorbell can be a security system, such as a security system 202 illustrated in FIG. 3. The second doorbell can include a camera (such as a video camera), a speaker, a microphone, and/or a wireless communication assembly. Step 620 can include coupling the second doorbell to the bracket.

Step 624 can include using the electrical wires to provide electrical power to a speaker, microphone, and/or camera located at least partially inside of the second doorbell. Step 628 can include using a first computing device (e.g., mobile computing device, smartphone, laptop, desktop, tablet) to connect the second doorbell to a wireless network. Step 632 can include using a motion sensor, proximity sensor, audio sensor, and/or button located at least partially inside of the second doorbell to detect at least one visitor. The visitor can be a person who approaches the second doorbell and/or rings the second doorbell.

Step 636 can include sending information regarding the visitor (e.g., the presence of the visitor, doorbell ring, video, audio) to a second computing device (e.g., a remotely located computing device), which can be the first computing device. Step 640 can include opening a means for two-way communication between the visitor and a user of the second computing device. The means for two-way communication can enable the user to talk with the visitor and/or see the visitor via a wireless network, a cellular network, and/or the Internet.

Modes of Operation

FIG. 17 illustrates methods of using a security system, according to some embodiments. The steps can be performed by a security system and/or by a remotely located server and/or computer. In some embodiments, all of the steps shown in FIG. 17 are performed by a security system (e.g., a doorbell). In some embodiments, Steps 700, 704, 708, 712, 716, 720, and/or 724 are performed by a security system (e.g., a doorbell). In some embodiments, Steps 720, 724, 728, 732, 736, 740, 744, and/or 748 are performed by at least one remote server and/or at least one remote computing system. The steps can be performed in many different orders.

Some embodiments include a Shipping Mode, which can be an ultra-low power mode (e.g., can use even less power than a Sleep Mode). Wireless communication (e.g., WiFi communication, communication module 504 in FIG. 11) can be disabled during Shipping Mode. The camera, motion detector, sound detector, microphone, infrared sensors, infrared lights, infrared components, thermometer, heating element, and/or proximity sensor can be disabled during Shipping Mode. During Shipping Mode, the security system (e.g., 202 in FIG. 11) can be configured to detect whether the security system is electrically coupled to an external power source (e.g., electricity from a building or home). If the security system detects that the security system is electrically coupled to an external power source, then the security system can be configured to exit Shipping Mode and enter another mode (e.g., Sleep Mode, Standby Mode, Detection Mode, Alert Mode). In some embodiments, a security system enters Sleep Mode once the security system exits Shipping Mode. Step 692 can include entering a Shipping Mode. Step 696 can include detecting external power. Methods can include exiting a Shipping Mode and/or entering a Sleep Mode in response to detecting external power (e.g., power from outside of the security system).

Step 700 can include entering a Sleep Mode. In some embodiments, Sleep Mode has lower power consumption than Standby Mode and/or Alert Mode. In several embodiments, Sleep Mode turns off, powers down, and/or reduces the activity of one or more components and/or assemblies. In some embodiments, the camera is off, not recording, and/or in Low Power Mode while the system is in Sleep Mode. In some embodiments, the speaker is off, not recording, and/or in Low Power Mode while the system is in Sleep Mode. In several embodiments, the microphone is off, not recording, and/or in Low Power Mode while the system is in Sleep Mode.

Step 704 can include detecting motion, proximity, and/or noise. Step 708 can include exiting the Sleep Mode and entering a Standby Mode. Step 712 can include detecting motion, proximity, noise, and/or button contact. Step 716 can include entering an Alert Mode.

In some embodiments, thresholds necessary to exit the Sleep Mode and enter a Standby Mode are less than thresholds necessary to exit the Standby Mode and enter an Alert Mode. In several embodiments, greater motion, closer proximity, and/or louder noise are necessary to enter an Alert Mode than are necessary to exit the Sleep Mode and enter a Standby Mode. In some embodiments, button contact is necessary to enter an Alert Mode. In some embodiments, a system will exit the Sleep Mode and enter a Standby Mode upon detecting motion, detecting motion within 10 feet, or detecting motion within 20 feet. In some embodiments, a system will exit the Sleep Mode and enter a Standby Mode upon detecting sound, upon detecting sound louder than 10 decibels, upon detecting sound louder than 25 decibels, upon detecting sound louder than 50 decibels, upon detecting sound louder than 80 decibels, or upon detecting sound louder than 90 decibels.

In several embodiments, Standby Mode turns on, powers up, and/or increases the activity (e.g., electrical activity, detection activity, detecting) of one or more components and/or assemblies (relative to Sleep Mode). In some embodiments, the camera is on, recording, and/or in an Intermediate Power Mode while the system is in Standby Mode. In some embodiments of Standby Mode, the camera is configured to quickly start recording, but is not recording. In several embodiments of Standby Mode, the microphone is on, in Detection Mode, and/or detecting sounds to help the system determine if it should change to Alert Mode.

In several embodiments, the system takes a picture when the system enters Standby Mode. In some embodiments, the system takes a picture each time a visitor is detected even if the visitor does not ring the doorbell.

In some embodiments of Alert Mode, the system has determined that a visitor is present and/or attempting to contact a person in the building (e.g., the visitor is ringing a doorbell, waiting by the doorbell, knocking on a door). Some embodiments go into Alert Mode even if the visitor is not trying to contact a person in the building (e.g., the visitor could be a person trying to break into the building). The system can be configured to enter Alert Mode if the system detects a visitor within 20 feet, within 10 feet, or within five feet. The system can be configured to enter Alert Mode if the system detects a sound greater than 50 decibels, 80 decibels, and/or 90 decibels. The system can be configured to enter Alert Mode if a visitor presses a doorbell button and/or triggers a proximity sensor.

The system can be configured to block or allow a communication request (as shown in Steps 720 and 724). The user might want to block communication requests because she is busy or asleep. The user can configure the system to autonomously and/or automatically block communication requests (e.g., a visitor ringing the doorbell would not initiate a communication request to the user). In several embodiments, the system that blocks or allows a communication request can be the doorbell (e.g., 202 in FIG. 1), a computing device (e.g., 204 in FIG. 1), or a remote server (e.g., 206 in FIG. 1).

If the communication request is allowed, the system can send the communication request via Simultaneous Mode as illustrated in Step 728. Simultaneous Mode can include sending the communication request simultaneously to at least two computing devices (e.g., computing devices 204 in FIG. 3). The request can be sent simultaneously even if the communication requests are not initiated at the same moment as long as the communication requests overlap in at least one moment of time. In some embodiments, if a first user does not respond to a first communication request to a first computing device, the system can send a second communication request to a second computing device while the first communication request is still underway. As a result, the system starts by sending the communication request to the first user, but then simultaneously sends communication requests to both the first user and a second user.

Step 732 can include assigning priorities to remote computing devices. In some embodiments, a computing device with a higher priority will receive a communication request before a computing device with a lower priority. In several embodiments, a computing device and/or user with higher priority will have privileges that are not available to a computing device and/or user with a lower priority. These privileges can include administrative abilities and the ability to alter settings.

Step 736 can include sending the communication request to a first remote computing device with the first highest priority. Step 740 can include determining whether to send the communication request to a second computing device with the second highest priority. Step 744 can include sending the communication request to the second remote computing device with the second highest priority.

Step 748 can include determining whether to enter an Autonomous Answer Mode. Autonomous Answer Mode can include methods of the security system, server, and/or remote computing device interacting with the visitor without user action. For example, if a user does not respond to a communication request, the system can play a recorded message, provide pre-recorded instructions from the user to the visitor, and/or request the visitor to leave a message for the user (e.g., an audio message, a video message).

A notification regarding the presence of a visitor can be sent (e.g., simultaneously) to multiple remote computing devices that have been authorized to communicate with a security system 202 (shown in FIG. 1). A first user can answer a push notification regarding the presence of a visitor to start two-way communication with the visitor at door (e.g. located near the security system 202). Then, another user (who also received the push notification regarding the visitor) can also join the conversation (e.g., without any interaction from the first person). Thus, all three parties can talk simultaneously, and the two users can simultaneously see the visitor. This three-way communication can be enabled via administrative settings by authorizing multiple, specific remote computing devices 204 to communicate with one security system 202. In some embodiments, the users who can join the communication are limited to the users of remote computing devices on the account associated with the security system 202.

In some embodiments, the Autonomous Answer Mode includes sending the communication request to an answering service such as a call center. An operator at the answering service can speak with the visitor, provide instructions to the visitor, and/or take a message from the visitor.

In several embodiments, the user can select a pre-recorded message for the security system to play for the visitor. The security system can play the pre-recorded message for the visitor by emitting the audio message from the speaker. Once the visitor has responded to the pre-recorded message, the user can initiate two-way communication with the visitor. In one embodiment, the pre-recorded message asks the visitor to identify herself and/or to describe her reason for being at the building. The user can listen to the visitor's response before opening two-way communication with the visitor and/or letting the visitor know that the user is listening to the visitor and/or watching the visitor.

FIG. 52 illustrates methods of using a security system (e.g., a doorbell), according to some embodiments. Step 1002 can include obtaining a doorbell that comprises a speaker, a microphone, a camera, a battery, and a button. Step 1006 can include shipping a doorbell in a Shipping Mode. The Shipping Mode can be configured to detect whether the doorbell is electrically coupled to an external power source. Step 1010 can include entering a Setup Mode. Some methods include entering a Setup Mode in response to detecting electricity from an external power source. Step 1014 can include entering a Standby Mode. Several methods include entering a Standby Mode in response to detecting electricity from an external power source. Step 1018 can include entering a Network Connection Mode. Some methods include entering a Network Connection Mode in response to pressing a button of the doorbell for a period of time. Some methods include entering a Network Connection Mode in response to detecting electricity from an external power source. Step 1022 can include entering an Alert Mode. Several methods include entering an Alert Mode in response to detecting an indication of a visitor. Step 1026 can include sending a wireless notification to the remotely located computing device regarding a presence of the visitor. FIG. 52 includes optional steps and steps that can be combined with portions of other methods. The steps can be performed in many different orders.

Methods can include using a doorbell that is configurable to wirelessly communicate with a remotely located computing device, such as a cellular telephone, laptop, or tablet. Some embodiments include obtaining a doorbell that comprises a speaker, a microphone, a camera, and a button. The button can be configurable to enable a visitor to sound a chime (e.g., a speaker or another sound emission device located inside of a building). Several embodiments include shipping the doorbell in a Shipping Mode that consumes power. In the Shipping Mode, the doorbell can detect whether the doorbell is electrically coupled to an external power source (e.g., the electricity of a building to which the doorbell is attached). Methods can then include entering a Network Connection Mode in response to detecting electricity from the external power source. The Shipping Mode can consume less power than the Network Connection Mode. The Network Connection Mode can comprise detecting a wireless network (e.g., a wireless network emitted by a router). Several methods include detecting a first indication of the visitor using the doorbell.

Methods for using a doorbell that is configurable to wirelessly communicate with a remotely located computing device can include obtaining the doorbell that comprises a speaker, a microphone, a camera, and a button. The button can be configured to enable a visitor to sound a chime. Some methods include shipping the doorbell in a Shipping Mode that consumes power. During the Shipping Mode, the doorbell can be configured to detect whether the doorbell is electrically coupled to an external power source. Methods can include entering a Setup Mode in response to detecting electricity from the external power source. The Shipping Mode can consume less power than the Setup Mode. The Setup Mode can increase electrical activities of the doorbell relative to the Shipping Mode. Some embodiments include increasing the electrical activities of the communication module, circuit board, battery, microphone, speaker, and/or camera. Some embodiments include detecting a first indication of the visitor. The first indication can be detected using the doorbell.

The remotely located computing device can be a cellular telephone having a display screen. Methods can comprise sending an image of the visitor from the doorbell to the cellular telephone and displaying the image of the visitor on the display screen of the cellular telephone.

Some embodiments comprise detecting a second indication of the visitor, wherein the second indication is detected using the doorbell. Several methods comprise sending a wireless notification to the remotely located computing device regarding a presence of the visitor in response to detecting both the first indication and the second indication.

In some embodiments, detecting the first indication comprises detecting a signal indicative of the visitor above a first threshold and detecting the second indication comprises detecting the signal indicative of the visitor above a second threshold. In some embodiments, the second threshold is greater than the first threshold. The doorbell can comprise a first sensor. The signal indicative of the visitor can be sensed by the first sensor of the doorbell.

In several embodiments, the first sensor of the doorbell comprises a motion sensor and the signal is related to motion. The camera, the speaker, and/or the microphone can be disabled during the Setup Mode.

The first sensor of the doorbell can comprise a proximity sensor. The signal can be related to proximity of the visitor.

The first sensor of the doorbell can comprise a microphone. The signal can be related to sound. In some embodiments, detecting the second indication comprises detecting a knocking sound.

In several embodiments, a doorbell comprises a first sensor and a second sensor. The first indication can be detected using the first sensor and the second indication can be detected using the second sensor. The first sensor can be a different type of sensor than the second sensor.

In some embodiments, the first sensor of the doorbell comprises a motion sensor. The second sensor can comprise the microphone. Methods can comprise using the microphone to detect a knocking sound to verify the presence of the visitor detected by the motion sensor.

In several embodiments, the first sensor of the doorbell can comprise an infrared detector and the second sensor can comprise the camera.

In some embodiments, the doorbell comprises a battery. The Setup Mode can comprise automatically charging the battery in response to detecting the electricity from the external power source.

In some embodiments, the Setup Mode comprises automatically replenishing at least a portion of electrical energy consumed from the battery by the doorbell during the Shipping Mode. Methods can comprise precluding wireless communication by the doorbell until after replenishing the portion of the electrical energy and then entering a Network Connection Mode in response to pressing the button for at least eight seconds. Pressing the button for at least eight seconds can help the doorbell distinguish between when the user just wants to sound the chime and when the user wants the doorbell to enter the Network Connection Mode. The Network Connection Mode can comprise detecting a wireless network.

In several embodiments, the doorbell comprises a battery and the Setup Mode comprises using the electricity from the external power source to charge the battery before enabling communication between the doorbell and the remotely located computing device.

In some embodiments, the Setup Mode comprises a Network Connection Mode, and the method comprises entering the Network Connection Mode in response to pressing the button for at least eight seconds. The Network Connection Mode can comprise detecting a wireless network and inputting a doorbell identification code into the remotely located computing device. In some embodiments, inputting the doorbell identification code includes typing letters, numbers, words, and/or symbols on the remotely located computing device. Inputting the doorbell identification code can include speaking letters, numbers, words, and/or symbols such that the remotely located computing device hears the information and captures the information.

The doorbell identification code can be associated with the doorbell such that the code is correlated with at least one doorbell. The code can be used as an electronic key to unlock access to the doorbell. The Network Connection Mode can comprise using the doorbell identification code to verify whether the remotely located computing device is authorized to communicate with the doorbell. For example, the code can prevent an unauthorized computing device from hacking into the doorbell and receiving visitor alerts from the doorbell.

In several embodiments, the Network Connection Mode comprises enabling communication from the remotely located computing device to the doorbell in response to pressing the button for at least eight seconds and inputting the doorbell identification code into the remotely located computing device. Pressing the button for at least eight seconds can help the doorbell distinguish between when the user just wants to sound the chime and when the user wants to enable communication from the remotely located computing device to the doorbell.

In some embodiments, the remotely located computing device is connected to the wireless network such that the remotely located computing device is configured to transmit data via the wireless network. The wireless network can comprise a name and a password. The name can identify the wireless network to entities searching for wireless networks. The password can enable an electronic device to connect to the wireless network. The wireless network can enable electronic devices to connect to the Internet.

The communication from the remotely located computing device to the doorbell can comprise the name and the password of the wireless network to which the remotely located computing device is connected. The Network Connection Mode can comprise connecting the doorbell to the wireless network to which the remotely located computing device is connected such that the doorbell can send an alert regarding a presence of the visitor to the remotely located computing device via the wireless network.

Some embodiments include using the doorbell to detect multiple wireless networks. The wireless network to which the remotely located computing device is connected can be one of the multiple wireless networks. Methods can comprise automatically selecting the wireless network to which the remotely located computing device is connected. For example, the system can choose which wireless network to connect the doorbell without asking a person which wireless network the system should choose.

A remotely located computing device can be located near a doorbell. For example, during setup some users will hold a cellular phone within a couple of feet from the doorbell to input a doorbell identification code into the cellular phone to verify that the phone is authorized to communicate with the doorbell and to help the doorbell connect to a wireless network. The phone is located remotely from the doorbell because it is not physically attached to the doorbell.

Several methods include using a doorbell that is configurable to wirelessly communicate with a remotely located computing device. Methods can include shipping the doorbell in a Shipping Mode that consumes power. During some Shipping Mode embodiments, the doorbell is configured to detect whether the doorbell is electrically coupled to an external power source. Several embodiments include entering a Standby Mode in response to detecting electricity from the external power source. The Shipping Mode can consume less power than the Standby Mode. The speaker and the microphone can be disabled during the Standby Mode.

Some embodiments include exiting the Standby Mode and entering an Alert Mode in response to detecting a first indication of the visitor. The first indication can be detected using the doorbell. Several embodiments include sending a wireless notification to the remotely located computing device regarding a presence of the visitor in response to entering the Alert Mode.

Some embodiments comprise detecting multiple wireless networks and automatically selecting a first wireless network for communicating between the doorbell and the remotely located computing device. Prior to the automatic selection, the remotely located computing device can be connected to the first wireless network. Methods can further comprise authorizing the doorbell to communicate with the remotely located computing device by pressing the button for at least eight seconds and inputting a doorbell identification code into the remotely located computing device. The doorbell identification code can be associated with the doorbell. The first wireless network can comprise a name and a password. Methods can further comprise wirelessly communicating the name and the password from the remotely located computing device to the doorbell.

Several methods include entering a Network Connection Mode prior to sending the wireless notification. The Network Connection Mode can comprise detecting a first wireless network having a name and a password. The Network Connection Mode can comprise inputting a doorbell identification code into the remotely located computing device. The doorbell identification code can be associated with the doorbell. The Network Connection Mode can further comprise using the doorbell identification code to verify whether the remotely located computing device is authorized to communicate with the doorbell. The Network Connection Mode can comprise the remotely located computing device creating a second wireless network. The Network Connection Mode can comprise transmitting the name and the password of the first wireless network directly from the remotely located computing device to the doorbell via the second wireless network to enable the doorbell to communicate with the remotely located computing device via the first wireless network. Methods can comprise the doorbell directly communicating with the remotely located computing device via the second wireless network prior to the doorbell indirectly communicating with the remotely located computing device via the first wireless network.

Entering the doorbell's identification code via typing can be cumbersome and prone to user error. In some embodiments, each security system 202 (or any other type of smart device) can come with a barcode (e.g., a matrix barcode such as a Quick Response Code). This barcode can be on a sticker on the security system 202 (e.g., on the backside), can be laser etched onto device, and/or can be included in materials shipped with the security system 202 (e.g., in an instruction manual). The remote computing device 204 (e.g., shown in FIG. 1) can include software (e.g., an “app”) configured to scan the barcode to receive the doorbell identification code and/or other setup data.

In some embodiments, the barcode or other image configured to be scanned has limited data transmission ability. For example, some barcodes only communicate a number. In some embodiments, the remote computing device contacts a remote computer (e.g., a server) and provides information from the barcode to the remote computer. Then, the remote computer can use the information from the barcode to authorize providing more detailed information to the remote computing device. In some embodiments, the remote computer uses a database to find information associated with the information from the barcode. In several embodiments, the remote computer can pass the more detailed information to the remote computing device in response to the remote computing device providing data from the barcode or other image located on the security system (e.g., a doorbell).

In several embodiments, the barcode or other image on the security system can replace the doorbell identification code. For example the barcode or other image can be used to determine that the remote computing device is authorized to setup and/or control features, functions, and/or communications of the security system.

In some embodiments, the barcode communicates the doorbell identification code to the remote computing device. The remote computing device can use its camera to take a picture of the barcode. The remote computing device can then analyze the picture to “read” the barcode.

In some cases, barcodes include information helpful to connect security systems and/or remote computing devices to Wi-Fi networks. For example, network passwords and names can be embedded in images (e.g., barcodes).

Network Congestion

In some cases, communication networks might be unable to transmit data at sufficient rates between a security system 202 and a remote computing device 204. Network congestion can occur when a link or node is carrying too much data, which can result in the deterioration of the quality of communication services. Several embodiments include methods to address network congestion and low data transmission rates.

FIG. 18 illustrates a data prioritization method, according to some embodiments. FIG. 18 includes optional steps and steps that can be performed in any order. Step 800 can include determining if a data transmission rate is insufficient to avoid communication issues (e.g., delayed transmission, blocked transmission). For example, a data transmission rate between a security system 202 and a computing device 204 can be insufficient if audio and/or video is not transmitted reliably, is transmitted intermittently, and/or the video data is transmitted more than 0.2 seconds after the audio data. If the data transmission rate is insufficient, the method can include means to address the problem, and then can include determining if the means to address the problem resolved the insufficiency. If the insufficiency is not resolved, the method can include using another means to address the problem, and then can include determining if the second means to address the problem resolved the insufficiency. The method can include using additional means to address the insufficiency until the data transmission rate is sufficient to avoid communication issues.

Several embodiments include prioritizing audio data over image data (e.g., video data), which is included in FIG. 18 as Step 804. Methods can include determining if a data transmission rate is insufficient to avoid communication issues. If the data transmission rate is insufficient to avoid communication issues, the method can include adding and/or using priority information (e.g., control information, header information) regarding the type of service (e.g., quality of service) to audio data and/or video data (e.g., payload data). The method can also include making the priority information for audio data higher than the priority information for video data.

Some embodiments include making the priority information for a picture (e.g., a still image) of the visitor higher than the priority information for a video of the visitor. Some embodiments include making the priority information for audio of the visitor higher than the priority information for the picture of the visitor and/or higher than the priority information for the video of the visitor. Some embodiments include making the priority information for audio of the user (e.g., the user of the computing device 204 in FIG. 1) higher than the priority information for the audio of the visitor.

Step 808 can include reducing the resolution of images transmitted to a computing device. Step 812 can include reducing the number of frames per second transmitted to the computing device. Step 816 can include switching from a Video Mode to a Snapshot Mode. The Snapshot Mode includes sending at least one still image (not more than every 0.3 seconds). Step 820 can include switching from a Picture Mode (e.g., the Video Mode, the Snapshot Mode) to an Audio Mode. In the Audio Mode, no videos or pictures are sent to the computing device (e.g., 204 in FIG. 1).

Following Mode

Referring now to FIGS. 2 and 5, in some embodiments, allowing the user to see the visitor can be important to facilitate quality interaction with the visitor or to identify the visitor. In some embodiments, the camera assembly 208 moves to point towards the visitor (e.g., moves towards the center the motion detected by the motion detector, moves towards the center of an IR signal indicative of a human temperature, moves as controlled by the user via a computing device 204).

In several embodiments, the image 252 is a portion of the image captured by the camera assembly 208. The image captured by the camera assembly 208 is the camera's field of view (“FOV”) 840 (as shown in FIGS. 19 and 20). The image 252 can be a portion of the camera's FOV 840 that includes the visitor (as detected by the motion sensor, IR sensor, machine vision, and/or facial recognition software).

Referring now to FIGS. 2, 19, and 20, the portion of the camera's FOV 840 that is shown on the computing device 204 (e.g., in the image 252) is the displayed portion 848a,b. The communication system can be configured such that the displayed portion 848a,b includes the visitor 844 even when the visitor 844 moves from a first position (as illustrated in FIG. 19) to a second position (as illustrated in FIG. 20) within the camera's FOV 840. In some embodiments, the camera's FOV 840 is maintained (i.e., doesn't change) even though the displayed portion 848a,b changes. The method of displaying a portion that includes a visitor is called Following Mode.

In some embodiments, the user can select characteristics of the portion of the camera's FOV 840 that is shown on the computing device 204. These characteristics can include a Face Mode, wherein the displayed portion 848a,b includes less than 90% of the FOV 840 but at least 40% of the displayed portion 848a,b shows the visitor's head, at least 30% of the displayed portion 848a,b shows the visitor's head, or at least 15% of the displayed portion 848a,b shows the visitor's head. These characteristics can include a Body Mode wherein the image 252 includes less than the entire FOV 840 or less than 80% of the FOV 840 but includes at least 80% of the body of the visitor, at least 50% of the body of the visitor, or at least 30% of the body of the visitor. These characteristics can include a Group Mode wherein the image 252 includes less than the entire FOV 840 or less than 80% of the FOV 840 but includes at least a portion of each of two visitors (if present), at least a portion of each of three visitors (if present), at least at portion of the majority of each of the visitors, at least 30% of all of the visitors, or at least the heads of all of the visitors. Once the user sets Face Mode, Body Mode, or Group Mode, the system automatically shows the portion of the FOV 840 described above in the image 252 without the user having to manually zoom.

FIG. 21 illustrates a method of displaying a visitor, according to some embodiments of Following Mode. Step 860 can include detecting the presence of a visitor. Step 864 can include recording an image with a security system. Step 868 can include identifying a portion of the image that includes the visitor. Step 872 can include displaying the portion on a remote computing device.

FIG. 22 illustrates a method of displaying a visitor, according to some embodiments of Following Mode. Step 880 can include detecting the presence of a visitor. Step 884 can include recording (e.g., filming, taking, sensing even if not stored in memory) a first image with a security system. Step 888 can include identifying a first location of the visitor within the first image at a first time. Step 892 can include displaying a first portion of the first image, wherein the first portion includes at least a portion of the first location. Step 896 can include recording a second image with the security system. Step 900 can include identifying a second location of the visitor within the second image at a second time. In some embodiments, the first image and the second image have the same FOV. Some methods include maintaining the camera's field of view between the first image and the second image. Step 904 can include displaying a second portion of the second image, wherein the second portion includes at least a portion of the second location. Displaying can include displaying an image on a computing device (e.g., 204 in FIG. 2).

Additional Devices

Communication systems can include additional devices, can work in conjunction with additional devices, and/or can communicate with additional devices. In some embodiments, the additional devices (e.g., chimes as described previously) are part of the communication system. In some embodiments, the additional devices are not part of the communication system.

Referring now to FIG. 23, additional devices can include chimes 910, speakers 914, and lights 918, 922. In some embodiments, a communication system causes an exterior light 918 (e.g., a porch light) and/or an interior light 922 (e.g., a lamp, overhead lights inside of a home) to illuminate when the security system 202 detects a visitor (e.g., when a visitor pushes the doorbell button).

Some embodiments include a speaker 914 located inside of the building. The user's voice can be emitted from the speaker 914 located inside of the building to make the visitor believe the user is speaking from inside the building (even when the user is located far away from the building and speaking into a remote computing device such as a smartphone). The security system 202 can transmit the user's audio information to the speaker 914 located inside of the building via wireless communication means such as Bluetooth.

In some embodiments, the security system 202 wirelessly communicates with a chime 910 located inside of the building. In some embodiments, the security system sends information or signals to a chime 910 via wires.

In several embodiments, the security system 202 wirelessly communicates with a garage door opener 926, which can be located inside of the building and configured to open a garage door of the building. The user can instruct the garage door to open via a user interface on a remote computing device 204a. The remote computing device 204a can communicate with the security system 202, which can wirelessly communicate the command to the garage door and/or garage door opener 926.

In several embodiments, the security system 202 communicates with a door lock 930 (e.g., a deadbolt). The user can instruct the door lock 930 to open via a user interface on a remote computing device 204a. The remote computing device 204a can communicate with the security system 202, which can communicate the command to the door lock 930. In some embodiments, the user can “buzz” someone into an apartment complex via an app on a computing device such as a smartphone.

In several embodiments, the security system 202 communicates with a gate opener 934 (e.g., an electric or robotic gate opener configured to unlock and/or open a gate, such as a gate to an apartment complex or a gate that blocks an entrance to a driveway).

As illustrated in FIG. 23, a first remote computing device 204a can send commands to and/or receive information from devices (e.g., chimes 910, speakers 914, exterior lights 918, interior lights 922, garage door openers 926, door locks 930) via a security system 202, which can include a doorbell. The security system 202 can communicate with a second remote computing device 204b.

In some embodiments, the first remote computing device 204a can communicate information regarding the security system 202 with the second remote computing device 204b. The information regarding the security system 202 communicated between remote computing devices can be any of the information described herein.

In several embodiments, the first remote computing device 204a forwards information from the security system 202 to a third remote computing device 204c and/or to an alert device 938. The alert device 938 can be any device configured to alert a user or person. In some embodiments, the alert device 938 is a watch that vibrates or displays a message to a user. In some embodiments, the alert device 938 is an alarm system.

In some embodiments, the software and/or user interface of a first computing device 204a allows the user to forward the communication request to a second computing device 204b and/or to a third computing device 204c. For example, a user might see that the visitor is a friend of the user's child. The user can then forward the communication request to the child's computing device with or without answering the communication request. In some embodiments, once a communication request is forwarded to another computing device, the security system plays a pre-recorded message, which can be a message that instructs the visitor to standby, wait, and/or have patience while the communication request is forwarded to another user.

Some embodiments include one security system 202 that can communicate with many computing devices. For example, one security system 202 can be placed at the entrance of an apartment complex that includes 100 individual homes. The security system 202 can be configured to properly route a communication request to the appropriate user. Some multi-home buildings include a call box near a central entryway. The security system 202 can listen to the sounds (e.g., tones) a visitor types in the call box to identify the home (and thus, the user) the visitor seeks. The security system 202 can listen to the user name the visitor requests (e.g., states) to identify the user the visitor seeks. The security system 202 can use a microphone and/or sound recognition software listen and recognize sounds. In some embodiments, the security system 202 identifies that a visitor is making a communication request by listening for a sound (e.g., a buzz of an intercom system). The security system 202 can then respond appropriately.

FIG. 24 illustrates an embodiment of a security system 950 (e.g., a doorbell) with an outer housing 954 and a camera assembly 958. The security system 950 can have buttons 962, which can be number and/or letter buttons configured to enable a visitor to select and/or dial a specific house, apartment, office, and/or person. Not all of the buttons 962 are labeled in FIG. 24 in the interest of clarity. The buttons 962 are illustrated as circles. The security system 950 can be placed near an entryway of a building in which many people are located. For example, a visitor might want to contact home number “204.” The visitor can type “204” into the security system 950, which can cause the security system to initiate contact with a computing device of a user who lives in home number “204.”

The security system 950 can enable two-way audio. A microphone inside the security system 950 can detect a visitor's sounds and a speaker in a computing device can deliver the visitor's sounds to the user. A microphone in the computing device can detect a user's sounds and a speaker in the security system 950 can deliver the user's sounds. The security system 950 can enable two-way video. A video camera of the security system 950 can detect images of the visitor and a screen of the computing device can display the images of the visitor. A video camera of the computing device can detect images of the user and a screen 970 of the security system 950 can display the images of the user. The screen 970 can be a light emitting diode display, a liquid crystal display, a plasma display, or any other display that can show images.

Some security system embodiments allow users and/or visitors to enter information (e.g., a password) with the buttons 962 to cause certain actions and/or enable certain features (e.g., unlock a door, open a garage, open a gate, turn an alarm system off, turn an alarm system on, call a particular person, enter a network password, enter a network name, enter any of the modes described herein, exit any of the modes described herein).

Select System Embodiments

FIG. 25 depicts an illustrative embodiment of a security system 202. The security system 202 may include at least one processing unit (or processor(s)) 2502 and at least one memory 2504. The processor(s) 2502 may be implemented as appropriate in hardware, computer-executable instructions, firmware or combinations thereof. Computer-executable instruction or firmware implementations of the processor(s) 2502 may include computer-executable or machine-executable instructions written in any suitable programming language to perform the various functions described. The security system 202 may also contain communications connection(s) 2506 that allow the security system 202 to communicate with a wireless router, another computing device or server, user terminals, and/or other devices.

The processor 2502 described herein can be hardware circuitry or at least one computer system. As used used herein “microprocessor” and “processor” can refer to circuitry, hardware circuitry, a computer, a computer system, and/or one or more computer systems. As used herein, “module” can refer to a portion of a security system, a portion of a computer, hardware circuitry, and/or software.

In some implementations, the memory 2504 may include different types of memory, such as static random access memory (“SRAM”), dynamic random access memory (“DRAM”) or read only memory (“ROM”). Turning to the contents of the memory 2504 in more detail, the memory 2504 may include an operating system 2508 and at least one application program or service for implementing the features disclosed herein including at least a functionality module 2510. The functionality module 2510 can refer to software and/or a computer. The memory 2504 may further include additional storage 2512 that is capable of storing recorded data.

FIG. 26 depicts an illustrative embodiment of a system or architecture 2600 in which a security system may be implemented. In some embodiments of this architecture 2600, at least one security system 202 may be in communication with a service provider 2604 via a network 2606. The security system 202 may provide notifications or recorded data to the service provider 2604.

The remote computing devices 2608 may be any type of computing device such as, but not limited to, a mobile phone, a smart phone, a personal digital assistant (“PDA”), a laptop computer, a desktop computer, a server computer, a thin-client device, a tablet PC, etc. The remote computing device 2608 may include at least one device processor 2610 capable of processing data recorded by the security system 202. Data may be stored in the remote computing device's 2608 device memory 2612 or it may be streamed over the network 2606. Where the data is streamed over the network 2606, it may be displayed using a browser application 2614. The device processor 2610 described herein can be hardware circuitry.

In some embodiments, the networks 2606 may include any one or a combination of many different types of networks, such as cable networks, the Internet, wireless networks, cellular networks, and other private and/or public networks. While the illustrated embodiment represents the users accessing the browser application 2614 over the networks 2606, the described techniques may equally apply in instances where the users interact with a service provider computer 2604 via the remote computing device 2608 over a landline phone, via a kiosk, or in any other manner. It is also noted that the described techniques may apply in other client/server arrangements (e.g., set-top boxes, etc.), as well as in non-client/server arrangements (e.g., locally stored applications, peer-to-peer systems, etc.).

As described briefly above, the browser application 2614 may allow the users to interact with a service provider computer 2604, such as to store, access, and/or manage data, develop and/or deploy computer applications, and/or host web content. The at least one service provider computer 2604, perhaps arranged in a cluster of servers or as a server farm, may host the browser application 2614. These servers may be configured to host a website (or combination of websites) viewable via the remote computing device 2608 or a web browser accessible by a user. Other server architectures may also be used to host the browser application 2614. The browser application 2614 may be capable of handling requests from many users and serving, in response, various user interfaces that can be rendered at the remote computing device 2608 such as, but not limited to, a web site. The browser application 2614 can be any type of website that supports user interaction, including social networking sites, electronic retailers, informational sites, blog sites, search engine sites, news and entertainment sites, and so forth. As discussed above, the described techniques can similarly be implemented outside of the browser application 2614, such as with other applications running on the remote computing device.

The service provider computers 2604 may be any type of computing device such as, but not limited to, a mobile phone, a smart phone, a personal digital assistant (“PDA”), a laptop computer, a desktop computer, a server computer, a thin-client device, a tablet PC, etc. The service provider computers 2604 may be the server 206 depicted in FIG. 1. Additionally, it should be noted that in some embodiments, the service provider computers 2604 may be executed by at least one virtual machine implemented in a hosted computing environment. The hosted computing environment may include at least one rapidly provisioned and released computing resource, which may include computing, networking, and/or storage devices. A hosted computing environment may also be referred to as a cloud-computing environment.

In one illustrative configuration, the service provider computers 2604 may include at least one memory 2616 and at least one processing unit (or processor(s)) 2618. The processor(s) 2618 may be implemented as appropriate in hardware, computer-executable instructions, firmware or combinations thereof. Computer-executable instructions or firmware implementations of the processor(s) 2618 may include computer-executable or machine-executable instructions written in any suitable programming language to perform the various functions described. The processor 2618 described herein can be hardware circuitry.

The memory 2616 may store program instructions that are loadable and executable on the processor(s) 2618, as well as data generated during the execution of these programs. Depending on the configuration and type of service provider computers 2604, the memory 2616 may be volatile, such as random access memory (“RAM”), and/or non-volatile, such as read-only memory (“ROM”) or flash memory. The service provider computers 2604 may also include additional storage 2620, such as either removable storage or non-removable storage including, but not limited to, magnetic storage, optical disks, and/or tape storage. The disk drives and their associated computer-readable media may provide non-volatile storage of computer-readable instructions, data structures, program modules, and other data for the computing devices. In some implementations, the memory 2616 may include multiple different types of memory, such as static random access memory (“SRAM”), dynamic random access memory (“DRAM”) or ROM. Turning to the contents of the memory 2616 in more detail, the memory 2616 may include an operating system 2622 and at least one application program or service for implementing the features disclosed herein including at least one operating module 2624. The memory 2616 may further include a database 2626 with information related to contacts or people. The database 2626 may also be a third-party database. One illustrative example of this element is a social networking website database or a criminal database. The operating module 2624 can be a computer, hardware circuitry, and/or software.

The memory 2616 and the additional storage 2620, both removable and non-removable, are examples of computer-readable storage media. For example, computer-readable storage media may include volatile or non-volatile, removable or non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules or other data. As used herein, modules may refer to programming modules executed by computing systems (e.g., processors) that are part of the remote computing device 2608 or the service provider computers 2604. The service provider computers 2604 may also contain communications connection(s) 2628 that allow the service provider computers 2604 to communicate with a stored database, another computing device or server, user terminals, and/or other devices on the networks 2606. The service provider computers 2604 may also include input/output (“I/O”) device(s) and/or ports 2630, such as for enabling connection with a keyboard, a mouse, a pen, a voice input device, a touch input device, a display, speakers, a printer, etc.

Turning to the contents of the memory 2616 in more detail, the memory 2616 may include an operating system 2622, a database containing contact data 2626 and the at least one application program or service for implementing the features disclosed herein including an operating module 2626.

Some or all aspects of the operating module 2624 may be implemented on a remote computing device 2608, such as in a mobile application. There are many methods of implementing the following features. For example, the following features could be implemented by installing a mobile application on a remote computing device 2608 or by accessing a service provider 2604 via a web browser application 2614 on a remote computing device 2608. The operating module 2624 may be configured to process data received from at least one remote computing device 2608 and/or the security system 202. The operating module 2624 may also be configured to convey messages between the remote computing device 2608 and the security system 202. Additionally, the operating module 2624 may provide a user of the remote computing device 2608 with the ability to control settings or functions of the security system 202.

In some embodiments, the operating module 2624 may have facial recognition functionality capable of identifying a potential visitor. There are multiple methods of implementing such a system. For example, some social networking sites, such as Facebook.com, have facial recognition functionality. It is envisioned that the operating module 2624 may communicate with such a site to receive a visitor's identity. Alternatively, the service provider 2604 may provide the functionality itself based on contacts stored in a database 2626. Facial recognition may also be used to determine if a human is present. For example, if a motion detector on the security system 202 detects movement, the operating module 2624 may use facial recognition to determine whether a person is present before notifying a remote computing device 2608.

The operating module 2624 may be configured to communicate and interact with the functionality module 2510 of the security system 202, as well as the remote computing device 2608. This communication and interaction can be achieved in a variety of ways. It is envisioned that the operating module 2624 will be able to provide a user of the remote computing device 2608 with the ability to perform several types of functions in conjunction with the security system 202.

Temperature Regulation

Referring now to FIG. 11, the security system 202 can include one or more heating elements 508 configured to regulate the temperature of the security system 202. For example, security systems 202 can be used in very cold environments, such as in Alaska. The heating element 508 can be used in various methods to protect temperature sensitive portions of the security system 202 from cold weather.

While protecting the security system 202 from cold weather can be important in some embodiments, protecting visitors from excessive heat can also be important in some embodiments. Excessive heat could burn visitors as they “ring” the doorbell (e.g., press the doorbell button 212 shown in FIG. 10).

The security system 202 can include a thermometer 512 to enable the system to determine the temperature inside a portion of the security system 202 and/or outside of the security system 202. In some embodiments, a remote computing device, a server, a service provider, and/or the security system 202 is the portion of the system that determines the temperature based on data from the thermometer 512.

In some embodiments, heating elements 508 generate heat by passing electric current through a conductive path with high resistance. This process can convert electricity to heat. The conductive path with relatively high resistance can be straight, coiled, or oriented in a curved path. Heating elements can use wire, ribbon, or strips made from 80% nickel and 20% chromium. Some heating elements use iron-chromium-aluminum alloys or copper-nickel alloys. Some heating elements use a conductive path made from ceramic such as molybdenum disilicide, molybdenum silicide, or molybdenum disilicide doped with aluminum. Some heating elements use a conductive path made from PCT ceramic with a positive thermal coefficient of resistance. Some heating elements use screen printed metal and/or ceramic tracks deposited on ceramic insulated metal plates.

In some embodiments, the heating element 508 produces heat when a temperature inside of the security system 202 falls below a first threshold. In some embodiments, the first threshold that causes the heating element 508 to produce heat is less than 50 degrees Fahrenheit (“F”) and/or greater than negative 20 degrees F.; less than 35 degrees F. and/or greater than negative 10 degrees F.; less than 32 degrees F. and/or greater than 0 degrees F.; or less than 10 degrees F. In some embodiments, the heating element 508 stops producing heat when the temperature inside of the security system 202 rises above a second threshold. In several embodiments, the second threshold that causes the heating element 508 to stop producing heat is less than 50 degrees F. and/or greater than negative 20 degrees F.; less than 35 degrees F. and/or greater than negative 10 degrees F.; less than 32 degrees F. and/or greater than 0 degrees F.; or less than 10 degrees F.

In some embodiments, the first threshold is equal to the second threshold, although in several embodiments, the first threshold is not equal to the second threshold. In some embodiments, the second threshold is at least 5 degrees F., at least 10 degrees F., or at least 15 degrees F. greater than the first threshold. In an example embodiment, the heating element 508 starts generating heat when the temperature inside of the security system 202 falls below 35 degrees F. and the heating element 508 continues to generate heat until the temperature inside of the security system 202 rises above 45 degrees F.

Referring now to FIGS. 10 and 11, some embodiments include stopping the generation of heat from the heating element 508 before the doorbell button 212 and/or the outer housing 224 reaches a temperature of greater than 50 degrees F., 65 degrees F., or 80 degrees F. The IR detector 470 can face towards (or at least partially towards) the outer face 214 of the outer housing 224 and/or towards (or at least partially towards) the doorbell button 212. The IR detector 470 can be used to collect data indicative of an outer temperature (e.g., the temperature of the outer housing 224, the outer face 214, and/or the doorbell button 212). Although this indicative data may actually be the temperature of an inner surface of the outer housing 224, the outer face 214, and/or the doorbell button 212, the indicative data can be used to determine whether to stop generating heat (e.g., via the heating element 508).

Thus, some embodiments including collecting data indicative of temperature using the IR detector 470 and/or the thermometer 512; analyzing the data to determine whether to start generating heat (e.g., when a temperature falls below a threshold); generating heat inside a portion of a security system (e.g., doorbell) by running electrical current through a heating element; collecting data indicative of temperature using the IR detector 470 and/or thermometer 512; analyzing the data to determine whether to stop generating heat; and/or stopping the flow of electrical current to a heating element (e.g., when a temperature rises above a threshold).

Some heating embodiments include power management methods. In some embodiments, the first and second thresholds are lower when the security system 202 is relying on internal power (e.g., from a battery 462) than when the security system 202 is relying on external power (e.g., from a building's electrical system). In some embodiments, the first threshold and/or the second threshold are at least 10 degrees F. lower, at least 20 degrees F. lower, or at least 30 degrees F. lower when the security system 202 is relying on internal power than when the security system 202 is relying on external power. In some embodiments, the security system 202 is configured to provide heat via the heating element 508 when the security system 202 has access to external power and when a temperature (inside or outside of the security system 202) falls below a threshold. In some embodiments, the security system 202 is configured to not provide heat via the heating element 508 when the security system does not have access to external power (e.g., to conserve battery power).

Silent Modes

Various embodiments include many different means of alerting users and visitors. In some embodiments, certain means of alerting users and/or visitors are silenced based on settings selected by a user (e.g., an administrator, the user of the primary computing device). Referring now to FIGS. 2 and 3, software with a user interface 240 can be used to allow a user to silence one or more of the following items: a chime 302 (e.g., a speaker, a sound output device) located inside of a building 300, a remote computing device 204, and a security system 202 (e.g., the speaker 488 shown in FIG. 11). The user interface 240 can include a button to silence the doorbell sound and to place the security system 202 in Silent Mode.

In some embodiments of Silent Mode, pressing the doorbell button 212 (shown in FIG. 5) will not send a signal (e.g., from the security system 202) to a chime located inside the building. As a result, the chime will not emit a sound. In some embodiments, the chime is a speaker (such as a speaker made by Bose Corporation) located inside of the building, which can be a home, office, warehouse, or other structure. For example, a visitor pressing the doorbell button 212 could cause the computing device 204 to notify the user, but would not cause a sound (e.g., a chime) to be emitted inside and/or near the building. In several embodiments, the security system 202 is configured to emit a sound even when the chime (e.g., speaker) located inside of the building is silenced. This configuration can notify the visitor that the security system 202 has detected the communication request of the visitor without disturbing people inside of the building.

In several embodiments, the security system 202 is silenced such that pressing the doorbell button 212 will not cause the security system 202 to emit a sound from the security system 202 (e.g., the speaker 488 in FIG. 11 will not emit a sound). When the security system 202 is silenced, the chime located inside of the building can optionally notify people inside of the building and/or the remote computing device 204 can optionally notify a user. In some embodiments, both the security system 202 and the chime inside of the building are silenced, but the computing device is not silenced. In some embodiments, the entire system is silenced. For example, the security system 202, the chime inside of the building, and the computing device can be silenced.

In some embodiments, the remote computing devices 204 are silenced such that they do not emit a sound to notify users of the remote computing devices 204. In several embodiments, the remote computing devices 204 provide no real-time audio alert, no real-time alert, or no real-time notification to users but store information (e.g., pictures of the visitor, videos of the visitor, sound from the visitors) for later review by the users of the remote computing devices 204. As used herein, “real-time alert” refers to an alert provided to a user while the visitor is located by the security system 202.

A user interface can enable users to select the types of alerts provided by the computing devices 204. Example types of alerts include sounds, images, and haptic notifications (e.g., vibrations).

Emergency Responses

In some embodiments, the operating module 2624 and/or the remote computing device 2608 may be configured to provide emergency responses, behaviors, and functions. The user of a remote computing device 2608 may be provided with the ability to dial an emergency number while still in communication with the security system 202 and/or without exiting the application software used to control the security system 202. For example, a user of the remote computing device 2608 may use the security system 202 to identify a threatening individual at the entryway to his residence. The user may then be provided with the ability to dial 911 without disconnecting communication with the security system 202, which can allow the user to continue to observe the threatening individual (e.g., a potentially harmful or destructive visitor).

FIG. 37 illustrates an emergency options selection button 3708. The user can change the phone number or other notification means that the communication system calls in the event of an emergency. For example, some users might want to call the police in the event of an emergency while other users might want to call a neighbor. FIG. 30 illustrates a button 3000 that allows a user to select which phone number is called in an emergency. FIG. 28 illustrates an emergency button 2816 that can allow for quick notification of emergency personnel or another person. Pressing the emergency button 2816 can cause the computing device 2608 to call the selected emergency number and/or send an emergency notification. The user can press the emergency button 2816 without exiting the communication system's software application running on the computing device 2608. As a result, users can more easily call emergency personnel. In addition, users can continue to watch the visitor via the user interface while they wait for emergency personnel to arrive.

Several embodiments reduce the likelihood of inadvertently selecting the emergency button 2816. In one embodiment, the emergency button 2816 must be continuously selected (e.g., pressed or contacted) for more than a threshold amount of time (e.g., at least 2 seconds, at least 3 seconds, at least 5 seconds) before the system will trigger an emergency response (e.g., notify emergency personnel or another emergency contact person). In another embodiment, the user must select the emergency button 2816 and then confirm the emergency selection and/or the presence of an emergency (e.g., by pressing a confirmation button) before the system will trigger an emergency response (e.g., notify emergency personnel or another emergency contact person). In some embodiments, the system will notify the user that the system will call emergency response personnel (e.g., will call 911) unless the user cancels the request (e.g., within a particular timeframe such as within 5 seconds or within 10 seconds). The emergency response can be that the system calls 911, provides location information to emergency response personnel, and/or provides circumstantial information to emergency response personnel (e.g., the nature of the emergency, the identity of the user).

In several embodiments, when a user indicates there is an emergency (e.g., by pressing the emergency button 2816), the security system takes a picture or a video (e.g., of the visitor). The picture or video taken in response to the user indicating there is an emergency can be stored on a server 206, on a computing device 204 (e.g., the computing device that the user utilizes to indicate there is an emergency or another computing device), and/or on the security system 202 (shown in FIG. 1). Referring now to FIG. 26, the picture or video taken in response to the user indicating there is an emergency can be stored by a network 2606, by a service provider 2604, and/or by one or more remote computing devices 2608.

The user can indicate there is an emergency by any of the means described herein including by pressing a button and/or by making a noise indicative of an emergency (e.g., screaming). Referring now to FIG. 1, the security system 202 can automatically take a picture and/or a video (e.g., of the visitor) when there is a triggering event, such as an emergency, breaking glass sounds, the presence of an unwanted visitor, an unwanted visitor entering the building, and/or any other event that the user configures to trigger automatically taking a picture and/or video. In some embodiments, the user can configure the security system 202 to automatically take a picture and/or video at time increments, at particular times, when a visitor is present, when a particular type (e.g., classification) of visitor is present, and/or when there is an emergency.

Some embodiments include detecting the presence of a visitor; sending an image or video of the visitor to a remote computing device; displaying the image or video of the visitor on a display of the remote computing device; detecting an emergency indicator (e.g., detecting a user indicating there is an emergency via the remote computing device); taking a picture (or recording a video) of the visitor in response to the emergency indicator; saving the picture or video of the visitor that was taken in response to the emergency indicator; and/or sending the picture or video taken in response to the emergency indicator to a third party (e.g., the police, a central monitoring company, monitoring personnel, security personnel, a remote server, a person located remotely from the user and the visitor).

In some embodiments, the system enables the user to allow the visitor to hear the emergency response personnel (e.g., the 911 operator) to scare the visitor away (e.g., the call to the emergency personnel is emitted through a speaker of the security system). As soon as the user presses the emergency button 2816, the security system 202 can emit a sound, which can be an alert sound such as a siren sound.

In several embodiments, the user can hear the visitor and can hear a contact person of the emergency response personnel (e.g., the 911 operator). In some embodiments, the user can hear a contact person of the emergency response personnel and can see the visitor, but the visitor cannot hear the contact person of the emergency response personnel.

In some embodiments, the software application of the communication system provides information regarding the emergency to the emergency personnel. For example, the communication system can communicate at least some of the following information to the emergency personnel: the address of the security system, the name of the user, information regarding the unwanted visitor, a video of the visitor, a picture of the visitor, audio of the visitor, and audio of the user.

In some embodiments, the operating module 2624 and/or the remote computing device 2608 may be configured to contact emergency personnel if the remote computing device 2608 is shaken, if several keys or buttons are pressed, or if the remote computing device 2608 detects noises indicative of potential panic or harm (e.g., screams). In several embodiments, the communication system will enter a Potential Emergency Mode if the communication system determines there is a potential emergency. The communication system can determine there is a potential emergency by the security system 202 and/or the computing device 2608 detecting screams, loud noises, breaking glass, and/or tampering with the security system 202 (e.g., removed from building). In some embodiments, the computing device 2608 will call emergency response personnel (e.g., the police) if the user does not intervene within a predetermined time period. The predetermined time period can be at least 3 seconds and/or less than 60 seconds or at least 10 seconds and/or less than 120 seconds. The user can intervene by instructing the computing device 2608 not to call emergency response personnel (e.g., by selecting a button on a user interface to preclude the call).

In some embodiments, the operating module 2624 and/or the security system 202 may be configured to contact emergency personnel automatically. For example, a user may have a restraining order or a no-contact order against a particular visitor. The operating module 2624 may be configured to identify a potential visitor as the particular individual (such as through facial recognition or fingerprint matching) and send an alert to law enforcement. In some embodiments, the operating module 2624 may send a notification to at least one remote computing device 2608 with the option to notify law enforcement.

In some embodiments, the operating module 2624 and/or the security system 202 may be configured to contact law enforcement if someone other than a resident attempts to use the entryway. For example, the security system 202 may be configured to detect that an entry attempt has been made, such as a deadbolt has been released and/or that a door has been opened. In this embodiment, the operating module 2624 may be configured to send a notification to law enforcement and/or a remote computing device 2608 if the individual is not identified as being granted access. In some embodiments, a user may be able to indicate to the operating module 2624 that he is away from the business or residence. In this embodiment, the operating module 2624 may be configured to contact law enforcement if the security system 202 detects that an entry attempt has been made, such as a deadbolt has been released or that a door has been opened.

In some embodiments, the operating module 2624 and/or the security system 202 may be configured to check potential visitors against a criminal database. The operating module 2624 may send a notification to a remote computing device 2608 and/or emergency personnel. The user of the remote computing device 2608 may additionally be given information related to the criminal history of the potential visitor. For example, the operating module 2624 may identify a potential visitor as a registered sex offender. In some embodiments, the operating module 2624 may be configured to contact law enforcement if the potential visitor has a criminal background. For example, a user may configure the operating module 2624 to contact law enforcement when the home is unoccupied and a potential visitor has a history of burglary.

In several embodiments, the communication system 200 uses facial recognition to identify a visitor. The communication system 200 can then find information regarding the visitor. The communication system 200 can then send information regarding the visitor to the computing device 204 (e.g., while the computing device 204 is displaying a picture or video of the visitor). The information regarding the visitor can include name, age, occupation, number of previous visits to the security system, criminal background, social media profile (e.g., Facebook profile, LinkedIn profile), and/or purpose of the visit. In some embodiments, the computing device 204 displays a category or classification that applies to the visitor. Example categories and classifications include friend, family, acquaintance, sales person, worker, service provider, and unknown.

Custom Messages

In some embodiments, the operating module 2624 may be configured to provide personal messaging. The security system 202 may be provided with pre-recorded messages that can be chosen by a user. In some embodiments, the user may be able to record a message. Where the user is able to record a message, the user may be able to record the message on the security system 202 directly, or the user may be able to use a remote computing device 2608 to record a message. Messages recorded on the security system 202 and/or the remote computing device 2608 may be stored on the security system 202, on the remote computing device 2608, and/or at the service provider 2604.

In some embodiments, the security system 202 and/or the operating module 2624 may be configured to play a specific message for a specific visiting individual, and/or it may be configured to play a specific message when a potential visitor is identified as a specific person or is included in a list of specific people.

In some embodiments, the security system 202 and/or the operating module 2624 may be configured to play a specific message if the potential visitor is not included in a list. For example, where a potential visitor is not included in a list of the resident's contacts, the security system 202 and/or operating module 2624 may be configured to indicate that the resident does not accept solicitors and/or request the visitor to provide identifying information or describe the purpose of the visit.

In some embodiments, the security system 202 and/or the operating module 2624 may be configured to play a specific message if the potential visitor has a criminal background. For example, a user may configure the security system 202 and/or the operating module 2624 to play a specific message where a potential visitor is a registered sex offender.

In some embodiments, the security system 202 may be configured to receive messages. In these embodiments, a visitor may be able to leave a message for one or more occupants. For example, where a user has chosen not to answer the door (or where the security system is set to block communication requests) the visitor may be prompted to leave a message, which may be delivered to at least one remote computing device 2608.

Security System Control

In some embodiments, the operating module 2624 may be configured to provide system control functionality. In these embodiments, the user may be capable of controlling settings, features, and/or functionality of the security system 202 through a remote computing device 2608. The operating module 2624 may be configured to provide a user with the ability to activate or deactivate any or all of the modes of operation mentioned herein. The operating module 2624 can be configured to enable the user to see available security systems and connected computing devices.

In some embodiments, the operating module 2624 may be configured to provide security system control functionality through a secure login. In some embodiments, the remote computing device 2608 may be specific to one or more security systems 202. In some embodiments, a user may be given the ability to change settings for all associated security system(s) 202. For example, where a user has one security system 202 for his home and one security system 202 for his office building, he may be provided with the ability to control both security systems 202 from a single device. Where a user login is needed, the user may be provided with control over multiple security systems 202 within the same login session.

In some embodiments, a user may be able to use a mobile device to pan a camera located on the security system 202 in order to change the FOV. The user may be able to select (or silence) the doorbell speaker sound (the sound heard outside by the visitor). The user may be able to select (or silence) the inside chime (the sound heard inside the building). The user may be able to change notification settings, indicate which remote computing devices 2608 will receive notifications, or turn off notifications entirely.

In some embodiments, a user of a remote computing device 2608 may be able to turn on/off the LED light(s) on the security system 202. For example, a user interface 3700 can include a button 3704 (shown in FIG. 37) configured to turn at least one or all of the visible lights of the security system 202 off. For example, the button 3704 can turn off the power indicator light 220 and the diagnostic light 216 (shown in FIG. 1). When the security system 202 has access to power, but does not emit any visible light, the security system 202 is in Dark Mode. Dark Mode can include emitting infrared light to enable a camera to see at night.

In some embodiments, the operating module 2624 may be configured to provide a user with the ability to change settings of the security system 202 via a remote computing device. The operating module 2624 may be configured to provide a user with the ability to set security settings as previously discussed. For example, the user may be able to indicate that he is “away” from his home and that all attempts to enter his home should result in a notification to law enforcement. The operating module 2624 may be configured to provide a user with the ability to indicate which messages should be played in accordance with the personal messaging functionality previously discussed.

FIG. 27 depicts a flow diagram embodiment 2700 showing methods of operating a doorbell communication system. Portions of FIG. 27 illustrate a process for providing a user of a remote computing device with functionality related to a visitor. Some or all of the process 2700 (or any other processes described herein, or variations and/or combinations thereof) may be performed under the control of one or more computer systems configured with executable instructions and may be implemented as code (e.g., executable instructions, one or more computer programs or one or more applications) executing collectively on one or more processors, hardware circuitry, a computer system, one or more computer systems, a network, hardware, or combinations thereof. The code may be stored on a computer-readable storage medium, for example, in the form of a computer program comprising a plurality of instructions executable by one or more processors. The computer-readable storage medium may be non-transitory. The one or more service provider computers 2604 (e.g., utilizing at least the operating module 2624) shown in FIG. 26 and/or the security system 202 from FIG. 25 may perform the process 2700 of FIG. 27.

In process 2700, the security system 202 may detect a triggering event at 2702. A triggering event is any event that indicates that a potential visitor may be present. Some non-limiting examples of a triggering event may be the ringing of a doorbell on the security system 202, activation of a motion sensor, or detection of a sound. In order to prevent excessive notifications, it may be necessary to determine whether a person is actually present at 2704. This may be done by comparing the triggering event against a threshold (such as only identifying that a visitor is present when a motion is within a given distance or a sound is over a given decibel level) or by using a specified technique. For example, the service provider 2604 may determine through facial recognition and/or computer vision that a person is present. If no visitor is detected, then the security system 202 may continue to monitor for a triggering event at 2706.

U.S. patent application Ser. No. 14/463,548, filed Aug. 19, 2014, describes various image analysis systems and methods. U.S. patent application Ser. No. 14/463,548 is incorporated by reference herein.

If a visitor is detected at 2704, then the service provider 2604 may, at 2706, send a notification to one or more remote computing devices 2608, or mobile devices, based on current settings. At 2708, the process 2700 will determine whether a user of a particular remote computing device 2608 has responded to the notification. If there has been no response, then the process, at 2710, may send a notification to a second device. If a user has responded, then communication may be allowed between the user of the remote computing device 2608 and the potential visitor at 2712. The user may be granted some or all of the functional features previously discussed in this disclosure during the communication at 2714 (or at any other time). Some of this functionality is further described in the following figures.

FIG. 28 depicts an illustrative embodiment of several features that can be implemented in a mobile application. This embodiment is illustrative of some features implemented on a remote computing device. In this embodiment, the security system 202 is identified at 2802 so the user knows which security system 202 the user is utilizing. This may be desired where more than one security system 202 is associated with a particular user or remote computing device 2608. In this embodiment, the FOV of the security system 202 is shown at 2804. In some embodiments, it may be possible to pan, or zoom with the camera in order to change the FOV.

A record button 2806 provides a user with the capability to take video recordings of the FOV. A picture button 2808 provides a user with the capability to take still pictures of the FOV. The videos and pictures may be stored on the security system 202, the remote computing device 2608, and/or the service provider 2604. Where a user wishes to watch a previously recorded video, the user may be given the ability to select the playback speed.

A speed button 2810 enables the user to select video settings related to the displayed video 2804 or image. For example, a user experiencing a slow data transmission rate may choose a lower speed, lower resolution, or still images. In some embodiments, the user can select to view still images or videos images of the FOV. In some embodiments, the user can adjust the resolution of the displayed video or images.

A mute button 2812 can allow a user to prevent a visitor from hearing the user. In some embodiments, the mute button 2812 prevents the user from hearing the visitor (e.g., if the sound recorded by the security system is bothering the user). A sound button 2814 allows the user to adjust the speaker volume to help the visitor hear better (e.g., adjust the sound level of the speaker 488 shown in FIG. 11).

An emergency button 2816 can allow for a quick notification of emergency personnel without the need to disconnect communication between the security system 202 and the remote computing device 2608. The “end call” button 2818 allows for disconnection of communication between the security system 202 and the remote computing device 2608.

Several embodiments include “on-demand” service. For example, a user can initiate communicate via a doorbell and/or can initiate live video from the doorbell by pressing a button (e.g., on demand 2820) on a user interface. Pressing the on-demand button again can terminate the communication and/or the live video.

FIG. 29 depicts an illustrative embodiment of a user being provided with the ability to record a message via a remote computing device. In some embodiments, a user is able to save the message to the security system 202 and/or the service provider 2604. The user may then be able to select if and under what conditions each message is played. In some embodiments, the user can press the custom message button 2900 to record a message. The user can instruct the system to play the message in particular circumstances. In some embodiments, the recorded message is played each time a visitor presses the doorbell button and/or each time the security system detects a visitor. The user interface 2904 can include an erase button 2908 to erase the previously recorded message, a save button 2912 to save the previously recorded message, and/or a re-record button 2916 to record a new message. In several embodiments, a user can record a first message for use in a first set of circumstances and can record a second message for use in a second set of circumstances. For example, the first message can be used when the user wants the visitor to record a message to the user and the second message can be used to tell the visitor to go to a location (e.g., to the backyard, to leave the property).

FIG. 31 depicts an illustrative embodiment of a menu for selecting notification settings. As depicted in this embodiment, the operating module 2624 may be configured to allow a user to control what notification level is provided. In this embodiment, the settings may be saved at the security system 202, at the remote computing device 2608, and/or at the service provider 2604. A first button 3100 allows the user to select that pressing the doorbell button 212 (shown in FIG. 5) results in the communication system calling the computing device and sending an image of the FOV to the computing device. In other embodiments, the first button 3100 allows the user to select that pressing the doorbell button 212 (shown in FIG. 5) results in the communication system calling the computing device and sending a video of the FOV to the computing device. A second button 3104 allows the user to configure the communication system such that when the security system detects motion (e.g., of a visitor) the security system will call the user and send an image of the FOV. A third button 3108 allows the user to configure the communication system such that when the security system detects motion (e.g., of a visitor) the security system will alert the user and send an image of the FOV. The alert is different from the call because the alert does not include a live feed upon motion detection.

In several embodiments, detection of a visitor (e.g., by the doorbell) results in a static image of the visitor being sent to the remote computing device of at least one user. Once the user selects to accept the communication request from the doorbell (e.g., from the visitor), the system can show a video (rather than a static image) of the visitor on the remote computing device. If the communication request is sent to multiple users' computing devices, each computing device can display the static image of the visitor. Once one of the users “answers” the communication request (e.g., selects to communicate with the visitor), the computing device of the user who “answers” the communication request can display a video of the visitor. In some embodiments, detection of a visitor results in a video (rather than a static image) of the visitor being sent to at least one remote computing device to enable users to “answer” the communication request.

FIG. 32 depicts an illustrative embodiment of a menu for selecting volume settings for the security system 202. As depicted in this embodiment, the operating module 2624 may be configured to allow a user to control the volume of a speaker that will be heard from the security system. For example, a speaker volume selection interface can have three settings: low 3200, medium 3204, and high 3208. The settings can control the volume of the speaker 488 shown in FIG. 11. In this example, the settings may be saved at the security system 202, at the remote computing device 2608, and/or at the service provider 2604.

FIG. 33 depicts an illustrative embodiment of a menu for selecting sound settings for the security system 202. As depicted in this embodiment, the operating module 2624 may be configured to allow a user to control what sounds are played by the security system 202 when a user presses a doorbell button and/or triggers a sensor of the security system. The user may be able to select (or silence) the sound heard outside by the visitor.

In some embodiments, a user interface is configured to enable a user to select what sound a visitor hears from the security system (e.g., when the visitor “rings” the doorbell). Selecting a first button 3304 can configure the security system to emit a traditional chime sound when a visitor presses a doorbell button. Selecting a second button 3308 can configure the security system to emit a dial tone sound or ringing sound when a visitor presses a doorbell button. Selecting a third button 3312 can configure the security system to emit a custom sound when a visitor presses a doorbell button (e.g., a sound recorded as described in the context of FIG. 29). Selecting a fourth button 3316 can configure the security system to not emit sound from a speaker when a visitor presses a doorbell button. Selecting a fifth button 3320 can enable the user to record a new custom sound (as described previously), select another sound from a list, or download a sound. The new custom sound can then become the custom sound emitted due to selecting the third button 3212. In this example, the settings may be saved at the security system 202, at the remote computing device 2608, and/or at the service provider 2604.

In some embodiments, the user can use the remote computing device to select a sound emitted by the chime located inside of the building or silence the chime located inside of the building. Several embodiments include many different sounds that the inside chime can emit when someone rings the doorbell.

FIG. 34 depicts a user interface with a menu for selecting alert settings (e.g., Ring Modes) for the security system 202. As depicted in this example, the operating module 2624 may be configured to allow a user to control whether the chime is active and whether alerts are sent to at least one remote device. Selecting a first button 3400 can configure the communication system to send an alert to the computing device and emit a sound from a chime (e.g., a speaker) located inside of the building to which the security system is attached. Selecting a second button 3404 can configure the communication system to send an alert to the computing device, but not emit a sound from a chime (e.g., a speaker) located inside of the building to which the security system is attached. Selecting a third button 3408 can configure the communication system to emit a sound from a chime (e.g., a speaker) located inside of the building but not send an alert to the computing device. Selecting a fourth button 3412 can configure the communication system to not send an alert to the computing device and not emit a sound from a chime (e.g., a speaker) located inside of the building to which the security system is attached. In this example, the settings may be saved at the security system 202, at the remote computing device 2608, and/or at the service provider 2604.

FIG. 35 depicts an illustrative embodiment of a menu for selecting which users receive notifications for the security system 202. As depicted in this embodiment, the operating module 2624 may be configured to allow a user to control what users are provided with notifications and/or in what order notifications are provided. In the illustrated example, a first user 3500 is the administrator and will receive notifications from the security system. The second user 3504 can have subordinate rights granted by the administrator to receive notifications from the security system. The third user 3508 will not receive notifications from the security system because the administrator has not selected the third user 3508 (as indicated by the lack of a check mark). In this example, the settings may be saved at the security system 202, at the remote computing device 2608, and/or at the service provider 2604.

FIG. 36 depicts an embodiment of a menu for selecting between multiple security systems 202. As depicted in this embodiment, the operating module 2624 may be configured to allow a user to select from multiple security systems 202 associated with the same remote computing device 2608. In some embodiments, a user may be given the ability to change settings for all associated security systems 202. For example, where a user has one security system 202 for his home and one security system 202 for his office building, the user may be provided with the ability to control both security systems 202 from a single computing device. Where a user login is needed, the user may be provided with control over multiple security systems 202 within the same login session. In this example, the settings may be saved at the security system 202, at the remote computing device 2608, and/or at the service provider 2604.

Each security system 3600, 3604, 3608 can include a status indicator 3612, 3616, 3620 to indicate the strength of the wireless connection that each security system 3600, 3604, 3608 is using to communicate with the computing device. The third status indicator 3620 indicates that the third security system 3608 is not connected to a network and cannot communicate with the computing device. The third status indicator 3620 can have a different visual appearance than the first status indicator 3612 and the second status indicator 3616 to indicate that the third security system 3608 is not connected to a wireless network and cannot communicate with the computing device. The different visual appearance can include a different color, a different icon, and/or a flashing icon. Selecting a security system button in FIG. 36 can cause the computing device to display a user interface regarding the selected security system (e.g., the user interface shown in FIG. 37). In some embodiments, security systems (or communication systems) continuously or intermittently monitor communication status (e.g., to evaluate if the security system is ready to send a communication request to a user and/or enable remote communication between a visitor and a user).

FIG. 37 depicts an embodiment for viewing and selecting settings for the security system 202. The settings interface illustrated in FIG. 37 summarizes several of the settings configured on other user interfaces illustrated in other figures. As depicted in this embodiment, the operating module 2624 may be configured to allow a user to select several settings for the security system 202. In this example, the settings may be saved at the security system 202, at the remote computing device 2608, and/or at the service provider 2604.

A status indicator 3712 can indicate whether the security system is connected to a wireless network. A sensor mode indicator 3716 can indicate how the security system will respond to the triggering of various sensors (see FIG. 31). A call mode indicator 3720 can indicate how users will be notified regarding communication requests (see FIG. 34). A user indicator 3724 can indicate which users will be notified via computing devices (see FIG. 35). A wireless network indicator 3728 can indicate the wireless network to which the security device is connected. A sound indicator 3732 can indicate the sound that will be emitted by the security system (see FIG. 33). A volume indicator 3736 can indicate the volume level at which sound will be emitted by the security system (see FIG. 32). Selecting the feed button 3740 can start a video stream of the FOV, display a picture of the FOV, initiate an audio stream from the security system to the computing device, and/or initiate an audio stream from the computing device to the security system.

Image Delivery Methods and Systems

Methods to address network congestion (e.g., in the context of FIG. 18) and methods of selecting video settings (e.g., in the context of FIG. 28) are taught herein. Optimizing the delivery of videos to the computing device can be important because increasing video resolution can cause the amount of data that must be delivered to the computing device to grow exponentially. In addition, some computing devices (e.g., smartphones) have such small screens that high-resolution video is not necessary in order to provide a satisfying viewing experience to a user. Sending high-resolution videos from security systems to computing devices (e.g., as shown in FIG. 1) can lead to inconsistent, intermittent, or choppy video delivery.

As described previously, some embodiments include delivering still images rather than videos. Some embodiments include delivering still images at less than 50 frames per second (“FPS”) and/or greater than 25 FPS; less than 25 FPS and/or greater than 5 FPS; less than 10 FPS and/or greater than 0.2 FPS; or less than 5 FPS and/or greater than 0.1 FPS.

Some embodiments include delivering a single still image of the visitor taken when the visitor presses the doorbell button. Some embodiments include delivering more than one still image, but include delivering an image of the visitor pressing the doorbell button to help the user determine if the user wants to answer the communication request. To avoid the visitor's hand being in the way, and thus blocking a clear view of the visitor's face, some embodiments include delivering an image of the visitor taken at least 1 second and/or less than 25 seconds after the visitor presses the doorbell button; at least 2 seconds and/or less than 10 seconds after the visitor presses the doorbell button; or at least 1 second and/or less than 5 seconds after the visitor presses the doorbell button.

Some embodiments include delivering a video taken of the visitor to the user. In several embodiments, the video can have a resolution of less than or equal to 640 pixels wide by less than or equal to 480 pixels high. In several embodiments, the video can have a resolution of less than or equal to 320 pixels wide by less than or equal to 240 pixels high. In some embodiments, the delivered video is at least 30 pixels in width and/or less than 400 pixels in width; at least 80 pixels in width and/or less than 250 pixels in width; or at least 100 pixels in width and/or less than 200 pixels in width. Some embodiments include very high-resolution video (e.g., 2560×2048).

In several embodiments, video of a user is delivered to a screen 970 of a security system 950 (shown in FIG. 24). The video of the user can be taken via a camera of a remote computing device.

Remote Camera Adjustments

Referring now to FIGS. 8-10, the camera assembly 208 has a field of view (“FOV”). Sometimes the FOV is inadequate because it does not include a desired area (e.g., outside of a building). For example, a user might want to adjust the FOV to better see a particularly tall or short visitor. A user might want to move the FOV to see other activities near the security system 202, such as the progress of a lawn care crew. If the user is not at home or if the user wants to adjust the FOV without going outside (e.g., where a visitor might be present), the user might want to adjust the FOV remotely.

FIG. 38 illustrates a user interface 3800 configured to enable a user to adjust the FOV of an image 252 displayed on a computing device 204. The user interface 3800 can include zoom buttons 3804, 3808. One zoom button 3804 can zoom in (i.e., decrease the FOV and make items in the FOV appear larger). Another zoom button 3808 can zoom out (i.e., increase the FOV and make items in the FOV appear smaller).

In some embodiments, the user interface illustrated in FIG. 38 does not physically move a camera assembly of a security system, but instead changes the portion of the camera's FOV that is displayed in the image 252. Referring now to FIGS. 19, 20 and 38, moving the sphere 3812 or otherwise selecting a direction (e.g., the dashed arrows in FIG. 38) can cause the displayed portion 848a, 848b to change while the camera's FOV 840 remains constant. In several embodiments, the user interface illustrated in FIG. 38 is used to physically move a camera assembly of a security system to enable a user to see different areas.

In some embodiments, user interfaces are configured to enable use with touch screens, such as the screen of a smartphone or tablet. User interfaces can also be used with non-touch screens (e.g., via mouse and/or keyboard input).

Referring now to FIG. 38, the user interface 3800 can also include a means to adjust the camera's viewing angle (and thus, adjust the FOV). The user interface 3800 can include arrows (shown in dashed lines) that act as buttons to adjust the viewing angle. In some embodiments, the user interface 3800 has a virtual sphere (or circle) 3812. The user interface 3800 can be a touch screen that enables the user to manipulate the sphere 3812 in any direction (including the directions shown by the dashed arrows). Moving the sphere 3812 can cause the camera assembly 208 (shown in FIGS. 8 and 9) to move to adjust the viewing angle. In several embodiments, the camera assembly 208 moves less than 70% as far as the movement indicated by the user via the sphere 3812. For example, moving the sphere 3812 50 degrees might only cause the camera assembly 208 to move 25 degrees. In several embodiments, the camera assembly 208 moves at least 1% and/or less than 70% as far as the movement indicated by the user via the sphere 3812 and/or arrows; at least 5% and/or less than 50% as far as the movement indicated by the user via the sphere 3812 and/or arrows; or at least 10% and/or less than 30% as far as the movement indicated by the user via the sphere 3812 and/or arrows. This approach can enable the user to precisely adjust the viewing angle.

FIG. 39 illustrates a top view of a camera orientation embodiment. Referring now to FIGS. 38 and 39, at least one motor assembly 3900a, 3900b can physically move the camera assembly 208 in response to user commands entered via the user interface 3800. The motor assemblies 3900a, 3900b can be coupled to the PCB 450. (Many items are not shown on the PCB 450 in the interest of clarifying particular items.) The motor assemblies 3900a, 3900b can include rollers 3904 rollably coupled to the camera assembly 208 such that rotation of the rollers 3904 can cause the camera assembly to move. In some embodiments, the roller assemblies 3904 contact (e.g., gently contact) an outer surface of the camera assembly 208, which can be a camera assembly with a spherical portion. A roller assembly 3904 can include a rubber roller secured by a pin 3908 around which the rubber roller rotates. The pins 3908 can be metal rods. Each motor assembly 3900a, 3900b can include a motor configured to rotate the rollers and powered by electricity that flows through the PCB 450.

The camera assembly 208 can be otherwise contained within a housing (e.g., the cover 404 shown in FIG. 9) to prevent the camera assembly from falling out or being inappropriately displaced. In some embodiments, the motor assemblies 3900a, 3900b are located on the side of the PCB 450 that is closest to the outer face 214 and doorbell button 212 (shown in FIG. 10).

In some embodiments, two motor assemblies 3900a, 3900b are oriented at an angle 3912 relative to each other. The angle can be approximately 90 degrees; at least 45 degrees and/or less than 135 degrees; at least 70 degrees and/or less than 110 degrees; or at least 80 degrees and/or less than 100 degrees. A first motor assembly 3900a can be configured to rotate the camera assembly 208 in a first direction and a second motor assembly can be configured to rotate the camera assembly 208 in a second direction. The second direction can be oriented approximately 90 degrees relative to the first direction; at least 45 degrees and/or less than 135 degrees relative to the first direction; at least 70 degrees and/or less than 110 degrees relative to the first direction; or at least 80 degrees and/or less than 100 degrees relative to the first direction.

FIG. 40 illustrates a side view of the camera orientation embodiment from FIG. 39. Referring now to FIGS. 8, 9, and 40, the camera assembly 208 can include a protrusion 4000, which can be located around a camera lens 434 or on the opposite side from the camera lens 434. The protrusion 4000 can be configured to contact a perimeter 402 of the outer housing 224 and/or the cover 404. As a result, the protrusion 4000 can limit the travel of the camera assembly 208 because the protrusion 4000 is configured to collide with the perimeter 402 to limit the movement of the camera assembly 208. The protrusion 4000 can extend away from the rest of the camera assembly 208. In some embodiments, the motor assemblies 3900a, 3900b are stepper motors and the software is configured to limit the travel of the motor assemblies 3900a, 3900b. Some user interfaces include a warning (e.g., sound, image, icon) when a user reaches a movement limit such that the camera assembly 208 cannot move farther.

FIGS. 41 and 42 illustrate perspective views of the camera orientation embodiment from FIG. 39. The camera assembly 208 is hidden in FIG. 42. The PCB 450 can include a hole 4200 configured to limit the travel of the camera assembly 208. The camera assembly 208 can be at least partially located in the hole 4200 of the PCB 450.

Identity Scanner

Any of the embodiments described herein can also include an identity scanner, which can be configured to identify the visitor. In some embodiments, the identify scanner can classify the visitor. Classifications can include unwanted visitor, wanted visitor, family member, owner, employee, and authorized service provider. Some methods include using the identity scanner to determine if the visitor is authorized to enter the building or if the visitor is unauthorized to enter the building. If the visitor is authorized to enter the building, then the security system (e.g., 202 in FIG. 1) can enable the authorized visitor to enter the building. The user can pre-authorize certain individuals or classifications of visitors such that the security system will allow the preauthorized individuals and classifications of visitors to unlock a door, gate, or entrance (and thereby enter the building) without additional interaction with the user. For example, if a user pre-authorizes a service provider, the security system will allow the service provider to enter the building (e.g., unlock a door) without real-time input from the user. This approach enables an authorized party (e.g., an authorized visitor) to gain access to the building without disturbing the user.

FIG. 43 illustrates a security system 202a with multiple identity scanners (e.g., 208a, 4004). The camera assembly 208a is configured to visually identify visitors through machine vision and/or image recognition. The security system 202a can include a finger scanner 4004, which can be a fingerprint reader that enables the system to compare the fingerprint of the visitor to a database of fingerprints to identify and/or classify the visitor. The database of fingerprints can be created by the user and/or can include a database of fingerprints from a law enforcement agency (e.g., a database of criminals).

The finger scanner 4004 can use any suitable algorithm including minutia and pattern algorithms. The finger scanner 4004 can analyze fingerprint patterns including arch patterns, loop patterns, and whorl patterns. The finger scanner 4004 can include any suitable fingerprint sensor including optical, ultrasonic, passive capacitance, and active capacitance sensors. The finger scanner 4004 can be integrated into the outer housing 224 of the security system 202a, which can be mounted within 7 feet of a door or entryway of a building, such as a house. In some embodiments, the security system 202a can be configured to be mounted in an entryway. Some methods include mounting a security system in an entryway of a building.

The finger scanner 4004 can be integrated into the doorbell button 212a. Pressing the doorbell button 212a can enable the finger scanner 4004 to analyze the fingerprint of the visitor. The doorbell button 212a can be used to “ring” the doorbell and house at least a portion of the finger scanner 4004.

The security system 202a and/or a remote computer can determine if the visitor is on a pre-authorized list of individuals. The security system 202a and/or a remote computer can determine if the visitor is on a list of unauthorized or screened individuals. The system can block the communication request of screened individuals and/or can call emergency response personnel in reaction to determining the identity of a screened visitor.

FIGS. 44A and 44B illustrate various method embodiments. Referring now to FIG. 44A, Block 4008 can include the visitor pressing the doorbell button (or placing a finger in proximity to a doorbell housing). Block 4012 can include a security system collecting information (e.g., capturing information) regarding a fingerprint of the visitor. Block 4016 can include comparing the fingerprint information to a fingerprint database. The comparison can include implementing a matching algorithm. Block 4020 can include using the fingerprint information to identify the visitor. Block 4024 can include determining if the visitor is included in a list of individuals. The list of individuals can be created by the user (e.g., the user can select which individuals to include in the list).

In some embodiments, the security system can be configured to collect fingerprint samples, the system can be configured to record the fingerprint samples, and the remote computing device can be configured to assign fingerprint samples to a list of individuals, classifications of individuals, and/or information regarding individuals. Referring now to FIG. 43, a user could use the finger scanner 4004 to collect fingerprint samples of family members, friends, and/or wanted visitors. The user could use a computing device to add the fingerprint samples to a database, assign an identity to each fingerprint sample, and/or add the fingerprint samples (or a person associated with each sample) to a list of individuals.

Referring now to FIG. 44A, Block 4028 can include implementing an unrecognized visitor protocol. Unrecognized visitor protocols can be customized by the user. Unrecognized visitor protocols can include disabling a chime, speaker, or audio output device located inside of the building during certain hours of the day (e.g., between 11:00 PM and 6:00 AM). Unrecognized visitor protocols can include directing the communication request to a particular user (e.g., an adult user rather than to a child user or a user under a certain age threshold). Unrecognized visitor protocols can include emitting a chime or sound inside of the building but not notifying a remote computing device (e.g., 204 in FIG. 1).

Block 4032 can include implementing a recognized visitor protocol, which can be different than the unrecognized visitor protocol. If the visitor is include on a list of individuals authorized to automatically enter the building, then the security system can enable the visitor to enter the building (e.g., unlock a door) without further approval by the user (e.g., by automatically unlocking a door as shown in Block 4036). As shown in Block 4040, if the visitor is recognized, but not included on a list of individuals authorized to automatically enter the building, then the communication system can wait for the user to provide authorization via a remote computing device for the visitor to enter the building (e.g., unlock the door).

As mentioned previously in the context of FIG. 43, the camera assembly 208a can be configured to visually identify visitors through machine vision and/or image recognition. For example, the camera assembly 208a can take an image of the visitor. Software run by any portion of the system can then compare select facial features from the image to a facial database. In some embodiments, the select facial features include dimensions based on facial landmarks. For example, the distance between a visitor's eyes; the triangular shape between the eyes and nose; and the width of the mouth can be used to characterize a visitor and then to compare the visitor's characterization to a database of characterization information to match the visitor's characterization to an identity (e.g., an individual's name, authorization status, and classification). Some embodiments use three-dimensional visitor identification methods.

Referring now to FIG. 44B, Block 4078 can include the visitor pressing the doorbell button (or placing a finger in proximity to a doorbell housing). Block 4082 can include a security system collecting information (e.g., capturing information such as an image) regarding a visual appearance of the visitor. Block 4086 can include comparing the visual information to a visual information database. The comparison can include implementing a matching algorithm and/or any of the image recognition methods mentioned above. Block 4090 can include using the visual information to identify the visitor. Block 4094 can include determining if the visitor is included in a list of individuals. The list of individuals can be created by the user (e.g., the user can select which individuals to include in the list).

Block 4098 can include implementing an unrecognized visitor protocol. Unrecognized visitor protocols can be customized by the user. Unrecognized visitor protocols can include disabling a chime, speaker, or audio output device located inside of the building during certain hours of the day (e.g., between 11:00 PM and 6:00 AM). Unrecognized visitor protocols can include directing the communication request to a particular user (e.g., an adult user rather than to a child user or a user under a certain age threshold). Unrecognized visitor protocols can include emitting a chime or sound inside of the building but not notifying a remote computing device (e.g., 204 in FIG. 1).

Block 4102 can include implementing a recognized visitor protocol, which can be different than the unrecognized visitor protocol. If the visitor is include on a list of individuals authorized to automatically enter the building, then the security system can enable the visitor to enter the building (e.g., unlock a door) without further approval by the user (e.g., by automatically unlocking a door as shown in Block 4106). As shown in Block 4110, if the visitor is recognized, but not included on a list of individuals authorized to automatically enter the building, then the communication system can wait for the user to provide authorization via a remote computing device for the visitor to enter the building (e.g., unlock the door).

Locking System

Various mounting bracket embodiments are described herein (e.g., 420 in FIGS. 12, 14, and 15). FIG. 45 illustrates a perspective view of an embodiment that couples the mounting bracket 420 (shown in FIG. 12) to the outer housing 224. A threaded screw 4044 (e.g., a setscrew or any suitable screw) is rotated through a hole 4048 in the outer housing 224 by a tool 4052 (e.g., an allen wrench, a hex wrench, a screwdriver). The threaded screw 4044 passes at least partially through the hole 4048 and into a portion of the bracket 420 (not shown). The hole 4048 can be located at a bottom portion of the outer housing 224 and/or along an outer perimeter of the outer housing 224. In some embodiments, the outer housing 224 includes a cylindrical shape and the hole 4048 is located on an outer, curved portion of the cylindrical shape.

FIGS. 46A and 46B illustrate side views with a partial cross section to illustrate how the screw 4044 can pass through the hole 4048 in the outer housing 224 and into a hole 4062 of the bracket 420. The hole 4062 of the bracket 420 can be threaded. FIG. 46A illustrates the outer housing 224 in a locked position (e.g., the screw 4044 is coupled to the hole 4062 in the bracket 420 and protrudes into the hole 4048 of the outer housing 224 such that the outer housing 224 is coupled to the bracket 420). FIG. 46B illustrates the outer housing 224 in an unlocked position (e.g., the screw 4044 does not protrude into the hole 4048 of the outer housing 224 such that the outer housing 224 can be removed from the bracket 420). Some embodiments include coupling the bracket 420 to a wall by screwing screws into the wall in a first direction and coupling an outer housing 224 (e.g., of a doorbell security system) to the bracket 420 by screwing a screw in a second direction, wherein the first direction is perpendicular to the plane of the wall and the second direction is angled at 90 degrees relative to the first direction (e.g., the second direction is parallel to the plane of the wall).

Auto-Ringing Doorbell

As described herein, various embodiments include the ability to detect whether a visitor is present even if the visitor does not press a doorbell button. For example, some embodiments include infrared detection of visitors, motion detection of visitors, noise detection of visitors, and/or visual recognition of visitors. If a visitor is present for more than a threshold amount of time, the system (e.g., 200 in FIG. 1) can cause a chime (e.g., 302 in FIG. 3) to emit a sound inside of the building and/or can send a notification to a user (e.g., via a remote computing device). The threshold amount of time can be at least 3 seconds, at least 5 seconds, at least ten seconds, and/or at least twenty seconds. The threshold amount of time can be less than 20 seconds, 15 seconds, and/or five seconds.

In some embodiments, the system can be configured to only notify a user (e.g., via a chime and/or via a remote computing device) once per detected visitor and/or once per detection episode. This approach can prevent unnecessarily redundant notifications. In several embodiments, the system will send a notification to the user when a visitor is detected (or after a threshold amount of time) but then will not send a second notification regarding the same visitor unless a second triggering event occurs. Example triggering events can include the passage of a second threshold amount of time, a second knocking episode, and/or pressing the doorbell button.

Power Management

Different parts of the world often use different types of electrical power. In addition, different houses sometimes have different wiring configurations and system installers might use different installation techniques. Several embodiments include special features that enable compatibility with any voltage, current, and wiring configuration. Some embodiments can function properly regardless of current direction or type.

Referring now to FIG. 11, several embodiments can be configured for 9 to 40 volts alternating current (“VAC”) and/or 9 to 40 volts direct current (“VDC”). Some embodiments convert input electricity into direct current (DC), such as 12 VDC. Several embodiments include a converter 494 for power conversion (e.g., converting electrical energy from one form to another). The converter 494 can convert input power (e.g., from wiring in a building) to a suitable power form for the security system 202. The power conversion can convert between AC and DC, change the voltage, and/or change the frequency. The converter 494 can include a transformer and/or a voltage regulator. In several embodiments, the converter 494 can include a DC to DC converter, a voltage stabilizer, a linear regulator, a surge protector, a rectifier, a power supply unit, a switch, an inverter, and/or a voltage converter. In some embodiments, the converter 494 converts 50 Hertz (“Hz”) power into 60 Hz power.

In some embodiments, the security system 202 uses a first amount of power to “ring” the chime inside of the building and a second amount of power when in Standby Mode, wherein the first amount of power is at least twice as large as the second amount of power.

FIG. 47 illustrates a diagrammatic view of an electrical power configuration, according to some embodiments. The security system 202 can be located outside of a building 300 and/or coupled to a wall of the building 300. The building 300 can be a home, an office building, a government building, an enclosure, or any other type of structure configured to shelter people.

The building 300 can include a building power supply 5000, which can receive electrical power from a public utility. A transformer 5004 can be electrically coupled to the building power supply 5000 by a first wire 5004 and a second wire 5006. As used herein, “wire” can include electrical conductors such as metal cables and wires. The transformer 5004 can step down the electrical power (e.g., 120 volts AC, 240 volts AC) from the building power supply 5000 to a lower voltage (e.g., at least 10 volts and/or less than 20 volts, at least 7 volts and/or less than 25 volts).

A third wire 5010 can electrically couple the transformer 5004 to a sound output device 5014, which can be a chime, a speaker, a bell, or another device suitable to emit a sound inside of the building 300. A fourth wire 5018 can electrically couple the transformer 5004 to the security system 202 (e.g., the doorbell). A fifth wire 5022 can electrically couple the security system 202 to the sound output device 5014. As a result of this configuration, the security system 202 can control the flow of electricity to the sound output device 5014. In many embodiments, the sound output device 5014 is configured such that it cannot emit sound without a trigger power above a triggering threshold. The trigger power comes from the building power supply 5000 and flows into the transformer 5004 (via wires 5004, 5006). Thus, the transformer 5004 can supply the trigger power to a first circuit that comprises the fourth wire 5018, at least a portion of the security system 202, the fifth wire 5022, the sound output device 5014, and the third wire 5010. The fourth wire 5018 and the fifth wire 5022 can protrude from a hole 5012 in the outside of the building 300.

In some doorbell electrical power configurations, pressing a mechanical doorbell button (not shown) creates a closed electrical loop to energize a chime. In other words, the mechanical doorbell button can be a switch that is normally in an open position and is in a closed position when a person presses the button.

Some doorbell systems include a sound output device 5014 that includes a plunger configured to strike two flat metal bar resonators. The plunger can be operated by solenoids. Pressing the mechanical doorbell button can cause the solenoid to force the plunger to hit a first resonator. If a spring is included, then the spring can cause the plunger to hit a second resonator (e.g., when the mechanical doorbell button is released). The plunger hitting a resonator can cause a sound (e.g., a “ding” sound) to be emitted from the sound output device 5014.

Some sound output devices include a first solenoid and a second solenoid. The first solenoid can be configured to hit both a first metal bar and a second metal bar (e.g., to make a “ding-dong” sound). The second solenoid can be configured to hit the first metal bar, but not the second metal bar (e.g., to make a “ding” sound). In some cases, a first doorbell (e.g., a front doorbell) activates the first solenoid (e.g., to make a “ding-dong” sound) and a second doorbell (e.g., a back doorbell) activates the second solenoid (e.g., to make a “ding” sound). This approach can enable a user to distinguish between the front doorbell's sound and the back doorbell's sound (as emitted from a sound output device).

While pressing a mechanical doorbell button can close an electrical circuit to energize a chime and thereby cause a chime to emit a sound to notify a person inside of a building, the security system 202 can be configured (in some embodiments) such that pressing the doorbell button 212 does not mechanically close an electrical circuit to cause a chime to emit a sound. In several embodiments, the doorbell button 212 is not a switch that electrically couples the fourth wire 5018 to the fifth wire 5022. Instead, the fourth wire 5018 and the fifth wire 5022 can be electrically coupled to a printed circuit board (“PCB”) 516 (shown in FIG. 11). The other items in FIG. 11 (e.g., 458, 524, 500, 504, 508, 510, 512, 462, 484, 494, 488, 480, 492, 208) can receive electrical power from the PCB 516.

In some embodiments, the doorbell button 212 is a press sensor (rather than the doorbell button 212 being physically coupled to a mechanical switch that can electrically close a circuit between the transformer 5004 and the sound output device 5014). The sensor can detect when a visitor presses the doorbell button 212. This “press detection” is used by software of the security system 202 or of the communication system 200 (shown in FIG. 1) to help determine whether to emit sound from the sound output device 5014 and/or whether to notify the user via a computing device (e.g., 204 in FIG. 1) based on additional parameters such as a profile and/or user settings.

Referring now to FIGS. 11 and 47, in some embodiments, the security system 202 (e.g., the PCB 516 and electrical components coupled to the PCB 516) is configured to allow alternating current (“AC”) power to flow from the security system 202, to the sound output device 5014, and/or to the transformer 5004. In several embodiments, the security system 202 is configured to provide direct current (“DC”) power to at least portions of the PCB 516. In some embodiments, the security system 202 is configured to provide AC power to the sound output device 5014 while providing DC power to at least portions of the PCB 516.

In several embodiments, electrical power for the sound output device 5014 and/or electrical power for the PCB 516 are routed through the security system 202 and/or through the PCB 516. Electrical power from the fourth wire 5018 can be routed through the security system 202 and/or through the PCB 516 prior to reaching the fifth wire 5022. Electrical power from the fifth wire 5022 can be routed through the security system 202 and/or through the PCB 516 prior to reaching the fourth wire 5018. Thus, electrical power for the sound output device 5014 (e.g., chime) does not need to bypass the security system 202.

In some embodiments, the security system 202 includes a Non-energizing Mode in which the security system 202 provides DC power to at least portions of the PCB 516 while draining power to the sound output device 5014, wherein the power to the sound output device is below a triggering threshold. The triggering threshold is the amount of electrical power (e.g., volts, current) necessary to cause the sound output device 5014 to emit a notification sound (e.g., a sound configured to notify a person inside of the building 300 that someone is at the door). In several embodiments, the security system 202 includes an Energizing Mode in which the security system 202 provides AC power to the sound output device above the triggering threshold. In some embodiments of the Energizing Mode, the security system 202 provides DC power to at least portions of the PCB 516.

In some embodiments of the Non-energizing Mode, the security system 202 provides less than 30%, less than 20%, less than 10%, at least 3%, at least 1%, and/or at least 0.1% of the power from the transformer 5004 to the sound output device 5014. In some embodiments of Energizing Mode, the security system 202 provides at least 70%, at least 80%, at least 90%, or at least 95% of the power from the transformer 5004 to the sound output device 5014. In several embodiments, the security system 202 charges the battery 462 during Non-energizing Mode and does not charge the battery 462 during Energizing Mode.

In some embodiments, the security system 202 includes a rectifier 524 to convert AC to DC. The rectifier 524 can comprise vacuum tube diodes, mercury-arc valves, copper and selenium oxide rectifiers, semiconductor diodes, silicone-controlled rectifiers, and/or silicone-based semiconductor switches.

Methods for using a doorbell system can include obtaining a doorbell (e.g., security system 202) that comprises a speaker, a microphone, a camera, and an outer housing; and connecting the doorbell electrically to an electrical power supply 5000 of a building 300. The electrical power supply can be provided by a utility company. In some embodiments, the electrical power supply is a transformer 5004 that is electrically connected to a building's electricity that is provided by a utility company.

In some embodiments, the doorbell can be connected electrically to a sound output device 5014 (e.g., a digital chime, a mechanical chime, a speaker) that is located remotely relative to the doorbell. For example, the doorbell can be coupled to an outside wall of a building and the sound output device can be coupled to an inside wall of the building. The building can couple the sound output device to the doorbell while the sound output device is located remotely relative to the doorbell. The doorbell can be connected communicatively to a remote computing device to enable the doorbell to communicate (e.g., wirelessly) with the remote computing device.

Methods can include receiving a first current into the doorbell (e.g., through the fourth wire 5018) from the power supply 5000 of the building 300 and using the first current to provide at least a first portion of a first electrical energy to the camera 208 and to the microphone 452 (shown in FIG. 9). Providing the first current can enable the camera and microphone to have electricity to operate.

Some methods include using the doorbell to close an electrical circuit 5026 that comprises the sound output device 5014 such that the first current flows through the sound output device 5014 and the first current provides a first electricity that is less than a triggering threshold of the sound output device 5014 such that the sound output device 5014 does not emit a notification sound in response to the first electricity.

Some embodiments comprise using the doorbell (e.g., security system 202) to detect a presence of a visitor while closing the electrical circuit 5026 such that first current provides the first electricity that is less than the triggering threshold. Then, in response to detecting the presence of the visitor, methods can include using the doorbell to close the electrical circuit 5026 to supply a second electricity to the sound output device 5014. The second electricity can be greater than the triggering threshold of the sound output device 5014 such that the sound output device emits the notification sound in response to the second electricity. Embodiments can also include sending a wireless notification to the remote computing device 204 (shown in FIG. 1) regarding the presence of the visitor (e.g., in response to the second electricity or in response to simply detecting the visitor).

In several embodiments, the electrical circuit 5026 comprises the doorbell (e.g., 202), the sound output device 5014, and a transformer 5004 (which can have an alternating current or direct current output). The transformer 5004 can electrically couple the electrical circuit 5026 to the power supply 5000 of the building 300 such that the transformer 5004 is configured to provide electrical power from the power supply 5000 to the electrical circuit 5026. The transformer 5004 can comprise an electrical output having a direct current. Receiving the first current into the doorbell (e.g., 202) from the power supply 5000 of the building 300 can comprise receiving the direct current from the transformer 5004.

Electrically connecting a doorbell to an electrical power supply can include indirectly electrically connecting the doorbell to the power supply (e.g., using the transformer 5004 to electrically couple the doorbell 202 to the power supply 5000). A wire can be electrically connected when the wire is connected such that it could conduct electricity if there was a complete circuit. A doorbell can be electrically connected to a wire if the doorbell is conductively coupled to the wire (even if a complete circuit is not present to enable an electrical current).

In several embodiments, the electrical circuit comprises the doorbell, the sound output device, and a transformer. The transformer can electrically couple the electrical circuit to the power supply of the building such that the transformer is configured to provide electrical power from the power supply to the electrical circuit. The transformer can comprise an electrical output having an alternating current. Receiving the first current into the doorbell from the power supply of the building can comprise receiving the alternating current from the transformer. Method can further comprise converting at least a second portion of the alternating current into a direct current. The converting can occur within the outer housing of the doorbell.

In some embodiments, the power supply 5000 provides the second electricity to the electrical circuit. The doorbell can be configured to control whether the doorbell system provides the first electricity or the second electricity to the sound output device.

Several embodiments include initiating a transmission of the wireless notification (e.g., 230 in FIG. 1) to the remote computing device regarding the presence of the visitor while using the doorbell to supply the second electricity to the sound output device. Then, after initiating the transmission of the wireless notification to the remote computing device, methods can include terminating the supply of the second electricity to the sound output device and using the doorbell to close the electrical circuit to provide a third electricity to the sound output device. The third electricity can be less than the triggering threshold of the sound output device such that the sound output device does not emit the notification sound in response to the third electricity.

Some embodiments comprise using the doorbell to supply the third electricity to the sound output device while continuing to transmit the wireless notification to the remote computing device.

Several embodiments comprise terminating the supply of the second electricity to the sound output device and using the doorbell to close the electrical circuit to provide a third electricity to the sound output device. The third electricity can be less than the triggering threshold of the sound output device such that the sound output device does not emit the notification sound in response to the third electricity. Embodiments can include initiating a transmission of the wireless notification from the doorbell to the remote computing after terminating the supply of the second electricity to the sound output device.

Some embodiments include using the doorbell to detect the presence of the visitor while closing the electrical circuit comprises using a motion sensor (e.g., motion detector 218 shown in FIG. 1) to detect the presence of the visitor. Methods can also include using the first current to provide at least a second portion of the first electrical energy to the motion sensor. The second portion of the first electrical energy can be greater than an operational threshold of the motion sensor such that the second portion of first electrical energy is capable of providing sufficient electrical power for the doorbell to operate the motion sensor while the first current provides the first electricity that is less than the triggering threshold of the sound output device. An operational threshold is an electrical threshold that represents the minimum electricity necessary to operate an item. The motion sensor can be replaced with a proximity sensor 500 (shown in FIG. 11) configured to detect whether a visitor is located near the doorbell. The proximity sensor can be a laser or infrared proximity sensor. The proximity sensor can also be the doorbell button 212 (that rings the chime) as shown in FIG. 6.

In several embodiments, using the doorbell to detect the presence of the visitor while closing the electrical circuit comprises using image analysis to detect the presence of the visitor. Methods can further comprise using the first current to provide at least a second portion of the first electrical energy to an image analysis system 520 (shown in FIG. 11). The second portion of the first electrical energy can be greater than an operational threshold of the image analysis system such that the second portion of first electrical energy is capable of providing sufficient electrical power for the doorbell to operate the image analysis system while the first current provides the first electricity that is less than the triggering threshold of the sound output device.

In some embodiments, the first current is configured such that the first portion of the first electrical energy is greater than an operational threshold of the camera while the first current is configured such that the first current provides the first electricity that is less than the triggering threshold of the sound output device.

In several embodiments, the first current is configured such that the first portion of the first electrical energy is less than an operational threshold of the camera while the first current is configured such that the first current provides the first electricity that is less than the triggering threshold of the sound output device, the method further comprising using the first portion of the first electrical energy to charge a battery located inside of the outer housing of the doorbell, and then discharging at least an electrical portion of the battery to provide a second electrical energy that is greater than the operational threshold to the camera.

In some embodiments, the doorbell comprises a wireless communication system configured to enable sending the wireless notification from the doorbell to the remote computing device. Embodiments can include using the first current to provide at least a second portion of the first electrical energy to the wireless communication system, wherein the first current is configured such that the second portion of the first electrical energy is less than an operational threshold of the wireless communication system while the first current is configured such that the first current provides the first electricity that is less than the triggering threshold of the sound output device. Methods can also include using the second portion of the first electrical energy to charge a battery located inside of the outer housing of the doorbell, and then discharging at least an electrical portion of the battery to provide a second electrical energy that is greater than the operational threshold to the wireless communication system. Then, embodiments can include using the wireless communication system to send the wireless notification to the remote computing device using the second electrical energy.

FIG. 47 illustrates a first doorbell 5028 just after the first doorbell 5028 was disconnected from the fourth wire 5018 and the fifth wire 5022. The first doorbell 5028 was replaced with a second doorbell (e.g., security system 202).

Several embodiments include methods for replacing a first doorbell with a second doorbell. The first doorbell 5028 comprises a switch configured to close an electrical circuit 5026 having a transformer 5004 and a sound output device 5014 to enable the sound output device 5014 to emit a notification sound. Methods can include detaching the first doorbell from a first wire that is electrically connected to the transformer; detaching the first doorbell from a second wire that is electrically connected to the sound output device; and obtaining the second doorbell. The second doorbell can comprise a speaker, a microphone, a camera, and an outer housing. The speaker, the microphone, and the camera can be coupled to the outer housing.

Some embodiments include connecting the second doorbell electrically to the first wire that is electrically connected to the transformer, and connecting the second doorbell electrically to the second wire that is electrically connected to the sound output device. The second doorbell can be located remotely relative to the sound output device. For example, the second doorbell can be located on an outside wall of a building while the sound output device is located inside of the building.

Several embodiments include connecting the second doorbell communicatively to a remote computing device such that the second doorbell is configured to communicate with the remote computing device. Embodiments can include receiving a first current into the second doorbell from at least one of the first wire and the second wire; using the first current to provide a first electrical energy to at least a first portion of the second doorbell; and draining the first current to at least one of the first wire and the second wire.

Some embodiments include entering a first mode in response to connecting the second doorbell electrically to the first wire that is electrically connected to the transformer, and in response to connecting the second doorbell electrically to the second wire that is electrically connected to the sound output device. During the first mode, methods can comprise using the second doorbell to close the electrical circuit that includes the transformer and the sound output device such that the first current flows through the sound output device and the first current provides a first electricity that is less than a triggering threshold of the sound output device such that the sound output device does not emit a notification sound in response to the first electricity.

Several embodiments include entering a second mode in response to using the doorbell to detect a presence of a visitor. During the second mode, the methods can comprise using the doorbell to close the electrical circuit to supply a second electricity to the sound output device. The second electricity can be greater than the triggering threshold of the sound output device such that the sound output device emits the notification sound in response to the second electricity. The second mode can also include sending a wireless notification to the remote computing device regarding the presence of the visitor.

FIG. 48 illustrates a diagrammatic view of a security system configured to communicate wirelessly with a sound output device 5014 and/or a speaker 5016, according to some embodiments. A digital chime is one type of sound output device 5014. In some embodiments, chimes do not include solenoids configured to drive a plunger to hit a metal component to make a sound (e.g., a “ding” sound). In some embodiments, the sound output device 5014 is a speaker 5016 that can emit a digital sound such as a pre-recorded “ding” or any other sound (e.g., a song or prerecorded words).

In some embodiments, the security system 202 is connected electrically to a transformer 5004 (e.g., via a third wire 5020 and a fourth wire 5024) and/or is electrically connected to a building power supply 5000 (e.g., via a first wire 5004 and a second wire 5006). In several embodiments, the security system 202 can wirelessly communicate with the sound output device 5014 (e.g., a solenoid-based chime, a digital chime, a speaker) via any suitable means of wireless communication 230. Wireless communication 230 between the security system 202 (e.g., a doorbell) and the speaker 5016 can enable the system to emit notification sounds from the external speaker 5016, which can be located inside of the building 300 (although the speaker 5016 is external relative to the security system 202).

Inside Uses

Several embodiments can be used even in areas that are not entryways or near doors. For example, security systems (e.g., 202 in FIG. 1) can be mounted on a stand, on an interior wall, on a wheelchair, by a bed, or on another suitable object to enable a person (e.g., the visitor) to send a communication request (e.g., a notification) to a remote user. For example, an elderly person or a bedridden person can press the button 212 (shown in FIG. 5) to communicate with a user who can see and hear the elderly person or bedridden person. Some security system embodiments include a screen 907 (shown in FIG. 24) that can enable the elderly person or bedridden person to see the user (e.g., an adult child or caregiver).

FIG. 49 illustrates a diagrammatic view of a security system 202 located inside of a building 300, according to some embodiments. The security system 202 can be mounted on a stand, on an interior wall, or on another object suitable for holding the security system 202. In several embodiments, the security system 202 is not electrically connected to an external sound output device, although the security system 202 can emit sound from a speaker (e.g., speaker 488 shown in FIG. 11) coupled to the security system 202. In some embodiments, the speaker 488 is located inside of an outer housing 224 (shown in FIGS. 1 and 11).

A first wire 5004 and a second wire 5006 can electrically connect (e.g., couple) the security system 202 to a building power supply 5000 (e.g., an electrical outlet or an electrical panel). In some embodiments, the security system 202 is battery operated such that attaching the security system 202 to an external power supply (e.g., the building power supply 5000) is unnecessary. In several embodiments, the power supply 5000 provides more than 6 volts, less than 36 volts, less than 140 volts, and/or less than 260 volts. In some embodiments, electrical power from a building must be changed (e.g., different voltage, different current) prior to providing the electrical power to the security system 202 (e.g., a doorbell).

Communication Control

Referring now to FIGS. 1 and 11, in several embodiments, the user (e.g., of the computing device 204) has superior communication rights than the visitor talking into the security system 202. Sometimes, the user and the visitor might attempt to talk at the same time. This situation can lead to ineffective communication. In addition, if the microphone 484 is capturing (e.g., recording, sensing) sound while the speaker 488 is emitting sound from the user of the computing device 204, then the communication system 200 could suffer from audio feedback (e.g., the user's voice emitted by the speaker 488 could be captured by the microphone 484 and emitted by the computing device 204). At least some of these complications can be solved by various communication control embodiments.

In some embodiments, the computing device 204 has superior communication rights relative to the security system 202. As a result, if the speaker 488 is emitting sound, then the microphone 488 can be disabled. In several embodiment, the microphone 488 is disabled (e.g., prevented from capturing sound or being used to transmit sound to the computing device 204) a first period of time before the speaker 488 emits sound, while the speaker 488 emits sound, and/or a second period of time after the speaker 488 emits sound. The first period and/or the second period can be at least one nanosecond, at least one millisecond, at least 50 milliseconds, and/or less than one second.

Referring now to FIG. 3, in some embodiments, multiple devices (e.g., 204, 306) are used to communicate with a visitor via at least one security system 202. Some methods include assigning superior communication rights to some devices (e.g., 204, 306) relative to other devices (e.g., 204, 306).

Pool Monitoring

Drowning is the second-leading cause of injury-related death for children under 14 years old. Traditional pool monitoring devices rely on detecting when a person enters the water. People can drown in less than two minutes. As a result, sending a notification to a remote computing device when a person enters the water can leave insufficient time for the user of the remote computing device to save the drowning person. Various embodiments described herein address at least some of these shortcomings of traditional pool monitoring devices.

FIG. 50 illustrates a diagrammatic view of a security system 202 being used to monitor a pool area, according to some embodiments. The motion detector 218 can be configured to determine whether a person is located in the pool 5030 even when the security system 202 is located outside of the pool 5030. In some embodiments, the security system 202 is placed at least three feet and/or less than fifty feet from the pool 5030.

The security system 202 can take a picture 208 with the camera assembly 208 in response to detecting motion (e.g., via the motion detector 218). The security system 202 (or another portion of the communication system 200 illustrated in FIG. 1) can analyze the picture to determine if the motion was caused by an adult or by a child (e.g., by a person under a predetermined height threshold). In some cases, the height threshold can be 5 feet, 4.5 feet, 3.5 feet, or 3 feet.

The camera assembly 208 can be configured to visually identify people through machine vision and/or image recognition. For example, the camera assembly 208 can take an image of the person located near the pool 5030. Software run by any portion of the system can then analyze select features of the person from the image. The software can use scaling to estimate the height of the person (e.g., based on previous calibration procedures and information).

In some embodiments, if the motion was caused by an adult and/or by a person taller than the height threshold, then the system will not send a notification (e.g., alarm) to the remote computing device and/or will not emit an alert sound from the speaker 488 (shown in FIG. 11) of the security system 202. In some embodiments, if the motion was caused by a child and/or by a person shorter than the height threshold, then the system will send a notification to the remote computing device and/or will emit an alert from the speaker of the security system 202.

Although the security system 202 can be configured to detect if a person falls into the pool 5030, the security system 202 can also be configured to detect whether a person is located within a zone 5034 that includes at least a portion of the pool 5030. In some embodiments, the zone 5034 includes all of the pool 5030 and/or an area around the perimeter of the pool 5030. The zone 5034 can define a danger zone. Once the security system 202 detects that a person is located in the zone 5034, the security system can enter a Standby Mode in which the security system 202 conducts at least one analysis to determine if the person might be in danger (e.g., if the person is shorter than the height threshold or if the person is authorized to be in the zone 5034 and/or in the pool 5030).

In some embodiments, the security system 202 will send a notification to a remote computing device and/or emit an alert sound from the speaker unless the detected person is wearing a device that indicates the person is authorized to be in the zone 5034 and/or in the pool 5030. The authorization device 5038 can be a bracelet or other object worn by the person. The authorization device 5038 can include a radio-frequency identification (“RFID”) or Bluetooth communication device configured to provide data to the security system 202 (e.g., data regarding the authorization of the device to be located in the zone 5034 and/or pool 5030).

Several methods include using the security system 202 to detect whether a person is located in the zone 5034. Methods can include determining whether the person is authorized to be in the zone 5034. In some embodiments, methods include sending a notification to a remote computing device and/or emitting an alert sound from the speaker 488 (shown in FIG. 11) of the security system 202 if the person is located in the zone 5034 and/or not authorized to be in the zone 5034.

Advertising

In some embodiments, the communication system 200 (shown in FIG. 1) is used to deliver targeted ads based on the location of the user of the remote computing device. Referring now to FIGS. 1 and 2, some embodiments include tracking the location (e.g., GPS coordinates) of the computing device 204 and using the location to select advertisements (e.g., based on the location). For example, if the remote computing device 204 is located in a particular city, the system 200 can deliver ads for nearby restaurants and services. The advertisements 258 can be displayed on the user interface 240 (shown in FIG. 2). In some embodiments, the advertisements are shown near the bottom of the screen of the computing device. The advertisements can be sent through and/or controlled by the server 206 and/or a database.

In several embodiments, the advertisements 258 are selected based on at least one feature or characteristic of the visitor. For example, if the visitor is a vacuum salesperson, then the advertisement 258 can be related to vacuums. In some embodiments, the advertisements 258 offer to provide additional information regarding the visitor (e.g., background check information, identity information, visit history information, relationships to acquaintances of the user).

Statistics

Several embodiments include tracking, recording, and/or providing information regarding visitors and/or visits. This information can include statistics and other forms of data. Referring now to FIG. 1, some embodiments track, record, and/or provide the number of times a visitor has visited and/or been detected by a security system 202. Several embodiments track, record, and/or provide the number of times a visitor has pressed (e.g., “rung”) the doorbell button 212 (shown in FIG. 5), visited a particular location (e.g., the building to which the security system 202 is coupled), and/or communicated with a particular computing device 204. Some embodiments track, record, and/or provide the number of visitors and/or the number of visits to a particular area monitored by a security system 202.

Several embodiments include aggregating, combining, and/or comparing information regarding visitors and/or visits from at least two security systems 202 (and/or from at least two buildings). This aggregated and/or combined data can be analyzed by a third party (e.g., not a user of one of the security systems 202) to identify visit trends and/or to track individual visitors. For example, this data can be used to determine which neighborhoods receive the most visitors and/or visits. This data can also be used to track a particular visitor as the visitor moves from one building to another building or neighborhood. Aggregated and/or combined data regarding visitors can be searched and/or analyzed to determine if a particular individual has visited a particular area, neighborhood, or building.

Some embodiments include creating a log that records the date and time of opening and closing of a door. Referring now to FIG. 23, the door log 916 can include locking and unlocking data. Several embodiments include a log that records whether a door was unlocked by a physical key or via an automated system (e.g., a security system 202). The security system 202 can lock and unlock a door lock 930. Data regarding whether a physical key or an automated system unlocked a door can aid criminal investigations. The door log 916 can also include a picture of visitors who unlock a door and/or pass through a door. A camera assembly 208 (shown in FIG. 1) can take the picture. The door log 916 can also include the identity of the visitors.

Security

In some embodiments, security systems 202 (e.g., doorbells) are disabled if they are stolen. This approach can deter theft once potential thieves know stolen systems will not function properly (e.g., once disabled).

In several methods, the owner (e.g., a user) of a stolen security system 202 can contact a remote administrator (e.g., the manufacturer of the stolen security system). Based on the request of the owner, the remote administrator can disable the stolen security system 202 remotely (e.g., without physically touching the security system 202). The remote administrator can use wireless communication 230 and/or a server 206 to disable the stolen security system 202.

In some embodiments, the remote administrator, the owner, and/or the user can detect the location of the stolen security system 202. The remote administrator can tell the owner the location of the stolen security system 202. For example, if a person connects the stolen security system 202 to a communication network (e.g., the Internet), the administrator can locate the stolen security system 202.

In several embodiments, once a security system 202 is connected to a wireless network, the security system 202 cannot connect to another wireless network without being “unlocked.” Thus, if the security system 202 is stolen, the security system 202 could be nearly worthless because the thief likely will not be able to connect the security system to another wireless network (e.g., the wireless network at the thief's home). In this context, “unlocked” means that the security system 202 is capable of connecting to another wireless network and capable of sending notification requests to a remote computing device 204 via the other network. Thus, in some embodiments, once a security system 202 is connected to a first wireless network, the security system 202 cannot be connected to another wireless network without being unlocked (e.g., from the first wireless network). Once the security system 202 is unlocked, then it can be connected to a second wireless network.

A remote administrator and/or the owner can unlock the security system 202 by, for example, entering a password and/or logging into a website configured for unlocking security systems 202.

Delivery Identification

FIG. 53 illustrates an embodiment of barcodes 1030, 1034 on a package 1038 being held up to a camera assembly 208 of a security system 202 to scan the barcodes 1030, 1034. In some embodiments, a doorbell is configured to identify a package by scanning a barcode. The package can be placed with 36 inches and/or within 20 inches of a camera of the doorbell to enable the doorbell to scan the barcode. “Barcode” is used in a broad sense herein and includes optical machine-readable representations of data regarding the object to which the barcode is attached. Barcodes can include many different geometric patterns and are not limited to straight lines. Barcodes can include Quick Response (QR) codes, Universal Product Codes (UPC), and many other machine-readable representations of data.

In some embodiments, once the security system 202 scans a barcode to enable identifying the package 1038, methods include sending a notification to a person associated with the package (such as the person to whom the package is addressed). The notification can include an email to the person, a text message, and/or an automated phone call. The notification can communicate that the package has arrived. The notification can also communicate the contents of the package. As used herein, “package” is used in a broad sense and can include letters and boxes delivered to a building.

Laser Identification

Referring now to FIG. 53, the security system 202 can include a light 1042, which can be a laser. The light 1042 can emit a beam of light 1044, which can be a laser beam. Some embodiments include using the laser beam to detect is a visitor is present near the security system 202. The security system 202 can be configured to detect whether a visitor is present based on whether the beam 1044 is broken (e.g., interrupted) by the visitor. In some embodiments, the security system 202 determines an average beam behavior and then identifies deviations from the average beam behavior as indications of a visitor. For example, if a beam 1044 typically travels 10 feet without being broken, but suddenly the beam only travels two feet without being broken, then the system can interpret the change in the beam signal as an indication of the presence of a visitor. Some security systems 202 are configured to detect light reflected back to the security system 202.

Answering Devices

Many types of computing devices can be used to receive notifications regarding the presence of a visitor and to communication with a visitor. For example, a car and glasses can be configured to receive alerts regarding the presence of a visitor.

FIG. 54 illustrates a front view of a dashboard of a vehicle 1054 such as a car, truck, bus, airplane, or motorcycle. The vehicle includes a computing device 204a, which can include any of the features and perform any of the methods described herein in the context of other embodiments and computing devices 204. The computing device 204a can include a display screen 242a, which can be integrated into the dashboard of the vehicle 1054. Some embodiments include answering visitor alerts via vehicles 1054. A user interface 240 can enable users to control the computing device 204a.

In some embodiments, the display screen 242a is part of a television, which can be configured to receive alerts regarding the presence of visitors. The television can be configured to receive push notifications from a security system 202 (shown in FIG. 51). Televisions can be embodiments of computing devices 204 (shown in FIG. 51). Some embodiments include answering visitor alerts via televisions.

FIG. 55 illustrates a perspective view of glasses 1058, which can be virtual reality glasses, augmented reality glasses, and/or a Google Glass made by Google Inc. The glasses 1058 can include a display screen 242b. Glasses 1058 can be embodiments of a computing device 204b, which can include any of the features and perform any of the methods described herein in the context of other embodiments and computing devices 204.

Some embodiments include answering visitor alerts via glasses 1058. A user can control and interact with the glasses 1058 via voice commands. The glasses 1058 can include a speaker to allow the user to hear the visitor.

User Interfaces

FIGS. 57-60 illustrate front views of a display screen or portions thereof with graphical user interfaces. The graphical user interfaces can be displayed on the display screen 242 shown in FIG. 2. The graphical user interfaces can include any of the features described in the context of FIG. 2.

The graphical user interface shown in FIG. 57 includes a Bright Mode button 544. Touching the Bright Mode button on a display screen 242 (labeled in FIG. 2) can increase the brightness of the image 252a taken by the camera assembly 208 of the doorbell 202. Pressing the Bright Mode button 544 a second time can decrease the brightness of the image 252a.

Mounting Embodiments

FIG. 61 illustrates a front view of the security system 202 just before the security system 202 is mounted to a power outlet 228 by pressing electrical prongs 274 (shown in FIG. 63) that protrude from a backside 278 (shown in FIG. 63) of the security system 202 into electrical ports 270 of the power outlet 228. Each power outlet 228 includes at least two electrical ports 270 (not all of which are labeled to increase the clarity of the drawing).

FIG. 62 illustrates a front view of the security system 202 after the security system 202 is mounted to a power outlet 228 by pressing electrical prongs that protrude from a backside of the security system 202 into electrical ports 270 of the power outlet 228.

FIG. 63 illustrates a side perspective view of the security system 202 just before the security system 202 is mounted to a power outlet 228 by pressing electrical prongs 274 that protrude from a backside 278 of the security system 202 into electrical ports 270 of the power outlet 228.

As shown in FIGS. 61-63, a security system 202 can include, among other things, an outer housing 224, a backside 278, and a detection system 211. The outer housing 224 is an outward 280 facing portion of the security system 202. The backside 278 is an inward 282 facing portion of the security system 202. The detection system 211 may include, among other things, a motion detector 209 and a camera assembly 208, the camera assembly 208 including at least a camera 215. The security system 202 can be configured to mount to a power outlet 228. The inwardly facing portion (backside 278) may have a first electrical prong 274 and a second electrical prong 274 that protrude into the power outlet 228 to mount the security system 202 to the power outlet 228. The power outlet 228 may mechanically support the security system 202. The outwardly facing portion (outer housing 224) may be configured to face away from the power outlet 228 (i.e. outward 280). The detection system 211 may be coupled to the outer housing 224 of the security system 202. The detection system 211 can include, among other things, a camera assembly 208 and a motion detector 209.

In several embodiments, the security system 202 may be communicatively coupled to a remote computing device such as a mobile phone. When the motion detector 209 detects a first motion, the security system 202 may be arranged and configured to send an alert to the remote computing device. The user may not want to receive alerts to the mobile device at all times of the day. For example, the user may not want alerts while at home. The security system 202 may be arranged and configured to send the alert to the remote computing device in response to the motion detector 209 detecting the first motion during a first predetermined time of day (i.e. during working hours). The security system 202 can be arranged and configured to not send the alert to the remote computing device in response to the motion detector 209 detecting a second motion during a second predetermined time of day.

In order to conserve energy and/or system memory, the security system 202 may have a sleep mode. When the camera 215 is in the sleep mode, the camera 215 may not capture images. The security system 202 may be arranged and configured to exit a sleep mode and enter a live view mode in response to the motion detector 209 detecting the first motion. When the camera 215 is in the live view mode the camera 215 can capture images. The camera 215 may be arranged and configured to exit a sleep mode and enter a live view mode in response to receiving a wireless request from the remote computing device. The wireless request may be sent in response to the user opening an app, pushing a button, turning on the mobile device, or another action. The camera 215 may be configured to record images in response to receiving the wireless request from the remote computing device.

In some embodiments the detection system 211 may include at least one of a microphone 213, a motion detector 209, and a speaker 217. The microphone 213 may start to record noise in response to the motion detector 209 detecting a motion. The microphone 213 may record noise in response to the occurrence of the security system 202 sending an alert to the remote computing device and/or the security system 202 receiving a wireless request from the remote computing device. The first electrical prong 274 and the second electrical prong 274 may be arranged and configured to receive electrical power from the power outlet 228 to power the security system 202. The security system 202 may include a camera lens. Different camera lenses may be selected to provide a different field of view. A fisheye lens 210 may be coupled to the outwardly facing portion 224 of the security system 202. The fisheye lens 210 may be arranged and configured to create a broader field of view for the camera 215.

In some embodiments a security system 202 may include an outwardly facing portion 224, an inwardly facing portion 278, and a detection system 211. The security system 202 may be configured to mount to a power outlet 228. The outwardly facing portion 224 may be configured to face away from the power outlet 228. The inwardly facing portion 278 may have a first electrical prong 274 and a second electrical prong 274 that protrude into the power outlet 228 to mount the security system 202 to the power outlet 228. The detection system 211 may be coupled to the outwardly facing portion 224. The detection system 211 may include a camera assembly 208 and a microphone 213. The camera assembly includes, at least, a camera 215.

In some embodiments, a remote computing device may be communicatively coupled to the security system 202. In response to the microphone 213 detecting a first noise, the security system 202 may be arranged and configured to send an alert to the remote computing device. A user may not always want to receive an alert to the remote computing device, for example when they are sleeping. The security system 202 may be arranged and configured to send the alert to the remote computing device in response to the microphone 213 detecting the first noise during a first predetermined time of day. For example the security system 202may send an alert to the remote computing device only during business hours. The security system may be arranged and configured to not send the alert to the remote computing device in response to the microphone 213 detecting a second noise during a second predetermined time of day.

A security system and camera running constantly may use a lot of power and/or memory. In order to conserve power and/or memory the security system and/or camera can enter a sleep mode in which less power and/or memory is used. When the camera 215 is in the sleep mode the camera 215 may be configured to not capture images. In several embodiments, the camera 215 may be arranged and configured to exit a sleep mode and enter a live view mode in response to the microphone 213 detecting the first noise. When the camera 215 is in the live view mode the camera 215 may be configured to capture images. The microphone 213 may be configured to record noise in response to receiving a wireless request from the remote computing device.

A fisheye lens 210 can be configured to provide a 180 degree side-to-side view of the room in which the power outlet 228 is located. In some embodiments, the fisheye lens 210 provides a 360 degree view.

One portion of the security system 202 faces inward 282 and one portion of the security system 202 faces outward 280. Inward and outward directions are shown by arrows in FIG. 63. Inward faces towards a wall (e.g., towards the power outlet 228). Outward faces away from the wall (e.g., away from the power outlet 228).

The security system 202b illustrated in FIGS. 64-67 is also configured to plug into a power outlet 228 (shown in FIG. 61). The camera assembly 208b can include a high-resolution, wide-viewing-angle lens. A long-range motion detector 218b can protrude through the outer housing 224b.

All of the embodiments described in the context of other security systems (e.g., security system 202) described herein and/or described in applications and/or patents incorporated by reference can be applied to the security systems 202, 202b, 202c, 202d, 202e shown in FIGS. 61-73. Some features are not labeled in FIGS. 61-73 to increase the clarity of labeled features.

This application claims the benefit of U.S. Provisional Patent Application No. 62/016,863; filed Jun. 25, 2014; and entitled WALL PLUG CAMERAS. The entire contents of Patent Application No. 62/016,863 are incorporated by reference herein.

FIG. 1 illustrates a remote surveillance system 200 (e.g., the security system 202 and the computing device 204). The remote surveillance system 200 can communicate via a server 206 and/or via wireless communication 230. The security system 202 is configured to mount to a power outlet 228 on a wall of a building.

FIG. 64 illustrates a remote surveillance system 200b, which can include a security system 202b and a remotely located computing device 204. The computing device 204 can be located remotely such that the computing device 204 is not mechanically or electrically coupled to the security system 202b (but can sometimes be in wireless communication with the security system 202b). In some embodiments, the remote surveillance system 200b does not include a remotely located computing device 204.

Referring now to FIGS. 65 and 66, the remote surveillance system can include an outwardly facing portion 642 configured to face away from the power outlet 228 (shown in FIG. 61). The system can also include an inwardly facing portion 644 having a first electrical prong 274 and a second electrical prong 274 that protrude into the power outlet to mount the inwardly facing portion to the power outlet. (Inward can be a direction towards the wall of the building.) A camera assembly 208b can be coupled to the outwardly facing portion 642. The camera assembly 208b can have a camera that faces outward. (Outward can mean away from the wall.) The camera can face directly outward (i.e., perpendicularly to the wall) or the camera can face outward at an angle (e.g., at an angle relative to the direction that is perpendicular to the wall).

As used herein, “outward” means in a direction away from a wall (but not necessarily in a direction perpendicular to the wall). “Inward” means in a direction towards a wall (but not necessarily in a direction perpendicular to the wall). In some embodiments, the camera faces directly outward from the wall (in a direction that is perpendicular to the wall). In several embodiments, the camera includes a pivot to enable changing the orientation of the camera relative to the wall and relative to the outwardly facing portion.

Referring now to FIGS. 11 and 64, the remote surveillance system 200b can include a wireless transmitter (e.g., the communication module 504) coupled to at least one of the outwardly facing portion and the inwardly facing portion. The remote surveillance system 200b can also include a remotely located computing device 204 that is in wireless communication with the wireless transmitter such that the wireless transmitter is configured to send a first picture taken by the camera assembly 208b to the remotely located computing device 204. The first picture can be a still picture or a part of a video.

FIG. 63 illustrates an embodiment in which the outwardly facing portion is coupled to the inwardly facing portion such that the outwardly facing portion is located directly over the power outlet 228. Once the prongs 274 of the security system 202 are inserted into the power outlet 228, the power outlet 228 can mechanically support each portion of the security system 202 (e.g., the outwardly facing portion and the camera assembly 208). FIG. 62 illustrates a power outlet (which is hidden by the security system 202) holding up the security system 202.

Referring now to FIGS. 67 and 68, the security system 202b includes a separable connection 646 configured to couple the outwardly facing portion 642 to the inwardly facing portion 644 such that the power outlet can mechanically support the camera assembly 208b (shown in FIG. 64). This approach can provide a very convenient and minimally invasive way to mount the security system 202b.

The separable connection 646 can be configured to enable decoupling the outwardly facing portion 642 from the inwardly facing portion 644 to mount the outwardly facing portion 642 in a location away from the power outlet (as shown in FIG. 70). For example, the outwardly facing portion 642 can be mounted several feet higher on the wall than the inwardly facing portion.

In several embodiments, the remote surveillance system further comprises a first mounting bracket 648. The first mounting bracket 648 can be inserted into the outward facing portion 642 such that the first mounting bracket 648 is coupled to an inward section of the outwardly facing portion 642. The first mounting bracket 648 can be configured to mount the outwardly facing portion 642 to the wall in the location away from the power outlet 228 (as shown in FIG. 70). The remote surveillance system can also include a second mounting bracket 650 coupled to the inwardly facing portion 644. The second mounting bracket 650 can be configured to couple the outwardly facing portion 642 to the inwardly facing portion 644 (e.g., while the first bracket 648 is hidden inside the outward portion 642).

As shown in FIGS. 68 and 69, the second mounting bracket 650 is coupled to an outward section of the inwardly facing portion 644. The first mounting bracket 648 can be located between the outwardly facing portion 642 and the inwardly facing portion 644 while the outwardly facing portion 642 is coupled to the inwardly facing portion 644 such that the power outlet 228 mechanically supports the camera assembly 208b (e.g., as shown in FIG. 71). As shown in FIGS. 67 and 71, the first mounting bracket 648 can be at least partially hidden between the outwardly facing portion 642 and the inwardly facing portion 644 while the outwardly facing portion 642 is located directly outward from the power outlet 228.

Referring now to FIGS. 67 and 69, the separable connection 646 comprises a first coupling member 652. The first mounting bracket 648 includes a second coupling member 654 that structurally matches the first coupling member 652, and in some cases, cosmetically matches the first coupling member. As used herein, “structurally matches” means that the structures are essentially the same (e.g., even if the structures have different cosmetic features such as colors, surface finishes, and ornamental features).

The separable connection 646 comprises at least one movable protrusion 662, which can be a screw or other fastener. The first bracket 648 and the second bracket 650 include a hole 664. The protrusion 662 can move up and down to go into either hole 664 to secure the outward portion 642 to either the first bracket 648 (e.g., when the first bracket 648 is mounted on a wall) or the second bracket 650 (e.g., to rigidly couple the outward portion 642 to the inward portion 644).

Moving the protrusion 662 can decouple the outwardly facing portion 642 from the inwardly facing portion 644. In some embodiments, the protrusion 662 is a screw and the holes 664 are threaded holes. As shown in FIG. 69, the movable protrusion 662 is oriented radially away from a direction 668 that is perpendicular to the wall such that the movable protrusion moves radially to decouple the outwardly facing portion 642 from the inwardly facing portion 644 (e.g., even if the movable protrusion 662 is not oriented perpendicularly to the direction 668 that is perpendicular to the wall).

Referring now to FIG. 68, several embodiments include a flexible electrical cable 656 that electrically couples the outwardly facing portion 642 to the inwardly facing portion 644 to provide electricity when the outwardly facing portion 642 is located away from the power outlet 228 (shown in FIG. 70). The electrical cable 656 can be at least 18 inches long (e.g., to enable mounting the camera higher on the wall than the power outlet). The housing can include the outward portion 642 and the inward portion 644. A majority of the cable 656 can be wrapped between the outwardly facing portion 642 and the inwardly facing portion 644 (e.g., in a cable storage area 658, which can be a hollow volume inside the housing).

The cable 656 can be wrapped around a protrusion 660 that extends outward (e.g., between sections of the outward portion 642 and the inward portion 644). The cable 656 can be wrapped around the protrusion 660 in the cable storage area 658.

In the embodiment illustrates in FIG. 68, at least a portion of the camera assembly 208b is located directly outward from the power outlet 228, which is not shown, but the prongs 274 are located at least partially inside the power outlet 228. A motion sensor 218b can be coupled to the outwardly facing portion 642. The remote surveillance system can be configured to record a video in response to detecting motion (e.g., using the motion sensor 218b). The inwardly facing portion 644 can include a transformer 670 configured to reduce an input voltage from the power outlet 228. A wireless transmitter (e.g., the communication module 504 shown in FIG. 11) can be electrically coupled to the inwardly facing portion 644. The wireless transmitter can be configured to send a video taken using the camera assembly 208b to a remotely located computing device.

The remote surveillance system can include a printed circuit board 516 and a wireless transmitter 504 (shown in FIG. 11) electrically coupled to the inwardly facing portion. The wireless transmitter 504 can be configured to send a video taken using the camera assembly 208b to a remotely located computing device. The printed circuit board 516 and the wireless transmitter 504 can be located within the housing 672 (labeled in FIG. 69).

FIG. 71 illustrates an embodiment with a button 212c that can be used to “ring” a chime and/or to initiate configuring at least one parameter of the security system 202c. The security system 202c is rigidly mounted to a power outlet that is partially hidden behind the security system 202c.

Any of the security system embodiments can be used with any of the methods described herein. Thus, structural elements described in the context of one embodiment can be applied to method embodiments described using other structural elements.

In some embodiments, a remote surveillance system comprises a remotely located computing device and a security system. The security system can comprise an outwardly facing portion having a camera assembly and an inwardly facing portion having a first electrical prong and a second electrical prong. Several methods include mounting the security system to a wall of a building by inserting the first electrical prong and the second electrical prong into a power outlet; using the camera assembly to take a first video while the outwardly facing portion is mechanically supported by the power outlet; and/or wirelessly sending the video to the remotely located computing device.

Several embodiments include decoupling the outwardly facing portion from the inwardly facing portion; attaching a mounting bracket to the wall; attaching the outwardly facing portion to the bracket while the inwardly facing portion is mechanically supported by the power outlet; and/or using the camera assembly to take a second video while the outwardly facing portion is mechanically supported by the bracket in a location away from the power outlet. Some methods include recording the first video in response to detecting a first motion, and recording the second video in response to detecting a second motion.

360-Degree Camera

FIG. 72 illustrates a security system 202d that includes a 360-degree camera assembly 208c (e.g., the camera 208c can see a complete panoramic view and/or can see a half-sphere). A cable 656c provides power from an electrical outlet to a base 674. The base 674 can charge the security system 202d. The security system 202d can be removed from the base 674 and relocated to a location that is remote relative to the base 674. The embodiment shown in FIG. 72 can be combined with any of the embodiments described herein and/or incorporated by reference.

Tabletop Camera

FIG. 73 illustrates a security system 202e that can be coupled to a dock 676. The dock 676 can hold the security system 202e such that the camera assembly 208b can have a field of view that is perpendicular to the ground. A cable 656c can provide power to the dock 676, which can charge the security system 202e. The embodiment shown in FIG. 73 can be combined with any of the embodiments described herein and/or incorporated by reference.

Detecting Nonmotion Events

As illustrated in FIGS. 1 and 61-71, the disclosure includes a security system 200 configured to mount to a power outlet 228. The system 200 can include a detection system 202 comprising a camera 215, motion detector 209, speaker 217, microphone 213, and a pair of electrical prongs 274 arranged and configured to protrude into the power outlet 228 to receive power for the detection system 202.

With specific reference to FIG. 1, the system 200 can include a remote computing device 204 communicatively coupled to the detection system 202. It should be appreciated that the remote computing device 204 can be remotely located with respect to the detection system 202.

The security system 200 can be arranged and configured to send an alert to the remote computing device 204 in response to the motion detector 209 detecting no motion. For example, if an elderly resident has an adverse medical event, such as a heart attack, and becomes immobilized, then the system 200 can detect and alert remote computing device(s) 204 that are communicatively coupled to the detection system 202.

To avoid the possibility of false positives, the system 202 can further be arranged and configured to send an alert to the remote computing device 204 in response to the motion detector 209 detecting no motion for at least a predetermined amount of time. The predetermined amount of time can be any amount of time, such as 1 minute, 10 minutes, 1 hour, 2 hours, and the like. In some embodiments, the system 200 emits a precorded message from the speaker 217 in response to the motion detector 209 detecting no motion for at least a predetermined amount of time.

Furthermore, the security system 200 can be arranged and configured to send an alert to the remote computing device in response to the motion detector 209 detecting no motion during a first predetermined time of day. For example, if a resident of the premises is usually at home and moving around during the day on a Sunday afternoon, then the system 200 can alert remote computing device(s) 204 if the motion detector 209 detects no motion during Sunday afternoons. Generally speaking, the first predetermined time of day can be any time, such as weekday afternoons, weekend evenings, every day from 6 pm to 9 pm, and any such desired time of day.

Accordingly, the security system 200 can be arranged and configured to not send an alert to the remote computing device 204 in response to the motion detector 209 detecting no motion during a second predetermined time of day. This is basically the opposite situation as described in the previous paragraph. For example, if the resident is usually asleep at 4 am and if the motion detector 209 detects no motion at 4 am, then the system 200 may not send the alert to the remote computing device 204 in response to the motion detector 209 not detecting motion at 4 am.

As illustrated in FIG. 71, the detection system 202 can include a button 212 that when pressed initiates a communication session with the remote computing device 204. In some embodiments, when the button 212 is pressed the camera 208 captures an image of an area adjacent the detection system 202. As well, the security system 200 may then send an image file to the remote computing device 204 whereby the image file represents the image captured by the camera 208.

Furthermore, in some embodiments, when the button 212 is pressed the microphone 213 records an audible sound from an area adjacent the detection system 202. Also, the security system 200 may send an audio file to the remote computing device 204 whereby the audio file represents the audible sound captured by the microphone 213.

Now with reference to FIG. 74, the disclosure includes a method of detecting a nonmotion event with a security system 200 mounted to a power outlet 228. The method can include detecting, via the motion detector 209, the nonmotion event. The nonmotion event can include an event whereby no movement is detected within a field of view of the motion detector 209 (at step 7400). The method can also include initiating a communication session between the detection system 202 and the remote computing device 204 in response to detecting the nonmotion event (at step 7402).

Methods may also include determining, via the security system 200, whether the nonmotion event has occurred for at least a predetermined amount of time (at step 7404). Accordingly, methods may also include initiating the communication session between the detection system 202 and the remote computing device 204 in response to determining that the nonmotion event has occurred for at least the predetermined amount of time (at step 7406). Furthermore, methods may also include emitting, via the speaker 217, a precorded message in response to the motion detector 209 detecting the nonmotion event for at least the predetermined amount of time (at step 7408).

Methods may even include detecting, via the microphone 213, an audible sound (at step 7410), and initiating the communication session between the detection system 202 and the remote computing device 204 in response to detecting the audible sound (at step 7500). In some embodiments, the audible sound comprises a response to the prerecorded message.

In some embodiments, methods may include determining, via the security system 200, whether the nonmotion event has occurred during a first predetermined time of day (at step 7502). Methods can also include initiating the communication session between the detection system 202 and the remote computing device 204 in response to determining that the nonmotion event has occurred during the first predetermined time of day (at step 7504).

Even still, methods may include determining, via the security system 200, whether the nonmotion event has occurred during a second predetermined time of day (at step 7506). Accordingly, methods may include not initiating a communication session between the detection system 202 and the remote computing device 204 in response to determining that the nonmotion event has occurred during a second predetermined time of day (at step 7508).

The disclosure also includes a method of detecting a nonmotion event with a security system 200 mounted to a power outlet 228. Methods can include determining, via the security system 200, that the button 212 has been pressed (at step 7600). In some embodiments, the method also includes initiating a communication session between the detection system 202 and the remote computing device 204 in response to determining that the button 212 has been pressed (at step 7602).

Methods may also include capturing, via the camera 208, an image of an area adjacent the detection system 202 in response to determining that the button 212 has been pressed (at step 7604) and transmitting an image file to the remote computing device 204 whereby the image file represents the image captured by the camera 208 (at step 7606). Additionally, methods may include recording, via the microphone 213, an audible sound from an area adjacent the detection system 202 in response to determining that the button 212 has been pressed (at step 7608) and transmitting an audio file to the remote computing device 204 whereby the audio file represents the audible sound captured by the microphone 213 (at step 7610).

In some embodiments, methods may include receiving, via the security system 200, an input from the remote computing device 204 (at step 7612). Accordingly, methods may include initiating the communication session between the detection system 202 and the remote computing device 204 in response to receiving the input from the remote computing device 204 (at step 7614).

Interpretation

None of the steps described herein is essential or indispensable. Any of the steps can be adjusted or modified. Other or additional steps can be used. Any portion of any of the steps, processes, structures, and/or devices disclosed or illustrated in one embodiment, flowchart, or example in this specification can be combined or used with or instead of any other portion of any of the steps, processes, structures, and/or devices disclosed or illustrated in a different embodiment, flowchart, or example. The embodiments and examples provided herein are not intended to be discrete and separate from each other.

The section headings and subheadings provided herein are nonlimiting. The section headings and subheadings do not represent or limit the full scope of the embodiments described in the sections to which the headings and subheadings pertain. For example, a section titled “Topic 1” may include embodiments that do not pertain to Topic 1 and embodiments described in other sections may apply to and be combined with embodiments described within the “Topic 1” section.

Some of the devices, systems, embodiments, and processes use computers. Each of the routines, processes, methods, and algorithms described in the preceding sections may be embodied in, and fully or partially automated by, code modules executed by one or more computers, computer processors, or machines configured to execute computer instructions. The code modules may be stored on any type of non-transitory computer-readable storage medium or tangible computer storage device, such as hard drives, solid state memory, flash memory, optical disc, and/or the like. The processes and algorithms may be implemented partially or wholly in application-specific circuitry. The results of the disclosed processes and process steps may be stored, persistently or otherwise, in any type of non-transitory computer storage such as, e.g., volatile or non-volatile storage.

The various features and processes described above may be used independently of one another, or may be combined in various ways. All possible combinations and subcombinations are intended to fall within the scope of this disclosure. In addition, certain method, event, state, or process blocks may be omitted in some implementations. The methods, steps, and processes described herein are also not limited to any particular sequence, and the blocks, steps, or states relating thereto can be performed in other sequences that are appropriate. For example, described tasks or events may be performed in an order other than the order specifically disclosed. Multiple steps may be combined in a single block or state. The example tasks or events may be performed in serial, in parallel, or in some other manner. Tasks or events may be added to or removed from the disclosed example embodiments. The example systems and components described herein may be configured differently than described. For example, elements may be added to, removed from, or rearranged compared to the disclosed example embodiments.

Conditional language used herein, such as, among others, “can,” “could,” “might,” “may,” “e.g.,” and the like, unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments include, while other embodiments do not include, certain features, elements and/or steps. Thus, such conditional language is not generally intended to imply that features, elements and/or steps are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without author input or prompting, whether these features, elements and/or steps are included or are to be performed in any particular embodiment. The terms “comprising,” “including,” “having,” and the like are synonymous and are used inclusively, in an open-ended fashion, and do not exclude additional elements, features, acts, operations and so forth. Also, the term “or” is used in its inclusive sense (and not in its exclusive sense) so that when used, for example, to connect a list of elements, the term “or” means one, some, or all of the elements in the list. Conjunctive language such as the phrase “at least one of X, Y, and Z,” unless specifically stated otherwise, is otherwise understood with the context as used in general to convey that an item, term, etc. may be either X, Y, or Z. Thus, such conjunctive language is not generally intended to imply that certain embodiments require at least one of X, at least one of Y, and at least one of Z to each be present.

The term “and/or” means that “and” applies to some embodiments and “or” applies to some embodiments. Thus, A, B, and/or C can be replaced with A, B, and C written in one sentence and A, B, or C written in another sentence. A, B, and/or C means that some embodiments can include A and B, some embodiments can include A and C, some embodiments can include B and C, some embodiments can only include A, some embodiments can include only B, some embodiments can include only C, and some embodiments include A, B, and C. The term “and/or” is used to avoid unnecessary redundancy.

While certain example embodiments have been described, these embodiments have been presented by way of example only, and are not intended to limit the scope of the inventions disclosed herein. Thus, nothing in the foregoing description is intended to imply that any particular feature, characteristic, step, module, or block is necessary or indispensable. Indeed, the novel methods and systems described herein may be embodied in a variety of other forms; furthermore, various omissions, substitutions, and changes in the form of the methods and systems described herein may be made without departing from the spirit of the inventions disclosed herein.

	Number	Date	Country
Parent	15292019	Oct 2016	US
Child	15615818		US
Parent	14861613	Sep 2015	US
Child	15292019		US
Parent	14714577	May 2015	US
Child	14861613		US
Parent	14623741	Feb 2015	US
Child	14714577		US
Parent	14813479	Jul 2015	US
Child	14861613		US
Parent	14623741	Feb 2015	US
Child	14813479		US

POWER OUTLET CAMERAS

Information

Publication Number

Date Filed

Date Published

Inventors

Original Assignees

CPC

International Classifications

Abstract

Description

Claims

CROSS-REFERENCE TO RELATED APPLICATIONS

Continuation in Parts (6)