US20200120309A1 - Accessing cameras of audio/video recording and communication devices based on location - Google Patents
Accessing cameras of audio/video recording and communication devices based on location Download PDFInfo
- Publication number
- US20200120309A1 US20200120309A1 US16/716,383 US201916716383A US2020120309A1 US 20200120309 A1 US20200120309 A1 US 20200120309A1 US 201916716383 A US201916716383 A US 201916716383A US 2020120309 A1 US2020120309 A1 US 2020120309A1
- Authority
- US
- United States
- Prior art keywords
- client device
- recording
- communication
- communication device
- proximity zone
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N7/00—Television systems
- H04N7/18—Closed-circuit television [CCTV] systems, i.e. systems in which the video signal is not broadcast
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M1/00—Substation equipment, e.g. for use by subscribers
- H04M1/02—Constructional features of telephone sets
- H04M1/0291—Door telephones
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M1/00—Substation equipment, e.g. for use by subscribers
- H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
- H04M1/724—User interfaces specially adapted for cordless or mobile telephones
- H04M1/72403—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
- H04M1/72409—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality by interfacing with external accessories
- H04M1/72412—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality by interfacing with external accessories using two-way short-range wireless interfaces
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M1/00—Substation equipment, e.g. for use by subscribers
- H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
- H04M1/724—User interfaces specially adapted for cordless or mobile telephones
- H04M1/72403—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
- H04M1/72418—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality for supporting emergency services
-
- H04M1/7253—
-
- H04M1/72536—
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M11/00—Telephonic communication systems specially adapted for combination with other electrical systems
- H04M11/02—Telephonic communication systems specially adapted for combination with other electrical systems with bell or annunciator systems
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M11/00—Telephonic communication systems specially adapted for combination with other electrical systems
- H04M11/02—Telephonic communication systems specially adapted for combination with other electrical systems with bell or annunciator systems
- H04M11/025—Door telephones
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
- H04N21/41—Structure of client; Structure of client peripherals
- H04N21/422—Input-only peripherals, i.e. input devices connected to specially adapted client devices, e.g. global positioning system [GPS]
- H04N21/4223—Cameras
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
- H04N21/43—Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
- H04N21/442—Monitoring of processes or resources, e.g. detecting the failure of a recording device, monitoring the downstream bandwidth, the number of times a movie has been viewed, the storage space available from the internal hard disk
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
- H04N21/43—Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
- H04N21/442—Monitoring of processes or resources, e.g. detecting the failure of a recording device, monitoring the downstream bandwidth, the number of times a movie has been viewed, the storage space available from the internal hard disk
- H04N21/4424—Monitoring of the internal components or processes of the client device, e.g. CPU or memory load, processing speed, timer, counter or percentage of the hard disk space used
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
- H04N21/47—End-user applications
- H04N21/482—End-user interface for program selection
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N7/00—Television systems
- H04N7/18—Closed-circuit television [CCTV] systems, i.e. systems in which the video signal is not broadcast
- H04N7/183—Closed-circuit television [CCTV] systems, i.e. systems in which the video signal is not broadcast for receiving images from a single remote source
- H04N7/186—Video door telephones
Definitions
- the present embodiments relate to audio/video (A/V) recording and communication devices, including A/V recording and communication doorbell systems.
- A/V audio/video
- the present embodiments relate to improvements in the functionality of A/V recording and communication devices that strengthen the ability of such devices to reduce crime and enhance public safety.
- Audio/Video (A/V) recording and communication devices such as doorbells, provide this functionality, and can also aid in crime detection and prevention.
- A/V recording and communication doorbell can be uploaded to the cloud and recorded on a remote server. Subsequent review of the A/V footage can aid law enforcement in capturing perpetrators of home burglaries and other crimes.
- the presence of one or more an A/V recording and communication devices on the exterior of a home, such as a doorbell unit at the entrance of a home acts as a powerful deterrent against would-be burglars.
- One aspect of the present embodiments includes the realization that as A/V recording and communication devices continue to become more prevalent, leveraging the functionalities of these devices (e.g., video doorbells, security cameras, etc.) by persons other than the owners/users of the A/V recording and communication devices may prove increasingly useful.
- Current A/V recording and communication devices, other than the present embodiments sometimes do not allow persons other than the owner/user of the A/V recording and communication device access to the device's functionalities (e.g., the camera, the speaker, etc.). As a result, there may be missed opportunities for persons other than the owners/users of the A/V recording and communication devices to leverage these functionalities to provide safety, security, and peace of mind.
- a neighborhood may include a plurality of A/V recording and communication devices installed at various homes, and the neighborhood may be dark and/or dangerous.
- a person walking through the neighborhood may desire to view video being recorded in a field of view of one or more of the A/V recording and communication devices in order to determine if there is any suspicious activity or suspicious persons in the neighborhood.
- the present embodiments solve this problem by leveraging the functionality of A/V recording and communication devices, such as A/V recording and communication doorbells, to allow access to the A/V recording and communication devices by users of client devices in proximity to the A/V recording and communication devices.
- A/V recording and communication devices such as A/V recording and communication doorbells
- the users of the client devices may be able to determine if any suspicious activity and/or persons are present, and in response, take the appropriate action. For example, the users of the client devices may notify law enforcement, leave the area, signal for help, signal an alarm, and/or speak to a suspicious person through a speaker of one or more of the A/V recording and communication devices.
- the users of the client devices in proximity to the A/V recording and communication devices may be able to leverage the functionalities of the devices, the safety of the users and the neighborhood, in addition to the overall public safety, may be increased.
- a client device including a display, a communication module, and a processor, in response to entering a proximity zone of an audio/video (A/V) recording and communication device, requests, by the processor using the communication module, access to a camera of the A/V recording and communication device; in response to the request for access, receives, by the processor using the communication module, from the camera, image data being recorded by the camera in a field of view of the camera; and displays, by the processor on the display, the image data.
- A/V audio/video
- the A/V recording and communication device is visible to a user of the client device when the client device is within the proximity zone.
- the proximity zone is defined by the A/V recording and communication device.
- the proximity zone includes the field of view of the camera of the A/V recording and communication device.
- the client device determines, by the processor, that the client device has entered the proximity zone.
- determining that the client device has entered the proximity zone includes comparing client device location data to proximity zone location data.
- the client device location data and the proximity zone location data include at least one of global positioning system (GPS) data and Wi-Fi positioning system (WPS) data.
- GPS global positioning system
- WPS Wi-Fi positioning system
- the client device prior to receiving the image data and after requesting access, the client device establishes a connection to the A/V recording and communication device.
- establishing the connection includes connecting to a network of the A/V recording and communication device.
- the network is a Wi-Fi network.
- the network is an ad hoc network generated by the A/V recording and communication device.
- connection to the network is an unsecure connection.
- the client device in response to entering the proximity zone, displays, by the processor on the display, a list of devices configured for access by the client device, the list of devices including the A/V recording and communication device, wherein requesting access to the camera includes receiving, by the processor on the display, a selection of the A/V recording and communication device from the list of devices.
- a client device including a display, a communication module, and a processor, in response to entering a proximity zone of an audio/video (A/V) recording and communication device, receives, by the processor using the communication module, from the A/V recording and communication device, an access request for allowing the client device to access the camera of the A/V recording and communication device; in response to receiving the access request, transmits, by the processor using the communication module, to the A/V recording and communication device, an acceptance of the access request; in response to transmitting the acceptance, receives, by the processor using the communication module, from the camera, image data being recorded by the camera in a field of view of the camera; and displays, by the processor on the display, the image data.
- A/V audio/video
- the A/V recording and communication device is visible to a user of the client device when the client device is within the proximity zone.
- the proximity zone is defined by the A/V recording and communication device.
- the proximity zone includes the field of view of the camera of the A/V recording and communication device.
- a determination that the client device has entered the proximity zone includes comparing client device location data to proximity zone location data.
- the client device location data and the proximity zone location data include at least one of global positioning system (GPS) data and Wi-Fi positioning system (WPS) data.
- GPS global positioning system
- WPS Wi-Fi positioning system
- the client device prior to receiving the image data and after transmitting the acceptance, establishes, by the processor using the communication module, a connection to the A/V recording and communication device.
- establishing the connection includes connecting to a network of the A/V recording and communication device.
- the network is a Wi-Fi network.
- the network is an ad hoc network generated by the A/V recording and communication device.
- connection to the network is an unsecure connection.
- the client device in response to receiving the access request, displays, by the processor on the display, a list of devices configured for access by the client device, the list of devices including the A/V recording and communication device, wherein the acceptance of the access request includes receiving, by the processor on the display, a selection of the A/V recording and communication device from the list of devices.
- a client device including a display, a communication module, and a processor, in response to entering a proximity zone of an audio/video (A/V) recording and communication device having a camera, receives, by the processor using the communication module, an access request for allowing the client device access to the camera of the A/V recording and communication device; displays, by the processor on the display, a list of devices accessible by the client device, the list of devices including at least the A/V recording and communication device; in response to the displaying and based on the receiving the access request, receives, by the processor, an input including an acceptance of the access request; in response to receiving the input, transmits, by the processor using the communication module, to the A/V recording and communication device, the acceptance of the access request; in response to transmitting the acceptance of the access request, receives, by the processor using the communication module, from the camera of the A/V recording and communication device, image data being recorded in a field of view of the camera; and displays, by the processor on the display, the image data.
- A/V audio
- the A/V recording and communication device is visible to a user of the client device when the client device is within the proximity zone.
- the proximity zone is defined by the A/V recording and communication device.
- the proximity zone includes the field of view of the camera of the A/V recording and communication device.
- a determination that the client device has entered the proximity zone includes comparing client device location data to proximity zone location data.
- the client device location data and the proximity zone location data include at least one of global positioning system (GPS) data and Wi-Fi positioning system (WPS) data.
- GPS global positioning system
- WPS Wi-Fi positioning system
- the client device prior to receiving the image data and after transmitting the acceptance, the client device establishes a connection to the A/V recording and communication device.
- establishing the connection includes connecting to a network of the A/V recording and communication device.
- the network is a Wi-Fi network.
- the network is an ad hoc network generated by the A/V recording and communication device.
- connection to the network is an unsecure connection.
- an audio/video (A/V) recording and communication device including a processor, a communication module, and a camera, in response to detecting the presence of a client device in a proximity zone of the A/V recording and communication device, transmits, by the processor using the communication module, an access request to the client device for allowing the client device access to the camera; in response to the transmitting the access request, receives, by the processor using the communication module, an acceptance of the access request from the client device; and in response to receiving the acceptance, transmits, by the processor using the communication module, image data being recorded by the camera to the client device.
- A/V audio/video
- the A/V recording and communication device detects, by the processor using the communication module, the presence of the client device in the proximity zone of the A/V recording and communication device.
- detecting the presence of the client device includes scanning, by the processor using the communication module, the proximity zone for network connection signals.
- the network connection signals are at least one of Bluetooth signals and Wi-Fi signals.
- detecting the presence of the client device further includes, in response to scanning, identifying client device network connection signals being broadcast by the client device.
- the proximity zone is generated by the A/V recording and communication device.
- the proximity zone is defined by a user of a client device associated with the A/V recording and communication device.
- the A/V recording and communication device prior to transmitting the image data and after receiving the acceptance, establishes a connection to the client device.
- establishing the connection includes: transmitting, by the processor using the communication module, network access credentials of a network of the A/V recording and communication device to the client device; and in response to the transmitting, connecting, by the processor using the communication module, to the client device over the network.
- the network is a Wi-Fi network.
- the network is an ad hoc network generated by the A/V recording and communication device.
- transmitting the image data includes: analyzing, by the processor, the image data to determine whether a person is present; and in response to determining that a person is present, transmitting the image data to the client device.
- transmitting the image data includes: analyzing, by the processor, the image data to determine whether a person is present; in response to determining that a person is present, determining, by the processor, whether the person is a user of the client device; and in response to determining that the person is the user, transmitting, by the processor using the communication module, the image data to the client device.
- an audio/video (A/V) recording and communication device including a processor, a communication module, and a camera, in response to a client device entering a proximity zone of the A/V recording and communication device, receives, by the processor using the communication module, an access request from the client device for allowing the client device access to the camera; in response to the receiving the access request, accepts, by the processor, the access request; and in response to the accepting, transmits, by the processor using the communication module, to the client device, image data being recorded by the camera in a field of view of the camera.
- A/V audio/video
- accepting the access request includes: analyzing, by the processor, the image data to determine whether a person is present; and in response to determining that a person is present, accepting the access request.
- accepting the access request includes: analyzing, by the processor, the image data to determine whether a person is present; in response to determining that a person is present, determining, by the processor, whether the person is a user of the client device; and in response to determining that the person is the user, accepting the access request.
- the A/V recording and communication device prior to transmitting the image data and after accepting the access request, establishes a connection to the client device.
- establishing the connection includes: transmitting, by the processor using the communication module, network access credentials of a network of the A/V recording and communication device to the client device; and in response to the transmitting, connecting, by the processor using the communication module, to the client device over the network.
- the network is a Wi-Fi network.
- the network is an ad hoc network generated by the A/V recording and communication device.
- the proximity zone is generated by the A/V recording and communication device.
- the proximity zone is defined by a user of a client device associated with the A/V recording and communication device.
- an audio/video (A/V) recording and communication device including a processor, a communication module, and a camera, generates, by the processor, a proximity zone for detecting the presence of one or more client devices within the proximity zone; based on the generating, detects, by the processor, the presence of a first client device within the proximity zone of the A/V recording and communication device; in response to detecting the presence of the first client device, transmits, by the processor using the communication module, an access request to the client device for allowing the client device access to the camera; in response to the transmitting the access request, receives, by the processor using the communication module, an acceptance of the access request from the client device; and in response to receiving the acceptance, transmits, by the processor using the communication module, image data being recorded by the camera to the client device.
- A/V audio/video
- the proximity zone is defined by a user of a client device associated with the A/V recording and communication device.
- the A/V recording and communication device prior to transmitting the image data and after receiving the acceptance, establishes a connection to the client device.
- establishing the connection includes: transmitting, by the processor using the communication module, network access credentials of a network of the A/V recording and communication device to the client device; and in response to the transmitting, connecting, by the processor using the communication module, to the client device over the network.
- the network is a Wi-Fi network.
- the network is an ad hoc network generated by the A/V recording and communication device.
- transmitting the image data includes: analyzing, by the processor, the image data to determine whether a person is present; and in response to determining that a person is present, transmitting the image data to the client device.
- transmitting the image data includes: analyzing, by the processor, the image data to determine whether a person is present; in response to determining that a person is present, determining, by the processor, whether the person is a user of the client device; and in response to determining that the person is the user, transmitting, by the processor using the communication module, the image data to the client device.
- a method for use with a client device and an audio/video (A/V) recording and communication device having a camera comprises: in response to the client device entering a proximity zone of the A/V recording and communication device, receiving, from the client device, an access request to allow the client device access to the camera of the A/V recording and communication device; in response to receiving the access request, transmitting the access request to the A/V recording and communication device; in response to transmitting the access request, receiving, from the A/V recording and communication device, image data being recorded by the camera of the A/V recording and communication device in a field of view of the camera; and in response to receiving the image data, transmitting the image data to the client device.
- A/V audio/video
- the proximity zone is generated by the A/V recording and communication device.
- the proximity zone is defined by a user of a client device associated with the A/V recording and communication device.
- the method is performed by a backend device.
- the backend device is a server.
- a method for use with a client device and an audio/video (A/V) recording and communication device having a camera comprises: in response to the client device entering a proximity zone of the A/V recording and communication device, receiving, from the A/V recording and communication device, an access request to allow the client device access to the camera of the A/V recording and communication device; in response to receiving the access request, transmitting the access request to the client device; in response to transmitting the access request, receiving an acceptance of the access request from the client device; in response to the receiving the acceptance, retrieving, from the A/V recording and communication device, image data being recorded by the camera in a field of view of the camera; and in response to retrieving the image data, transmitting the image data to the client device.
- the proximity zone is generated by the A/V recording and communication device.
- the proximity zone is defined by a user of a client device associated with the A/V recording and communication device.
- the method is performed by a backend device.
- the backend device is a server.
- a method for use with a client device and an audio/video (A/V) recording and communication device having a camera comprises: receiving, from the A/V recording and communication device, first location information including a proximity zone; receiving, from the client device, second location data including a location of the client device; in response to receiving the second location data and based on the first location data, analyzing the second location data to determine whether the client device is within the proximity zone; based on the determination of whether the client device is within the proximity zone, transmitting, to the client device, an access request for allowing the client device to access the camera of the A/V recording and communication device; in response to transmitting the access request, receiving, from the client device, an acceptance of the access request; in response to receiving the acceptance, retrieving, from the A/V recording and communication device, image data being recorded by the camera in a field of view of the camera; and in response to retrieving the image data, transmitting the image data to the client device.
- the proximity zone is generated by the A/V recording and communication device.
- the proximity zone is defined by a user of a client device associated with the A/V recording and communication device.
- the method is performed by a backend device.
- the backend device is a server.
- FIG. 1 is a functional block diagram illustrating one embodiment of a system including an A/V recording and communication device according to various aspects of the present disclosure
- FIG. 2 is a flowchart illustrating one embodiment of a process for streaming and storing A/V content from an A/V recording and communication doorbell system according to various aspects of the present disclosure
- FIG. 3 is a functional block diagram illustrating an embodiment of an A/V recording and communication doorbell system according to the present disclosure
- FIG. 4 is a front perspective view of an embodiment of an A/V recording and communication doorbell according to the present disclosure
- FIG. 5 is a rear perspective view of the A/V recording and communication doorbell of FIG. 4 ;
- FIG. 6 is a partially exploded front perspective view of the A/V recording and communication doorbell of FIG. 4 showing the cover removed;
- FIGS. 7, 8, and 9 are front perspective views of various internal components of the A/V recording and communication doorbell of FIG. 4 ;
- FIG. 10 is a right-side cross-sectional view of the A/V recording and communication doorbell of FIG. 4 taken through the line 10 - 10 in FIG. 4 ;
- FIGS. 11-13 are rear perspective views of various internal components of the A/V recording and communication doorbell of FIG. 4 ;
- FIG. 14 is a front view of an A/V recording and communication device according to various aspects of the present disclosure.
- FIG. 15 is a rear view of the A/V recording and communication device of FIG. 14 ;
- FIG. 16 is right-side cross-sectional view of the A/V recording and communication device of FIG. 14 ;
- FIG. 17 is an exploded view of the A/V recording and communication device of FIG. 14 and a mounting bracket;
- FIG. 18 is a top view of a passive infrared sensor assembly according to various aspects of the present disclosure.
- FIG. 19 is a front view of the passive infrared sensor assembly of FIG. 18 ;
- FIG. 20 is a top view of the passive infrared sensor assembly of FIG. 18 , illustrating the fields of view of the passive infrared sensors according to various aspects of the present disclosure
- FIG. 21 is a functional block diagram of the components of the A/V recording and communication device of FIG. 14 ;
- FIG. 22 is a functional block diagram illustrating a system for communicating in a network according to various aspects of the present disclosure
- FIG. 23 is a functional block diagram illustrating one embodiment of an A/V recording and communication device according to various aspects of the present disclosure
- FIG. 24 is a functional block diagram illustrating one embodiment of a backend device according to various aspects of the present disclosure.
- FIG. 25 is a functional block diagram illustrating one embodiment of a client device according to various aspects of the present disclosure.
- FIGS. 26-39 are flowcharts illustrating processes for accessing cameras of A/V recording and communication devices based on location according to various aspects of the present disclosure
- FIGS. 40-41 are example environments illustrating aspects of a process for accessing cameras of A/V recording and communication devices according to various aspects of the present disclosure
- FIGS. 42-43 are screenshots of a graphical user interface (GUI) illustrating aspects of a process for accessing cameras of A/V recording and communication devices according to various aspects of the present disclosure
- FIG. 44 is a functional block diagram of a client device on which the present embodiments may be implemented according to various aspects of the present disclosure.
- FIG. 45 is a functional block diagram of a general-purpose computing system on which the present embodiments may be implemented according to various aspects of present disclosure.
- the present embodiments include an audio/video (A/V) recording and communication device 100 .
- the A/V recording and communication device 100 may in some embodiments comprise a doorbell, and may be located near the entrance to a structure (not shown), such as a dwelling, a business, a storage facility, etc.
- the A/V recording and communication device 100 includes a camera 102 , a microphone 104 , and a speaker 106 .
- the camera 102 may comprise, for example, a high definition (HD) video camera, such as one capable of capturing video images at an image display resolution of 720p, or 1080p, or better.
- HD high definition
- the A/V recording and communication device 100 may also include other hardware and/or components, such as a housing, one or more motion sensors (and/or other types of sensors), a button, etc.
- the A/V recording and communication device 100 may further include similar componentry and/or functionality as the wireless communication doorbells described in U.S. Patent Application Publication Nos. 2015/0022620 (application Ser. No. 14/499,828) and 2015/0022618 (application Ser. No. 14/334,922), both of which are incorporated herein by reference in their entireties as if fully set forth.
- the A/V recording and communication device 100 communicates with a user's network 110 , which may be for example a wired and/or wireless network. If the user's network 110 is wireless, or includes a wireless component, the network 110 may be a Wi-Fi network compatible with the IEEE 802.11 standard and/or other wireless communication standard(s).
- the user's network 110 is connected to another network 112 , which may comprise, for example, the Internet and/or a public switched telephone network (PSTN).
- PSTN public switched telephone network
- the A/V recording and communication device 100 may communicate with a user's client device 114 via the user's network 110 and the network 112 (Internet/PSTN).
- the user's client device 114 may comprise, for example, a mobile telephone (may also be referred to as a cellular telephone), such as a smartphone, a personal digital assistant (PDA), or another communication device.
- the user's client device 114 comprises a display (not shown) and related components capable of displaying streaming and/or recorded video images.
- the user's client device 114 may also comprise a speaker and related components capable of broadcasting streaming and/or recorded audio, and may also comprise a microphone.
- the A/V recording and communication device 100 may also communicate with one or more remote storage device(s) 116 (may be referred to interchangeably as “cloud storage device(s)”), one or more servers 118 , and/or a backend API (application programming interface) 120 via the user's network 110 and the network 112 (Internet/PSTN). While FIG. 1 illustrates the storage device 116 , the server 118 , and the backend API 120 as components separate from the network 112 , it is to be understood that the storage device 116 , the server 118 , and/or the backend API 120 may be considered to be components of the network 112 .
- the network 112 may be any wireless network or any wired network, or a combination thereof, configured to operatively couple the above-mentioned modules, devices, and systems as shown in FIG. 1 .
- the network 112 may include one or more of the following: a PSTN (public switched telephone network), the Internet, a local intranet, a PAN (Personal Area Network), a LAN (Local Area Network), a WAN (Wide Area Network), a MAN (Metropolitan Area Network), a virtual private network (VPN), a storage area network (SAN), a frame relay connection, an Advanced Intelligent Network (AIN) connection, a synchronous optical network (SONET) connection, a digital T1, T3, E1 or E3 line, a Digital Data Service (DDS) connection, a DSL (Digital Subscriber Line) connection, an Ethernet connection, an ISDN (Integrated Services Digital Network) line, a dial-up port such as a V.90, V.34, or V.34bis analog modem connection, a cable mode
- communications may also include links to any of a variety of wireless networks, including WAP (Wireless Application Protocol), GPRS (General Packet Radio Service), GSM (Global System for Mobile Communication), LTE, VoLTE, LoRaWAN, LPWAN, RPMA, LTE Cat-“X” (e.g.
- LTE Cat 1 LTE Cat 1, LTE Cat 0, LTE CatM1, LTE Cat NB1
- CDMA Code Division Multiple Access
- TDMA Time Division Multiple Access
- FDMA Frequency Division Multiple Access
- OFDMA Orthogonal Frequency Division Multiple Access
- GNSS global navigation satellite systems
- GPS global positioning system
- CDPD cellular digital packet data
- RIM Research in Motion, Limited
- Bluetooth radio or an IEEE 802.11-based radio frequency network.
- the network can further include or interface with any one or more of the following: RS-232 serial connection, IEEE-1394 (Firewire) connection, Fibre Channel connection, IrDA (infrared) port, SCSI (Small Computer Systems Interface) connection, USB (Universal Serial Bus) connection, or other wired or wireless, digital or analog, interface or connection, mesh or Digi® networking.
- IEEE-1394 Firewire
- Fibre Channel Fibre Channel
- IrDA infrared
- SCSI Small Computer Systems Interface
- USB Universal Serial Bus
- the A/V recording and communication device 100 detects the visitor's presence and begins capturing video images within a field of view of the camera 102 .
- the A/V recording and communication device 100 may also capture audio through the microphone 104 .
- the A/V recording and communication device 100 may detect the visitor's presence by detecting motion using the camera 102 and/or a motion sensor, and/or by detecting that the visitor has depressed the front button on the A/V recording and communication device 100 (in embodiments in which the A/V recording and communication device 100 comprises a doorbell).
- the A/V recording and communication device 100 sends an alert to the user's client device 114 ( FIG. 1 ) via the user's network 110 and the network 112 .
- the A/V recording and communication device 100 also sends streaming video, and may also send streaming audio, to the user's client device 114 . If the user answers the alert, two-way audio communication may then occur between the visitor and the user through the A/V recording and communication device 100 and the user's client device 114 .
- the user may view the visitor throughout the duration of the call, but the visitor cannot see the user (unless the A/V recording and communication device 100 includes a display, which it may in some embodiments).
- the video images captured by the camera 102 of the A/V recording and communication device 100 may be uploaded to the cloud and recorded on the remote storage device 116 ( FIG. 1 ).
- the video and/or audio may be recorded on the remote storage device 116 even if the user chooses to ignore the alert sent to his or her client device 114 .
- the system may further comprise a backend API 120 including one or more components.
- a backend API application programming interface
- a backend API may comprise, for example, a server (e.g. a real server, or a virtual machine, or a machine running in a cloud infrastructure as a service), or multiple servers networked together, exposing at least one API to client(s) accessing it.
- These servers may include components such as application servers (e.g. software servers), depending upon what other components are included, such as a caching layer, or database layers, or other components.
- a backend API may, for example, comprise many such applications, each of which communicate with one another using their public APIs. In some embodiments, the API backend may hold the bulk of the user data and offer the user management capabilities, leaving the clients to have very limited state.
- the backend API 120 illustrated FIG. 1 may include one or more APIs.
- An API is a set of routines, protocols, and tools for building software and applications.
- An API expresses a software component in terms of its operations, inputs, outputs, and underlying types, defining functionalities that are independent of their respective implementations, which allows definitions and implementations to vary without compromising the interface.
- an API may provide a programmer with access to an application's functionality without the programmer needing to modify the application itself, or even understand how the application works.
- An API may be for a web-based system, an operating system, or a database system, and it provides facilities to develop applications for that system using a given programming language.
- an API can ease the work of programming GUI components.
- an API can facilitate integration of new features into existing applications (a so-called “plug-in API”).
- An API can also assist otherwise distinct applications with sharing data, which can help to integrate and enhance the functionalities of the applications.
- the backend API 120 illustrated in FIG. 1 may further include one or more services (also referred to as network services).
- a network service is an application that provides data storage, manipulation, presentation, communication, and/or other capability.
- Network services are often implemented using a client-server architecture based on application-layer network protocols.
- Each service may be provided by a server component running on one or more computers (such as a dedicated server computer offering multiple services) and accessed via a network by client components running on other devices.
- client and server components can both be run on the same machine.
- Clients and servers may have a user interface, and sometimes other hardware associated with them.
- FIG. 2 is a flowchart illustrating a process for streaming and storing A/V content from an A/V recording and communication doorbell system according to various aspects of the present disclosure.
- the A/V recording and communication device 100 detects the visitor's presence and begins capturing video images within a field of view of the camera 102 .
- the A/V recording and communication device 100 may also capture audio through the microphone 104 .
- the A/V recording and communication device 100 may detect the visitor's presence by detecting motion using the camera 102 and/or a motion sensor, and/or by detecting that the visitor has depressed the front button on the A/V recording and communication device 100 (in embodiments in which the A/V recording and communication device 100 comprises a doorbell).
- a communication module of the A/V recording and communication device 100 sends a connection request, via the user's network 110 and the network 112 , to a device in the network 112 .
- the network device to which the request is sent may be a server such as the server 118 .
- the server 118 may comprise a computer program and/or a machine that waits for requests from other machines or software (clients) and responds to them.
- a server typically processes data.
- One purpose of a server is to share data and/or hardware and/or software resources among clients. This architecture is called the client-server model. The clients may run on the same computer or may connect to the server over a network. Examples of computing servers include database servers, file servers, mail servers, print servers, web servers, game servers, and application servers.
- the term server may be construed broadly to include any computerized process that shares a resource to one or more client processes.
- the network device may connect the A/V recording and communication device 100 to the user's client device 114 through the user's network 110 and the network 112 .
- the A/V recording and communication device 100 may record available audio and/or video data using the camera 102 , the microphone 104 , and/or any other sensor available.
- the audio and/or video data is transmitted (streamed) from the A/V recording and communication device 100 to the user's client device 114 via the user's network 110 and the network 112 .
- the user may receive a notification on his or her client device 114 with a prompt to either accept or deny the call.
- the process determines whether the user has accepted or denied the call. If the user denies the notification, then the process advances to block B 214 , where the audio and/or video data is recorded and stored at a cloud server. The session then ends at block B 216 and the connection between the A/V recording and communication device 100 and the user's client device 114 is terminated. If, however, the user accepts the notification, then at block B 218 the user communicates with the visitor through the user's client device 114 while audio and/or video data captured by the camera 102 , the microphone 104 , and/or other sensors is streamed to the user's client device 114 .
- the user may terminate the connection between the user's client device 114 and the A/V recording and communication device 100 and the session ends at block B 216 .
- the audio and/or video data may be recorded and stored at a cloud server (block B 214 ) even if the user accepts the notification and communicates with the visitor through the user's client device 114 .
- standard wired doorbell systems include a button outside the home next to the front door.
- the button activates a signaling device (such as a bell or a buzzer) inside the building. Pressing the doorbell button momentarily closes the doorbell circuit, which may be, for example, a single-pole, single-throw (SPST) push button switch.
- SPST single-pole, single-throw
- One terminal of the button is wired to a terminal on a transformer.
- the transformer steps down the 120-volt or 240-volt household AC electrical power to a lower voltage, typically 16 to 24 volts.
- Another terminal on the transformer is wired to a terminal on the signaling device.
- a common signaling device includes two flat metal bar resonators, which are struck by plungers operated by two solenoids.
- the flat bars are tuned to different notes.
- the first solenoid's plunger strikes one of the bars, and when the button is released, a spring on the plunger pushes the plunger up, causing it to strike the other bar, creating a two-tone sound (“ding-dong”).
- A/V recording and communication doorbell systems are incompatible with existing wired doorbell systems of the type described in the preceding paragraph.
- One reason for this incompatibility is that the A/V recording and communication doorbell draws an amount of power from the household AC electrical power supply that is above the threshold necessary for causing the signaling device to sound.
- the A/V recording and communication doorbell thus causes frequent inadvertent sounding of the signaling device, which is not only bothersome to the home's occupant(s), but also undermines the usefulness of the doorbell.
- the present embodiments solve this problem by limiting the power consumption of the A/V recording and communication doorbell to an amount that is below the threshold necessary for causing the signaling device to sound.
- Embodiments of the present A/V recording and communication doorbell can thus be connected to the existing household AC power supply and the existing signaling device without causing inadvertent sounding of the signaling device.
- the camera of the present A/V recording and communication doorbell can be powered on continuously.
- the camera In a typical battery-powered A/V recording and communication doorbell, the camera is powered on only part of the time so that the battery does not drain too rapidly.
- the present embodiments do not rely on a battery as a primary (or sole) power supply, and are thus able to keep the camera powered on continuously. Because the camera is able to be powered on continuously, it can always be recording, and recorded footage can be continuously stored in a rolling buffer or sliding window. In some embodiments, about 10-15 seconds of recorded footage can be continuously stored in the rolling buffer or sliding window.
- the camera is able to be powered on continuously, it can be used for motion detection, thus eliminating any need for a separate motion detection device, such as a passive infrared sensor (PIR). Eliminating the PIR simplifies the design of the A/V recording and communication doorbell and enables the doorbell to be made more compact. Also, because the camera is able to be powered on continuously, it can be used as a light detector for use in controlling the current state of the IR cut filter and turning the IR LED on and off. Using the camera as a light detector eliminates any need for a separate light detector, thereby further simplifying the design of the A/V recording and communication doorbell and enabling the doorbell to be made even more compact.
- a separate motion detection device such as a passive infrared sensor
- FIGS. 3-13 illustrate one embodiment of a low-power-consumption A/V recording and communication doorbell 130 according to various aspects of the present disclosure.
- FIG. 3 is a functional block diagram illustrating various components of the A/V recording and communication doorbell 130 and their relationships to one another.
- the A/V recording and communication doorbell 130 includes a pair of terminals 131 , 132 configured to be connected to a source of external AC (alternating-current) power, such as a household AC power supply 134 (may also be referred to as AC mains).
- the AC power 134 may have a voltage in the range of 16-24 VAC, for example.
- the incoming AC power 134 may be converted to DC (direct-current) by an AC/DC rectifier 136 .
- An output of the AC/DC rectifier 136 may be connected to an input of a DC/DC converter 138 , which may step down the voltage from the output of the AC/DC rectifier 136 from 16-24 VDC to a lower voltage of about 5 VDC, for example.
- the output of the DC/DC converter 138 may be in a range of from about 2.5 V to about 7.5 V, for example.
- the output of the DC/DC converter 138 is connected to a power manager 140 , which may comprise an integrated circuit including a processor core, memory, and/or programmable input/output peripherals.
- the power manager 140 may be an off-the-shelf component, such as the BQ24773 chip manufactured by Texas Instruments.
- the power manager 140 controls, among other things, an amount of power drawn from the external power supply 134 , as well as an amount of supplemental power drawn from a battery 142 , to power the A/V recording and communication doorbell 130 .
- the power manager 140 may, for example, limit the amount of power drawn from the external power supply 134 so that a threshold power draw is not exceeded.
- the threshold power as measured at the output of the DC/DC converter 138 , may be equal to 1.4 A.
- the power manager 140 may also control an amount of power drawn from the external power supply 134 and directed to the battery 142 for recharging of the battery 142 .
- An output of the power manager 140 is connected to a power sequencer 144 , which controls a sequence of power delivery to other components of the A/V recording and communication doorbell 130 , including a communication module 146 , a front button 148 , a microphone 150 , a speaker driver 151 , a speaker 152 , an audio CODEC (Coder-DECoder) 153 , a camera 154 , an infrared (IR) light source 156 , an IR cut filter 158 , a processor 160 (may also be referred to as a controller 160 ), a plurality of light indicators 162 , and a controller 164 for the light indicators 162 .
- a communication module 146 includes a communication module 146 , a front button 148 , a microphone 150 , a speaker driver 151 , a speaker 152 , an audio CODEC (Coder-DECoder) 153 , a camera 154 , an infrared (IR) light source 156
- the power sequencer 144 may comprise an integrated circuit including a processor core, memory, and/or programmable input/output peripherals.
- the power sequencer 144 may be an off-the-shelf component, such as the RT5024 chip manufactured by Richtek.
- the A/V recording and communication doorbell 130 further comprises an electronic switch 166 that closes when the front button 148 is depressed. When the electronic switch 166 closes, power from the AC power source 134 is diverted through a signaling device 168 that is external to the A/V recording and communication doorbell 130 to cause the signaling device 168 to emit a sound, as further described below.
- the electronic switch 166 may be a triac device.
- the A/V recording and communication doorbell 130 further comprises a reset button 170 configured to initiate a hard reset of the processor 160 , as further described below.
- the processor 160 may perform data processing and various other functions, as described below.
- the processor 160 may comprise an integrated circuit including a processor core, memory 172 , non-volatile memory 174 , and/or programmable input/output peripherals (not shown).
- the memory 172 may comprise, for example, DDR3 (double data rate type three synchronous dynamic random-access memory).
- the non-volatile memory 174 may comprise, for example, NAND flash memory. In the embodiment illustrated in FIG. 3 , the memory 172 and the non-volatile memory 174 are illustrated within the box representing the processor 160 . It is to be understood that the embodiment illustrated in FIG.
- the memory 172 and/or the non-volatile memory 174 are not necessarily physically incorporated with the processor 160 .
- the memory 172 and/or the non-volatile memory 174 may be shared by one or more other components (in addition to the processor 160 ) of the present A/V recording and communication doorbell 130 .
- the transfer of digital audio between the user and a visitor may be compressed and decompressed using the audio CODEC 153 , which is operatively coupled to the processor 160 .
- the visitor speaks audio from the visitor is compressed by the audio CODEC 153
- digital audio data is sent through the communication module 146 to the network 112 via the user's network 110 , routed by the server 118 and delivered to the user's client device 114 .
- the user speaks after being transferred through the network 112 , the user's network 110 , and the communication module 146 , the digital audio data is decompressed by the audio CODEC 153 and emitted to the visitor through the speaker 152 , which is driven by the speaker driver 151 .
- some of the present embodiments may include a shunt 176 connected in parallel with the signaling device 168 .
- the shunt 176 facilitates the ability of the A/V recording and communication doorbell 130 to draw power from the AC power source 134 without inadvertently triggering the signaling device 168 .
- the shunt 176 during normal standby operation, presents a relatively low electrical impedance, such as a few ohms, across the terminals of the signaling device 168 . Most of the current drawn by the A/V recording and communication doorbell 130 , therefore, flows through the shunt 176 , and not through the signaling device 168 .
- the shunt 176 contains electronic circuitry (described below) that switches the shunt 176 between a state of low impedance, such as a few ohms, for example, and a state of high impedance, such as >1K ohms, for example.
- a state of low impedance such as a few ohms, for example
- a state of high impedance such as >1K ohms, for example.
- the circuitry in the shunt 176 senses this voltage, and switches the shunt 176 to the high impedance state, so that power from the AC power source 134 is diverted through the signaling device 168 .
- the diverted AC power 134 is above the threshold necessary to cause the signaling device 168 to emit a sound. Pressing the front button 148 of the doorbell 130 therefore causes the signaling device 168 to “ring,” alerting any person(s) within the structure to which the doorbell 130 is mounted that there is a visitor at the front door (or at another location corresponding to the location of the doorbell 130 ).
- the electronic switch 166 may be a triac device.
- the A/V recording and communication doorbell 130 further comprises a housing 178 having an enclosure 180 ( FIG. 6 ), a back plate 182 secured to the rear of the enclosure 180 , and a shell 184 overlying the enclosure 180 .
- the shell 184 includes a recess 186 that is sized and shaped to receive the enclosure 180 in a close-fitting engagement, such that outer surfaces of the enclosure 180 abut conforming inner surfaces of the shell 184 .
- Exterior dimensions of the enclosure 180 may be closely matched with interior dimensions of the shell 184 such that friction maintains the shell 184 about the enclosure 180 .
- the enclosure 180 and/or the shell 184 may include mating features 188 , such as one or more tabs, grooves, slots, posts, etc. to assist in maintaining the shell 184 about the enclosure 180 .
- the back plate 182 is sized and shaped such that the edges of the back plate 182 extend outward from the edges of the enclosure 180 , thereby creating a lip 190 against which the shell 184 abuts when the shell 184 is mated with the enclosure 180 , as shown in FIGS. 4 and 5 .
- multiple shells 184 in different colors may be provided so that the end user may customize the appearance of his or her A/V recording and communication doorbell 130 .
- the A/V recording and communication doorbell 130 may be packaged and sold with multiple shells 184 in different colors in the same package.
- a front surface of the A/V recording and communication doorbell 130 includes the button 148 (may also be referred to as front button 148 , FIG. 3 ), which is operatively connected to the processor 160 .
- the button 148 may also be referred to as front button 148 , FIG. 3
- an alert may be sent to the user's client device to notify the user that someone is at his or her front door (or at another location corresponding to the location of the A/V recording and communication doorbell 130 ).
- the A/V recording and communication doorbell 130 further includes the camera 154 , which is operatively connected to the processor 160 , and which is located behind a shield 192 .
- the camera 154 is configured to capture video images from within its field of view. Those video images can be streamed to the user's client device and/or uploaded to a remote network device for later viewing according to a process similar to that described above with reference to FIG. 2 .
- a pair of terminal screws 194 extends through the back plate 182 .
- the terminal screws 194 are connected at their inner ends to the terminals 131 , 132 ( FIG. 3 ) within the A/V recording and communication doorbell 130 .
- the terminal screws 194 are configured to receive electrical wires to connect to the A/V recording and communication doorbell 130 , through the terminals 131 , 132 , to the household AC power supply 134 of the structure on which the A/V recording and communication doorbell 130 is mounted.
- the terminal screws 194 are located within a recessed portion 196 of the rear surface 198 of the back plate 182 so that the terminal screws 194 do not protrude from the outer envelope of the A/V recording and communication doorbell 130 .
- the A/V recording and communication doorbell 130 can thus be mounted to a mounting surface with the rear surface 198 of the back plate 182 abutting the mounting surface.
- the back plate 182 includes apertures 200 adjacent its upper and lower edges to accommodate mounting hardware, such as screws (not shown), for securing the back plate 182 (and thus the A/V recording and communication doorbell 130 ) to the mounting surface.
- the enclosure 180 includes corresponding apertures 202 adjacent its upper and lower edges that align with the apertures 200 in the back plate 182 to accommodate the mounting hardware.
- the A/V recording and communication doorbell 130 may include a mounting plate or bracket (not shown) to facilitate securing the A/V recording and communication doorbell 130 to the mounting surface.
- the shell 184 includes a central opening 204 in a front surface.
- the central opening 204 is sized and shaped to accommodate the shield 192 .
- the shield 192 is substantially rectangular, and includes a central opening 206 through which the front button 148 protrudes.
- the shield 192 defines a plane parallel to and in front of a front surface 208 of the enclosure 180 .
- the shield 192 resides within the central opening 204 of the shell 184 such that a front surface 210 of the shield 192 is substantially flush with a front surface 212 of the shell 184 and there is little or no gap ( FIG. 4 ) between the outer edges of the shield 192 and the inner edges of the central opening 204 in the shell 184 .
- the shield 192 includes an upper portion 214 (located above and to the sides of the front button 148 ) and a lower portion 216 (located below and to the sides of the front button 148 ).
- the upper and lower portions 214 , 216 of the shield 192 may be separate pieces, and may comprise different materials.
- the upper portion 214 of the shield 192 may be transparent or translucent so that it does not interfere with the field of view of the camera 154 .
- the upper portion 214 of the shield 192 may comprise glass or plastic.
- the microphone 150 which is operatively connected to the processor 160 , is located behind the upper portion 214 of the shield 192 .
- the upper portion 214 therefore, may include an opening 218 that facilitates the passage of sound through the shield 192 so that the microphone 150 is better able to pick up sounds from the area around the A/V recording and communication doorbell 130 .
- the lower portion 216 of the shield 192 may comprise a material that is substantially transparent to infrared (IR) light, but partially or mostly opaque with respect to light in the visible spectrum.
- the lower portion 216 of the shield 192 may comprise a plastic, such as polycarbonate.
- the lower portion 216 of the shield 192 therefore, does not interfere with transmission of IR light from the IR light source 156 , which is located behind the lower portion 216 .
- the IR light source 156 and the IR cut filter 158 which are both operatively connected to the processor 160 , facilitate “night vision” functionality of the camera 154 .
- the upper portion 214 and/or the lower portion 216 of the shield 192 may abut an underlying cover 220 ( FIG. 10 ), which may be integral with the enclosure 180 or may be a separate piece.
- the cover 220 which may be opaque, may include a first opening 222 corresponding to the location of the camera 154 , a second opening (not shown) corresponding to the location of the microphone 150 and the opening 218 in the upper portion 214 of the shield 192 , and a third opening (not shown) corresponding to the location of the IR light source 156 .
- FIGS. 7-10 illustrate various internal components of the A/V recording and communication doorbell 130 .
- FIGS. 7-9 are front perspective views of the doorbell 130 with the shell 184 and the enclosure 180 removed, while FIG. 10 is a right-side cross-sectional view of the doorbell 130 taken through the line 10 - 10 in FIG. 4 .
- the A/V recording and communication doorbell 130 further comprises a main printed circuit board (PCB) 224 and a front PCB 226 .
- the front PCB 226 comprises a button actuator 228 .
- the front button 148 is located in front of the button actuator 228 .
- the front button 148 includes a stem 230 ( FIG. 10 ) that extends into the housing 178 to contact the button actuator 228 . When the front button 148 is pressed, the stem 230 depresses the button actuator 228 , thereby closing the electronic switch 166 ( FIG. 8 ), as described below.
- the front PCB 226 further comprises the light indicators 162 , which may illuminate when the front button 148 of the doorbell 130 is pressed.
- the light indicators 162 comprise light-emitting diodes (LEDs 162 ) that are surface mounted to the front surface of the front PCB 226 and are arranged in a circle around the button actuator 228 .
- LEDs 162 light-emitting diodes
- the present embodiments are not limited to the light indicators 162 being LEDs, and in alternative embodiments the light indicators 162 may comprise any other type of light-emitting device.
- the present embodiments are also not limited by the number of light indicators 162 shown in FIG. 8 , nor by the pattern in which they are arranged.
- the doorbell 130 further comprises a light pipe 232 .
- the light pipe 232 is a transparent or translucent ring that encircles the front button 148 .
- the light pipe 232 resides in an annular space between the front button 148 and the central opening 206 in the shield 192 , with a front surface 234 of the light pipe 232 being substantially flush with the front surface 210 of the shield 192 .
- a rear portion of light pipe 232 includes a plurality of posts 236 whose positions correspond to the positions of the LEDs 162 .
- the LEDs 162 When the LEDs 162 are illuminated, light is transmitted through the posts 236 and the body of the light pipe 232 so that the light is visible at the front surface 234 of the light pipe 232 .
- the LEDs 162 and the light pipe 232 thus provide a ring of illumination around the front button 148 .
- the light pipe 232 may comprise a plastic, for example, or any other suitable material capable of transmitting light.
- the LEDs 162 and the light pipe 232 may function as visual indicators for a visitor and/or a user.
- the LEDs 162 may illuminate upon activation or stay illuminated continuously.
- the LEDs 162 may change color to indicate that the front button 148 has been pressed.
- the LEDs 162 may also indicate that the battery 142 needs recharging, or that the battery 142 is currently being charged, or that charging of the battery 142 has been completed.
- the LEDs 162 may indicate that a connection to the user's wireless network is good, limited, poor, or not connected.
- the LEDs 162 may be used to guide the user through setup or installation steps using visual cues, potentially coupled with audio cues emitted from the speaker 152 .
- the A/V recording and communication doorbell 130 further comprises a rechargeable battery 142 .
- the A/V recording and communication doorbell 130 is connected to an external power source 134 ( FIG. 3 ), such as AC mains.
- the A/V recording and communication doorbell 130 is primarily powered by the external power source 134 , but may also draw power from the rechargeable battery 142 so as not to exceed a threshold amount of power from the external power source 134 , to thereby avoid inadvertently sounding the signaling device 168 .
- the battery 142 is operatively connected to the power manager 140 .
- the power manager 140 controls an amount of power drawn from the battery 142 to supplement the power drawn from the external AC power source 134 to power the A/V recording and communication doorbell 130 when supplemental power is needed.
- the power manager 140 also controls recharging of the battery 142 using power drawn from the external power source 134 .
- the battery 142 may comprise, for example, a lithium-ion battery, or any other type of rechargeable battery.
- the A/V recording and communication doorbell 130 further comprises the camera 154 .
- the camera 154 is coupled to a front surface of the front PCB 226 , and includes a lens 238 and an imaging processor 240 ( FIG. 9 ).
- the camera lens 238 may be a lens capable of focusing light into the camera 154 so that clear images may be captured.
- the camera 154 may comprise, for example, a high definition (HD) video camera, such as one capable of capturing video images at an image display resolution of 720p or better. In certain of the present embodiments, the camera 154 may be used to detect motion within its field of view, as described below.
- HD high definition
- the A/V recording and communication doorbell 130 further comprises an infrared (IR) light source 242 .
- the IR light source 242 comprises an IR light-emitting diode (LED) 242 coupled to an IR LED printed circuit board (PCB) 244 .
- the IR LED 242 may not comprise a separate PCB 244 , and may, for example, be coupled to the front PCB 226 .
- the IR LED PCB 244 is located below the front button 148 ( FIG. 7 ) and behind the lower portion 216 of the shield 192 ( FIG. 10 ). As described above, the lower portion 216 of the shield 192 is transparent to IR light, but may be opaque with respect to light in the visible spectrum.
- the IR LED 242 may be triggered to activate when a low level of ambient light is detected. When activated, IR light emitted from the IR LED 242 illuminates the camera 154 's field of view. The camera 154 , which may be configured to detect IR light, may then capture the IR light emitted by the IR LED 242 as it reflects off objects within the camera 154 's field of view, so that the A/V recording and communication doorbell 130 can clearly capture images at night (may be referred to as “night vision”).
- the A/V recording and communication doorbell 130 further comprises an IR cut filter 158 .
- the IR cut filter 158 is a mechanical shutter that can be selectively positioned between the lens 238 and the image sensor of the camera 154 .
- the IR cut filter 158 is positioned between the lens 238 and the image sensor to filter out IR light so that it does not distort the colors of images as the human eye sees them.
- the IR cut filter 158 is withdrawn from the space between the lens 238 and the image sensor, so that the camera 154 is sensitive to IR light (“night vision”).
- the camera 154 acts as a light detector for use in controlling the current state of the IR cut filter 158 and turning the IR LED 242 on and off.
- Using the camera 154 as a light detector is facilitated in some embodiments by the fact that the A/V recording and communication doorbell 130 is powered by a connection to AC mains, and the camera 154 , therefore, is always powered on.
- the A/V recording and communication doorbell 130 may include a light sensor separate from the camera 154 for use in controlling the IR cut filter 158 and the IR LED 242 .
- the A/V recording and communication doorbell 130 further comprises a reset button 170 .
- the reset button 170 contacts a reset button actuator 246 ( FIG. 8 ) coupled to the front PCB 226 .
- the reset button 170 When the reset button 170 is pressed, it may contact the reset button actuator 246 , which may trigger the erasing of any data stored at the non-volatile memory 174 and/or at the memory 172 ( FIG. 3 ), and/or may trigger a reboot of the processor 160 .
- FIGS. 11-13 further illustrate internal components of the A/V recording and communication doorbell 130 .
- FIGS. 11-13 are rear perspective views of the doorbell 130 with the back plate 182 and additional components removed.
- the back plate 182 is removed, while in FIG. 12 the back plate 182 and the main PCB 224 are removed, and in FIG. 13 the back plate 182 , the main PCB 224 , and the front PCB 226 are removed.
- FIG. 11 several components are coupled to the rear surface of the main PCB 224 , including the communication module 146 , the processor 160 , memory 172 , and non-volatile memory 174 . The functions of each of these components are described below. With reference to FIG.
- FIG. 12 several components are coupled to the rear surface of the front PCB 226 , including the power manager 140 , the power sequencer 144 , the AC/DC rectifier 136 , the DC/DC converter 138 , and the controller 164 for the light indicators 162 .
- the functions of each of these components are also described below.
- FIG. 13 several components are visible within the enclosure 180 , including the microphone 150 , a speaker chamber 248 (in which the speaker 152 is located), and an antenna 250 for the communication module 146 . The functions of each of these components are also described below.
- the antenna 250 is coupled to the front surface of the main PCB 224 and operatively connected to the communication module 146 , which is coupled to the rear surface of the main PCB 224 ( FIG. 11 ).
- the microphone 150 which may also be coupled to the front surface of the main PCB 224 , is located near the opening 218 ( FIG. 4 ) in the upper portion 214 of the shield 192 so that sounds emanating from the area around the A/V recording and communication doorbell 130 can pass through the opening 218 and be detected by the microphone 150 .
- the speaker chamber 248 is located near the bottom of the enclosure 180 .
- the speaker chamber 248 comprises a hollow enclosure in which the speaker 152 is located.
- the hollow speaker chamber 248 amplifies the sounds made by the speaker 152 so that they can be better heard by a visitor in the area near the A/V recording and communication doorbell 130 .
- the lower surface 252 of the shell 184 and the lower surface (not shown) of the enclosure 180 may include an acoustical opening 254 through which the sounds made by the speaker 152 can pass so that they can be better heard by a visitor in the area near the A/V recording and communication doorbell 130 .
- the acoustical opening 254 is shaped generally as a rectangle having a length extending substantially across the lower surface 252 of the shell 184 (and also the enclosure 180 ). The illustrated shape is, however, just one example.
- the lower surface 252 of the shell 184 may further include an opening 256 for receiving a security screw (not shown).
- the security screw may extend through the opening 256 and into a similarly located opening in the enclosure 180 to secure the shell 184 to the enclosure 180 . If the doorbell 130 is mounted to a mounting bracket (not shown), the security screw may also maintain the doorbell 130 on the mounting bracket.
- the A/V recording and communication doorbell 130 may further include a battery heater 258 .
- the present A/V recording and communication doorbell 130 is configured for outdoor use, including in cold climates. Cold temperatures, however, can cause negative performance issues for rechargeable batteries, such as reduced energy capacity, increased internal resistance, reduced ability to charge without damage, and reduced ability to supply load current.
- the battery heater 258 helps to keep the rechargeable battery 142 warm in order to reduce or eliminate the foregoing negative performance issues.
- the battery heater 258 comprises a substantially flat, thin sheet abutting a side surface of the rechargeable battery 142 .
- the battery heater 258 may comprise, for example, an electrically resistive heating element that produces heat when electrical current is passed through it.
- the battery heater 258 may thus be operatively coupled to the power manager 140 and/or the power sequencer 144 ( FIG. 12 ).
- the rechargeable battery 142 may include a thermally sensitive resistor (“thermistor,” not shown) operatively connected to the processor 160 so that the battery 142 's temperature can be monitored and the amount of power supplied to the battery heater 258 can be adaptively controlled to keep the rechargeable battery 142 within a desired temperature range.
- thermally sensitive resistor (“thermistor,” not shown) operatively connected to the processor 160 so that the battery 142 's temperature can be monitored and the amount of power supplied to the battery heater 258 can be adaptively controlled to keep the rechargeable battery 142 within a desired temperature range.
- the present embodiments advantageously limit the power consumption of the A/V recording and communication doorbell to an amount that is below the threshold necessary for causing the signaling device to sound (except when the front button of the doorbell is pressed).
- the present A/V recording and communication doorbell can thus be connected to the existing household AC power supply and the existing signaling device without causing inadvertent sounding of the signaling device.
- the camera of the present A/V recording and communication doorbell can be powered on continuously.
- the camera In a typical battery-powered A/V recording and communication doorbell, the camera is powered on only part of the time so that the battery does not drain too rapidly.
- the present embodiments do not rely on a battery as a primary (or sole) power supply, and are thus able to keep the camera powered on continuously. Because the camera is able to be powered on continuously, it can always be recording, and recorded footage can be continuously stored in a rolling buffer or sliding window. In some embodiments, about 10-15 seconds of recorded footage can be continuously stored in the rolling buffer or sliding window.
- the camera is able to be powered on continuously, it can be used for motion detection, thus eliminating any need for a separate motion detection device, such as a passive infrared sensor (PIR). Eliminating the PIR simplifies the design of the A/V recording and communication doorbell and enables the doorbell to be made more compact, although in some alternative embodiments the doorbell may include one or more PIRs and/or other motion detectors, heat source detectors, etc. Also, because the camera is able to be powered on continuously, it can be used as a light detector for use in controlling the current state of the IR cut filter and turning the IR LED on and off.
- PIR passive infrared sensor
- the doorbell may include a separate light detector.
- FIGS. 14-18 illustrate another embodiment of a wireless audio/video (A/V) communication doorbell 330 according to an aspect of present embodiments.
- FIG. 14 is a front view
- FIG. 15 is a rear view
- FIG. 16 is a right-side cross-sectional view
- FIG. 17 is an exploded view of the doorbell 330 and a mounting bracket 337 .
- the doorbell 330 is configured to be connected to an external power source, such as household wiring, but is also configured to be powered by an on-board rechargeable battery instead of, or in addition to, the external power source.
- the doorbell 330 includes a faceplate 335 mounted to a back plate 339 ( FIG. 15 ). With reference to FIG. 16 , the faceplate 335 has a substantially flat profile.
- the faceplate 335 may comprise any suitable material, including, without limitation, metals, such as brushed aluminum or stainless steel, metal alloys, or plastics.
- the faceplate 335 protects the internal contents of the doorbell 330 and serves as an exterior front surface of the doorbell 330 .
- the faceplate 335 includes a button 333 and a light pipe 336 .
- the button 333 and the light pipe 336 may have various profiles that may or may not match the profile of the faceplate 335 .
- the light pipe 336 may comprise any suitable material, including, without limitation, transparent plastic, that is capable of allowing light produced within the doorbell 330 to pass through.
- the light may be produced by one or more light-emitting components, such as light-emitting diodes (LED's), contained within the doorbell 330 , as further described below.
- the button 333 may make contact with a button actuator (not shown) located within the doorbell 330 when the button 333 is pressed by a visitor. When pressed, the button 333 may trigger one or more functions of the doorbell 330 , as further described below.
- the doorbell 330 further includes an enclosure 331 that engages the faceplate 335 .
- the enclosure 331 abuts an upper edge 335 T ( FIG. 14 ) of the faceplate 335 , but in alternative embodiments one or more gaps between the enclosure 331 and the faceplate 335 may facilitate the passage of sound and/or light through the doorbell 330 .
- the enclosure 331 may comprise any suitable material, but in some embodiments the material of the enclosure 331 preferably permits infrared light to pass through from inside the doorbell 330 to the environment and vice versa.
- the doorbell 330 further includes a lens 332 .
- the lens may comprise a Fresnel lens, which may be patterned to deflect incoming light into one or more infrared sensors located within the doorbell 330 .
- the doorbell 330 further includes a camera 334 , which captures video data when activated, as described below.
- FIG. 15 is a rear view of the doorbell 330 , according to an aspect of the present embodiments.
- the enclosure 331 may extend from the front of the doorbell 330 around to the back thereof and may fit snugly around a lip of the back plate 339 .
- the back plate 339 may comprise any suitable material, including, without limitation, metals, such as brushed aluminum or stainless steel, metal alloys, or plastics.
- the back plate 339 protects the internal contents of the doorbell 330 and serves as an exterior rear surface of the doorbell 330 .
- the faceplate 335 may extend from the front of the doorbell 330 and at least partially wrap around the back plate 339 , thereby allowing a coupled connection between the faceplate 335 and the back plate 339 .
- the back plate 339 may have indentations in its structure to facilitate the coupling.
- spring contacts 340 may provide power to the doorbell 330 when mated with other conductive contacts connected to a power source.
- the spring contacts 340 may comprise any suitable conductive material, including, without limitation, copper, and may be capable of deflecting when contacted by an inward force, for example the insertion of a mating element.
- the doorbell 330 further comprises a connector 360 , such as a micro-USB or other connector, whereby power and/or data may be supplied to and from the components within the doorbell 330 .
- a reset button 359 may be located on the back plate 339 , and may make contact with a button actuator (not shown) located within the doorbell 330 when the reset button 359 is pressed. When the reset button 359 is pressed, it may trigger one or more functions, as described below.
- FIG. 16 is a right side cross-sectional view of the doorbell 330 without the mounting bracket 337 .
- the lens 332 is substantially coplanar with the front surface 331 F of the enclosure 331 .
- the lens 332 may be recessed within the enclosure 331 or may protrude outward from the enclosure 331 .
- the camera 334 is coupled to a camera printed circuit board (PCB) 347 , and a lens 334 a of the camera 334 protrudes through an opening in the enclosure 331 .
- the camera lens 334 a may be a lens capable of focusing light into the camera 334 so that clear images may be taken.
- the camera PCB 347 may be secured within the doorbell with any suitable fasteners, such as screws, or interference connections, adhesives, etc.
- the camera PCB 347 comprises various components that enable the functionality of the camera 334 of the doorbell 330 , as described below.
- Infrared light-emitting components such as infrared LED's 368 , are coupled to the camera PCB 347 and may be triggered to activate when a light sensor detects a low level of ambient light. When activated, the infrared LED's 368 may emit infrared light through the enclosure 331 and/or the camera 334 out into the ambient environment.
- the camera 334 which may be configured to detect infrared light, may then capture the light emitted by the infrared LED's 368 as it reflects off objects within the camera's 334 field of view, so that the doorbell 330 can clearly capture images at night (may be referred to as “night vision”).
- the doorbell 330 further comprises a front PCB 346 , which in the illustrated embodiment resides in a lower portion of the doorbell 330 adjacent a battery 366 .
- the front PCB 346 may be secured within the doorbell 330 with any suitable fasteners, such as screws, or interference connections, adhesives, etc.
- the front PCB 346 comprises various components that enable the functionality of the audio and light components, as further described below.
- the battery 366 may provide power to the doorbell 330 components while receiving power from the spring contacts 340 , thereby engaging in a trickle-charge method of power consumption and supply.
- the doorbell 330 may draw power directly from the spring contacts 340 while relying on the battery 366 only when the spring contacts 340 are not providing the power necessary for all functions.
- the battery 366 may comprise the sole source of power for the doorbell 330 .
- the spring contacts 340 may not be connected to a source of power. When the battery 366 is depleted of its charge, it may be recharged, such as by connecting a power source to the connector 360 .
- the doorbell 330 further comprises a power PCB 348 , which in the illustrated embodiment resides behind the camera PCB 347 .
- the power PCB 348 may be secured within the doorbell 330 with any suitable fasteners, such as screws, or interference connections, adhesives, etc.
- the power PCB 348 comprises various components that enable the functionality of the power and device-control components, as further described below.
- the doorbell 330 further comprises a communication module 364 coupled to the power PCB 348 .
- the communication module 364 facilitates communication with client devices in one or more remote locations, as further described below.
- the connector 360 may protrude outward from the power PCB 348 and extend through a hole in the back plate 339 .
- the doorbell 330 further comprises passive infrared (PIR) sensors 344 , which are secured on or within a PIR sensor holder 343 , and the assembly resides behind the lens 332 .
- the doorbell 330 may comprise three PIR sensors 344 , as further described below, but in other embodiments any number of PIR sensors 344 may be provided.
- one or more of the PIR sensors 344 may comprise a pyroelectric infrared sensor.
- the PIR sensor holder 343 may be secured to the doorbell 330 with any suitable fasteners, such as screws, or interference connections, adhesives, etc.
- the PIR sensors 344 may be any type of sensor capable of detecting and communicating the presence of a heat source within their field of view.
- alternative embodiments may comprise one or more motion sensors either in place of or in addition to the PIR sensors 344 .
- the motion sensors may be configured to detect motion using any methodology, such as a methodology that does not rely on detecting the presence of a heat source within a field of view.
- FIG. 17 is an exploded view of the doorbell 330 and the mounting bracket 337 according to an aspect of the present embodiments.
- the mounting bracket 337 is configured to be mounted to a mounting surface (not shown) of a structure, such as a home or an office.
- FIG. 17 shows the front side 337 F of the mounting bracket 337 .
- the mounting bracket 337 is configured to be mounted to the mounting surface such that the back side 337 B thereof faces the mounting surface.
- the mounting bracket 337 may be mounted to surfaces of various composition, including, without limitation, wood, concrete, stucco, brick, vinyl siding, aluminum siding, etc., with any suitable fasteners, such as screws, or interference connections, adhesives, etc.
- the doorbell 330 may be coupled to the mounting bracket 337 with any suitable fasteners, such as screws, or interference connections, adhesives, etc.
- the illustrated embodiment of the mounting bracket 337 includes the terminal screws 338 .
- the terminal screws 338 are configured to receive electrical wires adjacent the mounting surface of the structure upon which the mounting bracket 337 is mounted, so that the doorbell 330 may receive electrical power from the structure's electrical system.
- the terminal screws 338 are electrically connected to electrical contacts 377 of the mounting bracket. If power is supplied to the terminal screws 338 , then the electrical contacts 377 also receive power through the terminal screws 338 .
- the electrical contacts 377 may comprise any suitable conductive material, including, without limitation, copper, and may protrude slightly from the face of the mounting bracket 337 so that they may mate with the spring contacts 340 located on the back plate 339 .
- the mounting bracket 337 further comprises a bracket PCB 349 .
- the bracket PCB 349 is situated outside the doorbell 330 , and is therefore configured for various sensors that measure ambient conditions, such as an accelerometer 350 , a barometer 351 , a humidity sensor 352 , and a temperature sensor 353 ( FIG. 18 ). The functions of these components are discussed in more detail below.
- the bracket PCB 349 may be secured to the mounting bracket 337 with any suitable fasteners, such as screws, or interference connections, adhesives, etc.
- the faceplate 335 may extend from the bottom of the doorbell 330 up to just below the camera 334 , and connect to the back plate 339 as described above.
- the lens 332 may extend and curl partially around the side of the doorbell 330 .
- the enclosure 331 may extend and curl around the side and top of the doorbell 330 , and may be coupled to the back plate 339 as described above.
- the camera 334 may protrude slightly through the enclosure 331 , thereby giving it a wider field of view.
- the mounting bracket 337 may couple with the back plate 339 such that they contact each other at various points in a common plane of contact, thereby creating an assembly including the doorbell 330 and the mounting bracket 337 .
- Interference fittings may refer to a type of connection where a material relies on pressure and/or gravity coupled with the material's physical strength to support a connection to a different element.
- FIG. 18 is a top view and FIG. 19 is a front view of a passive infrared sensor assembly 179 including the lens 132 , the passive infrared sensor holder 143 , the passive infrared sensors 144 , and a flexible power circuit 145 .
- the passive infrared sensor holder 143 is configured to mount the passive infrared sensors 144 facing out through the lens 132 at varying angles, thereby allowing the passive infrared sensor 144 field of view to be expanded to 180 ° or more and also broken up into various zones, as further described below.
- the passive infrared sensor holder 143 may include one or more faces 178 , including a center face 178 C and two side faces 178 S to either side of the center face 178 C.
- each of the faces 178 defines an opening 181 within or on which the passive infrared sensors 144 may be mounted.
- the faces 178 may not include openings 181 , but may instead comprise solid flat faces upon which the passive infrared sensors 144 may be mounted.
- the faces 178 may be any physical structure capable of housing and/or securing the passive infrared sensors 144 in place.
- the passive infrared sensor holder 143 may be secured to the rear face of the lens 132 .
- the flexible power circuit 145 may be any material or component capable of delivering power and/or data to and from the passive infrared sensors 144 , and may be contoured to conform to the non-linear shape of the passive infrared sensor holder 143 .
- the flexible power circuit 145 may connect to, draw power from, and/or transmit data to and from, the power printed circuit board 148 .
- FIG. 20 is a top view of the passive infrared sensor assembly 179 illustrating the fields of view of the passive infrared sensors 144 .
- the side faces 178 S of the passive infrared sensor holder 143 are angled at 55 ° facing outward from the center face 178 C, and each passive infrared sensor 144 has a field of view of 110 ° .
- these angles may be increased or decreased as desired.
- Zone 1 is the area that is visible only to a first one of the passive infrared sensors 144 - 1 .
- Zone 2 is the area that is visible only to the first passive infrared sensor 144 - 1 and a second one of the passive infrared sensors 144 - 2 .
- Zone 3 is the area that is visible only to the second passive infrared sensor 144 - 2 .
- Zone 4 is the area that is visible only to the second passive infrared sensor 144 - 2 and a third one of the passive infrared sensors 144 - 3 .
- Zone 5 is the area that is visible only to the third passive infrared sensor 144 - 3 .
- the doorbell 130 may be capable of determining the direction that an object is moving based upon which zones are triggered in a time sequence.
- FIG. 21 is a functional block diagram of the components within or in communication with the doorbell 330 , according to an aspect of the present embodiments.
- the bracket PCB 349 may comprise an accelerometer 350 , a barometer 351 , a humidity sensor 352 , and a temperature sensor 353 .
- the accelerometer 350 may be one or more sensors capable of sensing motion and/or acceleration.
- the barometer 351 may be one or more sensors capable of determining the atmospheric pressure of the surrounding environment in which the bracket PCB 349 may be located.
- the humidity sensor 352 may be one or more sensors capable of determining the amount of moisture present in the atmospheric environment in which the bracket PCB 349 may be located.
- the temperature sensor 353 may be one or more sensors capable of determining the temperature of the ambient environment in which the bracket PCB 349 may be located. As described above, the bracket PCB 349 may be located outside the housing of the doorbell 330 so as to reduce interference from heat, pressure, moisture, and/or other stimuli generated by the internal components of the doorbell 330 .
- the bracket PCB 349 may further comprise terminal screw inserts 354 , which may be configured to receive the terminal screws 338 and transmit power to the electrical contacts 377 on the mounting bracket 337 ( FIG. 17 ).
- the bracket PCB 349 may be electrically and/or mechanically coupled to the power PCB 348 through the terminal screws 338 , the terminal screw inserts 354 , the spring contacts 340 , and the electrical contacts 377 .
- the terminal screws 338 may receive electrical wires located at the surface to which the doorbell 330 is mounted, such as the wall of a building, so that the doorbell can receive electrical power from the building's electrical system.
- power may be transferred to the bracket PCB 349 , and to all of the components associated therewith, including the electrical contacts 377 .
- the electrical contacts 377 may transfer electrical power to the power PCB 348 by mating with the spring contacts 340 .
- the front PCB 346 may comprise a light sensor 355 , one or more light-emitting components, such as LED's 356 , one or more speakers 357 , and a microphone 358 .
- the light sensor 355 may be one or more sensors capable of detecting the level of ambient light of the surrounding environment in which the doorbell 330 may be located.
- LED's 356 may be one or more light-emitting diodes capable of producing visible light when supplied with power.
- the speakers 357 may be any electromechanical device capable of producing sound in response to an electrical signal input.
- the microphone 358 may be an acoustic-to-electric transducer or sensor capable of converting sound waves into an electrical signal.
- the LED's 356 When activated, the LED's 356 may illuminate the light pipe 336 ( FIG. 14 ).
- the front PCB 346 and all components thereof may be electrically coupled to the power PCB 348 , thereby allowing data and/or power to be transferred to and from the power PCB 348 and the front PCB 346 .
- the speakers 357 and the microphone 358 may be coupled to the camera processor 370 through an audio CODEC 361 .
- the transfer of digital audio from the user's client device 114 and the speakers 357 and the microphone 358 may be compressed and decompressed using the audio CODEC 361 , coupled to the camera processor 370 .
- digital audio data may be sent through the communication module 364 to the network 112 , routed by one or more servers 118 , and delivered to the user's client device 114 .
- the user speaks after being transferred through the network 112 , digital audio data is decompressed by audio CODEC 361 and emitted to the visitor via the speakers 357 .
- the power PCB 348 may comprise a power management module 362 , a microcontroller 363 (may also be referred to as “processor,” “CPU,” or “controller”), the communication module 364 , and power PCB non-volatile memory 365 .
- the power management module 362 may comprise an integrated circuit capable of arbitrating between multiple voltage rails, thereby selecting the source of power for the doorbell 330 .
- the battery 366 , the spring contacts 340 , and/or the connector 360 may each provide power to the power management module 362 .
- the power management module 362 may have separate power rails dedicated to the battery 366 , the spring contacts 340 , and the connector 360 .
- the power management module 362 may continuously draw power from the battery 366 to power the doorbell 330 , while at the same time routing power from the spring contacts 340 and/or the connector 360 to the battery 366 , thereby allowing the battery 366 to maintain a substantially constant level of charge.
- the power management module 362 may continuously draw power from the spring contacts 340 and/or the connector 360 to power the doorbell 330 , while only drawing from the battery 366 when the power from the spring contacts 340 and/or the connector 360 is low or insufficient.
- the battery 366 may comprise the sole source of power for the doorbell 330 .
- the spring contacts 340 may not be connected to a source of power. When the battery 366 is depleted of its charge, it may be recharged, such as by connecting a power source to the connector 360 .
- the power management module 362 may also serve as a conduit for data between the connector 360 and the microcontroller 363 .
- the microcontroller 363 may comprise an integrated circuit including a processor core, memory, and programmable input/output peripherals.
- the microcontroller 363 may receive input signals, such as data and/or power, from the PIR sensors 344 , the bracket PCB 349 , the power management module 362 , the light sensor 355 , the microphone 358 , and/or the communication module 364 , and may perform various functions as further described below.
- the microcontroller 363 may be triggered to perform one or more functions.
- the light sensor 355 may trigger the microcontroller 363 to enable “night vision,” as further described below.
- the microcontroller 363 may also act as a conduit for data communicated between various components and the communication module 364 .
- the communication module 364 may comprise an integrated circuit including a processor core, memory, and programmable input/output peripherals.
- the communication module 364 may also be configured to transmit data wirelessly to a remote network device, and may include one or more transceivers (not shown).
- the wireless communication may comprise one or more wireless networks, such as, without limitation, Wi-Fi, cellular, Bluetooth, and/or satellite networks.
- the communication module 364 may receive inputs, such as power and/or data, from the camera PCB 347 , the microcontroller 363 , the button 333 , the reset button 359 , and/or the power PCB non-volatile memory 365 .
- the communication module 364 may be triggered to perform one or more functions.
- the communication module 364 may be triggered to erase any data stored at the power PCB non-volatile memory 365 and/or at the camera PCB memory 369 .
- the communication module 364 may also act as a conduit for data communicated between various components and the microcontroller 363 .
- the power PCB non-volatile memory 365 may comprise flash memory configured to store and/or transmit data.
- the power PCB non-volatile memory 365 may comprise serial peripheral interface (SPI) flash memory.
- the camera PCB 347 may comprise components that facilitate the operation of the camera 334 .
- an imager 371 may comprise a video recording sensor and/or a camera chip.
- the imager 371 may comprise a complementary metal-oxide semiconductor (CMOS) array, and may be capable of recording high definition (e.g., 1080p or better) video files.
- CMOS complementary metal-oxide semiconductor
- a camera processor 370 may comprise an encoding and compression chip.
- the camera processor 370 may comprise a bridge processor. The camera processor 370 may process video recorded by the imager 371 and audio recorded by the microphone 358 , and may transform this data into a form suitable for wireless transfer by the communication module 364 to a network.
- the camera PCB memory 369 may comprise volatile memory that may be used when data is being buffered or encoded by the camera processor 370 .
- the camera PCB memory 369 may comprise synchronous dynamic random-access memory (SD RAM).
- IR LED's 368 may comprise light-emitting diodes capable of radiating infrared light.
- IR cut filter 367 may comprise a system that, when triggered, configures the imager 371 to see primarily infrared light as opposed to visible light.
- the IR LED's 368 may shine infrared light through the doorbell 330 enclosure out to the environment, and the IR cut filter 367 may enable the imager 371 to see this infrared light as it is reflected or refracted off of objects within the field of view of the doorbell. This process may provide the doorbell 330 with the “night vision” function mentioned above.
- Computer vision includes methods for acquiring, processing, analyzing, and understanding images and, in general, high-dimensional data from the real world in order to produce numerical or symbolic information, e.g. in the form of decisions.
- Computer vision seeks to duplicate the abilities of human vision by electronically perceiving and understanding an image. Understanding in this context means the transformation of visual images (the input of the retina) into descriptions of the world that can interface with other thought processes and elicit appropriate action. This image understanding can be seen as the disentangling of symbolic information from image data using models constructed with the aid of geometry, physics, statistics, and learning theory.
- Computer vision has also been described as the enterprise of automating and integrating a wide range of processes and representations for vision perception.
- computer vision is concerned with the theory behind artificial systems that extract information from images.
- the image data can take many forms, such as video sequences, views from multiple cameras, or multi-dimensional data from a scanner.
- computer vision seeks to apply its theories and models for the construction of computer vision systems.
- One aspect of computer vision comprises determining whether or not the image data contains some specific object, feature, or activity.
- Different varieties of computer vision recognition include: Object Recognition (also called object classification)—One or several pre-specified or learned objects or object classes can be recognized, usually together with their 2D positions in the image or 3D poses in the scene. Identification—An individual instance of an object is recognized. Examples include identification of a specific person's face or fingerprint, identification of handwritten digits, or identification of a specific vehicle.
- Detection The image data are scanned for a specific condition. Examples include detection of possible abnormal cells or tissues in medical images or detection of a vehicle in an automatic road toll system. Detection based on relatively simple and fast computations is sometimes used for finding smaller regions of interesting image data that can be further analyzed by more computationally demanding techniques to produce a correct interpretation.
- OCR Optical Character Recognition
- 2D Code Reading Reading of 2D codes such as data matrix and QR codes.
- Facial Recognition Shape Recognition Technology (SRT)—Differentiating human beings (e.g. head and shoulder patterns) from objects.
- embodiments of the present A/V recording and communication doorbell 130 may include a computer vision module 163 .
- the computer vision module 163 may include any of the components (e.g. hardware) and/or functionality described herein with respect to computer vision, including, without limitation, one or more cameras, sensors, and/or processors.
- the microphone 150 , the camera 154 , and/or the imaging processor 240 may be components of the computer vision module 163 .
- Image acquisition A digital image is produced by one or several image sensors, which, besides various types of light-sensitive cameras, may include range sensors, tomography devices, radar, ultra-sonic cameras, etc. Depending on the type of sensor, the resulting image data may be a 2D image, a 3D volume, or an image sequence.
- the pixel values may correspond to light intensity in one or several spectral bands (gray images or color images), but can also be related to various physical measures, such as depth, absorption or reflectance of sonic or electromagnetic waves, or nuclear magnetic resonance.
- Pre-processing Before a computer vision method can be applied to image data in order to extract some specific piece of information, it is usually beneficial to process the data in order to assure that it satisfies certain assumptions implied by the method. Examples of pre-processing include, but are not limited to re-sampling in order to assure that the image coordinate system is correct, noise reduction in order to assure that sensor noise does not introduce false information, contrast enhancement to assure that relevant information can be detected, and scale space representation to enhance image structures at locally appropriate scales.
- Feature extraction Image features at various levels of complexity are extracted from the image data. Typical examples of such features are: Lines, edges, and ridges; Localized interest points such as corners, blobs, or points; More complex features may be related to texture, shape, or motion.
- Detection/segmentation At some point in the processing a decision may be made about which image points or regions of the image are relevant for further processing. Examples are: Selection of a specific set of interest points; Segmentation of one or multiple image regions that contain a specific object of interest; Segmentation of the image into nested scene architecture comprising foreground, object groups, single objects, or salient object parts (also referred to as spatial-taxon scene hierarchy).
- the input may be a small set of data, for example a set of points or an image region that is assumed to contain a specific object.
- the remaining processing may comprise, for example: Verification that the data satisfy model-based and application-specific assumptions; Estimation of application-specific parameters, such as object pose or object size; Image recognition—classifying a detected object into different categories; Image registration—comparing and combining two different views of the same object.
- One or more of the present embodiments may include a vision processing unit (not shown separately, but may be a component of the computer vision module 163 ).
- a vision processing unit is an emerging class of microprocessor; it is a specific type of AI (artificial intelligence) accelerator designed to accelerate machine vision tasks.
- Vision processing units are distinct from video processing units (which are specialized for video encoding and decoding) in their suitability for running machine vision algorithms such as convolutional neural networks, SIFT, etc.
- Vision processing units may include direct interfaces to take data from cameras (bypassing any off-chip buffers), and may have a greater emphasis on on-chip dataflow between many parallel execution units with scratchpad memory, like a manycore DSP (digital signal processor). But, like video processing units, vision processing units may have a focus on low precision fixed point arithmetic for image processing.
- Some of the present embodiments may use facial recognition hardware and/or software, as a part of the computer vision system.
- Various types of facial recognition exist, some or all of which may be used in the present embodiments.
- Some face recognition algorithms identify facial features by extracting landmarks, or features, from an image of the subject's face. For example, an algorithm may analyze the relative position, size, and/or shape of the eyes, nose, cheekbones, and jaw. These features are then used to search for other images with matching features. Other algorithms normalize a gallery of face images and then compress the face data, only saving the data in the image that is useful for face recognition. A probe image is then compared with the face data.
- One of the earliest successful systems is based on template matching techniques applied to a set of salient facial features, providing a sort of compressed face representation.
- Recognition algorithms can be divided into two main approaches, geometric, which looks at distinguishing features, or photometric, which is a statistical approach that distills an image into values and compares the values with templates to eliminate variances.
- Popular recognition algorithms include principal component analysis using eigenfaces, linear discriminant analysis, elastic bunch graph matching using the Fisherface algorithm, the hidden Markov model, the multilinear subspace learning using tensor representation, and the neuronal motivated dynamic link matching.
- a newly emerging trend, claimed to achieve improved accuracy, is three-dimensional face recognition.
- This technique uses 3D sensors to capture information about the shape of a face. This information is then used to identify distinctive features on the surface of a face, such as the contour of the eye sockets, nose, and chin.
- 3D face recognition is that it is not affected by changes in lighting like other techniques. It can also identify a face from a range of viewing angles, including a profile view. Three-dimensional data points from a face vastly improve the precision of face recognition. 3D research is enhanced by the development of sophisticated sensors that do a better job of capturing 3D face imagery. The sensors work by projecting structured light onto the face. Up to a dozen or more of these image sensors can be placed on the same CMOS chip—each sensor captures a different part of the spectrum.
- Another variation is to capture a 3D picture by using three tracking cameras that point at different angles; one camera pointing at the front of the subject, a second one to the side, and a third one at an angle. All these cameras work together to track a subject's face in real time and be able to face detect and recognize.
- thermal cameras which may only detect the shape of the head and ignore the subject accessories such as glasses, hats, or make up.
- Biometrics refers to metrics related to human characteristics.
- Biometrics authentication (or realistic authentication) is used in various forms of identification and access control.
- Biometric identifiers are the distinctive, measurable characteristics used to label and describe individuals.
- Biometric identifiers can be physiological characteristics and/or behavioral characteristics. Physiological characteristics may be related to the shape of the body. Examples include, but are not limited to, fingerprints, palm veins, facial recognition, three-dimensional facial recognition, skin texture analysis, DNA, palm prints, hand geometry, iris recognition, retina recognition, and odor/scent recognition. Behavioral characteristics may be related to the pattern of behavior of a person, including, but not limited to, typing rhythm, gait, and voice recognition.
- the present embodiments may use any one, or any combination of more than one, of the foregoing biometrics to identify and/or authenticate a person who is either suspicious or who is authorized to take certain actions with respect to a property or expensive item of collateral.
- the computer vision module 163 , and/or the camera 154 and/or the processor 160 may receive information about the person using any one, or any combination of more than one, of the foregoing biometrics.
- one aspect of the present embodiments includes the realization that as A/V recording and communication devices continue to become more prevalent, leveraging the functionalities of these devices (e.g., video doorbells, security cameras, etc.) by persons other than the owners/users of the A/V recording and communication devices may prove increasingly useful.
- Current A/V recording and communication devices, other than the present embodiments sometimes do not allow persons other than the owner/user of the A/V recording and communication device access to the device's functionalities (e.g., the camera, the speaker, etc.). As a result, there may be missed opportunities for persons other than the owners/users of the A/V recording and communication devices to leverage these functionalities to provide safety, security, and peace of mind.
- a neighborhood may include a plurality of A/V recording and communication devices installed at various homes, and the neighborhood may be dark and/or dangerous.
- a person walking through the neighborhood may desire to view video being recorded in a field of view of one or more of the A/V recording and communication devices in order to determine if there is any suspicious activity or suspicious persons in the neighborhood.
- the present embodiments solve this problem by leveraging the functionality of A/V recording and communication devices, such as A/V recording and communication doorbells, to allow access to the A/V recording and communication devices by users of client devices in proximity to the A/V recording and communication devices.
- A/V recording and communication devices such as A/V recording and communication doorbells
- the users of the client devices may be able to determine if any suspicious activity and/or persons are present, and in response, take the appropriate action. For example, the users of the client devices may notify law enforcement, leave the area, signal for help, signal an alarm, and/or speak to a suspicious person through a speaker of one or more of the A/V recording and communication devices.
- the users of the client devices in proximity to the A/V recording and communication devices may be able to leverage the functionalities of the devices, the safety of the users and the neighborhood, in addition to the overall public safety, may be increased.
- a client device in response to entering a proximity zone of an audio/video (A/V) recording and communication device, requests, by a processor of the client device using a communication module, access to a camera of the A/V recording and communication device; in response to the request for access, receives, by the processor using the communication module, from the camera, image data being recorded by the camera in a field of view of the camera; and displays, by the processor on the display, the image data.
- A/V audio/video
- FIG. 22 is a functional block diagram illustrating a system 400 for communicating in a network according to various aspects of the present disclosure.
- the system 400 may include one or more audio/video (A/V) recording and communication devices 402 configured to access a user's network 408 to connect to a network (Internet/PSTN) 410 .
- the one or more A/V recording and communication devices 402 may include any or all of the components and/or functionality of the A/V recording and communication device 100 ( FIGS. 1-2 ), the A/V recording and communication doorbell 130 ( FIGS. 3-13 ), and/or the A/V recording and communication doorbell 330 ( FIGS. 14-21 ).
- the present disclosure provides numerous examples of methods and systems including A/V recording and communication devices 402 , such as A/V recording and communication doorbells, but the present embodiments are equally applicable for A/V recording and communication devices 402 other than doorbells.
- the present embodiments may include one or more A/V recording and communication security cameras and/or A/V recording and communication security floodlights instead of, or in addition to, one or more A/V recording and communication doorbells.
- An example A/V recording and communication security camera may include substantially all of the structure and functionality of the doorbell 130 , but without the front button 148 , the button actuator 228 , and/or the light pipe 232 .
- the user's network 408 may include any or all of the components and/or functionality of the user's network 110 described herein.
- the network (Internet/PSTN) 410 may include any or all of the components and/or functionality of the network (Internet/PSTN) 112 described herein.
- the system 400 may also include one or more client devices 404 , 406 , which in various embodiments may be configured to be in network communication and/or associated with the A/V recording and communication device 402 . In some of the present embodiments, the client devices 404 , 406 may be configured to be in network communication with one or more backend devices, such as the backend server(s) 430 .
- the client devices 404 , 406 may comprise, for example, a mobile phone such as a smartphone, or a computing device such as a tablet computer, a laptop computer, a desktop computer, etc.
- the client devices 404 , 406 may include any or all of the components and/or functionality of the client device 114 and/or the client device 800 described herein.
- the client devices 404 , 406 may not be associated with the A/V recording and communication device 402 .
- the user/owner of the client device(s) 404 , 406 may not also use/own a A/V recording and communication device 402 .
- the system 400 may also include one or more client devices 407 , which in various embodiments may be configured to be in communication with the one or more A/V recording and communication devices 402 .
- the one or more client devices 407 may be in network communication with the A/V recording and communication device 402 over the network (Internet/PSTN) 410 and/or the user's network 408 .
- the one or more client devices 407 may be connected to the user's network 408 and communicate with the A/V recording and communication device 402 directly over the user's network 408 .
- the one or more client devices 407 may be directly connected to the A/V recording and communication device 402 (e.g., where the A/V recording and communication device 402 generates an ad hoc network), and thus communicate directly with the A/V recording and communication device 402 without using the network (Internet/PSTN) 410 and/or the user's network 408 .
- the client devices 407 may be configured to be in network communication with one or more backend devices, such as the backend server(s) 430 .
- the client devices 407 may communicate with the one or more backend devices to access the image data 460 ( FIG.
- the client devices 407 may comprise, for example, a mobile phone such as a smartphone, or a computing device such as a tablet computer, a laptop computer, a desktop computer, etc.
- the client devices 407 may include any or all of the components and/or functionality of the client device 114 and/or the client device 800 described herein.
- the client devices 407 may not be associated with any A/V recording and communication devices, including the A/V recording and communication device 402 .
- the client devices 407 may be associated with an A/V recording and communication device that is not connected to and/or in communication with the user's network 408 .
- the user/owner of the A/V recording and communication device 402 may not be the user/owner of the client device 407 .
- the system 400 may also include various backend devices such as (but not limited to) storage devices 432 , backend servers 430 , and backend APIs 428 that may be in network communication with the A/V recording and communication device 402 , the client devices 404 , 406 , and/or the client devices 407 .
- the storage devices 432 may be a separate device from the backend servers 430 (as illustrated) or may be an integral component of the backend servers 430 .
- the storage devices 432 may be similar in structure and/or function to the storage device 116 ( FIG. 1 ).
- the backend servers 430 and backend APIs 428 may be similar in structure and/or function to the server 118 and the backend API 120 ( FIG. 1 ), respectively.
- FIG. 23 is a functional block diagram illustrating an embodiment of the A/V recording and communication device 402 according to various aspects of the present disclosure.
- the A/V recording and communication device 402 may comprise a processing module 446 that is operatively connected to a camera 444 , a microphone 446 , a speaker 448 , a motion sensor 474 , and a communication module 450 .
- the processing module 446 may comprise a processor 452 , volatile memory 454 , and non-volatile memory 456 that includes a device application 458 .
- the device application 458 may configure the processor 452 to capture image data 460 using the camera 444 , audio data 462 using the microphone 446 , and/or motion data 468 using the camera 444 and/or the motion sensor 474 . In some embodiments, the device application 458 may also configure the processor 452 to generate text data 464 describing the image data 460 , such as in the form of metadata, for example. In some of the present embodiments, the device application 458 may also configure the processor 452 to generate the proximity zone 470 and/or monitor the proximity zone 470 using the communication module 450 .
- the device application 458 may configure the processor 452 to transmit the image data 460 , the audio data 462 , the motion data 468 , and/or the text data 464 to the client device 404 , 406 , the client device 407 , and/or the backend server 430 using the communication module 450 .
- the processor 452 may further configure the device application 458 to transmit the communication signals 479 and/or receive the communication signals 481 ( FIG. 25 ) from the client device 407 and measure the signal strength (e.g., Received Signal Strength Indication (RSSI)) of the communication signals 481 .
- RSSI Received Signal Strength Indication
- the device application 458 may also configure the processor 452 to generate and transmit an output signal 466 that may include the image data 460 , the audio data 462 , the text data 464 , the access request 474 , and/or the motion data 468 .
- the output signal 466 may be transmitted to the backend server(s) 430 using the communication module 450 , and the backend server(s) 430 may transmit (or forward) the output signal 466 to the client device 404 , 406 and/or the client device 407 .
- the output signal 466 may be transmitted directly to the client device 404 , 406 and/or the client device 407 .
- the device application 458 may configure the processor 452 to receive the output signal 467 from the client device 407 using the communication module 450 , where the output signal 467 may include the access request 475 , the location data 477 (e.g., the current physical location of the client device 407 ), and/or the communication signals 479 generated by the client device 407 .
- the image data 460 may comprise image sensor data such as (but not limited to) exposure values and data regarding pixel values for a particular sized grid. Further, the image data 460 may comprise converted image sensor data for standard image file formats such as (but not limited to) JPEG, JPEG 2000, TIFF, BMP, or PNG. In addition, the image data 460 may also comprise data related to the still image, video, or combination thereof, included in the image data 460 . Such data may include (but is not limited to) image sequences, frame rates, and the like. Moreover, the image data 460 may include data that is analog, digital, compressed, uncompressed, and/or in vector formats.
- the image data 460 may include still images, live video, and/or pre-recorded video.
- the image data 460 may be recorded by the camera 444 in a field of view of the camera 444 .
- the processor 452 may be configured to transmit the image data 460 (e.g., as live streaming video) to the client device 404 , 406 and/or the client device 407 (in some embodiments, via the backend server 430 ).
- the image data 460 may take on various forms and formats as appropriate to the requirements of a specific application in accordance with the present embodiments.
- the term “record” may also be referred to as “capture” as appropriate to the requirements of a specific application in accordance with the present embodiments.
- the motion data 468 may comprise motion sensor data generated in response to motion events.
- the motion data 468 may include an amount or level of a data type generated by the motion sensor 474 .
- the motion data 468 may include voltage data generated by the motion sensor 474 in response to the presence of infrared radiation.
- the motion data 468 may also comprise time-based and/or location-based information such as the amount of time a motion event is detected and/or the location of the motion event in the field of view of the motion sensor 474 (e.g., Zones 1-5 ( FIG.
- the motion data 468 may include the amount of time an increase in voltage is detected based on the presence of infrared radiation indicative of a motion event.
- the motion data 468 may include the data type (e.g., voltage) generated specific to the type of motion sensor 474 (e.g., PIR, microwave, acoustic, etc.).
- the motion data 468 may further include an estimated speed and/or direction data of the person and/or object that caused the motion event.
- the motion data 468 may include an estimated speed of a person and/or object passing in a field of view of the motion sensor 474 .
- the motion data 468 may include a direction that a person and/or object in front of the motion sensor 474 is traveling, such as toward or away from the A/V recording and communication device 402 .
- the motion data 468 may be generated by the camera 444 .
- the A/V recording and communication device 402 may not have a motion sensor 474 (as illustrated by the dashed lines around the motion sensor 474 in FIG. 23 ).
- the detection of a motion event, the determination of whether a motion event is caused by the movement of a person in a field of view of the A/V recording and communication device 402 , and/or the speed and/or location of a person and/or object in the field of view of the A/V recording and communication device 402 may be determined using the motion data 468 generated by the camera 444 .
- the motion data 468 may include differences between successive frames (e.g., pixels) of the image data 460 , where the differences may be the result of motion in the field of view of the camera 444 , for example.
- the location data 476 may include the location of the A/V recording and communication device 402 .
- the location data 476 may be based on global positioning system (GPS) data, Wi-Fi positioning system (WPS) data, the known location of the Access Point (e.g., router) that the A/V recording and communication device 402 is using to access the user's network 408 , the IP Address of the A/V recording and communication device 402 , or the like.
- the location of the A/V recording and communication device 402 may be determined from the location data 476 during a set-up/activation process of the device 402 (and during any subsequent set-up/activation process).
- the location data 476 may include the proximity zone 470 .
- the proximity zone 470 may be an area, region, etc. where, when the client device 407 enters the proximity zone 470 , the client device 407 may be able to access and/or communicate with the A/V recording and communication device 402 (e.g., access the camera 444 and/or access the speaker 446 ).
- the proximity zone 470 may or may not include the location of the A/V recording and communication device 402 , depending on the embodiment.
- the proximity zone 470 may include a portion of the street on which the house having the A/V recording and communication device 402 is located, but may not include the house and/or the property the house sits on, so as not to encourage the user of the client device 407 to enter the property where the A/V recording and communication device 402 is located.
- the proximity zone 470 may include the A/V recording and communication device 402 along with other A/V recording and communication devices (e.g., similar to the illustration of FIG. 41 ).
- the proximity zone 470 may be defined by a portion of a street, a neighborhood, a town, etc., and the A/V recording and communication devices within the proximity zone 470 may share the same or similar proximity zone 470 .
- the proximity zone 470 may be defined by the user of the client device 404 , 406 associated with the A/V recording and communication device 402 (e.g., as user settings). In other embodiments, the proximity zone 470 may be defined by the settings of the A/V recording and communication device 402 (e.g., as default settings).
- the user of the client device 404 , 406 may be able to activate a sharing mode of the A/V recording and communication device 402 , for example, whereby the A/V recording and communication device 402 may generate and monitor the proximity zone 470 and allow access to the A/V recording and communication device 402 in response to the client device 407 (and/or other client devices) entering the proximity zone 470 .
- the client device 407 may transmit an access request 475 to the A/V recording and communication device 402 when inside of the proximity zone 470 to request access to the A/V recording and communication device 402 .
- the user of the client device 404 , 406 may receive a notification of the access request 475 ( FIG.
- the client device 407 may be automatically allowed access, or may be allowed access based on the settings of the A/V recording and communication device 402 (e.g., user settings, default settings, etc.). For example, in some of the present embodiments, the client device 407 may be allowed access to the A/V recording and communication device 402 only if the client device 407 is associated with another A/V recording and communication device (e.g., part of a network of users/owners of A/V recording and communication devices).
- the client device 407 may be allowed access to the A/V recording and communication device 402 only if the client device 407 is associated with another A/V recording and communication device (e.g., part of a network of users/owners of A/V recording and communication devices).
- the client device 407 may be allowed access to the A/V recording and communication device 402 .
- the communication signals 479 may be transmitted by the A/V recording and communication device 402 (e.g., within the proximity zone 470 ).
- the communication signals 481 may be transmitted by the client device 407 ( FIG. 25 ) to the A/V recording and communication device 402 .
- the communication signals 479 may include the access request 474 from the A/V recording and communication device 402 , such that when the client device 407 enters the proximity zone 470 , the client device 407 receives the communication signals 479 including the access request 474 .
- the user of the client device 407 may accept the access request 474 and access the A/V recording and communication device 402 .
- the client device 407 may automatically (without user intervention) accept the access request 474 and access the A/V recording and communication device 402 .
- the communication signals 479 may be received by the client device 407 (and/or other client devices), and in response, the client device 407 may transmit the location data 477 of the client device 407 to the A/V recording and communication device 402 (and/or the backend server 430 ) for comparing against the proximity zone 470 to determine if the client device 407 is within the proximity zone 470 .
- the A/V recording and communication device 402 may transmit the access request 474 to the client device 407 to establish connection/communication with the client device 407 (in some embodiments, via the backend server 430 ).
- the A/V recording and communication device 402 may receive the communication signals 481 from the client device 407 , where the communication signals 481 may include the access request 475 and/or the location data 477 .
- the A/V recording and communication device 402 (and/or the backend server 430 ) may compare the location data 477 of the client device 407 to the proximity zone 470 to determine if the client device 407 is within the proximity zone 470 . If it is determined that the client device 407 is within the proximity zone 470 , the client device 407 may be allowed access to the A/V recording and communication device 402 .
- the communication signals 479 , 481 may be used for defining the proximity zone 470 .
- the communication signals 479 , 481 may include Wi-Fi, Bluetooth, ZigBee, and/or other signal types.
- the Received Signal Strength Indication (RSSI) of the communication signals 479 , 481 may define the proximity zone 470 (because RSSI values may be indicative of a distance from the device transmitting the communication signals 479 , 481 ).
- the A/V recording and communication device 402 may transmit the communication signals 479 and the client device 407 may receive the communication signals 479 and analyze the communication signals 479 to determine the RSSI values of the communication signals 479 .
- the client device 407 may then transmit the RSSI values of the communication signals 479 to the A/V recording and communication device 402 (and/or the backend server 430 ), and the A/V recording and communication device 402 (and/or the backend server 430 ) may compare the RSSI values to the RSSI values that define the proximity zone 470 (e.g., Bluetooth RSSI values greater than ⁇ 70 dBm on a ⁇ 100-0 scale) to determine if the client device 470 is within the proximity zone 470 .
- the RSSI values that define the proximity zone 470 e.g., Bluetooth RSSI values greater than ⁇ 70 dBm on a ⁇ 100-0 scale
- the client device 407 may transmit the communication signals 481 (e.g., Bluetooth, Wi-Fi (e.g., acting as a mobile hotspot), ZigBee, and/or other signal types) to the A/V recording and communication device 402 and the A/V recording and communication device 402 may analyze the communication signals 481 to determine the RSSI values of the communication signals 481 . Once the RSSI values of the communication signals 481 are determined, the A/V recording and communication device 402 (and/or the backend server 430 ) may determine if the client device 407 is within the proximity zone 470 .
- the communication signals 481 e.g., Bluetooth, Wi-Fi (e.g., acting as a mobile hotspot), ZigBee, and/or other signal types
- the scale used to determine the RSSI values may be different dependent on the manufacturer of the Wi-Fi chip, Bluetooth chip, ZigBee chip, or other signal type chip. For example, one Bluetooth chip manufacturer may have an RSSI scale of ⁇ 100-0 dBm while another Bluetooth Chip manufacturer may have an RSSI scale of ⁇ 200-0 dBm.
- the RSSI scale of the chip from the A/V recording and communication device 402 may be known, and the proximity zone 470 may be defined based on the known RSSI scale.
- the processor 534 of the client device 407 may program the client application 540 to determine an identification of the chip of the client device 407 and/or the RSSI scale of the particular chip of the client device 407 .
- the client device 407 may transmit the identification of the chip and/or the RSSI scale along with the RSSI values of the communication signals 479 from the A/V recording and communication device 402 to the A/V recording and communication device 402 and/or the backend server 430 .
- the RSSI values may be normalized, such as by converting the RSSI values to a percentage in view of the RSSI scale, and the percentage may be used to define the proximity zone 470 .
- an RSSI database may be stored on the A/V recording and communication device 402 and/or the backend server 430 , and the client device 407 may transmit the RSSI values and an identification of the chip and/or the RSSI scale to the A/V recording and communication device 402 and/or the backend server 430 to be compared against the RSSI database.
- the RSSI values that define the proximity zone 470 may be determined in view of the identification of the chip and/or the RSSI scale. The RSSI values may then be compared to the RSSI values that define the proximity zone 470 to determine if the client device 407 is within the proximity zone 470 .
- the communication signals 479 , 481 may include signals generated in Low Power Wide Area Networks (LPWAN) such as Long Range Wide Area Network (LoRaWANTM) devices.
- LPWAN Low Power Wide Area Networks
- LoRaWANTM Long Range Wide Area Network
- location data 476 , 477 of the A/V recording and communication device 402 and/or the client device 407 may be based on the communication signals 479 , 481 from LPWANs.
- the A/V recording and communication device 402 and/or the backend server 430 may be in communication with and/or include a LPWAN device (e.g., a concentrator or gateway, such as a LoRa® gateway) configured to operate in LoRaWANsTM and/or other LPWANs.
- a LPWAN device e.g., a concentrator or gateway, such as a LoRa® gateway
- the LPWAN device may be included in the Access Point (e.g., router) that the A/V recording and communication device 402 is connected.
- the LPWAN device may be configured to detect the presence and/or location of devices that include an LPWAN sensor (e.g., a LoRa® RF sensor), which in some embodiments, may be the client device 407 and/or the A/V recording and communication device 402 .
- an LPWAN sensor e.g., a LoRa® RF sensor
- the communication signals 479 , 481 may be received by the LPWAN device and analyzed (e.g., by the LPWAN device, the backend server 430 , etc.) to determine the location data 476 , 477 of the client device 407 and/or the A/V recording and communication device 402 .
- the location data 476 , 477 may then be used by the A/V recording and communication device 402 and/or the backend server 430 to determine if the client device 407 is within the proximity zone 470 .
- FIG. 24 is a functional block diagram illustrating one embodiment of the backend server(s) 430 according to various aspects of the present disclosure.
- the backend server(s) 430 may comprise a processing module 500 including a processor 502 , volatile memory 504 , a network interface 520 , and non-volatile memory 506 .
- the network interface 520 may allow the backend server(s) 430 to access and communicate with devices connected to the network (Internet/PSTN) 410 .
- the non-volatile memory 506 may include a server application 508 that configures the processor 502 to receive the image data 460 , the audio data 462 , the text data 464 , the motion data 468 , the location data 476 , 477 , the access requests 474 , 475 , the proximity zone 470 , and/or information related to the communication signals 479 , 481 from the A/V recording and communication device 402 and/or the client device 407 (e.g., in the output signal 466 , 467 ).
- a server application 508 that configures the processor 502 to receive the image data 460 , the audio data 462 , the text data 464 , the motion data 468 , the location data 476 , 477 , the access requests 474 , 475 , the proximity zone 470 , and/or information related to the communication signals 479 , 481 from the A/V recording and communication device 402 and/or the client device 407 (e.g., in the output signal 4
- the non-volatile memory 506 may also include source identifying data 510 that may be used to identify the A/V recording and communication device 402 , the client devices 404 , 406 , and/or the client device 407 .
- the source identifying data 410 may include (and/or be used in combination with) the location data 476 , 477 .
- identifying the A/V recording and communication device 402 may include determining the location of the A/V recording and communication device 402 and/or the corresponding proximity zone 470 of the device 402 based on the location data 476 .
- the server application 508 may further configure the processor 502 to generate and transmit a report signal (not shown) to a third-party client device (not shown), which may be associated with a law enforcement agency, for example.
- the report signal sent to the law enforcement agency may include information indicating an approximate location of where the image data 460 was captured, which may assist the law enforcement agency with apprehending the criminal perpetrator shown in the image data 460 .
- the backend server 430 may determine the proximity zone 470 and/or the location data 476 associated with the proximity zone 470 . In such embodiments, the backend server 430 may also receive the location data 477 of the client device 407 and compare the location data 477 to the proximity zone 470 to determine if the client device 407 is within the proximity zone 470 . In some of the present embodiments, the backend server 430 may receive the location data 476 of the A/V recording and communication device 402 to determine the location (e.g., geographical coordinates) of the A/V recording and communication device 402 .
- the backend server 430 may use this information, and the information pertaining to the proximity zone 470 (e.g., size, shape, etc.), to determine the location data 476 (e.g., geographical coordinates) of the proximity zone 470 .
- the backend server 430 may transmit the proximity zone 470 and/or location data 476 to the A/V recording and communication device 402 , or may analyze the proximity zone 470 locally on the backend server 430 .
- the proximity zone 470 may not be defined based on a location of a single A/V recording and communication device 402 , but may be defined by a region (e.g., a street, a neighborhood, a town, etc.).
- the backend server 430 may receive the location data 476 of the A/V recording and communication device 402 and analyze the location data 476 to determine if the A/V recording and communication device 402 is within a proximity zone 470 (such as the A/V recording and communication device 724 located within the proximity zone 716 of FIG. 41 ).
- the backend server 430 (and/or the A/V recording and communication device 402 ) may analyze the location data 477 of the client device 407 (and/or other client devices) to determine if the client device 407 is within the proximity zone 470 , and the client device 407 may be allowed access to each of the A/V recording and communication devices 402 within the proximity zone 470 .
- the backend server(s) 430 may be configured to, in response to the client device 407 entering the proximity zone 470 of the A/V recording and communication device 402 , receive, from the client device 407 , an access request 475 to allow the client device 407 access to the camera 444 of the A/V recording and communication device 402 ; in response to receiving the access request 475 , transmit the access request 475 to the A/V recording and communication device 402 ; in response to transmitting the access request 475 , receive, from the A/V recording and communication device 402 , the image data 460 being recorded by the camera 444 of the A/V recording and communication device 402 in a field of view of the camera 444 ; and in response to receiving the image data 460 , transmitting the image data 460 to the client device 407 .
- FIG. 25 is a functional block diagram illustrating one embodiment of a client device 407 according to various aspects of the present disclosure.
- the client device 407 may comprise a processing module 532 that is operatively connected to an input interface 524 , a microphone 527 , a speaker 528 , and a communication module 530 .
- the client device 407 may further comprise a camera (not shown) operatively connected to the processing module 532 .
- the processing module 532 may comprise a processor 534 , volatile memory 536 , and non-volatile memory 538 that includes a client application 540 .
- the client application 540 may configure the processor 534 to receive input(s) to the input interface 524 (e.g., requests for access to the A/V recording and communication device 402 ) and/or to capture the audio data 463 using the microphone 527 , for example.
- the client application 540 may configure the processor 534 to transmit the location data 477 , the access request 475 , the audio data 463 , the communication signals 481 , and/or the output signal 467 to the A/V recording and communication device 402 and/or the backend server(s) 430 using the communication module 530 .
- the input interface 524 may include a display 525 .
- the display 525 may include a touchscreen, such that the user of the client device 407 can provide inputs directly to the display 525 (e.g., a request for access to the A/V recording and communication device 402 ).
- the client device 407 may not include a touchscreen.
- the user may provide an input using any input device, such as, without limitation, a mouse, a trackball, a touchpad, a joystick, a pointing stick, a stylus, etc.
- the location data 477 may be used by the A/V recording and communication device 402 and/or the backend server 430 to determine if the client device 407 is within the proximity zone 470 .
- the client device 407 may transmit the location data 477 to the A/V recording and communication device 402 and/or the backend server 430 as part of the communication signals 481 and/or the output signal 467 using the communication module 450 .
- the client device 407 may receive the access request 474 from the A/V recording and communication device 402 and/or transmit the access request 475 to the A/V recording and communication device 402 using the communication module 450 .
- a device list 478 (including each of the devices from which the client device 407 may be allowed to request access) may include the A/V recording and communication device 402 .
- the user of the client device 407 may be able to select the A/V recording and communication device 402 from the device list 478 , and in response, the access request 475 may be transmitted to the selected A/V recording and communication device 402 .
- the A/V recording and communication device 402 may be included in the device list 478 in response to the client device 407 receiving the access request 474 from the A/V recording and communication device 402 , such that the selection of the A/V recording and communication device 402 from the device list 478 may include an acceptance of the access request 474 .
- the various components including (but not limited to) the processing modules 446 , 532 , 500 , the communication modules 450 , 530 , and the network interface 520 are represented by separate boxes.
- the graphical representations depicted in each of FIGS. 23-25 are, however, merely examples, and are not intended to indicate that any of the various components of the A/V recording and communication device 402 , the client device 407 , or the backend server(s) 430 are necessarily physically separate from one another, although in some embodiments they might be. In other embodiments, however, the structure and/or functionality of any or all of the components of the A/V recording and communication device 402 may be combined.
- the communication module 450 may include its own processor, volatile memory, and/or non-volatile memory. Further, the structure and/or functionality of any or all of the components of the client device 407 may be combined. In addition, in some embodiments the communication module 530 may include its own processor, volatile memory, and/or non-volatile memory. Further, the structure and/or functionality of any or all of the components of the backend server(s) 430 may be combined. In addition, in some embodiments the network interface 520 may include its own processor, volatile memory, and/or non-volatile memory.
- FIG. 26 is a flowchart illustrating a process for accessing cameras of A/V recording and communication devices based on location according to various aspects of the present disclosure.
- the process 2600 in response to entering a proximity zone of an A/V recording and communication device, requests, by a processor using a communication module, access to a camera of the A/V recording and communication device.
- the processor 534 of the client device 407 in response to entering the proximity zone 470 , may request, using the communication module 530 , access to the camera 444 of the A/V recording and communication device 402 .
- a variety of methods may be used to determine that the client device 407 is within the proximity zone 470 .
- the backend server 430 and/or the A/V recording and communication device 402 may compare the location data 477 of the client device 407 to the proximity zone 470 , and in response to determining that the client device 407 is within the proximity zone 470 , may provide an indication to the client device 407 that the A/V recording and communication device 402 may be accessed (e.g., by including the A/V recording and communication device 402 on the device list 478 ).
- the client device 407 may query the backend server 430 to determine whether the client device 407 is within a proximity zone of any A/V recording and communication devices, which may include the proximity zone 470 of the A/V recording and communication device 402 .
- the user of the client device 407 may open a computer program application (e.g., the client application 540 , a web server, etc.) and request to view available devices, and in response, receive a notification that the A/V recording and communication device 402 may be accessed.
- the user of the client device 407 may transmit the access request 475 to the A/V recording and communication device 402 (in some embodiments, via the backend server 430 ).
- the proximity zone 470 may be defined by the communication signals 479 of the A/V recording and communication device 402 .
- the A/V recording and communication device 402 may transmit the communication signals 479 and the client device 407 may receive the communication signals 479 and analyze the communication signals 479 to determine the signal strength (e.g., RSSI), and the client device 407 may transmit the signal strength information to the A/V recording and communication device 402 and/or the backend server 430 to determine if the client device 407 is within the proximity zone 470 .
- the signal strength e.g., RSSI
- the communication signals 481 of the client device 407 may be analyzed by the A/V recording and communication device 402 to determine if the client device 407 is within the proximity zone 470 .
- the client device 407 in response to receiving the communication signals 479 from the A/V recording and communication device 402 , the client device 407 may transmit the communication signals 481 to the A/V recording and communication device 402 , where the communication signals 481 may include the location data 476 of the client device 407 .
- the A/V recording and communication device 402 may compare the location data 476 to the proximity zone 470 to determine if the client device 407 is within the proximity zone 470 .
- the A/V recording and communication device 402 may measure the signal strength of the communication signals 481 received from the client device 407 and the signals strength may be used to determine if the client device 407 is within the proximity zone 470 .
- the process 2600 in response to the request for access, receives, by the processor using the communication module, from the camera, image data being recorded by the camera in a field of view of the camera.
- the processor 534 of the client device 407 in response to transmitting the access request 475 , may receive from the camera 444 the image data 460 being recorded by the camera 444 in a field of view of the camera 444 .
- the client device 407 may receive the image data 460 as live streaming video being recorded in the field of view of the camera 444 .
- the process 2600 displays, by the processor on the display, the image data.
- the processor 534 of the client device 407 may display the image data 460 on the display 525 .
- the image data 460 may be displayed as a visual representation of the live video being recorded by the camera 444 in a field of view of the camera 444 .
- the process 2700 displays, by the processor on a display, a list of devices configured for access by a client device, the list of devices including an A/V recording and communication device 402 .
- the processor 534 of the client device 407 may display on the display 525 the device list 478 including a list of devices configured for access by the client device 407 , where device list 478 may include the A/V recording and communication device 402 .
- the device list 478 of the client device 407 may be populated and displayed on the display 525 .
- the process 2700 may continue to block B 600 of FIG. 26 .
- FIG. 28 is a flowchart illustrating a process for accessing cameras of A/V recording and communication devices based on location according to various aspects of the present disclosure.
- the process 2800 may continue from block B 600 of FIG. 26 .
- the process 2800 establishes, by a processor using a communication module, a connection to an A/V recording and communication device.
- the processor 534 of the client device 407 using the communication module 530 , may connect to (and communicate with) the A/V recording and communication device 402 .
- connection/communication may be a direct connection/communication between the A/V recording and communication device 402 and the client device 407 , such as over the user's network 408 and/or the network (Internet/PSTN) 408 .
- the A/V recording and communication device 402 may transmit the network credentials of the user's network (or an ad hoc network generated by the A/V recording and communication device 402 ) to the client device 407 (e.g., using the communication signals 479 , 481 ).
- the client device 407 may join the user's network 408 and establish the connection/communication with the A/V recording and communication device 402 .
- the client device 407 may be connected to the network (Internet/PSTN) 410 over a cellular network, for example, and the A/V recording and communication device 402 may be connected to the network (Internet/PSTN) 410 over the user's network 408 (e.g., using a router).
- the client device 407 may communicate with the A/V recording and communication device 402 over the network (Internet/PSTN) 410 .
- connection/communication may be performed using the backend server 430 , such that the backend server 430 acts as an intermediary between the client device 407 and the A/V recording and communication device 402 , as described below with respect to FIGS. 38-40 .
- FIGS. 26-28 may be implemented in a variety of embodiments, including those discussed below. However, the below-detailed embodiments are not intended to be limiting, and are provided merely as example embodiments of the present disclosure. Other embodiments similar to those outlined herein may also fall within the scope of the present disclosure.
- the process 2600 in response to the client device 407 (e.g., carried by the user 712 ) entering the proximity zone 706 , 708 , and/or 710 , may request access to the A/V recording and communication device 402 located at the house 704 .
- the proximity zone 706 is an example of a proximity zone 470 that includes the A/V recording and communication device 402 .
- the proximity zones 470 may be defined by the user of the client device 404 , 406 associated with the A/V recording and communication device 402 .
- the user may select a size of the proximity zone, such as a small (e.g., proximity zone 706 ) or large (e.g., proximity zone 708 ) proximity zone 470 .
- the user may fit a shape (e.g., a circle for the proximity zone 706 , 708 ) to a map including the house 704 or a visual representation of the house 704 , where the shape defines the proximity zone 470 .
- the user may define a proximity (e.g., radius) for the proximity zone 470 .
- the proximity zone 470 may be based on the settings of the A/V recording and communication device 402 .
- the proximity zones 470 may include the area in front of the A/V recording and communication device 402 , such as the field of view of the A/V recording and communication device 402 .
- the proximity zone 470 may be defined by a street or neighborhood, such that when the client device 407 enters the proximity zone 470 (e.g., enters the street or neighborhood), the client device 407 may be able to transmit the access request 475 to the A/V recording and communication device 402 .
- the process 2800 establishes a connection with the A/V recording and communication device 402 .
- the client device 407 may establish the connection with the A/V recording and communication device 402 over the network (Internet/PSTN) 410 and/or the user's network 408 , as described above.
- the client device 407 may receive network credentials for the user's network 408 (e.g., from the backend server 430 ) such that the client device 407 can connect to the user's network 408 to communicate with the A/V recording and communication device 402 .
- the client device 407 may be granted unsecured access to the user's network 408 .
- the client device 407 may receive temporary network credentials for the user's network 408 that expire at the expiration of the connection/communication between the client device 407 and the A/V recording and communication device 402 .
- the A/V recording and communication device 402 may generate an ad hoc network, for example, and the client device 407 may receive the network credentials of the ad hoc network and connect directly to the A/V recording and communication device 402 over the ad hoc network.
- the client device 407 may communicate to the A/V recording and communication device 402 using the backend server 430 such that the backend server 430 acts as an intermediary between the client device 407 and the A/V recording and communication device 402 .
- the client device 407 may be authenticated by the A/V recording and communication device 402 (or the backend server 430 ). In such embodiments, the client device 407 may transmit authentication information to the A/V recording and communication device 402 (and/or the backend server 430 ), and the authentication information may be compared to an authentication database (stored on the A/V recording and communication device and/or the backend server 430 ), for example, to determine if the client device 407 should be allowed access to the A/V recording and communication device 402 . For example, the ability to access A/V recording and communication devices 402 from the client device 407 may be a paid service, and the authentication may be to verify that the user of the client device 407 has paid for the service.
- client devices that are associated with an A/V recording and communication device may be allowed to access the A/V recording and communication device 402 .
- the authentication may include verifying that the client device 407 is associated with an A/V recording and communication device.
- the process 2600 in response to transmitting the access request 475 to the A/V recording and communication device 402 , receives from the camera 444 the image data 460 being recorded by the camera 444 in a field of view of the camera 444 .
- the process 2600 displays the image data 460 on the display 525 of the client device 407 .
- the process 2700 displays the device list 478 on the display 525 of the client device 407 , as illustrated in FIG. 42 .
- the device list 478 may include all of the devices to which the client device 407 may have access (e.g., the devices in whose proximity zones 470 the client device 407 is located).
- the user 712 of the client device 407 may be located on a street 762 , within the proximity zone 716 .
- the proximity zone 716 is an example of a shared proximity zone 716 .
- each of the A/V recording and communication devices 724 , 725 , 726 may share the proximity zone 716 .
- each of the A/V recording and communication devices 724 , 725 , 726 may have its own proximity zone 470 , or two or more of the A/V recording and communication devices 724 , 725 , 726 may share a proximity zone 470 while the other(s) A/V recording and communication devices 724 , 725 , 726 share a proximity zone 470 and/or have their own proximity zone 470 , for example.
- FIG. 1 In the example of FIG.
- the proximity zone 716 may include the A/V recording and communication device 724 , which may be a video doorbell located at the house 704 , the A/V recording and communication device 725 , which may be a security camera located at the house 730 , and the A/V recording and communication device 726 , which may be a video doorbell located at the house 720 .
- the device list 478 may include each of the A/V recording and communication devices 724 , 725 , 726 configured for access by the client device 407 .
- the device list 478 may include an access button 734 , 736 , 738 for each of the A/V recording and communication devices 724 , 725 , 726 , respectively.
- the access buttons 734 , 736 , 738 may be configured to allow the user 712 to provide an input (e.g., by the finger 744 of the user 712 , or another input device, as described above) to the access buttons 734 , 736 , 738 to request access (e.g., transmit the access request 475 ) to the corresponding A/V recording and communication device 724 , 725 , 726 .
- the device list 478 may also include an access all button 739 , which may allow the client device 407 to access each of the A/V recording and communication devices 724 , 725 , 726 (e.g., by transmitting the access request 475 to each of the devices 724 , 725 , 726 ).
- the client device 407 may display the image data 460 on the display 525 of the client device 407 for each of the A/V recording and communication devices 724 , 725 , 726 (e.g., in grid form).
- the user may be able to selectively view the image data 460 from one or more of the A/V recording and communication devices 724 , 725 , 726 as the user 712 desires (e.g., may toggle selection of different devices 724 , 725 , 726 ).
- the device list 478 may include an identification of the type of device each of the A/V recording and communication devices 724 , 725 , 726 is, and may further include the address where each of the A/V recording and communication devices 724 , 725 , 726 is located.
- the device list 478 may also include an indication of suspicious activity identified by one or more of the A/V recording and communication devices 724 , 725 , 726 , such as by providing the warning icon 746 when the burglar 740 (or another suspicious/dangerous person) is present (or has recently been present) in the field of the view of the A/V recording and communication device 726 (e.g., by including a time stamp).
- the identification of suspicious activity may be determined by the A/V recording and communication device 726 when analyzing the image data 460 generated by the camera of the A/V recording and communication device 726 , such as by using a computer vision process (e.g., facial recognition, facial detection, object recognition, etc.) or the like.
- a computer vision process e.g., facial recognition, facial detection, object recognition, etc.
- the process 2700 may continue to block B 600 of the process 2600 .
- the client device 407 may transmit the access request 475 to the A/V recording and communication device 726 in response to the user 712 providing a selection to the access button 738 on the device list 478 using his or her finger 744 , as illustrated in FIG. 42 .
- the user 712 may have selected to access the A/V recording and communication device 726 because the device list 478 included the warning icon 746 and the user 712 wanted to be notified of any potential danger in the neighborhood (e.g., on the street 762 ).
- the client device 407 may establish a connection to the A/V recording and communication device 726 .
- the process 2800 may continue to block B 602 of FIG. 26 .
- the client device 407 in response to transmitting the access request 475 (at block B 600 ), and in response to establishing connection/communication with the A/V recording and communication device 726 (at block B 612 ), the client device 407 may receive the image data 460 being recorded by the A/V recording and communication device 726 .
- the client device 407 may receive access to the previously recorded image data 460 from the A/V recording and communication device 726 .
- the client device 407 may be allowed access to the previous 10 seconds, 20 seconds, 30 seconds, or 1 minute of recorded image data 460 , for example.
- the user 712 of the client device 407 may be able to view the suspicious activity of the burglar 740 , or view better quality (e.g., closer, more focused) image of the burglar 740 , even if the burglar 740 is not currently in the field of view and/or not in close proximity to the A/V recording and communication device 726 (e.g., the burglar 740 has fertil the scene).
- This may also allow the user 712 to determine that the burglar 740 has a gun 742 and/or determine what direction the burglar 740 is traveling so that the user 712 may take a more appropriate action (e.g., hide, alert law enforcement, etc.).
- the client device 407 may display the image data 460 on the display 525 , as illustrated in the screenshot of FIG. 43 .
- the screenshot of FIG. 43 may be a screenshot of a GUI of a computer program application (e.g., a smart phone application).
- the image data 460 may include the burglar 740 and the gun 742 , allowing the user 712 to determine the reason for the warning icon 746 displayed on the device list 478 .
- the GUI may include the warning icon 746 , as illustrated in FIG. 43 .
- the GUI may also include an identification of the type of device that the A/V recording and communication device 726 is, and may further include the address where the device 726 is located.
- a recording status indicator 745 may also be displayed on the display 525 to provide an indication of whether the image data 460 is live or pre-recorded, for example.
- the GUI may also include an action button 750 .
- the action button 750 (e.g., when selected) may provide the user 712 with a list of actions 758 from which the user 712 may be able to select.
- the list of actions 758 may include a use speaker button 752 , a sound alarm button 754 , a notify police button 756 , and/or other buttons corresponding to different actions for the user 712 .
- the use speaker button 752 may enable the user 712 to speak through the speaker of the A/V recording and communication device 726 , such as to communicate with and/or scare off the burglar 740 , for example.
- the sound alarm button 754 may trigger an audible and/or visible alarm at the A/V recording and communication device 726 .
- the notify police button 756 may send a notification to law enforcement and/or initiate a call between the user 712 and law enforcement.
- the notify police button 756 may also trigger the A/V recording and communication device 726 to transmit the image data 460 to law enforcement, as described above.
- the GUI may also include control features for controlling the image data 460 , such as a play button 768 , a pause button 788 , a return button 790 , a fast forward button 792 , and/or other buttons.
- the return button 790 (e.g., when selected) may provide a return button list 781 for allowing the user 712 to select an amount of time to go back in the image data 460 and/or a specific point in the image data 460 .
- the user 712 may be able to select 10 seconds 780 or 30 seconds 782 to go back 10 seconds or 30 seconds in the image data 460 , respectively.
- the return button list 781 may also include a person present button 784 .
- the person present button 784 may go back to in the image data 460 to when a person is present (e.g., detected by the A/V recording and communication device 726 ), such as when the burglar 740 was first detected, when the burglar 740 is facing the camera, and/or at any time that the burglar is in the field of view of the A/V recording and communication device 726 .
- the A/V recording and communication device 726 may use computer vision or the like, as described above, to determine when the burglar 740 is present and/or to determine the position of the burglar 740 with respect to the A/V recording and communication device 726 (e.g., when the burglar 740 is facing the A/V recording and communication device).
- FIG. 29 is a flowchart illustrating a process for accessing cameras of A/V recording and communication devices based on location according to various aspects of the present disclosure.
- the process 2900 may be similar to the process 2600 , except in the process 2900 the A/V recording and communication device 402 transmits the access request 474 .
- the processes 2900 and 2600 may be combined such that both the client device 407 and the A/V recording and communication device 402 may transmit the access requests 474 , 475 .
- the client device 407 may periodically determine if any A/V recording and communication devices are available for access and transmit the access request 475 , and the A/V recording and communication device 402 may periodically determine if any client devices are available for access and transmit the access request 474 .
- the client device 407 may primarily transmit the access request 475 , and the A/V recording and communication device 402 may only determine if any client devices are available and transmit the access request 474 in response to a suspicious activity warning/flag (e.g., after detecting that the burglar 740 is present).
- the processes 3200 and 3600 may be combined.
- the processes 3800 and 3900 may be combined.
- the process 2900 in response to entering a proximity zone of an A/V recording and communication device, receives, from the A/V recording and communication device, an access request for allowing a client device to access a camera of the A/V recording and communication device.
- the processor 534 of the client device 407 receives, using the communication module 530 , the access request 474 from the A/V recording and communication device 402 for allowing the client device 407 access to the A/V recording and communication device 402 .
- the A/V recording and communication device 402 may determine that the client device 407 has entered the proximity zone 470 (e.g., by comparing the location data 477 to the proximity zone 470 ) and transmit the access request 474 .
- the backend server 430 may compare the location data 477 to the proximity zone 470 and transmit the access request 474 to the client device 407 (and/or forward the access request 474 from the A/V recording and communication device 402 ).
- the process 2900 transmits, by the processor using the communication module, to the A/V recording and communication device, an acceptance of the access request.
- the processor 534 may transmit, using the communication module 530 , an acceptance of the access request 474 to the A/V recording and communication device 402 .
- the client device 407 may display the device list 478 , and the user 712 of the client device 407 may select the A/V recording and communication device 402 from the device list 478 as an acceptance of the access request 474 .
- the client device 407 may transmit the acceptance.
- the client device 407 may, depending on the settings of the client device 407 , automatically accept access requests 474 . For example, if the access request 474 includes a suspicious activity warning/flag (e.g., if the access request 474 is transmitted in response to suspicious behavior detected by the A/V recording and communication device 402 and/or the backend server 430 in response to analyzing the image data 460 , such as if the image data 460 includes the burglar 740 ), the client device 407 may be programmed to automatically transmit an acceptance to the access request 474 .
- a suspicious activity warning/flag e.g., if the access request 474 is transmitted in response to suspicious behavior detected by the A/V recording and communication device 402 and/or the backend server 430 in response to analyzing the image data 460 , such as if the image data 460 includes the burglar 740
- the client device 407 may be programmed to automatically transmit an acceptance to the access request 474 .
- the process 2900 in response to the transmitting the acceptance, receives, by the processor using the communication module, from the camera, image data being recorded in a field of view of the camera.
- the processor 534 in response to transmitting the acceptance, may receive, using the communication module 530 , from the camera 444 , the image data 460 being recorded by the camera 444 in a field of view of the camera 444 .
- This process may be similar to that of block B 602 of FIG. 26 , described above.
- the process 2900 displays, by the processor on a display, the image data.
- the processor 534 displays the image data 460 on the display 525 .
- This process may be similar to that of block B 604 of FIG. 26 , described above.
- FIG. 30 is a flowchart illustrating a process for accessing cameras of A/V recording and communication devices based on location according to various aspects of the present disclosure.
- the process 3000 may continue from block B 616 of FIG. 29 .
- the process 3000 in response to receiving an access request, displays, by a processor on a display, a list of devices configured for access by a client device, the list of devices including an A/V recording and communication device.
- the processor 534 may display the device list 478 on the display 525 of the client device 407 , where the device list 478 may include the A/V recording and communication device 402 .
- the process 3000 receives, by the processor, an input including a selection of the A/V recording and communication device from the list of devices, the input including an acceptance of the access request.
- the processor 534 may receive an input including a selection of the A/V recording and communication device 402 from the device list 478 , where the input includes an acceptance of the access request 474 .
- the user 712 may make a selection of one or more of the A/V recording and communication devices 724 , 725 , 726 from the device list 478 , where the selection includes an acceptance of the access request 474 transmitted by the corresponding A/V recording and communication device 724 , 725 , 726 .
- the device list 478 may include the A/V recording and communication devices 724 , 725 , 726 that transmitted the access requests 474 , and/or the A/V recording and communication devices 724 , 725 , 726 that are available for access by the client device 407 but have not transmitted the access request 474 (e.g., where the client device 407 must transmit the access request 475 ).
- selecting the access button 734 , 736 , 738 may include an acceptance of the access request 474 .
- selecting the access button 734 , 736 , 738 may include transmitting the access request 475 from the client device 407 to the corresponding A/V recording and communication device 724 , 725 , 726 .
- the process 3000 may continue to block B 618 of FIG. 29 .
- FIG. 31 is a flowchart illustrating a process for accessing cameras of A/V recording and communication devices based on location according to various aspects of the present disclosure.
- the process 3100 may continue from block B 618 of FIG. 29 .
- the process 3100 may establish, by a processor using a communication module, a connection to an A/V recording and communication device.
- the processor 534 of the client device 407 may establish a connection to the A/V recording and communication device 402 using the communication module 530 .
- This process may be similar to that of block B 612 of FIG. 28 , described above.
- the process 3100 may continue to block B 620 of FIG. 29 .
- FIG. 32 is a flowchart illustrating a process for accessing cameras of A/V recording and communication devices based on location according to various aspects of the present disclosure.
- the process 3200 may be similar to the process 2900 of FIG. 29 , except the process 3200 may be directed to the processes of the A/V recording and communication device 402 while the process 2900 may be directed to the processes of the client device 407 .
- the process 3200 may transmit the access request 474
- the client device 407 may receive the access request 474 from the A/V recording and communication device 402 .
- the process 3200 in response to detecting the presence of a client device in a proximity zone of an A/V recording and communication device, transmits, by a processor using the communication module, an access request to the client device for allowing the client device to access the camera.
- the A/V recording and communication device 402 may transmit, by the processor 452 using the communication module 450 , the access request 474 to the client device 407 for allowing the client device 407 access to the camera 444 (and/or other features of the A/V recording and communication device 402 ).
- the access request 474 may be transmitted over the network (Internet/PSTN) 410 and/or the user's network 408 .
- the access request 474 may be transmitted to the client device 407 and/or to the backend server 430 and the backend server 430 may forward the access request 474 to the client device 407 .
- the access request may be transmitted directly to the client device 407 over an ad hoc network generated by the A/V recording and communication device 402 .
- the process 3200 in response to transmitting the access request, receives, by the processor using the communication module, an acceptance of the access request from the client device.
- the processor 452 using the communication module 450 may receive the acceptance of the access request 474 from the client device 407 in response to transmitting the access request 474 .
- the acceptance may be received over the network (Internet/PSTN) 410 and/or the user's network 408 .
- the acceptance may be received from the client device 407 and/or from the backend server 430 after the backend server 430 receives the acceptance from the client device 407 .
- the acceptance may be received directly by the A/V recording and communication device 402 over the ad hoc network.
- the process 3200 in response to receiving the acceptance, transmits, by the processor using the communication module, image data being recorded by the camera in a field of view of the camera.
- the processor 452 using the communication module 450 may transmit the image data 460 being recorded by the camera 444 in field of view of the camera 444 .
- the image data 460 may be transmitted to the client device 407 over the network (Internet/PSTN) 410 and/or the user's network 408 (in some embodiments, via the backend server 430 ). In other embodiments, as described above, the image data 460 may be transmitted directly to the client device 407 over the ad hoc network generated by the A/V recording and communication device 402 .
- FIG. 33 is a flowchart illustrating a process for accessing cameras of A/V recording and communication devices based on location according to various aspects of the present disclosure.
- the process 3200 detects, by a processor using a communication module, the presence of a client device in a proximity zone of an A/V recording and communication device.
- the processor 452 using the communication module 450 may detect the presence of the client device 407 in the proximity zone 470 of the A/V recording and communication device 402 .
- the A/V recording and communication device 402 may listen, using the communication module 450 , for incoming communication signals 481 of the client device 407 (e.g., that may be transmitted by the client device 407 at an interval, such as every 10 seconds, every 20 seconds, etc.).
- the communication signals 481 may include the location data 477 of the client device 407 for comparison with the proximity zone 470 .
- the A/V recording and communication device 402 may transmit the communication signals 479 (e.g., at interval, such as every 10 seconds, every 20 seconds, etc.), and the client device 407 may listen for the communication signals 479 .
- the client device 407 may transmit the communication signals 481 including the location data 477 for the A/V recording and communication device 402 to compare to the proximity zone 470 .
- the process 3300 may continue to block B 646 .
- the client device 407 may transmit the location data 477 to the backend server 430 and the backend server 430 may determine, and/or forward the location data 477 to the A/V recording and communication device 402 for determining, if the client device 407 within the proximity zone 470 .
- the process 3300 may continue to block B 638 of FIG. 32 .
- FIG. 34 is a flowchart illustrating a process for accessing cameras of A/V recording and communication devices based on location according to various aspects of the present disclosure.
- the process 3400 may continue from block B 640 of FIG. 32 .
- the process 3400 may establish, by a processor using a communication module, a connection to a client device.
- the processor 452 of the A/V recording and communication device 402 using the communication module 450 , may establish a connection/communication to the client device 407 .
- This process may be similar to that of block B 634 of FIG. 3100 and/or block B 612 of FIG. 28 , described above.
- the process 3400 may continue to block B 642 of FIG. 32 .
- FIG. 35 is a flowchart illustrating a process for accessing cameras of A/V recording and communication devices based on location according to various aspects of the present disclosure.
- the process 3500 generates, by a processor, a proximity zone for detecting the presence of one or more client devices within a proximity zone.
- the processor 452 may generate the proximity zone 470 for detecting the presence of one or more client devices (e.g., the client device 407 ).
- the proximity zone 470 as described above, may be based on the settings of the A/V recording and communication device 402 .
- the proximity zone 470 may be a default size and shape, and the generation of the proximity zone 470 may include a determination of the location data 476 (e.g., geographical coordinates) relating to the default proximity zone 470 at the location of the A/V recording and communication device 402 .
- the generating of the proximity zone 470 may include determining the location data 476 (e.g., geographical coordinates) within the 300-foot radius of the A/V recording and communication device 402 .
- the proximity zone 470 may be user created (e.g., by selecting a size, setting a region, drawing the proximity zone 470 over a map on the display, etc.).
- the A/V recording and communication device 402 may generate the proximity zone 470 , similar to described above, by determining the location data 476 (e.g., geographical coordinates) of the proximity zone 470 .
- the location data 476 of the proximity zone 470 may then be compared to the location data 477 (e.g., geographical coordinates from a GPS or) of the client device 407 to determine if the client device 407 is within the proximity zone 470 .
- the backend server 430 may transmit the proximity zone 470 to the A/V recording and communication device 402 .
- the A/V recording and communication device 402 may receive the location data 476 defining the proximity zone 470 , and generating the proximity zone 470 may include updating the settings of the A/V recording and communication device 402 with the location data 476 including the proximity zone 470 received from the backend server 430 .
- the A/V recording and communication device 402 may determine whether the client device 407 is within the proximity zone 470 .
- the location data 477 may include (in addition to or in lieu of GPS data) cellular data, such as a Mobile Country Code (MCC), a Mobile Network Code (MNC), a Location Area Code (LAC), and a Cell ID (CID).
- MCC Mobile Country Code
- MNC Mobile Network Code
- LAC Location Area Code
- CID Cell ID
- the cellular data may be used to determine the location data 477 of the client device 407 , such as geographical coordinates, which may be compared to the location data 476 of the proximity zone 470 to determine if the client device 407 is within the proximity zone 470 .
- the communication signals 479 , 481 may be used to define the proximity zone 470 .
- the location data 477 may include Wi-Fi Positioning System (WPS) data, and the WPS data may be used to determine a location of the client device 407 . The location of the client device 407 may then be compared to the proximity zone 470 to determine if the client device 407 is within the proximity zone 470 .
- the location data 477 may include Bluetooth and/or ZigBee data, and the Bluetooth and/or Zigbee data may be used to determine a location of the client device 407 . The location of the client device 407 may then be compared to the proximity zone 470 to determine if the client device 407 is within the proximity zone 470 .
- the proximity zone 470 may be defined by signal strength of the Wi-Fi, Bluetooth, ZigBee and/or other signal type signals, rather than by geographical coordinates.
- the signal strength may be measured as the Received Signal Strength Indication (RSSI) of the Wi-Fi, Bluetooth, ZigBee, and/or other signal type signals.
- RSSI Received Signal Strength Indication
- the proximity zone 470 may then be defined (e.g., user defined or by default) by the RSSI values for the Wi-Fi, Bluetooth, ZigBee, and/or other signal type signals that may render a determination that a client device is within the proximity zone 470 (e.g., Bluetooth RSSI greater than ⁇ 65 dBm on a ⁇ 100-0 scale). As such, when the RSSI is within the RSSI values for the proximity zone 470 , the client device 407 is determined to be within the proximity zone 470 .
- the A/V recording and communication device 402 may transmit the Wi-Fi, Bluetooth, ZigBee, and/or other signal type signals (e.g., the communication signals 479 , 481 ) using a Wi-Fi, Bluetooth, ZigBee, and/or other signal type transmitter (e.g., a transceiver, a transmitter, or a transmitter-receiver), for example, and the client device 407 may receive the signals (e.g., via a receiver, a transceiver, or a transmitter-receiver) and measure the RSSI values of the signals.
- signal type signals e.g., the communication signals 479 , 481
- a Wi-Fi, Bluetooth, ZigBee, and/or other signal type transmitter e.g., a transceiver, a transmitter, or a transmitter-receiver
- the client device 407 may receive the signals (e.g., via a receiver, a transceiver, or a transmitter-receiver)
- the client device 407 may transmit the RSSI values to the A/V recording and communication device 402 and/or the backend server 430 to be compared to the RSSI values of the proximity zone 470 to determine if the client device 407 is within the proximity zone 470 .
- the client device 407 may transmit the Wi-Fi, Bluetooth, ZigBee, and/or other signal type signals using a Wi-Fi, Bluetooth, ZigBee, and/or other signal type transmitter (e.g., a transceiver, a transmitter, or a transmitter-receiver), for example, and the A/V recording and communication device 402 may receive the signals (e.g., via a receiver, a transceiver, or a transmitter-receiver) and measure the RSSI values of the signals, and analyze the RSSI values locally on the A/V recording and communication device 402 and/or transmit the RSSI values to the backend server 430 to be compared to the RSSI values of the proximity zone 470 to determine if the client device 407 is within the proximity zone 470 .
- a Wi-Fi e.g., Bluetooth, ZigBee, and/or other signal type transmitter
- the A/V recording and communication device 402 may receive the signals (e.g., via a receiver, a transce
- the proximity zone 470 may be determined by the backend server 430 and transmitted to the A/V recording and communication device 402 .
- the proximity zone 470 received from the backend server 430 may include the RSSI values that define the proximity zone 470 , for example, and the A/V recording and communication device 402 may update the settings of the device 402 to reflect the received proximity zone 470 information.
- the location data 477 may be based on active reflector technology, where the active reflector technology may be used to determine a distance of the client device 407 from the A/V recording and communication device 402 , and based on the distance, determine if the client device 407 is within the proximity zone 470 .
- the proximity zone 470 may be defined by a diameter (e.g., 400 feet), and the active reflector technology may be used to determine the estimated location data 477 (e.g., distance) of the client device 407 to determine if the client device 407 is within the proximity zone 470 .
- the client device 407 and/or the A/V recording and communication device 402 may include ZigBee transceivers.
- the process may continue to block B 638 of FIG. 32 or block B 644 of FIG. 33 .
- FIGS. 32-35 may be implemented in a variety of embodiments, including those discussed below. However, the below-detailed embodiments are not intended to be limiting, and are provided merely as example embodiments of the present disclosure. Other embodiments similar to those outlined herein may also fall within the scope of the present disclosure.
- the A/V recording and communication device 402 may generate one of the proximity zones 706 , 708 , 710 for detecting the presence of a client device within (at block B 654 of FIG. 35 ).
- the A/V recording and communication device 402 may generate the proximity zones 706 , 708 , 710 according to any of the methods described herein and/or may receive the location data 476 of the proximity zone 470 from the backend server 430 .
- the A/V recording and communication device 402 may detect the client device 407 within the proximity zone 706 , 708 , 710 (at block B 644 of FIG. 33 ) and transmit the access request 474 to the client device 407 (at block B 638 of FIG. 32 ).
- the A/V recording and communication device 402 may listen for communication signals 481 from the client device 407 (and/or other client devices).
- the A/V recording and communication device 402 may listen at a set interval, such as every second, every 5 seconds, every 10 seconds, or every 30 seconds, for example.
- the communication signals 481 may include the location data 477 of the client device 407 for the A/V recording and communication device 402 to compare against the proximity zone 470 .
- the A/V recording and communication device 402 may communicate with the backend server 430 to determine if the client device 407 (and/or other client devices 407 ) have location data 477 indicative of the client device 407 being within the proximity zone 470 , and in response to determining that the client device 407 is within the proximity zone, may transmit the access request 474 to the client device 407 (in some embodiments, via the backend server 430 ).
- the A/V recording and communication device 402 may communicate with the backend server 430 to determine if any client devices are within the proximity zone 470 at an interval, such as every second, every 5 seconds, every 10 seconds, every 30 seconds, or at each router check-in, for example.
- the A/V recording and communication device 402 may receive an acceptance of the access request 474 (at block B 640 of FIG. 32 ). For example, the user 712 of the client device 407 may select the A/V recording and communication device 402 from the device list 478 . In response to receiving the acceptance, the A/V recording and communication device 402 may connect to the client device 407 (at block B 650 of FIG. 34 ). After establishing the connection, the A/V recording and communication device 402 may transmit the image data 460 to the client device 407 (at block B 642 of FIG. 32 ). The image data 460 may be transmitted over the user's network 408 and/or the network (Internet/PSTN) 410 to the client device 407 (in some embodiments, via the backend server 430 ).
- the A/V recording and communication device 726 may detect the suspicious activity of the burglar 740 carrying the gun 742 .
- the A/V recording and communication device 726 may determine (e.g., by detecting the client devices (at block B 644 of FIG. 33 ), by querying the backend processor 430 , etc.) if any client devices are within the proximity zone 716 in order to alert the users of the client devices of the suspicious behavior of the burglar 740 .
- the A/V recording and communication device 726 may determine that the client device 407 is within the proximity zone 470 .
- the A/V recording and communication device 726 may transmit the access request 474 to the client device 407 to allow the client device 407 to access the camera 444 (and/or prerecorded image data 460 ) of the A/V recording and communication device 726 (at block B 638 of FIG. 32 ).
- the access request 474 may be received by the client device 407 (e.g., at block B 616 of FIG. 29 ) and the client device 407 , based on the settings of the client application 540 , for example, may automatically accept the access request 474 based on the suspicious activity warning/flag included in the access request 474 ).
- the access request 474 may display as a notification on the display 525 of the client device 407 (e.g., a push notification), where the notification may include the suspicious activity warning/flag (e.g., “suspicious activity reported in your immediate vicinity, access video?”).
- the user 712 of the client device 407 may accept (e.g., at block B 618 of FIG. 29 ) the access request 474 (e.g., automatically, in response to interacting with the notification, by selecting the A/V recording and communication device 726 from the device list 478 of FIG. 42 , etc.).
- the A/V recording and communication device 726 may receive the acceptance to the access request 474 from the client device 407 (at block B 640 ).
- the A/V recording and communication device 402 (and/or the backend server 430 ) may transmit the image data 460 of the burglar 740 to the client device 407 (at block B 642 ).
- the client device 407 may automatically accept the access request 474 , and may automatically display the image data 460 on the display 525 of the client device 407 in order to warn the user 712 of the suspicious activity.
- the image data 460 may be transmitted live, such that the user 712 of the client device 407 can see the current field of view of the camera 444 of the A/V recording and communication device 726 .
- the image data 460 transmitted to the client device 407 may be the pre-recorded image data 460 including the burglar 740 .
- the user 712 may be able to see the appearance (e.g., physical appearance, identity, clothing, etc.) of the burglar 740 and/or the gun 742 being carried by the burglar 740 and determine that the burglar 740 is in fact suspicious.
- the user 712 may be more likely to hide, flee, alert law enforcement, or take other appropriate actions based on the knowledge of the burglar's 740 presence.
- the user 712 may access the device list 478 after being notified of the burglar 740 , and determine if any of the other A/V recording and communication devices in the proximity zone 716 have identified suspicious activity (e.g., the burglar 740 ), in order to determine the safest exit route and/or hiding places, for example.
- the warning icons 746 may include a time stamp, such that the user 712 can view when the suspicious activity was detected by the A/V recording and communication devices 724 , 725 , 726 .
- the warning icon 746 may have a time stamp of 8:05 PM, and another warning icon 746 (not shown) may be included next to the A/V recording and communication device 724 on the device list 478 with a time stamp of 8:15 PM.
- the user 712 may be able to determine that the burglar 740 may be moving, from left to right, down the street 762 and take appropriate action.
- the A/V recording and communication devices 724 , 725 , 726 may use computer vision (e.g., facial recognition, facial detection, object recognition, etc.) to determine that the suspicious activity is caused by the same person(s) (e.g., the burglar 740 ) and provide an indication of this determination to the user 712 of the client device 407 (e.g., on the device list 478 ).
- computer vision e.g., facial recognition, facial detection, object recognition, etc.
- FIG. 36 is a flowchart illustrating a process for accessing cameras of A/V recording and communication devices based on location according to various aspects of the present disclosure.
- the process 3600 may be similar to the process 2600 of FIG. 26 , except the process 3600 may be directed to the processes of the A/V recording and communication device 402 while the process 2600 may be directed to the processes of the client device 407 .
- the client device 407 may transmit the access request 475
- the A/V recording and communication device 402 may receive the access request 475 from the client device 407 .
- the process 3600 in response to a client device entering a proximity zone of an A/V recording and communication device 402 , receives, by a processor using a communication module, an access request from the client device for allowing the client device access to a camera.
- the processor 452 of the A/V recording and communication device 402 using the communication module 450 may receive the access request 475 from the client device 407 for allowing the client device 407 access to the camera 444 of the A/V recording and communication device 402 .
- the user of the client device 470 may receive a notification that the user can access (e.g., is within the proximity zone 470 of the A/V recording and communication device 402 ) the A/V recording and communication device 402 (e.g., in the device list 478 ).
- the user may request access and the client device 407 may transmit the access request 475 to the A/V recording and communication device 402 .
- the A/V recording and communication device 402 may receive the access request 475 .
- the process 3600 in response to receiving the access request, accepts, by the processor, the access request.
- the processor 452 of the A/V recording and communication device 402 may accept the access request 475 .
- the A/V recording and communication device 402 may receive the location data 477 of the client device 407 (e.g., along with the access request 475 ) and may compare the location data 477 to the proximity zone 470 to determine whether the client device 407 is within the proximity zone 470 .
- the A/V recording and communication device 402 may accept the access request 475 .
- the user/owner of the A/V recording and communication device 402 may receive a notification of the access request 475 from the A/V recording and communication device 402 (in some embodiments via the backend server 430 ), and may allow access or deny access. If the user/owner allows access, then the A/V recording and communication device 402 may accept the access request 475 .
- the process 3600 in response to the acceptance, transmits, by the processor using the communication module, image data being recorded by the camera to the client device.
- the processor 452 of the A/V recording and communication device using the communication module 450 , may transmit the image data 460 being recorded by the camera 444 to the client device 407 .
- This process may be similar to that of block B 642 of FIG. 32 , described above.
- FIG. 37 is a flowchart illustrating a process for accessing cameras of A/V recording and communication devices based on location according to various aspects of the present disclosure.
- the process 3700 may continue from block B 660 of FIG. 36 .
- the process 3700 establishes, by a processor using a communication module, a connection to a client device.
- the processor 452 of the A/V recording and communication device 402 using the communication module 450 , may establish a connection to/communication with the client device 407 .
- This process may be similar to that of block B 650 of FIG. 34 , described above.
- the process 3700 may continue to block B 662 of FIG. 36 .
- FIG. 38 is a flowchart illustrating a process for accessing cameras of A/V recording and communication devices based on location according to various aspects of the present disclosure.
- the process 3800 may be similar to the process 2600 of FIG. 26 and the process 3600 of FIG. 36 , except the process 3800 may be directed to the processes of the backend server 430 while the process 2600 may be directed to the processes of the client device 407 and the process 3600 may be directed to the process of the A/V recording and communication device 402 .
- the client device 407 may transmit the access request 475
- the backend server 430 may receive the access request 475 from the client device 407 , and at block B 672 , transmit the access request 475 to the A/V recording and communication device 402 .
- the A/V recording and communication device 402 may receive the access request 475 from the backend server 430 .
- the process 3800 may be similar to the process 2900 of FIG. 29 and the process 3200 of FIG. 32 , except the process 3800 may be directed to the processes of the backend server 430 while the process 2900 may be directed to the processes of the client device 407 and the process 3200 may be directed to the process of the A/V recording and communication device 402 .
- the A/V recording and communication device 402 may transmit the access request 474
- the backend server 430 may receive the access request 474 from the A/V recording and communication device 402 , and at block B 672 , transmit the access request 474 to the client device 407 .
- the client device 407 may receive the access request 474 from the backend server 430 .
- the process 3800 in response to a client device entering a proximity zone of an A/V recording and communication device, receives, from the client device and/or the A/V recording and communication device, an access request for allowing the client device access to the camera of the A/V recording and communication device.
- the processor 502 of the backend server 430 may receive, from the client device 407 and/or the A/V recording and communication device 402 , the access request 474 , 475 for allowing the client device 407 access to the camera 444 of the A/V recording and communication device 402 .
- the backend server 430 may receive the access request 474 , 475 over the network (Internet/PSTN) 410 using the network interface 520 , for example.
- the access request 474 , 475 may be received in the output signal 466 , 467 from the A/V recording and communication device 402 and/or the client device 407 .
- the access request 475 may further include the location data 477 of the client device 407 .
- the process 3800 in response to receiving the access request, transmits the access request to the A/V recording and communication device and/or the client device.
- the processor 502 of the backend server 430 may transmit the access request 474 , 475 to the A/V recording and communication device 402 and/or the client device 407 .
- the backend server 430 may receive an acceptance to the access request 474 from the client device 407 and transmit the acceptance to the A/V recording and communication device 402 , prior to proceeding to block B 674 , discussed below.
- the process 3800 in response to transmitting the access request, receives, from the A/V recording and communication device, image data being recorded by the camera of the A/V recording and communication device in a field of view of the camera.
- the processor 502 of the backend server 430 in response to transmitting the access request 474 , 475 (and, in some embodiments receiving the acceptance of the access request 474 from the client device 407 ), the processor 502 of the backend server 430 , using the network interface 520 , may receive the image data 460 being recorded by the camera 444 of the A/V recording and communication device 402 .
- the process 3800 in response to receiving the image data, transmits, to the client device, the image data.
- the processor 502 of the backend server 430 may transmit the image data 460 to the client device 407 .
- FIG. 38 may be implemented in a variety of embodiments, including those discussed below. However, the below-detailed embodiments are not intended to be limiting, and are provided merely as example embodiments of the present disclosure. Other embodiments similar to those outlined herein may also fall within the scope of the present disclosure.
- the backend server 430 may receive the access request 474 from the A/V recording and communication device 402 and/or the access request 475 from the client device 407 in response to the user 712 entering the one of the proximity zones 706 , 708 , 710 .
- the client device 407 and/or the A/V recording and communication device 402 may transmit the access request 474 , 475 to the backend server 430 , and the backend server 430 may receive the access request 474 , 475 (at block B 670 ).
- the client device 407 may receive a notification that the A/V recording and communication device 402 is available for access in response to entering the proximity zone 470 , and the user 712 may elect to access the A/V recording and communication device 402 .
- the notification may be received from the backend server 430 and/or the A/V recording and communication device 402 .
- the backend server 430 may transmit the access request 474 to the client device 407 over the network (Internet/PSTN) 410 .
- the backend server 430 may receive an acceptance to the access request 474 from the client device 407 (e.g., based on a selection of the device 402 from the device list 478 ) over the network (Internet/PSTN) 410 , and transmit the acceptance to the A/V recording and communication device 402 .
- the backend server 430 may transmit the access request 475 to the A/V recording and communication device 402 over the network (Internet/PSTN) 410 and/or the user's network 408 .
- the backend server 430 may receive the image data 460 being recorded by the camera 444 of the A/V recording and communication device 402 . In response to receiving the image data 460 , at block B 676 of the process 3800 , the backend server 430 may transmit the image data 460 to the client device 407 .
- FIG. 39 is a flowchart illustrating a process for accessing cameras of A/V recording and communication devices based on location according to various aspects of the present disclosure.
- the process 3900 receives, from an A/V recording and communication device, first location data including a proximity zone.
- the processor 502 of the backend server 430 may receive, using the network interface 520 , the location data 476 including the proximity zone 470 from the A/V recording and communication device 402 .
- the processor 502 of the backend server 430 may receive the location data 476 over the network (Internet/PSTN) 410 and/or the user's network 408 .
- the location data 476 may include the location of the A/V recording and communication device 402 based on GPS data, known location data of the access point (e.g., router) that the A/V recording and communication device 402 is connected to for access to the user's network 408 , Internet Protocol (IP) address data, WPS data, or the like.
- IP Internet Protocol
- the location data 476 may include the location data 476 for the proximity zone 470 .
- the proximity zone 470 may be defined by all of the geographical coordinates within the proximity zone 470 such that the location data 477 (e.g., geographical coordinates) of the client device 407 (received at block B 680 ) may be compared to the geographical coordinates of the proximity zone 470 to determine if the client device 407 is within the proximity zone 470 .
- the location data 477 e.g., geographical coordinates
- the client device 407 received at block B 680
- the backend server 430 may only receive the location data 476 from the A/V recording and communication device 402 , and the processor 502 may generate the proximity zone 470 based on the location data 476 and the settings (e.g., user settings, default settings, etc.) relating to the proximity zone 470 .
- the proximity zone 470 may be defined by a 500-foot radius around the A/V recording and communication device 402 .
- the backend server 430 may receive the location data 476 of the A/V recording and communication device 402 and determine the location data 476 (e.g., the geographical coordinates) that defines a circle having a 500-foot radius around the A/V recording and communication device 402 , and this location data 476 may be stored on the backend server 430 as the proximity zone 470 .
- the location data 476 e.g., the geographical coordinates
- the process 3900 receives, from a client device, second location data including a location of the client device.
- the processor 502 of the backend server 430 may receive, using the network interface 520 , the location data 477 of the client device 407 .
- the location data 477 may be received by the backend server 430 over the network (Internet/PSTN) 410 .
- the location data 477 may include the geographical coordinates of the location of the client device 407 .
- the location data 477 may be based on GPS data, Cell ID (as described above), or the like.
- the proximity zone 470 may be defined by the signal strength of the communication signals 479 , 481 , such as the RSSI values of the communication signals 479 , 481 .
- the client device 407 and/or the A/V recording and communication device 402 may measure the RSSI values of the communication signals 479 , 481 received from the other device (e.g., the client device 407 may measure the RSSI values of the communication signals 479 received from the A/V recording and communication device 402 ) and transmit the RSSI values to the backend server 430 .
- the location data 476 , 477 may include the RSSI values, and the location data 476 , 477 may be received by the backend server 430 from the A/V recording and communication device 402 and/or the client device 407 .
- the proximity zone 470 may be defined by a threshold RSSI value for the signal strength of the communication signals 479 , 481 .
- the proximity zone 470 may be defined by ZigBee RSSI values greater than ⁇ 80 dBm (e.g., on a ⁇ 100-0 scale), such that if the RSSI values for ZigBee communication signals 479 , 481 are greater than ⁇ 80 dBm (e.g., ⁇ 60 dBm), the client device 407 may be determined to be within the proximity zone 470 .
- the process 3900 in response to receiving the first location data and the second location data, analyzes the first and the second location data to determine whether the client device is within the proximity zone.
- the processor 502 of the backend server 430 may analyze the location data 477 of the client device and the location data 476 of the proximity zone 470 to determine whether the client device 407 is within the proximity zone 470 .
- the processor 502 may compare the geographical coordinates from the location data 477 of the client device 407 to the geographical coordinates that define the proximity zone 470 to determine whether the client device 407 is within the proximity zone 470 .
- the client device 407 may be determined that the client device 407 is within the proximity zone 470 .
- the process 3900 based on the determination of whether the client device is within the proximity zone (at block B 682 ), transmits, to the client device, an access request for allowing the client device to access the camera of the A/V recording and communication device.
- the processor 502 of the backend server 430 may transmit, using the network interface 520 , the access request 474 to the client device 407 (e.g., over the network (Internet/PSTN) 410 ) for allowing the client device 407 to access the camera 444 (and/or the image data 460 ) of the A/V recording and communication device 402 .
- the access request 474 may be received by the client device 407 , similar to that of block B 616 of FIG. 29 , described above.
- the client device 407 may provide a notification to the user of the client device 407 (e.g., by listing the A/V recording and communication device 402 in the device list 478 ) that the client device 407 may access the A/V recording and communication device 402 .
- the process 3900 in response to the transmitting the access request, receives, from the client device, an acceptance of the access request.
- the processor 502 of the backend server 430 may receive the acceptance of the access request 474 (e.g., over the network (Internet/PSTN) 410 ).
- the client device 407 may provide a notification to the user of the client device 407 (e.g., in the device list 478 ), that the A/V recording and communication device 402 is accessible by the client device 407 .
- the user of the client device 407 may select the A/V recording and communication device 402 from the device list 478 , and the client device 407 may transmit the acceptance.
- the access request 474 may not be transmitted to the client device 407 (at block B 684 ) and as a result, an acceptance to the access request 474 may not be received (at block B 686 ). In such embodiments, the process 3900 may continue directly to block B 688 after block B 688 .
- the location data 477 received from the client device 407 may also include the access request 475 from the client device 407 .
- the access request 475 may be a general access request from the client device 407 , such that the user of the client device 407 may want to connect/communicate with at least one A/V recording and communication device (which may include the A/V recording and communication device 402 ).
- the processor 502 of the backend server 430 may determine if the client device 407 , based on the location data 477 , is within the proximity zone 470 of any A/V recording and communication devices, such as the A/V recording and communication device 402 .
- the user of the client device 407 may have been provided with a notification that the A/V recording and communication device 402 is accessible (e.g., that the client device 407 is within the proximity zone 470 of the A/V recording and communication device 402 ) and, in response to the user's input to access the A/V recording and communication device 402 , the client device 407 may transmit the access request 475 .
- the analyzing of the location data 476 and the location data 477 may be a verification that the client device 407 is within the proximity zone 470 , and, after the verification, the process 3900 may continue to block B 688 .
- the process 3900 in response to receiving the acceptance, retrieves, from the A/V recording and communication device, image data being recorded by the camera in a field of view of the camera.
- the processor 502 of the backend server 430 may retrieve the image data 460 recorded by the camera 444 in a field of view of the camera 444 .
- the image data 460 may be a live recording
- the backend server 430 may receive the live recording from the camera 444 over the network (Internet/PSTN) 410 using the network interface 520 .
- the image data 460 may be stored on the A/V recording and communication device 402 , and the backend server 430 may retrieve the image data 460 from the A/V recording and communication device 402 .
- the A/V recording and communication device 402 may be programmed to transmit the image data 460 to the backend server 430 each time the camera 444 records the image data 460 .
- the image data 460 recorded by the A/V recording and communication device 402 may already be stored on the backend server 430 , and the backend server 430 may retrieve the image data 460 from the non-volatile memory 506 , for example.
- the process 3900 in response to retrieving the image data, transmits the image data to the client device.
- the processor 502 of the backend server 430 may transmit the image data 460 to the client device 407 .
- the image data 460 may be transmitted over the network (Internet/PSTN) 410 .
- the client device 407 may receive the image data 460 and display a virtual representation of the image data 460 on the display 525 .
- FIG. 39 may be implemented in a variety of embodiments, including those discussed below. However, the below-detailed embodiments are not intended to be limiting, and are provided merely as example embodiments of the present disclosure. Other embodiments similar to those outlined herein may also fall within the scope of the present disclosure.
- the backend server 430 may receive the location data 476 from at least one of the A/V recording and communication device 724 , 725 , 726 (at block B 678 ). In some embodiments, the backend server 430 may receive the location data 476 from each of the A/V recording and communication devices 724 , 725 , 726 during each set-up/activation process of the devices 724 , 725 , 726 . In addition, the backend server 430 may receive the proximity zone 716 of each of the A/V recording and communication devices 724 , 725 , 726 and/or may generate the proximity zone 716 , as described above.
- the backend server 430 may receive the location data 477 of the client device 407 (at block B 680 ).
- the client device 407 (and/or other client devices) may transmit their location to the backend server 430 at an interval, such as every 10 seconds, every 20 seconds, every 30 seconds, or every minute, for example.
- the backend server 430 may receive the image data 460 from the A/V recording and communication devices 724 , 725 , 726 , and may determine if the image data 460 includes any suspicious activity (e.g., suspicious activity warnings/flags).
- the backend server 430 may analyze the location data 477 received from the client device 407 (and/or other client devices) to determine if the client device 407 is within the proximity zone 716 of the A/V recording and communication device 726 that generated the image data 460 including the suspicious activity (at block B 682 ). In response to determining that the client device 407 is within the proximity zone 716 , the backend server 430 may transmit the access request 474 to the client device 407 (at block B 684 ), as described above, and may receive the acceptance of the access request 474 from the client device 407 (at block B 686 ). In response to receiving the acceptance, the backend server 430 may retrieve (at block B 688 ) and transmit (at block B 690 ) the image data 460 from the A/V recording and communication device 726 to the client device 407 .
- the image data 460 may be transmitted live, such that the user 712 of the client device 407 can see the current field of view of the camera 444 of the A/V recording and communication device 726 .
- the image data 460 transmitted to the client device 407 may be the pre-recorded image data 460 including the burglar 740 , and thus may be retrieved from the non-volatile memory 506 of the backend server 430 and/or from the A/V recording and communication device 726 .
- the user 712 may be able to see the appearance (e.g., physical appearance, identity, clothing, etc.) of the burglar 740 and/or the gun 742 being carried by the burglar 740 and determine that the burglar 740 is in fact suspicious. As a result, the user 712 may be more likely to hide, flee, alert law enforcement, or take other appropriate actions based on the knowledge of the burglar's 740 presence.
- the user 712 may access the device list 478 after being notified of the burglar 740 , and determine if any of the other A/V recording and communication devices in the proximity zone 716 have identified suspicious activity (e.g., the burglar 740 ), in order to determine the safest exit route and/or hiding places, for example.
- the processes 2600 - 3900 may provide users of client devices that may not be associated with A/V recording and communication devices in the user's vicinity, access to image data recorded by the A/V recording and communication devices.
- the user may be more likely to avoid dangerous and/or suspicious situations that the user may not otherwise be made aware of.
- the user may be able to view video of a suspicious person in the vicinity of the user by accessing the camera of an A/V recording and communication device in the user's vicinity. After viewing the suspicious person, the user may turn around and decide to take an alternate route, or the user may alert law enforcement, ultimately preventing or detecting criminal activity.
- the overall public safety may be enhanced, as persons may be more likely to avoid dangerous scenarios that they otherwise may not have been aware of
- the present disclosure provides numerous examples of methods and systems including A/V recording and communication doorbells, but the present embodiments are equally applicable for A/V recording and communication devices other than doorbells.
- the present embodiments may include one or more A/V recording and communication security cameras instead of, or in addition to, one or more A/V recording and communication doorbells.
- An example A/V recording and communication security camera may include substantially all of the structure and functionality of the doorbell 130 , but without the front button 148 , the button actuator 228 , and/or the light pipe 232 .
- FIG. 44 is a functional block diagram of a client device 800 on which the present embodiments may be implemented according to various aspects of the present disclosure.
- the user's client device 114 described with reference to FIG. 1 may include some or all of the components and/or functionality of the client device 800 .
- the client device 800 may comprise, for example, a smartphone.
- the client device 800 includes a processor 802 , a memory 804 , a user interface 806 , a communication module 808 , and a dataport 810 . These components are communicatively coupled together by an interconnect bus 812 .
- the processor 802 may include any processor used in smartphones and/or portable computing devices, such as an ARM processor (a processor based on the RISC (reduced instruction set computer) architecture developed by Advanced RISC Machines (ARM).).
- the processor 802 may include one or more other processors, such as one or more conventional microprocessors, and/or one or more supplementary co-processors, such as math co-processors.
- the memory 804 may include both operating memory, such as random-access memory (RAM), as well as data storage, such as read-only memory (ROM), hard drives, flash memory, or any other suitable memory/storage element.
- RAM random-access memory
- ROM read-only memory
- the memory 804 may include removable memory elements, such as a CompactFlash card, a MultiMediaCard (MMC), and/or a Secure Digital (SD) card.
- MMC MultiMediaCard
- SD Secure Digital
- the memory 804 may comprise a combination of magnetic, optical, and/or semiconductor memory, and may include, for example, RAM, ROM, flash drive, and/or a hard disk or drive.
- the processor 802 and the memory 804 each may be, for example, located entirely within a single device, or may be connected to each other by a communication medium, such as a USB port, a serial port cable, a coaxial cable, an Ethernet-type cable, a telephone line, a radio frequency transceiver, or other similar wireless or wired medium or combination of the foregoing.
- a communication medium such as a USB port, a serial port cable, a coaxial cable, an Ethernet-type cable, a telephone line, a radio frequency transceiver, or other similar wireless or wired medium or combination of the foregoing.
- the processor 802 may be connected to the memory 804 via the dataport 810 .
- the user interface 806 may include any user interface or presentation elements suitable for a smartphone and/or a portable computing device, such as a keypad, a display screen, a touchscreen, a microphone, and a speaker.
- the communication module 808 is configured to handle communication links between the client device 800 and other, external devices or receivers, and to route incoming/outgoing data appropriately. For example, inbound data from the dataport 810 may be routed through the communication module 808 before being directed to the processor 802 , and outbound data from the processor 802 may be routed through the communication module 808 before being directed to the dataport 810 .
- the communication module 808 may include one or more transceiver modules capable of transmitting and receiving data, and using, for example, one or more protocols and/or technologies, such as GSM, UMTS (3GSM), IS-95 (CDMA one), IS-2000 (CDMA 2000), LTE, FDMA, TDMA, W-CDMA, CDMA, OFDMA, Wi-Fi, WiMAX, or any other protocol and/or technology.
- GSM Global System for Mobile communications
- the dataport 810 may be any type of connector used for physically interfacing with a smartphone and/or a portable computing device, such as a mini-USB port or an IPHONE®/IPOD® 30-pin connector or LIGHTNING® connector.
- the dataport 810 may include multiple communication channels for simultaneous communication with, for example, other processors, servers, and/or client terminals.
- the memory 804 may store instructions for communicating with other systems, such as a computer.
- the memory 804 may store, for example, a program (e.g., computer program code) adapted to direct the processor 802 in accordance with the present embodiments.
- the instructions also may include program elements, such as an operating system. While execution of sequences of instructions in the program causes the processor 802 to perform the process steps described herein, hard-wired circuitry may be used in place of, or in combination with, software/firmware instructions for implementation of the processes of the present embodiments.
- the present embodiments are not limited to any specific combination of hardware and software.
- FIG. 45 is a functional block diagram of a general-purpose computing system on which the present embodiments may be implemented according to various aspects of present disclosure.
- the computer system 900 may execute at least some of the operations described above.
- the computer system 900 may be embodied in at least one of a personal computer (also referred to as a desktop computer) 900 A, a portable computer (also referred to as a laptop or notebook computer) 900 B, and/or a server 900 C.
- a server is a computer program and/or a machine that waits for requests from other machines or software (clients) and responds to them.
- a server typically processes data.
- the purpose of a server is to share data and/or hardware and/or software resources among clients. This architecture is called the client—server model.
- the clients may run on the same computer or may connect to the server over a network.
- Examples of computing servers include database servers, file servers, mail servers, print servers, web servers, game servers, and application servers.
- server may be construed broadly to include any computerized process that shares a resource to one or more client processes.
- the computer system 900 may include at least one processor 910 , memory 920 , at least one storage device 930 , and input/output (I/O) devices 940 . Some or all of the components 910 , 920 , 930 , 940 may be interconnected via a system bus 950 .
- the processor 910 may be single- or multi-threaded and may have one or more cores.
- the processor 910 may execute instructions, such as those stored in the memory 920 and/or in the storage device 930 . Information may be received and output using one or more I/O devices 940 .
- the memory 920 may store information, and may be a computer-readable medium, such as volatile or non-volatile memory.
- the storage device(s) 930 may provide storage for the system 900 , and may be a computer-readable medium.
- the storage device(s) 930 may be a flash memory device, a hard disk device, an optical disk device, a tape device, or any other type of storage device.
- the I/O devices 940 may provide input/output operations for the system 900 .
- the I/O devices 940 may include a keyboard, a pointing device, and/or a microphone.
- the I/O devices 940 may further include a display unit for displaying graphical user interfaces, a speaker, and/or a printer.
- External data may be stored in one or more accessible external databases 960 .
- the features of the present embodiments described herein may be implemented in digital electronic circuitry, and/or in computer hardware, firmware, software, and/or in combinations thereof.
- Features of the present embodiments may be implemented in a computer program product tangibly embodied in an information carrier, such as a machine-readable storage device, and/or in a propagated signal, for execution by a programmable processor.
- Embodiments of the present method steps may be performed by a programmable processor executing a program of instructions to perform functions of the described implementations by operating on input data and generating output.
- a computer program may include a set of instructions that may be used, directly or indirectly, in a computer to perform a certain activity or bring about a certain result.
- a computer program may be written in any form of programming language, including compiled or interpreted languages, and it may be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment.
- Suitable processors for the execution of a program of instructions may include, for example, both general and special purpose processors, and/or the sole processor or one of multiple processors of any kind of computer.
- a processor may receive instructions and/or data from a read only memory (ROM), or a random-access memory (RAM), or both.
- ROM read only memory
- RAM random-access memory
- Such a computer may include a processor for executing instructions and one or more memories for storing instructions and/or data.
- a computer may also include, or be operatively coupled to communicate with, one or more mass storage devices for storing data files.
- mass storage devices for storing data files.
- Such devices include magnetic disks, such as internal hard disks and/or removable disks, magneto-optical disks, and/or optical disks.
- Storage devices suitable for tangibly embodying computer program instructions and/or data may include all forms of non-volatile memory, including for example semiconductor memory devices, such as EPROM, EEPROM, and flash memory devices, magnetic disks such as internal hard disks and removable disks, magneto-optical disks, and CD-ROM and DVD-ROM disks.
- the processor and the memory may be supplemented by, or incorporated in, one or more ASICs (application-specific integrated circuits).
- ASICs application-specific integrated circuits
- the features of the present embodiments may be implemented on a computer having a display device, such as an LCD (liquid crystal display) monitor, for displaying information to the user.
- the computer may further include a keyboard, a pointing device, such as a mouse or a trackball, and/or a touchscreen by which the user may provide input to the computer.
- the features of the present embodiments may be implemented in a computer system that includes a back-end component, such as a data server, and/or that includes a middleware component, such as an application server or an Internet server, and/or that includes a front-end component, such as a client computer having a graphical user interface (GUI) and/or an Internet browser, or any combination of these.
- the components of the system may be connected by any form or medium of digital data communication, such as a communication network. Examples of communication networks may include, for example, a LAN (local area network), a WAN (wide area network), and/or the computers and networks forming the Internet.
- the computer system may include clients and servers.
- a client and server may be remote from each other and interact through a network, such as those described herein.
- the relationship of client and server may arise by virtue of computer programs running on the respective computers and having a client-server relationship to each other.
- the phrases “at least one of A, B and C,” “at least one of A, B, or C,” and “A, B, and/or C” are synonymous and mean logical “OR” in the computer science sense.
- each of the foregoing phrases should be understood to read on (A), (B), (C), (A and B), (A and C), (B and C), and (A and B and C), where A, B, and C are variables representing elements or features of the claim.
- A, B, and C are variables representing elements or features of the claim.
Landscapes
- Engineering & Computer Science (AREA)
- Signal Processing (AREA)
- Multimedia (AREA)
- Computer Networks & Wireless Communication (AREA)
- Human Computer Interaction (AREA)
- Databases & Information Systems (AREA)
- Business, Economics & Management (AREA)
- Emergency Management (AREA)
- Telephonic Communication Services (AREA)
Abstract
First data representing geographic coordinates defining a proximity zone for access to an A/V recording and communication device may be received from a first client device associated with the A/V recording and communication device. Based at least in part on a graphical user interface being accessed within an application executing on the second client device, second data representing a location of the second client device may be received. A determination that the second client device is within the proximity zone may be made, and third data indicating that the A/V recording and communication device is accessible by the second client device may be transmitted to the second client device. A request for access to the A/V recording and communication device may be received from the second client device, and image data generated by the A/V recording and communication device may be obtained and transmitted to the second client device.
Description
- This application is a continuation of, and claims priority to, U.S. patent application Ser. No. 16/028,252, filed Jul. 7, 2018, which claims priority to U.S. provisional application Ser. No. 62/529,460, filed on Jul. 6, 2017. The entire contents of each application is hereby incorporated by reference.
- The present embodiments relate to audio/video (A/V) recording and communication devices, including A/V recording and communication doorbell systems. In particular, the present embodiments relate to improvements in the functionality of A/V recording and communication devices that strengthen the ability of such devices to reduce crime and enhance public safety.
- Home safety is a concern for many homeowners and renters. Those seeking to protect or monitor their homes often wish to have video and audio communications with visitors, for example, those visiting an external door or entryway. Audio/Video (A/V) recording and communication devices, such as doorbells, provide this functionality, and can also aid in crime detection and prevention. For example, audio and/or video captured by an A/V recording and communication doorbell can be uploaded to the cloud and recorded on a remote server. Subsequent review of the A/V footage can aid law enforcement in capturing perpetrators of home burglaries and other crimes. Further, the presence of one or more an A/V recording and communication devices on the exterior of a home, such as a doorbell unit at the entrance of a home, acts as a powerful deterrent against would-be burglars.
- The various embodiments of the present accessing cameras of A/V recording and communication devices based on location have several features, no single one of which is solely responsible for their desirable attributes. Without limiting the scope of the present embodiments as expressed by the claims that follow, their more prominent features now will be discussed briefly. After considering this discussion, and particularly after reading the section entitled “Detailed Description,” one will understand how the features of the present embodiments provide the advantages described herein.
- One aspect of the present embodiments includes the realization that as A/V recording and communication devices continue to become more prevalent, leveraging the functionalities of these devices (e.g., video doorbells, security cameras, etc.) by persons other than the owners/users of the A/V recording and communication devices may prove increasingly useful. Current A/V recording and communication devices, other than the present embodiments, sometimes do not allow persons other than the owner/user of the A/V recording and communication device access to the device's functionalities (e.g., the camera, the speaker, etc.). As a result, there may be missed opportunities for persons other than the owners/users of the A/V recording and communication devices to leverage these functionalities to provide safety, security, and peace of mind. For example, a neighborhood may include a plurality of A/V recording and communication devices installed at various homes, and the neighborhood may be dark and/or dangerous. As a result, a person walking through the neighborhood may desire to view video being recorded in a field of view of one or more of the A/V recording and communication devices in order to determine if there is any suspicious activity or suspicious persons in the neighborhood.
- The present embodiments solve this problem by leveraging the functionality of A/V recording and communication devices, such as A/V recording and communication doorbells, to allow access to the A/V recording and communication devices by users of client devices in proximity to the A/V recording and communication devices. By allowing this access, the users of the client devices may be able to determine if any suspicious activity and/or persons are present, and in response, take the appropriate action. For example, the users of the client devices may notify law enforcement, leave the area, signal for help, signal an alarm, and/or speak to a suspicious person through a speaker of one or more of the A/V recording and communication devices. Ultimately, because the users of the client devices in proximity to the A/V recording and communication devices may be able to leverage the functionalities of the devices, the safety of the users and the neighborhood, in addition to the overall public safety, may be increased.
- In a first aspect, a client device including a display, a communication module, and a processor, in response to entering a proximity zone of an audio/video (A/V) recording and communication device, requests, by the processor using the communication module, access to a camera of the A/V recording and communication device; in response to the request for access, receives, by the processor using the communication module, from the camera, image data being recorded by the camera in a field of view of the camera; and displays, by the processor on the display, the image data.
- In an embodiment of the first aspect, the A/V recording and communication device is visible to a user of the client device when the client device is within the proximity zone.
- In another embodiment of the first aspect, the proximity zone is defined by the A/V recording and communication device.
- In another embodiment of the first aspect, the proximity zone includes the field of view of the camera of the A/V recording and communication device.
- In another embodiment of the first aspect, prior to requesting access, the client device determines, by the processor, that the client device has entered the proximity zone.
- In another embodiment of the first aspect, determining that the client device has entered the proximity zone includes comparing client device location data to proximity zone location data.
- In another embodiment of the first aspect, the client device location data and the proximity zone location data include at least one of global positioning system (GPS) data and Wi-Fi positioning system (WPS) data.
- In another embodiment of the first aspect, prior to receiving the image data and after requesting access, the client device establishes a connection to the A/V recording and communication device.
- In another embodiment of the first aspect, establishing the connection includes connecting to a network of the A/V recording and communication device.
- In another embodiment of the first aspect, the network is a Wi-Fi network.
- In another embodiment of the first aspect, the network is an ad hoc network generated by the A/V recording and communication device.
- In another embodiment of the first aspect, the connection to the network is an unsecure connection.
- In another embodiment of the first aspect, the client device, in response to entering the proximity zone, displays, by the processor on the display, a list of devices configured for access by the client device, the list of devices including the A/V recording and communication device, wherein requesting access to the camera includes receiving, by the processor on the display, a selection of the A/V recording and communication device from the list of devices.
- In a second aspect, a client device including a display, a communication module, and a processor, in response to entering a proximity zone of an audio/video (A/V) recording and communication device, receives, by the processor using the communication module, from the A/V recording and communication device, an access request for allowing the client device to access the camera of the A/V recording and communication device; in response to receiving the access request, transmits, by the processor using the communication module, to the A/V recording and communication device, an acceptance of the access request; in response to transmitting the acceptance, receives, by the processor using the communication module, from the camera, image data being recorded by the camera in a field of view of the camera; and displays, by the processor on the display, the image data.
- In an embodiment of the second aspect, the A/V recording and communication device is visible to a user of the client device when the client device is within the proximity zone.
- In another embodiment of the second aspect, the proximity zone is defined by the A/V recording and communication device.
- In another embodiment of the second aspect, the proximity zone includes the field of view of the camera of the A/V recording and communication device.
- In another embodiment of the second aspect, a determination that the client device has entered the proximity zone includes comparing client device location data to proximity zone location data.
- In another embodiment of the second aspect, the client device location data and the proximity zone location data include at least one of global positioning system (GPS) data and Wi-Fi positioning system (WPS) data.
- In another embodiment of the second aspect, the client device, prior to receiving the image data and after transmitting the acceptance, establishes, by the processor using the communication module, a connection to the A/V recording and communication device.
- In another embodiment of the second aspect, establishing the connection includes connecting to a network of the A/V recording and communication device.
- In another embodiment of the second aspect, the network is a Wi-Fi network.
- In another embodiment of the second aspect, the network is an ad hoc network generated by the A/V recording and communication device.
- In another embodiment of the second aspect, the connection to the network is an unsecure connection.
- In another embodiment of the second aspect, in response to receiving the access request, the client device displays, by the processor on the display, a list of devices configured for access by the client device, the list of devices including the A/V recording and communication device, wherein the acceptance of the access request includes receiving, by the processor on the display, a selection of the A/V recording and communication device from the list of devices.
- In a third aspect, a client device including a display, a communication module, and a processor, in response to entering a proximity zone of an audio/video (A/V) recording and communication device having a camera, receives, by the processor using the communication module, an access request for allowing the client device access to the camera of the A/V recording and communication device; displays, by the processor on the display, a list of devices accessible by the client device, the list of devices including at least the A/V recording and communication device; in response to the displaying and based on the receiving the access request, receives, by the processor, an input including an acceptance of the access request; in response to receiving the input, transmits, by the processor using the communication module, to the A/V recording and communication device, the acceptance of the access request; in response to transmitting the acceptance of the access request, receives, by the processor using the communication module, from the camera of the A/V recording and communication device, image data being recorded in a field of view of the camera; and displays, by the processor on the display, the image data.
- In an embodiment of the third aspect, the A/V recording and communication device is visible to a user of the client device when the client device is within the proximity zone.
- In another embodiment of the third aspect, the proximity zone is defined by the A/V recording and communication device.
- In another embodiment of the third aspect, the proximity zone includes the field of view of the camera of the A/V recording and communication device.
- In another embodiment of the third aspect, a determination that the client device has entered the proximity zone includes comparing client device location data to proximity zone location data.
- In another embodiment of the third aspect, the client device location data and the proximity zone location data include at least one of global positioning system (GPS) data and Wi-Fi positioning system (WPS) data.
- In another embodiment of the third aspect, prior to receiving the image data and after transmitting the acceptance, the client device establishes a connection to the A/V recording and communication device.
- In another embodiment of the third aspect, establishing the connection includes connecting to a network of the A/V recording and communication device.
- In another embodiment of the third aspect, the network is a Wi-Fi network.
- In another embodiment of the third aspect, the network is an ad hoc network generated by the A/V recording and communication device.
- In another embodiment of the third aspect, the connection to the network is an unsecure connection.
- In a fourth aspect, an audio/video (A/V) recording and communication device including a processor, a communication module, and a camera, in response to detecting the presence of a client device in a proximity zone of the A/V recording and communication device, transmits, by the processor using the communication module, an access request to the client device for allowing the client device access to the camera; in response to the transmitting the access request, receives, by the processor using the communication module, an acceptance of the access request from the client device; and in response to receiving the acceptance, transmits, by the processor using the communication module, image data being recorded by the camera to the client device.
- In an embodiment of the fourth aspect, the A/V recording and communication device detects, by the processor using the communication module, the presence of the client device in the proximity zone of the A/V recording and communication device.
- In another embodiment of the fourth aspect, detecting the presence of the client device includes scanning, by the processor using the communication module, the proximity zone for network connection signals.
- In another embodiment of the fourth aspect, the network connection signals are at least one of Bluetooth signals and Wi-Fi signals.
- In another embodiment of the fourth aspect, detecting the presence of the client device further includes, in response to scanning, identifying client device network connection signals being broadcast by the client device.
- In another embodiment of the fourth aspect, the proximity zone is generated by the A/V recording and communication device.
- In another embodiment of the fourth aspect, the proximity zone is defined by a user of a client device associated with the A/V recording and communication device.
- In another embodiment of the fourth aspect, prior to transmitting the image data and after receiving the acceptance, the A/V recording and communication device establishes a connection to the client device.
- In another embodiment of the fourth aspect, establishing the connection includes: transmitting, by the processor using the communication module, network access credentials of a network of the A/V recording and communication device to the client device; and in response to the transmitting, connecting, by the processor using the communication module, to the client device over the network.
- In another embodiment of the fourth aspect, the network is a Wi-Fi network.
- In another embodiment of the fourth aspect, the network is an ad hoc network generated by the A/V recording and communication device.
- In another embodiment of the fourth aspect, transmitting the image data includes: analyzing, by the processor, the image data to determine whether a person is present; and in response to determining that a person is present, transmitting the image data to the client device.
- In another embodiment of the fourth aspect, transmitting the image data includes: analyzing, by the processor, the image data to determine whether a person is present; in response to determining that a person is present, determining, by the processor, whether the person is a user of the client device; and in response to determining that the person is the user, transmitting, by the processor using the communication module, the image data to the client device.
- In a fifth aspect, an audio/video (A/V) recording and communication device including a processor, a communication module, and a camera, in response to a client device entering a proximity zone of the A/V recording and communication device, receives, by the processor using the communication module, an access request from the client device for allowing the client device access to the camera; in response to the receiving the access request, accepts, by the processor, the access request; and in response to the accepting, transmits, by the processor using the communication module, to the client device, image data being recorded by the camera in a field of view of the camera.
- In an embodiment of the fifth aspect, accepting the access request includes: analyzing, by the processor, the image data to determine whether a person is present; and in response to determining that a person is present, accepting the access request.
- In another embodiment of the fifth aspect, accepting the access request includes: analyzing, by the processor, the image data to determine whether a person is present; in response to determining that a person is present, determining, by the processor, whether the person is a user of the client device; and in response to determining that the person is the user, accepting the access request.
- In another embodiment of the fifth aspect, prior to transmitting the image data and after accepting the access request, the A/V recording and communication device establishes a connection to the client device.
- In another embodiment of the fifth aspect, establishing the connection includes: transmitting, by the processor using the communication module, network access credentials of a network of the A/V recording and communication device to the client device; and in response to the transmitting, connecting, by the processor using the communication module, to the client device over the network.
- In another embodiment of the fifth aspect, the network is a Wi-Fi network.
- In another embodiment of the fifth aspect, the network is an ad hoc network generated by the A/V recording and communication device.
- In another embodiment of the fifth aspect, the proximity zone is generated by the A/V recording and communication device.
- In another embodiment of the fifth aspect, the proximity zone is defined by a user of a client device associated with the A/V recording and communication device.
- In a sixth aspect, an audio/video (A/V) recording and communication device including a processor, a communication module, and a camera, generates, by the processor, a proximity zone for detecting the presence of one or more client devices within the proximity zone; based on the generating, detects, by the processor, the presence of a first client device within the proximity zone of the A/V recording and communication device; in response to detecting the presence of the first client device, transmits, by the processor using the communication module, an access request to the client device for allowing the client device access to the camera; in response to the transmitting the access request, receives, by the processor using the communication module, an acceptance of the access request from the client device; and in response to receiving the acceptance, transmits, by the processor using the communication module, image data being recorded by the camera to the client device.
- In an embodiment of the sixth aspect, the proximity zone is defined by a user of a client device associated with the A/V recording and communication device.
- In another embodiment of the sixth aspect, prior to transmitting the image data and after receiving the acceptance, the A/V recording and communication device establishes a connection to the client device.
- In another embodiment of the sixth aspect, establishing the connection includes: transmitting, by the processor using the communication module, network access credentials of a network of the A/V recording and communication device to the client device; and in response to the transmitting, connecting, by the processor using the communication module, to the client device over the network.
- In another embodiment of the sixth aspect, the network is a Wi-Fi network.
- In another embodiment of the sixth aspect, the network is an ad hoc network generated by the A/V recording and communication device.
- In another embodiment of the sixth aspect, transmitting the image data includes: analyzing, by the processor, the image data to determine whether a person is present; and in response to determining that a person is present, transmitting the image data to the client device.
- In another embodiment of the sixth aspect, transmitting the image data includes: analyzing, by the processor, the image data to determine whether a person is present; in response to determining that a person is present, determining, by the processor, whether the person is a user of the client device; and in response to determining that the person is the user, transmitting, by the processor using the communication module, the image data to the client device.
- In a seventh aspect, a method for use with a client device and an audio/video (A/V) recording and communication device having a camera, comprises: in response to the client device entering a proximity zone of the A/V recording and communication device, receiving, from the client device, an access request to allow the client device access to the camera of the A/V recording and communication device; in response to receiving the access request, transmitting the access request to the A/V recording and communication device; in response to transmitting the access request, receiving, from the A/V recording and communication device, image data being recorded by the camera of the A/V recording and communication device in a field of view of the camera; and in response to receiving the image data, transmitting the image data to the client device.
- In an embodiment of the seventh aspect, the proximity zone is generated by the A/V recording and communication device.
- In another embodiment of the seventh aspect, the proximity zone is defined by a user of a client device associated with the A/V recording and communication device.
- In another embodiment of the seventh aspect, the method is performed by a backend device.
- In another embodiment of the seventh aspect, the backend device is a server.
- In an eighth aspect, a method for use with a client device and an audio/video (A/V) recording and communication device having a camera, comprises: in response to the client device entering a proximity zone of the A/V recording and communication device, receiving, from the A/V recording and communication device, an access request to allow the client device access to the camera of the A/V recording and communication device; in response to receiving the access request, transmitting the access request to the client device; in response to transmitting the access request, receiving an acceptance of the access request from the client device; in response to the receiving the acceptance, retrieving, from the A/V recording and communication device, image data being recorded by the camera in a field of view of the camera; and in response to retrieving the image data, transmitting the image data to the client device.
- In an embodiment of the eighth aspect, the proximity zone is generated by the A/V recording and communication device.
- In another embodiment of the eighth aspect, the proximity zone is defined by a user of a client device associated with the A/V recording and communication device.
- In another embodiment of the eighth aspect, the method is performed by a backend device.
- In another embodiment of the eighth aspect, the backend device is a server.
- In a ninth aspect, a method for use with a client device and an audio/video (A/V) recording and communication device having a camera, comprises: receiving, from the A/V recording and communication device, first location information including a proximity zone; receiving, from the client device, second location data including a location of the client device; in response to receiving the second location data and based on the first location data, analyzing the second location data to determine whether the client device is within the proximity zone; based on the determination of whether the client device is within the proximity zone, transmitting, to the client device, an access request for allowing the client device to access the camera of the A/V recording and communication device; in response to transmitting the access request, receiving, from the client device, an acceptance of the access request; in response to receiving the acceptance, retrieving, from the A/V recording and communication device, image data being recorded by the camera in a field of view of the camera; and in response to retrieving the image data, transmitting the image data to the client device.
- In an embodiment of the ninth aspect, the proximity zone is generated by the A/V recording and communication device.
- In another embodiment of the ninth aspect, the proximity zone is defined by a user of a client device associated with the A/V recording and communication device.
- In another embodiment of the ninth aspect, the method is performed by a backend device.
- In another embodiment of the ninth aspect, the backend device is a server.
- The various embodiments of the present accessing cameras of A/V recording and communication devices based on location now will be discussed in detail with an emphasis on highlighting the advantageous features. These embodiments depict the novel and non-obvious accessing cameras of A/V recording and communication devices based on location shown in the accompanying drawings, which are for illustrative purposes only. These drawings include the following figures, in which like numerals indicate like parts:
-
FIG. 1 is a functional block diagram illustrating one embodiment of a system including an A/V recording and communication device according to various aspects of the present disclosure; -
FIG. 2 is a flowchart illustrating one embodiment of a process for streaming and storing A/V content from an A/V recording and communication doorbell system according to various aspects of the present disclosure; -
FIG. 3 is a functional block diagram illustrating an embodiment of an A/V recording and communication doorbell system according to the present disclosure; -
FIG. 4 is a front perspective view of an embodiment of an A/V recording and communication doorbell according to the present disclosure; -
FIG. 5 is a rear perspective view of the A/V recording and communication doorbell ofFIG. 4 ; -
FIG. 6 is a partially exploded front perspective view of the A/V recording and communication doorbell ofFIG. 4 showing the cover removed; -
FIGS. 7, 8, and 9 are front perspective views of various internal components of the A/V recording and communication doorbell ofFIG. 4 ; -
FIG. 10 is a right-side cross-sectional view of the A/V recording and communication doorbell ofFIG. 4 taken through the line 10-10 inFIG. 4 ; -
FIGS. 11-13 are rear perspective views of various internal components of the A/V recording and communication doorbell ofFIG. 4 ; -
FIG. 14 is a front view of an A/V recording and communication device according to various aspects of the present disclosure; -
FIG. 15 is a rear view of the A/V recording and communication device ofFIG. 14 ; -
FIG. 16 is right-side cross-sectional view of the A/V recording and communication device ofFIG. 14 ; -
FIG. 17 is an exploded view of the A/V recording and communication device ofFIG. 14 and a mounting bracket; -
FIG. 18 is a top view of a passive infrared sensor assembly according to various aspects of the present disclosure; -
FIG. 19 is a front view of the passive infrared sensor assembly ofFIG. 18 ; -
FIG. 20 is a top view of the passive infrared sensor assembly ofFIG. 18 , illustrating the fields of view of the passive infrared sensors according to various aspects of the present disclosure; -
FIG. 21 is a functional block diagram of the components of the A/V recording and communication device ofFIG. 14 ; -
FIG. 22 is a functional block diagram illustrating a system for communicating in a network according to various aspects of the present disclosure; -
FIG. 23 is a functional block diagram illustrating one embodiment of an A/V recording and communication device according to various aspects of the present disclosure; -
FIG. 24 is a functional block diagram illustrating one embodiment of a backend device according to various aspects of the present disclosure; -
FIG. 25 is a functional block diagram illustrating one embodiment of a client device according to various aspects of the present disclosure; -
FIGS. 26-39 are flowcharts illustrating processes for accessing cameras of A/V recording and communication devices based on location according to various aspects of the present disclosure; -
FIGS. 40-41 are example environments illustrating aspects of a process for accessing cameras of A/V recording and communication devices according to various aspects of the present disclosure; -
FIGS. 42-43 are screenshots of a graphical user interface (GUI) illustrating aspects of a process for accessing cameras of A/V recording and communication devices according to various aspects of the present disclosure; -
FIG. 44 is a functional block diagram of a client device on which the present embodiments may be implemented according to various aspects of the present disclosure; and -
FIG. 45 is a functional block diagram of a general-purpose computing system on which the present embodiments may be implemented according to various aspects of present disclosure. - The following detailed description describes the present embodiments with reference to the drawings. In the drawings, reference numbers label elements of the present embodiments. These reference numbers are reproduced below in connection with the discussion of the corresponding drawing features.
- The embodiments of the present accessing cameras of A/V recording and communication devices based on location are described below with reference to the figures. These figures, and their written descriptions, indicate that certain components of the apparatus are formed integrally (e.g., a single unitary piece), and certain other components are formed as separate pieces. Components shown and described herein as being formed integrally may in alternative embodiments be formed as separate pieces. Further, components shown and described herein as being formed as separate pieces may in alternative embodiments be formed integrally.
- With reference to
FIG. 1 , the present embodiments include an audio/video (A/V) recording andcommunication device 100. The A/V recording andcommunication device 100 may in some embodiments comprise a doorbell, and may be located near the entrance to a structure (not shown), such as a dwelling, a business, a storage facility, etc. The A/V recording andcommunication device 100 includes acamera 102, amicrophone 104, and aspeaker 106. Thecamera 102 may comprise, for example, a high definition (HD) video camera, such as one capable of capturing video images at an image display resolution of 720p, or 1080p, or better. While not shown, the A/V recording andcommunication device 100 may also include other hardware and/or components, such as a housing, one or more motion sensors (and/or other types of sensors), a button, etc. The A/V recording andcommunication device 100 may further include similar componentry and/or functionality as the wireless communication doorbells described in U.S. Patent Application Publication Nos. 2015/0022620 (application Ser. No. 14/499,828) and 2015/0022618 (application Ser. No. 14/334,922), both of which are incorporated herein by reference in their entireties as if fully set forth. - With further reference to
FIG. 1 , the A/V recording andcommunication device 100 communicates with a user'snetwork 110, which may be for example a wired and/or wireless network. If the user'snetwork 110 is wireless, or includes a wireless component, thenetwork 110 may be a Wi-Fi network compatible with the IEEE 802.11 standard and/or other wireless communication standard(s). The user'snetwork 110 is connected to anothernetwork 112, which may comprise, for example, the Internet and/or a public switched telephone network (PSTN). As described below, the A/V recording andcommunication device 100 may communicate with a user's client device 114 via the user'snetwork 110 and the network 112 (Internet/PSTN). The user's client device 114 may comprise, for example, a mobile telephone (may also be referred to as a cellular telephone), such as a smartphone, a personal digital assistant (PDA), or another communication device. The user's client device 114 comprises a display (not shown) and related components capable of displaying streaming and/or recorded video images. The user's client device 114 may also comprise a speaker and related components capable of broadcasting streaming and/or recorded audio, and may also comprise a microphone. The A/V recording andcommunication device 100 may also communicate with one or more remote storage device(s) 116 (may be referred to interchangeably as “cloud storage device(s)”), one ormore servers 118, and/or a backend API (application programming interface) 120 via the user'snetwork 110 and the network 112 (Internet/PSTN). WhileFIG. 1 illustrates thestorage device 116, theserver 118, and the backend API 120 as components separate from thenetwork 112, it is to be understood that thestorage device 116, theserver 118, and/or the backend API 120 may be considered to be components of thenetwork 112. - The
network 112 may be any wireless network or any wired network, or a combination thereof, configured to operatively couple the above-mentioned modules, devices, and systems as shown inFIG. 1 . For example, thenetwork 112 may include one or more of the following: a PSTN (public switched telephone network), the Internet, a local intranet, a PAN (Personal Area Network), a LAN (Local Area Network), a WAN (Wide Area Network), a MAN (Metropolitan Area Network), a virtual private network (VPN), a storage area network (SAN), a frame relay connection, an Advanced Intelligent Network (AIN) connection, a synchronous optical network (SONET) connection, a digital T1, T3, E1 or E3 line, a Digital Data Service (DDS) connection, a DSL (Digital Subscriber Line) connection, an Ethernet connection, an ISDN (Integrated Services Digital Network) line, a dial-up port such as a V.90, V.34, or V.34bis analog modem connection, a cable modem, an ATM (Asynchronous Transfer Mode) connection, or an FDDI (Fiber Distributed Data Interface) or CDDI (Copper Distributed Data Interface) connection. Furthermore, communications may also include links to any of a variety of wireless networks, including WAP (Wireless Application Protocol), GPRS (General Packet Radio Service), GSM (Global System for Mobile Communication), LTE, VoLTE, LoRaWAN, LPWAN, RPMA, LTE Cat-“X” (e.g. LTE Cat 1,LTE Cat 0, LTE CatM1, LTE Cat NB1), CDMA (Code Division Multiple Access), TDMA (Time Division Multiple Access), FDMA (Frequency Division Multiple Access), and/or OFDMA (Orthogonal Frequency Division Multiple Access) cellular phone networks, global navigation satellite systems (GNSS), such as global positioning system (GPS), CDPD (cellular digital packet data), RIM (Research in Motion, Limited) duplex paging network, Bluetooth radio, or an IEEE 802.11-based radio frequency network. The network can further include or interface with any one or more of the following: RS-232 serial connection, IEEE-1394 (Firewire) connection, Fibre Channel connection, IrDA (infrared) port, SCSI (Small Computer Systems Interface) connection, USB (Universal Serial Bus) connection, or other wired or wireless, digital or analog, interface or connection, mesh or Digi® networking. - According to one or more aspects of the present embodiments, when a person (may be referred to interchangeably as “visitor”) arrives at the A/V recording and
communication device 100, the A/V recording andcommunication device 100 detects the visitor's presence and begins capturing video images within a field of view of thecamera 102. The A/V recording andcommunication device 100 may also capture audio through themicrophone 104. The A/V recording andcommunication device 100 may detect the visitor's presence by detecting motion using thecamera 102 and/or a motion sensor, and/or by detecting that the visitor has depressed the front button on the A/V recording and communication device 100 (in embodiments in which the A/V recording andcommunication device 100 comprises a doorbell). - In response to the detection of the visitor, the A/V recording and
communication device 100 sends an alert to the user's client device 114 (FIG. 1 ) via the user'snetwork 110 and thenetwork 112. The A/V recording andcommunication device 100 also sends streaming video, and may also send streaming audio, to the user's client device 114. If the user answers the alert, two-way audio communication may then occur between the visitor and the user through the A/V recording andcommunication device 100 and the user's client device 114. The user may view the visitor throughout the duration of the call, but the visitor cannot see the user (unless the A/V recording andcommunication device 100 includes a display, which it may in some embodiments). - The video images captured by the
camera 102 of the A/V recording and communication device 100 (and the audio captured by the microphone 104) may be uploaded to the cloud and recorded on the remote storage device 116 (FIG. 1 ). In some embodiments, the video and/or audio may be recorded on theremote storage device 116 even if the user chooses to ignore the alert sent to his or her client device 114. - With further reference to
FIG. 1 , the system may further comprise a backend API 120 including one or more components. A backend API (application programming interface) may comprise, for example, a server (e.g. a real server, or a virtual machine, or a machine running in a cloud infrastructure as a service), or multiple servers networked together, exposing at least one API to client(s) accessing it. These servers may include components such as application servers (e.g. software servers), depending upon what other components are included, such as a caching layer, or database layers, or other components. A backend API may, for example, comprise many such applications, each of which communicate with one another using their public APIs. In some embodiments, the API backend may hold the bulk of the user data and offer the user management capabilities, leaving the clients to have very limited state. - The backend API 120 illustrated
FIG. 1 may include one or more APIs. An API is a set of routines, protocols, and tools for building software and applications. An API expresses a software component in terms of its operations, inputs, outputs, and underlying types, defining functionalities that are independent of their respective implementations, which allows definitions and implementations to vary without compromising the interface. Advantageously, an API may provide a programmer with access to an application's functionality without the programmer needing to modify the application itself, or even understand how the application works. An API may be for a web-based system, an operating system, or a database system, and it provides facilities to develop applications for that system using a given programming language. In addition to accessing databases or computer hardware like hard disk drives or video cards, an API can ease the work of programming GUI components. For example, an API can facilitate integration of new features into existing applications (a so-called “plug-in API”). An API can also assist otherwise distinct applications with sharing data, which can help to integrate and enhance the functionalities of the applications. - The backend API 120 illustrated in
FIG. 1 may further include one or more services (also referred to as network services). A network service is an application that provides data storage, manipulation, presentation, communication, and/or other capability. Network services are often implemented using a client-server architecture based on application-layer network protocols. Each service may be provided by a server component running on one or more computers (such as a dedicated server computer offering multiple services) and accessed via a network by client components running on other devices. However, the client and server components can both be run on the same machine. Clients and servers may have a user interface, and sometimes other hardware associated with them. -
FIG. 2 is a flowchart illustrating a process for streaming and storing A/V content from an A/V recording and communication doorbell system according to various aspects of the present disclosure. At block B200, the A/V recording andcommunication device 100 detects the visitor's presence and begins capturing video images within a field of view of thecamera 102. The A/V recording andcommunication device 100 may also capture audio through themicrophone 104. As described above, the A/V recording andcommunication device 100 may detect the visitor's presence by detecting motion using thecamera 102 and/or a motion sensor, and/or by detecting that the visitor has depressed the front button on the A/V recording and communication device 100 (in embodiments in which the A/V recording andcommunication device 100 comprises a doorbell). - At block B202, a communication module of the A/V recording and
communication device 100 sends a connection request, via the user'snetwork 110 and thenetwork 112, to a device in thenetwork 112. For example, the network device to which the request is sent may be a server such as theserver 118. Theserver 118 may comprise a computer program and/or a machine that waits for requests from other machines or software (clients) and responds to them. A server typically processes data. One purpose of a server is to share data and/or hardware and/or software resources among clients. This architecture is called the client-server model. The clients may run on the same computer or may connect to the server over a network. Examples of computing servers include database servers, file servers, mail servers, print servers, web servers, game servers, and application servers. The term server may be construed broadly to include any computerized process that shares a resource to one or more client processes. - In response to the request, at block B204 the network device may connect the A/V recording and
communication device 100 to the user's client device 114 through the user'snetwork 110 and thenetwork 112. At block B206, the A/V recording andcommunication device 100 may record available audio and/or video data using thecamera 102, themicrophone 104, and/or any other sensor available. At block B208, the audio and/or video data is transmitted (streamed) from the A/V recording andcommunication device 100 to the user's client device 114 via the user'snetwork 110 and thenetwork 112. At block B210, the user may receive a notification on his or her client device 114 with a prompt to either accept or deny the call. - At block B212, the process determines whether the user has accepted or denied the call. If the user denies the notification, then the process advances to block B214, where the audio and/or video data is recorded and stored at a cloud server. The session then ends at block B216 and the connection between the A/V recording and
communication device 100 and the user's client device 114 is terminated. If, however, the user accepts the notification, then at block B218 the user communicates with the visitor through the user's client device 114 while audio and/or video data captured by thecamera 102, themicrophone 104, and/or other sensors is streamed to the user's client device 114. At the end of the call, the user may terminate the connection between the user's client device 114 and the A/V recording andcommunication device 100 and the session ends at block B216. In some embodiments, the audio and/or video data may be recorded and stored at a cloud server (block B214) even if the user accepts the notification and communicates with the visitor through the user's client device 114. - Many of today's homes include a wired doorbell system that does not have A/V communication capabilities. Instead, standard wired doorbell systems include a button outside the home next to the front door. The button activates a signaling device (such as a bell or a buzzer) inside the building. Pressing the doorbell button momentarily closes the doorbell circuit, which may be, for example, a single-pole, single-throw (SPST) push button switch. One terminal of the button is wired to a terminal on a transformer. The transformer steps down the 120-volt or 240-volt household AC electrical power to a lower voltage, typically 16 to 24 volts. Another terminal on the transformer is wired to a terminal on the signaling device. Another terminal on the signaling device is wired to the other terminal on the button. A common signaling device includes two flat metal bar resonators, which are struck by plungers operated by two solenoids. The flat bars are tuned to different notes. When the doorbell button is pressed, the first solenoid's plunger strikes one of the bars, and when the button is released, a spring on the plunger pushes the plunger up, causing it to strike the other bar, creating a two-tone sound (“ding-dong”).
- Many current A/V recording and communication doorbell systems (other than the present embodiments) are incompatible with existing wired doorbell systems of the type described in the preceding paragraph. One reason for this incompatibility is that the A/V recording and communication doorbell draws an amount of power from the household AC electrical power supply that is above the threshold necessary for causing the signaling device to sound. The A/V recording and communication doorbell thus causes frequent inadvertent sounding of the signaling device, which is not only bothersome to the home's occupant(s), but also undermines the usefulness of the doorbell. The present embodiments solve this problem by limiting the power consumption of the A/V recording and communication doorbell to an amount that is below the threshold necessary for causing the signaling device to sound. Embodiments of the present A/V recording and communication doorbell can thus be connected to the existing household AC power supply and the existing signaling device without causing inadvertent sounding of the signaling device.
- Several advantages flow from the ability of the present embodiments to be connected to the existing household AC power supply. For example, the camera of the present A/V recording and communication doorbell can be powered on continuously. In a typical battery-powered A/V recording and communication doorbell, the camera is powered on only part of the time so that the battery does not drain too rapidly. The present embodiments, by contrast, do not rely on a battery as a primary (or sole) power supply, and are thus able to keep the camera powered on continuously. Because the camera is able to be powered on continuously, it can always be recording, and recorded footage can be continuously stored in a rolling buffer or sliding window. In some embodiments, about 10-15 seconds of recorded footage can be continuously stored in the rolling buffer or sliding window. Also, because the camera is able to be powered on continuously, it can be used for motion detection, thus eliminating any need for a separate motion detection device, such as a passive infrared sensor (PIR). Eliminating the PIR simplifies the design of the A/V recording and communication doorbell and enables the doorbell to be made more compact. Also, because the camera is able to be powered on continuously, it can be used as a light detector for use in controlling the current state of the IR cut filter and turning the IR LED on and off. Using the camera as a light detector eliminates any need for a separate light detector, thereby further simplifying the design of the A/V recording and communication doorbell and enabling the doorbell to be made even more compact.
-
FIGS. 3-13 illustrate one embodiment of a low-power-consumption A/V recording andcommunication doorbell 130 according to various aspects of the present disclosure.FIG. 3 is a functional block diagram illustrating various components of the A/V recording andcommunication doorbell 130 and their relationships to one another. For example, the A/V recording andcommunication doorbell 130 includes a pair ofterminals 131, 132 configured to be connected to a source of external AC (alternating-current) power, such as a household AC power supply 134 (may also be referred to as AC mains). TheAC power 134 may have a voltage in the range of 16-24 VAC, for example. Theincoming AC power 134 may be converted to DC (direct-current) by an AC/DC rectifier 136. An output of the AC/DC rectifier 136 may be connected to an input of a DC/DC converter 138, which may step down the voltage from the output of the AC/DC rectifier 136 from 16-24 VDC to a lower voltage of about 5 VDC, for example. In various embodiments, the output of the DC/DC converter 138 may be in a range of from about 2.5 V to about 7.5 V, for example. - With further reference to
FIG. 3 , the output of the DC/DC converter 138 is connected to apower manager 140, which may comprise an integrated circuit including a processor core, memory, and/or programmable input/output peripherals. In one non-limiting example, thepower manager 140 may be an off-the-shelf component, such as the BQ24773 chip manufactured by Texas Instruments. As described in detail below, thepower manager 140 controls, among other things, an amount of power drawn from theexternal power supply 134, as well as an amount of supplemental power drawn from abattery 142, to power the A/V recording andcommunication doorbell 130. Thepower manager 140 may, for example, limit the amount of power drawn from theexternal power supply 134 so that a threshold power draw is not exceeded. In one non-limiting example, the threshold power, as measured at the output of the DC/DC converter 138, may be equal to 1.4 A. Thepower manager 140 may also control an amount of power drawn from theexternal power supply 134 and directed to thebattery 142 for recharging of thebattery 142. An output of thepower manager 140 is connected to apower sequencer 144, which controls a sequence of power delivery to other components of the A/V recording andcommunication doorbell 130, including acommunication module 146, afront button 148, amicrophone 150, aspeaker driver 151, a speaker 152, an audio CODEC (Coder-DECoder) 153, acamera 154, an infrared (IR)light source 156, anIR cut filter 158, a processor 160 (may also be referred to as a controller 160), a plurality oflight indicators 162, and acontroller 164 for thelight indicators 162. Each of these components is described in detail below. Thepower sequencer 144 may comprise an integrated circuit including a processor core, memory, and/or programmable input/output peripherals. In one non-limiting example, thepower sequencer 144 may be an off-the-shelf component, such as the RT5024 chip manufactured by Richtek. - With further reference to
FIG. 3 , the A/V recording andcommunication doorbell 130 further comprises anelectronic switch 166 that closes when thefront button 148 is depressed. When theelectronic switch 166 closes, power from theAC power source 134 is diverted through asignaling device 168 that is external to the A/V recording andcommunication doorbell 130 to cause thesignaling device 168 to emit a sound, as further described below. In one non-limiting example, theelectronic switch 166 may be a triac device. The A/V recording andcommunication doorbell 130 further comprises areset button 170 configured to initiate a hard reset of theprocessor 160, as further described below. - With further reference to
FIG. 3 , theprocessor 160 may perform data processing and various other functions, as described below. Theprocessor 160 may comprise an integrated circuit including a processor core,memory 172,non-volatile memory 174, and/or programmable input/output peripherals (not shown). Thememory 172 may comprise, for example, DDR3 (double data rate type three synchronous dynamic random-access memory). Thenon-volatile memory 174 may comprise, for example, NAND flash memory. In the embodiment illustrated inFIG. 3 , thememory 172 and thenon-volatile memory 174 are illustrated within the box representing theprocessor 160. It is to be understood that the embodiment illustrated inFIG. 3 is merely an example, and in some embodiments thememory 172 and/or thenon-volatile memory 174 are not necessarily physically incorporated with theprocessor 160. Thememory 172 and/or thenon-volatile memory 174, regardless of their physical location, may be shared by one or more other components (in addition to the processor 160) of the present A/V recording andcommunication doorbell 130. - The transfer of digital audio between the user and a visitor may be compressed and decompressed using the
audio CODEC 153, which is operatively coupled to theprocessor 160. When the visitor speaks, audio from the visitor is compressed by theaudio CODEC 153, digital audio data is sent through thecommunication module 146 to thenetwork 112 via the user'snetwork 110, routed by theserver 118 and delivered to the user's client device 114. When the user speaks, after being transferred through thenetwork 112, the user'snetwork 110, and thecommunication module 146, the digital audio data is decompressed by theaudio CODEC 153 and emitted to the visitor through the speaker 152, which is driven by thespeaker driver 151. - With further reference to
FIG. 3 , some of the present embodiments may include a shunt 176 connected in parallel with thesignaling device 168. The shunt 176 facilitates the ability of the A/V recording andcommunication doorbell 130 to draw power from theAC power source 134 without inadvertently triggering thesignaling device 168. The shunt 176, during normal standby operation, presents a relatively low electrical impedance, such as a few ohms, across the terminals of thesignaling device 168. Most of the current drawn by the A/V recording andcommunication doorbell 130, therefore, flows through the shunt 176, and not through thesignaling device 168. The shunt 176, however, contains electronic circuitry (described below) that switches the shunt 176 between a state of low impedance, such as a few ohms, for example, and a state of high impedance, such as >1K ohms, for example. When thefront button 148 of the A/V recording andcommunication doorbell 130 is pressed, theelectronic switch 166 closes, causing the voltage from theAC power source 134 to be impressed mostly across the shunt 176 and thesignaling device 168 in parallel, while a small amount of voltage, such as about 1V, is impressed across theelectronic switch 166. The circuitry in the shunt 176 senses this voltage, and switches the shunt 176 to the high impedance state, so that power from theAC power source 134 is diverted through thesignaling device 168. The divertedAC power 134 is above the threshold necessary to cause thesignaling device 168 to emit a sound. Pressing thefront button 148 of the doorbell 130 therefore causes thesignaling device 168 to “ring,” alerting any person(s) within the structure to which thedoorbell 130 is mounted that there is a visitor at the front door (or at another location corresponding to the location of the doorbell 130). In one non-limiting example, theelectronic switch 166 may be a triac device. - With reference to
FIGS. 4-6 , the A/V recording andcommunication doorbell 130 further comprises ahousing 178 having an enclosure 180 (FIG. 6 ), aback plate 182 secured to the rear of theenclosure 180, and ashell 184 overlying theenclosure 180. With reference toFIG. 6 , theshell 184 includes arecess 186 that is sized and shaped to receive theenclosure 180 in a close-fitting engagement, such that outer surfaces of theenclosure 180 abut conforming inner surfaces of theshell 184. Exterior dimensions of theenclosure 180 may be closely matched with interior dimensions of theshell 184 such that friction maintains theshell 184 about theenclosure 180. Alternatively, or in addition, theenclosure 180 and/or theshell 184 may include mating features 188, such as one or more tabs, grooves, slots, posts, etc. to assist in maintaining theshell 184 about theenclosure 180. Theback plate 182 is sized and shaped such that the edges of theback plate 182 extend outward from the edges of theenclosure 180, thereby creating alip 190 against which theshell 184 abuts when theshell 184 is mated with theenclosure 180, as shown inFIGS. 4 and 5 . In some embodiments,multiple shells 184 in different colors may be provided so that the end user may customize the appearance of his or her A/V recording andcommunication doorbell 130. For example, the A/V recording andcommunication doorbell 130 may be packaged and sold withmultiple shells 184 in different colors in the same package. - With reference to
FIG. 4 , a front surface of the A/V recording andcommunication doorbell 130 includes the button 148 (may also be referred to asfront button 148,FIG. 3 ), which is operatively connected to theprocessor 160. In a process similar to that described above with reference toFIG. 2 , when a visitor presses thefront button 148, an alert may be sent to the user's client device to notify the user that someone is at his or her front door (or at another location corresponding to the location of the A/V recording and communication doorbell 130). With further reference toFIG. 4 , the A/V recording andcommunication doorbell 130 further includes thecamera 154, which is operatively connected to theprocessor 160, and which is located behind ashield 192. As described in detail below, thecamera 154 is configured to capture video images from within its field of view. Those video images can be streamed to the user's client device and/or uploaded to a remote network device for later viewing according to a process similar to that described above with reference toFIG. 2 . - With reference to
FIG. 5 , a pair ofterminal screws 194 extends through theback plate 182. The terminal screws 194 are connected at their inner ends to theterminals 131, 132 (FIG. 3 ) within the A/V recording andcommunication doorbell 130. The terminal screws 194 are configured to receive electrical wires to connect to the A/V recording andcommunication doorbell 130, through theterminals 131, 132, to the householdAC power supply 134 of the structure on which the A/V recording andcommunication doorbell 130 is mounted. In the illustrated embodiment, theterminal screws 194 are located within a recessedportion 196 of the rear surface 198 of theback plate 182 so that theterminal screws 194 do not protrude from the outer envelope of the A/V recording andcommunication doorbell 130. The A/V recording andcommunication doorbell 130 can thus be mounted to a mounting surface with the rear surface 198 of theback plate 182 abutting the mounting surface. Theback plate 182 includesapertures 200 adjacent its upper and lower edges to accommodate mounting hardware, such as screws (not shown), for securing the back plate 182 (and thus the A/V recording and communication doorbell 130) to the mounting surface. With reference toFIG. 6 , theenclosure 180 includes correspondingapertures 202 adjacent its upper and lower edges that align with theapertures 200 in theback plate 182 to accommodate the mounting hardware. In certain embodiments, the A/V recording andcommunication doorbell 130 may include a mounting plate or bracket (not shown) to facilitate securing the A/V recording andcommunication doorbell 130 to the mounting surface. - With further reference to
FIG. 6 , theshell 184 includes acentral opening 204 in a front surface. Thecentral opening 204 is sized and shaped to accommodate theshield 192. In the illustrated embodiment, theshield 192 is substantially rectangular, and includes acentral opening 206 through which thefront button 148 protrudes. Theshield 192 defines a plane parallel to and in front of afront surface 208 of theenclosure 180. When theshell 184 is mated with theenclosure 180, as shown inFIGS. 4 and 10 , theshield 192 resides within thecentral opening 204 of theshell 184 such that afront surface 210 of theshield 192 is substantially flush with afront surface 212 of theshell 184 and there is little or no gap (FIG. 4 ) between the outer edges of theshield 192 and the inner edges of thecentral opening 204 in theshell 184. - With further reference to
FIG. 6 , theshield 192 includes an upper portion 214 (located above and to the sides of the front button 148) and a lower portion 216 (located below and to the sides of the front button 148). The upper andlower portions shield 192 may be separate pieces, and may comprise different materials. Theupper portion 214 of theshield 192 may be transparent or translucent so that it does not interfere with the field of view of thecamera 154. For example, in certain embodiments theupper portion 214 of theshield 192 may comprise glass or plastic. As described in detail below, themicrophone 150, which is operatively connected to theprocessor 160, is located behind theupper portion 214 of theshield 192. Theupper portion 214, therefore, may include anopening 218 that facilitates the passage of sound through theshield 192 so that themicrophone 150 is better able to pick up sounds from the area around the A/V recording andcommunication doorbell 130. - The
lower portion 216 of theshield 192 may comprise a material that is substantially transparent to infrared (IR) light, but partially or mostly opaque with respect to light in the visible spectrum. For example, in certain embodiments thelower portion 216 of theshield 192 may comprise a plastic, such as polycarbonate. Thelower portion 216 of theshield 192, therefore, does not interfere with transmission of IR light from the IRlight source 156, which is located behind thelower portion 216. As described in detail below, the IRlight source 156 and the IR cutfilter 158, which are both operatively connected to theprocessor 160, facilitate “night vision” functionality of thecamera 154. - The
upper portion 214 and/or thelower portion 216 of theshield 192 may abut an underlying cover 220 (FIG. 10 ), which may be integral with theenclosure 180 or may be a separate piece. Thecover 220, which may be opaque, may include afirst opening 222 corresponding to the location of thecamera 154, a second opening (not shown) corresponding to the location of themicrophone 150 and theopening 218 in theupper portion 214 of theshield 192, and a third opening (not shown) corresponding to the location of the IRlight source 156. -
FIGS. 7-10 illustrate various internal components of the A/V recording andcommunication doorbell 130.FIGS. 7-9 are front perspective views of the doorbell 130 with theshell 184 and theenclosure 180 removed, whileFIG. 10 is a right-side cross-sectional view of the doorbell 130 taken through the line 10-10 inFIG. 4 . With reference toFIGS. 7 and 8 , the A/V recording andcommunication doorbell 130 further comprises a main printed circuit board (PCB) 224 and afront PCB 226. With reference toFIG. 8 , thefront PCB 226 comprises abutton actuator 228. With reference toFIGS. 7, 8, and 10 , thefront button 148 is located in front of thebutton actuator 228. Thefront button 148 includes a stem 230 (FIG. 10 ) that extends into thehousing 178 to contact thebutton actuator 228. When thefront button 148 is pressed, the stem 230 depresses thebutton actuator 228, thereby closing the electronic switch 166 (FIG. 8 ), as described below. - With reference to
FIG. 8 , thefront PCB 226 further comprises thelight indicators 162, which may illuminate when thefront button 148 of thedoorbell 130 is pressed. In the illustrated embodiment, thelight indicators 162 comprise light-emitting diodes (LEDs 162) that are surface mounted to the front surface of thefront PCB 226 and are arranged in a circle around thebutton actuator 228. The present embodiments are not limited to thelight indicators 162 being LEDs, and in alternative embodiments thelight indicators 162 may comprise any other type of light-emitting device. The present embodiments are also not limited by the number oflight indicators 162 shown inFIG. 8 , nor by the pattern in which they are arranged. - With reference to
FIG. 7 , the doorbell 130 further comprises alight pipe 232. Thelight pipe 232 is a transparent or translucent ring that encircles thefront button 148. With reference toFIG. 4 , thelight pipe 232 resides in an annular space between thefront button 148 and thecentral opening 206 in theshield 192, with afront surface 234 of thelight pipe 232 being substantially flush with thefront surface 210 of theshield 192. With reference toFIGS. 7 and 10 , a rear portion oflight pipe 232 includes a plurality ofposts 236 whose positions correspond to the positions of theLEDs 162. When theLEDs 162 are illuminated, light is transmitted through theposts 236 and the body of thelight pipe 232 so that the light is visible at thefront surface 234 of thelight pipe 232. TheLEDs 162 and thelight pipe 232 thus provide a ring of illumination around thefront button 148. Thelight pipe 232 may comprise a plastic, for example, or any other suitable material capable of transmitting light. - The
LEDs 162 and thelight pipe 232 may function as visual indicators for a visitor and/or a user. For example, theLEDs 162 may illuminate upon activation or stay illuminated continuously. In one aspect, theLEDs 162 may change color to indicate that thefront button 148 has been pressed. TheLEDs 162 may also indicate that thebattery 142 needs recharging, or that thebattery 142 is currently being charged, or that charging of thebattery 142 has been completed. TheLEDs 162 may indicate that a connection to the user's wireless network is good, limited, poor, or not connected. TheLEDs 162 may be used to guide the user through setup or installation steps using visual cues, potentially coupled with audio cues emitted from the speaker 152. - With further reference to
FIG. 7 , the A/V recording andcommunication doorbell 130 further comprises arechargeable battery 142. As described in further detail below, the A/V recording andcommunication doorbell 130 is connected to an external power source 134 (FIG. 3 ), such as AC mains. The A/V recording andcommunication doorbell 130 is primarily powered by theexternal power source 134, but may also draw power from therechargeable battery 142 so as not to exceed a threshold amount of power from theexternal power source 134, to thereby avoid inadvertently sounding thesignaling device 168. With reference toFIG. 3 , thebattery 142 is operatively connected to thepower manager 140. As described below, thepower manager 140 controls an amount of power drawn from thebattery 142 to supplement the power drawn from the externalAC power source 134 to power the A/V recording andcommunication doorbell 130 when supplemental power is needed. Thepower manager 140 also controls recharging of thebattery 142 using power drawn from theexternal power source 134. Thebattery 142 may comprise, for example, a lithium-ion battery, or any other type of rechargeable battery. - With further reference to
FIG. 7 , the A/V recording andcommunication doorbell 130 further comprises thecamera 154. Thecamera 154 is coupled to a front surface of thefront PCB 226, and includes alens 238 and an imaging processor 240 (FIG. 9 ). Thecamera lens 238 may be a lens capable of focusing light into thecamera 154 so that clear images may be captured. Thecamera 154 may comprise, for example, a high definition (HD) video camera, such as one capable of capturing video images at an image display resolution of 720p or better. In certain of the present embodiments, thecamera 154 may be used to detect motion within its field of view, as described below. - With further reference to
FIG. 7 , the A/V recording andcommunication doorbell 130 further comprises an infrared (IR) light source 242. In the illustrated embodiment, the IR light source 242 comprises an IR light-emitting diode (LED) 242 coupled to an IR LED printed circuit board (PCB) 244. In alternative embodiments, the IR LED 242 may not comprise aseparate PCB 244, and may, for example, be coupled to thefront PCB 226. - With reference to
FIGS. 7 and 10 , theIR LED PCB 244 is located below the front button 148 (FIG. 7 ) and behind thelower portion 216 of the shield 192 (FIG. 10 ). As described above, thelower portion 216 of theshield 192 is transparent to IR light, but may be opaque with respect to light in the visible spectrum. - The IR LED 242 may be triggered to activate when a low level of ambient light is detected. When activated, IR light emitted from the IR LED 242 illuminates the
camera 154's field of view. Thecamera 154, which may be configured to detect IR light, may then capture the IR light emitted by the IR LED 242 as it reflects off objects within thecamera 154's field of view, so that the A/V recording andcommunication doorbell 130 can clearly capture images at night (may be referred to as “night vision”). - With reference to
FIG. 9 , the A/V recording andcommunication doorbell 130 further comprises anIR cut filter 158. The IR cutfilter 158 is a mechanical shutter that can be selectively positioned between thelens 238 and the image sensor of thecamera 154. During daylight hours, or whenever there is a sufficient amount of ambient light, the IR cutfilter 158 is positioned between thelens 238 and the image sensor to filter out IR light so that it does not distort the colors of images as the human eye sees them. During nighttime hours, or whenever there is little to no ambient light, the IR cutfilter 158 is withdrawn from the space between thelens 238 and the image sensor, so that thecamera 154 is sensitive to IR light (“night vision”). In some embodiments, thecamera 154 acts as a light detector for use in controlling the current state of the IR cutfilter 158 and turning the IR LED 242 on and off. Using thecamera 154 as a light detector is facilitated in some embodiments by the fact that the A/V recording andcommunication doorbell 130 is powered by a connection to AC mains, and thecamera 154, therefore, is always powered on. In other embodiments, however, the A/V recording andcommunication doorbell 130 may include a light sensor separate from thecamera 154 for use in controlling the IR cutfilter 158 and the IR LED 242. - With reference back to
FIG. 6 , the A/V recording andcommunication doorbell 130 further comprises areset button 170. Thereset button 170 contacts a reset button actuator 246 (FIG. 8 ) coupled to thefront PCB 226. When thereset button 170 is pressed, it may contact the reset button actuator 246, which may trigger the erasing of any data stored at thenon-volatile memory 174 and/or at the memory 172 (FIG. 3 ), and/or may trigger a reboot of theprocessor 160. -
FIGS. 11-13 further illustrate internal components of the A/V recording andcommunication doorbell 130.FIGS. 11-13 are rear perspective views of the doorbell 130 with theback plate 182 and additional components removed. For example, inFIG. 11 theback plate 182 is removed, while inFIG. 12 theback plate 182 and themain PCB 224 are removed, and inFIG. 13 theback plate 182, themain PCB 224, and thefront PCB 226 are removed. With reference toFIG. 11 , several components are coupled to the rear surface of themain PCB 224, including thecommunication module 146, theprocessor 160,memory 172, andnon-volatile memory 174. The functions of each of these components are described below. With reference toFIG. 12 , several components are coupled to the rear surface of thefront PCB 226, including thepower manager 140, thepower sequencer 144, the AC/DC rectifier 136, the DC/DC converter 138, and thecontroller 164 for thelight indicators 162. The functions of each of these components are also described below. With reference toFIG. 13 , several components are visible within theenclosure 180, including themicrophone 150, a speaker chamber 248 (in which the speaker 152 is located), and anantenna 250 for thecommunication module 146. The functions of each of these components are also described below. - With reference to
FIG. 7 , theantenna 250 is coupled to the front surface of themain PCB 224 and operatively connected to thecommunication module 146, which is coupled to the rear surface of the main PCB 224 (FIG. 11 ). Themicrophone 150, which may also be coupled to the front surface of themain PCB 224, is located near the opening 218 (FIG. 4 ) in theupper portion 214 of theshield 192 so that sounds emanating from the area around the A/V recording andcommunication doorbell 130 can pass through theopening 218 and be detected by themicrophone 150. With reference toFIG. 13 , the speaker chamber 248 is located near the bottom of theenclosure 180. The speaker chamber 248 comprises a hollow enclosure in which the speaker 152 is located. The hollow speaker chamber 248 amplifies the sounds made by the speaker 152 so that they can be better heard by a visitor in the area near the A/V recording andcommunication doorbell 130. With reference toFIGS. 5 and 13 , thelower surface 252 of theshell 184 and the lower surface (not shown) of theenclosure 180 may include anacoustical opening 254 through which the sounds made by the speaker 152 can pass so that they can be better heard by a visitor in the area near the A/V recording andcommunication doorbell 130. In the illustrated embodiment, theacoustical opening 254 is shaped generally as a rectangle having a length extending substantially across thelower surface 252 of the shell 184 (and also the enclosure 180). The illustrated shape is, however, just one example. With reference toFIG. 5 , thelower surface 252 of theshell 184 may further include anopening 256 for receiving a security screw (not shown). The security screw may extend through theopening 256 and into a similarly located opening in theenclosure 180 to secure theshell 184 to theenclosure 180. If thedoorbell 130 is mounted to a mounting bracket (not shown), the security screw may also maintain the doorbell 130 on the mounting bracket. - With reference to
FIG. 13 , the A/V recording andcommunication doorbell 130 may further include abattery heater 258. The present A/V recording andcommunication doorbell 130 is configured for outdoor use, including in cold climates. Cold temperatures, however, can cause negative performance issues for rechargeable batteries, such as reduced energy capacity, increased internal resistance, reduced ability to charge without damage, and reduced ability to supply load current. Thebattery heater 258 helps to keep therechargeable battery 142 warm in order to reduce or eliminate the foregoing negative performance issues. In the illustrated embodiment, thebattery heater 258 comprises a substantially flat, thin sheet abutting a side surface of therechargeable battery 142. Thebattery heater 258 may comprise, for example, an electrically resistive heating element that produces heat when electrical current is passed through it. Thebattery heater 258 may thus be operatively coupled to thepower manager 140 and/or the power sequencer 144 (FIG. 12 ). In some embodiments, therechargeable battery 142 may include a thermally sensitive resistor (“thermistor,” not shown) operatively connected to theprocessor 160 so that thebattery 142's temperature can be monitored and the amount of power supplied to thebattery heater 258 can be adaptively controlled to keep therechargeable battery 142 within a desired temperature range. - As described above, the present embodiments advantageously limit the power consumption of the A/V recording and communication doorbell to an amount that is below the threshold necessary for causing the signaling device to sound (except when the front button of the doorbell is pressed). The present A/V recording and communication doorbell can thus be connected to the existing household AC power supply and the existing signaling device without causing inadvertent sounding of the signaling device.
- Several advantages flow from the ability of the present embodiments to be connected to the existing household AC power supply. For example, the camera of the present A/V recording and communication doorbell can be powered on continuously. In a typical battery-powered A/V recording and communication doorbell, the camera is powered on only part of the time so that the battery does not drain too rapidly. The present embodiments, by contrast, do not rely on a battery as a primary (or sole) power supply, and are thus able to keep the camera powered on continuously. Because the camera is able to be powered on continuously, it can always be recording, and recorded footage can be continuously stored in a rolling buffer or sliding window. In some embodiments, about 10-15 seconds of recorded footage can be continuously stored in the rolling buffer or sliding window. Also, because the camera is able to be powered on continuously, it can be used for motion detection, thus eliminating any need for a separate motion detection device, such as a passive infrared sensor (PIR). Eliminating the PIR simplifies the design of the A/V recording and communication doorbell and enables the doorbell to be made more compact, although in some alternative embodiments the doorbell may include one or more PIRs and/or other motion detectors, heat source detectors, etc. Also, because the camera is able to be powered on continuously, it can be used as a light detector for use in controlling the current state of the IR cut filter and turning the IR LED on and off. Using the camera as a light detector eliminates any need for a separate light detector, thereby further simplifying the design of the A/V recording and communication doorbell and enabling the doorbell to be made even more compact, although in some alternative embodiments the doorbell may include a separate light detector.
-
FIGS. 14-18 illustrate another embodiment of a wireless audio/video (A/V)communication doorbell 330 according to an aspect of present embodiments.FIG. 14 is a front view,FIG. 15 is a rear view,FIG. 16 is a right-side cross-sectional view, andFIG. 17 is an exploded view of thedoorbell 330 and a mountingbracket 337. As described below, thedoorbell 330 is configured to be connected to an external power source, such as household wiring, but is also configured to be powered by an on-board rechargeable battery instead of, or in addition to, the external power source. - The
doorbell 330 includes afaceplate 335 mounted to a back plate 339 (FIG. 15 ). With reference toFIG. 16 , thefaceplate 335 has a substantially flat profile. Thefaceplate 335 may comprise any suitable material, including, without limitation, metals, such as brushed aluminum or stainless steel, metal alloys, or plastics. Thefaceplate 335 protects the internal contents of thedoorbell 330 and serves as an exterior front surface of thedoorbell 330. - With reference to
FIG. 14 , thefaceplate 335 includes abutton 333 and alight pipe 336. Thebutton 333 and thelight pipe 336 may have various profiles that may or may not match the profile of thefaceplate 335. Thelight pipe 336 may comprise any suitable material, including, without limitation, transparent plastic, that is capable of allowing light produced within thedoorbell 330 to pass through. The light may be produced by one or more light-emitting components, such as light-emitting diodes (LED's), contained within thedoorbell 330, as further described below. Thebutton 333 may make contact with a button actuator (not shown) located within thedoorbell 330 when thebutton 333 is pressed by a visitor. When pressed, thebutton 333 may trigger one or more functions of thedoorbell 330, as further described below. - With reference to
FIGS. 3 and 4 , the doorbell 330 further includes anenclosure 331 that engages thefaceplate 335. In the illustrated embodiment, theenclosure 331 abuts anupper edge 335T (FIG. 14 ) of thefaceplate 335, but in alternative embodiments one or more gaps between theenclosure 331 and thefaceplate 335 may facilitate the passage of sound and/or light through thedoorbell 330. Theenclosure 331 may comprise any suitable material, but in some embodiments the material of theenclosure 331 preferably permits infrared light to pass through from inside the doorbell 330 to the environment and vice versa. Thedoorbell 330 further includes alens 332. In some embodiments, the lens may comprise a Fresnel lens, which may be patterned to deflect incoming light into one or more infrared sensors located within thedoorbell 330. Thedoorbell 330 further includes acamera 334, which captures video data when activated, as described below. -
FIG. 15 is a rear view of thedoorbell 330, according to an aspect of the present embodiments. As illustrated, theenclosure 331 may extend from the front of the doorbell 330 around to the back thereof and may fit snugly around a lip of theback plate 339. Theback plate 339 may comprise any suitable material, including, without limitation, metals, such as brushed aluminum or stainless steel, metal alloys, or plastics. Theback plate 339 protects the internal contents of thedoorbell 330 and serves as an exterior rear surface of thedoorbell 330. Thefaceplate 335 may extend from the front of thedoorbell 330 and at least partially wrap around theback plate 339, thereby allowing a coupled connection between thefaceplate 335 and theback plate 339. Theback plate 339 may have indentations in its structure to facilitate the coupling. - With further reference to
FIG. 15 ,spring contacts 340 may provide power to the doorbell 330 when mated with other conductive contacts connected to a power source. Thespring contacts 340 may comprise any suitable conductive material, including, without limitation, copper, and may be capable of deflecting when contacted by an inward force, for example the insertion of a mating element. Thedoorbell 330 further comprises aconnector 360, such as a micro-USB or other connector, whereby power and/or data may be supplied to and from the components within thedoorbell 330. Areset button 359 may be located on theback plate 339, and may make contact with a button actuator (not shown) located within thedoorbell 330 when thereset button 359 is pressed. When thereset button 359 is pressed, it may trigger one or more functions, as described below. -
FIG. 16 is a right side cross-sectional view of the doorbell 330 without the mountingbracket 337. In the illustrated embodiment, thelens 332 is substantially coplanar with thefront surface 331F of theenclosure 331. In alternative embodiments, thelens 332 may be recessed within theenclosure 331 or may protrude outward from theenclosure 331. Thecamera 334 is coupled to a camera printed circuit board (PCB) 347, and alens 334 a of thecamera 334 protrudes through an opening in theenclosure 331. Thecamera lens 334 a may be a lens capable of focusing light into thecamera 334 so that clear images may be taken. - The
camera PCB 347 may be secured within the doorbell with any suitable fasteners, such as screws, or interference connections, adhesives, etc. Thecamera PCB 347 comprises various components that enable the functionality of thecamera 334 of thedoorbell 330, as described below. Infrared light-emitting components, such as infrared LED's 368, are coupled to thecamera PCB 347 and may be triggered to activate when a light sensor detects a low level of ambient light. When activated, the infrared LED's 368 may emit infrared light through theenclosure 331 and/or thecamera 334 out into the ambient environment. Thecamera 334, which may be configured to detect infrared light, may then capture the light emitted by the infrared LED's 368 as it reflects off objects within the camera's 334 field of view, so that the doorbell 330 can clearly capture images at night (may be referred to as “night vision”). - With continued reference to
FIG. 16 , the doorbell 330 further comprises afront PCB 346, which in the illustrated embodiment resides in a lower portion of the doorbell 330 adjacent abattery 366. Thefront PCB 346 may be secured within the doorbell 330 with any suitable fasteners, such as screws, or interference connections, adhesives, etc. Thefront PCB 346 comprises various components that enable the functionality of the audio and light components, as further described below. Thebattery 366 may provide power to the doorbell 330 components while receiving power from thespring contacts 340, thereby engaging in a trickle-charge method of power consumption and supply. Alternatively, thedoorbell 330 may draw power directly from thespring contacts 340 while relying on thebattery 366 only when thespring contacts 340 are not providing the power necessary for all functions. Still further, thebattery 366 may comprise the sole source of power for thedoorbell 330. In such embodiments, thespring contacts 340 may not be connected to a source of power. When thebattery 366 is depleted of its charge, it may be recharged, such as by connecting a power source to theconnector 360. - With continued reference to
FIG. 16 , the doorbell 330 further comprises apower PCB 348, which in the illustrated embodiment resides behind thecamera PCB 347. Thepower PCB 348 may be secured within the doorbell 330 with any suitable fasteners, such as screws, or interference connections, adhesives, etc. Thepower PCB 348 comprises various components that enable the functionality of the power and device-control components, as further described below. - With continued reference to
FIG. 16 , the doorbell 330 further comprises acommunication module 364 coupled to thepower PCB 348. Thecommunication module 364 facilitates communication with client devices in one or more remote locations, as further described below. Theconnector 360 may protrude outward from thepower PCB 348 and extend through a hole in theback plate 339. Thedoorbell 330 further comprises passive infrared (PIR)sensors 344, which are secured on or within aPIR sensor holder 343, and the assembly resides behind thelens 332. In some embodiments, thedoorbell 330 may comprise threePIR sensors 344, as further described below, but in other embodiments any number ofPIR sensors 344 may be provided. In some embodiments, one or more of thePIR sensors 344 may comprise a pyroelectric infrared sensor. ThePIR sensor holder 343 may be secured to the doorbell 330 with any suitable fasteners, such as screws, or interference connections, adhesives, etc. ThePIR sensors 344 may be any type of sensor capable of detecting and communicating the presence of a heat source within their field of view. Further, alternative embodiments may comprise one or more motion sensors either in place of or in addition to thePIR sensors 344. The motion sensors may be configured to detect motion using any methodology, such as a methodology that does not rely on detecting the presence of a heat source within a field of view. -
FIG. 17 is an exploded view of thedoorbell 330 and the mountingbracket 337 according to an aspect of the present embodiments. The mountingbracket 337 is configured to be mounted to a mounting surface (not shown) of a structure, such as a home or an office.FIG. 17 shows thefront side 337F of the mountingbracket 337. The mountingbracket 337 is configured to be mounted to the mounting surface such that theback side 337B thereof faces the mounting surface. In certain embodiments, the mountingbracket 337 may be mounted to surfaces of various composition, including, without limitation, wood, concrete, stucco, brick, vinyl siding, aluminum siding, etc., with any suitable fasteners, such as screws, or interference connections, adhesives, etc. Thedoorbell 330 may be coupled to the mountingbracket 337 with any suitable fasteners, such as screws, or interference connections, adhesives, etc. - With continued reference to
FIG. 17 , the illustrated embodiment of the mountingbracket 337 includes the terminal screws 338. The terminal screws 338 are configured to receive electrical wires adjacent the mounting surface of the structure upon which the mountingbracket 337 is mounted, so that thedoorbell 330 may receive electrical power from the structure's electrical system. The terminal screws 338 are electrically connected toelectrical contacts 377 of the mounting bracket. If power is supplied to theterminal screws 338, then theelectrical contacts 377 also receive power through the terminal screws 338. Theelectrical contacts 377 may comprise any suitable conductive material, including, without limitation, copper, and may protrude slightly from the face of the mountingbracket 337 so that they may mate with thespring contacts 340 located on theback plate 339. - With continued reference to
FIG. 17 , the mountingbracket 337 further comprises abracket PCB 349. Thebracket PCB 349 is situated outside thedoorbell 330, and is therefore configured for various sensors that measure ambient conditions, such as anaccelerometer 350, abarometer 351, ahumidity sensor 352, and a temperature sensor 353 (FIG. 18 ). The functions of these components are discussed in more detail below. Thebracket PCB 349 may be secured to the mountingbracket 337 with any suitable fasteners, such as screws, or interference connections, adhesives, etc. - With continued reference to
FIG. 17 , thefaceplate 335 may extend from the bottom of the doorbell 330 up to just below thecamera 334, and connect to theback plate 339 as described above. Thelens 332 may extend and curl partially around the side of thedoorbell 330. Theenclosure 331 may extend and curl around the side and top of thedoorbell 330, and may be coupled to theback plate 339 as described above. Thecamera 334 may protrude slightly through theenclosure 331, thereby giving it a wider field of view. The mountingbracket 337 may couple with theback plate 339 such that they contact each other at various points in a common plane of contact, thereby creating an assembly including thedoorbell 330 and the mountingbracket 337. The couplings described in this paragraph, and elsewhere, may be secured by, for example and without limitation, screws, interference fittings, adhesives, or other fasteners. Interference fittings may refer to a type of connection where a material relies on pressure and/or gravity coupled with the material's physical strength to support a connection to a different element. -
FIG. 18 is a top view andFIG. 19 is a front view of a passive infrared sensor assembly 179 including the lens 132, the passive infrared sensor holder 143, the passiveinfrared sensors 144, and a flexible power circuit 145. The passive infrared sensor holder 143 is configured to mount the passiveinfrared sensors 144 facing out through the lens 132 at varying angles, thereby allowing the passiveinfrared sensor 144 field of view to be expanded to 180° or more and also broken up into various zones, as further described below. The passive infrared sensor holder 143 may include one or more faces 178, including a center face 178C and two side faces 178S to either side of the center face 178C. With reference toFIG. 19 , each of thefaces 178 defines an opening 181 within or on which the passiveinfrared sensors 144 may be mounted. In alternative embodiments, thefaces 178 may not include openings 181, but may instead comprise solid flat faces upon which the passiveinfrared sensors 144 may be mounted. Generally, thefaces 178 may be any physical structure capable of housing and/or securing the passiveinfrared sensors 144 in place. - With reference to
FIG. 18 , the passive infrared sensor holder 143 may be secured to the rear face of the lens 132. The flexible power circuit 145 may be any material or component capable of delivering power and/or data to and from the passiveinfrared sensors 144, and may be contoured to conform to the non-linear shape of the passive infrared sensor holder 143. The flexible power circuit 145 may connect to, draw power from, and/or transmit data to and from, the power printedcircuit board 148. -
FIG. 20 is a top view of the passive infrared sensor assembly 179 illustrating the fields of view of the passiveinfrared sensors 144. In the illustrated embodiment, the side faces 178S of the passive infrared sensor holder 143 are angled at 55° facing outward from the center face 178C, and each passiveinfrared sensor 144 has a field of view of 110° . However, these angles may be increased or decreased as desired.Zone 1 is the area that is visible only to a first one of the passive infrared sensors 144-1.Zone 2 is the area that is visible only to the first passive infrared sensor 144-1 and a second one of the passive infrared sensors 144-2.Zone 3 is the area that is visible only to the second passive infrared sensor 144-2.Zone 4 is the area that is visible only to the second passive infrared sensor 144-2 and a third one of the passive infrared sensors 144-3.Zone 5 is the area that is visible only to the third passive infrared sensor 144-3. In some embodiments, thedoorbell 130 may be capable of determining the direction that an object is moving based upon which zones are triggered in a time sequence. -
FIG. 21 is a functional block diagram of the components within or in communication with thedoorbell 330, according to an aspect of the present embodiments. As described above, thebracket PCB 349 may comprise anaccelerometer 350, abarometer 351, ahumidity sensor 352, and atemperature sensor 353. Theaccelerometer 350 may be one or more sensors capable of sensing motion and/or acceleration. Thebarometer 351 may be one or more sensors capable of determining the atmospheric pressure of the surrounding environment in which thebracket PCB 349 may be located. Thehumidity sensor 352 may be one or more sensors capable of determining the amount of moisture present in the atmospheric environment in which thebracket PCB 349 may be located. Thetemperature sensor 353 may be one or more sensors capable of determining the temperature of the ambient environment in which thebracket PCB 349 may be located. As described above, thebracket PCB 349 may be located outside the housing of the doorbell 330 so as to reduce interference from heat, pressure, moisture, and/or other stimuli generated by the internal components of thedoorbell 330. - With further reference to
FIG. 21 , thebracket PCB 349 may further comprise terminal screw inserts 354, which may be configured to receive theterminal screws 338 and transmit power to theelectrical contacts 377 on the mounting bracket 337 (FIG. 17 ). Thebracket PCB 349 may be electrically and/or mechanically coupled to thepower PCB 348 through theterminal screws 338, the terminal screw inserts 354, thespring contacts 340, and theelectrical contacts 377. The terminal screws 338 may receive electrical wires located at the surface to which thedoorbell 330 is mounted, such as the wall of a building, so that the doorbell can receive electrical power from the building's electrical system. Upon theterminal screws 338 being secured within the terminal screw inserts 354, power may be transferred to thebracket PCB 349, and to all of the components associated therewith, including theelectrical contacts 377. Theelectrical contacts 377 may transfer electrical power to thepower PCB 348 by mating with thespring contacts 340. - With further reference to
FIG. 21 , thefront PCB 346 may comprise alight sensor 355, one or more light-emitting components, such as LED's 356, one ormore speakers 357, and amicrophone 358. Thelight sensor 355 may be one or more sensors capable of detecting the level of ambient light of the surrounding environment in which thedoorbell 330 may be located. LED's 356 may be one or more light-emitting diodes capable of producing visible light when supplied with power. Thespeakers 357 may be any electromechanical device capable of producing sound in response to an electrical signal input. Themicrophone 358 may be an acoustic-to-electric transducer or sensor capable of converting sound waves into an electrical signal. When activated, the LED's 356 may illuminate the light pipe 336 (FIG. 14 ). Thefront PCB 346 and all components thereof may be electrically coupled to thepower PCB 348, thereby allowing data and/or power to be transferred to and from thepower PCB 348 and thefront PCB 346. - The
speakers 357 and themicrophone 358 may be coupled to thecamera processor 370 through anaudio CODEC 361. For example, the transfer of digital audio from the user's client device 114 and thespeakers 357 and themicrophone 358 may be compressed and decompressed using theaudio CODEC 361, coupled to thecamera processor 370. Once compressed byaudio CODEC 361, digital audio data may be sent through thecommunication module 364 to thenetwork 112, routed by one ormore servers 118, and delivered to the user's client device 114. When the user speaks, after being transferred through thenetwork 112, digital audio data is decompressed byaudio CODEC 361 and emitted to the visitor via thespeakers 357. - With further reference to
FIG. 21 , thepower PCB 348 may comprise apower management module 362, a microcontroller 363 (may also be referred to as “processor,” “CPU,” or “controller”), thecommunication module 364, and power PCBnon-volatile memory 365. In certain embodiments, thepower management module 362 may comprise an integrated circuit capable of arbitrating between multiple voltage rails, thereby selecting the source of power for thedoorbell 330. Thebattery 366, thespring contacts 340, and/or theconnector 360 may each provide power to thepower management module 362. Thepower management module 362 may have separate power rails dedicated to thebattery 366, thespring contacts 340, and theconnector 360. In one aspect of the present disclosure, thepower management module 362 may continuously draw power from thebattery 366 to power thedoorbell 330, while at the same time routing power from thespring contacts 340 and/or theconnector 360 to thebattery 366, thereby allowing thebattery 366 to maintain a substantially constant level of charge. Alternatively, thepower management module 362 may continuously draw power from thespring contacts 340 and/or theconnector 360 to power thedoorbell 330, while only drawing from thebattery 366 when the power from thespring contacts 340 and/or theconnector 360 is low or insufficient. Still further, thebattery 366 may comprise the sole source of power for thedoorbell 330. In such embodiments, thespring contacts 340 may not be connected to a source of power. When thebattery 366 is depleted of its charge, it may be recharged, such as by connecting a power source to theconnector 360. Thepower management module 362 may also serve as a conduit for data between theconnector 360 and themicrocontroller 363. - With further reference to
FIG. 21 , in certain embodiments themicrocontroller 363 may comprise an integrated circuit including a processor core, memory, and programmable input/output peripherals. Themicrocontroller 363 may receive input signals, such as data and/or power, from thePIR sensors 344, thebracket PCB 349, thepower management module 362, thelight sensor 355, themicrophone 358, and/or thecommunication module 364, and may perform various functions as further described below. When themicrocontroller 363 is triggered by thePIR sensors 344, themicrocontroller 363 may be triggered to perform one or more functions. When thelight sensor 355 detects a low level of ambient light, thelight sensor 355 may trigger themicrocontroller 363 to enable “night vision,” as further described below. Themicrocontroller 363 may also act as a conduit for data communicated between various components and thecommunication module 364. - With further reference to
FIG. 21 , thecommunication module 364 may comprise an integrated circuit including a processor core, memory, and programmable input/output peripherals. Thecommunication module 364 may also be configured to transmit data wirelessly to a remote network device, and may include one or more transceivers (not shown). The wireless communication may comprise one or more wireless networks, such as, without limitation, Wi-Fi, cellular, Bluetooth, and/or satellite networks. Thecommunication module 364 may receive inputs, such as power and/or data, from thecamera PCB 347, themicrocontroller 363, thebutton 333, thereset button 359, and/or the power PCBnon-volatile memory 365. When thebutton 333 is pressed, thecommunication module 364 may be triggered to perform one or more functions. When thereset button 359 is pressed, thecommunication module 364 may be triggered to erase any data stored at the power PCBnon-volatile memory 365 and/or at thecamera PCB memory 369. Thecommunication module 364 may also act as a conduit for data communicated between various components and themicrocontroller 363. The power PCBnon-volatile memory 365 may comprise flash memory configured to store and/or transmit data. For example, in certain embodiments the power PCBnon-volatile memory 365 may comprise serial peripheral interface (SPI) flash memory. - With further reference to
FIG. 21 , thecamera PCB 347 may comprise components that facilitate the operation of thecamera 334. For example, animager 371 may comprise a video recording sensor and/or a camera chip. In one aspect of the present disclosure, theimager 371 may comprise a complementary metal-oxide semiconductor (CMOS) array, and may be capable of recording high definition (e.g., 1080p or better) video files. Acamera processor 370 may comprise an encoding and compression chip. In some embodiments, thecamera processor 370 may comprise a bridge processor. Thecamera processor 370 may process video recorded by theimager 371 and audio recorded by themicrophone 358, and may transform this data into a form suitable for wireless transfer by thecommunication module 364 to a network. Thecamera PCB memory 369 may comprise volatile memory that may be used when data is being buffered or encoded by thecamera processor 370. For example, in certain embodiments thecamera PCB memory 369 may comprise synchronous dynamic random-access memory (SD RAM). IR LED's 368 may comprise light-emitting diodes capable of radiating infrared light. IR cutfilter 367 may comprise a system that, when triggered, configures theimager 371 to see primarily infrared light as opposed to visible light. When thelight sensor 355 detects a low level of ambient light (which may comprise a level that impedes the performance of theimager 371 in the visible spectrum), the IR LED's 368 may shine infrared light through the doorbell 330 enclosure out to the environment, and the IR cutfilter 367 may enable theimager 371 to see this infrared light as it is reflected or refracted off of objects within the field of view of the doorbell. This process may provide the doorbell 330 with the “night vision” function mentioned above. - Some of the present embodiments may comprise computer vision for one or more aspects, such as object and/or facial recognition. Computer vision includes methods for acquiring, processing, analyzing, and understanding images and, in general, high-dimensional data from the real world in order to produce numerical or symbolic information, e.g. in the form of decisions. Computer vision seeks to duplicate the abilities of human vision by electronically perceiving and understanding an image. Understanding in this context means the transformation of visual images (the input of the retina) into descriptions of the world that can interface with other thought processes and elicit appropriate action. This image understanding can be seen as the disentangling of symbolic information from image data using models constructed with the aid of geometry, physics, statistics, and learning theory. Computer vision has also been described as the enterprise of automating and integrating a wide range of processes and representations for vision perception. As a scientific discipline, computer vision is concerned with the theory behind artificial systems that extract information from images. The image data can take many forms, such as video sequences, views from multiple cameras, or multi-dimensional data from a scanner. As a technological discipline, computer vision seeks to apply its theories and models for the construction of computer vision systems.
- One aspect of computer vision comprises determining whether or not the image data contains some specific object, feature, or activity. Different varieties of computer vision recognition include: Object Recognition (also called object classification)—One or several pre-specified or learned objects or object classes can be recognized, usually together with their 2D positions in the image or 3D poses in the scene. Identification—An individual instance of an object is recognized. Examples include identification of a specific person's face or fingerprint, identification of handwritten digits, or identification of a specific vehicle. Detection—The image data are scanned for a specific condition. Examples include detection of possible abnormal cells or tissues in medical images or detection of a vehicle in an automatic road toll system. Detection based on relatively simple and fast computations is sometimes used for finding smaller regions of interesting image data that can be further analyzed by more computationally demanding techniques to produce a correct interpretation.
- Several specialized tasks based on computer vision recognition exist, such as: Optical Character Recognition (OCR)—Identifying characters in images of printed or handwritten text, usually with a view to encoding the text in a format more amenable to editing or indexing (e.g. ASCII). 2D Code Reading—Reading of 2D codes such as data matrix and QR codes. Facial Recognition. Shape Recognition Technology (SRT)—Differentiating human beings (e.g. head and shoulder patterns) from objects.
- Typical functions and components (e.g. hardware) found in many computer vision systems are described in the following paragraphs. The present embodiments may include at least some of these aspects. For example, with reference to
FIG. 3 , embodiments of the present A/V recording andcommunication doorbell 130 may include acomputer vision module 163. Thecomputer vision module 163 may include any of the components (e.g. hardware) and/or functionality described herein with respect to computer vision, including, without limitation, one or more cameras, sensors, and/or processors. In some of the present embodiments, themicrophone 150, thecamera 154, and/or theimaging processor 240 may be components of thecomputer vision module 163. - Image acquisition—A digital image is produced by one or several image sensors, which, besides various types of light-sensitive cameras, may include range sensors, tomography devices, radar, ultra-sonic cameras, etc. Depending on the type of sensor, the resulting image data may be a 2D image, a 3D volume, or an image sequence. The pixel values may correspond to light intensity in one or several spectral bands (gray images or color images), but can also be related to various physical measures, such as depth, absorption or reflectance of sonic or electromagnetic waves, or nuclear magnetic resonance.
- Pre-processing—Before a computer vision method can be applied to image data in order to extract some specific piece of information, it is usually beneficial to process the data in order to assure that it satisfies certain assumptions implied by the method. Examples of pre-processing include, but are not limited to re-sampling in order to assure that the image coordinate system is correct, noise reduction in order to assure that sensor noise does not introduce false information, contrast enhancement to assure that relevant information can be detected, and scale space representation to enhance image structures at locally appropriate scales.
- Feature extraction—Image features at various levels of complexity are extracted from the image data. Typical examples of such features are: Lines, edges, and ridges; Localized interest points such as corners, blobs, or points; More complex features may be related to texture, shape, or motion.
- Detection/segmentation—At some point in the processing a decision may be made about which image points or regions of the image are relevant for further processing. Examples are: Selection of a specific set of interest points; Segmentation of one or multiple image regions that contain a specific object of interest; Segmentation of the image into nested scene architecture comprising foreground, object groups, single objects, or salient object parts (also referred to as spatial-taxon scene hierarchy).
- High-level processing—At this step, the input may be a small set of data, for example a set of points or an image region that is assumed to contain a specific object. The remaining processing may comprise, for example: Verification that the data satisfy model-based and application-specific assumptions; Estimation of application-specific parameters, such as object pose or object size; Image recognition—classifying a detected object into different categories; Image registration—comparing and combining two different views of the same object.
- Decision making—Making the final decision required for the application, for example match/no-match in recognition applications.
- One or more of the present embodiments may include a vision processing unit (not shown separately, but may be a component of the computer vision module 163). A vision processing unit is an emerging class of microprocessor; it is a specific type of AI (artificial intelligence) accelerator designed to accelerate machine vision tasks. Vision processing units are distinct from video processing units (which are specialized for video encoding and decoding) in their suitability for running machine vision algorithms such as convolutional neural networks, SIFT, etc. Vision processing units may include direct interfaces to take data from cameras (bypassing any off-chip buffers), and may have a greater emphasis on on-chip dataflow between many parallel execution units with scratchpad memory, like a manycore DSP (digital signal processor). But, like video processing units, vision processing units may have a focus on low precision fixed point arithmetic for image processing.
- Some of the present embodiments may use facial recognition hardware and/or software, as a part of the computer vision system. Various types of facial recognition exist, some or all of which may be used in the present embodiments.
- Some face recognition algorithms identify facial features by extracting landmarks, or features, from an image of the subject's face. For example, an algorithm may analyze the relative position, size, and/or shape of the eyes, nose, cheekbones, and jaw. These features are then used to search for other images with matching features. Other algorithms normalize a gallery of face images and then compress the face data, only saving the data in the image that is useful for face recognition. A probe image is then compared with the face data. One of the earliest successful systems is based on template matching techniques applied to a set of salient facial features, providing a sort of compressed face representation.
- Recognition algorithms can be divided into two main approaches, geometric, which looks at distinguishing features, or photometric, which is a statistical approach that distills an image into values and compares the values with templates to eliminate variances.
- Popular recognition algorithms include principal component analysis using eigenfaces, linear discriminant analysis, elastic bunch graph matching using the Fisherface algorithm, the hidden Markov model, the multilinear subspace learning using tensor representation, and the neuronal motivated dynamic link matching.
- Further, a newly emerging trend, claimed to achieve improved accuracy, is three-dimensional face recognition. This technique uses 3D sensors to capture information about the shape of a face. This information is then used to identify distinctive features on the surface of a face, such as the contour of the eye sockets, nose, and chin.
- One advantage of 3D face recognition is that it is not affected by changes in lighting like other techniques. It can also identify a face from a range of viewing angles, including a profile view. Three-dimensional data points from a face vastly improve the precision of face recognition. 3D research is enhanced by the development of sophisticated sensors that do a better job of capturing 3D face imagery. The sensors work by projecting structured light onto the face. Up to a dozen or more of these image sensors can be placed on the same CMOS chip—each sensor captures a different part of the spectrum.
- Another variation is to capture a 3D picture by using three tracking cameras that point at different angles; one camera pointing at the front of the subject, a second one to the side, and a third one at an angle. All these cameras work together to track a subject's face in real time and be able to face detect and recognize.
- Another emerging trend uses the visual details of the skin, as captured in standard digital or scanned images. This technique, called skin texture analysis, turns the unique lines, patterns, and spots apparent in a person's skin into a mathematical space.
- Another form of taking input data for face recognition is by using thermal cameras, which may only detect the shape of the head and ignore the subject accessories such as glasses, hats, or make up.
- Further examples of automatic identification and data capture (AIDC) and/or computer vision that can be used in the present embodiments to verify the identity and/or authorization of a person include, without limitation, biometrics. Biometrics refers to metrics related to human characteristics. Biometrics authentication (or realistic authentication) is used in various forms of identification and access control. Biometric identifiers are the distinctive, measurable characteristics used to label and describe individuals. Biometric identifiers can be physiological characteristics and/or behavioral characteristics. Physiological characteristics may be related to the shape of the body. Examples include, but are not limited to, fingerprints, palm veins, facial recognition, three-dimensional facial recognition, skin texture analysis, DNA, palm prints, hand geometry, iris recognition, retina recognition, and odor/scent recognition. Behavioral characteristics may be related to the pattern of behavior of a person, including, but not limited to, typing rhythm, gait, and voice recognition.
- The present embodiments may use any one, or any combination of more than one, of the foregoing biometrics to identify and/or authenticate a person who is either suspicious or who is authorized to take certain actions with respect to a property or expensive item of collateral. For example, the
computer vision module 163, and/or thecamera 154 and/or theprocessor 160 may receive information about the person using any one, or any combination of more than one, of the foregoing biometrics. - As discussed above, one aspect of the present embodiments includes the realization that as A/V recording and communication devices continue to become more prevalent, leveraging the functionalities of these devices (e.g., video doorbells, security cameras, etc.) by persons other than the owners/users of the A/V recording and communication devices may prove increasingly useful. Current A/V recording and communication devices, other than the present embodiments, sometimes do not allow persons other than the owner/user of the A/V recording and communication device access to the device's functionalities (e.g., the camera, the speaker, etc.). As a result, there may be missed opportunities for persons other than the owners/users of the A/V recording and communication devices to leverage these functionalities to provide safety, security, and peace of mind. For example, a neighborhood may include a plurality of A/V recording and communication devices installed at various homes, and the neighborhood may be dark and/or dangerous. As a result, a person walking through the neighborhood may desire to view video being recorded in a field of view of one or more of the A/V recording and communication devices in order to determine if there is any suspicious activity or suspicious persons in the neighborhood.
- The present embodiments solve this problem by leveraging the functionality of A/V recording and communication devices, such as A/V recording and communication doorbells, to allow access to the A/V recording and communication devices by users of client devices in proximity to the A/V recording and communication devices. By allowing this access, the users of the client devices may be able to determine if any suspicious activity and/or persons are present, and in response, take the appropriate action. For example, the users of the client devices may notify law enforcement, leave the area, signal for help, signal an alarm, and/or speak to a suspicious person through a speaker of one or more of the A/V recording and communication devices. Ultimately, because the users of the client devices in proximity to the A/V recording and communication devices may be able to leverage the functionalities of the devices, the safety of the users and the neighborhood, in addition to the overall public safety, may be increased.
- For example, in some of the present embodiments, a client device, in response to entering a proximity zone of an audio/video (A/V) recording and communication device, requests, by a processor of the client device using a communication module, access to a camera of the A/V recording and communication device; in response to the request for access, receives, by the processor using the communication module, from the camera, image data being recorded by the camera in a field of view of the camera; and displays, by the processor on the display, the image data.
- Now referring to
FIG. 22 ,FIG. 22 is a functional block diagram illustrating asystem 400 for communicating in a network according to various aspects of the present disclosure. Thesystem 400 may include one or more audio/video (A/V) recording andcommunication devices 402 configured to access a user'snetwork 408 to connect to a network (Internet/PSTN) 410. The one or more A/V recording andcommunication devices 402 may include any or all of the components and/or functionality of the A/V recording and communication device 100 (FIGS. 1-2 ), the A/V recording and communication doorbell 130 (FIGS. 3-13 ), and/or the A/V recording and communication doorbell 330 (FIGS. 14-21 ). As discussed herein, the present disclosure provides numerous examples of methods and systems including A/V recording andcommunication devices 402, such as A/V recording and communication doorbells, but the present embodiments are equally applicable for A/V recording andcommunication devices 402 other than doorbells. For example, the present embodiments may include one or more A/V recording and communication security cameras and/or A/V recording and communication security floodlights instead of, or in addition to, one or more A/V recording and communication doorbells. An example A/V recording and communication security camera may include substantially all of the structure and functionality of thedoorbell 130, but without thefront button 148, thebutton actuator 228, and/or thelight pipe 232. - The user's
network 408 may include any or all of the components and/or functionality of the user'snetwork 110 described herein. The network (Internet/PSTN) 410 may include any or all of the components and/or functionality of the network (Internet/PSTN) 112 described herein. Thesystem 400 may also include one ormore client devices communication device 402. In some of the present embodiments, theclient devices client devices client devices client devices communication device 402. In other words, the user/owner of the client device(s) 404, 406 may not also use/own a A/V recording andcommunication device 402. - The
system 400 may also include one ormore client devices 407, which in various embodiments may be configured to be in communication with the one or more A/V recording andcommunication devices 402. The one ormore client devices 407 may be in network communication with the A/V recording andcommunication device 402 over the network (Internet/PSTN) 410 and/or the user'snetwork 408. In some of the present embodiments, the one ormore client devices 407 may be connected to the user'snetwork 408 and communicate with the A/V recording andcommunication device 402 directly over the user'snetwork 408. In further embodiments, the one ormore client devices 407 may be directly connected to the A/V recording and communication device 402 (e.g., where the A/V recording andcommunication device 402 generates an ad hoc network), and thus communicate directly with the A/V recording andcommunication device 402 without using the network (Internet/PSTN) 410 and/or the user'snetwork 408. In some of the present embodiments, theclient devices 407 may be configured to be in network communication with one or more backend devices, such as the backend server(s) 430. For example, theclient devices 407 may communicate with the one or more backend devices to access the image data 460 (FIG. 23 ) of the A/V recording and communication device 402 (e.g., where theimage data 460 is stored on the backend device, such as the backend server 430). Theclient devices 407 may comprise, for example, a mobile phone such as a smartphone, or a computing device such as a tablet computer, a laptop computer, a desktop computer, etc. Theclient devices 407 may include any or all of the components and/or functionality of the client device 114 and/or the client device 800 described herein. Theclient devices 407 may not be associated with any A/V recording and communication devices, including the A/V recording andcommunication device 402. In some of the present embodiments, theclient devices 407 may be associated with an A/V recording and communication device that is not connected to and/or in communication with the user'snetwork 408. In addition, the user/owner of the A/V recording andcommunication device 402 may not be the user/owner of theclient device 407. - With further reference to
FIG. 22 , thesystem 400 may also include various backend devices such as (but not limited to)storage devices 432,backend servers 430, andbackend APIs 428 that may be in network communication with the A/V recording andcommunication device 402, theclient devices client devices 407. In some embodiments, thestorage devices 432 may be a separate device from the backend servers 430 (as illustrated) or may be an integral component of thebackend servers 430. Thestorage devices 432 may be similar in structure and/or function to the storage device 116 (FIG. 1 ). In addition, in some embodiments, thebackend servers 430 andbackend APIs 428 may be similar in structure and/or function to theserver 118 and the backend API 120 (FIG. 1 ), respectively. -
FIG. 23 is a functional block diagram illustrating an embodiment of the A/V recording andcommunication device 402 according to various aspects of the present disclosure. The A/V recording andcommunication device 402 may comprise aprocessing module 446 that is operatively connected to acamera 444, amicrophone 446, aspeaker 448, amotion sensor 474, and acommunication module 450. Theprocessing module 446 may comprise aprocessor 452,volatile memory 454, andnon-volatile memory 456 that includes adevice application 458. In various embodiments, thedevice application 458 may configure theprocessor 452 to captureimage data 460 using thecamera 444, audio data 462 using themicrophone 446, and/ormotion data 468 using thecamera 444 and/or themotion sensor 474. In some embodiments, thedevice application 458 may also configure theprocessor 452 to generatetext data 464 describing theimage data 460, such as in the form of metadata, for example. In some of the present embodiments, thedevice application 458 may also configure theprocessor 452 to generate theproximity zone 470 and/or monitor theproximity zone 470 using thecommunication module 450. In addition, thedevice application 458 may configure theprocessor 452 to transmit theimage data 460, the audio data 462, themotion data 468, and/or thetext data 464 to theclient device client device 407, and/or thebackend server 430 using thecommunication module 450. In some of the present embodiments, theprocessor 452 may further configure thedevice application 458 to transmit the communication signals 479 and/or receive the communication signals 481 (FIG. 25 ) from theclient device 407 and measure the signal strength (e.g., Received Signal Strength Indication (RSSI)) of the communication signals 481. - In various embodiments, the
device application 458 may also configure theprocessor 452 to generate and transmit an output signal 466 that may include theimage data 460, the audio data 462, thetext data 464, theaccess request 474, and/or themotion data 468. In some of the present embodiments, the output signal 466 may be transmitted to the backend server(s) 430 using thecommunication module 450, and the backend server(s) 430 may transmit (or forward) the output signal 466 to theclient device client device 407. In other embodiments, the output signal 466 may be transmitted directly to theclient device client device 407. In some of the present embodiments, thedevice application 458 may configure theprocessor 452 to receive the output signal 467 from theclient device 407 using thecommunication module 450, where the output signal 467 may include the access request 475, the location data 477 (e.g., the current physical location of the client device 407), and/or the communication signals 479 generated by theclient device 407. - In further reference to
FIG. 23 , theimage data 460 may comprise image sensor data such as (but not limited to) exposure values and data regarding pixel values for a particular sized grid. Further, theimage data 460 may comprise converted image sensor data for standard image file formats such as (but not limited to) JPEG, JPEG 2000, TIFF, BMP, or PNG. In addition, theimage data 460 may also comprise data related to the still image, video, or combination thereof, included in theimage data 460. Such data may include (but is not limited to) image sequences, frame rates, and the like. Moreover, theimage data 460 may include data that is analog, digital, compressed, uncompressed, and/or in vector formats. - The
image data 460 may include still images, live video, and/or pre-recorded video. Theimage data 460 may be recorded by thecamera 444 in a field of view of thecamera 444. Theprocessor 452 may be configured to transmit the image data 460 (e.g., as live streaming video) to theclient device image data 460 may take on various forms and formats as appropriate to the requirements of a specific application in accordance with the present embodiments. As described herein, the term “record” may also be referred to as “capture” as appropriate to the requirements of a specific application in accordance with the present embodiments. - In further reference to
FIG. 23 , themotion data 468 may comprise motion sensor data generated in response to motion events. For example, in embodiments using amotion sensor 474, themotion data 468 may include an amount or level of a data type generated by themotion sensor 474. For example, in embodiments that use PIRs, themotion data 468 may include voltage data generated by themotion sensor 474 in response to the presence of infrared radiation. In some of the present embodiments, themotion data 468 may also comprise time-based and/or location-based information such as the amount of time a motion event is detected and/or the location of the motion event in the field of view of the motion sensor 474 (e.g., Zones 1-5 (FIG. 20 ), the location within one of the Zones 1-5, and/or the proximity to the motion sensor 474). For example, in embodiments that use PIRs, themotion data 468 may include the amount of time an increase in voltage is detected based on the presence of infrared radiation indicative of a motion event. In other embodiments, dependent on the type ofmotion sensor 474 implemented in a given embodiment, themotion data 468 may include the data type (e.g., voltage) generated specific to the type of motion sensor 474 (e.g., PIR, microwave, acoustic, etc.). - The
motion data 468 may further include an estimated speed and/or direction data of the person and/or object that caused the motion event. For example, themotion data 468 may include an estimated speed of a person and/or object passing in a field of view of themotion sensor 474. For another example, themotion data 468 may include a direction that a person and/or object in front of themotion sensor 474 is traveling, such as toward or away from the A/V recording andcommunication device 402. - In some of the present embodiments, such as those where the A/V recording and communication device is similar to that of the A/V recording and
communication doorbell 130 ofFIGS. 3-13 , themotion data 468 may be generated by thecamera 444. In such embodiments, the A/V recording andcommunication device 402 may not have a motion sensor 474 (as illustrated by the dashed lines around themotion sensor 474 inFIG. 23 ). As such, the detection of a motion event, the determination of whether a motion event is caused by the movement of a person in a field of view of the A/V recording andcommunication device 402, and/or the speed and/or location of a person and/or object in the field of view of the A/V recording andcommunication device 402 may be determined using themotion data 468 generated by thecamera 444. In such embodiments, themotion data 468 may include differences between successive frames (e.g., pixels) of theimage data 460, where the differences may be the result of motion in the field of view of thecamera 444, for example. - With further reference to
FIG. 23 , the location data 476 may include the location of the A/V recording andcommunication device 402. The location data 476 may be based on global positioning system (GPS) data, Wi-Fi positioning system (WPS) data, the known location of the Access Point (e.g., router) that the A/V recording andcommunication device 402 is using to access the user'snetwork 408, the IP Address of the A/V recording andcommunication device 402, or the like. The location of the A/V recording andcommunication device 402 may be determined from the location data 476 during a set-up/activation process of the device 402 (and during any subsequent set-up/activation process). - In some of the present embodiments, the location data 476 may include the
proximity zone 470. For example, theproximity zone 470 may be an area, region, etc. where, when theclient device 407 enters theproximity zone 470, theclient device 407 may be able to access and/or communicate with the A/V recording and communication device 402 (e.g., access thecamera 444 and/or access the speaker 446). Theproximity zone 470 may or may not include the location of the A/V recording andcommunication device 402, depending on the embodiment. For example, theproximity zone 470 may include a portion of the street on which the house having the A/V recording andcommunication device 402 is located, but may not include the house and/or the property the house sits on, so as not to encourage the user of theclient device 407 to enter the property where the A/V recording andcommunication device 402 is located. In other embodiments, theproximity zone 470 may include the A/V recording andcommunication device 402 along with other A/V recording and communication devices (e.g., similar to the illustration ofFIG. 41 ). In such embodiments, theproximity zone 470 may be defined by a portion of a street, a neighborhood, a town, etc., and the A/V recording and communication devices within theproximity zone 470 may share the same orsimilar proximity zone 470. In some of the present embodiments, theproximity zone 470 may be defined by the user of theclient device proximity zone 470 may be defined by the settings of the A/V recording and communication device 402 (e.g., as default settings). - In various embodiments, the user of the
client device communication device 402, for example, whereby the A/V recording andcommunication device 402 may generate and monitor theproximity zone 470 and allow access to the A/V recording andcommunication device 402 in response to the client device 407 (and/or other client devices) entering theproximity zone 470. In various embodiments, theclient device 407 may transmit an access request 475 to the A/V recording andcommunication device 402 when inside of theproximity zone 470 to request access to the A/V recording andcommunication device 402. In response, the user of theclient device FIG. 25 ) from the A/V recording and communication device 402 (and/or the backend server 430) and determine whether or not to accept the access request 475 from theclient device 407. In other embodiments, theclient device 407 may be automatically allowed access, or may be allowed access based on the settings of the A/V recording and communication device 402 (e.g., user settings, default settings, etc.). For example, in some of the present embodiments, theclient device 407 may be allowed access to the A/V recording andcommunication device 402 only if theclient device 407 is associated with another A/V recording and communication device (e.g., part of a network of users/owners of A/V recording and communication devices). In other words, if the user of theclient device 407 is also a user/owner of an A/V recording and communication device (e.g., at a home of the user of the client device 407), and/or the user of theclient device 407 has opted in to allow access to his or her A/V recording andcommunication device 402, theclient device 407 may be allowed access to the A/V recording andcommunication device 402. - With further reference to
FIG. 23 , the communication signals 479 may be transmitted by the A/V recording and communication device 402 (e.g., within the proximity zone 470). In some of the present embodiments, the communication signals 481 may be transmitted by the client device 407 (FIG. 25 ) to the A/V recording andcommunication device 402. The communication signals 479 may include theaccess request 474 from the A/V recording andcommunication device 402, such that when theclient device 407 enters theproximity zone 470, theclient device 407 receives the communication signals 479 including theaccess request 474. In response, the user of theclient device 407 may accept theaccess request 474 and access the A/V recording andcommunication device 402. Alternatively, theclient device 407 may automatically (without user intervention) accept theaccess request 474 and access the A/V recording andcommunication device 402. In some of the present embodiments, the communication signals 479 may be received by the client device 407 (and/or other client devices), and in response, theclient device 407 may transmit the location data 477 of theclient device 407 to the A/V recording and communication device 402 (and/or the backend server 430) for comparing against theproximity zone 470 to determine if theclient device 407 is within theproximity zone 470. Once it is determined that theclient device 407 is within theproximity zone 470, the A/V recording andcommunication device 402 may transmit theaccess request 474 to theclient device 407 to establish connection/communication with the client device 407 (in some embodiments, via the backend server 430). - In other embodiments, the A/V recording and
communication device 402 may receive the communication signals 481 from theclient device 407, where the communication signals 481 may include the access request 475 and/or the location data 477. In such embodiments, the A/V recording and communication device 402 (and/or the backend server 430) may compare the location data 477 of theclient device 407 to theproximity zone 470 to determine if theclient device 407 is within theproximity zone 470. If it is determined that theclient device 407 is within theproximity zone 470, theclient device 407 may be allowed access to the A/V recording andcommunication device 402. - In some of the present embodiments, as described in greater detail below, the communication signals 479, 481 may be used for defining the
proximity zone 470. For example, the communication signals 479, 481 may include Wi-Fi, Bluetooth, ZigBee, and/or other signal types. In some embodiments, for example, the Received Signal Strength Indication (RSSI) of the communication signals 479, 481 may define the proximity zone 470 (because RSSI values may be indicative of a distance from the device transmitting the communication signals 479, 481). For example, the A/V recording andcommunication device 402 may transmit the communication signals 479 and theclient device 407 may receive the communication signals 479 and analyze the communication signals 479 to determine the RSSI values of the communication signals 479. Theclient device 407 may then transmit the RSSI values of the communication signals 479 to the A/V recording and communication device 402 (and/or the backend server 430), and the A/V recording and communication device 402 (and/or the backend server 430) may compare the RSSI values to the RSSI values that define the proximity zone 470 (e.g., Bluetooth RSSI values greater than −70 dBm on a −100-0 scale) to determine if theclient device 470 is within theproximity zone 470. In some of the present embodiments, theclient device 407 may transmit the communication signals 481 (e.g., Bluetooth, Wi-Fi (e.g., acting as a mobile hotspot), ZigBee, and/or other signal types) to the A/V recording andcommunication device 402 and the A/V recording andcommunication device 402 may analyze the communication signals 481 to determine the RSSI values of the communication signals 481. Once the RSSI values of the communication signals 481 are determined, the A/V recording and communication device 402 (and/or the backend server 430) may determine if theclient device 407 is within theproximity zone 470. - In embodiments where the RSSI values are measured, the scale used to determine the RSSI values may be different dependent on the manufacturer of the Wi-Fi chip, Bluetooth chip, ZigBee chip, or other signal type chip. For example, one Bluetooth chip manufacturer may have an RSSI scale of −100-0 dBm while another Bluetooth Chip manufacturer may have an RSSI scale of −200-0 dBm. In embodiments where the A/V recording and
communication device 402 is measuring the RSSI values of the communication signals 481 received from theclient device 407, the RSSI scale of the chip from the A/V recording andcommunication device 402 may be known, and theproximity zone 470 may be defined based on the known RSSI scale. However, in embodiments where theclient device 407 is measuring the RSSI of the communication signals 479 from the A/V recording andcommunication device 402, theprocessor 534 of theclient device 407 may program theclient application 540 to determine an identification of the chip of theclient device 407 and/or the RSSI scale of the particular chip of theclient device 407. In response, theclient device 407 may transmit the identification of the chip and/or the RSSI scale along with the RSSI values of the communication signals 479 from the A/V recording andcommunication device 402 to the A/V recording andcommunication device 402 and/or thebackend server 430. In such embodiments, the RSSI values may be normalized, such as by converting the RSSI values to a percentage in view of the RSSI scale, and the percentage may be used to define theproximity zone 470. In another example, an RSSI database may be stored on the A/V recording andcommunication device 402 and/or thebackend server 430, and theclient device 407 may transmit the RSSI values and an identification of the chip and/or the RSSI scale to the A/V recording andcommunication device 402 and/or thebackend server 430 to be compared against the RSSI database. In response to comparing the identification of the chip and/or the RSSI scale to the RSSI database, the RSSI values that define theproximity zone 470 may be determined in view of the identification of the chip and/or the RSSI scale. The RSSI values may then be compared to the RSSI values that define theproximity zone 470 to determine if theclient device 407 is within theproximity zone 470. - In some of the present embodiments, the communication signals 479, 481 may include signals generated in Low Power Wide Area Networks (LPWAN) such as Long Range Wide Area Network (LoRaWAN™) devices. In such embodiments, location data 476, 477 of the A/V recording and
communication device 402 and/or theclient device 407 may be based on the communication signals 479, 481 from LPWANs. For example, the A/V recording andcommunication device 402 and/or thebackend server 430 may be in communication with and/or include a LPWAN device (e.g., a concentrator or gateway, such as a LoRa® gateway) configured to operate in LoRaWANs™ and/or other LPWANs. In some of the present embodiments, the LPWAN device may be included in the Access Point (e.g., router) that the A/V recording andcommunication device 402 is connected. The LPWAN device may be configured to detect the presence and/or location of devices that include an LPWAN sensor (e.g., a LoRa® RF sensor), which in some embodiments, may be theclient device 407 and/or the A/V recording andcommunication device 402. Ultimately, in embodiments that use LPWAN technology, the communication signals 479, 481 (e.g., LoRa® RF signals transmitted by the LoRa® RF sensor) may be received by the LPWAN device and analyzed (e.g., by the LPWAN device, thebackend server 430, etc.) to determine the location data 476, 477 of theclient device 407 and/or the A/V recording andcommunication device 402. The location data 476, 477 may then be used by the A/V recording andcommunication device 402 and/or thebackend server 430 to determine if theclient device 407 is within theproximity zone 470. -
FIG. 24 is a functional block diagram illustrating one embodiment of the backend server(s) 430 according to various aspects of the present disclosure. The backend server(s) 430 may comprise aprocessing module 500 including aprocessor 502,volatile memory 504, anetwork interface 520, andnon-volatile memory 506. Thenetwork interface 520 may allow the backend server(s) 430 to access and communicate with devices connected to the network (Internet/PSTN) 410. Thenon-volatile memory 506 may include aserver application 508 that configures theprocessor 502 to receive theimage data 460, the audio data 462, thetext data 464, themotion data 468, the location data 476, 477, the access requests 474, 475, theproximity zone 470, and/or information related to the communication signals 479, 481 from the A/V recording andcommunication device 402 and/or the client device 407 (e.g., in the output signal 466, 467). - In further reference to
FIG. 24 , thenon-volatile memory 506 may also includesource identifying data 510 that may be used to identify the A/V recording andcommunication device 402, theclient devices client device 407. In some of the present embodiments, thesource identifying data 410 may include (and/or be used in combination with) the location data 476, 477. For example, identifying the A/V recording andcommunication device 402 may include determining the location of the A/V recording andcommunication device 402 and/or the correspondingproximity zone 470 of thedevice 402 based on the location data 476. In response to determining theproximity zone 470, a determination of whichclient devices 407 will receive theimage data 460 may be made. In some embodiments, theserver application 508 may further configure theprocessor 502 to generate and transmit a report signal (not shown) to a third-party client device (not shown), which may be associated with a law enforcement agency, for example. The report signal sent to the law enforcement agency may include information indicating an approximate location of where theimage data 460 was captured, which may assist the law enforcement agency with apprehending the criminal perpetrator shown in theimage data 460. - In some of the present embodiments, the
backend server 430 may determine theproximity zone 470 and/or the location data 476 associated with theproximity zone 470. In such embodiments, thebackend server 430 may also receive the location data 477 of theclient device 407 and compare the location data 477 to theproximity zone 470 to determine if theclient device 407 is within theproximity zone 470. In some of the present embodiments, thebackend server 430 may receive the location data 476 of the A/V recording andcommunication device 402 to determine the location (e.g., geographical coordinates) of the A/V recording andcommunication device 402. Thebackend server 430 may use this information, and the information pertaining to the proximity zone 470 (e.g., size, shape, etc.), to determine the location data 476 (e.g., geographical coordinates) of theproximity zone 470. In such embodiments, thebackend server 430 may transmit theproximity zone 470 and/or location data 476 to the A/V recording andcommunication device 402, or may analyze theproximity zone 470 locally on thebackend server 430. - In some of the present embodiments, such as illustrated in
FIG. 41 , theproximity zone 470 may not be defined based on a location of a single A/V recording andcommunication device 402, but may be defined by a region (e.g., a street, a neighborhood, a town, etc.). In such embodiments, thebackend server 430 may receive the location data 476 of the A/V recording andcommunication device 402 and analyze the location data 476 to determine if the A/V recording andcommunication device 402 is within a proximity zone 470 (such as the A/V recording andcommunication device 724 located within theproximity zone 716 ofFIG. 41 ). In such embodiments, the backend server 430 (and/or the A/V recording and communication device 402) may analyze the location data 477 of the client device 407 (and/or other client devices) to determine if theclient device 407 is within theproximity zone 470, and theclient device 407 may be allowed access to each of the A/V recording andcommunication devices 402 within theproximity zone 470. - In one embodiment, and as described below, the backend server(s) 430 may be configured to, in response to the
client device 407 entering theproximity zone 470 of the A/V recording andcommunication device 402, receive, from theclient device 407, an access request 475 to allow theclient device 407 access to thecamera 444 of the A/V recording andcommunication device 402; in response to receiving the access request 475, transmit the access request 475 to the A/V recording andcommunication device 402; in response to transmitting the access request 475, receive, from the A/V recording andcommunication device 402, theimage data 460 being recorded by thecamera 444 of the A/V recording andcommunication device 402 in a field of view of thecamera 444; and in response to receiving theimage data 460, transmitting theimage data 460 to theclient device 407. - Now referring to
FIG. 25 ,FIG. 25 is a functional block diagram illustrating one embodiment of aclient device 407 according to various aspects of the present disclosure. Theclient device 407 may comprise aprocessing module 532 that is operatively connected to aninput interface 524, amicrophone 527, aspeaker 528, and acommunication module 530. Theclient device 407 may further comprise a camera (not shown) operatively connected to theprocessing module 532. Theprocessing module 532 may comprise aprocessor 534,volatile memory 536, andnon-volatile memory 538 that includes aclient application 540. In various embodiments, theclient application 540 may configure theprocessor 534 to receive input(s) to the input interface 524 (e.g., requests for access to the A/V recording and communication device 402) and/or to capture the audio data 463 using themicrophone 527, for example. In addition, theclient application 540 may configure theprocessor 534 to transmit the location data 477, the access request 475, the audio data 463, the communication signals 481, and/or the output signal 467 to the A/V recording andcommunication device 402 and/or the backend server(s) 430 using thecommunication module 530. - With further reference to
FIG. 25 , theinput interface 524 may include adisplay 525. Thedisplay 525 may include a touchscreen, such that the user of theclient device 407 can provide inputs directly to the display 525 (e.g., a request for access to the A/V recording and communication device 402). In some embodiments, theclient device 407 may not include a touchscreen. In such embodiments, the user may provide an input using any input device, such as, without limitation, a mouse, a trackball, a touchpad, a joystick, a pointing stick, a stylus, etc. - With further reference to
FIG. 25 , the location data 477 may be used by the A/V recording andcommunication device 402 and/or thebackend server 430 to determine if theclient device 407 is within theproximity zone 470. Theclient device 407 may transmit the location data 477 to the A/V recording andcommunication device 402 and/or thebackend server 430 as part of the communication signals 481 and/or the output signal 467 using thecommunication module 450. - In some of the present embodiments, once the
client device 407 is within theproximity zone 470, theclient device 407 may receive theaccess request 474 from the A/V recording andcommunication device 402 and/or transmit the access request 475 to the A/V recording andcommunication device 402 using thecommunication module 450. For example, once theclient device 407 enters theproximity zone 470, a device list 478 (including each of the devices from which theclient device 407 may be allowed to request access) may include the A/V recording andcommunication device 402. As such, the user of theclient device 407 may be able to select the A/V recording andcommunication device 402 from thedevice list 478, and in response, the access request 475 may be transmitted to the selected A/V recording andcommunication device 402. In various embodiments, the A/V recording andcommunication device 402 may be included in thedevice list 478 in response to theclient device 407 receiving theaccess request 474 from the A/V recording andcommunication device 402, such that the selection of the A/V recording andcommunication device 402 from thedevice list 478 may include an acceptance of theaccess request 474. - In the illustrated embodiment of
FIGS. 23-25 , the various components including (but not limited to) theprocessing modules communication modules network interface 520 are represented by separate boxes. The graphical representations depicted in each ofFIGS. 23-25 are, however, merely examples, and are not intended to indicate that any of the various components of the A/V recording andcommunication device 402, theclient device 407, or the backend server(s) 430 are necessarily physically separate from one another, although in some embodiments they might be. In other embodiments, however, the structure and/or functionality of any or all of the components of the A/V recording andcommunication device 402 may be combined. In addition, in some embodiments thecommunication module 450 may include its own processor, volatile memory, and/or non-volatile memory. Further, the structure and/or functionality of any or all of the components of theclient device 407 may be combined. In addition, in some embodiments thecommunication module 530 may include its own processor, volatile memory, and/or non-volatile memory. Further, the structure and/or functionality of any or all of the components of the backend server(s) 430 may be combined. In addition, in some embodiments thenetwork interface 520 may include its own processor, volatile memory, and/or non-volatile memory. - Now referring to
FIG. 26 ,FIG. 26 is a flowchart illustrating a process for accessing cameras of A/V recording and communication devices based on location according to various aspects of the present disclosure. At block B600, theprocess 2600, in response to entering a proximity zone of an A/V recording and communication device, requests, by a processor using a communication module, access to a camera of the A/V recording and communication device. For example, theprocessor 534 of theclient device 407, in response to entering theproximity zone 470, may request, using thecommunication module 530, access to thecamera 444 of the A/V recording andcommunication device 402. A variety of methods may be used to determine that theclient device 407 is within theproximity zone 470. For example, thebackend server 430 and/or the A/V recording andcommunication device 402 may compare the location data 477 of theclient device 407 to theproximity zone 470, and in response to determining that theclient device 407 is within theproximity zone 470, may provide an indication to theclient device 407 that the A/V recording andcommunication device 402 may be accessed (e.g., by including the A/V recording andcommunication device 402 on the device list 478). In some of the present embodiments, theclient device 407 may query thebackend server 430 to determine whether theclient device 407 is within a proximity zone of any A/V recording and communication devices, which may include theproximity zone 470 of the A/V recording andcommunication device 402. For example, the user of theclient device 407 may open a computer program application (e.g., theclient application 540, a web server, etc.) and request to view available devices, and in response, receive a notification that the A/V recording andcommunication device 402 may be accessed. In response, the user of theclient device 407 may transmit the access request 475 to the A/V recording and communication device 402 (in some embodiments, via the backend server 430). - In some of the present embodiments, as described above, the
proximity zone 470 may be defined by the communication signals 479 of the A/V recording andcommunication device 402. In such embodiments, the A/V recording andcommunication device 402 may transmit the communication signals 479 and theclient device 407 may receive the communication signals 479 and analyze the communication signals 479 to determine the signal strength (e.g., RSSI), and theclient device 407 may transmit the signal strength information to the A/V recording andcommunication device 402 and/or thebackend server 430 to determine if theclient device 407 is within theproximity zone 470. - In other embodiments, as described herein, the communication signals 481 of the
client device 407 may be analyzed by the A/V recording andcommunication device 402 to determine if theclient device 407 is within theproximity zone 470. In some of the present embodiments, in response to receiving the communication signals 479 from the A/V recording andcommunication device 402, theclient device 407 may transmit the communication signals 481 to the A/V recording andcommunication device 402, where the communication signals 481 may include the location data 476 of theclient device 407. In response, the A/V recording andcommunication device 402 may compare the location data 476 to theproximity zone 470 to determine if theclient device 407 is within theproximity zone 470. In other embodiments, the A/V recording andcommunication device 402 may measure the signal strength of the communication signals 481 received from theclient device 407 and the signals strength may be used to determine if theclient device 407 is within theproximity zone 470. - At block B602, the
process 2600, in response to the request for access, receives, by the processor using the communication module, from the camera, image data being recorded by the camera in a field of view of the camera. For example, in response to transmitting the access request 475, theprocessor 534 of theclient device 407, using thecommunication module 530, may receive from thecamera 444 theimage data 460 being recorded by thecamera 444 in a field of view of thecamera 444. For example, theclient device 407 may receive theimage data 460 as live streaming video being recorded in the field of view of thecamera 444. - At block B604, the
process 2600 displays, by the processor on the display, the image data. For example, theprocessor 534 of theclient device 407 may display theimage data 460 on thedisplay 525. Theimage data 460 may be displayed as a visual representation of the live video being recorded by thecamera 444 in a field of view of thecamera 444. - Now referring to
FIG. 27 , is a flowchart illustrating a process for accessing cameras of A/V recording and communication devices based on location according to various aspects of the present disclosure. At block B606, theprocess 2700, displays, by the processor on a display, a list of devices configured for access by a client device, the list of devices including an A/V recording andcommunication device 402. For example, theprocessor 534 of theclient device 407 may display on thedisplay 525 thedevice list 478 including a list of devices configured for access by theclient device 407, wheredevice list 478 may include the A/V recording andcommunication device 402. For example, in response to a request from theclient device 407 and/or the device entering theproximity zone 470, thedevice list 478 of theclient device 407 may be populated and displayed on thedisplay 525. - At block B608, the
process 2700 may continue to block B600 ofFIG. 26 . - Now referring to
FIG. 28 ,FIG. 28 is a flowchart illustrating a process for accessing cameras of A/V recording and communication devices based on location according to various aspects of the present disclosure. At block B610, theprocess 2800 may continue from block B600 ofFIG. 26 . At block B612, theprocess 2800 establishes, by a processor using a communication module, a connection to an A/V recording and communication device. For example, theprocessor 534 of theclient device 407, using thecommunication module 530, may connect to (and communicate with) the A/V recording andcommunication device 402. In some of the present embodiments, the connection/communication may be a direct connection/communication between the A/V recording andcommunication device 402 and theclient device 407, such as over the user'snetwork 408 and/or the network (Internet/PSTN) 408. In such embodiments, for example, in response to receiving the access request 475 from theclient device 407, the A/V recording andcommunication device 402 may transmit the network credentials of the user's network (or an ad hoc network generated by the A/V recording and communication device 402) to the client device 407 (e.g., using the communication signals 479, 481). In response to receiving the network credentials, theclient device 407 may join the user'snetwork 408 and establish the connection/communication with the A/V recording andcommunication device 402. In other embodiments, theclient device 407 may be connected to the network (Internet/PSTN) 410 over a cellular network, for example, and the A/V recording andcommunication device 402 may be connected to the network (Internet/PSTN) 410 over the user's network 408 (e.g., using a router). In such embodiments, theclient device 407 may communicate with the A/V recording andcommunication device 402 over the network (Internet/PSTN) 410. - In other embodiments, the connection/communication may be performed using the
backend server 430, such that thebackend server 430 acts as an intermediary between theclient device 407 and the A/V recording andcommunication device 402, as described below with respect toFIGS. 38-40 . - The processes of
FIGS. 26-28 may be implemented in a variety of embodiments, including those discussed below. However, the below-detailed embodiments are not intended to be limiting, and are provided merely as example embodiments of the present disclosure. Other embodiments similar to those outlined herein may also fall within the scope of the present disclosure. - With reference to
FIG. 40 , at block B600, theprocess 2600, in response to the client device 407 (e.g., carried by the user 712) entering theproximity zone communication device 402 located at thehouse 704. Theproximity zone 706 is an example of aproximity zone 470 that includes the A/V recording andcommunication device 402. In some of the present embodiments, theproximity zones 470 may be defined by the user of theclient device communication device 402. The user may select a size of the proximity zone, such as a small (e.g., proximity zone 706) or large (e.g., proximity zone 708)proximity zone 470. In some embodiments, the user may fit a shape (e.g., a circle for theproximity zone 706, 708) to a map including thehouse 704 or a visual representation of thehouse 704, where the shape defines theproximity zone 470. In other embodiments, the user may define a proximity (e.g., radius) for theproximity zone 470. In other embodiments, theproximity zone 470 may be based on the settings of the A/V recording andcommunication device 402. For example, the proximity zones 470 (e.g., proximity zone 710) may include the area in front of the A/V recording andcommunication device 402, such as the field of view of the A/V recording andcommunication device 402. In other embodiments, theproximity zone 470 may be defined by a street or neighborhood, such that when theclient device 407 enters the proximity zone 470 (e.g., enters the street or neighborhood), theclient device 407 may be able to transmit the access request 475 to the A/V recording andcommunication device 402. - At block B612, the
process 2800 establishes a connection with the A/V recording andcommunication device 402. Theclient device 407 may establish the connection with the A/V recording andcommunication device 402 over the network (Internet/PSTN) 410 and/or the user'snetwork 408, as described above. For example, theclient device 407 may receive network credentials for the user's network 408 (e.g., from the backend server 430) such that theclient device 407 can connect to the user'snetwork 408 to communicate with the A/V recording andcommunication device 402. In various embodiments, theclient device 407 may be granted unsecured access to the user'snetwork 408. In such embodiments, theclient device 407 may receive temporary network credentials for the user'snetwork 408 that expire at the expiration of the connection/communication between theclient device 407 and the A/V recording andcommunication device 402. In some of the present embodiments, the A/V recording andcommunication device 402 may generate an ad hoc network, for example, and theclient device 407 may receive the network credentials of the ad hoc network and connect directly to the A/V recording andcommunication device 402 over the ad hoc network. In some of the present embodiments, theclient device 407 may communicate to the A/V recording andcommunication device 402 using thebackend server 430 such that thebackend server 430 acts as an intermediary between theclient device 407 and the A/V recording andcommunication device 402. - In various embodiments, the
client device 407 may be authenticated by the A/V recording and communication device 402 (or the backend server 430). In such embodiments, theclient device 407 may transmit authentication information to the A/V recording and communication device 402 (and/or the backend server 430), and the authentication information may be compared to an authentication database (stored on the A/V recording and communication device and/or the backend server 430), for example, to determine if theclient device 407 should be allowed access to the A/V recording andcommunication device 402. For example, the ability to access A/V recording andcommunication devices 402 from theclient device 407 may be a paid service, and the authentication may be to verify that the user of theclient device 407 has paid for the service. In another example, only client devices that are associated with an A/V recording and communication device (e.g., an A/V recording and communication device other than the A/V recording andcommunication device 402, such as an A/V recording and communication device owned by the user of the client device 407) may be allowed to access the A/V recording andcommunication device 402. As such, the authentication may include verifying that theclient device 407 is associated with an A/V recording and communication device. - At block B602, the
process 2600, in response to transmitting the access request 475 to the A/V recording andcommunication device 402, receives from thecamera 444 theimage data 460 being recorded by thecamera 444 in a field of view of thecamera 444. At block B604, theprocess 2600 displays theimage data 460 on thedisplay 525 of theclient device 407. - With reference to
FIGS. 41-43 , theprocess 2700, at block B606, displays thedevice list 478 on thedisplay 525 of theclient device 407, as illustrated inFIG. 42 . Thedevice list 478 may include all of the devices to which theclient device 407 may have access (e.g., the devices in whoseproximity zones 470 theclient device 407 is located). As illustrated inFIG. 41 , theuser 712 of theclient device 407 may be located on astreet 762, within theproximity zone 716. Theproximity zone 716 is an example of a sharedproximity zone 716. For example, each of the A/V recording andcommunication devices proximity zone 716. In such an example, when theuser 712 enters theproximity zone 716, the user may be allowed access to each of the A/V recording andcommunication devices communication devices own proximity zone 470, or two or more of the A/V recording andcommunication devices proximity zone 470 while the other(s) A/V recording andcommunication devices proximity zone 470 and/or have theirown proximity zone 470, for example. In the example ofFIG. 41 , theproximity zone 716 may include the A/V recording andcommunication device 724, which may be a video doorbell located at thehouse 704, the A/V recording andcommunication device 725, which may be a security camera located at thehouse 730, and the A/V recording andcommunication device 726, which may be a video doorbell located at thehouse 720. As such, because theclient device 407 is within theproximity zone 716, thedevice list 478 may include each of the A/V recording andcommunication devices client device 407. - The
device list 478 may include anaccess button communication devices access buttons user 712 to provide an input (e.g., by thefinger 744 of theuser 712, or another input device, as described above) to theaccess buttons communication device device list 478 may also include an access allbutton 739, which may allow theclient device 407 to access each of the A/V recording andcommunication devices devices client device 407 may display theimage data 460 on thedisplay 525 of theclient device 407 for each of the A/V recording andcommunication devices client device 407 has accessed (e.g., connected to and/or established communication with) each of the A/V recording andcommunication devices image data 460 from one or more of the A/V recording andcommunication devices user 712 desires (e.g., may toggle selection ofdifferent devices - In addition, the
device list 478 may include an identification of the type of device each of the A/V recording andcommunication devices communication devices device list 478 may also include an indication of suspicious activity identified by one or more of the A/V recording andcommunication devices warning icon 746 when the burglar 740 (or another suspicious/dangerous person) is present (or has recently been present) in the field of the view of the A/V recording and communication device 726 (e.g., by including a time stamp). The identification of suspicious activity may be determined by the A/V recording andcommunication device 726 when analyzing theimage data 460 generated by the camera of the A/V recording andcommunication device 726, such as by using a computer vision process (e.g., facial recognition, facial detection, object recognition, etc.) or the like. - At block B608, the
process 2700 may continue to block B600 of theprocess 2600. At block B600, theclient device 407 may transmit the access request 475 to the A/V recording andcommunication device 726 in response to theuser 712 providing a selection to theaccess button 738 on thedevice list 478 using his or herfinger 744, as illustrated inFIG. 42 . For example, theuser 712 may have selected to access the A/V recording andcommunication device 726 because thedevice list 478 included thewarning icon 746 and theuser 712 wanted to be notified of any potential danger in the neighborhood (e.g., on the street 762). - At block B612, in the
process 2800, theclient device 407 may establish a connection to the A/V recording andcommunication device 726. At block B614, theprocess 2800 may continue to block B602 ofFIG. 26 . At block B602 of theprocess 2600, in response to transmitting the access request 475 (at block B600), and in response to establishing connection/communication with the A/V recording and communication device 726 (at block B612), theclient device 407 may receive theimage data 460 being recorded by the A/V recording andcommunication device 726. In some of the present embodiments, in addition to receiving theimage data 460 being recorded, theclient device 407 may receive access to the previously recordedimage data 460 from the A/V recording andcommunication device 726. For example, theclient device 407 may be allowed access to the previous 10 seconds, 20 seconds, 30 seconds, or 1 minute of recordedimage data 460, for example. As a result, theuser 712 of theclient device 407 may be able to view the suspicious activity of theburglar 740, or view better quality (e.g., closer, more focused) image of theburglar 740, even if theburglar 740 is not currently in the field of view and/or not in close proximity to the A/V recording and communication device 726 (e.g., theburglar 740 has fled the scene). This may also allow theuser 712 to determine that theburglar 740 has agun 742 and/or determine what direction theburglar 740 is traveling so that theuser 712 may take a more appropriate action (e.g., hide, alert law enforcement, etc.). - At block B604 of the
process 2600, theclient device 407 may display theimage data 460 on thedisplay 525, as illustrated in the screenshot ofFIG. 43 . The screenshot ofFIG. 43 may be a screenshot of a GUI of a computer program application (e.g., a smart phone application). Theimage data 460 may include theburglar 740 and thegun 742, allowing theuser 712 to determine the reason for thewarning icon 746 displayed on thedevice list 478. The GUI may include thewarning icon 746, as illustrated inFIG. 43 . The GUI may also include an identification of the type of device that the A/V recording andcommunication device 726 is, and may further include the address where thedevice 726 is located. Arecording status indicator 745 may also be displayed on thedisplay 525 to provide an indication of whether theimage data 460 is live or pre-recorded, for example. - The GUI may also include an
action button 750. The action button 750 (e.g., when selected) may provide theuser 712 with a list ofactions 758 from which theuser 712 may be able to select. For example, the list ofactions 758 may include a use speaker button 752, asound alarm button 754, a notifypolice button 756, and/or other buttons corresponding to different actions for theuser 712. The use speaker button 752 may enable theuser 712 to speak through the speaker of the A/V recording andcommunication device 726, such as to communicate with and/or scare off theburglar 740, for example. Thesound alarm button 754 may trigger an audible and/or visible alarm at the A/V recording andcommunication device 726. The notifypolice button 756 may send a notification to law enforcement and/or initiate a call between theuser 712 and law enforcement. The notifypolice button 756 may also trigger the A/V recording andcommunication device 726 to transmit theimage data 460 to law enforcement, as described above. - The GUI may also include control features for controlling the
image data 460, such as a play button 768, apause button 788, areturn button 790, afast forward button 792, and/or other buttons. The return button 790 (e.g., when selected) may provide areturn button list 781 for allowing theuser 712 to select an amount of time to go back in theimage data 460 and/or a specific point in theimage data 460. For example, theuser 712 may be able to select 10seconds seconds 782 to go back 10 seconds or 30 seconds in theimage data 460, respectively. In some of the present embodiments, thereturn button list 781 may also include a personpresent button 784. The personpresent button 784 may go back to in theimage data 460 to when a person is present (e.g., detected by the A/V recording and communication device 726), such as when theburglar 740 was first detected, when theburglar 740 is facing the camera, and/or at any time that the burglar is in the field of view of the A/V recording andcommunication device 726. The A/V recording andcommunication device 726 may use computer vision or the like, as described above, to determine when theburglar 740 is present and/or to determine the position of theburglar 740 with respect to the A/V recording and communication device 726 (e.g., when theburglar 740 is facing the A/V recording and communication device). - Now referring to
FIG. 29 ,FIG. 29 is a flowchart illustrating a process for accessing cameras of A/V recording and communication devices based on location according to various aspects of the present disclosure. Theprocess 2900 may be similar to theprocess 2600, except in theprocess 2900 the A/V recording andcommunication device 402 transmits theaccess request 474. In various embodiments, without limitation, theprocesses client device 407 and the A/V recording andcommunication device 402 may transmit the access requests 474, 475. For example, theclient device 407 may periodically determine if any A/V recording and communication devices are available for access and transmit the access request 475, and the A/V recording andcommunication device 402 may periodically determine if any client devices are available for access and transmit theaccess request 474. In another example, theclient device 407 may primarily transmit the access request 475, and the A/V recording andcommunication device 402 may only determine if any client devices are available and transmit theaccess request 474 in response to a suspicious activity warning/flag (e.g., after detecting that theburglar 740 is present). Similarly, with reference toFIG. 32 andFIG. 36 , without limitation, theprocesses FIG. 38 andFIG. 39 , without limitation, theprocesses - With further reference to
FIG. 29 , at block B616, theprocess 2900, in response to entering a proximity zone of an A/V recording and communication device, receives, from the A/V recording and communication device, an access request for allowing a client device to access a camera of the A/V recording and communication device. For example, in response to entering theproximity zone 470 of the A/V recording andcommunication device 402, theprocessor 534 of theclient device 407 receives, using thecommunication module 530, theaccess request 474 from the A/V recording andcommunication device 402 for allowing theclient device 407 access to the A/V recording andcommunication device 402. In some of the present embodiments, the A/V recording andcommunication device 402 may determine that theclient device 407 has entered the proximity zone 470 (e.g., by comparing the location data 477 to the proximity zone 470) and transmit theaccess request 474. In other embodiments, thebackend server 430 may compare the location data 477 to theproximity zone 470 and transmit theaccess request 474 to the client device 407 (and/or forward theaccess request 474 from the A/V recording and communication device 402). - At block B620, the
process 2900 transmits, by the processor using the communication module, to the A/V recording and communication device, an acceptance of the access request. For example, theprocessor 534 may transmit, using thecommunication module 530, an acceptance of theaccess request 474 to the A/V recording andcommunication device 402. For example, in response to receiving theaccess request 474, theclient device 407 may display thedevice list 478, and theuser 712 of theclient device 407 may select the A/V recording andcommunication device 402 from thedevice list 478 as an acceptance of theaccess request 474. In such an example, in response to the selection of the A/V recording andcommunication device 402 on thedisplay 525, theclient device 407 may transmit the acceptance. In some of the present embodiments, theclient device 407 may, depending on the settings of theclient device 407, automatically accept access requests 474. For example, if theaccess request 474 includes a suspicious activity warning/flag (e.g., if theaccess request 474 is transmitted in response to suspicious behavior detected by the A/V recording andcommunication device 402 and/or thebackend server 430 in response to analyzing theimage data 460, such as if theimage data 460 includes the burglar 740), theclient device 407 may be programmed to automatically transmit an acceptance to theaccess request 474. - At block B620, the
process 2900, in response to the transmitting the acceptance, receives, by the processor using the communication module, from the camera, image data being recorded in a field of view of the camera. For example, theprocessor 534, in response to transmitting the acceptance, may receive, using thecommunication module 530, from thecamera 444, theimage data 460 being recorded by thecamera 444 in a field of view of thecamera 444. This process may be similar to that of block B602 ofFIG. 26 , described above. - At block B622, the
process 2900 displays, by the processor on a display, the image data. For example, theprocessor 534 displays theimage data 460 on thedisplay 525. This process may be similar to that of block B604 ofFIG. 26 , described above. - Now referring to
FIG. 30 ,FIG. 30 is a flowchart illustrating a process for accessing cameras of A/V recording and communication devices based on location according to various aspects of the present disclosure. At block B624, theprocess 3000 may continue from block B616 ofFIG. 29 . At block B626, theprocess 3000, in response to receiving an access request, displays, by a processor on a display, a list of devices configured for access by a client device, the list of devices including an A/V recording and communication device. For example, in response to receiving theaccess request 474, theprocessor 534 may display thedevice list 478 on thedisplay 525 of theclient device 407, where thedevice list 478 may include the A/V recording andcommunication device 402. - At block B628, the
process 3000 receives, by the processor, an input including a selection of the A/V recording and communication device from the list of devices, the input including an acceptance of the access request. For example, theprocessor 534 may receive an input including a selection of the A/V recording andcommunication device 402 from thedevice list 478, where the input includes an acceptance of theaccess request 474. For example, as illustrated inFIG. 42 , theuser 712 may make a selection of one or more of the A/V recording andcommunication devices device list 478, where the selection includes an acceptance of theaccess request 474 transmitted by the corresponding A/V recording andcommunication device device list 478 may include the A/V recording andcommunication devices communication devices client device 407 but have not transmitted the access request 474 (e.g., where theclient device 407 must transmit the access request 475). In such embodiments, when the A/V recording andcommunication devices access request 474, selecting theaccess button access request 474. When the A/V recording andcommunication devices access request 474, selecting theaccess button client device 407 to the corresponding A/V recording andcommunication device - At block B630, the
process 3000 may continue to block B618 ofFIG. 29 . - Now referring to
FIG. 31 ,FIG. 31 is a flowchart illustrating a process for accessing cameras of A/V recording and communication devices based on location according to various aspects of the present disclosure. At block B632, theprocess 3100 may continue from block B618 ofFIG. 29 . At block B634, theprocess 3100 may establish, by a processor using a communication module, a connection to an A/V recording and communication device. For example, theprocessor 534 of theclient device 407 may establish a connection to the A/V recording andcommunication device 402 using thecommunication module 530. This process may be similar to that of block B612 ofFIG. 28 , described above. At block B634, theprocess 3100 may continue to block B620 ofFIG. 29 . - Now referring to
FIG. 32 ,FIG. 32 is a flowchart illustrating a process for accessing cameras of A/V recording and communication devices based on location according to various aspects of the present disclosure. Theprocess 3200 may be similar to theprocess 2900 ofFIG. 29 , except theprocess 3200 may be directed to the processes of the A/V recording andcommunication device 402 while theprocess 2900 may be directed to the processes of theclient device 407. For example, at block B638, theprocess 3200 may transmit theaccess request 474, and at block B616 of theprocess 2900 ofFIG. 29 , theclient device 407 may receive theaccess request 474 from the A/V recording andcommunication device 402. - With further reference to
FIG. 32 , at block B638, theprocess 3200, in response to detecting the presence of a client device in a proximity zone of an A/V recording and communication device, transmits, by a processor using the communication module, an access request to the client device for allowing the client device to access the camera. For example, in response to detecting the presence of theclient device 407 in theproximity zone 470, the A/V recording andcommunication device 402 may transmit, by theprocessor 452 using thecommunication module 450, theaccess request 474 to theclient device 407 for allowing theclient device 407 access to the camera 444 (and/or other features of the A/V recording and communication device 402). Theaccess request 474 may be transmitted over the network (Internet/PSTN) 410 and/or the user'snetwork 408. Theaccess request 474 may be transmitted to theclient device 407 and/or to thebackend server 430 and thebackend server 430 may forward theaccess request 474 to theclient device 407. In some of the present embodiments, as described above, the access request may be transmitted directly to theclient device 407 over an ad hoc network generated by the A/V recording andcommunication device 402. - At block B640, the
process 3200, in response to transmitting the access request, receives, by the processor using the communication module, an acceptance of the access request from the client device. For example, theprocessor 452 using thecommunication module 450 may receive the acceptance of theaccess request 474 from theclient device 407 in response to transmitting theaccess request 474. The acceptance may be received over the network (Internet/PSTN) 410 and/or the user'snetwork 408. The acceptance may be received from theclient device 407 and/or from thebackend server 430 after thebackend server 430 receives the acceptance from theclient device 407. In some of the present embodiments, as described above, the acceptance may be received directly by the A/V recording andcommunication device 402 over the ad hoc network. - At block B642, the
process 3200, in response to receiving the acceptance, transmits, by the processor using the communication module, image data being recorded by the camera in a field of view of the camera. For example, theprocessor 452 using thecommunication module 450 may transmit theimage data 460 being recorded by thecamera 444 in field of view of thecamera 444. Theimage data 460 may be transmitted to theclient device 407 over the network (Internet/PSTN) 410 and/or the user's network 408 (in some embodiments, via the backend server 430). In other embodiments, as described above, theimage data 460 may be transmitted directly to theclient device 407 over the ad hoc network generated by the A/V recording andcommunication device 402. - Now referring to
FIG. 33 ,FIG. 33 is a flowchart illustrating a process for accessing cameras of A/V recording and communication devices based on location according to various aspects of the present disclosure. At block B644, theprocess 3200 detects, by a processor using a communication module, the presence of a client device in a proximity zone of an A/V recording and communication device. For example, theprocessor 452 using thecommunication module 450 may detect the presence of theclient device 407 in theproximity zone 470 of the A/V recording andcommunication device 402. In some of the present embodiments, the A/V recording andcommunication device 402 may listen, using thecommunication module 450, for incoming communication signals 481 of the client device 407 (e.g., that may be transmitted by theclient device 407 at an interval, such as every 10 seconds, every 20 seconds, etc.). The communication signals 481 may include the location data 477 of theclient device 407 for comparison with theproximity zone 470. In some of the present embodiments, the A/V recording andcommunication device 402 may transmit the communication signals 479 (e.g., at interval, such as every 10 seconds, every 20 seconds, etc.), and theclient device 407 may listen for the communication signals 479. In response to receiving the communication signals 479, theclient device 407 may transmit the communication signals 481 including the location data 477 for the A/V recording andcommunication device 402 to compare to theproximity zone 470. In either of the embodiments, once it is determined, based on the location data 477, for example, that theclient device 407 is within theproximity zone 470, theprocess 3300 may continue to block B646. - In various embodiments, the
client device 407 may transmit the location data 477 to thebackend server 430 and thebackend server 430 may determine, and/or forward the location data 477 to the A/V recording andcommunication device 402 for determining, if theclient device 407 within theproximity zone 470. - At block B646, the
process 3300 may continue to block B638 ofFIG. 32 . - Now referring to
FIG. 34 ,FIG. 34 is a flowchart illustrating a process for accessing cameras of A/V recording and communication devices based on location according to various aspects of the present disclosure. At block B648, theprocess 3400 may continue from block B640 ofFIG. 32 . At block B650, theprocess 3400 may establish, by a processor using a communication module, a connection to a client device. For example, theprocessor 452 of the A/V recording andcommunication device 402, using thecommunication module 450, may establish a connection/communication to theclient device 407. This process may be similar to that of block B634 ofFIG. 3100 and/or block B612 ofFIG. 28 , described above. At block B652, theprocess 3400 may continue to block B642 ofFIG. 32 . - Now referring to
FIG. 35 ,FIG. 35 is a flowchart illustrating a process for accessing cameras of A/V recording and communication devices based on location according to various aspects of the present disclosure. At block B654, theprocess 3500 generates, by a processor, a proximity zone for detecting the presence of one or more client devices within a proximity zone. For example, theprocessor 452 may generate theproximity zone 470 for detecting the presence of one or more client devices (e.g., the client device 407). Theproximity zone 470, as described above, may be based on the settings of the A/V recording andcommunication device 402. For example, theproximity zone 470 may be a default size and shape, and the generation of theproximity zone 470 may include a determination of the location data 476 (e.g., geographical coordinates) relating to thedefault proximity zone 470 at the location of the A/V recording andcommunication device 402. In other words, for example, if theproximity zone 470 includes a 300-foot radius around the A/V recording andcommunication device 402, the generating of theproximity zone 470 may include determining the location data 476 (e.g., geographical coordinates) within the 300-foot radius of the A/V recording andcommunication device 402. As further discussed above, theproximity zone 470 may be user created (e.g., by selecting a size, setting a region, drawing theproximity zone 470 over a map on the display, etc.). In such examples, in response to receiving the user input for theproximity zone 470 from theclient device communication device 402 may generate theproximity zone 470, similar to described above, by determining the location data 476 (e.g., geographical coordinates) of theproximity zone 470. The location data 476 of theproximity zone 470 may then be compared to the location data 477 (e.g., geographical coordinates from a GPS or) of theclient device 407 to determine if theclient device 407 is within theproximity zone 470. - In some of the present embodiments, the
backend server 430 may transmit theproximity zone 470 to the A/V recording andcommunication device 402. In such embodiments, the A/V recording andcommunication device 402 may receive the location data 476 defining theproximity zone 470, and generating theproximity zone 470 may include updating the settings of the A/V recording andcommunication device 402 with the location data 476 including theproximity zone 470 received from thebackend server 430. As such, in response to receiving the location data 477 of theclient device 407, the A/V recording andcommunication device 402 may determine whether theclient device 407 is within theproximity zone 470. - In some of the present embodiments, the location data 477 may include (in addition to or in lieu of GPS data) cellular data, such as a Mobile Country Code (MCC), a Mobile Network Code (MNC), a Location Area Code (LAC), and a Cell ID (CID). The cellular data may be used to determine the location data 477 of the
client device 407, such as geographical coordinates, which may be compared to the location data 476 of theproximity zone 470 to determine if theclient device 407 is within theproximity zone 470. - In some of the present embodiments, as described above, the communication signals 479, 481 may be used to define the
proximity zone 470. As an example, in some of the present embodiments, the location data 477 may include Wi-Fi Positioning System (WPS) data, and the WPS data may be used to determine a location of theclient device 407. The location of theclient device 407 may then be compared to theproximity zone 470 to determine if theclient device 407 is within theproximity zone 470. In some of the present embodiments, the location data 477 may include Bluetooth and/or ZigBee data, and the Bluetooth and/or Zigbee data may be used to determine a location of theclient device 407. The location of theclient device 407 may then be compared to theproximity zone 470 to determine if theclient device 407 is within theproximity zone 470. - In embodiments where Wi-Fi data, Bluetooth, ZigBee, and/or other signal types are used, the
proximity zone 470 may be defined by signal strength of the Wi-Fi, Bluetooth, ZigBee and/or other signal type signals, rather than by geographical coordinates. For example, the signal strength may be measured as the Received Signal Strength Indication (RSSI) of the Wi-Fi, Bluetooth, ZigBee, and/or other signal type signals. Theproximity zone 470 may then be defined (e.g., user defined or by default) by the RSSI values for the Wi-Fi, Bluetooth, ZigBee, and/or other signal type signals that may render a determination that a client device is within the proximity zone 470 (e.g., Bluetooth RSSI greater than −65 dBm on a −100-0 scale). As such, when the RSSI is within the RSSI values for theproximity zone 470, theclient device 407 is determined to be within theproximity zone 470. In such embodiments, the A/V recording andcommunication device 402 may transmit the Wi-Fi, Bluetooth, ZigBee, and/or other signal type signals (e.g., the communication signals 479, 481) using a Wi-Fi, Bluetooth, ZigBee, and/or other signal type transmitter (e.g., a transceiver, a transmitter, or a transmitter-receiver), for example, and theclient device 407 may receive the signals (e.g., via a receiver, a transceiver, or a transmitter-receiver) and measure the RSSI values of the signals. After measuring the RSSI values, theclient device 407 may transmit the RSSI values to the A/V recording andcommunication device 402 and/or thebackend server 430 to be compared to the RSSI values of theproximity zone 470 to determine if theclient device 407 is within theproximity zone 470. In some of the present embodiments, theclient device 407 may transmit the Wi-Fi, Bluetooth, ZigBee, and/or other signal type signals using a Wi-Fi, Bluetooth, ZigBee, and/or other signal type transmitter (e.g., a transceiver, a transmitter, or a transmitter-receiver), for example, and the A/V recording andcommunication device 402 may receive the signals (e.g., via a receiver, a transceiver, or a transmitter-receiver) and measure the RSSI values of the signals, and analyze the RSSI values locally on the A/V recording andcommunication device 402 and/or transmit the RSSI values to thebackend server 430 to be compared to the RSSI values of theproximity zone 470 to determine if theclient device 407 is within theproximity zone 470. - In some of the present embodiments, as described above, the
proximity zone 470 may be determined by thebackend server 430 and transmitted to the A/V recording andcommunication device 402. In such embodiments, theproximity zone 470 received from thebackend server 430 may include the RSSI values that define theproximity zone 470, for example, and the A/V recording andcommunication device 402 may update the settings of thedevice 402 to reflect the receivedproximity zone 470 information. - In examples where ZigBee is implemented, in addition to or in lieu of the RSSI, the location data 477 may be based on active reflector technology, where the active reflector technology may be used to determine a distance of the
client device 407 from the A/V recording andcommunication device 402, and based on the distance, determine if theclient device 407 is within theproximity zone 470. In such embodiments, theproximity zone 470 may be defined by a diameter (e.g., 400 feet), and the active reflector technology may be used to determine the estimated location data 477 (e.g., distance) of theclient device 407 to determine if theclient device 407 is within theproximity zone 470. In such embodiments, theclient device 407 and/or the A/V recording andcommunication device 402 may include ZigBee transceivers. - At block B656, the process may continue to block B638 of
FIG. 32 or block B644 ofFIG. 33 . - The processes of
FIGS. 32-35 may be implemented in a variety of embodiments, including those discussed below. However, the below-detailed embodiments are not intended to be limiting, and are provided merely as example embodiments of the present disclosure. Other embodiments similar to those outlined herein may also fall within the scope of the present disclosure. - With reference to
FIG. 40 , the A/V recording andcommunication device 402 may generate one of theproximity zones FIG. 35 ). The A/V recording andcommunication device 402 may generate theproximity zones proximity zone 470 from thebackend server 430. - The A/V recording and
communication device 402 may detect theclient device 407 within theproximity zone FIG. 33 ) and transmit theaccess request 474 to the client device 407 (at block B638 ofFIG. 32 ). For example, the A/V recording andcommunication device 402 may listen for communication signals 481 from the client device 407 (and/or other client devices). The A/V recording andcommunication device 402 may listen at a set interval, such as every second, every 5 seconds, every 10 seconds, or every 30 seconds, for example. The communication signals 481 may include the location data 477 of theclient device 407 for the A/V recording andcommunication device 402 to compare against theproximity zone 470. In another example, the A/V recording andcommunication device 402 may communicate with thebackend server 430 to determine if the client device 407 (and/or other client devices 407) have location data 477 indicative of theclient device 407 being within theproximity zone 470, and in response to determining that theclient device 407 is within the proximity zone, may transmit theaccess request 474 to the client device 407 (in some embodiments, via the backend server 430). The A/V recording andcommunication device 402 may communicate with thebackend server 430 to determine if any client devices are within theproximity zone 470 at an interval, such as every second, every 5 seconds, every 10 seconds, every 30 seconds, or at each router check-in, for example. - After transmitting the
access request 474, the A/V recording andcommunication device 402 may receive an acceptance of the access request 474 (at block B640 ofFIG. 32 ). For example, theuser 712 of theclient device 407 may select the A/V recording andcommunication device 402 from thedevice list 478. In response to receiving the acceptance, the A/V recording andcommunication device 402 may connect to the client device 407 (at block B650 ofFIG. 34 ). After establishing the connection, the A/V recording andcommunication device 402 may transmit theimage data 460 to the client device 407 (at block B642 ofFIG. 32 ). Theimage data 460 may be transmitted over the user'snetwork 408 and/or the network (Internet/PSTN) 410 to the client device 407 (in some embodiments, via the backend server 430). - With reference to
FIGS. 41-43 , the A/V recording and communication device 726 (and/or other A/V recording and communication devices within the proximity zone 716) may detect the suspicious activity of theburglar 740 carrying thegun 742. In response, in some of the present embodiments, the A/V recording andcommunication device 726 may determine (e.g., by detecting the client devices (at block B644 ofFIG. 33 ), by querying thebackend processor 430, etc.) if any client devices are within theproximity zone 716 in order to alert the users of the client devices of the suspicious behavior of theburglar 740. In response, the A/V recording andcommunication device 726 may determine that theclient device 407 is within theproximity zone 470. The A/V recording and communication device 726 (in some embodiments, via the backend server 430) may transmit theaccess request 474 to theclient device 407 to allow theclient device 407 to access the camera 444 (and/or prerecorded image data 460) of the A/V recording and communication device 726 (at block B638 ofFIG. 32 ). In some of the present embodiments, theaccess request 474 may be received by the client device 407 (e.g., at block B616 ofFIG. 29 ) and theclient device 407, based on the settings of theclient application 540, for example, may automatically accept theaccess request 474 based on the suspicious activity warning/flag included in the access request 474). In other embodiments, theaccess request 474 may display as a notification on thedisplay 525 of the client device 407 (e.g., a push notification), where the notification may include the suspicious activity warning/flag (e.g., “suspicious activity reported in your immediate vicinity, access video?”). Theuser 712 of theclient device 407 may accept (e.g., at block B618 ofFIG. 29 ) the access request 474 (e.g., automatically, in response to interacting with the notification, by selecting the A/V recording andcommunication device 726 from thedevice list 478 ofFIG. 42 , etc.). In response to the acceptance of theaccess request 474, the A/V recording and communication device 726 (in some embodiments, via the backend server 430) may receive the acceptance to theaccess request 474 from the client device 407 (at block B640). In response to receiving the acceptance, the A/V recording and communication device 402 (and/or the backend server 430) may transmit theimage data 460 of theburglar 740 to the client device 407 (at block B642). In embodiments where there is a suspicious activity warning/flag, theclient device 407 may automatically accept theaccess request 474, and may automatically display theimage data 460 on thedisplay 525 of theclient device 407 in order to warn theuser 712 of the suspicious activity. - In some of the present embodiments, the
image data 460 may be transmitted live, such that theuser 712 of theclient device 407 can see the current field of view of thecamera 444 of the A/V recording andcommunication device 726. In other embodiments, such as where theburglar 740 has now left the field of view of the camera 444 (e.g., as determined by computer vision), theimage data 460 transmitted to theclient device 407 may be thepre-recorded image data 460 including theburglar 740. In such embodiments, theuser 712 may be able to see the appearance (e.g., physical appearance, identity, clothing, etc.) of theburglar 740 and/or thegun 742 being carried by theburglar 740 and determine that theburglar 740 is in fact suspicious. As a result, theuser 712 may be more likely to hide, flee, alert law enforcement, or take other appropriate actions based on the knowledge of the burglar's 740 presence. In addition, theuser 712 may access thedevice list 478 after being notified of theburglar 740, and determine if any of the other A/V recording and communication devices in theproximity zone 716 have identified suspicious activity (e.g., the burglar 740), in order to determine the safest exit route and/or hiding places, for example. - In some of the present embodiments, the warning
icons 746 may include a time stamp, such that theuser 712 can view when the suspicious activity was detected by the A/V recording andcommunication devices warning icon 746 may have a time stamp of 8:05 PM, and another warning icon 746 (not shown) may be included next to the A/V recording andcommunication device 724 on thedevice list 478 with a time stamp of 8:15 PM. As such, theuser 712 may be able to determine that theburglar 740 may be moving, from left to right, down thestreet 762 and take appropriate action. In some of the present embodiments, the A/V recording andcommunication devices user 712 of the client device 407 (e.g., on the device list 478). - Now referring to
FIG. 36 ,FIG. 36 is a flowchart illustrating a process for accessing cameras of A/V recording and communication devices based on location according to various aspects of the present disclosure. Theprocess 3600 may be similar to theprocess 2600 ofFIG. 26 , except theprocess 3600 may be directed to the processes of the A/V recording andcommunication device 402 while theprocess 2600 may be directed to the processes of theclient device 407. For example, at block B600 of theprocess 2600, theclient device 407 may transmit the access request 475, and at block B658 of theprocess 3600, the A/V recording andcommunication device 402 may receive the access request 475 from theclient device 407. - With further reference to
FIG. 36 , at block B658, theprocess 3600, in response to a client device entering a proximity zone of an A/V recording andcommunication device 402, receives, by a processor using a communication module, an access request from the client device for allowing the client device access to a camera. For example, in response to theclient device 407 entering theproximity zone 470 of the A/V recording andcommunication device 402, theprocessor 452 of the A/V recording andcommunication device 402 using thecommunication module 450 may receive the access request 475 from theclient device 407 for allowing theclient device 407 access to thecamera 444 of the A/V recording andcommunication device 402. For example, in response to entering theproximity zone 470, the user of theclient device 470 may receive a notification that the user can access (e.g., is within theproximity zone 470 of the A/V recording and communication device 402) the A/V recording and communication device 402 (e.g., in the device list 478). As a result, the user may request access and theclient device 407 may transmit the access request 475 to the A/V recording andcommunication device 402. In response, the A/V recording andcommunication device 402 may receive the access request 475. - At block B660, the
process 3600, in response to receiving the access request, accepts, by the processor, the access request. For example, in response to receiving the access request 475, theprocessor 452 of the A/V recording andcommunication device 402 may accept the access request 475. In some of the present embodiments, the A/V recording andcommunication device 402 may receive the location data 477 of the client device 407 (e.g., along with the access request 475) and may compare the location data 477 to theproximity zone 470 to determine whether theclient device 407 is within theproximity zone 470. Once the A/V recording andcommunication device 402 has confirmed that theclient device 407 is within theproximity zone 470, the A/V recording andcommunication device 402 may accept the access request 475. In some of the present embodiments, the user/owner of the A/V recording andcommunication device 402 may receive a notification of the access request 475 from the A/V recording and communication device 402 (in some embodiments via the backend server 430), and may allow access or deny access. If the user/owner allows access, then the A/V recording andcommunication device 402 may accept the access request 475. - At block B662, the
process 3600, in response to the acceptance, transmits, by the processor using the communication module, image data being recorded by the camera to the client device. For example, in response to accepting the access request 475 (at block B660), theprocessor 452 of the A/V recording and communication device, using thecommunication module 450, may transmit theimage data 460 being recorded by thecamera 444 to theclient device 407. This process may be similar to that of block B642 ofFIG. 32 , described above. - Now referring to
FIG. 37 ,FIG. 37 is a flowchart illustrating a process for accessing cameras of A/V recording and communication devices based on location according to various aspects of the present disclosure. At block B664, theprocess 3700 may continue from block B660 ofFIG. 36 . At block B666, theprocess 3700 establishes, by a processor using a communication module, a connection to a client device. For example, theprocessor 452 of the A/V recording andcommunication device 402, using thecommunication module 450, may establish a connection to/communication with theclient device 407. This process may be similar to that of block B650 ofFIG. 34 , described above. At block B668, theprocess 3700 may continue to block B662 ofFIG. 36 . - Now referring to
FIG. 38 ,FIG. 38 is a flowchart illustrating a process for accessing cameras of A/V recording and communication devices based on location according to various aspects of the present disclosure. In some of the present embodiments, theprocess 3800 may be similar to theprocess 2600 ofFIG. 26 and theprocess 3600 ofFIG. 36 , except theprocess 3800 may be directed to the processes of thebackend server 430 while theprocess 2600 may be directed to the processes of theclient device 407 and theprocess 3600 may be directed to the process of the A/V recording andcommunication device 402. For example, at block B600 of theprocess 3200, theclient device 407 may transmit the access request 475, and at block B670 of theprocess 3800, thebackend server 430 may receive the access request 475 from theclient device 407, and at block B672, transmit the access request 475 to the A/V recording andcommunication device 402. At block B658 of theprocess 3600, the A/V recording andcommunication device 402 may receive the access request 475 from thebackend server 430. - As another example, in some of the present embodiments, the
process 3800 may be similar to theprocess 2900 ofFIG. 29 and theprocess 3200 ofFIG. 32 , except theprocess 3800 may be directed to the processes of thebackend server 430 while theprocess 2900 may be directed to the processes of theclient device 407 and theprocess 3200 may be directed to the process of the A/V recording andcommunication device 402. For example, at block B638 of theprocess 3200, the A/V recording andcommunication device 402 may transmit theaccess request 474, and at block B670 of theprocess 3800, thebackend server 430 may receive theaccess request 474 from the A/V recording andcommunication device 402, and at block B672, transmit theaccess request 474 to theclient device 407. At block B616 of theprocess 2900, theclient device 407 may receive theaccess request 474 from thebackend server 430. - With further reference to
FIG. 38 , at block B670, theprocess 3800, in response to a client device entering a proximity zone of an A/V recording and communication device, receives, from the client device and/or the A/V recording and communication device, an access request for allowing the client device access to the camera of the A/V recording and communication device. For example, in response to theclient device 407 entering theproximity zone 470 of the A/V recording andcommunication device 402, theprocessor 502 of thebackend server 430 may receive, from theclient device 407 and/or the A/V recording andcommunication device 402, theaccess request 474, 475 for allowing theclient device 407 access to thecamera 444 of the A/V recording andcommunication device 402. Thebackend server 430 may receive theaccess request 474, 475 over the network (Internet/PSTN) 410 using thenetwork interface 520, for example. In some of the present embodiments, theaccess request 474, 475 may be received in the output signal 466, 467 from the A/V recording andcommunication device 402 and/or theclient device 407. In various embodiments, the access request 475 may further include the location data 477 of theclient device 407. - At block B672, the
process 3800, in response to receiving the access request, transmits the access request to the A/V recording and communication device and/or the client device. For example, in response to receiving theaccess request 474, 475 from the A/V recording andcommunication device 402 and/or theclient device 407, theprocessor 502 of thebackend server 430, using thenetwork interface 520, may transmit theaccess request 474, 475 to the A/V recording andcommunication device 402 and/or theclient device 407. In embodiments where theaccess request 474 is transmitted to theclient device 407, thebackend server 430 may receive an acceptance to theaccess request 474 from theclient device 407 and transmit the acceptance to the A/V recording andcommunication device 402, prior to proceeding to block B674, discussed below. - At block B674, the
process 3800, in response to transmitting the access request, receives, from the A/V recording and communication device, image data being recorded by the camera of the A/V recording and communication device in a field of view of the camera. For example, in response to transmitting theaccess request 474, 475 (and, in some embodiments receiving the acceptance of theaccess request 474 from the client device 407), theprocessor 502 of thebackend server 430, using thenetwork interface 520, may receive theimage data 460 being recorded by thecamera 444 of the A/V recording andcommunication device 402. - At block B676, the
process 3800, in response to receiving the image data, transmits, to the client device, the image data. For example, in response to receiving theimage data 460, theprocessor 502 of thebackend server 430, using thenetwork interface 520, may transmit theimage data 460 to theclient device 407. - The process of
FIG. 38 may be implemented in a variety of embodiments, including those discussed below. However, the below-detailed embodiments are not intended to be limiting, and are provided merely as example embodiments of the present disclosure. Other embodiments similar to those outlined herein may also fall within the scope of the present disclosure. - With reference to
FIG. 40 , at block B670 of theprocess 3800, thebackend server 430 may receive theaccess request 474 from the A/V recording andcommunication device 402 and/or the access request 475 from theclient device 407 in response to theuser 712 entering the one of theproximity zones client device 407 entering one of theproximity zones client device 407 and/or the A/V recording andcommunication device 402 may transmit theaccess request 474, 475 to thebackend server 430, and thebackend server 430 may receive theaccess request 474, 475 (at block B670). In some of the present embodiments, theclient device 407 may receive a notification that the A/V recording andcommunication device 402 is available for access in response to entering theproximity zone 470, and theuser 712 may elect to access the A/V recording andcommunication device 402. The notification may be received from thebackend server 430 and/or the A/V recording andcommunication device 402. - In some of the present embodiments, at block B672 of the
process 3800, in response to receiving theaccess request 474 from the A/V recording andcommunication device 402, thebackend server 430 may transmit theaccess request 474 to theclient device 407 over the network (Internet/PSTN) 410. In such embodiments, thebackend server 430 may receive an acceptance to theaccess request 474 from the client device 407 (e.g., based on a selection of thedevice 402 from the device list 478) over the network (Internet/PSTN) 410, and transmit the acceptance to the A/V recording andcommunication device 402. In other embodiments, at block B672 of theprocess 3800, in response to receiving the access request 475 from theclient device 407, thebackend server 430 may transmit the access request 475 to the A/V recording andcommunication device 402 over the network (Internet/PSTN) 410 and/or the user'snetwork 408. - At block B674 of the
process 3800, in response to theaccess request 474, 475 being transmitted (and in some embodiments, accepted), thebackend server 430 may receive theimage data 460 being recorded by thecamera 444 of the A/V recording andcommunication device 402. In response to receiving theimage data 460, at block B676 of theprocess 3800, thebackend server 430 may transmit theimage data 460 to theclient device 407. - Now referring to
FIG. 39 ,FIG. 39 is a flowchart illustrating a process for accessing cameras of A/V recording and communication devices based on location according to various aspects of the present disclosure. At block B678, theprocess 3900 receives, from an A/V recording and communication device, first location data including a proximity zone. For example, theprocessor 502 of thebackend server 430 may receive, using thenetwork interface 520, the location data 476 including theproximity zone 470 from the A/V recording andcommunication device 402. In some of the present embodiments, theprocessor 502 of thebackend server 430 may receive the location data 476 over the network (Internet/PSTN) 410 and/or the user'snetwork 408. The location data 476 may include the location of the A/V recording andcommunication device 402 based on GPS data, known location data of the access point (e.g., router) that the A/V recording andcommunication device 402 is connected to for access to the user'snetwork 408, Internet Protocol (IP) address data, WPS data, or the like. In addition, the location data 476 may include the location data 476 for theproximity zone 470. For example, theproximity zone 470 may be defined by all of the geographical coordinates within theproximity zone 470 such that the location data 477 (e.g., geographical coordinates) of the client device 407 (received at block B680) may be compared to the geographical coordinates of theproximity zone 470 to determine if theclient device 407 is within theproximity zone 470. - In some of the present embodiments, as described above, the
backend server 430 may only receive the location data 476 from the A/V recording andcommunication device 402, and theprocessor 502 may generate theproximity zone 470 based on the location data 476 and the settings (e.g., user settings, default settings, etc.) relating to theproximity zone 470. For example, based on the settings, theproximity zone 470 may be defined by a 500-foot radius around the A/V recording andcommunication device 402. As a result, thebackend server 430 may receive the location data 476 of the A/V recording andcommunication device 402 and determine the location data 476 (e.g., the geographical coordinates) that defines a circle having a 500-foot radius around the A/V recording andcommunication device 402, and this location data 476 may be stored on thebackend server 430 as theproximity zone 470. - At block B680, the
process 3900 receives, from a client device, second location data including a location of the client device. For example, theprocessor 502 of thebackend server 430 may receive, using thenetwork interface 520, the location data 477 of theclient device 407. In some of the present embodiments, the location data 477 may be received by thebackend server 430 over the network (Internet/PSTN) 410. The location data 477 may include the geographical coordinates of the location of theclient device 407. The location data 477 may be based on GPS data, Cell ID (as described above), or the like. - In other embodiments, as described above, the
proximity zone 470 may be defined by the signal strength of the communication signals 479, 481, such as the RSSI values of the communication signals 479, 481. In such embodiments, theclient device 407 and/or the A/V recording andcommunication device 402 may measure the RSSI values of the communication signals 479, 481 received from the other device (e.g., theclient device 407 may measure the RSSI values of the communication signals 479 received from the A/V recording and communication device 402) and transmit the RSSI values to thebackend server 430. In such embodiments, the location data 476, 477 may include the RSSI values, and the location data 476, 477 may be received by thebackend server 430 from the A/V recording andcommunication device 402 and/or theclient device 407. In such embodiments, theproximity zone 470 may be defined by a threshold RSSI value for the signal strength of the communication signals 479, 481. For example, theproximity zone 470 may be defined by ZigBee RSSI values greater than −80 dBm (e.g., on a −100-0 scale), such that if the RSSI values for ZigBee communication signals 479, 481 are greater than −80 dBm (e.g., −60 dBm), theclient device 407 may be determined to be within theproximity zone 470. - At block B682, the
process 3900, in response to receiving the first location data and the second location data, analyzes the first and the second location data to determine whether the client device is within the proximity zone. For example, theprocessor 502 of thebackend server 430 may analyze the location data 477 of the client device and the location data 476 of theproximity zone 470 to determine whether theclient device 407 is within theproximity zone 470. For example, theprocessor 502 may compare the geographical coordinates from the location data 477 of theclient device 407 to the geographical coordinates that define theproximity zone 470 to determine whether theclient device 407 is within theproximity zone 470. In such an example, if it is determined that the geographical coordinates from the location data 477 of theclient device 407 are included in the geographical coordinates of the location data 476 of theproximity zone 470, it may be determined that theclient device 407 is within theproximity zone 470. - At block B684, the
process 3900, based on the determination of whether the client device is within the proximity zone (at block B682), transmits, to the client device, an access request for allowing the client device to access the camera of the A/V recording and communication device. For example, based on the determination of whether theclient device 407 is within theproximity zone 470, theprocessor 502 of thebackend server 430 may transmit, using thenetwork interface 520, theaccess request 474 to the client device 407 (e.g., over the network (Internet/PSTN) 410) for allowing theclient device 407 to access the camera 444 (and/or the image data 460) of the A/V recording andcommunication device 402. In response, theaccess request 474 may be received by theclient device 407, similar to that of block B616 ofFIG. 29 , described above. For example, in response to receiving theaccess request 474, theclient device 407 may provide a notification to the user of the client device 407 (e.g., by listing the A/V recording andcommunication device 402 in the device list 478) that theclient device 407 may access the A/V recording andcommunication device 402. - At block B686, the
process 3900, in response to the transmitting the access request, receives, from the client device, an acceptance of the access request. For example, in response to transmitting theaccess request 474 to theclient device 407, theprocessor 502 of thebackend server 430, using thenetwork interface 520, may receive the acceptance of the access request 474 (e.g., over the network (Internet/PSTN) 410). As an example, in response to receiving theaccess request 474, theclient device 407 may provide a notification to the user of the client device 407 (e.g., in the device list 478), that the A/V recording andcommunication device 402 is accessible by theclient device 407. In response, the user of theclient device 407 may select the A/V recording andcommunication device 402 from thedevice list 478, and theclient device 407 may transmit the acceptance. - In some of the present embodiments, the
access request 474 may not be transmitted to the client device 407 (at block B684) and as a result, an acceptance to theaccess request 474 may not be received (at block B686). In such embodiments, theprocess 3900 may continue directly to block B688 after block B688. - In some of the present embodiments, the location data 477 received from the client device 407 (at block B680) may also include the access request 475 from the
client device 407. In such embodiments, the access request 475 may be a general access request from theclient device 407, such that the user of theclient device 407 may want to connect/communicate with at least one A/V recording and communication device (which may include the A/V recording and communication device 402). As such, at block B682, theprocessor 502 of thebackend server 430 may determine if theclient device 407, based on the location data 477, is within theproximity zone 470 of any A/V recording and communication devices, such as the A/V recording andcommunication device 402. - In other embodiments, the user of the
client device 407 may have been provided with a notification that the A/V recording andcommunication device 402 is accessible (e.g., that theclient device 407 is within theproximity zone 470 of the A/V recording and communication device 402) and, in response to the user's input to access the A/V recording andcommunication device 402, theclient device 407 may transmit the access request 475. In such an example, the analyzing of the location data 476 and the location data 477 (at block B682) may be a verification that theclient device 407 is within theproximity zone 470, and, after the verification, theprocess 3900 may continue to block B688. - With further reference to
FIG. 39 , at block B688, theprocess 3900, in response to receiving the acceptance, retrieves, from the A/V recording and communication device, image data being recorded by the camera in a field of view of the camera. For example, in response to receiving the acceptance of the access request 474 (or in some embodiments, as described above, where there is no acceptance of theaccess request 474, such as where theclient device 407 transmits the access request 475), theprocessor 502 of thebackend server 430 may retrieve theimage data 460 recorded by thecamera 444 in a field of view of thecamera 444. For example, as described above, theimage data 460 may be a live recording, and thebackend server 430 may receive the live recording from thecamera 444 over the network (Internet/PSTN) 410 using thenetwork interface 520. In other embodiments, theimage data 460 may be stored on the A/V recording andcommunication device 402, and thebackend server 430 may retrieve theimage data 460 from the A/V recording andcommunication device 402. In some of the present embodiments, the A/V recording andcommunication device 402 may be programmed to transmit theimage data 460 to thebackend server 430 each time thecamera 444 records theimage data 460. In such embodiments, theimage data 460 recorded by the A/V recording andcommunication device 402 may already be stored on thebackend server 430, and thebackend server 430 may retrieve theimage data 460 from thenon-volatile memory 506, for example. - At block B690, the
process 3900, in response to retrieving the image data, transmits the image data to the client device. For example, in response to retrieving theimage data 460, theprocessor 502 of thebackend server 430, using thenetwork interface 520, may transmit theimage data 460 to theclient device 407. In some of the present embodiments, theimage data 460 may be transmitted over the network (Internet/PSTN) 410. In response, theclient device 407 may receive theimage data 460 and display a virtual representation of theimage data 460 on thedisplay 525. - The processes of
FIG. 39 may be implemented in a variety of embodiments, including those discussed below. However, the below-detailed embodiments are not intended to be limiting, and are provided merely as example embodiments of the present disclosure. Other embodiments similar to those outlined herein may also fall within the scope of the present disclosure. - With reference to
FIGS. 41-43 , thebackend server 430 may receive the location data 476 from at least one of the A/V recording andcommunication device backend server 430 may receive the location data 476 from each of the A/V recording andcommunication devices devices backend server 430 may receive theproximity zone 716 of each of the A/V recording andcommunication devices proximity zone 716, as described above. Thebackend server 430 may receive the location data 477 of the client device 407 (at block B680). In some of the present embodiments, the client device 407 (and/or other client devices) may transmit their location to thebackend server 430 at an interval, such as every 10 seconds, every 20 seconds, every 30 seconds, or every minute, for example. In some of the present embodiments, thebackend server 430 may receive theimage data 460 from the A/V recording andcommunication devices image data 460 includes any suspicious activity (e.g., suspicious activity warnings/flags). In response to determining that theimage data 460 includes suspicious activity, thebackend server 430 may analyze the location data 477 received from the client device 407 (and/or other client devices) to determine if theclient device 407 is within theproximity zone 716 of the A/V recording andcommunication device 726 that generated theimage data 460 including the suspicious activity (at block B682). In response to determining that theclient device 407 is within theproximity zone 716, thebackend server 430 may transmit theaccess request 474 to the client device 407 (at block B684), as described above, and may receive the acceptance of theaccess request 474 from the client device 407 (at block B686). In response to receiving the acceptance, thebackend server 430 may retrieve (at block B688) and transmit (at block B690) theimage data 460 from the A/V recording andcommunication device 726 to theclient device 407. - In some of the present embodiments, the
image data 460 may be transmitted live, such that theuser 712 of theclient device 407 can see the current field of view of thecamera 444 of the A/V recording andcommunication device 726. In other embodiments, such as where theburglar 740 has now left the field of view of the camera 444 (e.g., as determined by computer vision), theimage data 460 transmitted to theclient device 407 may be thepre-recorded image data 460 including theburglar 740, and thus may be retrieved from thenon-volatile memory 506 of thebackend server 430 and/or from the A/V recording andcommunication device 726. In such embodiments, theuser 712 may be able to see the appearance (e.g., physical appearance, identity, clothing, etc.) of theburglar 740 and/or thegun 742 being carried by theburglar 740 and determine that theburglar 740 is in fact suspicious. As a result, theuser 712 may be more likely to hide, flee, alert law enforcement, or take other appropriate actions based on the knowledge of the burglar's 740 presence. In addition, theuser 712 may access thedevice list 478 after being notified of theburglar 740, and determine if any of the other A/V recording and communication devices in theproximity zone 716 have identified suspicious activity (e.g., the burglar 740), in order to determine the safest exit route and/or hiding places, for example. - The processes 2600-3900, described above, may provide users of client devices that may not be associated with A/V recording and communication devices in the user's vicinity, access to image data recorded by the A/V recording and communication devices. As a result, the user may be more likely to avoid dangerous and/or suspicious situations that the user may not otherwise be made aware of. For example, the user may be able to view video of a suspicious person in the vicinity of the user by accessing the camera of an A/V recording and communication device in the user's vicinity. After viewing the suspicious person, the user may turn around and decide to take an alternate route, or the user may alert law enforcement, ultimately preventing or detecting criminal activity. As a result, the overall public safety may be enhanced, as persons may be more likely to avoid dangerous scenarios that they otherwise may not have been aware of
- As discussed above, the present disclosure provides numerous examples of methods and systems including A/V recording and communication doorbells, but the present embodiments are equally applicable for A/V recording and communication devices other than doorbells. For example, the present embodiments may include one or more A/V recording and communication security cameras instead of, or in addition to, one or more A/V recording and communication doorbells. An example A/V recording and communication security camera may include substantially all of the structure and functionality of the
doorbell 130, but without thefront button 148, thebutton actuator 228, and/or thelight pipe 232. -
FIG. 44 is a functional block diagram of a client device 800 on which the present embodiments may be implemented according to various aspects of the present disclosure. The user's client device 114 described with reference toFIG. 1 may include some or all of the components and/or functionality of the client device 800. The client device 800 may comprise, for example, a smartphone. - With reference to
FIG. 44 , the client device 800 includes aprocessor 802, amemory 804, auser interface 806, acommunication module 808, and adataport 810. These components are communicatively coupled together by aninterconnect bus 812. Theprocessor 802 may include any processor used in smartphones and/or portable computing devices, such as an ARM processor (a processor based on the RISC (reduced instruction set computer) architecture developed by Advanced RISC Machines (ARM).). In some embodiments, theprocessor 802 may include one or more other processors, such as one or more conventional microprocessors, and/or one or more supplementary co-processors, such as math co-processors. - The
memory 804 may include both operating memory, such as random-access memory (RAM), as well as data storage, such as read-only memory (ROM), hard drives, flash memory, or any other suitable memory/storage element. Thememory 804 may include removable memory elements, such as a CompactFlash card, a MultiMediaCard (MMC), and/or a Secure Digital (SD) card. In some embodiments, thememory 804 may comprise a combination of magnetic, optical, and/or semiconductor memory, and may include, for example, RAM, ROM, flash drive, and/or a hard disk or drive. Theprocessor 802 and thememory 804 each may be, for example, located entirely within a single device, or may be connected to each other by a communication medium, such as a USB port, a serial port cable, a coaxial cable, an Ethernet-type cable, a telephone line, a radio frequency transceiver, or other similar wireless or wired medium or combination of the foregoing. For example, theprocessor 802 may be connected to thememory 804 via thedataport 810. - The
user interface 806 may include any user interface or presentation elements suitable for a smartphone and/or a portable computing device, such as a keypad, a display screen, a touchscreen, a microphone, and a speaker. Thecommunication module 808 is configured to handle communication links between the client device 800 and other, external devices or receivers, and to route incoming/outgoing data appropriately. For example, inbound data from thedataport 810 may be routed through thecommunication module 808 before being directed to theprocessor 802, and outbound data from theprocessor 802 may be routed through thecommunication module 808 before being directed to thedataport 810. Thecommunication module 808 may include one or more transceiver modules capable of transmitting and receiving data, and using, for example, one or more protocols and/or technologies, such as GSM, UMTS (3GSM), IS-95 (CDMA one), IS-2000 (CDMA 2000), LTE, FDMA, TDMA, W-CDMA, CDMA, OFDMA, Wi-Fi, WiMAX, or any other protocol and/or technology. - The
dataport 810 may be any type of connector used for physically interfacing with a smartphone and/or a portable computing device, such as a mini-USB port or an IPHONE®/IPOD® 30-pin connector or LIGHTNING® connector. In other embodiments, thedataport 810 may include multiple communication channels for simultaneous communication with, for example, other processors, servers, and/or client terminals. - The
memory 804 may store instructions for communicating with other systems, such as a computer. Thememory 804 may store, for example, a program (e.g., computer program code) adapted to direct theprocessor 802 in accordance with the present embodiments. The instructions also may include program elements, such as an operating system. While execution of sequences of instructions in the program causes theprocessor 802 to perform the process steps described herein, hard-wired circuitry may be used in place of, or in combination with, software/firmware instructions for implementation of the processes of the present embodiments. Thus, the present embodiments are not limited to any specific combination of hardware and software. -
FIG. 45 is a functional block diagram of a general-purpose computing system on which the present embodiments may be implemented according to various aspects of present disclosure. Thecomputer system 900 may execute at least some of the operations described above. Thecomputer system 900 may be embodied in at least one of a personal computer (also referred to as a desktop computer) 900A, a portable computer (also referred to as a laptop or notebook computer) 900B, and/or a server 900C. A server is a computer program and/or a machine that waits for requests from other machines or software (clients) and responds to them. A server typically processes data. The purpose of a server is to share data and/or hardware and/or software resources among clients. This architecture is called the client—server model. The clients may run on the same computer or may connect to the server over a network. Examples of computing servers include database servers, file servers, mail servers, print servers, web servers, game servers, and application servers. The term server may be construed broadly to include any computerized process that shares a resource to one or more client processes. - The
computer system 900 may include at least oneprocessor 910,memory 920, at least onestorage device 930, and input/output (I/O)devices 940. Some or all of thecomponents system bus 950. Theprocessor 910 may be single- or multi-threaded and may have one or more cores. Theprocessor 910 may execute instructions, such as those stored in thememory 920 and/or in thestorage device 930. Information may be received and output using one or more I/O devices 940. - The
memory 920 may store information, and may be a computer-readable medium, such as volatile or non-volatile memory. The storage device(s) 930 may provide storage for thesystem 900, and may be a computer-readable medium. In various aspects, the storage device(s) 930 may be a flash memory device, a hard disk device, an optical disk device, a tape device, or any other type of storage device. - The I/
O devices 940 may provide input/output operations for thesystem 900. The I/O devices 940 may include a keyboard, a pointing device, and/or a microphone. The I/O devices 940 may further include a display unit for displaying graphical user interfaces, a speaker, and/or a printer. External data may be stored in one or more accessibleexternal databases 960. - The features of the present embodiments described herein may be implemented in digital electronic circuitry, and/or in computer hardware, firmware, software, and/or in combinations thereof. Features of the present embodiments may be implemented in a computer program product tangibly embodied in an information carrier, such as a machine-readable storage device, and/or in a propagated signal, for execution by a programmable processor. Embodiments of the present method steps may be performed by a programmable processor executing a program of instructions to perform functions of the described implementations by operating on input data and generating output.
- The features of the present embodiments described herein may be implemented in one or more computer programs that are executable on a programmable system including at least one programmable processor coupled to receive data and/or instructions from, and to transmit data and/or instructions to, a data storage system, at least one input device, and at least one output device. A computer program may include a set of instructions that may be used, directly or indirectly, in a computer to perform a certain activity or bring about a certain result. A computer program may be written in any form of programming language, including compiled or interpreted languages, and it may be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment.
- Suitable processors for the execution of a program of instructions may include, for example, both general and special purpose processors, and/or the sole processor or one of multiple processors of any kind of computer. Generally, a processor may receive instructions and/or data from a read only memory (ROM), or a random-access memory (RAM), or both. Such a computer may include a processor for executing instructions and one or more memories for storing instructions and/or data.
- Generally, a computer may also include, or be operatively coupled to communicate with, one or more mass storage devices for storing data files. Such devices include magnetic disks, such as internal hard disks and/or removable disks, magneto-optical disks, and/or optical disks. Storage devices suitable for tangibly embodying computer program instructions and/or data may include all forms of non-volatile memory, including for example semiconductor memory devices, such as EPROM, EEPROM, and flash memory devices, magnetic disks such as internal hard disks and removable disks, magneto-optical disks, and CD-ROM and DVD-ROM disks. The processor and the memory may be supplemented by, or incorporated in, one or more ASICs (application-specific integrated circuits).
- To provide for interaction with a user, the features of the present embodiments may be implemented on a computer having a display device, such as an LCD (liquid crystal display) monitor, for displaying information to the user. The computer may further include a keyboard, a pointing device, such as a mouse or a trackball, and/or a touchscreen by which the user may provide input to the computer.
- The features of the present embodiments may be implemented in a computer system that includes a back-end component, such as a data server, and/or that includes a middleware component, such as an application server or an Internet server, and/or that includes a front-end component, such as a client computer having a graphical user interface (GUI) and/or an Internet browser, or any combination of these. The components of the system may be connected by any form or medium of digital data communication, such as a communication network. Examples of communication networks may include, for example, a LAN (local area network), a WAN (wide area network), and/or the computers and networks forming the Internet.
- The computer system may include clients and servers. A client and server may be remote from each other and interact through a network, such as those described herein. The relationship of client and server may arise by virtue of computer programs running on the respective computers and having a client-server relationship to each other.
- As used herein, the phrases “at least one of A, B and C,” “at least one of A, B, or C,” and “A, B, and/or C” are synonymous and mean logical “OR” in the computer science sense. Thus, each of the foregoing phrases should be understood to read on (A), (B), (C), (A and B), (A and C), (B and C), and (A and B and C), where A, B, and C are variables representing elements or features of the claim. Also, while these examples are described with three variables (A, B, C) for ease of understanding, the same interpretation applies to similar phrases in these formats with any number of two or more variables.
- The above description presents the best mode contemplated for carrying out the present embodiments, and of the manner and process of practicing them, in such full, clear, concise, and exact terms as to enable any person skilled in the art to which they pertain to practice these embodiments. The present embodiments are, however, susceptible to modifications and alternate constructions from those discussed above that are fully equivalent. Consequently, the present invention is not limited to the particular embodiments disclosed. On the contrary, the present invention covers all modifications and alternate constructions coming within the spirit and scope of the present disclosure. For example, the steps in the processes described herein need not be performed in the same order as they have been presented, and may be performed in any order(s). Further, steps that have been presented as being performed separately may in alternative embodiments be performed concurrently. Likewise, steps that have been presented as being performed concurrently may in alternative embodiments be performed separately.
Claims (19)
1. A method for providing image data, captured by a video doorbell located at a house, to a first client device not associated with the video doorbell or the house, the method comprising:
receiving, at the video doorbell and from a second client device associated with the video doorbell, a configuration of a proximity zone about the video doorbell and based upon a received signal strength indication (RSSI) scale;
receiving, by the video doorbell and from the first client device, a communication signal including a request for access to the image data of the video doorbell;
determining a received signal strength indication (RSSI) of the communication signal;
determining, based upon the RSSI and the RSSI scale, whether the first client device is within the proximity zone;
sending a notification of the request for access by the first client device to the second client device;
receiving, in response to the notification, an indication of whether the first client device may access the video doorbell; and
when the first client device is within the proximity zone and can access the video doorbell, sending the image data to the first client device.
2. An audio/video recording and communication device (A/V device) method for providing access to a first client device not associated with the A/V device, the method comprising:
receiving, at the A/V device from the first client device, a communication signal including a request for access to the A/V device;
determining whether the A/V device is accessible by the first client device; and
wherein image data generated by a camera of the A/V device is sent to the first client device.
3. The A/V device method of claim 2 , further comprising determining whether the first client device is within a proximity zone about the A/V device.
4. The A/V device method of claim 3 , further comprising (a) determining a received signal strength indication (RSSI) of the communication signal, and (b) using the RSSI to determine whether the first client device is within the proximity zone.
5. The A/V device method of claim 4 , a signal type of the communication signal comprising one of Wi-Fi, Bluetooth, and ZigBee.
6. The A/V device method of claim 5 , the proximity zone being based upon an RSSI scale corresponding to the signal type, wherein determining whether the first client device is within the proximity zone comprises using the RSSI scale.
7. The A/V device method of claim 2 , further comprising comparing location data of the first client device received within the communication signal to a proximity zone about the A/V device to determine whether the first client device is within the proximity zone.
8. The A/V device method of claim 2 , further comprising:
generating, at the A/V device, an ad-hoc network; and
connecting with the first client device via the ad-hoc network to transmit the image data to the first client device.
9. The A/V device method of claim 2 , further comprising:
transmitting, to the first client device, network credentials of a network to which the A/V device is connected; and
connecting with the first client device via the network to transmit the image data to the first client device.
10. The A/V device method of claim 2 , further comprising connecting with the first client device via the Internet to transmit the image data to the first client device.
11. The A/V device method of claim 2 , further comprising sending a notification of the request for access to a second client device associated with the A/V device, wherein a user of the second client device determines whether the A/V device is accessible by the first client device.
12. The A/V device method of claim 2 , further comprising determining whether the first client device is associated with a second audio/video recording and communication device that is not associated with the A/V device, wherein the A/V device is accessible by the first client device only when the first client device is associated with the second audio/video recording and communication device.
13. An audio/video recording and communication device (A/V device) method for providing image data access to a first client device not associated with the A/V device, the method comprising:
transmitting, at intervals from the A/V device, a communication signal;
receiving, at the A/V device and in response to the communication signal, an access request from the first client device;
determining whether the A/V device is accessible by the first client device; and
wherein image data generated by a camera of the A/V device is sent to the first client device.
14. The A/V device method of claim 13 , further comprising:
receiving, at the A/V device and in response to the communication signal, a received signal strength indication (RSSI) of the communication signal as determined by the first client device; and
determining whether the first client device is within a proximity zone about the A/V device based, at least in part, upon the RSSI, wherein the A/V device is accessible by the first client device only when the first client device is within the proximity zone.
15. The A/V device method of claim 14 , a signal type of the communication signal comprising one of Wi-Fi, Bluetooth, and ZigBee.
16. The A/V device method of claim 15 , the proximity zone being defined based upon an RSSI scale corresponding to the signal type, wherein determining whether the first client device is within the proximity zone comprises using the RSSI and the RSSI scale.
17. The A/V device method of claim 13 , further comprising:
receiving, at the A/V device and in response to the communication signal, location data of the first client device; and
determining, based upon the location data, whether the first client device is within a proximity zone about the A/V device, wherein the A/V device is accessible by the first client device only when the first client device is within the proximity zone.
18. The A/V device method of claim 13 , further comprising sending a notification of the access request to a second client device associated with the A/V device, wherein a user of the second client device determines whether the A/V device is accessible by the first client device.
19. The A/V device method of claim 13 , further comprising determining whether the first client device is associated with a second audio/video recording and communication device, wherein the A/V device is accessible by the first client device only when the first client device is associated with the second audio/video recording and communication device and is part of a network of owners of A/V devices.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US16/716,383 US20200120309A1 (en) | 2017-07-06 | 2019-12-16 | Accessing cameras of audio/video recording and communication devices based on location |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201762529460P | 2017-07-06 | 2017-07-06 | |
US16/028,252 US10511810B2 (en) | 2017-07-06 | 2018-07-05 | Accessing cameras of audio/video recording and communication devices based on location |
US16/716,383 US20200120309A1 (en) | 2017-07-06 | 2019-12-16 | Accessing cameras of audio/video recording and communication devices based on location |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/028,252 Continuation US10511810B2 (en) | 2017-07-06 | 2018-07-05 | Accessing cameras of audio/video recording and communication devices based on location |
Publications (1)
Publication Number | Publication Date |
---|---|
US20200120309A1 true US20200120309A1 (en) | 2020-04-16 |
Family
ID=64903533
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/028,252 Active US10511810B2 (en) | 2017-07-06 | 2018-07-05 | Accessing cameras of audio/video recording and communication devices based on location |
US16/716,383 Abandoned US20200120309A1 (en) | 2017-07-06 | 2019-12-16 | Accessing cameras of audio/video recording and communication devices based on location |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/028,252 Active US10511810B2 (en) | 2017-07-06 | 2018-07-05 | Accessing cameras of audio/video recording and communication devices based on location |
Country Status (1)
Country | Link |
---|---|
US (2) | US10511810B2 (en) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2022000378A1 (en) * | 2020-07-01 | 2022-01-06 | 深圳市大疆创新科技有限公司 | Radar apparatus and mobile device |
US11653076B2 (en) * | 2020-06-03 | 2023-05-16 | Hubbell Incorporated | Internet protocol (IP)-speaker with IP-camera |
Families Citing this family (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10367980B1 (en) * | 2018-01-26 | 2019-07-30 | Zheng Li | Camera device integrated with light source and method for capturing images |
USD875158S1 (en) * | 2018-06-05 | 2020-02-11 | Guangzhou Bosma Corp | Camera |
US11232685B1 (en) * | 2018-12-04 | 2022-01-25 | Amazon Technologies, Inc. | Security system with dual-mode event video and still image recording |
CN109581747A (en) * | 2019-01-02 | 2019-04-05 | 京东方科技集团股份有限公司 | Light source module group and display module |
FR3092458B1 (en) * | 2019-02-05 | 2022-03-18 | Engie | Low-power hub and detector configured to communicate with this hub |
EP3731197A1 (en) * | 2019-04-26 | 2020-10-28 | Carrier Corporation | Geolocation based security in intrusion systems |
US11659332B2 (en) * | 2019-07-30 | 2023-05-23 | Dolby Laboratories Licensing Corporation | Estimating user location in a system including smart audio devices |
USD945898S1 (en) | 2020-03-03 | 2022-03-15 | Amazon Technologies, Inc. | Doorbell |
Citations (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20110211069A1 (en) * | 2010-02-26 | 2011-09-01 | Bryan Sybesma | Virtual internet protocol modulator |
US20120257061A1 (en) * | 2011-04-05 | 2012-10-11 | Honeywell International Inc. | Neighborhood Camera Linking System |
US20130201847A1 (en) * | 2010-04-26 | 2013-08-08 | Interdigital Patent Holdings, Inc. | Method and apparatus to enable ad hoc networks |
US20140187190A1 (en) * | 2012-12-31 | 2014-07-03 | Motorola Solutions, Inc. | Method and apparatus for receiving a data stream during an incident |
US20150139213A1 (en) * | 2013-11-18 | 2015-05-21 | Qualcomm Incorporated | Wireless discovery location and ranging |
US20160094810A1 (en) * | 2014-09-30 | 2016-03-31 | Verizon Patent And Licensing Inc. | System and method for providing neighborhood services through networked cameras |
US20170094523A1 (en) * | 2015-09-25 | 2017-03-30 | Mutualink, Inc. | Enabling Emergency Access to Secure Wireless Communications Networks |
US20170124834A1 (en) * | 2014-06-06 | 2017-05-04 | Maher Pedersoli | Systems and methods for secure collection of surveillance data |
US20170187995A1 (en) * | 2015-09-22 | 2017-06-29 | SkyBell Technologies, Inc. | Doorbell communication systems and methods |
US20170264604A1 (en) * | 2016-03-08 | 2017-09-14 | Dean Drako | Apparatus for sharing private video streams with first responders and method of operation |
US20170374560A1 (en) * | 2016-06-15 | 2017-12-28 | Luma Home, Inc. | System and method for network access point installation and access control |
US20180091962A1 (en) * | 2016-09-23 | 2018-03-29 | Apple Inc. | Context-dependent allocation of shared resources in a wireless communication interface |
Family Cites Families (120)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6072402A (en) | 1992-01-09 | 2000-06-06 | Slc Technologies, Inc. | Secure entry system with radio communications |
US4764953A (en) | 1987-05-22 | 1988-08-16 | Chern Lih Ju | Method and apparatus for remote doorbell answering |
KR950005150B1 (en) | 1992-03-23 | 1995-05-18 | 조명언 | Image monitor apparatus of a portable tv |
US5428388A (en) | 1992-06-15 | 1995-06-27 | Richard von Bauer | Video doorbell system |
JPH07264532A (en) | 1994-02-03 | 1995-10-13 | Samsung Electron Co Ltd | Message storing/outputting device of built-in camera type magnetic recording/reproducing equipment, and method therefor |
US6185294B1 (en) | 1996-11-01 | 2001-02-06 | O. Joseph Chornenky | Method and apparatus for installing telephone intercom-voice messaging apparatus at doorbell for dwelling |
IT1306222B1 (en) | 1996-12-09 | 2001-06-04 | Sideral Srl | ANTI-INTRUSION PROTECTION AND ALARM SYSTEM FOR VILLAS, BUILDINGS FOR HOUSING AND WORK, THROUGH VIDEO EQUIPMENT IN GENERAL |
US6192257B1 (en) | 1998-03-31 | 2001-02-20 | Lucent Technologies Inc. | Wireless communication terminal having video image capability |
US6429893B1 (en) | 1998-06-04 | 2002-08-06 | Alfred X. Xin | Security system |
US6970183B1 (en) | 2000-06-14 | 2005-11-29 | E-Watch, Inc. | Multimedia surveillance and monitoring system including network configuration |
US6271752B1 (en) | 1998-10-02 | 2001-08-07 | Lucent Technologies, Inc. | Intelligent multi-access system |
US6633231B1 (en) | 1999-06-07 | 2003-10-14 | Horiba, Ltd. | Communication device and auxiliary device for communication |
US8520068B2 (en) | 1999-07-20 | 2013-08-27 | Comcast Cable Communications, Llc | Video security system |
US6476858B1 (en) | 1999-08-12 | 2002-11-05 | Innovation Institute | Video monitoring and security system |
FR2797732B1 (en) | 1999-08-16 | 2001-11-09 | Dpf Electronique | DOOR AUDIOVIDEO ANSWERING MACHINE |
GB2354394B (en) | 1999-09-09 | 2003-11-26 | Roke Manor Research | Method and apparatus for communicating via the internet |
JP2001103463A (en) | 1999-09-30 | 2001-04-13 | Matsushita Electric Ind Co Ltd | Interphone system |
GB9924436D0 (en) | 1999-10-16 | 1999-12-15 | Applied Technologies Mfg Ltd | Internet & intranet remote viewing & security system |
US20020094111A1 (en) | 2000-05-19 | 2002-07-18 | Puchek Daniel R. | Access control method and apparatus |
AU2001263483A1 (en) | 2000-05-26 | 2001-12-11 | Royal Thoughts L.L.C. | Modular communication and control system and method |
JP2002033839A (en) | 2000-07-18 | 2002-01-31 | Nec Corp | Security system using intercom, and service providing method |
JP2002125059A (en) | 2000-10-13 | 2002-04-26 | Matsushita Electric Ind Co Ltd | Interphone system and interphone system transfer method for multiple dwelling house |
NO314376B1 (en) | 2001-04-11 | 2003-03-10 | Endre Roesjoe | Access control system |
JP2002344640A (en) | 2001-05-14 | 2002-11-29 | Matsushita Electric Ind Co Ltd | Interphone system |
JP2002342863A (en) | 2001-05-20 | 2002-11-29 | Yukio Shimada | Communication interphone |
JP2002354137A (en) | 2001-05-26 | 2002-12-06 | Mihoko Shimada | Multiple dwelling house automatic telephone message answering interphone system |
JP2002368890A (en) | 2001-06-11 | 2002-12-20 | Katsunori Terasawa | Empty home communication facility |
US20030043047A1 (en) | 2001-08-29 | 2003-03-06 | Braun David A. | Electronic doorbell system |
KR100459047B1 (en) | 2001-09-27 | 2004-12-03 | 모빌토크(주) | Remote Visitor-Identification and Door opening-shutting Control Apparatus using Mobile Communication Terminal and Mobile Internet Service |
US6658091B1 (en) | 2002-02-01 | 2003-12-02 | @Security Broadband Corp. | LIfestyle multimedia security system |
WO2003067360A2 (en) | 2002-02-06 | 2003-08-14 | Nice Systems Ltd. | System and method for video content analysis-based detection, surveillance and alarm management |
JP4454907B2 (en) | 2002-03-27 | 2010-04-21 | アイホン株式会社 | TV door phone system |
AU2003230229A1 (en) | 2002-05-09 | 2003-11-11 | Castaldo - Elettronica And Telecomunicazioni | Portable videointercom set |
TW577032B (en) | 2002-06-28 | 2004-02-21 | Hoa Telecom Network Co Ltd | Intercom system |
US20040095254A1 (en) | 2002-09-20 | 2004-05-20 | Maruszczak Douglas D. | Door bell answering system |
JP2004128835A (en) | 2002-10-02 | 2004-04-22 | Nec Fielding Ltd | Absent house monitoring system, monitoring terminal unit, and method for dealing with absent house visitor |
US8154581B2 (en) | 2002-10-15 | 2012-04-10 | Revolutionary Concepts, Inc. | Audio-video communication system for receiving person at entrance |
US8139098B2 (en) | 2002-10-15 | 2012-03-20 | Revolutionary Concepts, Inc. | Video communication method for receiving person at entrance |
US8144183B2 (en) | 2002-10-15 | 2012-03-27 | Revolutionary Concepts, Inc. | Two-way audio-video communication method for receiving person at entrance |
US7193644B2 (en) | 2002-10-15 | 2007-03-20 | Revolutionary Concepts, Inc. | Automated audio video messaging and answering system |
US6753774B2 (en) | 2002-10-25 | 2004-06-22 | Tung-Hsing Pan | Antitheft system with signals transmitted by mobile phone network |
US20040086093A1 (en) | 2002-10-29 | 2004-05-06 | Schranz Paul Steven | VoIP security monitoring & alarm system |
US20040085205A1 (en) | 2002-10-31 | 2004-05-06 | Jacob Yeh | Monitor system with video and audio transmission actuated by doorbell actuator |
US20040135686A1 (en) | 2002-11-04 | 2004-07-15 | Parker Dionna O. | Remote audio visual home monitor |
US7012523B2 (en) | 2002-11-05 | 2006-03-14 | Stuart John C | System for surveillance of and communication with residential entryway from remote location using existing telephone lines |
CN2585521Y (en) | 2002-11-22 | 2003-11-05 | 张健 | Video door bell with automatic photographing and recording function |
US7062291B2 (en) | 2003-01-06 | 2006-06-13 | Vtech Telecommunications Limited | Wireless multi-handset telephone system with integrated video monitoring accessories |
US7738917B2 (en) | 2003-03-31 | 2010-06-15 | Vtech Telecommunications Limited | Intercom/wireless door bell for multi-handset telephone system |
GB2400958B (en) | 2003-04-23 | 2005-12-07 | Frank Cunningham | Security system |
ITMI20031012A1 (en) | 2003-05-20 | 2004-11-21 | Fly S R L | EQUIPMENT FOR SHOOTING, REMOTE TRANSMISSION AND VISUALIZATION OF IMAGES AND SOUNDS FROM / FOR A MULTIPLE OF TERMINALS. |
US7450638B2 (en) | 2003-07-21 | 2008-11-11 | Sony Corporation | Power-line communication based surveillance system |
JP4066924B2 (en) | 2003-09-19 | 2008-03-26 | ソニー株式会社 | Transmission / reception system |
US7085361B2 (en) | 2003-12-18 | 2006-08-01 | Bellsouth Intellectual Property Corporation | Methods and systems for communication from an exterior of a location |
US7373395B2 (en) | 2004-02-04 | 2008-05-13 | Perseus Wireless, Inc. | Method and system for providing information to remote clients |
JP2005341040A (en) | 2004-05-25 | 2005-12-08 | Mitsubishi Electric Corp | Communications apparatus, communications system, communication method, and program |
US7109860B2 (en) | 2004-06-02 | 2006-09-19 | Inventec Appliances Corporation | Surveillance apparatus integrated with mobile phone |
KR100557895B1 (en) | 2004-06-14 | 2006-03-10 | 백형동 | Videophone Having Multi- function |
US7304572B2 (en) | 2004-06-29 | 2007-12-04 | Motorola, Inc. | Cellular communications based intercom system and methods |
JP2006048174A (en) | 2004-07-30 | 2006-02-16 | A・T・Gジャパン株式会社 | Home security system |
KR100561633B1 (en) | 2004-09-22 | 2006-03-20 | 한국전자통신연구원 | Intelligent system and method of visitor confirming and communication service using mobile terminal |
JP3992038B2 (en) | 2004-11-16 | 2007-10-17 | セイコーエプソン株式会社 | Electronic element mounting method, electronic device manufacturing method, circuit board, electronic device |
IL165959A0 (en) | 2004-12-23 | 2006-01-15 | Vascode Technologies Ltd | Method and device for use in a cellular communication network |
US20060139449A1 (en) | 2004-12-23 | 2006-06-29 | Wen-Liang Cheng | Wireless audio-video doorbell monitoring system |
CA2532502A1 (en) | 2005-01-12 | 2006-07-12 | Walter W. Wang | Remote viewing system |
CN2792061Y (en) | 2005-03-01 | 2006-06-28 | 王春芳 | Wireless long-distance video signal transmitting door bell |
US7643056B2 (en) | 2005-03-14 | 2010-01-05 | Aptina Imaging Corporation | Motion detecting camera system |
JP4616045B2 (en) | 2005-03-18 | 2011-01-19 | Dxアンテナ株式会社 | intercom |
US20070008081A1 (en) | 2005-06-17 | 2007-01-11 | Tylicki Scott B | MP3 doorbell chime system |
US7382249B2 (en) | 2005-08-31 | 2008-06-03 | Complete Surveillance Solutions | Security motion sensor and video recording system |
ES2302430B2 (en) | 2006-04-28 | 2009-03-16 | Universidad De Malaga | MODULAR SYSTEM FOR WIRELESS ELECTRONIC PORTER. |
US8619136B2 (en) | 2006-12-01 | 2013-12-31 | Centurylink Intellectual Property Llc | System and method for home monitoring using a set top box |
JP5367239B2 (en) | 2007-06-28 | 2013-12-11 | 京セラ株式会社 | Mobile terminal and application display method of mobile terminal |
US9077863B2 (en) * | 2007-10-08 | 2015-07-07 | Nice Systems Ltd. | System and method for managing location based video services |
US20100225455A1 (en) | 2007-10-24 | 2010-09-09 | Jimmy David Claiborne | Polyphonic Doorbell Chime System |
US8581957B2 (en) * | 2008-01-09 | 2013-11-12 | Sony Corporation | Video conference using an external video stream |
US8736678B2 (en) * | 2008-12-11 | 2014-05-27 | At&T Intellectual Property I, L.P. | Method and apparatus for vehicle surveillance service in municipal environments |
US20110058034A1 (en) * | 2009-09-05 | 2011-03-10 | Alwaysview, Inc. | Sharing of video surveillance information |
US20130057695A1 (en) | 2011-09-07 | 2013-03-07 | Timothy J. Huisking | Method and apparatus for unlocking/locking a door and enabling two-way communications with a door security system via a smart phone |
US8934754B2 (en) * | 2012-11-13 | 2015-01-13 | International Business Machines Corporation | Providing emergency access to surveillance video |
US10999561B2 (en) | 2013-03-15 | 2021-05-04 | Vivint, Inc. | Methods for using an image capture device integrated at a building entry with an automation control panel, and systems and devices related thereto |
US9172920B1 (en) | 2014-09-01 | 2015-10-27 | SkyBell Technologies, Inc. | Doorbell diagnostics |
US8953040B1 (en) | 2013-07-26 | 2015-02-10 | SkyBell Technologies, Inc. | Doorbell communication and electrical systems |
US8780201B1 (en) | 2013-07-26 | 2014-07-15 | SkyBell Technologies, Inc. | Doorbell communication systems and methods |
US9237318B2 (en) | 2013-07-26 | 2016-01-12 | SkyBell Technologies, Inc. | Doorbell communication systems and methods |
US9058738B1 (en) | 2013-07-26 | 2015-06-16 | SkyBell Technologies, Inc. | Doorbell communication systems and methods |
US8941736B1 (en) | 2013-07-26 | 2015-01-27 | SkyBell Technologies, Inc. | Doorbell communication systems and methods |
US9736284B2 (en) | 2013-07-26 | 2017-08-15 | SkyBell Technologies, Inc. | Doorbell communication and electrical systems |
US9060104B2 (en) | 2013-07-26 | 2015-06-16 | SkyBell Technologies, Inc. | Doorbell communication systems and methods |
US9118819B1 (en) | 2013-07-26 | 2015-08-25 | SkyBell Technologies, Inc. | Doorbell communication systems and methods |
US9142214B2 (en) | 2013-07-26 | 2015-09-22 | SkyBell Technologies, Inc. | Light socket cameras |
US8937659B1 (en) | 2013-07-26 | 2015-01-20 | SkyBell Technologies, Inc. | Doorbell communication and electrical methods |
US9013575B2 (en) | 2013-07-26 | 2015-04-21 | SkyBell Technologies, Inc. | Doorbell communication systems and methods |
US9065987B2 (en) | 2013-07-26 | 2015-06-23 | SkyBell Technologies, Inc. | Doorbell communication systems and methods |
US9179109B1 (en) | 2013-12-06 | 2015-11-03 | SkyBell Technologies, Inc. | Doorbell communication systems and methods |
US9172922B1 (en) | 2013-12-06 | 2015-10-27 | SkyBell Technologies, Inc. | Doorbell communication systems and methods |
US9179107B1 (en) | 2013-07-26 | 2015-11-03 | SkyBell Technologies, Inc. | Doorbell chime systems and methods |
US9342936B2 (en) | 2013-07-26 | 2016-05-17 | SkyBell Technologies, Inc. | Smart lock systems and methods |
US9049352B2 (en) | 2013-07-26 | 2015-06-02 | SkyBell Technologies, Inc. | Pool monitor systems and methods |
US9179108B1 (en) | 2013-07-26 | 2015-11-03 | SkyBell Technologies, Inc. | Doorbell chime systems and methods |
US9160987B1 (en) | 2013-07-26 | 2015-10-13 | SkyBell Technologies, Inc. | Doorbell chime systems and methods |
US8947530B1 (en) | 2013-07-26 | 2015-02-03 | Joseph Frank Scalisi | Smart lock systems and methods |
US9230424B1 (en) | 2013-12-06 | 2016-01-05 | SkyBell Technologies, Inc. | Doorbell communities |
US9247219B2 (en) | 2013-07-26 | 2016-01-26 | SkyBell Technologies, Inc. | Doorbell communication systems and methods |
US9094584B2 (en) | 2013-07-26 | 2015-07-28 | SkyBell Technologies, Inc. | Doorbell communication systems and methods |
US9113051B1 (en) | 2013-07-26 | 2015-08-18 | SkyBell Technologies, Inc. | Power outlet cameras |
US9172921B1 (en) | 2013-12-06 | 2015-10-27 | SkyBell Technologies, Inc. | Doorbell antenna |
US9060103B2 (en) | 2013-07-26 | 2015-06-16 | SkyBell Technologies, Inc. | Doorbell security and safety |
US9113052B1 (en) | 2013-07-26 | 2015-08-18 | SkyBell Technologies, Inc. | Doorbell communication systems and methods |
US9165444B2 (en) | 2013-07-26 | 2015-10-20 | SkyBell Technologies, Inc. | Light socket cameras |
US9053622B2 (en) | 2013-07-26 | 2015-06-09 | Joseph Frank Scalisi | Light socket cameras |
US9196133B2 (en) | 2013-07-26 | 2015-11-24 | SkyBell Technologies, Inc. | Doorbell communication systems and methods |
US9769435B2 (en) | 2014-08-11 | 2017-09-19 | SkyBell Technologies, Inc. | Monitoring systems and methods |
US9197867B1 (en) | 2013-12-06 | 2015-11-24 | SkyBell Technologies, Inc. | Identity verification using a social network |
US8872915B1 (en) | 2013-07-26 | 2014-10-28 | SkyBell Technologies, Inc. | Doorbell communication systems and methods |
US9253455B1 (en) | 2014-06-25 | 2016-02-02 | SkyBell Technologies, Inc. | Doorbell communication systems and methods |
US9743049B2 (en) | 2013-12-06 | 2017-08-22 | SkyBell Technologies, Inc. | Doorbell communication systems and methods |
US9799183B2 (en) | 2013-12-06 | 2017-10-24 | SkyBell Technologies, Inc. | Doorbell package detection systems and methods |
US9786133B2 (en) | 2013-12-06 | 2017-10-10 | SkyBell Technologies, Inc. | Doorbell chime systems and methods |
US20150163463A1 (en) | 2013-12-06 | 2015-06-11 | Vivint, Inc. | Systems and methods for operating a doorbell camera |
US9819902B2 (en) * | 2015-03-19 | 2017-11-14 | Microsoft Technology Licensing, Llc | Proximate resource pooling in video/audio telecommunications |
-
2018
- 2018-07-05 US US16/028,252 patent/US10511810B2/en active Active
-
2019
- 2019-12-16 US US16/716,383 patent/US20200120309A1/en not_active Abandoned
Patent Citations (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20110211069A1 (en) * | 2010-02-26 | 2011-09-01 | Bryan Sybesma | Virtual internet protocol modulator |
US20130201847A1 (en) * | 2010-04-26 | 2013-08-08 | Interdigital Patent Holdings, Inc. | Method and apparatus to enable ad hoc networks |
US20120257061A1 (en) * | 2011-04-05 | 2012-10-11 | Honeywell International Inc. | Neighborhood Camera Linking System |
US20140187190A1 (en) * | 2012-12-31 | 2014-07-03 | Motorola Solutions, Inc. | Method and apparatus for receiving a data stream during an incident |
US20150139213A1 (en) * | 2013-11-18 | 2015-05-21 | Qualcomm Incorporated | Wireless discovery location and ranging |
US20170124834A1 (en) * | 2014-06-06 | 2017-05-04 | Maher Pedersoli | Systems and methods for secure collection of surveillance data |
US20160094810A1 (en) * | 2014-09-30 | 2016-03-31 | Verizon Patent And Licensing Inc. | System and method for providing neighborhood services through networked cameras |
US20170187995A1 (en) * | 2015-09-22 | 2017-06-29 | SkyBell Technologies, Inc. | Doorbell communication systems and methods |
US20170094523A1 (en) * | 2015-09-25 | 2017-03-30 | Mutualink, Inc. | Enabling Emergency Access to Secure Wireless Communications Networks |
US20170264604A1 (en) * | 2016-03-08 | 2017-09-14 | Dean Drako | Apparatus for sharing private video streams with first responders and method of operation |
US20170374560A1 (en) * | 2016-06-15 | 2017-12-28 | Luma Home, Inc. | System and method for network access point installation and access control |
US20180091962A1 (en) * | 2016-09-23 | 2018-03-29 | Apple Inc. | Context-dependent allocation of shared resources in a wireless communication interface |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11653076B2 (en) * | 2020-06-03 | 2023-05-16 | Hubbell Incorporated | Internet protocol (IP)-speaker with IP-camera |
WO2022000378A1 (en) * | 2020-07-01 | 2022-01-06 | 深圳市大疆创新科技有限公司 | Radar apparatus and mobile device |
Also Published As
Publication number | Publication date |
---|---|
US20190014291A1 (en) | 2019-01-10 |
US10511810B2 (en) | 2019-12-17 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10885396B2 (en) | Generating composite images using audio/video recording and communication devices | |
US10769914B2 (en) | Informative image data generation using audio/video recording and communication devices | |
US10511810B2 (en) | Accessing cameras of audio/video recording and communication devices based on location | |
US11158067B1 (en) | Neighborhood alert mode for triggering multi-device recording, multi-camera locating, and multi-camera event stitching for audio/video recording and communication devices | |
US11062577B2 (en) | Parcel theft deterrence for A/V recording and communication devices | |
US10475311B2 (en) | Dynamic assessment using an audio/video recording and communication device | |
US20180233010A1 (en) | Neighborhood alert mode for triggering multi-device recording, multi-camera motion tracking, and multi-camera event stitching for audio/video recording and communication devices | |
US20200320837A1 (en) | Parcel theft deterrence for audio/video recording and communication devices | |
US11024138B2 (en) | Adjustable alert tones and operational modes for audio/video recording and communication devices based upon user location | |
US20180247504A1 (en) | Identification of suspicious persons using audio/video recording and communication devices | |
US10839204B2 (en) | Sharing identification data with audio/video recording and communication devices and local processing of the shared data | |
US11064167B2 (en) | Input functionality for audio/video recording and communication doorbells | |
US11069210B2 (en) | Selecting a video frame for notification using audio/video recording and communication devices | |
US10930126B1 (en) | Motion sensing for electronic devices | |
US11349707B1 (en) | Implementing security system devices as network nodes | |
US11393108B1 (en) | Neighborhood alert mode for triggering multi-device recording, multi-camera locating, and multi-camera event stitching for audio/video recording and communication devices | |
US11350060B1 (en) | Using motion sensors for direction detection | |
US11627289B1 (en) | Activating security system alarms based on data generated by audio/video recording and communication devices | |
US10735696B1 (en) | Backup doorbell communication system and method |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: AMAZON TECHNOLOGIES, INC., WASHINGTON Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:SIMINOFF, JAMES;REEL/FRAME:051321/0481 Effective date: 20191025 |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |