US 9,196,133 B2Grant
Doorbell communication systems and methods
Issue Date:2015-11-24
•31 Claims
•23 Drawing Sheets
Abstract
Doorbell systems can include a doorbell having a speaker and a microphone. Doorbell systems can receive a custom message from a user. Doorbell systems can thereby detect an indication of a presence of a visitor, and then in response to detecting the indication of the presence of the visitor, doorbell systems can emit the custom message with the speaker.
Metadata
Assignee
- SkyBell Technologies, Inc.
Inventors
- Joseph Frank Scalisi
- Gregory Saul Harrison
- Desiree Mejia
- Andrew Paul Thomas
Application Information
Application Number:US 14/695,436
Filing Date:2015-04-24
Priority Date:2013-08-30
Art Unit:2486
Classifications
IPC:
H04N7/18H04N9/47G08B3/10
Field of Search:
G08B 13/00H04M 11/025H04M 1/0291H04N 7/186H04N 7/183H04N 7/188H04L 12/2803H04L 12/282H04L 12/2818G06F 17/30247
Patent Drawings (23 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/684,302; filed Apr. 10, 2015; and entitled DOORBELL COMMUNICATION SYSTEMS AND METHODS. The entire contents of patent application Ser. No. 14/684,302 are incorporated by reference herein.
[0002] 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.
[0003] 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.
[0004] 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.
[0005] 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.
[0006] 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.
[0007] 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.
[0008] 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.
[0009] 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
[0010] 1. Field
[0011] Various embodiments disclosed herein relate to doorbells. Certain embodiments relate to communication between a person near a doorbell and a person in another location.
[0012] 2. Description of Related Art
[0013] 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.
[0014] 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
[0015] This disclosure includes a method for emitting a custom message with a doorbell system, wherein the doorbell system comprises a doorbell having a speaker. The may method comprise: receiving a custom message with the doorbell system; and detecting, by the doorbell, an indication of a presence of a visitor, and then in response to detecting the indication of the presence of the visitor, emitting the custom message with the speaker.
[0016] The visitor may be a predetermined visitor and the method may further comprise assigning, by the doorbell system, the custom message to the predetermined visitor.
[0017] Methods may include determining, by the doorbell system, that the visitor is a predetermined visitor type, and selecting the custom message from a first message and a second message in response to determining that the visitor is the predetermined visitor type. As well, methods may include downloading the custom message from a smart phone that is communicatively coupled to the doorbell system.
[0018] The doorbell system may further comprise a remote computing device, and methods may further comprise recording the custom message with the remote computing device.
[0019] The doorbell may further comprise a microphone and a button, and methods may further comprise receiving an indication of a button press of the button, and then in response to receiving the button press, recording the custom message with the microphone.
[0020] The doorbell system may be operated by a homeowner and the visitor may be included on a contact list of the homeowner, and wherein the custom message may comprise a name of the visitor.
[0021] The doorbell may comprise a microphone, and wherein the custom message may comprise a question. Methods may further comprise receiving, by the microphone, an audible response to the question as spoken by the visitor.
[0022] Methods may further comprise determining, by the doorbell system, whether the audible response spoken by the visitor comprises a first meaning or a second meaning that is different from the first meaning; in response to determining that the audible response spoken by the visitor comprises the first meaning, emitting a first response message with the speaker; and in response to determining that the audible response spoken by the visitor comprises the second meaning, emitting a second response message with the speaker, wherein the second response message is different from the first response message.
[0023] The visitor may comprise a criminal, and the custom message may comprise a warning message. Methods may further comprise initiating, by the doorbell system, a communication session with a law enforcement agency.
[0024] Methods may include initiating, by the doorbell system, a communication session with a remote computing device of the visitor, wherein the communication session comprises a written message that substantially matches a content of the custom message.
[0025] The disclosure also includes a method for emitting a custom message with a doorbell system, wherein the doorbell system comprises a doorbell having a speaker. The method may comprise detecting, by the doorbell, an indication of a presence of a visitor; and determining, by the doorbell system, an occurrence of a predetermined condition and then in response to detecting the indication of the presence of the visitor and determining the occurrence of the predetermined condition, emitting the custom message with the speaker. Methods may also include recording the custom message with the doorbell system.
[0026] The custom message may be a first custom message, and the doorbell may be attached to a building that is occupied by a resident. As well, determining, by the doorbell system, the occurrence of the predetermined condition may comprise determining whether the resident is located within the building or whether the resident is not located within the building. Methods may further comprise recording a second custom message with the doorbell system, wherein the second custom message is different from the first custom message; in response to both detecting the indication of the presence of the visitor and determining the resident is present within the building, emitting the first custom message with the speaker; and in response to both detecting the indication of the presence of the visitor and determining the resident is not present within the building, emitting the second custom message with the speaker.
[0027] The doorbell system may further comprise a remote computing device. Methods may further include recording the custom message with the remote computing device. The doorbell may comprise a microphone, and methods may further comprise recording the custom message with the microphone.
[0028] The doorbell may further comprise a button. As well, methods may further comprise receiving an indication of a first button press of the button, and then in response to receiving the first button press, recording the custom message with the doorbell system and thereby storing the custom message within memory of the doorbell system; and receiving an indication of a second button press of the button, and then in response to receiving the second button press, erasing the custom message from the memory of the doorbell system.
[0029] The predetermined condition may comprise at least one of a predetermined timeframe and a predetermined time of day. The doorbell may be attached to a building occupied by a resident. The predetermined timeframe may comprise a time during which the resident is hosting a party within the building. As well, the custom message may comprise a welcome message to the party.
[0030] The custom message can be a second custom message, and the doorbell can comprise a microphone. Methods can further comprise recording a first custom message with the microphone, wherein the first custom message can be spoken by a first voice, wherein the second custom message emitted by the speaker can be spoken by a second voice, and wherein a content of the first custom message substantially matches a content of the second custom message.
[0031] Methods can further include taking, by the doorbell, a picture of the visitor, wherein determining the occurrence of the predetermined condition can comprise determining, based on the picture, that the visitor is included in a database of suspicious visitors that previously visited other doorbells.
[0032] Methods can further include creating a schedule of a first timeframe to emit a first sound, a second timeframe to emit a second sound, and a third timeframe to emit a third sound, wherein determining the occurrence of the predetermined condition can comprise determining that a visitation time of the visitor is within the first timeframe, and emitting the custom message comprises emitting the first sound in response to determining that the visitation time of the visitor is within the first timeframe.
[0033] The disclosure also includes a doorbell system, comprising: a doorbell including a button, a speaker and a microphone, wherein the doorbell is configurable to attach to an exterior of a building, and wherein the button is configurable to receive a first button press and a second button press; and a custom audible message received by the microphone in response to the first button press, wherein the custom audible message is then emitted by the speaker in response to the second button press.
[0034] The custom audible message may comprise a name of a select visitor, and the custom audible message may be emitted by the speaker in response to both the second button press and the doorbell detecting an indication of a presence of the select visitor.
[0035] Doorbell systems may further comprise a predetermined audible message emitted by the speaker in response to the first button press. The custom audible message may be received by the microphone in response to the first button press and after the predetermined audible message is emitted by the speaker.
[0036] The first button press may comprise two button presses and the second button press may comprise one button press. The first button press may comprise the button being pressed for a first duration and the second button press may comprise the button being pressed for a second duration. The first duration may be greater than the second duration.
[0037] The doorbell may further comprise a memory communicatively coupled to the microphone and speaker, wherein the memory may be configurable to store the custom audible message and the predetermined audible message.
[0038] The disclosure also include a doorbell system, comprising: a doorbell including a button, a speaker and a microphone, wherein the doorbell is configurable to attach to an exterior of a building; a first custom audible message emitted by the speaker in response to the doorbell detecting an indication of a presence of a first visitor; and a second custom audible message emitted by the speaker in response to the doorbell detecting an indication of a presence of a second visitor.
[0039] The doorbell system may be communicatively coupled to a second doorbell system attached to an exterior of a second building that is remotely located with respect to the first building. As well, detecting the indication of the presence of the first visitor may comprise the doorbell system receiving a first notification from the second doorbell system, and detecting the indication of the presence of the second visitor may comprise the doorbell system receiving a second notification from the second doorbell system.
[0040] The first custom audible message may comprise a first name of the first visitor. The second visitor may be a solicitor and the second custom audible message may comprise an apology and a message that a resident of the building does not patronize solicitors.
[0041] Doorbell systems may comprise a wireless communication system communicatively coupled to the doorbell, wherein the wireless communication system is configurable to retrieve data from a remote computer; a third custom audible message emitted by the speaker in response to the doorbell detecting an indication of a presence of a third visitor, wherein the third custom audible message comprises a first name of the third visitor; and a camera coupled to the doorbell, wherein the camera is configurable to capture a facial image of the third visitor, wherein the first name of the third visitor is thereby determined through the wireless communication system communicating with the remote computer to match facial recognition data from the facial image of the third visitor as captured by the camera with facial recognition data from a facial image of the third visitor from an online social network.
[0042] Detecting the indication of the presence of the first visitor may comprise determining an identity of the first visitor, and wherein detecting the indication of the presence of the second visitor may comprise determining an identity of the second visitor. Doorbell systems may further comprise: a remote computing device communicatively coupled to the doorbell; and a text message received by the remote computing device, wherein the text message comprises at least one of the identity of the first visitor and the identity of the second visitor.
[0043] The embodiments described above include many optional features and aspects. Features and aspects of the embodiments can be combined.
Brief Description of the Drawings
[0044] 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.
[0045] FIG. 1 illustrates a front view of a communication system, according to some embodiments.
[0046] FIG. 2 illustrates a computing device running software, according to some embodiments.
[0047] FIG. 3 illustrates an embodiment in which a security system is connected to a building, according to some embodiments.
[0048] FIG. 4 illustrates a communication system that includes a security system, a doorbell button, a wireless router, a server, and users, according to some embodiments.
[0049] FIG. 5 illustrates a flow diagram showing a method of operating a security system, according to some embodiments.
[0050] FIG. 6 illustrates a flow diagram showing another method of operating a security system, according to some embodiments.
[0051] FIGS. 7 , 8, 9 and 10 illustrate visitors being detected by security systems, according to various embodiments.
[0052] FIG. 11 illustrates a block diagram of a security system that is communicatively coupled to a communication system, according to some embodiments.
[0053] FIG. 12 illustrates a block diagram of various event detection devices that are communicatively coupled to a communication system, according to some embodiments.
[0054] FIG. 13 illustrates a flowchart of a method of monitoring for an event through a communication system, according to some embodiments.
[0055] FIG. 14 illustrates an example of various alarm types that may be used based on the certainty and severity of the event, according to some embodiments.
[0056] FIGS. 15 , 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27 and 28 illustrate flow diagrams showing methods of operating a security system, according to various embodiments.
Detailed Description
[0057] 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.
[0058] 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.
[0059] 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
[0060] 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.
[0061] 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.
[0062] 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.
[0063] 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.
[0064] 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.
[0065] 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.
[0066] 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).
[0067] 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.
[0068] 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.
[0069] 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).
[0070] 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.
[0071] 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.
[0072] 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.
[0073] 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.
[0074] 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.
[0075] 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).
[0076] 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.
[0077] 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).
[0078] 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.
[0079] 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.
[0080] 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.
[0081] 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.
[0082] 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.
[0083] 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.
[0084] 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.
[0085] 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.
[0086] 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.
[0087] 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.
[0088] 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.
[0089] 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.
[0090] 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.
[0091] 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.
[0092] 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.
[0093] FIG. 4 illustrates a communication system 310 that includes a security system 320, a doorbell button 212, a WiFi router 328, a server 332, and users 336. In step 340, a visitor initiates a communication request by pressing the doorbell button 212 or triggering a motion or proximity sensor. The visitor can trigger the motion or proximity sensor by approaching the security system 320. In step 350, the security system 320 connects or otherwise communicates with a home WiFi router 328. In step 360, the server 332 receives a signal from the WiFi router 328 and sends video and/or audio to the users 336 via a wireless network 364. In step 370, the users see the visitor, hear the visitor, and talk with the visitor. Step 370 can include using a software application to see, hear, and/or talk with the visitor. The visitor and users 336 can engage in two-way communication 374 via the internet or other wireless communication system even when the visitor and the users 336 are located far away from each other. Some embodiments enable users to receive communication requests and communicate with visitors via diverse mobile communication standards including third generation (“3G”), fourth generation (“4G”), long term evolution (“LTE”), worldwide interoperability for microwave access (“WiMAX”), and WiFi.
[0094] In some cases, the users 336 utilize the communication system 310 to communicate with visitors who are in close proximity to the users 336. For example, a user 336 located inside her home can communicate with a visitor located just outside the home via the communication system 310.
Situational Sound Embodiments
[0095] The security system 202 may be configured to play unique sounds in response to detecting specific situations and/or during certain times of day. The sounds may be preprogrammed sounds or completely customizable by a user of the security system 202. As well, the security system 202 may be configured to play any of the sounds according to specific situations. For example, the security system 202 may be configured to play a specific message for a specific visiting individual, and/or may be configured to play a specific message when a potential visitor is identified as a specific person or is included in a list of specific people.
[0096] The security system 202 may include a speaker 488 configured to emit any type of sound. The security system 202 may also include a visitor detection system that may include at least one of a button 212, a camera 208, and a motion detector 218. Accordingly, the visitor detection system may be configurable to receive various indications of a visitor's presence. As well, the speaker 488 and the visitor detection system may be directly or indirectly coupled to the security system 202. Even still, the speaker 488 and the visitor detection system may be mechanically, electrically, and/or communicatively coupled to the security system 202.
[0097] The security system 202 may detect different indications of a visitor's presence. As shown in FIG. 5 , the security system 202 can be configured to receive a first indication of a visitor's presence (at step 560). In response to receiving the first indication of the visitor's presence, the security system 202 can emit a first sound with the speaker 488 (at step 562). The security system 202 can be configured to receive a second indication of a visitor's presence (at step 564). In response to receiving the second indication of the visitor's presence, the security system 202 can emit a second sound with the speaker 488 (at step 566). The first sound can be audibly different than the second sound.
[0098] Some of the indications can be interpreted as being associated with a friendly or welcome visitor, while other indications can be interpreted as being associated with an unfriendly or unwelcome visitor. According to these different indications, the security system 202, by the speaker 488, can emit different sounds.
[0099] With reference to FIG. 7 , when the security system 202 receives an indication that a visitor 580 has pressed the button 212 (at step 582), this can be interpreted as an indication of a friendly, or welcome visitor. In response to receiving the indication that the button 212 has been pressed, the speaker 488 can emit a first sound (at step 584), such as a friendly sound (e.g. “Welcome to our humble abode.”).
[0100] As illustrated in FIG. 8 , when the security system 202 receives an indication that a visitor 586 has been moving in front of the security system 202 for a prolonged or predetermined time (e.g. 15 seconds or any time that indicates that the visitor is loitering) without pressing the button 212 (at step 588), this can be interpreted as an unfriendly or unwelcome visitor. In response to receiving the indication that the visitor has been moving in front of the security system 202 without pressing the button 212, the speaker 488 can emit a second sound (at step 590). The second sound can be an alert sound (e.g. a warning to move away from the building 300—“Step away from the house!”). It should be appreciated that the security system 202 can be configured to emit any number of sounds, such as a third sound, a fourth sound, a fifth sound, and any number of additional sounds.
[0101] The security system 202 can be configured to receive any number of indications. For example, in addition to a button press and a motion of a visitor, the indications can include indications of a remote computing device 204, a noise, a thermal signature (such as a thermal gradient indicating the presence of a person or animal), a retina scan, a fingerprint scan, a ground vibration, and the like. It should be appreciated that the indication can include any indication of a presence of any visitor, such as a person or animal.
[0102] In some embodiments, the security system 202 can emit different sounds for a first visitor. For example, as the first visitor approaches the building 300, the security system 202 can emit a first sound based upon the motion of the first visitor. As well, the security system 202 can emit a second sound once the first visitor pushes the button 212 of the security system 202.
[0103] Furthermore, any of the indications described in this disclosure can be associated with a visitor that is either welcome or unwelcome at the building. Accordingly, the security system 202 can be configured to any environment in which the building 300 is situated. For example, some buildings 300 can be located in high traffic areas where it is common for people to walk by the front of the security system 202 without pressing the button 212. In this regard, the security system 202 can be configured to ignore indications of motion and only emit sounds in response to affirmative indications that the visitor is visiting the building 300, such as an indication that the button 212 has been pressed. In some embodiments, the security system 202 can be configured to only respond to motion in certain zones. For example, if the security system 202 is located 20 feet from a busy sidewalk, then the security system 202 can be configured to ignore all motion that occurs more than 15 feet from the security system 202. In this manner, the security system 202 can only respond to movements occurring on the building property.
[0104] As well, combinations of indications can be interpreted in various manners. For example, a combination of an indication of motion (i.e. movement) of a visitor in front of the security system 202 and an indication that the visitor has pressed the button 212 can indicate that the visitor is welcome at the building 300. As previously described, the speaker 488 of the security system 202 can emit a friendly message in response to the combination of indications.
[0105] Even still, the security system 202 can be configured to emit different sounds in response to a positive detection of one indication and a negative detection of another indication. For example, if the security system 202 detects motion of a visitor but does not detect sound, this can be interpreted as an unwelcome visitor, such as a prowler sneaking around the outside of the building 300. In response, the speaker 488 of the security system 202 can emit an alert sound (e.g. a warning to exit the premise before the authorities are notified).
[0106] Furthermore, the time of day and/or day when a visitor approaches the building 300 can also indicate whether the visitor is welcome or not. As shown in FIG. 6 , the security system 202 can be configured to receive an indication of a visitor's presence at a first time of day (at step 570). The first time of day can occur between sunrise and sunset, or any other time of day. In response to receiving the indication of the visitor's presence at the first time of day, the security system 202 can emit a first sound with the speaker 488 (at step 572). In some embodiments, the first sound comprises an audible message spoken by a female voice, while some embodiments may comprise an audible message spoken by a male voice.
[0107] Furthermore, the security system 202 can be configured to receive an indication of the visitor's presence at a second time of day (at step 574). It should be appreciated that the second time of day can occur between sunset and sunrise, or any other time of day. In response to receiving the indication of the visitor's presence at the second time of day, the security system 202 can emit a second sound with the speaker 488 (at step 576). In some embodiments, the second sound comprises an audible message spoken by a male voice, while some embodiments may comprise an audible message spoken by a female voice.
[0108] To illustrate a more specific example, such as the one shown in FIG. 9 , if a visitor 592 presses the button 212 at noon on a weekend day (at step 594), the speaker 488 can emit a welcome message (e.g. “Welcome. We'll be right there.) (at step 596). In another example, as illustrated in FIG. 10 , if a visitor 597 presses the button 212 at midnight on a workday (at step 598), the speaker 488 can emit a do not disturb message or a message instructing the visitor to come back another time (e.g. “Please come back tomorrow!”).
[0109] Combinations of indications can be interpreted differently depending on the time of day. For example, in response to an indication of a motion and a noise during the day, the speaker 488 of the security system 202 can emit a friendly message. However, in response to an indication of a motion and a noise during the night, the speaker 488 can emit a warning message.
[0110] Even still, the security system 202 can be configured to respond differently based on the unique circumstances of the indication. For example, if the motion detector 218 of the security system 202 detects a slow movement versus a faster movement, then the speaker 488 can emit different sounds based upon these various circumstances. A slow movement can be interpreted as a prowler approaching the building, while a faster movement, such as a movement of a person walking at 3.5 miles per hour, can be interpreted as a friendly visitor approaching the building 300.
[0111] The time of day can be any selected time of day and any number of time ranges can be used. For example, the security system 202 can emit a welcome message during sunrise to sunset and an alert or warning message during sunset to sunrise. Accordingly, because sunrise and sunset change on a daily basis, the security system 202 can be communicatively coupled to an outside database(s) to allow the security system 202 to thereby automatically respond to these ever-changing conditions.
[0112] The security system 202 (e.g. doorbell) can elect to emit a particular sound, such as a first sound or a second sound, based on a time at which the security system 202 detects an indication of a presence of a visitor. In some embodiments, the security system 202 is configured to detect an amount of light, which may indicate a time of day. In response to detecting the amount of light, the security system 202 can elect to emit the first sound or the second sound based on the amount of light.
[0113] As well, the security system 202 can be configured to provide unique responses during different time ranges on specific days. For example, the user may have a bowling league every third Monday of the month. Accordingly, during that time, (e.g. from 6 pm-8:30 pm) on the third Monday of the month, in response to detecting an indication of a presence of a friendly visitor, the speaker 488 of the security system 202 can emit a friendly message telling the visitor that their presence is appreciated but the visitor should come back another time. In another example, the user may be on vacation from the 1st to the 10th and the user may wish to emit more intimidating warnings to secure the building 300. Generally speaking, the security system 202 can be configured to emit any type of sound in response to any time of day and/or day.
[0114] The security system 202 can be configured to detect specific visitors and emit certain sounds in response to detecting the specific visitors. For example, if the security system 202 detects a first visitor, such as a relative of the homeowner, the security system 202 can always emit a friendly sound, no matter how the first visitor approaches the home, or during what time of day. As well, if the security system 202 detects a second visitor, such as an unknown party (e.g. a solicitor), the security system 202 can emit an unfriendly sound, no matter how the second visitor approaches the home, or during what time of day.
[0115] To determine the identity of a visitor, the security system 202 can use any type of identity recognition technology, such as facial recognition, to determine an indication of an identity of a visitor. Some of these types of identity recognition technologies are disclosed in 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.
[0116] The different types of sounds emitted by the speaker 488 can be configured to match the appropriate indication as detected by the security system 202. For example, if the security system 202 detects an unfriendly visitor, the speaker 488 can emit a message spoken by a male voice to thereby intimidate the unfriendly visitor. Contra, if the security system 202 detects a friendly visitor, the speaker 488 can emit a message spoken by a female voice to thereby welcome the visitor. As well, the security system 202 can be configured to emit any other type of sound. For example, a welcome visitor can be greeted by a pleasant melody or a ding-dong, while an unwelcome visitor can be greeted by an alarm sound or a warning message.
[0117] As well, messages can be spoken in any language, volume, pitch, accent, and the like. Users may find that various combinations of vocal characteristics to be useful in different situations. For example, if a user is hosting a Mardi gras party, the user can configure the security system 202 to emit a message spoken by a person with a southern accent. Generally, it should be appreciated that the speaker 488 of the security system 202 can be configured to emit any type of sound for any type of specific situation.
[0118] Likewise, the security system 202 can be configured to play a specific message if the potential visitor is not included in a list. For example, where a potential visitor is not included in a list of the resident's contacts, the security system 202 can be configured to indicate that the resident does not accept solicitors and/or request the visitor to provide identifying information or describe the purpose of the visit.
[0119] In some embodiments, the security system 202 can be configured to play a specific message if the potential visitor has a criminal background. For example, a user can configure the security system 202 to play a specific message where a potential visitor is a registered sex offender.
[0120] The sounds emitted by the security system 202 can be recorded by the user him/herself. As well, the sounds can be downloaded from another source, such as a remote computer (e.g. a remote server), a remote computing device (e.g. a smart phone), a website, a database (e.g. iTunes®), and the like. Also, methods can include selecting the first sound and the second sound with a remote computing device that is configured to receive alerts from the doorbell. The selected sounds can be wirelessly transmitted to the doorbell.
[0121] As well, the sounds can be recorded with a remote computing device 204 and the sounds can be set up for temporary use whereby the sounds can expire upon a predetermined time. For example, a user can enter an expiration date of the recorded sound with the remote computing device 204. Furthermore, the user can wirelessly send the first sound and the expiration date from the remote computing device to the doorbell. Once the expiration date passes, the security system 202 can then cease to emit the recorded sound from the security system 202.
[0122] As well, the security system 202 can be configured to receive sound emitting parameters from a remote computing device 204. The security system 202 can emit a predetermined sound based upon the sound emitting parameter. In some embodiments, the sound emitting parameter includes at least one of an identity of the first visitor, data associated with the first visitor, a time, a location of a user of the remote computing device. In some embodiments, the security system 202 can automatically download a third sound based on the sound emitting parameters. The security system 202 can emit the third sound from the speaker according to rules associated with the third sound.
Alert Communication Embodiments
[0123] 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.
[0124] FIG. 11 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.
[0125] 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.
[0126] 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.
[0127] 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.
[0128] 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.
[0129] 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.
[0130] 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).
[0131] 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).
[0132] 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.
[0133] 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. The light 406 can comprise the diagnostic light 216 and/or the power indicator light 220, as shown in FIG. 1 , and/or any other light coupled to the security system 202. As well, the speaker 404 may comprise the speaker 488, as illustrated in FIG. 1 , and/or any other speaker coupled to the security system 202.
[0134] 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).
[0135] 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.
[0136] 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.
[0137] 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.
[0138] 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.
[0139] 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.
[0140] 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.
[0141] 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 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.
[0142] 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.
[0143] 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.
[0144] FIG. 12 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.
[0145] 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.
[0146] 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.
[0147] 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.
[0148] 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).
[0149] 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.
[0150] FIG. 13 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.
[0151] 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.
[0152] 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.
[0153] 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.
[0154] 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.
[0155] 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.
[0156] 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).
[0157] 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.
[0158] 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).
[0159] FIG. 14 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. 13 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.
[0160] 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.
Customized Sound Embodiments
[0161] The security system 202, or doorbell 202, may be configured to receive a custom sound(s) from a user and thereby emit the custom sound in response to a particular situation(s). For example, as illustrated in FIG. 15 , a doorbell system 200 may receive a custom message (at step 1500). A user of the system may then optionally assign the custom message to a select visitor (at step 1502). Thereby when an indication of a presence of the select visitor is detected by the doorbell 202 (at step 1504), the doorbell 202 may then respond by emitting the custom message with a speaker 404, 488 of the doorbell 202 (at step 1506). It should be appreciated that the term “detecting” may be defined as discovering or identifying the presence or existence of a visitor. As such, the term “detecting” may be used interchangeably with the term “determining.”
[0162] The custom sound, or custom message, may be received by the doorbell system 200 in a variety of ways. As shown in FIG. 16 , the doorbell system 200 may download the custom message from a remote computer, such as a remote computing device (e.g. a smart phone) (at step 1600). As well, the doorbell system 200 may record the custom message (at step 1602). For example, a user of the doorbell system 200 may record the custom message on his or her remote computing device, such as a smart phone, (at step 1602) and then download the custom message from the smart phone onto the doorbell system 200. In some embodiments, the custom message may be directly recorded by the doorbell 202 (at step 1602), such as recorded by a microphone of the doorbell 202. Generally, it should be appreciated that the custom message may be recorded by any type of recording device that is communicatively coupled to the doorbell system 200 (at step 1602). In this manner, the doorbell system 200 may download the custom message from the recording device.
[0163] As further illustrated in FIG. 16 , any number of custom messages may be recorded and/or downloaded by the doorbell system 200. For example, the doorbell system may record and/or download a second custom message (at step 1604), a third custom message, a fourth custom message, and any number of additional custom messages.
[0164] The doorbell system 200 may also be configured to interact with a visitor whereby the doorbell system 200 gives and receives audible information. In this manner, the doorbell system 200 may interpret information from the visitor. With reference to FIG. 17 , the doorbell system 200 (e.g. a speaker 404, 488 of the the doorbell 202) may be configured to emit an audible question(s) (at step 1700). The doorbell system 200 (e.g. via a microphone of the doorbell 202) may then receive an audible response from the visitor (at step 1702). The doorbell system 200 may thereby determine the meaning of the audible response given by the visitor. For example, the doorbell system 200 may determine whether the audible response comprises a first meaning or a second meaning (at step 1704). For example, if the doorbell system 200 determines that the audible response comprises the first meaning, the doorbell 202 may then emit a first audible response, via the speaker 404, 488, (at step 1706). As well, if the doorbell system 200 determines that the audible response comprises the second meaning, the doorbell 202 may then emit a second audible response, via the speaker 404, 488, (at step 1708). In this manner, the doorbell system 200 may be a smart system that is able to interpret and respond to different responses given by the visitor.
[0165] The doorbell system 200 may also be configured to intiate a communication session with a remote computing device 204, such as a remote computing device 204 associated with the visitor and/or a user of the doorbell system 200 (e.g. a resident of the building 300). For example, the doorbell system 200 may detect an indication of a presence of a visitor (at step 1800). The doorbell system 200 may then initiate a communication session with the remote computing device of the visitor and/or the resident (at step 1802). The communication session may comprise any type of communication and/or transmission to the remote computing device, such as a text message, phone call, voicemail, email, and the like. For example, the communication session may comprise a written message that substantially matches a content of the custom message as emitted by the speaker 404, 488. In this manner, hearing impaired visitors may be able to receive the message.
[0166] Furthermore, in some embodiments, the doorbell system 200 may be configured to determine an identity of a first visitor and/or a second visitor. Accordingly, the doorbell system 200 may intiate a communication session, such as transmit a text message, to a remote computing device 204 that includes at least one of the identity of the first visitor and/or the identity of the second visitor. Generally, it should be appreciated that the communication session may include any type of information relating to the visitor and/or the visitor's presence at the doorbell 200.
[0167] The doorbell system 200 may also be configured to detect various types of visitors. In some embodiments, as illustrated in FIG. 19 , the doorbell system 200 may be referred to as a first doorbell system 200a, which may be configured to detect an indication of a presence of a criminal (at step 1900). The first doorbell system 200a may detect the indication of the presence of a visitor, such as a criminal, by receiving a notification from a second doorbell sysem 200b that is communicatively coupled to the first doorbell system 200a and remotely located with respect to the first doorbell system 200a. For example, the second doorbell system 200b may determine that a criminal is in the area and then alert all other doorbell systems 200 located within the vicinity, including the first doorbell system 200a.
[0168] With reference to FIG. 19 , in response to the doorbell 202 and/or doorbell system 200 detecting the indication of the presence of the criminal, the doorbell 202 may emit a warning message with a speaker 404, 488 of the doorbell 202 (at step 1902). The doorbell system 200 may then initiate a communication session with a law enforcement agency to notify the agency of the presence of the criminal (at step 1904). It should be appreciated that the warning message may include a message to scare away the criminal and/or inform the criminal that the law enforcement agency has been contacted.
[0169] As shown in FIG. 20 , the doorbell system 200 may also be configured to identify a visitor, such as a criminal or suspicious person, by taking a picture of the visitor (at step 2000). The doorbell system 200 may then determine, based on the picture, that the visitor is included in a database of suspicious visitors, such as a database of criminals, that previously visited other doorbells 202 (at step 2002). The doorbell system 200, and/or a remote computer, may use facial recognition software to match the facial data of the criminal with facial data from a law enforcement database. As well, the doorbell system 200 may detect the indication of the presence of the criminal by detecting body language of the criminal, such as detecting evasive or suspicious moves, detecting a fingerprint of the criminal, detecting a retina of the criminal, and the like.
[0170] As well, the doorbell system 200 may be configured to determine various types of visitors. As shown in FIG. 21 , for example, the doorbell system 200 may determine that a visitor is a predetermined visitor type (at step 2100). The predetermined visitor type may comprise any type of visitor, such as a known visitor (e.g. a friend, a family member, and/or anyone included on a smart phone contact list of a user), a known visitor, a suspicious visitor, a criminal, and the like. In response to determining that the visitor is the predetermined visitor type, the doorbell system 200, via the doorbell 202, can select a custom message from a first message and a second message (at step 2102). In response to determining that the visitor is a known person, the doorbell system 200 may emit the first message (at step 2104). In some embodiments, the first message optionally includes a name of the known person. For example, the doorbell system 200 may determine that a known person named Tim, who is a friend of the resident, is present. Accordingly, the doorbell 202 may audibly announce, “Welcome, Tim.”
[0171] Likewise, in response to determining that the visitor is a stranger, the doorbell 202 may emit the second message (at step 2106). For example, if the doorbell system 200 determines that the stranger is a solicitor, the doorbell 202 may emit an audible message informing the solicitor that the resident does not purchase items from solicitors, an apology, and an invitation to exit the premise. Generally, it should be appreciated that the doorbell system 200 may be configured to determine any type of visitor and emit any type of custom message in response to the type of visitor.
[0172] The doorbell system 200 may also be configured to emit custom messages in response to the occurrence of predetermined conditions. As illustrated in FIG. 22 , the doorbell system 200 may detect an indication of a presence of a visitor (at step 2200). The doorbell system 200 may thereby determine that a predetermined condition has occurred (at step 2202). For example, the predetermined condition may be a time of day, a period of days, such as a time when the resident(s) is on vacation, an event (e.g. a birthday party, during a football game, etc.), and the like. Accordingly, in response to the indication of the presence of the visitor and the occurrence of the predetermined condition, the doorbell 202 may thereby emit a custom message (at step 2204). It should be appreciated that the custom message may correspond with the occurrence of the predetermined condition. For example, if the predetermined condition is the occurrence of a game in which the resident's favorite football team is competing, then the custom message may be the fight song for the football team.
[0173] The predetermined condition may also be an occurrence when the resident(s) is away from the building 300 or when the resident(s) is located within the building 300. With specific reference to FIG. 23 , the doorbell system 200 may be configured to record and/or download more than one custom message, such as a first custom message and/or a second custom message, and then emit the respective custom message in particular situations (at step 2300). Accordingly, the method may thereby include determining whether a resident is located within the building 300 or whether the resident is not located within the building 300 (at step 2302). In response to determining that the resident is present within the building 300, the doorbell 202 may thereby emit the first custom message (at step 2304). For example, the first custom message may be a message informing the visitor that the resident will be right there, such as, “Please wait a moment. Mr. Banks will be right there” (whereby Mr. Banks is the resident). In response to determining that the resident is not present within the building, the doorbell 202 may thereby emit the second custom message (at step 2306). The second custom message may include a message informing the visitor that the resident is busy (if the visitor is a suspicious person—to avoid a robbery) or away from the building 300 (if the visitor is a known person). For example, the second custom message may state, “I'm sorry. Mr. Banks is currently occupied. Please come back another time.”
[0174] The doorbell system 200, via the doorbell 202, may be configured to receive the custom message in response to a variety of inputs as received by the doorbell system 200. For example, as shown by FIG. 24 , the doorbell 202 may receive an indication of a first button press from a button 212 of the doorbell 202 (at step 2400). In response to receiving the first button press, the doorbell 202 may thereby record the custom message and store the custom message within a memory of the doorbell system 200 (at step 2402). As well, the doorbell system 200 may be configured to receive an input, such as receive an indication of a second button press from the doorbell 202 (at step 2404). In response to receiving the second button press, the doorbell system 200 can thereby erase the custom message from the memory of the doorbell system 200 (at step 2406).
[0175] It should be appreciated that any reference to first button press, second button press, and the like, can refer to any number of button presses or duration of respective button presses. For example, the first button press can comprise two button presses and the second button press can comprise one button press. As well, the first button press can comprise one button press and the second button press can comprise two button presses. In some embodiments, the first button press can comprise the button 212 being pressed for a first duration and the second button press can comprise the button 212 being pressed for a second duration. It should be appreciated that the first duration can be greater than, equal to, or less than the second duration.
[0176] However, it should be appreciated that the inputs may be any type of inputs into the doorbell system 200. For example, in conjunction or instead of a first and second button press, the doorbell system 200 may be configured to receive various motions from the user. In some embodiments, the camera 208 of the doorbell 202 may detect a first motion from the user, such as the user waving a hand once. In response to detecting the first motion, the doorbell 202 may thereby record the custom message and store the custom message within a memory of the doorbell system 200. As well, the camera 208 may detect a second motion from the user, such as the user waving a hand twice. In response to detecting the second motion, the doorbell 202 may thereby erase the custom message from the memory of the doorbell system 200. Generally, it should be appreciated that any type of input, such as a bodily motion, may be received by the doorbell system 200.
[0177] The doorbell system 200 may also be configured to provide security and anonymity to a user of the doorbell system 200. For example, as shown in FIG. 25 , the doorbell system 200 may record and/or download a first custom message (at step 2500). The first custom message may be spoken by a first voice. The doorbell system 200 may be configured to effectively convert the first message into a second message, whereby the second message is spoken by a second voice that is different from the first voice. The content of the first custom message can substantially match the content of the second custom message. As such, the doorbell system 200 may emit the second custom message (at step 2502) that is spoken by the second voice. In this manner, the doorbell system 200 may effectively protect the identity of the user (e.g. resident) of the doorbell system 200.
[0178] With respect to the various predetermined conditions, as shown in FIG. 26 , the doorbell system 200 may create a schedule of a first timeframe to emit a first sound, a second timeframe to emit a second sound, and a third timeframe to emit a third sound (at step 2600). The doorbell system 200 may thereby determine that a visitation time of the visitor is within the first timeframe (at step 2602), and in response to determining that the visitation time of the visitor is within the first timeframe, the doorbell 202 may emit the first sound (at step 2604). Accordingly, if the doorbell system 200 determines that the visitation time of the visitor is within the second timeframe, the doorbell 202 may emit the second sound. Likewise, if the doorbell system 200 determines that the visitation time of the visitor is within the third timeframe, the doorbell 202 may emit the third sound.
[0179] For example, the first timeframe might include overnight and morning hours when the resident is either sleeping or getting ready for work. The first sound may thereby inform a visitor that the resident is busy and that the visitor should come back another time. As well, the second timeframe might include daytime hours, when the resident is away at work. The second sound might include a message that the resident is not available and that the visitor can reach the resident at work or on the resident's smart phone, if the visitor is a known or trusted visitor. Finally, the third timeframe might include a time during evening hours when the resident is home from work. The third sound may thereby inform the visitor that the resident will answer the door shortly. Generally, it should be appreciated that the doorbell system 200 may be configured to accommodate any timeframe or number of timeframes. As well, the doorbell system 200 may be configured to receive and thereby emit any sound in response to any of the respective timeframes.
[0180] With reference to FIG. 27 , the doorbell system 200 may be configured to receive any number of custom messages and then emit respective messages in response to the doorbell system 200 (e.g. the doorbell 202) detecting an indication of a presence of any number of respective visitors. The doorbell 202 may emit a first custom audible message with a speaker 404, 488 in response to the doorbell system 200 detecting an indication of a presence of a first visitor (at step 2700). As well, the doorbell 202 may emit a second custom audible message with the speaker 404, 488 in response to the doorbell system 200 detecting an indication of a presence of a second visitor (at step 2702). Likewise, the doorbell 202 may emit a third custom audible message with the speaker 404, 488 in response to the doorbell system 200 detecting an indication of a presence of a third visitor (at step 2704).
[0181] The first, second and third custom audible messages can be assigned to specific visitors or groups of visitors. For example, the first custom audible message may be assigned to a specific first visitor. As well, the first custom audible message may be assigned to a specific group or type of visitor, such as any known visitor.
[0182] As shown in FIG. 28 , the doorbell system 200 may be referred to as a first doorbell system 200a that is attached to a first building 300a. The first doorbell system 200a may be communicatively coupled to a second doorbell system 200b that is attached to an exterior of a second building 300b that is remotely located with respect to the first building 300a. Accordingly, the first doorbell 202a may also be communicatively coupled to the second doorbell 202b. Thereby, the first doorbell system 202a may detect an indication of a presence of a first visitor by receiving a first notification from the second doorbell system 202b (at step 2800). As well, the first doorbell system 202a may detect an indication of a presence of a second visitor by receiving a second notification from the second doorbell system 202b (at step 2802). In this manner, the first doorbell system 202a and the second doorbell system 202b may be networked. This may allow doorbell systems 200 that are located within a specific area, such as a neighborhood, to communicate and transmit data to each other. The network of doorbell systems may exchange information and/or data to thereby monitor the entire neighborhood.
Interpretation
[0183] 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.
[0184] 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.
[0185] 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.
[0186] 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.
[0187] 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.
[0188] 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.
[0189] 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 for emitting a custom message with a doorbell system, wherein the doorbell system comprises a doorbell having a speaker, the method comprising:
receiving the custom message with the doorbell system;
detecting, by the doorbell, an indication of a presence of a visitor, and then in response to detecting the indication of the presence of the visitor, emitting the custom message with the speaker, wherein the custom message comprises a warning message and an indication that a resident does not welcome the visitor; and
initiating, by the doorbell system, a communication session with a law enforcement agency.
2. The method of claim 1, wherein the visitor is a predetermined visitor, the method further comprising assigning, by the doorbell system, the custom message to the predetermined visitor.
3. The method of claim 1, further comprising determining, by the doorbell system, that the visitor is a predetermined visitor type, and selecting the custom message from a first message and a second message in response to determining that the visitor is the predetermined visitor type.
4. The method of claim 2, further comprising downloading the custom message from a phone communicatively coupled to the doorbell system.
5. The method of claim 2, wherein the doorbell system further comprises a remote computing device, the method further comprising recording the custom message with the remote computing device.
6. The method of claim 2, wherein the doorbell further comprises a microphone and a button, the method further comprising receiving an indication of a button press of the button, and then in response to receiving the button press, recording the custom message with the microphone.
7. The method of claim 2, wherein the doorbell system is operated by a homeowner and the visitor is included on a contact list of the homeowner, and wherein the custom message comprises a name of the visitor,
wherein the doorbell comprises a microphone, and wherein the custom message comprises a question, the method further comprising receiving, by the microphone, an audible response to the question as spoken by the visitor, the method further comprising:
determining, by the doorbell system, whether the audible response spoken by the visitor comprises a first meaning or a second meaning that is different from the first meaning;
in response to determining that the audible response spoken by the visitor comprises the first meaning, emitting a first response message with the speaker; and
in response to determining that the audible response spoken by the visitor comprises the second meaning, emitting a second response message with the speaker, wherein the second response message is different from the first response message.
8. The method of claim 2, wherein the visitor comprises a solicitor and the communication session comprises an identity of the solicitor.
9. The method of claim 2, further comprising initiating, by the doorbell system, a communication session with a remote computing device of the visitor, wherein the communication session comprises a written message that substantially matches a content of the custom message.
10. A method for emitting a custom message with a doorbell system, wherein the doorbell system comprises a doorbell having a speaker, the method comprising:
detecting, by the doorbell, an indication of a presence of a visitor, wherein the doorbell is attached to a building occupied by a resident; and
determining, by the doorbell system, whether the resident is located within the building and then in response to detecting the indication of the presence of the visitor and determining that the resident is located within the building, emitting a first custom message with the speaker.
11. The method of claim 10, further comprising recording the custom message with the doorbell system.
12. The method of claim 11, further comprising:
recording a second custom message with the doorbell system, wherein the second custom message is different from the first custom message;
in response to both detecting the indication of the presence of the visitor and determining the resident is present within the building, emitting the first custom message with the speaker; and
in response to both detecting the indication of the presence of the visitor and determining the resident is not present within the building, emitting the second custom message with the speaker.
13. The method of claim 10, wherein the doorbell system further comprises a remote computing device, the method further comprising recording the custom message with the remote computing device.
14. The method of claim 10, wherein the doorbell comprises a microphone, the method further comprising recording the custom message with the microphone.
15. The method of claim 10, wherein the doorbell further comprises a button, the method further comprising:
receiving an indication of a first button press of the button, and then in response to receiving the first button press, recording the custom message with the doorbell system and thereby storing the custom message within a memory of the doorbell system; and
receiving an indication of a second button press of the button, and then in response to receiving the second button press, erasing the custom message from the memory of the doorbell system.
16. The method of claim 10, wherein the first custom message comprises a welcome message that welcomes the visitor.
17. The method of claim 10, wherein the custom message is a second custom message, and wherein the doorbell comprises a microphone, the method further comprising:
recording a first custom message with the microphone, wherein the first custom message is spoken by a first voice,
wherein the second custom message emitted by the speaker is spoken by a second voice, and wherein a content of the first custom message substantially matches a content of the second custom message.
18. The method of claim 10, further comprising taking, by the doorbell, a picture of the visitor, wherein determining the occurrence of the predetermined condition comprises determining, based on the picture, that the visitor is included in a database of suspicious visitors that previously visited other doorbells.
19. The method of claim 10, further comprising:
creating a schedule of a first timeframe to emit a first sound, a second timeframe to emit a second sound, and a third timeframe to emit a third sound;
determining, by the doorbell system, that a visitation time of the visitor is within the first timeframe; and
emitting, by the speaker, the first sound in response to determining that the visitation time of the visitor is within the first timeframe.
20. A doorbell system, comprising:
a doorbell including a button, a speaker and a microphone, wherein the doorbell is configurable to attach to an exterior of a building occupied by a resident; and
a custom audible message received by the doorbell system and emitted by the speaker in response to the doorbell system determining that the resident is located within the building.
21. The doorbell system of claim 20, wherein the custom audible message comprises a name of a select visitor, and wherein the custom audible message is emitted by the speaker in response to the doorbell detecting an indication of a presence of the select visitor.
22. The doorbell system of claim 20, further comprising a predetermined audible message emitted by the speaker in response to a first button press, wherein the custom audible message is received by the microphone in response to a second button press.
23. The doorbell system of claim 22, wherein the first button press comprises one button press and the second button press comprises two button presses.
24. The doorbell system of claim 22, wherein the first button press comprises the button being pressed for a first duration and the second button press comprises the button being pressed for a second duration, and wherein the first duration is less than the second duration.
25. The doorbell system of claim 22, wherein the doorbell further comprises a memory communicatively coupled to the microphone and the speaker, wherein the memory is configurable to store the custom audible message and the predetermined audible message.
26. A doorbell system, comprising:
a doorbell including a button, a speaker and a microphone, wherein the doorbell is configurable to attach to an exterior of a building; and
a custom audible message emitted by the speaker in response to the doorbell detecting an indication of a presence of a solicitor, wherein the custom audible message comprises an indication that a resident of the building does not welcome solicitors, wherein the custom audible comprises an apology.
27. The doorbell system of claim 26, wherein the custom audible message comprises a first custom audible message and the visitor comprises a first visitor the doorbell system further comprising a second custom audible message emitted by the speaker in response to the doorbell detecting an indication of a presence of a second visitor.
28. The doorbell system of claim 27, further comprising:
a wireless communication system communicatively coupled to the doorbell, wherein the wireless communication system is configurable to retrieve data from a remote computer;
a third custom audible message emitted by the speaker in response to the doorbell detecting an indication of a presence of a third visitor, wherein the third custom audible message comprises a first name of the third visitor; and
a camera coupled to the doorbell, wherein the camera is configurable to capture a facial image of the third visitor, wherein the first name of the third visitor is thereby determined through the wireless communication system communicating with the remote computer to match facial recognition data from the facial image of the third visitor as captured by the camera with facial recognition data from the facial image of the third visitor from an online social network.
29. The doorbell system of claim 27, wherein detecting the indication of the presence of the first visitor comprises determining an identity of the first visitor, and wherein detecting the indication of the presence of the second visitor comprises determining an identity of the second visitor, the doorbell system further comprising:
a remote computing device communicatively coupled to the doorbell; and
a text message received by the remote computing device, wherein the text message comprises at least one of the identity of the first visitor and the identity of the second visitor.
30. A doorbell system, comprising:
a doorbell including a button, a speaker and a microphone, wherein the doorbell is configurable to attach to an exterior of a building occupied by a resident; and
a custom audible message received by the doorbell system and emitted by the speaker in response to the doorbell system determining that the resident is not located within the building.
31. The doorbell system of claim 27, wherein the doorbell system is attached to a first building and the doorbell system is communicatively coupled to a second doorbell system attached to an exterior of a second building that is remotely located with respect to the first building,
wherein detecting the indication of the presence of the first visitor comprises the doorbell system receiving a first notification from the second doorbell system, and
wherein detecting the indication of the presence of the second visitor comprises the doorbell system receiving a second notification from the second doorbell system.
Patent Citations (186)
| 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 |
| US5210520(A) | 1993-05-01 | Housley | 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 |
| US5907352(A) | 1999-05-01 | Gilley | 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 |
| US7375492(B2) | 2008-05-01 | Calhoon | 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 |
| US7701171(B2) | 2010-04-01 | Defant | Applicant |
| US7738917(B2) | 2010-06-01 | Ryley | Applicant |
| US7746223(B2) | 2010-06-01 | Howarter | Applicant |
| US7752070(B2) | 2010-07-01 | Hatcher | Applicant |
| US7956576(B2) | 2011-06-01 | Neu | 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 |
| US8354914(B2) | 2013-01-01 | Buckingham | 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 |
| US8947530(B1) | 2015-02-01 | Scalisi | Applicant |
| US8953040(B1) | 2015-02-01 | Scalisi et al. | Applicant |
| US9013575(B2) | 2015-04-01 | Scalisi | Applicant |
| US9049352(B2) | 2015-06-01 | Scalisi et al. | Applicant |
| US9053622(B2) | 2015-06-01 | Scalisi | Applicant |
| US9055202(B1) | 2015-06-01 | Scalisi et al. | Applicant |
| US9058738(B1) | 2015-06-01 | Scalisi | Applicant |
| US9060103(B2) | 2015-06-01 | Scalisi | Applicant |
| US9060104(B2) | 2015-06-01 | Scalisi | Applicant |
| US9065987(B2) | 2015-06-01 | Kasmir 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/0071879(A1) | 2005-03-01 | Haldavnekar | Applicant |
| US2005/0097248(A1) | 2005-05-01 | Kelley | Applicant |
| US2005/0267605(A1) | 2005-12-01 | Lee | Applicant |
| US2005/0285934(A1) | 2005-12-01 | Carter | Applicant |
| US2005/0285944(A1) | 2005-12-01 | Wantanabe | Applicant |
| US2006/0010504(A1) | 2006-01-01 | Sharma | Applicant |
| US2006/0038663(A1) | 2006-02-01 | Steinetz | 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/0046442(A1) | 2007-03-01 | Bartorelli | Applicant |
| US2007/0126574(A1) | 2007-06-01 | Langer | Applicant |
| US2007/0146115(A1) | 2007-06-01 | Roosli | 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 | Applicant |
| 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/0134072(A1) | 2010-06-01 | Neu | 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 | Applicant |
| 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 | Applicant |
| 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/0327225(A1) | 2012-12-01 | Barley | Applicant |
| US2012/0327246(A1) | 2012-12-01 | Senior | Applicant |
| US2013/0020875(A1) | 2013-01-01 | Wozniak | 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/0015967(A1) | 2014-01-01 | Moore | 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/0167676(A1) | 2014-06-01 | Mack | Applicant |
| US2014/0253725(A1) | 2014-09-01 | Hsu | Applicant |
| 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 |
| US2015/0112885(A1) | 2015-04-01 | Fadell | Applicant |
| US2015/0194839(A1) | 2015-07-01 | Wojcik | 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 (72)
- 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
- 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 on May 24, 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=u9nNCm4tSYl; 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 andcameras.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
- 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
- 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=u9nNCm4tSYl.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/04118/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
- MyInterCom video system—Downloaded on Jun. 8, 2015 from http://myintercom.de/en/funktionsweise.Applicant