Patent Grant
11764990
Various embodiments disclosed herein relate to doorbells. Certain embodiments relate to communication between a person near a doorbell and a person in another location.
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.
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.
This disclosure includes a method of using a doorbell system to emit a sound from a chime. Methods can comprise selecting the sound by a remote computing device; sending a data file comprising information to a doorbell that is communicatively coupled to the remote computing device, wherein the information represents the sound; and sending the data file, by the doorbell, to the chime that is communicatively coupled to the doorbell and remotely located with respect to the doorbell.
Methods can include downloading, by at least one of the doorbell and the chime, the data file from a web server. The method can further include downloading, by the remote computing device, the data file from a web server.
As well, methods can comprise emitting the sound from a speaker of the chime at least partially in response to the chime receiving the data file and at least partially in response to the doorbell detecting an indication of a presence of a visitor. Even still, methods can include receiving, by the doorbell, a sound emission parameter from the remote computing device; and emitting the sound from a speaker of the chime in response to the doorbell system determining that the sound emission parameter has been met.
Methods can include emitting an audible message from a speaker of the chime, wherein the audible message is spoken by a user and recorded by the doorbell. As well, methods can include emitting an audible message from a speaker of the chime, wherein the audible message is spoken by a user and recorded by the remote computing device.
In embodiments, the chime can be located along an inside portion of a building. Accordingly, methods can include detecting a first motion, by a motion detector of the chime, within the inside portion of the building; and initiating a first communication session with the remote computing device in response to the chime detecting the first motion, wherein the first communication session comprises a first notification of the first motion detected by the motion detector of the chime. In embodiments, the remote computing device is a first remote computing device. Methods can further include detecting a second motion, by the motion detector of the chime, within an inside portion of the building, wherein the second motion is different from the first motion; and initiating a second communication session with a second remote computing device in response to the motion detector of the chime detecting the second motion, wherein the second communication session comprises a second notification of the second motion detected by the chime, and wherein the first remote computing device does not receive the second communication session.
As well, methods can include selecting a second sound by the remote computing device; sending a second data file comprising second information to the doorbell, wherein the second information represents the second sound; and sending the second data file to the chime. The chime can be located along an inside portion of a building and the doorbell can be located along an outside portion of the building. Accordingly, methods can further include detecting a first motion, by a motion detector of the doorbell, along the outside portion of the building; emitting the first sound from a speaker of the chime in response to the doorbell detecting the first motion; detecting a second motion, by the motion detector of the doorbell, along the outside portion of the building, wherein the second motion is different from the first motion; and emitting the second sound from the speaker of the chime in response to the doorbell detecting the second motion.
The disclosure also includes a method of using a doorbell system to emit a sound from a chime. Methods can include selecting the sound by a remote computing device; sending a data file comprising information to the chime that is communicatively coupled to the remote computing device, wherein the chime is located within an inside portion of a building, and wherein the information represents the sound; detecting an indication of a presence of a visitor with a doorbell that is communicatively coupled to the chime, wherein the doorbell is located along an outside portion of the building, and wherein the doorbell comprises a button configurable to detect a button press to indicate the presence of the visitor; and emitting the sound from a speaker of the chime in response to detecting the indication of the presence of the visitor.
As well, methods can include detecting a motion, by a motion detector of the chime, within the inside portion of the building; capturing an image, by a camera of the chime, within the inside portion of the building; and sending the image to the remote computing device. Even still, methods can include detecting a motion, by a motion detector of the chime, within the inside portion of the building; and flashing a light of the doorbell in response to the chime detecting the motion within the inside portion of the building.
Methods can also include recording a noise, by a microphone of the chime, within the inside portion of the building; and emitting the noise from a speaker of the remote computing device. As well, methods can include detecting a motion, by a motion detector of the chime, within the inside portion of the building; and initiating a communication session with the remote computing device in response to the motion detector of the chime detecting the motion, wherein the communication session comprises a notification of the motion detected by motion detector of the chime.
Even still, methods can include sending the data file comprising the information to the doorbell; and detecting a motion, by a motion detector of the chime, within the inside portion of the building. Methods can also include emitting the sound from a speaker of the doorbell in response to the chime detecting the motion within the inside portion of the building.
The disclosure also includes a doorbell system, comprising: a doorbell comprising a button configurable to detect a button press to indicate a presence of a visitor; a chime communicatively coupled to the doorbell; a remote computing device communicatively coupled to at least one of the doorbell and the chime; and a sound emitted by a speaker of the chime in response to the doorbell detecting an indication of a presence of a visitor. Embodiments of the chime can comprise a motion detector configurable to detect motion along an inside portion of a building; a camera assembly configurable to capture an image along the inside portion of the building; the speaker configurable to emit the first sound; and a microphone configurable to receive an audible message spoken by a user along the inside portion of the building.
Embodiments of the chime can comprise a thermometer configurable to determine temperature along the inside portion of the building; and a humidity sensor configurable to determine humidity along the inside portion of the building. As well, embodiments can include a communication system configurable to communicatively couple the chime to the doorbell.
The sound can be a first sound. The doorbell system can further include a second sound emitted by the speaker of the chime in response to the motion detector detecting the motion along the inside portion of the building. As well, embodiments of the doorbell system can include a third sound emitted by the speaker of the chime in response to the thermometer detecting that a predetermined temperature has been met; and a fourth sound emitted by the speaker of the chime in response to the humidity sensor detecting that a predetermined humidity has been met.
The disclosure can include a method of using a doorbell system to emit a first sound from a chime. Methods can include recognizing, by a doorbell, a first visitor; emitting the first sound from the chime in response to recognizing the first visitor; and emitting a second sound from the chime in response to not recognizing, by the doorbell, a second visitor, wherein the first sound and the second sound are different.
Methods can include selecting, by the remote computing device, the first sound and the second sound; and sending the first sound and the second sound to the chime. As well, methods can include selecting, by the remote computing device, the first sound and the second sound; and sending the first sound and the second sound to the doorbell, and then sending the first sound and the second sound from the doorbell to the chime.
Even still, methods can include sending the first sound and the second sound from the doorbell to the chime via wireless communication. Methods can also include sending the first sound and the second sound from the doorbell to the chime via an electrical wire that electrically couples the doorbell and the chime while the doorbell is located outside a building and the chime is located inside the building.
As well, methods can include recognizing the first visitor by the doorbell detecting a physical trait of the first visitor. Methods can also include recognizing the first visitor by the doorbell detecting a trait of an electronic device in the possession of the first visitor.
This disclosure includes a doorbell system configured to be electrically coupled to a doorbell power supply of a building. The doorbell system can comprise a doorbell comprising a button configurable to sound a chime, wherein a first wire electrically couples the doorbell to the power supply; the chime electrically coupled to the doorbell by a second wire; and a third wire that electrically couples the chime to the power supply to form a circuit comprising the first wire, the doorbell, the second wire, the chime, the third wire, and the power supply.
The doorbell can be communicatively coupled to the chime via the second wire such that the chime is configured to receive a first data file from the doorbell via the second wire. Doorbell systems can further include a sound file communication sent from the doorbell to the chime via the second wire. In embodiments, the sound file communication can comprise at least one thousand bytes.
In embodiments, the first data file comprises a command configured to place the chime in silent mode. In some embodiments, the first data file comprises a command configured to adjust a volume setting of the chime. As well, in some embodiments, the first data file comprises a command configured to adjust a duration of a notification sound emitted by the chime. Furthermore, in some embodiments, the first data file comprises a video recorded by the doorbell. Even still, in embodiments, the first data file comprises a video recorded by the chime. In embodiments, the first data file comprises information regarding an event that occurred outside of the chime. Accordingly, in embodiments, the first data file comprises information regarding a person detected by the chime.
As well, in embodiments, the doorbell is located outside of the building and the chime is located inside of the building. Even still, in embodiments, the doorbell is communicatively coupled to the chime via the second wire such that the doorbell is configured to receive a first data file from the chime via the second wire.
Even still, in embodiments, the doorbell system can include a remote computing device communicatively coupled with the doorbell via a wireless communication, wherein the wireless communication comprises a first information regarding a notification sound; a wired communication sent from the doorbell to the chime via the second wire, wherein the wired communication comprises a second information regarding the notification sound; and the notification sound emitted from a speaker of the chime. Yet, in embodiments, the doorbell can include a first camera, a first speaker, and a first microphone. The chime can comprise a second camera, a second speaker, and a second microphone.
The disclosure also includes a method of using a doorbell system configured to be electrically coupled to a doorbell power supply of a building. Methods can include coupling a doorbell to a remote chime via a first wire; receiving, by the doorbell, a first data file comprising information; and sending a second data file comprising the information from the doorbell to the remote chime via the first wire.
The information can represent a sound that was unknown to the chime prior to receiving the second data file. Methods can further include emitting the sound from the chime at least partially in response to receiving the second data file.
As well, methods can include emitting the sound from the chime at least partially in response to the chime receiving a sound emission parameter from the doorbell. Methods can also include the doorbell receiving a sound emission parameter from a remote computing device; and emitting the sound from the chime in response to the doorbell system determining that the sound emission parameter has been met.
Even still, methods can include the doorbell receiving the first data file from a remote computing device. Furthermore, methods can include the doorbell receiving a video recorded by the chime via the first wire. As well, methods can include the chime receiving a video recorded by the doorbell via the first wire. The second data file can comprise at least one thousand bytes. Methods can include the chime using the second data file to emit a sound.
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.
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.
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.
The doorbell system may further comprise a remote computing device, and methods may further comprise recording the custom message with the remote computing device.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
This disclosure also includes a method of using a doorbell system comprising a doorbell and a chime, wherein the doorbell system is configured to be coupled to a building. Methods can include coupling communicatively the chime to a wireless network of the building, to the doorbell, and to a remote computing device; and detecting, by the doorbell, a trigger of a button of the doorbell.
Methods can include sending a visitor alert from the doorbell to the chime, and then sending the visitor alert from the chime to the remote computing device such that the chime communicatively couples the doorbell to the remote computing device. In embodiments, the visitor alert comprises a video. Accordingly, methods can further include the doorbell taking the video.
As well, methods can include sending the visitor alert from the doorbell to the chime while the doorbell is located outside of the building and while the chime is located inside of the building. Methods can also include sending the visitor alert from the chime to the remote computing device via the wireless network of the building.
Even still, methods can include sending the visitor alert from the chime to the remote computing device in response to the doorbell system detecting that the doorbell comprises inadequate wireless performance to send the visitor alert to the remote computing device via at least one of the wireless network and a cellular network. Methods can also include sending the visitor alert from the chime to the remote computing device in response to the doorbell system detecting that a wireless signal of the doorbell is below a threshold.
In embodiments, a wire communicatively couples the doorbell to the chime. Methods can also include taking a video, by the doorbell, and then sending the video to the chime via the wire. As well, methods can include sending the video from the chime to the remote computing device via the wireless network of the building. Even still, methods may include sending the video from the chime to the remote computing device while the doorbell is located outside of the building and while the chime is located inside of the building.
Methods can include coupling communicatively the chime to a doorlock via the wireless network of the building. As well, methods can include coupling communicatively the chime to a remote sensor via the wireless network of the building. The remote sensor can thereby comprise at least one of a fire alarm, a smoke alarm, a carbon monoxide detector, and a burglar alarm.
Even still, methods can include detecting an adverse event with the chime, wherein the adverse event comprises at least one of a motion, breaking glass, fire, a fire alarm sound, and smoke. As well, methods can include sending an adverse event alert to the remote computing device in response to detecting the adverse event, wherein the adverse event alert comprises a notification of the adverse event.
The disclosure includes a doorbell system including a chime; a remote computing device communicatively coupled to the chime; and a doorbell communicatively coupled with the remote computing device via the chime. In embodiments, the chime can be plugged into a power outlet of a building.
Doorbell systems can include a first communication from the doorbell to the chime. The first communication can comprise a video taken by a camera of the doorbell. As well, doorbell systems can include a second communication from the chime to the remote computing device. The second communication can comprise the video. As well, in embodiments, the remote computing device can comprise a display configurable to display the video.
The doorbell system can also include a sound emitted by a speaker of the chime in response to the doorbell detecting an indication of a presence of a visitor. The chime can also comprise a speaker configurable to play a sound file from the remote computing device. As well, the chime can comprise a light configurable to illuminate.
In embodiments, the chime can include a motion detector; a camera assembly; and a microphone configurable to receive an audible message spoken by a user. Even still, in embodiments, the chime can include a thermometer; a humidity sensor; and a communication system configurable to communicatively couple the chime to at least one of the doorbell and the remote computing device.
The embodiments described above include many optional features and aspects. Features and aspects of the embodiments can be combined.
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.
Although certain embodiments and examples are disclosed below, inventive subject matter extends beyond the specifically disclosed embodiments to other alternative embodiments and/or uses, and to modifications and equivalents thereof. Thus, the scope of the claims appended hereto is not limited by any of the particular embodiments described below. For example, in any method or process disclosed herein, the acts or operations of the method or process may be performed in any suitable sequence and are not necessarily limited to any particular disclosed sequence. Various operations may be described as multiple discrete operations in turn, in a manner that may be helpful in understanding certain embodiments; however, the order of description should not be construed to imply that these operations are order dependent. Additionally, the structures, systems, and/or devices described herein may be embodied as integrated components or as separate components.
For purposes of comparing various embodiments, certain aspects and advantages of these embodiments are described. Not necessarily all such aspects or advantages are achieved by any particular embodiment. Thus, for example, various embodiments may be carried out in a manner that achieves or optimizes one advantage or group of advantages as taught herein without necessarily achieving other aspects or advantages as may also be taught or suggested herein.
The following patent is incorporated herein by reference: U.S. Pat. No. 7,583,191, entitled SECURITY SYSTEM AND METHOD FOR USE OF SAME, and filed Nov. 14, 2006.
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.
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.
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.
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.
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.
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).
Several embodiments use near field communication (NFC) to communicate between the computing device 204 and the doorbell 202. The doorbell 202 and/or the computing device 204 can include a NFC tag. Some NFC technologies include Bluetooth, radio-frequency identification, and QR codes.
Some embodiments include computer software (e.g., application software), which can be a mobile application designed to run on smartphones, tablet computers, and other mobile devices. Software of this nature is sometimes referred to as “app” software. Some embodiments include software designed to run on desktop computers and laptop computers.
The computing device 204 can run software with a graphical user interface. The user interface can include icons or buttons. In some embodiments, the software is configured for use with a touch-screen computing device such as a smartphone or tablet.
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.
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.
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.
In some embodiments, the server 206 can initiate communication to the computer device 204 and/or to the security system 202. In several embodiments, the server 206 can initiate, control, and/or block communication between the computing device 204 and the security system 202.
In several embodiments, a user can log 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.
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).
In some embodiments, the user interface 240 displays an image 252 such as a still image or a video of an area near and/or in front of the security system 202. The image 252 can be taken by the camera assembly 208 and stored by the security system 202, server 206, and/or computing device 204. The user interface 240 can include a recording button 256 to enable a user to record images, videos, and/or sound from the camera assembly 208, microphone of the security system 202, and/or microphone of the computing device 204.
In several embodiments, the user interface 240 includes a picture button 260 to allow the user to take still pictures and/or videos of the area near and/or in front of the security system 202. The user interface 240 can also include a sound adjustment button 264 and a mute button 268. The user interface 240 can include camera manipulation buttons such as zoom, pan, and light adjustment buttons. In some embodiments, the camera assembly 208 automatically adjusts between Day Mode and Night Mode. Some embodiments include an infrared camera and/or infrared lights to illuminate an area near the security system 202 to enable the camera assembly 208 to provide sufficient visibility (even at night).
In some embodiments, buttons include diverse means of selecting various options, features, and functions. Buttons can be selected by mouse clicks, keyboard commands, and touching a touch screen. Many embodiments include buttons that can be selected without touch screens.
In some embodiments, the user interface 240 includes a quality selection button, which can allow a user to select the quality and/or amount of 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.
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.
The user interface 240 can include a termination button 276 to end communication between the security system 202 and the computing device 204. In some embodiments, the termination button 276 ends the ability of the person located near the security system 202 (i.e., the visitor) to hear and/or see the user of the computing device 204, but does not end the ability of the user of the computing device 204 to hear and/or see the person located near the security system 202.
In some embodiments, a button 276 is both an answer button (to accept a communication request from a visitor) and 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.
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.
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.
In some embodiments, the software includes means to start the video feed on demand. For example, a user of the computing device might wonder what is happening near the security system 202. The user can open the software application on the computing device 204 and instruct the application to show live video and/or audio from the security device 202 even if no event near the security system 202 has triggered the communication.
In several embodiments, the security device 202 can be configured to record 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.
Referring now to
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.
Electrical wires 304 can electrically couple the doorbell 202 to the electrical system of the building 300 such that the doorbell 202 can receive electrical power from the building 300. The building can include a door lock 250 to lock the door 254.
A wireless network 308 can allow devices to wirelessly access the Internet. The security system 202 can access the Internet via the wireless network 308. The wireless network 308 can transmit data from the security system 202 to the Internet, which can transmit the data to remotely located computing devices 204. The Internet and wireless networks can transmit data from remotely located computing devices 204 to the security system 202. In some embodiments, a security system 202 connects to a home's WiFi.
As illustrated in
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.
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.
The doorbell 202 can include one or more heating elements 508 configured to regulate the temperature of the doorbell 202. For example, doorbells 202 can be used in very cold environments, such as in Alaska. The heating element 508 can be used in various methods to protect temperature sensitive portions of the doorbell 202 from cold weather.
While protecting the doorbell 202 from cold weather can be important in some embodiments, protecting visitors from excessive heat can also be important in some embodiments. Excessive heat could burn visitors as they “ring” the doorbell (e.g., press the doorbell button 212 shown in
Several embodiments can be configured for 9 to 40 volts alternating current (“VAC”) and/or 9 to 40 volts direct current (“VDC”). Some embodiments convert input electricity into direct current (DC), such as 12 VDC. Several embodiments include a converter 494 for power conversion (e.g., converting electrical energy from one form to another). The converter 494 can convert input power (e.g., from wiring in a building) to a suitable power form for the doorbell 202. The power conversion can convert between AC and DC, change the voltage, and/or change the frequency. The converter 494 can include a transformer and/or a voltage regulator. In several embodiments, the converter 494 can include a DC to DC converter, a voltage stabilizer, a linear regulator, a surge protector, a rectifier, a power supply unit, a switch, an inverter, and/or a voltage converter. In some embodiments, the converter 494 converts 50 Hertz (“Hz”) power into 60 Hz power.
The electrical components of the doorbell 202 (e.g., the camera assembly 208, the memory 492, the chip 480, the speaker 488, the converter 494, the microphone 484, the lights 458, the rectifier 524, the proximity sensor 500, the communication module 504, the heating element 508, the electrical connectors 510, the thermometer 512, the image analysis system 520, and the battery 642) can be electrically coupled to a printed circuit board (“PCB”) 516 and can receive electrical power from the PCB 516.
The PCB 516 and the electrical components of the doorbell 202 can be the electrical system 456 of the doorbell 202. Additional details regarding the PCB 516 and the electrical components of the doorbell 202 are described 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.
Although some embodiments are described in the context of methods, the method embodiments can also be formulated as devices and systems. Methods described herein can be applied to the devices and systems incorporated by references herein.
Video Embodiments
Referring now to
Several embodiments include “on-demand” service. For example, a user can initiate communicate via a doorbell and/or can initiate live video from the doorbell by pressing a button 260 on a user interface (shown in
Situational Sound Embodiments
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.
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.
The security system 202 may detect different indications of a visitor's presence. As shown in
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.
With reference to
As illustrated in
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.
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.
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.
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.
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).
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
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.
To illustrate a more specific example, such as the one shown in
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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
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.
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.
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.
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.
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.
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.
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).
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).
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.
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
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).
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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).
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.
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.
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.
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.
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.
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.
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).
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.
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).
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
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
The custom sound, or custom message, may be received by the doorbell system 200 in a variety of ways. As shown in
As further illustrated in
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
The doorbell system 200 may also be configured to initiate 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.
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 initiate 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.
The doorbell system 200 may also be configured to detect various types of visitors. In some embodiments, as illustrated in
With reference to
As shown in
As well, the doorbell system 200 may be configured to determine various types of visitors. As shown in
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.
The doorbell system 200 may also be configured to emit custom messages in response to the occurrence of predetermined conditions. As illustrated in
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
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
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.
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.
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
With respect to the various predetermined conditions, as shown in
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.
With reference to
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.
As shown in
Chime Embodiments
Chimes 302 (shown in
Referring now to
As illustrated in
Even still, in embodiments, the chime 302 may include additional components including, but not limited to, a thermometer 512b configurable to determine temperature along the inside portion of the building 300 and a humidity sensor 305 configurable to determine humidity along the inside portion of the building 300. The chime 302 may include a detection system 528b that may include miscellaneous detection components to monitor and detect various other events. As well, the chime 302 may include a communication system 504b configurable to communicatively couple the chime to the doorbell 202, the remote computing device 204, and/or any other communication device. The communication system 504b may communicate via WiFi, Bluetooth, Bluetooth Low Energy, Thread, ZigBee, and the like. It should be appreciated that the chime 302 may utilize none, some, or all the same components as utilized by the doorbell 202.
A user can select a sound to be emitted by the chime 302 on her remote computing device 204 by using a control application 600. The remote computing device 204 can then send the sound to the chime 302 via the doorbell 202 (and/or via a server 206 and a wireless network 308). The sound can be a song, a greeting recorded by the user, or any other type of sound. Some embodiments include using a remote computing device 204 to download a sound from the Internet, sending the sound (or data associated with the sound) to the doorbell 202 (e.g., in response to using the remote computing device 204 to select the sound), sending the sound (or data associated with the sound) from the doorbell 202 to the chime 302, and/or emitting the sound from the chime 302.
As shown in
As illustrated in
As illustrated in
As well,
The system 200 can be configured to communicate in various manners. In some embodiments, the remote computing device 204 communicates directly with the doorbell 202, while the doorbell 202 communicates directly with the chime 302. In some embodiments, the remote computing device 204 communicates directly with the chime 302, while the doorbell 202 communicates directly with the chime. Generally, it should be understood that the system 200 can be configured in any manner by the user.
Methods of Using a Chime
According to various embodiments, the doorbell system 200 can emit sounds from a chime 302. As illustrated in
With continued reference to
As well, methods can include the doorbell 202 sending the data file 211, 213 to the chime 302 that is communicatively coupled to the doorbell 202 and remotely located with respect to the doorbell 202 (at step 1304). In embodiments, the data file 211, 213 is transmitted wirelessly to the chime 302. As well, in embodiments, the data file 211, 213 is transmitted via a wire, such as wire 304b, as shown in
There are various ways that the chime 302 can receive the data file 211, 213. In some methods, the data file can be downloaded from a web server, by at least one of the doorbell and the chime. Even still, in some embodiments, the remote computing device 204 can download the data file from the web server.
Methods can also include emitting the sound from a speaker 488b of the chime 302 at least partially in response to the chime 302 receiving the data file 211, 213 and at least partially in response to the doorbell 202 detecting an indication of a presence of a visitor. In this manner, when a visitor visits the building 300, the doorbell system 200 can alert the user by playing any type of customized or prerecorded sound through the speaker 488b of the chime 302.
As well, users of the doorbell system 200 may configure the system 200 to emit the sound in accordance with certain parameters, such as sound emission parameters. Accordingly, methods may include receiving, by the doorbell 202, a sound emission parameter from the remote computing device 204. Methods may also include emitting the sound from a speaker 488b of the chime 302 in response to the doorbell system 202 determining that the sound emission parameter has been met. In some embodiments, the sound emission parameters may comprise predetermined timeframes. For example, the user may elect a sound emission parameter, such as a “do not disturb” parameter, so that the chime 302 does not emit the sound during predetermined hours of the day. As well, in embodiments, the sound emission parameters 302 may comprise specific visitors. For example, if an unknown visitor or unwelcome visitor (e.g. a door-to-door salesperson) visits the building 300, the sound emission parameters can instruct the chime 302 not to emit the sound when the doorbell system 200 detects the presence of the unknown or unwelcome visitor.
The chime 302 may also be configured to emit an audible message from a speaker 488b of the chime 302. The audible message may be a message that is spoken by a user and recorded by the doorbell 202, the remote computing device 204, and/or the chime 302 itself. In embodiments, a user of the system 200 may wish to transmit an audible message through the chime 302. For example, a first resident may speak an audible message such as, “Honey, I'll be home in 30 minutes,” into his/her remote computing device 204. Accordingly, the system 200 may emit the audible message from the chime 302. Furthermore, in embodiments, the first resident my type a message into his/her remote computing device 204, and the system 200 may thereby announce an audible message that comprises the contents of the typed message.
The chime 302 may also be used to detect motion and capture audio and video recordings along an inside portion of a building 300. Specifically, the method may include the motion detector 218b of the chime 302 detecting a first motion within the inside portion of the building 300. Methods may also include initiating a first communication session with the remote computing device 204 in response to the motion detector 218b of the chime 302 detecting the first motion. The first communication session may include a first notification of the first motion detected by the motion detector of the chime. For example, the chime 302 may detect a prowler within the inside portion of the building 300 and the system 200 may thereby send an alert to the remote computing device 204 of the user.
In embodiments, the method may also include the motion detector 218b of the chime 302 detecting a second motion within an inside portion of the building 300. It should be appreciated that the second motion may be different from the first motion, or the same. The system 200 may thereby initiate a second communication session with a second remote computing device 204b in response to the motion detector 218b of the chime 302 detecting the second motion. The second communication session can comprise a second notification of the second motion detected by the chime 302. In this regard, the first remote computing device 204a may not receive the second communication session. Accordingly, the system 200 can be configured to alert different users based on different motions within the building 300. For example, the chime 302 may detect suspicious motions and thereby alert the police. In some examples, the chime 302 may detect non-suspicious motions within the building 300, such as the dog walking around, whereupon an alert is sent to the remote computing device 204 of the resident.
As well, methods may include selecting more than one sound and sending the more than one sound to the chime 302. For example, methods may include selecting a second sound by the remote computing device 204 and thereby sending a second data file comprising second information to the doorbell 202. The second information may represent the second sound. As well, methods may include sending the second data file to the chime 302.
In embodiments, the chime 302 may be configured to emit different sounds in response to different motions detected by the motion detector 218 of the doorbell along an outside portion of the building 300. For example, methods may include detecting a first motion, by a motion detector 218 of the doorbell 202, along the outside portion of the building 300. In response to the doorbell 202 detecting the first motion, the chime may thereby emit the first sound from a speaker 488b of the chime 302. As well, the motion detector 218 of the doorbell 202 may detect a second motion along the outside portion of the building 300. It should be appreciated that the second motion may be different from the first motion, or the same. Accordingly, methods may include emitting the second sound from the speaker 488 of the chime 302 in response to the doorbell 202 detecting the second motion. In this manner, the chime 302 may be configured to audibly alert people within the building 300 as to whether various motions have been detected by the doorbell 202. In embodiments, the chime 302 may emit an audible alarm if the doorbell 202 detects a suspicious motion. In embodiments, the chime 302 may emit a more friendly sound (e.g. “ding-dong”) if the doorbell 202 detects a non-suspicious motion.
As illustrated in
In addition to detecting motion, the chime 302 and/or the doorbell 202 may also capture audio, images and/or video. For example, as shown in
As well, the method may use a microphone 484b of the chime to detect and record audio within the inside portion of the building 300. The audio recording may thereby be transmitted to the doorbell 202 and/or the remote computing device 204, where it can be played back.
As well, the system 200 may be configured to respond in other various ways in response to detecting a motion. For instance, in embodiments, in response to detecting a motion with the motion detector 218b of the chime 302, the doorbell 202 may flash a light 216, 220 to thereby indicate to people passing by the building 300 that there is an event underway at the building 300. This may serve useful to personnel (e.g. law enforcement) to thereby determine the exact location of the building 300.
The chime 302 may be configured to emit any various type of sound in response to any of the previously mentioned components detecting various events. In embodiments, the chime 302 may emit a first sound in response to the doorbell detecting an indication of a presence of a visitor. As well, the chime 302 may emit a second sound in response to the motion detector 218b detecting motion along the inside portion of the building 300. Furthermore, if thermometer 512b detects that the temperature has exceeded a predetermined threshold, the chime 302 may emit a third sound, such as an announcement of the temperature as detected by the thermometer 528b. Even still, the chime 302 may be configured to emit a fourth sound in response to the humidity sensor 305 detecting that a predetermined humidity has been met.
As illustrated in
In order to detect the visitor, methods may include recognizing the first visitor and/or the second visitor by detecting various traits, such as a physical trait of the respective visitor. Physical traits can include traits such as a fingerprint, gait, body type, height, silhouette traits, silhouette volume, silhouette dimensions, other physical characteristics, and the like. As well, the system 200 may be configured to recognize the first visitor and/or the second visitor by the doorbell 202 detecting a trait of an electronic device in the possession of the first visitor and/or the second visitor. For example, the system 200 may be configured to detect a first remote computing device 204d associated with the first visitor and/or a second remote computing device 204e associated with the second visitor. In response to detecting a visitor by physical traits and/or electronic traits, the chime 302 may emit a sound associated with the particular visitor.
The following patent applications, which are incorporated by reference herein, describe additional embodiments of recognizing visitors: U.S. Provisional Patent Application No. 62/135,133; filed Mar. 18, 2015; and entitled DOORBELL COMMUNICATION SYSTEMS AND METHODS; U.S. Provisional Patent Application No. 62/016,050; filed Jun. 23, 2014; and entitled IDENTITY VERIFICATION USING A SOCIAL NETWORK; U.S. Provisional Patent Application No. 62/016,053; filed Jun. 23, 2014; and entitled IDENTITY VERIFICATION USING A SOCIAL NETWORK AND A NAME OF A VISITOR; and U.S. Provisional Patent Application No. 62/016,057; filed Jun. 23, 2014; and entitled IDENTITY VERIFICATION OF FREQUENT AND NON-FREQUENT VISITORS.
Wired Communication Embodiments
In addition to the doorbell system 200 being configured to be electrically and communicatively coupled via any wireless communication standard, the doorbell system 200 may also be electrically and communicatively coupled via any type of wired communication standard (e.g. wires). In embodiments, the wires may be the copper wires of the building 300.
As shown in
Because the doorbell 202 may be communicatively coupled to the chime 302 via the second wire 304b, the chime 302 may be configured to receive a first data file from the doorbell 202 via the second wire 304b. As well, the doorbell system 200 may include a sound file communication 209 that may be sent from the doorbell 202 to the chime 302 via the second wire 304b. In some embodiments, the sound file communication 209 may comprise at least one thousand bytes. As well, in embodiments, the sound file communication 209 may comprise less than one thousand bytes. It should also be appreciated that the second wire 304b may enable two-way communication from the doorbell 202 to the chime 302 and/or from the chime 302 to the doorbell 202.
In embodiments, the first data file may comprise commands to perform various operations or put the doorbell system 200 into various settings. For example, the first data file may comprise a command configured to place the chime 302 into silent mode, such that the chime 302 does not emit a sound. Likewise, the first data file may comprise a command configured to adjust a volume setting of the chime 302. Even still, the first data file may comprise a command configured to adjust a duration of a notification sound emitted by the chime 302. Generally, it should be appreciated that the first data file may command the chime 302 to perform any such operation.
Even still, the data file may comprise data gathered by the doorbell system 200, such as a video recorded by the doorbell 202. Accordingly, the data file may include information regarding an event that occurred outside the chime 302, such as the presence of a prowler or an image of an object associated with a motion detected by the system 200. In this regard, the data file may comprise identifying information regarding the person and/or object detected by the chime 302. For example, the doorbell 202 and/or chime 302 may detect a person located outside or inside the building 300. The chime may then receive the data file that comprises the identity of the person as detected by the doorbell 202 and/or chime 302. As well, the doorbell 202 may wirelessly receive the first data file from the remote computing device 204. In this manner, the doorbell 202 may receive various files, such as audio, and an image and/or video as recorded by the chime via the first wire. It should also be appreciated that the chime 302 may receive the various files from the doorbell 202 and/or the remote computing device 204.
As illustrated in
The information may represent a sound that was unknown to the chime 302 prior to receiving the second data file. In this regard, the method may include emitting the sound from the chime 302 at least partially in response to receiving the second data file. In this regard, the method may include the chime using the second data file to emit a sound. In some embodiments, the second data file may comprise at least one thousand bytes. As well, in embodiments, the second data file may comprise less than one thousand bytes.
As well, the method may include emitting the sound from the chime 302 at least partially in response to the chime 302 receiving a sound emission parameter from the doorbell 202 and/or the remote computing device 204. For example, the chime 302 may receive a sound emission parameter to only emit the sound between the hours of 9 am and 9 pm. Accordingly, if the system 200 detects a presence of a visitor between 9 am and 9 pm, and in response to the chime 302 having received the data file, the chime 302 may emit a sound in response to the doorbell system 200 having determined that the sound emission parameter has been met.
Chime-Hub Communication Embodiments
In embodiments, the chime 302 can serve as the communication hub that links the doorbell 202 to the remote computing device 204, and vice versa. The chime 302 can be configured as the communication hub for a variety of reasons. For example, in certain situations, the doorbell system can be configured to detect whether the doorbell 202 comprises inadequate wireless performance to communicate with a remote computing device 204 via at least one of the wireless network and a cellular network. Accordingly, when the doorbell 202 receives inadequate wireless performance, the doorbell 202 can thereby communicate with the chime 302, which in turn communicates with the remote computing device 204 to thereby communicatively couple the doorbell 202 to the remote computing device 204.
Accordingly, and as illustrated in
In embodiments, the doorbell system can be used to detect an indication of a presence of a visitor and thereby transmit the indication from the doorbell 202 to the remote computing device 204 via the chime 302. The presence of the visitor can be detected via a variety of indications. For example, methods can include detecting, by the doorbell 202, a trigger of a button 212 of the doorbell 202 (at step 1702).
As further illustrated in
Accordingly, the visitor alert 232a can be sent from the doorbell 202 to the chime 302 and/or the remote computing device 204 by a variety of methods. For example, in some embodiments, the doorbell 202 can be communicatively coupled to the chime 302 via a wire, a wireless network of the building 300, and/or a cellular network. As well, the chime 302 can be communicatively coupled to the remote computing device 204 via the wireless network of the building 300 and/or a cellular network. Methods can thereby include sending the visitor alert 232a from the doorbell 202 to the chime 302 via any combination of transmission systems including the wire, wireless network of the building 300, and/or cellular network (at step 1708). As well, methods can include sending the visitor alert 232a from the chime 302 to the remote computing device 204 via any combination including the wireless network of the building 300 and/or cellular network (at step 1708).
In some situations, the doorbell 202 may receive a wireless signal, but the wireless signal may be inadequate to transmit specific communications from the doorbell 202 to the remote computing device 204. In these situations, the chime 302 may serve as the communication hub between the doorbell 202 and the remote computing device 204. Accordingly, methods may include sending the visitor alert 232a from the chime 302 to the remote computing device 204 in response to the doorbell system detecting that the doorbell 202 comprises inadequate wireless performance to send the visitor alert 232a to the remote computing device 204 via at least one of the wireless network and a cellular network (at step 1710). Described differently, some methods can include sending the visitor alert 232a from the chime 302 to the remote computing device 204 in response to the doorbell system detecting that a wireless signal of the doorbell 202 is below a threshold (at step 1712).
The doorbell 202, remote computing device 204, and the chime 302 may be located in different locations with respect to each other. For example, the doorbell 202 may be located outside of the building 300, the chime 302 may be located inside the building 300, and the remote computing device 204 can be remotely located with respect to the building 300. As illustrated in
The visitor alert 232a can take various forms that alert a user that a visitor is present at the doorbell 202 or that a visitor has left a message for the user via the doorbell 202. In this regard, the visitor alert 232a can comprise a video, an image, a sound, a text message, an email, a phone call, and the like. With reference to
Upon the doorbell 202 capturing video, images, sounds, and the like, the doorbell system can thereby include various communications between the doorbell 202 and the chime 302, and between the chime 302 and the remote computing device 204. For example, the doorbell system can include a first communication from the doorbell 202 to the chime 302. The first communication can include a video and/or image taken by a camera 208 of the doorbell 202. Accordingly, the doorbell system can include a second communication from the chime 302 to the remote computing device 204. The second communication can also comprise the video.
Even still, the chime 302 can be communicatively coupled via the wireless network and/or cellular network to other peripheral devices, such as a door lock (e.g. a smart door lock) (at step 1802), a remote sensor (e.g. a fire alarm, a smoke alarm, a carbon monoxide detector, and a burglar alarm) (at step 1804), and the like. In this regard, the chime 302 can serve as the communication hub, not only between the doorbell 202 and the remote computing device 204, but also between the doorbell 202, the remote computing device 204, the door lock, the remote sensor, and any other peripheral device.
By configuring the chime 302 as the communication hub between such devices, the chime 302 may be used to transmit and communicate messages and instructions between devices. For example, a user may enter an instruction on a remote computing device 204 to lock a front door lock. The instruction may then be sent from the remote computing device 204 to the chime 302 whereby the chime 302 sends the instruction to the front door lock to move to a locked position. In response, the front door lock may lock the front door.
In another example, the chime 302 may detect an indication of an adverse event and/or receive the indication of the adverse event from the remote sensor. The adverse event can comprise various events, such as a motion, breaking glass, fire, a fire alarm sound, smoke, and the like. Accordingly, methods can include directly detecting an adverse event with the chime 302 (at step 1806), such as detecting the sound of glass breaking via a microphone of the chime 302. As well, methods can include the chime 302 receiving an indication of the adverse event from the remote sensor that is communicatively coupled to the chime 302, whereby the remote sensor is configured to detect adverse events. As illustrated in
The chime 302 can be configured to communicate with other devices, such as the remote computing device 204, remote sensors, and the like, via any wireless personal area network. For example, the chime 302 can be configured to communicate via Bluetooth, Bluetooth low energy, and the like. In this manner the chime 302 can communicate with Bluetooth low energy tags.
In various embodiments, the chime 302 may include a light configurable to illuminate an area or provide ambient lighting for comfort, such as a nightlight. The light may comprise the diagnostic light 216, the power indicator light 220, and/or any other light electrically coupled to the chime 302. As well, the light may be activated by various means, such as in response to an audible message from a user (e.g. “Max, turn on the light”). Even still, the light may be configurable to activate in response to external conditions, such as darkness of an adjacent area, much like a nightlight.
Referring now to
Remote sensors 418 can include a fire alarm, a smoke alarm, a carbon monoxide detector, a motion sensor, a glass-break sensor, and a burglar alarm. For example, the chime 302 can listen for a smoke alarm. Then, the chime 302 can send a notification to the remote computing device 204 in response to hearing the alarm sound of the smoke alarm.
Some embodiments include sending a second alert from the chime 302 to the remote computing device 204 in response to receiving, by the chime 302, a communication from the remote sensor 418. Several embodiments include coupling communicatively the chime 302 to a remote sensor 418. The remote sensor 418 can comprise at least one of a fire detector, a smoke detector, and a carbon monoxide detector. Embodiments can also include sending a second alert from the chime 302 to the remote computing device 204 in response to receiving, by the chime 302, a communication from the remote sensor 418.
Several embodiments comprise detecting, by a microphone 484b (shown in
Burglars often break glass windows and glass doors to enter homes and other buildings. Some embodiments include detecting, by a microphone 484b of the chime 302, glass breaking, and then sending a second alert from the chime 302 to the remote computing device 204 in response to detecting the glass breaking.
Some systems include a remote sensor 418 having at least one of a fire detector, a smoke detector, a carbon monoxide detector, a motion detector, and a glass-break detector. The remote sensor 418 can be communicatively coupled to the chime 302 (e.g., via wireless communication 230). Systems can include a third communication from the remote sensor 418 to the chime 302.
Several systems include a chime 302 that has a microphone 484b (shown in
Interpretation
None of the steps described herein is essential or indispensable. Any of the steps can be adjusted or modified. Other or additional steps can be used. Any portion of any of the steps, processes, structures, and/or devices disclosed or illustrated in one embodiment, flowchart, or example in this specification can be combined or used with or instead of any other portion of any of the steps, processes, structures, and/or devices disclosed or illustrated in a different embodiment, flowchart, or example. The embodiments and examples provided herein are not intended to be discrete and separate from each other.
The section headings and subheadings provided herein are nonlimiting. The section headings and subheadings do not represent or limit the full scope of the embodiments described in the sections to which the headings and subheadings pertain. For example, a section titled “Topic 1” may include embodiments that do not pertain to Topic 1 and embodiments described in other sections may apply to and be combined with embodiments described within the “Topic 1” section.
Some of the devices, systems, embodiments, and processes use computers. Each of the routines, processes, methods, and algorithms described in the preceding sections may be embodied in, and fully or partially automated by, code modules executed by one or more computers, computer processors, or machines configured to execute computer instructions. The code modules may be stored on any type of non-transitory computer-readable storage medium or tangible computer storage device, such as hard drives, solid state memory, flash memory, optical disc, and/or the like. The processes and algorithms may be implemented partially or wholly in application-specific circuitry. The results of the disclosed processes and process steps may be stored, persistently or otherwise, in any type of non-transitory computer storage such as, e.g., volatile or non-volatile storage.
The various features and processes described above may be used independently of one another, or may be combined in various ways. All possible combinations and subcombinations are intended to fall within the scope of this disclosure. In addition, certain method, event, state, or process blocks may be omitted in some implementations. The methods, steps, and processes described herein are also not limited to any particular sequence, and the blocks, steps, or states relating thereto can be performed in other sequences that are appropriate. For example, described tasks or events may be performed in an order other than the order specifically disclosed. Multiple steps may be combined in a single block or state. The example tasks or events may be performed in serial, in parallel, or in some other manner. Tasks or events may be added to or removed from the disclosed example embodiments. The example systems and components described herein may be configured differently than described. For example, elements may be added to, removed from, or rearranged compared to the disclosed example embodiments.
Conditional language used herein, such as, among others, “can,” “could,” “might,” “may,” “e.g.,” and the like, unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments include, while other embodiments do not include, certain features, elements and/or steps. Thus, such conditional language is not generally intended to imply that features, elements and/or steps are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without author input or prompting, whether these features, elements and/or steps are included or are to be performed in any particular embodiment. The terms “comprising,” “including,” “having,” and the like are synonymous and are used inclusively, in an open-ended fashion, and do not exclude additional elements, features, acts, operations and so forth. Also, the term “or” is used in its inclusive sense (and not in its exclusive sense) so that when used, for example, to connect a list of elements, the term “or” means one, some, or all of the elements in the list. Conjunctive language such as the phrase “at least one of X, Y, and Z,” unless specifically stated otherwise, is otherwise understood with the context as used in general to convey that an item, term, etc. may be either X, Y, or Z. Thus, such conjunctive language is not generally intended to imply that certain embodiments require at least one of X, at least one of Y, and at least one of Z to each be present.
The term “and/or” means that “and” applies to some embodiments and “or” applies to some embodiments. Thus, A, B, and/or C can be replaced with A, B, and C written in one sentence and A, B, or C written in another sentence. A, B, and/or C means that some embodiments can include A and B, some embodiments can include A and C, some embodiments can include B and C, some embodiments can only include A, some embodiments can include only B, some embodiments can include only C, and some embodiments include A, B, and C. The term “and/or” is used to avoid unnecessary redundancy.
While certain example embodiments have been described, these embodiments have been presented by way of example only, and are not intended to limit the scope of the inventions disclosed herein. Thus, nothing in the foregoing description is intended to imply that any particular feature, characteristic, step, module, or block is necessary or indispensable. Indeed, the novel methods and systems described herein may be embodied in a variety of other forms; furthermore, various omissions, substitutions, and changes in the form of the methods and systems described herein may be made without departing from the spirit of the inventions disclosed herein.
The entire contents of the following application are incorporated by reference herein: U.S. Nonprovisional patent application Ser. No. 16/920,611; filed Jul. 3, 2020; and entitled DOORBELL COMMUNICATION SYSTEMS AND METHODS. The entire contents of the following application are incorporated by reference herein: U.S. Nonprovisional patent application Ser. No. 16/057,169; filed Aug. 7, 2018; and entitled DOORBELL COMMUNICATION SYSTEMS AND METHODS. The entire contents of the following application are incorporated by reference herein: U.S. Nonprovisional patent application Ser. No. 16/054,961; filed Aug. 3, 2018; and entitled DOORBELL COMMUNICATION SYSTEMS AND METHODS. The entire contents of the following application are incorporated by reference herein: U.S. Nonprovisional patent application Ser. No. 14/861,613; filed Sep. 22, 2015; and entitled DOORBELL COMMUNICATION SYSTEMS AND METHODS. The entire contents of the following application are incorporated by reference herein: U.S. Nonprovisional patent application Ser. No. 14/737,411; filed Jun. 11, 2015; and entitled DOORBELL CHIME SYSTEMS AND METHODS. The entire contents of the following application are incorporated by reference herein: U.S. Nonprovisional patent application Ser. No. 14/724,723; filed May 28, 2015; and entitled DOORBELL CHIME SYSTEMS AND METHODS. The entire contents of the following application are incorporated by reference herein: U.S. Nonprovisional patent application Ser. No. 14/724,702; filed May 28, 2015; and entitled DOORBELL CHIME SYSTEMS AND METHODS. The entire contents of the following application are incorporated by reference herein: U.S. Nonprovisional patent application Ser. No. 14/695,436; filed Apr. 24, 2015; and entitled DOORBELL COMMUNICATION SYSTEMS AND METHODS. The entire contents of the following application are incorporated by reference herein: 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 the following application are incorporated by reference herein: U.S. Nonprovisional patent application Ser. No. 14/664,345; filed Mar. 20, 2015; and entitled DOORBELL COMMUNICATION SYSTEMS AND METHODS.
| Number | Name | Date | Kind |
|---|---|---|---|
| 3480727 | Moore | Nov 1969 | A |
| 4075659 | Desanti | Feb 1978 | A |
| 4370675 | Cohn | Jan 1983 | A |
| 4524384 | Lefkowitz | Jun 1985 | A |
| 4764953 | Chern | Aug 1988 | A |
| 4843461 | Tatsumi | Jun 1989 | A |
| 4959713 | Morotomi | Sep 1990 | A |
| 4982092 | Jehle | Jan 1991 | A |
| 5151945 | Lee | Sep 1992 | A |
| 5210520 | Housley | May 1993 | A |
| 5428388 | Von Bauer | Jun 1995 | A |
| 5521578 | Delvalle | May 1996 | A |
| 5717379 | Peters | Feb 1998 | A |
| 5781108 | Jacob | Jul 1998 | A |
| 5799130 | Hoshi | Aug 1998 | A |
| 5822542 | Smith | Oct 1998 | A |
| 5861804 | Fansa | Jan 1999 | A |
| 5878283 | House | Mar 1999 | A |
| 5907352 | Gilley | May 1999 | A |
| 6028626 | Aviv | Feb 2000 | A |
| 6060994 | Chen | May 2000 | A |
| 6064303 | Klein | May 2000 | A |
| 6069655 | Seeley | May 2000 | A |
| 6097429 | Seeley | Aug 2000 | A |
| 6104785 | Chen | Aug 2000 | A |
| 6134303 | Chen | Oct 2000 | A |
| 6154130 | Mondejar | Nov 2000 | A |
| 6185294 | Chornenky | Feb 2001 | B1 |
| 6313743 | Abraham-Fuchs | Nov 2001 | B1 |
| 6323897 | Kogane | Nov 2001 | B1 |
| 6359560 | Budge | Mar 2002 | B1 |
| 6385772 | Courtney | May 2002 | B1 |
| 6400265 | Saylor | Jun 2002 | B1 |
| 6414589 | Angott | Jul 2002 | B1 |
| 6421080 | Lambert | Jul 2002 | B1 |
| 6424371 | Wen | Jul 2002 | B1 |
| 6429893 | Xin | Aug 2002 | B1 |
| 6476858 | Diaz | Nov 2002 | B1 |
| 6542078 | Script | Apr 2003 | B2 |
| 6661340 | Saylor | Dec 2003 | B1 |
| 6816085 | Haynes | Nov 2004 | B1 |
| 6828909 | Script | Dec 2004 | B2 |
| 6870488 | Compton | Mar 2005 | B1 |
| 6943682 | Dowens | Sep 2005 | B1 |
| 6956478 | Oyagi | Oct 2005 | B2 |
| 6993123 | Allen | Jan 2006 | B1 |
| 7012523 | Stuart | Mar 2006 | B2 |
| 7015943 | Chiang | Mar 2006 | B2 |
| 7019770 | Katz | Mar 2006 | B1 |
| 7113090 | Saylor | Sep 2006 | B1 |
| 7119609 | Naidoo | Oct 2006 | B2 |
| 7123142 | Bohbot | Oct 2006 | B2 |
| 7187279 | Chung | Mar 2007 | B2 |
| 7193644 | Carter | Mar 2007 | B2 |
| 7218220 | Bovsun | May 2007 | B1 |
| 7242295 | Milnusic | Jul 2007 | B1 |
| 7262690 | Heaton | Aug 2007 | B2 |
| 7277010 | Joao | Oct 2007 | B2 |
| 7310111 | Ramirez-Diaz | Dec 2007 | B2 |
| 7375492 | Calhoon | May 2008 | B2 |
| 7403116 | Bittner | Jul 2008 | B2 |
| 7440025 | Cheng | Oct 2008 | B2 |
| 7477134 | Langer | Jan 2009 | B2 |
| 7529485 | Farmer | May 2009 | B2 |
| 7583191 | Zinser | Sep 2009 | B2 |
| 7609941 | Matsukawa | Oct 2009 | B2 |
| 7701171 | Defant | Apr 2010 | B2 |
| 7738917 | Ryley | Jun 2010 | B2 |
| 7746223 | Howarter | Jun 2010 | B2 |
| 7786891 | Owens | Aug 2010 | B2 |
| 7809966 | Imao | Oct 2010 | B2 |
| 7952609 | Simerly | May 2011 | B2 |
| 7956576 | Neu | Jun 2011 | B2 |
| 7956739 | Hong | Jun 2011 | B2 |
| 7991381 | Dunne | Aug 2011 | B1 |
| 8125329 | Hirou | Feb 2012 | B1 |
| 8138098 | Yu | Mar 2012 | B2 |
| 8144183 | Carter | Mar 2012 | B2 |
| 8144184 | Carter | Mar 2012 | B2 |
| 8154581 | Carter | Apr 2012 | B2 |
| 8164614 | Carter | Apr 2012 | B2 |
| 8237574 | Anderson | Aug 2012 | B2 |
| 8354914 | Buckingham | Jan 2013 | B2 |
| 8504103 | Ficquette | Aug 2013 | B2 |
| 8520068 | Naidoo | Aug 2013 | B2 |
| 8562158 | Chien | Oct 2013 | B2 |
| 8619136 | Howarter | Dec 2013 | B2 |
| 8669876 | Anderson | Mar 2014 | B2 |
| 8875208 | Abkairov | Oct 2014 | B1 |
| 8947530 | Scalisi | Feb 2015 | B1 |
| 8948245 | Henson | Feb 2015 | B2 |
| 8976244 | Felt | Mar 2015 | B2 |
| 9021134 | Patel | Apr 2015 | B1 |
| 9250267 | Jackson | Feb 2016 | B1 |
| 9300921 | Naidoo | Mar 2016 | B2 |
| 9414030 | Carter | Aug 2016 | B2 |
| 9432638 | Carter | Aug 2016 | B2 |
| 9485478 | Carter | Nov 2016 | B2 |
| 9516284 | Carter | Dec 2016 | B2 |
| 9554090 | Carter | Jan 2017 | B1 |
| 9635323 | Carter | Apr 2017 | B2 |
| 9648290 | Carter | May 2017 | B2 |
| 9697723 | Ladanyi | Jul 2017 | B1 |
| 9706178 | Carter | Jul 2017 | B2 |
| 9866802 | Carter | Jan 2018 | B2 |
| 9924141 | Carter | Mar 2018 | B2 |
| 9955090 | Yang | Apr 2018 | B2 |
| 10097796 | Carter | Oct 2018 | B2 |
| 10097797 | Carter | Oct 2018 | B2 |
| 10200660 | Carter | Feb 2019 | B2 |
| 10356303 | Jordan | Jul 2019 | B1 |
| 10523906 | Carter | Dec 2019 | B2 |
| 10674120 | Carter | Jun 2020 | B2 |
| 10863147 | Carter | Dec 2020 | B2 |
| 10977797 | Carter | Apr 2021 | B2 |
| 20010022627 | Bernhardt | Sep 2001 | A1 |
| 20020016971 | Berezowski | Feb 2002 | A1 |
| 20020030583 | Jang | Mar 2002 | A1 |
| 20020067259 | Fufidio | Jun 2002 | A1 |
| 20020071031 | Lord | Jun 2002 | A1 |
| 20020075307 | Alexander | Jun 2002 | A1 |
| 20020076049 | Alexander | Jun 2002 | A1 |
| 20020097161 | Deeds | Jul 2002 | A1 |
| 20020118283 | Guerrero | Aug 2002 | A1 |
| 20020147982 | Naidoo | Aug 2002 | A1 |
| 20030013503 | Menard | Jan 2003 | A1 |
| 20030046557 | Miller | Mar 2003 | A1 |
| 20030061344 | Monroe | Mar 2003 | A1 |
| 20030062997 | Naidoo | Apr 2003 | A1 |
| 20030071724 | D'Amico | Apr 2003 | A1 |
| 20030075287 | Weik | Apr 2003 | A1 |
| 20030081747 | Ahlstrom | May 2003 | A1 |
| 20030095184 | Lin | May 2003 | A1 |
| 20030095185 | Naifeh | May 2003 | A1 |
| 20030103138 | Assayag | Jun 2003 | A1 |
| 20030122514 | Mercier | Jul 2003 | A1 |
| 20030169178 | Jensen | Sep 2003 | A1 |
| 20030171930 | Junqua | Sep 2003 | A1 |
| 20030206101 | Dixon | Nov 2003 | A1 |
| 20030117280 | Prehn | Dec 2003 | A1 |
| 20040003051 | Krzyanowski | Jan 2004 | A1 |
| 20040036603 | Bingham | Feb 2004 | A1 |
| 20040080615 | Klein | Apr 2004 | A1 |
| 20040080627 | Kroll | Apr 2004 | A1 |
| 20040085205 | Yeh | May 2004 | A1 |
| 20040095254 | Maruszczak | May 2004 | A1 |
| 20040178889 | Buckingham | Sep 2004 | A1 |
| 20040229569 | Franz | Nov 2004 | A1 |
| 20040257336 | Hershkovitz | Dec 2004 | A1 |
| 20040257670 | Kawakami | Dec 2004 | A1 |
| 20050001717 | Bohbot | Jan 2005 | A1 |
| 20050006528 | Movsesian | Jan 2005 | A1 |
| 20050007451 | Chiang | Jan 2005 | A1 |
| 20050040954 | McNally | Feb 2005 | A1 |
| 20050071879 | Haldavnekar | Mar 2005 | A1 |
| 20050116480 | Deng | Jun 2005 | A1 |
| 20050165612 | Van Rysselberghe | Jul 2005 | A1 |
| 20050259641 | Beninato | Nov 2005 | A1 |
| 20050285934 | Carter | Dec 2005 | A1 |
| 20050285944 | Watanabe | Dec 2005 | A1 |
| 20060010504 | Sharma | Jan 2006 | A1 |
| 20060038663 | Steinetz | Feb 2006 | A1 |
| 20060087993 | Sengupta | Apr 2006 | A1 |
| 20060093187 | Mittal | May 2006 | A1 |
| 20060095539 | Renkis | May 2006 | A1 |
| 20060100002 | Luebke | May 2006 | A1 |
| 20060139449 | Cheng | Jun 2006 | A1 |
| 20060152365 | Kim | Jul 2006 | A1 |
| 20060156361 | Wang | Jul 2006 | A1 |
| 20060171453 | Rohlfing | Aug 2006 | A1 |
| 20060187034 | Styers | Aug 2006 | A1 |
| 20060195872 | Seo | Aug 2006 | A1 |
| 20060255931 | Hartsfield | Nov 2006 | A1 |
| 20060271678 | Jessup | Nov 2006 | A1 |
| 20060273895 | Kollin | Dec 2006 | A1 |
| 20070008081 | Tylicki | Jan 2007 | A1 |
| 20070025712 | Jezierski | Feb 2007 | A1 |
| 20070046442 | Bartorelli | Mar 2007 | A1 |
| 20070052531 | Matthews | Mar 2007 | A1 |
| 20070066316 | Hoover | Mar 2007 | A1 |
| 20070103548 | Carter | May 2007 | A1 |
| 20070109441 | Cheng | May 2007 | A1 |
| 20070118831 | Kondo | May 2007 | A1 |
| 20070126574 | Langer | Jun 2007 | A1 |
| 20070146115 | Roosli | Jun 2007 | A1 |
| 20070146122 | Ratner | Jun 2007 | A1 |
| 20070162748 | Okayama | Jul 2007 | A1 |
| 20080036862 | Lang | Feb 2008 | A1 |
| 20080047287 | Ruppert | Feb 2008 | A1 |
| 20080117299 | Carter | May 2008 | A1 |
| 20080128586 | Johnson | Jun 2008 | A1 |
| 20080129498 | Howarter | Jun 2008 | A1 |
| 20080145050 | Mayer | Jun 2008 | A1 |
| 20080157936 | Ebrom | Jul 2008 | A1 |
| 20080157956 | Radivojevic | Jul 2008 | A1 |
| 20080167072 | Berstis | Jul 2008 | A1 |
| 20080198225 | Gal | Aug 2008 | A1 |
| 20080291036 | Richmond | Nov 2008 | A1 |
| 20080297339 | Mathews | Dec 2008 | A1 |
| 20090042604 | Ficquette | Feb 2009 | A1 |
| 20090059002 | Kim | Mar 2009 | A1 |
| 20090072963 | Langer | Mar 2009 | A1 |
| 20090093235 | Grealish | Apr 2009 | A1 |
| 20090141939 | Chambers | Jun 2009 | A1 |
| 20090167862 | Jentoft | Jul 2009 | A1 |
| 20090207249 | Erel | Aug 2009 | A1 |
| 20090224912 | Sobol | Sep 2009 | A1 |
| 20090243852 | Haupt | Oct 2009 | A1 |
| 20090296641 | Bienas | Dec 2009 | A1 |
| 20090308116 | Lambrou | Dec 2009 | A1 |
| 20100087161 | Young | Apr 2010 | A1 |
| 20100103300 | Jones | Apr 2010 | A1 |
| 20100134072 | Neu | Jun 2010 | A1 |
| 20100195810 | Mota | Aug 2010 | A1 |
| 20100225455 | Claiborne | Sep 2010 | A1 |
| 20100245060 | Tylicki | Sep 2010 | A1 |
| 20100276570 | Moser | Nov 2010 | A1 |
| 20110028118 | Thomas | Feb 2011 | A1 |
| 20110121940 | Jones | May 2011 | A1 |
| 20110140845 | Sanders | Jun 2011 | A1 |
| 20110287718 | Abel | Nov 2011 | A1 |
| 20120027248 | Feris | Feb 2012 | A1 |
| 20120044050 | Vig | Feb 2012 | A1 |
| 20120044085 | Hung | Feb 2012 | A1 |
| 20120098439 | Recker | Apr 2012 | A1 |
| 20120113253 | Slater | May 2012 | A1 |
| 20120162416 | Su | Jun 2012 | A1 |
| 20120229282 | Zagami | Sep 2012 | A1 |
| 20120230203 | Casey | Sep 2012 | A1 |
| 20120267962 | Hanchett | Oct 2012 | A1 |
| 20120287123 | Starner | Nov 2012 | A1 |
| 20120293310 | Fitzgibbon | Nov 2012 | A1 |
| 20120327246 | Senior | Dec 2012 | A1 |
| 20130020875 | Wozniak | Jan 2013 | A1 |
| 20130045763 | Ruiz | Feb 2013 | A1 |
| 20130057695 | Huisking | Mar 2013 | A1 |
| 20130057696 | Felt | Mar 2013 | A1 |
| 20130128050 | Aghdasi | May 2013 | A1 |
| 20130130749 | Andersen | May 2013 | A1 |
| 20130147964 | Frank | Jun 2013 | A1 |
| 20130169809 | Grignan | Jul 2013 | A1 |
| 20130169814 | Liu | Jul 2013 | A1 |
| 20130201316 | Binder | Aug 2013 | A1 |
| 20130208123 | Lakhani | Aug 2013 | A1 |
| 20130328522 | Brockman | Dec 2013 | A1 |
| 20130335219 | Malkowski | Dec 2013 | A1 |
| 20140009609 | Webster | Jan 2014 | A1 |
| 20140015967 | Moore | Jan 2014 | A1 |
| 20140070922 | Davis | Mar 2014 | A1 |
| 20140087780 | Abhyanker | Mar 2014 | A1 |
| 20140088761 | Shamlian | Mar 2014 | A1 |
| 20140167676 | Mack | Jun 2014 | A1 |
| 20140253725 | Hsu | Sep 2014 | A1 |
| 20140265359 | Cheng | Sep 2014 | A1 |
| 20140266669 | Fadell | Sep 2014 | A1 |
| 20140266767 | Huang | Sep 2014 | A1 |
| 20140267716 | Child | Sep 2014 | A1 |
| 20140267740 | Almomani | Sep 2014 | A1 |
| 20140285672 | Hogasten | Sep 2014 | A1 |
| 20150022618 | Siminoff | Jan 2015 | A1 |
| 20150022620 | Siminoff | Jan 2015 | A1 |
| 20150027178 | Scalisi | Jan 2015 | A1 |
| 20150035987 | Fernandez | Feb 2015 | A1 |
| 20150061859 | Matsuoka | Mar 2015 | A1 |
| 20150109111 | Lee | Apr 2015 | A1 |
| 20150120015 | Fadell | Apr 2015 | A1 |
| 20150156031 | Fadell | Jun 2015 | A1 |
| 20150163463 | Hwang | Jun 2015 | A1 |
| 20150185964 | Stout | Jul 2015 | A1 |
| 20150194839 | Wojcik | Jul 2015 | A1 |
| 20150208032 | Gavney | Jul 2015 | A1 |
| 20150228281 | Raniere | Aug 2015 | A1 |
| 20150236966 | Francini | Aug 2015 | A1 |
| 20150245163 | Candelore | Aug 2015 | A1 |
| 20150276266 | Warren | Oct 2015 | A1 |
| 20150276820 | Floyd | Oct 2015 | A1 |
| 20150339895 | Chen | Nov 2015 | A1 |
| 20160001719 | Frost | Jan 2016 | A1 |
| 20160057199 | Aziz | Feb 2016 | A1 |
| 20160078699 | Kalb | Mar 2016 | A1 |
| 20160261425 | Horton | Sep 2016 | A1 |
| 20160292936 | Palmer | Oct 2016 | A1 |
| 20160314663 | Glencross | Oct 2016 | A1 |
| 20170109984 | Child | Apr 2017 | A1 |
| 20170149855 | Doshi | May 2017 | A1 |
| 20180019889 | Burns | Jan 2018 | A1 |
| 20180032979 | Siminoff | Feb 2018 | A1 |
| 20190058720 | Lindquist | Feb 2019 | A1 |
| 20190066471 | Jeon | Feb 2019 | A1 |
| 20190206243 | Siminoff | Jul 2019 | A1 |
| Number | Date | Country |
|---|---|---|
| 2228679 | Aug 1999 | CA |
| 2691774 | Aug 2010 | CA |
| 2131143 | Apr 1993 | CN |
| 2304927 | Jan 1999 | CN |
| 1704985 | Dec 2005 | CN |
| 101023466 | Aug 2007 | CN |
| 201266988 | Jul 2009 | CN |
| 102254385 | Nov 2011 | CN |
| 103348074 | Oct 2013 | CN |
| 103856739 | Jun 2014 | CN |
| 2759804 | Aug 1998 | FR |
| 2285365 | Jul 1995 | GB |
| H09107409 | Apr 1997 | JP |
| 19980039422 | Aug 1998 | KR |
| 20010074212 | Aug 2001 | KR |
| 100373449 | Sep 2001 | KR |
| 1999006976 | Feb 1999 | WO |
| 2001027763 | Apr 2001 | WO |
| 2001050731 | Jul 2001 | WO |
| 2001093220 | Dec 2001 | WO |
| 2001097524 | Dec 2001 | WO |
| 2002005220 | Jan 2002 | WO |
| 2002065420 | Aug 2002 | WO |
| 2003028375 | Apr 2003 | WO |
| 2006046234 | May 2006 | WO |
| 2007111802 | Oct 2007 | WO |
| 2008021312 | Feb 2008 | WO |
| Entry |
|---|
| Panasonic—“Panasonic Network Camera Operating Instructions Model No. KX-HCM270”—Instruction Manual—Printed in Japan, 2002—Downloaded Jun. 9, 2021—Available from Internet <URL: http://www.voicesonic.com/panasonic/manuals/Panasonic_Cameras/KX-HCM270_Network_Camera_Manual.pdf>. |
| Axis—“Axis adds wireless capability to its video offerings—introduces two new WLAN products”—Press Release—Published Feb. 24, 2003, Lund, Sweden—Downloaded Jun. 9, 2021—Available from Internet <URL: https://www.axis.com/files/press_releases/80211b_devices_pressrelease.pdf>. |
| Ching-Kai, Huang; and Tsuhan, Chen—“Motion Activated Video Surveillance Using TI DSP”—Carnegie Mellon University—Published DSPS Fest '99, Houston, Texas, Aug. 4-6, 1999—Downloaded Jun. 9, 2021—Available from Internet <URL: https://www.ti.com/sc/docs/general/dsp/fest99/avi/1paper.pdf>. |
| National Institute of Justice—“Video Surveillance Equipment Selection and Application Guide”—NIJ Guide 201-99—Published Oct. 1999, Rockville, MD—Downloaded Jun. 9, 2021—Available from Internet <URL: https://www.ojp.gov/pdffiles1/nij/179545.pdf>. |
| Schwartz, John—“Nanny-Cam May Leave a Home Exposed”—New York Times—Published Apr. 14, 2002—Downloaded Jun. 9, 2021—Available from Internet <URL: https://www.nytimes.com/2002/04/14/business/nanny-cam-may-leave-a-home-exposed.html>. |
| Nguyen, Duy—“Mobile Home Security with GPRS”—Edith Cowan University—Published 2002—Downloaded Jun. 9, 2021—Available from Internet <URL: https://ro.ecu.edu.au/theses_hons/339/>. |
| Raggio, Marco; Berbieri, Ivano; and Bailo, Gianluca—“Scalable Multimedia System for Interactive Surveillance and Video Communication Applications”—IEEE 10th European Signal Processing Conference, Sep. 4-8, 2000, Genova, Italy—pp. 1-4—Downloaded Jun. 9, 2021—Available from Internet <URL: https://ieeexplore.ieee.org/document/7075784>. |
| X10 Wireless Technology, Inc.—“XCam2™ and WideEey™ Indoor/Outdoor Wireless Camer System”—Owner's Manual—Downloaded Jun. 9, 2021—Available from Internet <URL: http://www.electronicoscaldas.com/datasheet/XCam2-WideEye_X10.pdf>. |
| Axis—“Axis 2100 Network Camera Users Guide V.1.2”—Technical User Manual—Published May 2001—Downloaded Jun. 9, 2021—Available from Internet <URL: https://docs.rs-online.com/7155/0900766b800a94f9.pdf>. |
| Enterasys Networks—“Enterasys Networks™ delivers the industry's first 54 megabit wireless access point”—Canada News Wire—Published Apr. 30, 2001—Downloaded Apr. 15, 2021—Available from Internet <URL: https://global-factiva-com.libproxy.mit.edu/hp/printsavews.aspx?pp=Print&hc=All>. |
| Panasonic—“Panasonic Network Cameras, including Model No. KC-HCM270”—Webstore Page—Downloaded Jun. 9, 2021—Available from Internet <URL: https://security.panasonic.com/products_technology/products/kx-hcm270/>. |
| Axis—“Axis Network Cameras, including Axis 2100”—Webstore Page—Downloaded Jun. 9, 2021—Available from Internet <URL: https://www.axis.com/products/axis-2100>. |
| Menard, Raymond J., et al.—“Modular Communication System and Method”—U.S. Appl. No. 09/579,913, filed May 26, 2000—Downloaded Jun. 9, 2021—Available from Internet <URL: https://patentscope.wipo.int/search/en/detail.jsf?docId=WO2001093220&tab=PCTDOCUMENTS>. |
| CNIPA—China National Intellectual Property Administration; Notification of the Third Office Action of CN Application No. 201510309496.5; dated Nov. 15, 2019. |
| CNIPA—China National Intellectual Property Administration; Notification of the First Office Action of CN Application No. 201510309104.5; dated Feb. 7, 2018. |
| Number | Date | Country | |
|---|---|---|---|
| 20220353107 A1 | Nov 2022 | US |
| Number | Date | Country | |
|---|---|---|---|
| 62161616 | May 2015 | US | |
| 62127660 | Mar 2015 | US | |
| 61872439 | Aug 2013 | US | |
| 61859070 | Jul 2013 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16920611 | Jul 2020 | US |
| Child | 17863325 | US | |
| Parent | 16057169 | Aug 2018 | US |
| Child | 16920611 | US | |
| Parent | 16054961 | Aug 2018 | US |
| Child | 16057169 | US | |
| Parent | 14861613 | Sep 2015 | US |
| Child | 16054961 | US | |
| Parent | 14724702 | May 2015 | US |
| Child | 14724723 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 14737411 | Jun 2015 | US |
| Child | 14861613 | US | |
| Parent | 14724723 | May 2015 | US |
| Child | 14737411 | US | |
| Parent | 14695436 | Apr 2015 | US |
| Child | 14724702 | US | |
| Parent | 14684302 | Apr 2015 | US |
| Child | 14695436 | US | |
| Parent | 14612376 | Feb 2015 | US |
| Child | 14684302 | US | |
| Parent | 14664345 | Mar 2015 | US |
| Child | 14612376 | US | |
| Parent | 14492809 | Sep 2014 | US |
| Child | 14664345 | US | |
| Parent | 14275811 | May 2014 | US |
| Child | 14492809 | US |
