US 9,113,052 B1Grant
Doorbell communication systems and methods
Issue Date:2015-08-18
•30 Claims
•8 Drawing Sheets
Abstract
Doorbell systems can be configurable to determine whether an emergency event has been initiated inside of a building to which the doorbell system is attached. In response to determining that the emergency event has been initiated, the doorbell system can activate an alert communication system to notify people located outside of the building.
Metadata
Assignee
- SkyBell Technologies, Inc.
Inventors
- Joseph Frank Scalisi
- Andrew Paul Thomas
Application Information
Application Number:US 14/684,302
Filing Date:2015-04-10
Priority Date:2015-02-03
Art Unit:2486
Classifications
IPC:
H04N7/18H04N9/47
Field of Search:
H04N 7/186H04N 7/188
Patent Drawings (8 sheets)
Description
Cross-Reference to Related Applications
[0001] This application claims the benefit of and is a continuation-in-part of U.S. Nonprovisional patent application Ser. No. 14/664,345; filed Mar. 20, 2015; and entitled DOORBELL COMMUNICATION SYSTEMS AND METHODS. The entire contents of patent application Ser. No. 14/664,345 are incorporated by reference herein.
[0002] This application claims the benefit of U.S. Provisional Patent Application No. 62/127,660; filed Mar. 3, 2015; and entitled DOORBELL COMMUNICATION SYSTEMS AND METHODS. The entire contents of Patent Application No. 62/127,660 are incorporated by reference herein.
[0003] This application claims the benefit of and is a continuation-in-part of U.S. Nonprovisional patent application Ser. No. 14/612,376; filed Feb. 3, 2015; and entitled DOORBELL COMMUNICATION SYSTEMS AND METHODS. The entire contents of patent application Ser. No. 14/612,376 are incorporated by reference herein.
[0004] U.S. Nonprovisional patent application Ser. No. 14/612,376 is a continuation-in-part of U.S. Nonprovisional patent application Ser. No. 14/589,830; filed Jan. 5, 2015; and entitled DOORBELL COMMUNICATION SYSTEMS AND METHODS. The entire contents of patent application Ser. No. 14/589,830 are incorporated by reference herein.
[0005] U.S. Nonprovisional patent application Ser. No. 14/589,830 is a continuation-in-part of U.S. Nonprovisional patent application Ser. No. 14/502,601; filed Sep. 30, 2014; and entitled DOORBELL COMMUNICATION SYSTEMS AND METHODS. The entire contents of patent application Ser. No. 14/502,601 are incorporated by reference herein.
[0006] U.S. Nonprovisional patent application Ser. No. 14/502,601 is a continuation-in-part of U.S. Nonprovisional patent application Ser. No. 14/492,809; filed Sep. 22, 2014; and entitled DOORBELL COMMUNICATION SYSTEMS AND METHODS; which claims the benefit of and is a continuation-in-part of U.S. Nonprovisional patent application Ser. No. 14/275,811; filed May 12, 2014; and entitled DOORBELL COMMUNICATION SYSTEMS AND METHODS (now U.S. Pat. No. 8,872,915); which claims the benefit of and is a continuation-in-part of U.S. Nonprovisional patent application Ser. No. 14/142,839; filed Dec. 28, 2013; and entitled DOORBELL COMMUNICATION SYSTEMS AND METHODS (now U.S. Pat. No. 8,842,180); which claims the benefit of and is a continuation-in-part of U.S. Nonprovisional patent application Ser. No. 14/099,888; filed Dec. 6, 2013; and entitled DOORBELL COMMUNICATION SYSTEMS AND METHODS (now U.S. Pat. No. 8,823,795); which claims the benefit of and is a continuation of U.S. Nonprovisional patent application Ser. No. 14/098,772; filed Dec. 6, 2013; and entitled DOORBELL COMMUNICATION SYSTEMS AND METHODS (now U.S. Pat. No. 8,780,201); which claims the benefit of U.S. Provisional Patent Application No. 61/872,439; filed Aug. 30, 2013; and entitled DOORBELL COMMUNICATION SYSTEMS AND METHODS; and also claims the benefit of U.S. Provisional Patent Application No. 61/859,070; filed Jul. 26, 2013; and entitled DOORBELL COMMUNICATION SYSTEMS AND METHODS. The entire contents of patent application Ser. No. 14/492,809; U.S. Pat. No. 8,872,915; U.S. Pat. No. 8,842,180; U.S. Pat. No. 8,823,795; U.S. Pat. No. 8,780,201; Patent Application No. 61/872,439; and Patent Application No. 61/859,070 are incorporated by reference herein.
[0007] The entire contents of the following application are incorporated herein by reference: International Application No. PCT/US14/53506; filed Aug. 29, 2014 with the U.S. Patent and Trademark Office; and entitled DOORBELL COMMUNICATION SYSTEMS AND METHODS.
[0008] The entire contents of the following application are incorporated herein by reference: International Application No. PCT/US14/47622; filed Jul. 22, 2014 with the U.S. Patent and Trademark Office; and entitled DOORBELL COMMUNICATION SYSTEMS AND METHODS.
Background
[0009] 1. Field
[0010] Various embodiments disclosed herein relate to doorbells. Certain embodiments relate to communication between a person near a doorbell and a person in another location.
[0011] 2. Description of Related Art
[0012] Homes, offices, and other buildings sometimes include communication and surveillance systems to enable friendly visitors to summon occupants of the buildings and to deter unwanted visitors. Communication and surveillance systems can include video cameras and doorbells.
[0013] Doorbells can enable a person located outside of an entry point, such as a door, to alert a person inside of an entry point that someone outside would like to talk to someone inside. Doorbells sometimes include a button located near a door, such as a front door, side door, or back door of a home, office, dwelling, warehouse, building, or structure. Doorbells are sometimes used near a gate or some other entrance to a partially enclosed area. Pushing the doorbell sometimes causes a chime or other alerting sound to be emitted. In some cases, this alerting sound can typically be heard within a short distance from the entry point or sound source. For example, a homeowner located remotely from her home likely would not be able to hear the alerting sound, and thus, would not be aware that someone is ringing her doorbell. Thus, there is a need for devices and methods to alert remotely located individuals that someone seeks the attention of the homeowner, tenant, building guardian, or steward.
Summary
[0014] This disclosure includes a method for using a doorbell system, wherein the doorbell system comprises a doorbell having an alert communication system. The method can comprise determining, by the doorbell, whether an emergency event has been initiated, and in response to determining that the emergency event has been initiated, activating the alert communication system.
[0015] In embodiments, the alert communication system comprises at least one of a light and a speaker, and wherein activating the alert communication system comprises at least one of illuminating the light and emitting a sound with the speaker.
[0016] The emergency event can comprise at least one of a fire, a gas leak, a break-in, elevated levels of smoke, elevated levels of radon, and elevated levels of carbon monoxide. The emergency event can be associated with a building. The doorbell can be attached to the building.
[0017] Methods can further comprise receiving a transmission from a communication system communicatively coupled to the doorbell. The communication system can be located remotely relative to the doorbell, and the transmission can comprise an indication that the emergency event has been initiated.
[0018] The transmission can be a second transmission and the indication can be a second indication, in such embodiments, receiving the second transmission from the communication system can occur in response to the communication system receiving a first transmission from a sensor communicatively coupled to the communication system. As well, the sensor can be located remotely relative to the communication system. The first transmission can comprise a first indication that the emergency event has been initiated.
[0019] Methods can further comprise receiving a first transmission from a first sensor communicatively coupled to the doorbell. The first sensor can be located remotely relative to the doorbell, and the first transmission can comprise a first indication that the emergency event has been initiated.
[0020] Methods can comprise receiving a second transmission from a second sensor communicatively coupled to the doorbell. The second sensor can be located remotely relative to both the doorbell and the first sensor, and the second transmission can comprise a second indication that a second emergency event has been initiated. Methods can also include determining, by the doorbell, whether a second emergency event has been initiated. In response to determining that the second emergency event has been initiated, methods can include activating the alert communication system.
[0021] In embodiments, the emergency event is a first emergency event. The alert communication system can comprise a light and a speaker. As well, activating the alert communication system in response to the first emergency event being initiated can comprise illuminating the light. Methods can also include determining, by the doorbell, whether a second emergency event has been initiated. In response to determining that the second emergency event has been initiated, methods can include emitting a sound with the speaker.
[0022] Methods can further comprise receiving a command to deactivate at least a portion of the alert communication system. In response to receiving the command to deactivate at least the portion of the alert communication system, methods can include deactivating at least the portion of the alert communication system.
[0023] In embodiments, the command to deactivate at least the portion of the alert communication system can comprise at least one of a button press and an audible predetermined message spoken by a user.
[0024] The doorbell can be communicatively coupled to a sensor remotely located with respect to the doorbell, and the sensor can comprise a first speaker that emits a first sound in response to the emergency event. Methods can further include receiving a button press, and then in response to the button press, methods can include turning off the first speaker so that the first speaker no longer emits the first sound.
[0025] Methods can further comprise initiating, by the doorbell, a communication session with a remote computing device. The communication session can comprise an indication that the emergency event that has been initiated.
[0026] The disclosure also includes a doorbell system comprising a doorbell. The doorbell can comprise an outer housing configurable to attach to a building and a visitor detection system coupled to the outer housing. The visitor detection system can comprise at least one of a button and a camera. The system can comprise an alert communication system coupled to the outer housing. The alert communication system can be configurable to activate in response to an initiation of an emergency event. The alert communication system can comprise at least one of a light and a speaker.
[0027] The alert communication system can comprise at least one of a speaker and a light. The speaker can be configurable to emit a sound in response to the initiation of the emergency event. The light can be configurable to illuminate in response to the initiation of the emergency event.
[0028] The doorbell system can further comprise a sensor communicatively coupled to the doorbell. The sensor can be located remotely relative to the doorbell, and the sensor can be configurable to determine whether the emergency event has been initiated.
[0029] The doorbell system can further comprise a communication system communicatively coupled to both the doorbell and the sensor. The communication system can be located remotely relative to both the doorbell and the sensor, and the communication system can be configurable to receive a transmission from the sensor to thereby determine whether the emergency event has been initiated.
[0030] In embodiments, the sensor comprises a smoke alarm. In embodiments, the sensor comprises a burglar alarm. In embodiments, the sensor comprises at least one of a radon sensor, a carbon monoxide sensor, a carbon dioxide sensor, a propane sensor, a methane sensor, a butane sensor, and a natural gas sensor.
[0031] The doorbell system can further comprise a remote computing device communicatively coupled to the doorbell. The doorbell can be configurable to initiate a communication session with the remote computing device. The communication session can comprise an indication that the emergency event that has been initiated.
[0032] The disclosure also includes a doorbell system comprising a doorbell having a button and a speaker. The doorbell can be configurable to attach to an exterior of a building. The doorbell system can also include a communication system located remotely relative to the doorbell and communicatively coupled to the doorbell and a first sensor located remotely relative to the communication system and communicatively coupled to the communication system. The first sensor can be configured to detect a first emergency event. The doorbell system can also comprise a first wireless communication regarding the first emergency event from the sensor to the communication system and a second wireless communication regarding the first emergency event from the communication system to the doorbell. The communication system can send the second wireless communication in response to receiving the first wireless communication. The doorbell system can also include a flashing light emitted from the doorbell in response to the second wireless communication.
[0033] The first sensor can comprises a smoke alarm and the first emergency event can comprise a smoke event. The first sensor can comprise a window detection sensor coupled to a window and the first emergency event can comprise a fracture of the window.
[0034] The doorbell system can further comprise a sound emitted from the doorbell in response to the second wireless communication, wherein the sound is configured to alert first responders. In embodiments, the sound comprises at least one word that communicates a nature of the first emergency event. In embodiments, the sound comprises at least one word that communicates a location of the first emergency event within the building.
[0035] The communication system can comprise a speaker, and the doorbell system can comprise an audio communication session initiated by pressing the button of the doorbell after the first sensor detects the first emergency event. The audio communication session can comprise audio recorded by the doorbell outside the building, wirelessly transmitted to the communication system, and emitted by the speaker of the communication system inside the building.
[0036] The disclosure also includes a doorbell system comprising a doorbell having a button and a speaker. The doorbell can be configurable to attach to an exterior of a building. The doorbell system can also include a smoke alarm located remotely relative to the doorbell and communicatively coupled to the doorbell, wherein the smoke alarm is configured to detect a smoke event.
[0037] The doorbell can further comprise a light that flashes in response to the smoke alarm detecting the smoke event. The doorbell can further comprise a speaker that emits a sound in response to the smoke alarm detecting the smoke event.
[0038] The embodiments described above include many optional features and aspects. Features and aspects of the embodiments can be combined.
Brief Description of the Drawings
[0039] 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.
[0040] FIG. 1 illustrates a front view of a communication system, according to some embodiments.
[0041] FIG. 2 illustrates a computing device running software, according to some embodiments.
[0042] FIG. 3 illustrates an embodiment in which a security system is connected to a building, according to some embodiments.
[0043] FIG. 4A illustrates a block diagram of a security system that is communicatively coupled to a communication system, according to some embodiments.
[0044] FIG. 4B illustrates a block diagram of various event detection devices that are communicatively coupled to a communication system, according to some embodiments.
[0045] FIG. 5 illustrates a flowchart of a method of monitoring for an event through a communication system, according to some embodiments.
[0046] FIG. 6 illustrates an example of various alarm types that may be used based on the certainty and severity of the event, according to some embodiments.
Detailed Description
[0047] 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.
[0048] 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.
[0049] 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
[0050] 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. Some communication systems allow an individual to hear, see, and talk with visitors who approach at least a portion of the communication system and/or press a button, such as a doorbell's button. 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.
[0051] FIG. 1 illustrates a front view of a communication system embodiment. The communication system 200 can include a security system 202 (e.g., a doorbell) 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 and a doorbell button 212. The camera assembly 208 can be a video camera, which in some embodiments is a webcam.
[0052] 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 300 to which the security system 202 is attached. 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.
[0053] As well, the security system 202 can include at least one speaker 488. The speaker 488 can be located along any portion of the security system 202. For example, the speaker 488 can be located within an inner portion of the security system 202 or along an outer portion of the security system 202. The speaker 488 can be any type of sound output device configured to emit sound, such as a digital speaker, an analog speaker, and the like.
[0054] Furthermore, the security system 202 (e.g., a doorbell) 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.
[0055] 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.
[0056] Wireless communication 230 can enable the security system 202 (e.g., a doorbell) 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).
[0057] 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.
[0058] 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.
[0059] FIG. 2 illustrates a computing device 204 running software. 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).
[0060] 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 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.
[0061] 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. 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.
[0062] 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 less than every 10 minutes; at least every 24 hours and/or less than every 60 minutes; or at least every hour and/or less than every second.
[0063] 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.
[0064] In several embodiments, a user can log into 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.
[0065] 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).
[0066] 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.
[0067] 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).
[0068] In some embodiments, buttons include diverse means of selecting various options, features, and functions. Buttons can be selected by mouse clicks, keyboard commands, and touching a touch screen. Many embodiments include buttons that can be selected without touch screens.
[0069] 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 the data transmitted from the security system 202 to the computing device 204 and/or from the computing device 204 to the security system 202.
[0070] 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.
[0071] 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.
[0072] In some embodiments, a button 276 is both an answer button (to accept a communication request from a visitor) and is 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.
[0073] 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.
[0074] Some method embodiments include detecting a visitor with a security system. The methods can include causing the user interface 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.
[0075] 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.
[0076] In several embodiments, the security device 202 can be configured to record 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 and/or audio records when the security device 202 detected movement and/or the presence of a person.
[0077] 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 be a doorbell with 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.
[0078] 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 conversations with visitors 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.
[0079] 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. A door lock 250 can be configured to lock and unlock the 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.
[0080] 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.
[0081] 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.
[0082] In some embodiments, the security system 202 can communicate (e.g., wirelessly 230) with a television 306, which can be a smart television. Users can view the television 306 to see a visitor and/or talk with the visitor.
Alert Communication Embodiments
[0083] Embodiments of the security system 202 can be configured to alert individuals located outside of a building (e.g. a home). For example, the security system 202 can be configured to flash a light, emit a sound (e.g. alternating high pitch and low pitch sounds), initiate a communication session with a remote computing device 204, and the like. These various alerts can be useful to individuals, such as first responders, seeking to identify the location of an event, such as an emergency event(s) occurring within or outside the home. Home, as used herein, may refer to a building whereby one or more occupants sleep in the building on a permanent basis. Home may distinguishable from an office building by the lack of permanent occupants that sleep in the office building. Home may refer to an apartment building due to the permanent nature of an occupant for the duration of a lease. Home may be distinguishable from a hotel due to the lack of permanent occupants.
[0084] FIG. 4A illustrates an embodiment in which a security system 202 is communicatively coupled to a communication device 416. The security system 202 may be part of a communication system 400. The communication system 400 can be similar to that of the communication system 200 except, the communication system 400 may also be configured to allow communication between the security system 202 and the communication device 416.
[0085] In various embodiments, the security system 202 can be communicatively coupled, directly and/or via the cloud, to a communication device 416, such as a hub device, a communication system, and/or an event detection device 418, such as a sensor, (e.g., a peripheral device, such as a Nest Protect® (registered by Google Inc.), Nest Learning Thermostat® (registered by Google Inc.), DropCam® (registered by Google Inc.), and the like. The communication device 416, event detection device 418 and/or the security system 202 can be used to monitor various events within the building 300 (e.g., home). Specifically, the communication device 416 and/or event detection device 418 can detect emergency events and then notify the security system 202. In some embodiments, the communication device 416 is communicatively coupled to the event detection device 418 that detects the emergency event or adverse event (which is discussed further herein). In this manner, the security system 202 may directly or indirectly receive a notification of the emergency event from the event detection device 418 and/or the communication device 416.
[0086] The security system 202 can communicate with the communication device 416 via a communication network 414. The communication network 414 can be similar to the wireless communication 230, however, the communication network 414 can be wired or wireless. In embodiments, the communication network 414 can utilize the existing electrical wires in the doorbell wires to communicate with the security system 202 (e.g., powerline networking). The communication network 414 can also utilize a wired Local Area Network. In embodiments, the communication network 414 can include a Wide Area Network (WAN) that connects the communication device 416 to the security system 202 over the Internet.
[0087] In embodiments, the communication device 416 is a type of device that is configured to connect multiple devices and facilitate communication between the multiple devices. The security system 202 may be a device that also is communicatively coupled to the communication device 416. The communication device 416 may receive a transmission from one device (i.e., an event detection device 418), make a determination on what type of communication to perform (e.g., an alert), and transmit the communication to a second device (e.g., the security system 202) to take further action.
[0088] The security system 202 can be configured to communicate with remote computing devices (i.e., the computing device 204). The computing device 204 may refer to a remote computing device in embodiments. The security system 202 can initiate a communication session through the communication network 414 by sending a request to the computing device 204 to establish a secure connection (e.g., a virtual private network) to enhance security. In embodiments, the communication session may also include an indication that an event (as discussed further herein) has been initiated.
[0089] The security system 202 can have an outer housing 224. The outer housing 224 may be configurable to attach to a building 300. The outer housing 224 of the security system 202 can attach to the building 300 using a variety of permanent or temporary mounting mechanisms. In embodiments, the permanent mounting mechanism may prevent the removal of the security system 202. The building 300 may include a variety of structures. For example, the building 300 includes a home, which is a type of building 300. The home can include various types of structures in various square footages. For example, a home can be a wooden framed building with an exterior of stucco, brick, or siding. In embodiments, a home can be distinguished from other types of buildings based on the livable area (e.g., 500 square feet to 5000 square feet). In embodiments, a home can also be defined as being a freestanding structure without shared walls. A home may also be defined by zoning constraints. For example, the home may be zoned residential instead of commercial or industrial.
[0090] The outer housing 224 can also include a visitor detection system 412 coupled to the outer housing 224. The visitor detection system 412 can be an assembly of components that are collectively configured to detect visitors in the immediate vicinity (e.g., within 0.5 to 50 feet) of the security system 202. The visitor detection system 412 can include the doorbell button 212, the camera assembly 208, and an audio input device 410. In addition, the visitor detection system 412 can also include the motion detector 218 and fingerprint sensor 210. The audio input device 410 can be a device that captures audio (e.g., a microphone). The audio input device 410 can have various sensitivity ranges depending on the application. In embodiments, the audio input device 410 can include multiple microphones to extend the coverage area of audio capture. For example, the audio input device can have one microphone on board the outer housing 224 and receive input from another microphone located within the house (e.g., through the communication network 414).
[0091] The outer housing 224 may also include a deactivation unit 411. The deactivation unit 411 can be a component that is communicatively coupled to the security system 202. The deactivation unit 411 may be responsible for disabling the alert communication system 402. In embodiments, the deactivation unit 411 is part of the alert communication system 402. The alert communication system 402 may work passively or actively. In an active configuration, the security system 202 can actively monitor for a command to deactivate. For example, the security system 202 can send “activation status requested” signal to a deactivation unit 411 in regular intervals along with a unique randomized code and receive an “activation=True” signal from the deactivation unit 411 along with the unique randomized code. When communication is interrupted, then a non-response of the activation status may indicate “activation=True”. When deactivated, the deactivation unit 411 transmits an “activation=False” signal along with the unique randomized code. The actively monitoring for the command can be advantageous where communication is lost with the deactivation unit 411 (i.e., the communication is modified or the deactivation is spoofed by an intruder).
[0092] The deactivation unit 411 may also passively monitor for the command. For example, an occupant may input a command through the deactivation unit 411 that is transmitted to the security system 202. The security system 202 can receive the command passively. In embodiments, the deactivation unit 411 may also be communicatively coupled with a remote computing device 204. The deactivation command may originate from the remote computing device 204 to deactivate the alert communication system 402 in either actively or passively.
[0093] The outer housing 224 can also include an alert communication system 402 coupled to the outer housing 224. The alert communication system 402 can be configurable to activate in response to an initiation of an event. For example, an alert from the communication device 416 that is transmitted to the security system 202 can activate various components on the security system 202 through the alert communication system 402. The alert communication system 402 can include components to communicate alerts to a user (e.g., an occupant of the home). In embodiments, the alert communication system 402 is the security system 202 or part of the security system 202. In embodiments, the alert communication system 402 includes a light 406 and a speaker 404. In embodiments, the alert communication system 402 refers to a collection of components for the purpose of alerting an occupant of the building 300. The alert communication system 402 can also refer to a control unit for the components that alert an occupant of the building 300. The control of the alert communication system 402 can be separate from the control for the security system 202. In embodiments, the alert communication system 402 is attached to an exterior surface of the home (i.e., a building 300). The outer housing 224 may be attached to an interior surface of the home (i.e., a building 300). The remote computing device 204 can be operated by the homeowner (i.e., a type of occupant).
[0094] The speaker 404 of the alert communication system 404 can be configured to emit a sound in response to the initiation of the event. For example, if the communication device 416 transmits an alert that indicates an emergency, then the security device 202 can emit a sound in the speaker 404 that indicates danger. The speaker 404 can be configured to emit a wide-range of sounds and various decibel levels depending on the application. For example, a more severe alert can be louder than a less severe alert. The security system 202 can alert an occupant of suspicious smoke by saying the location of the smoke and the time the smoke was detected.
[0095] The speaker 404 can simply emit a voice that says “Danger, Danger, Danger” to alert an occupant of the building 300. The sound emitted by the security device 202 can be unique to the type of alert. For example, if a fire alert is transmitted by the communication device 416, then the security device 202 can emit a voice that says “Fire, Fire, Fire” and repeats at a set interval. Various sounds can also be used to selectively alert other occupants. For example, a high frequency sound of 24 kHz to 45 kHz can selectively alert canine occupants of the building 300 without alerting a human. In another example, a sound from 17 kHz to 23 kHz may selectively alert children but not adults. Various patterns of sounds can also be produced. For example, the “SOS” Morse code pattern may be used to indicate distress.
[0096] The light 406 of the security system 202 may be configurable to illuminate in response to the initiation of the event. The light 406 can emit a variety of colors in a variety of patterns. For example, the light 406 can emit both a green light, a white light, and a red light. A green light can be lit during normal operation. A white light color can be used for ordinary alerts, such as a power outage. A red light color can be used to indicate an imminent emergency that alerts the occupant to leave the building 300 immediately. For example, the red light color can be used to alert the occupant of a gas leakage or a fire or armed intruders.
[0097] In embodiments, the light 406 can flash at various frequencies to indicate a pattern. For example, three short flashes, followed by three long flashes, followed by three short flashes, can indicate distress. While rapid flashes can indicate a higher priority than slower flashes of light. The light 406 can be coordinated with the speaker 404. For example, the light 406 can flash at the same time that the speaker 404 makes a sound. The light 406 can also flash before or after the emission of sound from the speaker 404.
[0098] The alert communication system 402 can also include emission of an odor. The odor can be discernable by an occupant to know that something is wrong or can ward away an intruder. For example, if the communication device 416 alerts the security system 202 of an intruder, then a strong smell (such as that of a skunk) can trigger a silent alarm. Various smells can be used. For example, flowery odors can be used for non-urgent alerts (such as a water leak) while mercaptan-based odors can be used for urgent alerts.
[0099] The alert communication system 402 can include remote communication 407. The remote communication 407 can be responsible for communicating with a remote computing device 204 the status of the alarm. In embodiments, the remote communication 407 can be a module that communicates with a security monitoring service, which can also have a dedicated communication channel that is different than the communication network 414 in order to alert authorities in the event of a power outage.
[0100] In embodiments, the security system 202 is powered by an electrical power input 408. The electrical power input 408 can be a battery. The electrical power input 408 can also be from an electrical source such as from a household Alternating Current. The electrical power input 408 can also be configured to receive a step-down voltage (e.g., around 8V to 24V) from doorbell wires 304. The alert communication system 402 may be electrically coupled to the electrical wires 409 (through the electrical power input 408). The electrical wires 409 can be configurable to be coupled to the doorbell wires 304 of a home (e.g., the building 300). The alert communication system 402 can be configurable to activate in response to a determination that an event has been initiated through the electrical wires 409. In embodiments, the communication can happen over powerline networking. Various spikes in electrical signals from the electrical wires 409 can also signal the alert communication system 402. In embodiments, a lack of electrical signal from the electrical wires 409 can also activate the alert communication system 402. For example, the lack of electrical power input 408 from the electrical wires 409 can activate the alert communication system 402. The alert communication system 402 can further utilize a backup battery system through the electrical power input 408 and cause the light 406 to emit white colored light so that an occupant can see.
[0101] The security system 202 may be configured as a passive or active device. As a passive device, the security system 202 may receive notifications of emergency events from the communication device and/or the event detection device 418. For example, a smoke detector event detection device 418 can transmit a smoke event to the communication device, which may communicate to the security system 202 an indication that the smoke event is occurring. The security system 202 can be monitoring for notifications from the communication device whenever a communication channel is established.
[0102] As an active device, the security system 202 may be configured to actively monitor whether the communication device and/or event detection device 418 has detected the occurrence or initiation of an emergency event (or adverse event). For example, the security system 202 can periodically request from the communication device a status of events. If there is no status, then the security system 202 can wait until another request is filled.
[0103] FIG. 4B illustrates a block diagram of an enhanced view of various event detection devices 418, according to some embodiments. The event detection devices 418 can be communicatively coupled to the communication device. Types of event detection device 418 can include a smoke alarm 420 or a burglar alarm 422. The event detection device 418 can be configured to communicate with a communication device or to the remote device 204 through the communication network 414. In embodiments, the event detection device 418 can be “smart” and communicate with a variety of devices. The event detection device 418 can connect via the Internet of Things (IoT) and may each have a unique network identifier. The IoT may encompass various standards. For example, standards may include ALLJOYN® (Registered by Qualcomm Innovation Center Inc.), Thread Group, IEEE® (Registered by the Institute of Electronic and Electrical Engineers, Inc.) P2413 working group, IoTivity® (Registered by Samsung Electronics Co., Ltd.), or Representational State Transfer.
[0104] The security system 202 may comprise an alert communication system 402 that may include a light 406, a speaker 404, and a wireless communication system 230 that may be configured to initiate a transmission with a remote computing device 204. For example, the communication device may comprise a smart smoke detector 420 (e.g. Nest Protect®, registered by Google Inc.), and in response to the smart smoke detector detecting elevated levels of smoke 434, or elevated levels of other toxic gases, the security system 202 may activate its alert communication system 402 (e.g. flashing a light and/or emit a sound). This may thereby alert individuals outside the home as to the location of the home where the emergency event is occurring.
[0105] As well, it should be appreciated that the emergency event can comprise any type of event 424 that may require the attention of another party. As used, event can refer to an emergency event or an adverse event, which indicates harm to an occupant or requires the attention of a party other than the occupant. For example, the emergency event may comprise at least one of a fire 426, a gas leak 428, a break-in 436, elevated levels of smoke 434, elevated levels of radon 432, elevated levels of carbon monoxide 430, and the like.
[0106] The alert communication system 402 can be configured to alert individuals located outside the home in any variety of ways. For example, the alert communication system 402 can flash a bright light emitting diode and/or a light located behind the doorbell button 212, such as the diagnostic light 216, on the security system 202. In some examples, the alert communication system 402 can emit a loud sound from the speaker 404. For example, the loud sound can be alternating high and low pitch sounds that may be heard by individuals located within 300 feet of the home. The high and low pitch sounds can be of high and low frequencies that may be heard by individuals located within a neighboring home and/or a vehicle passing by. The loud sound can be a unique sound easily detectable by individuals. As well, the sound can comprise a noise that indicates danger or help is required.
[0107] Furthermore, the alert communication system 402 can be configured to initiate a transmission to a remote computing device 204. For example, if the security system 202 determines that a break-in has occurred, the security system 202 may initiate a computing session and/or a notification with the remote computing device 204 to alert an individual that is operating the remote computing device 204 of the break-in 436 at the home. As well, it should be appreciated that the security system 202 can initiate a transmission to any other party, such as an emergency dispatcher (e.g. 911).
[0108] The security system 202 may be configured to activate its alert communication system 402 after a predetermined amount of time. The predetermined amount of time may be 0 seconds, 10 seconds, 20 seconds, 1 minute, and the like. Generally, it should be appreciated that the alert communication system 402 may activate nearly at the same time as the communication device 416 detecting the emergency event 424 or any time thereafter.
[0109] FIG. 5 illustrates a flowchart of a method 500 of monitoring for an event through a communication device 416, according to some embodiments. The method 500 can generally involve connecting to a communication device 416 and receiving a notification of an event from the communication device 416. The security system 202 can react based on the event from the communication system. The method 500 begins at block 510.
[0110] In block 510, the security system 202 can establish a connection with the communication system. As mentioned herein, the communication device 416 may utilize either a wired or wireless connection 230 to communicate with the security system 202. For example, a wireless home network that utilizes Wi-Fi may be used or local Bluetooth™ pairing may be used. Once connection is established, then the communication device 416 may be configured to only communicate with security system 202 at the ID provided by the security system 202. For example, the security system 202 may have a unique IPv6 address that the communication device 416 transmits to. The communication device 416 may also have a unique IPv6 address that the security system 202 transmits to. The security system 202 may also be configured to receive alerts from only the IPv6 address that belongs to the communication device 416, thus preventing spoofing type alarms. Various permissions may be set up using an Application Programming Interface (API) of the communication device 416. For example, the security system 202 can be set up as a client with read/write permissions which identifies the security system 202 that has permission to share data with the communication device 416.
[0111] In block 512, the security system 202 may monitor for an event. In embodiments, the security system 202 monitors for an event from the communication device 416. For example, the communication device 416 may receive a notification of an event from an event detection device 418. In embodiments, the security system 202 can monitor for an event using localized components. For example, the security system 202 may have a camera that is used to monitor for suspicious activity. The event may be communicated with the communication device 416 and the communication device 416 may take appropriate action (e.g., notify emergency services). As mentioned herein, the types of events may be selected from at least one of a fire, a gas leak, a break-in, elevated levels of smoke, elevated levels of radon, elevated levels of carbon monoxide, and the like.
[0112] The event detection device 418 may detect an event using a variety of methods. For example, various thresholds may be employed to detect an event 424. For example, the elevated levels of smoke event 434 can be based off of optical obscuration or electrostatic precipitation. The smoke can be based off of a threshold of parts per million or percentage of optical transmittance. The radon event 432 can be based off of PicoCuries per Liter reading from a radon detection unit. The gas leak event 428 can be based off of an 80% Lower Explosive Limit. Various gas detectors can be used (e.g., electrochemical, infrared point, infrared imaging, semiconductor, ultrasonic, holographic, etc.). A fire event 426 may be detected using temperature or a combination of readings from a smoke event 434 and a carbon monoxide event 430. The break-in event 436 may utilize various sensors present in the security system 202 or external sensors to the security system 202 (e.g., motion sensors). The event 424 is associated with a home (i.e., building 300), and the doorbell (i.e., security system 202) is attached to the home of a homeowner.
[0113] In block 514, the security system 202 can determine whether an event has been initiated. The event may be initiated whenever the security system 202 receives a transmission from a communication device 416 communicatively coupled to the security system. The transmission may be over various forms of communication and provide an indication that the event has been initiated. The security system 202 may monitor the communication system to detect whether the event has been initiated. In embodiments, the security system 202 (e.g., the doorbell) can interface with a remote computing device 204 to further communicate to an occupant that there is an alert at the home. Communicating via the remote computing device 204 may have the benefit of keeping occupants informed while away from the home. The security device 202 can establish a communication session with a remote computing device 204 in a similar manner as to the communication device 416. The communication session may include an indication that the event that has been initiated. For example, an occupant can receive a communication of a fire alert on a local application on their remote computing device 204 from the security system 202.
[0114] In block 516, the security system 202 can determine the alarm type. In embodiments, block 516 may be optional. Despite a variety of devices available to the security system 202, not all devices or tools may be appropriate in certain settings. For example, a non-urgent alert (such as elevated radon levels) may not warrant a high-pitched, high-volume noise in the middle of the night. The security system 202 can balance the severity of the alert with the certainty for the alert. For example, significant amounts of dust can trigger a smoke detector but the certainty of a fire can be determined using a carbon monoxide detector in conjunction with the smoke detector. The severity of a fire may be high but if the certainty that a fire is occurring is low, then the security system 202 can determine that another alarm type is more appropriate. Examples of determining an alarm type are described further herein.
[0115] In block 518, the security system 202 can activate the alert communication system 402 in response to determining that the event has been initiated in block 514. In embodiments, activating the alert communication system 402 can include activating selected components of the alert communication system 402 (e.g., the speaker 404 or the light 406). As mentioned herein, the alert communication system 402 can include a light 406 which, when the alert communication system 402 is activated, can cause the light 406 to illuminate in a variety of patterns and colors. The alert communication system 402 can also include a speaker 404 that emits a sound in a variety of intensities, frequencies, and patterns. The activating can also include activating a control element for the alert communication system 402. The control element for the alert communication system 402 can instigate a variety of patterns and alerts for multiple components (e.g., a flashing light followed by emission of selected sound frequencies).
[0116] In block 520, once the alert communication system 402 is activated, the security system 202 can monitor for a command to deactivate the alert communication system 402. In embodiments, block 520 may be optional. For example, a user of the security system 202 may not desire the security system 202 to alert occupants (e.g., a false positive). The command can be a sequence of instructions that is understood by the security system 202 to deactivate the alert communication system 402. In embodiments, the command can be a button press and an audible predetermined message. For example, an occupant can push a button (e.g., the door bell button 220) and speak an audible predetermined message such as “Alarm Deactivate” to deactivate the alert communication system 402. In various embodiments, the deactivation unit 411 can be configured to perform vocal recognition in order to distinguish between the voice of the occupant with the voice of a non-occupant, such as a prowler. Once the command is received, then the method 500 can continue to operation 522.
[0117] In block 522, the security system 202 can deactivate the alert communication system 402 in response to receiving the command to deactivate the alert communication system. The alert communication system 402 may be deactivated in a variety of ways. For example, the alert communication system 402 may deactivate (e.g. turn off the current alert) in response to the security system 202 receiving an indication that the doorbell button 212 has been pressed. In some embodiments, the security system 202 may be configured to turn off the alert communication system 402 in response to receiving an audible predetermined message, such as a spoken safety message or a spoken password that indicates that the event is being attended to or has ended. In some embodiments, the security system 202 can receive a deactivation command from the remote computing device 204. In this manner, the individual operating the remote computing device 204 may send a command through the remote computing device 204 to terminate the ongoing alert. The deactivation of the alert communication system 402 can include selectively deactivating less than all of the components of the alert communication system 402. For example, the deactivating of the alert communication system 402 can include deactivating only the localized communication (i.e., the speaker 404 and the light 406) but not the remote communication 407 with law enforcement (e.g., a silent alarm).
[0118] FIG. 6 illustrates an example table 600 of various alarm types that are used based on the certainty and severity of the event, according to some embodiments. The table 600 can correspond to block 516 in FIG. 5 where a security system 202 can determine the alarm type. In embodiments, the alarm type may be pre-assigned depending on the certainty and the severity of the event. For example, an occupant may desire that a gas leak is always associated with an audible alarm and a red light, despite a low certainty.
[0119] The alarm type can also be based on threshold values. For example, if the certainty of a fire is 20% but the severity is high, the security system 202 can create a score that is based on the severity and the certainty. The security system 202, based on the score, can determine the type of alarm. For example, a high severity event with a low certainty may (such as the fire) may be associated with a sound to invite an occupant to investigate further. A high severity event such as a gas leak but with a higher certainty may trigger a red flash along with the sound. A low severity event such as a baby crying can trigger a different set of alarm types such as playing comforting music.
Interpretation
[0120] 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.
[0121] 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.
[0122] 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.
[0123] 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.
[0124] 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.
[0125] 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.
[0126] 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.
Claims
The following is claimed:
1. A method of operating a doorbell system comprising a doorbell, wherein the doorbell comprises a button and an alert system having at least one of a light and a speaker, the method comprising:
determining, by the doorbell system, whether an emergency event has been initiated; and
activating the alert system in response to determining that the emergency event has been initiated.
2. The method of claim 1, wherein activating the alert system comprises at least one of illuminating the light and emitting a sound from the speaker.
3. The method of claim 1, further comprising determining, by the doorbell system, whether the emergency event comprises at least one of a fire, a gas leak, a break-in, elevated levels of smoke, elevated levels of radon, and elevated levels of carbon monoxide, wherein the emergency event is associated with a building, and wherein the doorbell is attached to the building.
4. The method of claim 1, further comprising receiving, by the doorbell system, a transmission from a communication system communicatively coupled to the doorbell and remotely located relative to the doorbell, the transmission comprising an indication that the emergency event has been initiated.
5. The method of claim 4, wherein the transmission is a second transmission and the indication is a second indication, wherein receiving, by the doorbell system, the second transmission from the communication system occurs in response to the communication system receiving a first transmission from a sensor communicatively coupled to the communication system and remotely located relative to the communication system, the first transmission comprising a first indication that the emergency event has been initiated.
6. The method of claim 1, further comprising receiving, by the doorbell system, a first transmission from a first sensor communicatively coupled to the doorbell, wherein the first sensor is and remotely located relative to the doorbell, and wherein the first transmission comprises a first indication that the emergency event has been initiated.
7. The method of claim 6, further comprising:
receiving, by the doorbell system, a second transmission from a second sensor communicatively coupled to the doorbell and remotely located relative to both the doorbell and the first sensor, the second transmission comprising a second indication that a second emergency event has been initiated; and
in response to the doorbell system receiving the second transmission, activating the alert system.
8. The method of claim 1, wherein the emergency event is a first emergency event, wherein the alert system comprises a light and a speaker, and wherein activating the alert system comprises illuminating the light, the method further comprising:
determining, by the doorbell system, whether a second emergency event has been initiated; and
emitting a sound from the speaker in response to determining that the second emergency event has been initiated.
9. The method of claim 1, further comprising:
receiving, by the doorbell system, a deactivation command; and
deactivating at least one of the light and the speaker in response to the doorbell system receiving the deactivation command.
10. The method of claim 9, wherein the deactivation command comprises at least one of a button press and an audible message spoken by a user.
11. The method of claim 1, wherein the doorbell is communicatively coupled to a sensor remotely located with respect to the doorbell, and wherein the sensor comprises a first speaker that emits a first sound in response to the emergency event, the method further comprising:
receiving a button press with the button; and
deactivating the first speaker so that the first speaker no longer emits the first sound in response to the button press.
12. The method of claim 1, further comprising initiating, by the doorbell system, a communication session with a remote computing device communicatively coupled to the doorbell system, wherein the communication session comprises an indication that the emergency event that has been initiated.
13. A doorbell system comprising a doorbell, wherein the doorbell comprises:
a housing;
a button coupled to the housing;
an alert system coupled to the housing, the alert system comprising at least one of a light and a speaker; and
an alert emitted by the alert system in response to an initiation of an emergency event.
14. The doorbell system of claim 13, wherein the alert comprises at least one of a sound emitted by the speaker and an illumination emitted by the light.
15. The doorbell system of claim 13, further comprising a sensor communicatively coupled to the doorbell and remotely located relative to the doorbell, the sensor configured to determine whether the emergency event has been initiated.
16. The doorbell system of claim 15, further comprising a communication system communicatively coupled to both the doorbell and the sensor, wherein the communication system is located remotely relative to both the doorbell and the sensor, and wherein the communication system is configurable to receive a transmission from the sensor to thereby determine whether the emergency event has been initiated.
17. The doorbell system of claim 15, wherein the sensor comprises a smoke alarm.
18. The doorbell system of claim 15, wherein the sensor comprises a burglar alarm.
19. The doorbell system of claim 15, wherein the sensor comprises at least one of a radon sensor, a carbon monoxide sensor, a carbon dioxide sensor, a propane sensor, a methane sensor, a butane sensor, and a natural gas sensor.
20. The doorbell system of claim 13, further comprising:
a remote computing device communicatively coupled to the doorbell system; and
a communication session between the doorbell system and the remote computing device, wherein the communication session comprises an indication that the emergency event that has been initiated.
21. A doorbell system, comprising:
a doorbell having a button, a light, and a speaker;
a communication system communicatively coupled to the doorbell and remotely located relative to the doorbell;
a first sensor communicatively coupled to the communication system and remotely located relative to the communication system, wherein the first sensor is configured to detect a first emergency event;
a first wireless communication received by the communication system, wherein the first wireless communication comprises a notification of the first emergency event;
a second wireless communication received by the doorbell after the communication system receives the first wireless communication, wherein the second wireless communication comprises a notification of the first emergency event; and
an illumination emitted from the light in response to the doorbell receiving the second wireless communication.
22. The doorbell system of claim 21, wherein the first sensor comprises a smoke alarm and the first emergency event comprises a smoke event.
23. The doorbell system of claim 21, wherein the first sensor comprises a window detection sensor coupled to a window of a building and the first emergency event comprises a fracture of the window.
24. The doorbell system of claim 21, further comprising a sound emitted from the speaker in response to the doorbell receiving the second wireless communication.
25. The doorbell system of claim 24, wherein the sound comprises at least one word that communicates a nature of the first emergency event.
26. The doorbell system of claim 24, wherein the sound comprises at least one word that communicates a location of the first emergency event within the building.
27. The doorbell system of claim 21, wherein the communication system comprises a speaker, and the doorbell system comprises an audio communication session initiated by pressing the button of the doorbell after the first sensor detects the first emergency event, wherein the audio communication session comprises audio recorded by the doorbell that is wirelessly transmitted to the communication system, and emitted by the speaker of the communication system.
28. A doorbell system, comprising:
a doorbell having a button and a speaker; and
a smoke alarm communicatively coupled to the doorbell and remotely located relative to the doorbell, wherein the smoke alarm is configurable to detect a smoke event.
29. The doorbell system of claim 28, wherein the doorbell further comprises a light that flashes in response to the smoke alarm detecting the smoke event.
30. The doorbell system of claim 28, wherein the speaker emits a sound in response to the smoke alarm detecting the smoke event.
Patent Citations (159)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US3708742(A) | 1973-01-01 | Gunn | Applicant |
| US4523193(A) | 1985-06-01 | Levinson | Applicant |
| USD283130(S) | 1986-03-01 | Boenning | Applicant |
| USD297222(S) | 1988-08-01 | Rauch | Applicant |
| US4843461(A) | 1989-06-01 | Tatsumi | Applicant |
| US5428388(A) | 1995-06-01 | Von Bauer | Applicant |
| US5493618(A) | 1996-02-01 | Stevens | Applicant |
| US5521578(A) | 1996-05-01 | Delvalle | Applicant |
| USD371086(S) | 1996-06-01 | Collins | Applicant |
| USD381638(S) | 1997-07-01 | Kruse | Applicant |
| US5784446(A) | 1998-07-01 | Stuart | Applicant |
| USD404673(S) | 1999-01-01 | Gordon | Applicant |
| US5995139(A) | 1999-11-01 | Lee | Applicant |
| US6028626(A) | 2000-02-01 | Aviv | Applicant |
| USD421727(S) | 2000-03-01 | Pierson | Applicant |
| USD422521(S) | 2000-04-01 | Morrow | Applicant |
| US6073192(A) | 2000-06-01 | Clapp | Applicant |
| US6094213(A) | 2000-07-01 | Mun | Applicant |
| US6185294(B1) | 2001-02-01 | Chornenky | Applicant |
| US6226031(B1) | 2001-05-01 | Barraclough | Applicant |
| US6429893(B1) | 2002-08-01 | Xin | Applicant |
| US6590604(B1) | 2003-07-01 | Tucker | Applicant |
| US6661340(B1) | 2003-12-01 | Saylor | Applicant |
| US6727811(B1) | 2004-04-01 | Fendis | Applicant |
| US6753899(B2) | 2004-06-01 | Lapalme | Applicant |
| US6778084(B2) | 2004-08-01 | Chang | Applicant |
| USD500751(S) | 2005-01-01 | Yukikado | Applicant |
| USD501652(S) | 2005-02-01 | Pierson | Applicant |
| US7015943(B2) | 2006-03-01 | Chiang | Applicant |
| USD519100(S) | 2006-04-01 | Shioya | Applicant |
| USD522490(S) | 2006-06-01 | Yukikado | Applicant |
| USD525963(S) | 2006-08-01 | Yukikado | Applicant |
| US7113578(B2) | 2006-09-01 | Unger | Applicant |
| USD531160(S) | 2006-10-01 | Yukikado | Applicant |
| US7193644(B2) | 2007-03-01 | Carter | Applicant |
| USD562306(S) | 2008-02-01 | Jeong | Applicant |
| US7330649(B2) | 2008-02-01 | Finizio | Applicant |
| USD577301(S) | 2008-09-01 | Johnson | Applicant |
| US7429924(B2) | 2008-09-01 | Langer | Applicant |
| US7477134(B2) | 2009-01-01 | Langer | Applicant |
| US7492303(B1) | 2009-02-01 | Levitan | Applicant |
| USD588574(S) | 2009-03-01 | Takahata | Applicant |
| USD595260(S) | 2009-06-01 | Takahata | Applicant |
| US7583191(B2) | 2009-09-01 | Zinser | Applicant |
| US7738917(B2) | 2010-06-01 | Ryley | Applicant |
| US7746223(B2) | 2010-06-01 | Howarter | Applicant |
| US7752070(B2) | 2010-07-01 | Hatcher | Applicant |
| US8016676(B2) | 2011-09-01 | Carter | Applicant |
| US8139098(B2) | 2012-03-01 | Carter | Applicant |
| US8144183(B2) | 2012-03-01 | Carter | Applicant |
| US8144184(B2) | 2012-03-01 | Carter | Applicant |
| US8154581(B2) | 2012-04-01 | Carter | Applicant |
| US8164614(B2) | 2012-04-01 | Carter | Applicant |
| USD660819(S) | 2012-05-01 | Chen | Applicant |
| US8193919(B2) | 2012-06-01 | Langer | Applicant |
| US8504103(B2) | 2013-08-01 | Ficquette | Applicant |
| USD689828(S) | 2013-09-01 | Pierson | Applicant |
| US8562158(B2) | 2013-10-01 | Chien | Applicant |
| US8565399(B2) | 2013-10-01 | Siminoff | Applicant |
| USD692847(S) | 2013-11-01 | Barley | Applicant |
| US8669876(B2) | 2014-03-01 | Anderson | Applicant |
| USD707147(S) | 2014-06-01 | Crippa | Applicant |
| US8780201(B1) | 2014-07-01 | Scalisi et al. | Applicant |
| USD710727(S) | 2014-08-01 | Siminoff | Applicant |
| USD710728(S) | 2014-08-01 | Siminoff | Applicant |
| USD711275(S) | 2014-08-01 | Scalisi | Applicant |
| US8823795(B1) | 2014-09-01 | Scalisi et al. | Applicant |
| US8842180(B1) | 2014-09-01 | Kasmir et al. | Applicant |
| US8872915(B1) | 2014-10-01 | Scalisi et al. | Applicant |
| US8937659(B1) | 2015-01-01 | Scalisi et al. | Applicant |
| US8941736(B1) | 2015-01-01 | Scalisi | Applicant |
| US8953040(B1) | 2015-02-01 | Scalisi et al. | Applicant |
| US2003/0025599(A1) | 2003-02-01 | Monroe | Applicant |
| US2004/0085205(A1) | 2004-05-01 | Yeh | Applicant |
| US2004/0085449(A1) | 2004-05-01 | Millet | Applicant |
| US2004/0086093(A1) | 2004-05-01 | Schranz | Applicant |
| US2004/0178889(A1) | 2004-09-01 | Buckingham | Applicant |
| US2004/0229569(A1) | 2004-11-01 | Franz | Applicant |
| US2004/0257336(A1) | 2004-12-01 | Hershkovitz | Applicant |
| US2005/0007451(A1) | 2005-01-01 | Chiang | Applicant |
| US2005/0097248(A1) | 2005-05-01 | Kelley | Applicant |
| US2005/0285934(A1) | 2005-12-01 | Carter | Examiner |
| US2005/0285944(A1) | 2005-12-01 | Watanabe | Applicant |
| US2006/0010504(A1) | 2006-01-01 | Sharma | Applicant |
| US2006/0093187(A1) | 2006-05-01 | Mittal | Applicant |
| US2006/0100002(A1) | 2006-05-01 | Luebke | Applicant |
| US2006/0139449(A1) | 2006-06-01 | Cheng | Applicant |
| US2006/0152365(A1) | 2006-07-01 | Kim | Applicant |
| US2006/0156361(A1) | 2006-07-01 | Wang | Applicant |
| US2006/0271678(A1) | 2006-11-01 | Jessup | Applicant |
| US2007/0126574(A1) | 2007-06-01 | Langer | Applicant |
| US2007/0194945(A1) | 2007-08-01 | Atkinson | Applicant |
| US2008/0036862(A1) | 2008-02-01 | Lang | Applicant |
| US2008/0128586(A1) | 2008-06-01 | Johnson | Applicant |
| US2008/0167072(A1) | 2008-07-01 | Berstis | Applicant |
| US2008/0198225(A1) | 2008-08-01 | Gal et al. | Examiner |
| US2008/0297339(A1) | 2008-12-01 | Mathews | Applicant |
| US2009/0059002(A1) | 2009-03-01 | Kim | Applicant |
| US2009/0072963(A1) | 2009-03-01 | Langer | Applicant |
| US2009/0093235(A1) | 2009-04-01 | Grealish | Applicant |
| US2009/0141939(A1) | 2009-06-01 | Chambers | Applicant |
| US2009/0284578(A1) | 2009-11-01 | Carter | Applicant |
| US2009/0296641(A1) | 2009-12-01 | Bienas | Applicant |
| US2010/0087161(A1) | 2010-04-01 | Young | Applicant |
| US2010/0103300(A1) | 2010-04-01 | Jones | Applicant |
| US2010/0195810(A1) | 2010-08-01 | Mota | Applicant |
| US2010/0245060(A1) | 2010-09-01 | Tylicki | Applicant |
| US2010/0276570(A1) | 2010-11-01 | Moser | Applicant |
| US2011/0121940(A1) | 2011-05-01 | Jones | Examiner |
| US2011/0207509(A1) | 2011-08-01 | Crawford | Applicant |
| US2011/0287718(A1) | 2011-11-01 | Abel | Applicant |
| US2012/0027248(A1) | 2012-02-01 | Feris | Applicant |
| US2012/0044049(A1) | 2012-02-01 | Vig | Applicant |
| US2012/0044050(A1) | 2012-02-01 | Vig et al. | Examiner |
| US2012/0098439(A1) | 2012-04-01 | Recker | Applicant |
| US2012/0108215(A1) | 2012-05-01 | Kameli | Applicant |
| US2012/0113253(A1) | 2012-05-01 | Slater | Applicant |
| US2012/0162416(A1) | 2012-06-01 | Su | Applicant |
| US2012/0229282(A1) | 2012-09-01 | Zagami | Applicant |
| US2012/0230203(A1) | 2012-09-01 | Casey | Applicant |
| US2012/0262581(A1) | 2012-10-01 | Carter | Applicant |
| US2012/0280783(A1) | 2012-11-01 | Gerhardt | Applicant |
| US2012/0280789(A1) | 2012-11-01 | Gerhardt | Applicant |
| US2012/0280790(A1) | 2012-11-01 | Gerhardt | Applicant |
| US2012/0287123(A1) | 2012-11-01 | Starner | Applicant |
| US2012/0327246(A1) | 2012-12-01 | Senior | Applicant |
| US2013/0045763(A1) | 2013-02-01 | Ruiz | Applicant |
| US2013/0057695(A1) | 2013-03-01 | Huisking | Applicant |
| US2013/0094444(A1) | 2013-04-01 | Lai | Applicant |
| US2013/0128050(A1) | 2013-05-01 | Aghdasi | Applicant |
| US2013/0130749(A1) | 2013-05-01 | Andersen | Applicant |
| US2013/0136033(A1) | 2013-05-01 | Patil | Applicant |
| US2013/0147964(A1) | 2013-06-01 | Frank | Applicant |
| US2013/0169809(A1) | 2013-07-01 | Grignan | Applicant |
| US2013/0169814(A1) | 2013-07-01 | Liu | Applicant |
| US2013/0173477(A1) | 2013-07-01 | Cairns | Applicant |
| US2013/0208123(A1) | 2013-08-01 | Lakhani | Applicant |
| US2013/0223279(A1) | 2013-08-01 | Tinnakornsrisuphap | Applicant |
| US2013/0293722(A1) | 2013-11-01 | Chen | Applicant |
| US2014/0088761(A1) | 2014-03-01 | Shamlian | Applicant |
| US2014/0125754(A1) | 2014-05-01 | Haywood | Applicant |
| US2014/0149706(A1) | 2014-05-01 | Shim | Applicant |
| US2014/0253725(A1) | 2014-09-01 | Hsu | Examiner |
| US2015/0022618(A1) | 2015-01-01 | Siminoff | Applicant |
| US2015/0022620(A1) | 2015-01-01 | Siminoff | Applicant |
| US2015/0029335(A1) | 2015-01-01 | Kasmir et al. | Applicant |
| US2015/0049191(A1) | 2015-02-01 | Scalisi et al. | Applicant |
| US2015/0054949(A1) | 2015-02-01 | Scalisi | Applicant |
| US2015/0061859(A1) | 2015-03-01 | Matsuoka | Applicant |
| US2015/0063559(A1) | 2015-03-01 | Siminoff | Applicant |
| US2015/0070495(A1) | 2015-03-01 | Scalisi | Applicant |
| US2015/0092055(A1) | 2015-04-01 | Scalisi et al. | Applicant |
| CN1902609 | 2010-05-01 | Applicant | |
| CN202872976 | 2013-04-01 | Applicant | |
| CN202939738 | 2013-05-01 | Applicant | |
| EP684743 | 1999-07-01 | Applicant | |
| GB2400958 | 2005-12-01 | Applicant | |
| WO1/93220 | 2001-12-01 | Applicant | |
| WO2007111802 | 2007-10-01 | Applicant |
Non-Patent Literature (71)
- iDoorCam—A Wi-Fi Enabled, Webcam Doorbell—Downloaded on Sep. 3, 2013 from http://www.idoorcam.com/.Applicant
- Squaritz IDS—Intelligent Doorbell System—Downloaded on Aug. 15, 2013 from http://www.indiegogo.com/projects/squaritz-ids-intelligent-doorbell-system.Applicant
- Wireless Video Doorbell Pager—Downloaded on Aug. 9, 2013 from http://www.indiegogo.com/projects/wireless-video-doorbell-pager--4.Applicant
- Lockitron—Downloaded on Jul. 24, 2013 from https://lockitron.com/preorder.Applicant
- Eyetalk for Home—Downloaded May 24, 2013 from http://www.revolutionaryconceptsinc.com/forhome.html.Applicant
- DoorBot—Downloaded on Jul. 26, 2013 from http://www.getdoorbot.com.Applicant
- Langer Doorbell Button Sized Light—Downloaded on Sep. 16, 2013 from http://www.youtube.com/watch?v=u9nNCm4tSYI.Applicant
- Langer Doorbell Light—Downloaded on Sep. 16, 2013 from http://www.youtube.com/watch?v=6dbU-Gyjgx8.Applicant
- SmartBell on Kickstarter—Downloaded on Feb. 28, 2014 from http://www.kickstarter.com/projects/1256599792/smartbell-wi-fi-doorbell-for-video-chats-to-ios-an.Applicant
- DefenDoor by Glate LLC—Downloaded on Dec. 11, 2014 from https://www.kickstarter.com/projects/85455040/defendoor-a-home-security-system-that-syncs-with-y.Applicant
- Notifi by Chamberlain—Downloaded on Jan. 9, 2015 from http://www.cnet.com/products/chamberlain-notifi-video-door-chime/.Applicant
- i-Bell—Downloaded on Jan. 13, 2015 from https://www.kickstarter.com/projects/729057054/i-bell.Applicant
- Dropcam—Downloaded on Jan. 19, 2015 from https://www.dropcam.com/dropcam-pro.Applicant
- DoorBird—Downloaded on Jan. 23, 2015 from http://www.doorbird.com/.Applicant
- Chui Doorbell—Downloaded on Jan. 23, 2015 from http://www.getchui.com/.Applicant
- Chui Doorbell—Downloaded on Jan. 23, 2015 from http://techcrunch.com/2014/04/18/214-technologies-is-crowdfunding-a-smart-doorbell-called-chui/.Applicant
- GoPano—Downloaded on Jan. 23, 2015 from http://www.gizmag.com/gopano-micro-captures-360-degree-video-on-iphone/18542/.Applicant
- Sengled Snap Light Camera—Downloaded on Mar. 9, 2015 from http://www.sengled.com/product/snap.Applicant
- Alarm.com Garage Door Camera—Downloaded on Mar. 9, 2015 from http://www.cnet.com/au/products/alarm-com-for-apple-watch/.Applicant
- Rollup iHome peephole doorbell—Downloaded on May 7, 2015 from http://www.rollupcn.com.Applicant
- Ring Chime—Smart Chime—Downloaded on May 13, 2015 from http://techcrunch.com/2015/05/13/rings-smart-doorbell-gets-a-smart-speaker/#.y0xlqx:SpqY.Applicant
- Peeple—Peephole Camera—Downloaded on May 14, 2015 from https://www.kickstarter.com/projects/1544392549/peeple-caller-id-for-your-front-door/video—share.Applicant
- Vivant Doorbell Camera—Downloaded on May 20, 2015 from http://www.vivint.com/company/newsroom/press/Vivint-Introduces-Wi-Fi-Enabled-Doorbell-Camera-into-Its-Smart-Home-Platform.Applicant
- Doorbot—Downloaded on Nov. 18, 2013 from http://www.craigncompany.com/home-tech-doorbot/; prior art publication at least as of Jun. 10, 2013.Applicant
- Doorbot—Downloaded on Nov. 18, 2013 from http://thenextweb.com/insider/2012/12/10/satisfaction-lies-in-hardware-for-siminoffs-christie-street-platform-and-doorbot-video-streaming-doorbell/; prior art publication at least as of Dec. 10, 2012.Applicant
- Doorbot—Downloaded on Nov. 18, 2013 from http://www.digitaltrends.com/lifestyle/doorbot-camera-see-visitors-smartphone/; prior art publication at least as of Dec. 9, 2012.Applicant
- Doorbot website—Downloaded on Nov. 18, 2013 from http://www.getdoorbot.com/.Applicant
- Doorbot users manual—Downloaded on Nov. 18, 2013 from http://static.mydoorbot.com/DoorBot%20Users%20Manual%201.0.pdf.Applicant
- Doorbot “fact sheet”—Downloaded on Nov. 18, 2013 from http://cdn.shopify.com/s/files/1/0247/6501/files/DoorBotMediaKit.pdf?17037.Applicant
- Doorbot “features kit”—Downloaded on Nov. 18, 2013 from http://cdn.shopify.com/s/files/1/0247/6501/files/DoorBot—Features—Kit.pdf?17037.Applicant
- CellNock index page—Originally downloaded on Sep. 23, 2013 from http://cellnock.com/index.html; The website says CellNock is “patent pending”.Applicant
- CellNock about founder page—downloaded on Nov. 18, 2013 from http://cellnock.com/index.html; The website says CellNock is “patent pending”.Applicant
- CellNock learn more page—Downloaded on Nov. 18, 2013 from http://cellnock.com/learn—more.htm; The website says CellNock is “patent pending”.Applicant
- CellNock product page—Downloaded on Nov. 18, 2013 from http://cellnock.com/products.htm; The website says CellNock is “patent pending”.Applicant
- Philips InSight Baby Monitor—Originally downloaded on Jul. 24, 2013 from http://www.amazon.com/Philips-B120-37-InSight-Wireless/dp/B00AALO9Z6/ref=sr—1—3?ie=UTF8&qid=1384808431&sr=8-3&keywords=philips+insight.Applicant
- MySkyBell.com—Part 1 (previously iDoorCam.com)—Downloaded on Nov. 18, 2013 from http://www.myskybell.com/.Applicant
- MySkyBell.com—Part 2 (previously iDoorCam.com)—Downloaded on Nov. 18, 2013 from http://www.myskybell.com/.Applicant
- MySkyBell.com—Part 3 (previously iDoorCam.com)—Downloaded on Nov. 18, 2013 from http://www.myskybell.com/.Applicant
- MySkyBell.com—Part 4 (previously iDoorCam.com)—Downloaded on Nov. 18, 2013 from http://www.myskybell.com/.Applicant
- MySkyBell.com—Part 5 (previously iDoorCam.com)—Downloaded on Nov. 18, 2013 from http://www.myskybell.com/.Applicant
- Squaritz IDS Doorbell System—Downloaded on Aug. 15, 2013 from http://www.indiegogo.com/projects/squaritz-ids-intelligent-doorbell-system.Applicant
- MyBells—Downloaded on Nov. 18, 2013 from http://www.indiegogo.com/projects/mybells-the-smart-bells.Applicant
- EyeTalk for home—Downloaded on May 2013 from http://www.revolutionaryconceptsinc.com/forhome.html.Applicant
- EyeTalk Product—Downloaded on Nov. 18, 2013 from http://www.revolutionaryconceptsinc.com/eyetalk.html.Applicant
- Langer Doorbell Light—Downloaded on Nov. 18, 2013 from http://www.youtube.com/watch?v=u9nNCm4tSYI; published at least as early as Apr. 2013.Applicant
- SmartBell—Downloaded on Dec. 5, 2013 from http://smartbell.co/This—is—smartbell.html.Applicant
- SmartBell—Downloaded on Dec. 5, 2013 from http://smartbell.co/Tech—specs.html.Applicant
- SmartBell—Downloaded on Dec. 5, 2013 from http://smartbell.co/FAQ.html.Applicant
- SmartBell—A Doorbell for Smartphones, published by Scrambled Brains Tech, LLC., Oct. 1, 2013.Applicant
- August Smart Lock—Part 1—Downloaded on Jun. 10, 2014 from www.August.com.Applicant
- August Smart Lock—Part 2—Downloaded on Jun. 10, 2014 from www.August.com.Applicant
- August Smart Lock—Part 3—Downloaded on Oct. 10, 2014 from www.August.com.Applicant
- Kevo Lock—User guide—Downloaded on Jun. 10, 2014 from http://s7d5.scene7.com/is/content/BDHHI/Kwikset/Website%20Content/Kevo/kevo-userguide-kwikset—eng.pdf.Applicant
- Kevo Lock—Installation guide—Downloaded on Oct. 10, 2014 from http://s7d5.scene7.com/is/content/BDHHI/Kwikset/Website%20Content/Kevo/installation—guide.pdf.Applicant
- Schlage Electronic Lock—User guide—Downloaded on Jun. 10, 2014 from www.schlage.com.Applicant
- Lock-Style Solenoid—Downloaded on Aug. 22, 2014 from www.AdaFruit.com.Applicant
- Power Matters Alliance—Downloaded on Aug. 23, 2014 from www.wikipedia.com.Applicant
- Push-Pull Solenoid—Downloaded on Aug. 22, 2014 from www.AdaFruit.com.Applicant
- Push-Pull Solenoid—Technical Details—Downloaded on Aug. 22, 2014 from www.AdaFruit.com.Applicant
- Qi—Downloaded on Aug. 23, 2014 from www.wikipedia.com.Applicant
- TP-Link—Website—Downloaded on Jul. 15, 2014 from www.tp-link.us.Applicant
- TP-Link—User guide—Downloaded on Jul. 15, 2014 from www.tp-link.us.Applicant
- AC Adapter Spy Camera—Downloaded on Jun. 24, 2014 from ahdcameras.com.Applicant
- FanFare Chime—Downloaded on Oct. 10, 2014 from https://www.kickstarter.com/projects/1040187373/1919517395?token=47099d90.Applicant
- Ring Video Doorbell—Downloaded on Oct. 10, 2014 from www.ring.com.Applicant
- Doorboot becomes Ring—Downloaded on Oct. 10, 2014 from http://techcrunch.com/2014/09/29/doorbot-ring-home-security-doorbell/?ncid=rss&utm—source=feedburner&utm—medium=feed&utm—campaign=Feed.Applicant
- iChime Customizable Digital Chime System—Downloaded on Nov. 7, 2014 from http://www.ichime.com/.Applicant
- Philips InSight Wireless HD Baby Monitor—Downloaded on Jul. 24, 2013 from http://www.amazon.com/Philips-InSight-Wireless-Baby-Monitor/dp/B00AALO9Z6/ref=sr—1—2?ie=UTF8&qid=1374704204&sr=8-2&keywords=philips+insight+wi-fi+baby+monitor.Applicant
- CellNock—Downloaded on Sep. 23, 2013 from http://cellnock.com/products.htm.Applicant
- CellNock Index—Downloaded on Sep. 23, 2013 from http://cellnock.com/index.html.Applicant
- DoorBot—Downloaded on Jun. 14, 2013 from https://christiestreet.com/products/doorbot.Applicant