Audio/Video Recording and Communication Devices with Multiple Cameras Having Variable Capture Settings

TECHNICAL FIELD

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.

BACKGROUND

Home security 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. AudioNideo (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 device 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 A/V recording and communication devices on the exterior of a home, such as a doorbell unit at the entrance to the home, acts as a powerful deterrent against would-be burglars.

SUMMARY

The various embodiments of the present audio/video (A/V) recording and communication devices with multiple cameras 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 audio/video (A/V) recording and communication devices could be enhanced by adding at least a second camera. For example, two cameras working in tandem could enable functionalities that might not be possible with only one camera. In some of the present embodiments, a first camera of an A/V recording and communication device may be configured with a first set of capture settings and a second camera of the A/V recording and communication device may be configured with a second set of capture settings, wherein the two cameras are configured to capture image data that are complementary to each other. In various embodiments, the first and second image data may be used to generate composite image data with enhanced quality and/or functionalities. For example, the first camera may be configured to capture first image data that is focused on a foreground of a field of view of the A/V recording and communication device whereas the second camera may be configured to capture second image data that is focused on a background of the field of view. In such embodiments, the composite image data may allow a user to optically zoom in on an object of interest whether the object is located near the foreground or background of a scene. In addition, the first image data captured by the first camera may be used to determine at least one setting of the second set of capture settings for the second camera. For example, in some embodiments, the first image data captured by the first camera may be analyzed for exposure conditions in the scene and used to determine an exposure setting for the second set of capture settings such that the second camera may be configured to capture second image data that is already adjusted for the correct exposure levels upon powering up. Variable capture settings for multiple cameras thus enable A/V recording and communication devices to capture image data with specific characteristics and/or image data suitable for generating composite image data. These and other aspects and advantages of the present embodiments are described in further detail below.

In a first aspect, an audio/video (A/V) recording and communication device is provided, the device comprising a first camera, having a first field of view, configured to capture image data using a first set of capture settings; a second camera, having a second field of view, configured to capture image data using a second set of capture settings; a communication module; and a processing module operatively connected to the first camera, the second camera, and the communication module, the processing module comprising: a processor; and a camera application, wherein the camera application configures the processor to: capture first image data using the first camera configured with the first set of capture settings; capture second image data using the second camera configured with the second set of capture settings; and generate composite image data using the first image data captured using the first camera and the second image data captured using the second camera.

In an embodiment of the first aspect, the first set of capture settings includes a first resolution setting that configures the first camera to capture the first image data having a first resolution.

In another embodiment of the first aspect, the second set of capture settings includes a second resolution setting that configures the second camera to capture the second image data having a second resolution.

In another embodiment of the first aspect, the first resolution is higher than the second resolution.

In another embodiment of the first aspect, the camera application further configures the processor to determine at least one capture setting of the second set of capture settings using the first image data captured using the first camera configured with the first set of capture settings.

In another embodiment of the first aspect, the camera application further configures the processor to measure exposure using the first image data captured using the first camera configured with the first set of capture settings and determine an exposure capture setting for the second set of capture settings.

In another embodiment of the first aspect, the first set of capture settings includes a first focal length capture setting and the second set of capture settings includes a second focal length capture setting.

In another embodiment of the first aspect, the first focal length setting configures the first camera to capture the first image data that is focused on a foreground.

In another embodiment of the first aspect, the second focal length setting configures the second camera to capture the second image data that is focused on a background.

In another embodiment of the first aspect, the first and second focal length capture settings configure the first and second cameras, respectively, to capture the first and second image data, respectively, that allows for optical zooming on an object of interest.

In another embodiment of the first aspect, the first set of capture settings includes a first luminosity setting that configures the first camera to capture the first image data having luminosity data.

In another embodiment of the first aspect, the first set of capture settings includes a first red-blue-green (RBG) setting that configures the first camera to capture the first image data having red, blue, and green channel data.

In another embodiment of the first aspect, the first set of capture settings includes a contrast setting that configures the first camera to capture the first image data having contrast data.

In another embodiment of the first aspect, the first set of capture settings includes an exposure setting that configures the first camera to capture the first image data having exposure data.

In another embodiment of the first aspect, the first set of capture settings configures the first camera to capture the first image data configured for face recognition.

In another embodiment of the first aspect, the second set of capture settings includes a second luminosity setting that configures the second camera to capture the second image data having luminosity data.

In another embodiment of the first aspect, the second set of capture settings includes a second RBG setting that configures the second camera to capture the second image data having red, blue, and green channel data.

In another embodiment of the first aspect, the second set of capture settings includes a contrast setting that configures the second camera to capture the second image data having contrast data.

In another embodiment of the first aspect, the second set of capture settings includes an exposure setting that configures the second camera to capture the second image data having exposure data.

In another embodiment of the first aspect, the second set of capture settings configures the second camera to capture the second image data configured for face recognition.

In another embodiment of the first aspect, the camera application further configures the processor to receive at least one capture setting from a user.

In another embodiment of the first aspect, the camera application further configures the processor to generate composite image data by post-processing the first image data with the second image data.

In another embodiment of the first aspect, the camera application further configures the processor to transmit the first image data and the second image data to a server using the communication module.

In another embodiment of the first aspect, the camera application further configures the processor to transmit the composite image data to a client device using the communication module.

In another embodiment of the first aspect, the first set of capture settings includes a first exposure setting that configures the first camera to capture the first image data having a first exposure range.

In another embodiment of the first aspect, the second set of capture settings includes a second exposure setting that configures the second camera to capture the second image data having a second exposure range, wherein the second exposure range does not overlap with the first exposure range.

In another embodiment of the first aspect, the camera application further configures the processor to generate composite image data by combining the first image data having the first exposure range with the second image data having the second exposure range to generate high-dynamic-range (HDR) image data.

In a second aspect, a method for an audio/video (A/V) recording and communication device is provided, the device comprising a first camera configured to capture image data using a first set of capture settings, a second camera configured to capture image data using a second set of capture settings, a communication module, and a processing module operatively connected to the first camera, the second camera, and the communication module, the method comprising: capturing first image data captured using the first camera configured with the first set of capture settings; capturing second image data captured using the second camera configured with the second set of capture settings; and generating composite image data using the first image data captured using the first camera and the second image data captured using the second camera.

In an embodiment of the second aspect, the first set of capture settings includes a first resolution setting that configures the first camera to capture the first image data having a first resolution.

In another embodiment of the second aspect, the second set of capture settings includes a second resolution setting that configures the second camera to capture the second image data having a second resolution.

In another embodiment of the second aspect, the first resolution is higher than the second resolution.

In another embodiment of the second aspect, the camera application further configures the processor to determine at least one capture setting of the second set of capture settings using the first image data captured using the first camera configured with the first set of capture settings.

In another embodiment of the second aspect, the camera application further configures the processor to measure exposure using the first image data captured using the first camera configured with the first set of capture settings and determine an exposure capture setting for the second set of capture settings.

In another embodiment of the second aspect, the first set of capture settings includes a first focal length capture setting and the second set of capture settings includes a second focal length capture setting.

In another embodiment of the second aspect, the first focal length capture setting configures the first camera to capture the first image data that is focused on a foreground.

In another embodiment of the second aspect, the second focal length capture setting configures the second camera to capture the second image data that is focused on a background.

In another embodiment of the second aspect, the first and second focal length capture settings configure the first and second cameras, respectively, to capture the first and second image data, respectively, that allows for optical zooming on an object of interest.

In another embodiment of the second aspect, the first set of capture settings includes a first luminosity setting that configures the first camera to capture the first image data having luminosity data.

In another embodiment of the second aspect, the first set of capture settings includes a first red-blue-green (RBG) setting that configures the first camera to capture the first image data having red, blue, and green channel data.

In another embodiment of the second aspect, the first set of capture settings includes a contrast setting that configures the first camera to capture the first image data having contrast data.

In another embodiment of the second aspect, the first set of capture settings includes an exposure setting that configures the first camera to capture the first image data having exposure data.

In another embodiment of the second aspect, the first set of capture settings configures the first camera to capture the first image data configured for face recognition.

In another embodiment of the second aspect, the second set of capture settings includes a second luminosity setting that configures the second camera to capture the second image data having luminosity data.

In another embodiment of the second aspect, the second set of capture settings includes a second RBG setting that configures the second camera to capture the second image data having red, blue, and green channel data.

In another embodiment of the second aspect, the second set of capture settings includes a contrast setting that configures the second camera to capture the second image data having contrast data.

In another embodiment of the second aspect, the second set of capture settings includes an exposure setting that configures the second camera to capture the second image data having exposure data.

In another embodiment of the second aspect, the second set of capture settings configures the second camera to capture the second image data configured for face recognition.

In another embodiment of the second aspect, the camera application further configures the processor to receive at least one of the first and second capture settings from a user.

In another embodiment of the second aspect, the camera application further configures the processor to generate composite image data by post-processing the first image data with the second image data.

In another embodiment of the second aspect, the camera application further configures the processor to transmit the first image data and the second image data to a server using the communication module.

In another embodiment of the second aspect, the camera application further configures the processor to transmit the composite image data to a client device using the communication module.

In another embodiment of the second aspect, the first set of capture settings includes a first exposure setting that configures the first camera to capture the first image data having a first exposure range.

In another embodiment of the second aspect, the second set of capture settings includes a second exposure setting that configures the second camera to capture the second image data having a second exposure range, wherein the second exposure range does not overlap with the first exposure range.

In another embodiment of the second aspect, the camera application further configures the processor to generate composite image data by combining the first image data having the first exposure range with the second image data having the second exposure range to generate high-dynamic-range (HDR) image data.

In a third aspect, a server for audio/video (A/V) recording and communication devices is provided, the server comprising: a communication module; and a processing module operatively connected to the communication module and in network communication with an A/V recording and communication device comprising a first camera, having a first field of view, configured to capture image data using a first set of capture settings and a second camera, having a second field of view, configured to capture image data using a second set of capture settings, the processing module comprising: a processor; and a server application, wherein the server application configures the processor to: receive first image data captured using the first camera configured with the first set of capture settings from the A/V recording and communication device; receive second image data captured using the second camera configured with the second set of capture settings from the A/V recording and communication device; and generate composite image data using the first image data captured using the first camera and the second image data captured using the second camera.

In an embodiment of the third aspect, the first image data includes a first resolution.

In another embodiment of the third aspect, the second image data includes a second resolution.

In another embodiment of the third aspect, the first resolution is higher than the second resolution.

In another embodiment of the third aspect, the first image data is focused on a foreground.

In another embodiment of the third aspect, the second image data is focused on a background.

In another embodiment of the third aspect, the first and second image data allow for optical zooming on an object of interest.

In another embodiment of the third aspect, the first image data includes luminosity data.

In another embodiment of the third aspect, the first image data includes red, blue, and green channel data.

In another embodiment of the third aspect, the first image data includes contrast data.

In another embodiment of the third aspect, the first image data includes exposure data.

In another embodiment of the third aspect, the first image data includes image data configured for face recognition.

In another embodiment of the third aspect, the second image data includes luminosity data.

In another embodiment of the third aspect, the second image data includes red, blue, and green channel data.

In another embodiment of the third aspect, the second image data includes contrast data.

In another embodiment of the third aspect, the second image data includes exposure data.

In another embodiment of the third aspect, the second image data includes image data configured for face recognition.

In another embodiment of the third aspect, the server application further configures the processor to generate the composite image data by post-processing the first image data with the second image data.

In another embodiment of the third aspect, the server application further configures the processor to transmit the composite image data to a client device.

In another embodiment of the third aspect, the first image data includes a first exposure range.

In another embodiment of the third aspect, the second image data includes a second exposure range, wherein the second exposure range does not overlap with the first exposure range.

In another embodiment of the third aspect, the server application further configures the processor to generate the composite image data by combining the first image data having the first exposure range with the second image data having the second exposure range to generate high-dynamic-range (HDR) image data.

In a fourth aspect, a method for a server is provided, the server comprising a communication module and a processing module operatively connected to the communication module, wherein the processing module is in network communication an audio/video (A/V) recording and communication device comprising a first camera configured to capture image data using a first set of capture settings and a second camera configured to capture image data using a second set of capture settings, the method comprising: receiving first image data captured using the first camera configured with the first set of capture settings from the A/V recording and communication device; receiving second image data captured using the second camera configured with the second set of capture settings from the A/V recording and communication device; and generating composite image data using the first image data captured using the first camera and the second image data captured using the second camera.

In an embodiment of the fourth aspect, the first image data includes a first resolution.

In another embodiment of the fourth aspect, the second image data includes a second resolution.

In another embodiment of the fourth aspect, the first resolution is higher than the second resolution.

In another embodiment of the fourth aspect, the first image data is focused on a foreground.

In another embodiment of the fourth aspect, the second image data is focused on a background.

In another embodiment of the fourth aspect, the first and second image data allows for optical zooming on an object of interest.

In another embodiment of the fourth aspect, the first image data includes luminosity data.

In another embodiment of the fourth aspect, the first image data includes red, blue, and green channel data.

In another embodiment of the fourth aspect, the first image data includes contrast data.

In another embodiment of the fourth aspect, the first image data includes exposure data.

In another embodiment of the fourth aspect, the first image data includes image data configured for face recognition.

In another embodiment of the fourth aspect, the second image data includes luminosity data.

In another embodiment of the fourth aspect, the second image data includes red, blue, and green channel data.

In another embodiment of the fourth aspect, the second image data includes contrast data.

In another embodiment of the fourth aspect, the second image data includes exposure data.

In another embodiment of the fourth aspect, the second image data includes image data configured for face recognition.

Another embodiment of the fourth aspect further comprises generating the composite image data by post-processing the first image data with the second image data.

Another embodiment of the fourth aspect further comprises transmitting the composite image data to a client device.

In another embodiment of the fourth aspect, the first image data includes a first exposure range.

In another embodiment of the fourth aspect, the second image data includes a second exposure range, wherein the second exposure range does not overlap with the first exposure range.

Another embodiment of the fourth aspect further comprises generating the composite image data by combining the first image data having the first exposure range with the second image data having the second exposure range to generate high-dynamic-range (HDR) image data.

BRIEF DESCRIPTION OF THE DRAWINGS

The various embodiments of the present audio/video (A/V) recording and communication devices with multiple cameras now will be discussed in detail with an emphasis on highlighting the advantageous features. These embodiments depict the novel and non-obvious A/V recording and communication devices with multiple cameras 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 a system for streaming and storing A/V content captured by an audio/video (A/V) recording and communication device according to various aspects of the present disclosure;

FIG. 2 is a flowchart illustrating a process for streaming and storing A/V content from an A/V recording and communication device according to various aspects of the present disclosure;

FIG. 3 is a front view of an A/V recording and communication device according to various aspects of the present disclosure;

FIG. 4 is a rear view of the A/V recording and communication device of FIG. 3;

FIG. 5 is a left side view of the A/V recording and communication device of FIG. 3 attached to a mounting bracket according to various aspects of the present disclosure;

FIG. 6 is cross-sectional right side view of the A/V recording and communication device of FIG. 3;

FIG. 7 is an exploded view of the A/V recording and communication device and the mounting bracket of FIG. 5;

FIG. 8 is a rear view of the mounting bracket of FIG. 5;

FIGS. 9 and 10 are top and bottom views, respectively, of the A/V recording and communication device and the mounting bracket of FIG. 5;

FIG. 11 is a top view of a passive infrared sensor assembly according to various aspects of the present disclosure;

FIG. 12 is a front view of the passive infrared sensor assembly of FIG. 11;

FIG. 13 is a top view of the passive infrared sensor assembly of FIG. 11, illustrating the fields of view of the passive infrared sensors according to various aspects of the present disclosure;

FIG. 14 a functional block diagram of the components of the A/V recording and communication device of FIG. 3;

FIG. 15 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. 16 is a functional block diagram illustrating one embodiment of a server according to various aspects of the present disclosure;

FIG. 17 is a diagram illustrating an A/V recording and communication device having two cameras with substantially coincident fields of view according to various aspects of the present disclosure;

FIG. 18 is a flowchart illustrating an embodiment of a process for generating composite image data using two cameras according to various aspects of the present disclosure;

FIG. 19 is a flowchart illustrating an embodiment of a process for determining capture settings according to various aspects of the present disclosure;

FIG. 20 is a flowchart illustrating another embodiment of a process for determining capture settings according to various aspects of the present disclosure;

FIG. 21 is a flowchart illustrating another embodiment of a process for generating composite image data according to various aspects of the present disclosure;

FIG. 22 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. 23 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.

DETAILED DESCRIPTION

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 audio/video (A/V) recording and communication devices with multiple cameras having variable capture settings are described below with reference to the figures. These figures, and their written descriptions, indicate that certain components of the apparatus are formed integrally, and certain other components are formed as separate pieces. Those of ordinary skill in the art will appreciate that components shown and described herein as being formed integrally may in alternative embodiments be formed as separate pieces. Those of ordinary skill in the art will further appreciate that components shown and described herein as being formed as separate pieces may in alternative embodiments be formed integrally. Further, as used herein the term integral describes a single unitary piece.

With reference to FIG. 1, the present embodiments include an audio/video (A/V) device 100. While the present disclosure provides numerous examples of methods and systems including A/V recording and communication doorbells, 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/or functionality of the doorbells described herein, but without the front button and related components.

The A/V recording and communication device 100 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 better. While not shown, the A/V recording and communication device 100 may also include other hardware and/or components, such as a housing, a communication module (which may facilitate wired and/or wireless communication with other devices), 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 US 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 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). As described below, the A/V recording and communication device 100 may communicate with the 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 and/or computing 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. For example, 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.34 bis 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, 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 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 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 pressed a front button of the A/V recording and communication device 100 (if the A/V recording and communication device 100 is 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'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 (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 the remote 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 the A/V recording and communication device 100 according to various aspects of the present disclosure. At block B200, the A/V recording and communication device 100 detects the visitor's presence and captures 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. As described above, 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 pressed a front button of the A/V recording and communication device 100 (if the A/V recording and communication device 100 is a doorbell). Also as described above, the video recording/capture may begin when the visitor is detected, or may begin earlier, as described below.

At block B202, 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. For example, 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. In another example, the network device to which the request is sent may be an API such as the backend API 120, which is described above.

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's network 110 and the network 112. At block B206, 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 device/sensor available. At block B208, 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. 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 the camera 102, the microphone 104, and/or other devices/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 and communication 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.

FIGS. 3-5 illustrate a wireless audio/video (A/V) communication doorbell 130 according to an aspect of present embodiments. FIG. 3 is a front view, FIG. 4 is a rear view, and FIG. 5 is a left side view of the doorbell 130 coupled with a mounting bracket 137. The doorbell 130 includes a faceplate 135 mounted to a back plate 139 (FIG. 4). With reference to FIG. 5, the faceplate 135 has a substantially flat profile. The faceplate 135 may comprise any suitable material, including, without limitation, metals, such as brushed aluminum or stainless steel, metal alloys, or plastics. The faceplate 135 protects the internal contents of the doorbell 130 and serves as an exterior front surface of the doorbell 130.

With reference to FIG. 3, the faceplate 135 includes a button 133 and a light pipe 136. The button 133 and the light pipe 136 may have various profiles that may or may not match the profile of the faceplate 135. The light pipe 136 may comprise any suitable material, including, without limitation, transparent plastic, that is capable of allowing light produced within the doorbell 130 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 130, as further described below. The button 133 may make contact with a button actuator (not shown) located within the doorbell 130 when the button 133 is pressed by a visitor. When pressed, the button 133 may trigger one or more functions of the doorbell 130, as further described below.

With reference to FIGS. 3 and 5, the doorbell 130 further includes an enclosure 131 that engages the faceplate 135. In the illustrated embodiment, the enclosure 131 abuts an upper edge 135T (FIG. 3) of the faceplate 135, but in alternative embodiments one or more gaps between the enclosure 131 and the faceplate 135 may facilitate the passage of sound and/or light through the doorbell 130. The enclosure 131 may comprise any suitable material, but in some embodiments the material of the enclosure 131 preferably permits infrared light to pass through from inside the doorbell 130 to the environment and vice versa. The doorbell 130 further includes a lens 132. 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 the doorbell 130. The doorbell 130 further includes a camera 134, which captures video data when activated, as described below.

FIG. 4 is a rear view of the doorbell 130, according to an aspect of the present embodiments. As illustrated, the enclosure 131 may extend from the front of the doorbell 130 around to the back thereof and may fit snugly around a lip of the back plate 139. The back plate 139 may comprise any suitable material, including, without limitation, metals, such as brushed aluminum or stainless steel, metal alloys, or plastics. The back plate 139 protects the internal contents of the doorbell 130 and serves as an exterior rear surface of the doorbell 130. The faceplate 135 may extend from the front of the doorbell 130 and at least partially wrap around the back plate 139, thereby allowing a coupled connection between the faceplate 135 and the back plate 139. The back plate 139 may have indentations in its structure to facilitate the coupling.

With further reference to FIG. 4, spring contacts 140 may provide power to the doorbell 130 when mated with other conductive contacts connected to a power source. The spring contacts 140 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 130 further comprises a connector 160, such as a micro-USB or other connector, whereby power and/or data may be supplied to and from the components within the doorbell 130. A reset button 159 may be located on the back plate 139, and may make contact with a button actuator (not shown) located within the doorbell 130 when the reset button 159 is pressed. When the reset button 159 is pressed, it may trigger one or more functions, as described below.

FIG. 5 is a left side profile view of the doorbell 130 coupled to the mounting bracket 137, according to an aspect of the present embodiments. The mounting bracket 137 facilitates mounting the doorbell 130 to a surface, such as the exterior of a building, such as a home or office. As illustrated in FIG. 5, the faceplate 135 may extend from the bottom of the doorbell 130 up to just below the camera 134, and connect to the back plate 139 as described above. The lens 132 may extend and curl partially around the side of the doorbell 130. The enclosure 131 may extend and curl around the side and top of the doorbell 130, and may be coupled to the back plate 139 as described above. The camera 134 may protrude slightly through the enclosure 131, thereby giving it a wider field of view. The mounting bracket 137 may couple with the back plate 139 such that they contact each other at various points in a common plane of contact, thereby creating an assembly including the doorbell 130 and the mounting bracket 137. 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. 6 is a right side cross-sectional view of the doorbell 130 without the mounting bracket 137. In the illustrated embodiment, the lens 132 is substantially coplanar with the front surface 131F of the enclosure 131. In alternative embodiments, the lens 132 may be recessed within the enclosure 131 or may protrude outward from the enclosure 131. The camera 134 is coupled to a camera printed circuit board (PCB) 147, and a lens 134a of the camera 134 protrudes through an opening in the enclosure 131. The camera lens 134a may be a lens capable of focusing light into the camera 134 so that clear images may be taken.

The camera PCB 147 may be secured within the doorbell with any suitable fasteners, such as screws, or interference connections, adhesives, etc. The camera PCB 147 comprises various components that enable the functionality of the camera 134 of the doorbell 130, as described below. Infrared light-emitting components, such as infrared LED's 168, are coupled to the camera PCB 147 and may be triggered to activate when a light sensor detects a low level of ambient light. When activated, the infrared LED's 168 may emit infrared light through the enclosure 131 and/or the camera 134 out into the ambient environment. The camera 134, which may be configured to detect infrared light, may then capture the light emitted by the infrared LED's 168 as it reflects off objects within the camera's 134 field of view, so that the doorbell 130 can clearly capture images at night (may be referred to as “night vision”).

With continued reference to FIG. 6, the doorbell 130 further comprises a front PCB 146, which in the illustrated embodiment resides in a lower portion of the doorbell 130 adjacent a battery 166. The front PCB 146 may be secured within the doorbell 130 with any suitable fasteners, such as screws, or interference connections, adhesives, etc. The front PCB 146 comprises various components that enable the functionality of the audio and light components, as further described below. The battery 166 may provide power to the doorbell 130 components while receiving power from the spring contacts 140, thereby engaging in a trickle-charge method of power consumption and supply. Alternatively, the doorbell 130 may draw power directly from the spring contacts 140 while relying on the battery 166 only when the spring contacts 140 are not providing the power necessary for all functions. Still further, the battery 166 may comprise the sole source of power for the doorbell 130. In such embodiments, the spring contacts 140 may not be connected to a source of power. When the battery 166 is depleted of its charge, it may be recharged, such as by connecting a power source to the connector 160.

With continued reference to FIG. 6, the doorbell 130 further comprises a power PCB 148, which in the illustrated embodiment resides behind the camera PCB 147. The power PCB 148 may be secured within the doorbell 130 with any suitable fasteners, such as screws, or interference connections, adhesives, etc. The power PCB 148 comprises various components that enable the functionality of the power and device-control components, as further described below.

With continued reference to FIG. 6, the doorbell 130 further comprises a communication module 164 coupled to the power PCB 148. The communication module 164 facilitates communication with client devices in one or more remote locations, as further described below. The connector 160 may protrude outward from the power PCB 148 and extend through a hole in the back plate 139. The doorbell 130 further comprises passive infrared (PIR) sensors 144, which are secured on or within a PIR sensor holder 143, and the assembly resides behind the lens 132. In some embodiments, the doorbell 130 may comprise three PIR sensors 144, as further described below, but in other embodiments any number of PIR sensors 144 may be provided. The PIR sensor holder 143 may be secured to the doorbell 130 with any suitable fasteners, such as screws, or interference connections, adhesives, etc. The PIR sensors 144 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 the PIR sensors 144. 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. 7 is an exploded view of the doorbell 130 and the mounting bracket 137 according to an aspect of the present embodiments. The mounting bracket 137 is configured to be mounted to a mounting surface (not shown) of a structure, such as a home or an office. FIG. 7 shows the front side 137F of the mounting bracket 137. The mounting bracket 137 is configured to be mounted to the mounting surface such that the back side 137B thereof faces the mounting surface. In certain embodiments the mounting bracket 137 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 130 may be coupled to the mounting bracket 137 with any suitable fasteners, such as screws, or interference connections, adhesives, etc.

With continued reference to FIG. 7, the illustrated embodiment of the mounting bracket 137 includes the terminal screws 138. The terminal screws 138 are configured to receive electrical wires adjacent the mounting surface of the structure upon which the mounting bracket 137 is mounted, so that the doorbell 130 may receive electrical power from the structure's electrical system. The terminal screws 138 are electrically connected to electrical contacts 177 of the mounting bracket. If power is supplied to the terminal screws 138, then the electrical contacts 177 also receive power through the terminal screws 138. The electrical contacts 177 may comprise any suitable conductive material, including, without limitation, copper, and may protrude slightly from the face of the mounting bracket 137 so that they may mate with the spring contacts 140 located on the back plate 139.

With reference to FIGS. 7 and 8 (which is a rear view of the mounting bracket 137), the mounting bracket 137 further comprises a bracket PCB 149. With reference to FIG. 8, the bracket PCB 149 is situated outside the doorbell 130, and is therefore configured for various sensors that measure ambient conditions, such as an accelerometer 150, a barometer 151, a humidity sensor 152, and a temperature sensor 153. The functions of these components are discussed in more detail below. The bracket PCB 149 may be secured to the mounting bracket 137 with any suitable fasteners, such as screws, or interference connections, adhesives, etc.

FIGS. 9 and 10 are top and bottom views, respectively, of the doorbell 130. As described above, the enclosure 131 may extend from the front face 131F of the doorbell 130 to the back, where it contacts and snugly surrounds the back plate 139. The camera 134 may protrude slightly beyond the front face 131F of the enclosure 131, thereby giving the camera 134 a wider field of view. The mounting bracket 137 may include a substantially flat rear surface 137R, such that the doorbell 130 and the mounting bracket 137 assembly may sit flush against the surface to which they are mounted. With reference to FIG. 10, the lower end of the enclosure 131 may include security screw apertures 141 configured to receive screws or other fasteners.

FIG. 11 is a top view and FIG. 12 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 178C and two side faces 178S to either side of the center face 178C. With reference to FIG. 12, each of the faces 178 defines an opening 181 within or on which the passive infrared sensors 144 may be mounted. In alternative embodiments, 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. Generally, the faces 178 may be any physical structure capable of housing and/or securing the passive infrared sensors 144 in place.

With reference to FIG. 11, 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. 13 is a top view of the passive infrared sensor assembly 179 illustrating the fields of view of the passive infrared 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 passive infrared 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, 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. 14 is a functional block diagram of the components within or in communication with the doorbell 130, according to an aspect of the present embodiments. As described above, the bracket PCB 149 may comprise an accelerometer 150, a barometer 151, a humidity sensor 152, and a temperature sensor 153. The accelerometer 150 may be one or more sensors capable of sensing motion and/or acceleration. The barometer 151 may be one or more sensors capable of determining the atmospheric pressure of the surrounding environment in which the bracket PCB 149 may be located. The humidity sensor 152 may be one or more sensors capable of determining the amount of moisture present in the atmospheric environment in which the bracket PCB 149 may be located. The temperature sensor 153 may be one or more sensors capable of determining the temperature of the ambient environment in which the bracket PCB 149 may be located. As described above, the bracket PCB 149 may be located outside the housing of the doorbell 130 so as to reduce interference from heat, pressure, moisture, and/or other stimuli generated by the internal components of the doorbell 130.

With further reference to FIG. 14, the bracket PCB 149 may further comprise terminal screw inserts 154, which may be configured to receive the terminal screws 138 and transmit power to the electrical contacts 177 on the mounting bracket 137 (FIG. 7). The bracket PCB 149 may be electrically and/or mechanically coupled to the power PCB 148 through the terminal screws 138, the terminal screw inserts 154, the spring contacts 140, and the electrical contacts 177. The terminal screws 138 may receive electrical wires located at the surface to which the doorbell 130 is mounted, such as the wall of a building, so that the doorbell can receive electrical power from the building's electrical system. Upon the terminal screws 138 being secured within the terminal screw inserts 154, power may be transferred to the bracket PCB 149, and to all of the components associated therewith, including the electrical contacts 177. The electrical contacts 177 may transfer electrical power to the power PCB 148 by mating with the spring contacts 140.

With further reference to FIG. 14, the front PCB 146 may comprise a light sensor 155, one or more light-emitting components, such as LED's 156, one or more speakers 157, and a microphone 158. The light sensor 155 may be one or more sensors capable of detecting the level of ambient light of the surrounding environment in which the doorbell 130 may be located. LED's 156 may be one or more light-emitting diodes capable of producing visible light when supplied with power. The speakers 157 may be any electromechanical device capable of producing sound in response to an electrical signal input. The microphone 158 may be an acoustic-to-electric transducer or sensor capable of converting sound waves into an electrical signal. When activated, the LED's 156 may illuminate the light pipe 136 (FIG. 3). The front PCB 146 and all components thereof may be electrically coupled to the power PCB 148, thereby allowing data and/or power to be transferred to and from the power PCB 148 and the front PCB 146.

The speakers 157 and the microphone 158 may be coupled to the camera processor 170 through an audio CODEC 161. For example, the transfer of digital audio from the user's client device 114 and the speakers 157 and the microphone 158 may be compressed and decompressed using the audio CODEC 161, coupled to the camera processor 170. Once compressed by audio CODEC 161, digital audio data may be sent through the communication module 164 to the network 112, routed by one or more servers 118, and delivered to the user's client device 114. When the user speaks, after being transferred through the network 112, digital audio data is decompressed by audio CODEC 161 and emitted to the visitor via the speakers 157.

With further reference to FIG. 14, the power PCB 148 may comprise a power management module 162, a microcontroller 163 (may also be referred to as “processor,” “CPU,” or “controller”), the communication module 164, and power PCB non-volatile memory 165. In certain embodiments, the power management module 162 may comprise an integrated circuit capable of arbitrating between multiple voltage rails, thereby selecting the source of power for the doorbell 130. The battery 166, the spring contacts 140, and/or the connector 160 may each provide power to the power management module 162. The power management module 162 may have separate power rails dedicated to the battery 166, the spring contacts 140, and the connector 160. In one aspect of the present disclosure, the power management module 162 may continuously draw power from the battery 166 to power the doorbell 130, while at the same time routing power from the spring contacts 140 and/or the connector 160 to the battery 166, thereby allowing the battery 166 to maintain a substantially constant level of charge. Alternatively, the power management module 162 may continuously draw power from the spring contacts 140 and/or the connector 160 to power the doorbell 130, while only drawing from the battery 166 when the power from the spring contacts 140 and/or the connector 160 is low or insufficient. Still further, the battery 166 may comprise the sole source of power for the doorbell 130. In such embodiments, the spring contacts 140 may not be connected to a source of power. When the battery 166 is depleted of its charge, it may be recharged, such as by connecting a power source to the connector 160. The power management module 162 may also serve as a conduit for data between the connector 160 and the microcontroller 163.

With further reference to FIG. 14, in certain embodiments the microcontroller 163 may comprise an integrated circuit including a processor core, memory, and programmable input/output peripherals. The microcontroller 163 may receive input signals, such as data and/or power, from the PIR sensors 144, the bracket PCB 149, the power management module 162, the light sensor 155, the microphone 158, and/or the communication module 164, and may perform various functions as further described below. When the microcontroller 163 is triggered by the PIR sensors 144, the microcontroller 163 may be triggered to perform one or more functions. When the light sensor 155 detects a low level of ambient light, the light sensor 155 may trigger the microcontroller 163 to enable “night vision,” as further described below. The microcontroller 163 may also act as a conduit for data communicated between various components and the communication module 164.

With further reference to FIG. 14, the communication module 164 may comprise an integrated circuit including a processor core, memory, and programmable input/output peripherals. The communication module 164 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 164 may receive inputs, such as power and/or data, from the camera PCB 147, the microcontroller 163, the button 133, the reset button 159, and/or the power PCB non-volatile memory 165. When the button 133 is pressed, the communication module 164 may be triggered to perform one or more functions. When the reset button 159 is pressed, the communication module 164 may be triggered to erase any data stored at the power PCB non-volatile memory 165 and/or at the camera PCB memory 169. The communication module 164 may also act as a conduit for data communicated between various components and the microcontroller 163. The power PCB non-volatile memory 165 may comprise flash memory configured to store and/or transmit data. For example, in certain embodiments the power PCB non-volatile memory 165 may comprise serial peripheral interface (SPI) flash memory.

With further reference to FIG. 14, the camera PCB 147 may comprise components that facilitate the operation of the camera 134. For example, an imager 171 may comprise a video recording sensor and/or a camera chip. In one aspect of the present disclosure, the imager 171 may comprise a complementary metal-oxide semiconductor (CMOS) array, and may be capable of recording high definition (e.g., 720p or better) video files. A camera processor 170 may comprise an encoding and compression chip. In some embodiments, the camera processor 170 may comprise a bridge processor. The camera processor 170 may process video recorded by the imager 171 and audio recorded by the microphone 158, and may transform this data into a form suitable for wireless transfer by the communication module 164 to a network. The camera PCB memory 169 may comprise volatile memory that may be used when data is being buffered or encoded by the camera processor 170. For example, in certain embodiments the camera PCB memory 169 may comprise synchronous dynamic random access memory (SD RAM). IR LED's 168 may comprise light-emitting diodes capable of radiating infrared light. IR cut filter 167 may comprise a system that, when triggered, configures the imager 171 to see primarily infrared light as opposed to visible light. When the light sensor 155 detects a low level of ambient light (which may comprise a level that impedes the performance of the imager 171 in the visible spectrum), the IR LED's 168 may shine infrared light through the doorbell 130 enclosure out to the environment, and the IR cut filter 167 may enable the imager 171 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 130 with the “night vision” function mentioned above.

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 the front button 133, the button actuator, and/or the light pipe 136. An example A/V recording and communication security camera may further omit other components, such as, for example, the bracket PCB 149 and its components.

FIG. 15 is a functional block diagram illustrating one embodiment of an A/V recording and communication device 300 according to various aspects of the present disclosure. In some embodiments, the A/V recording and communication device 300 may be used with the system illustrated in FIG. 1. For example, the A/V recording and communication device 300 may take the place of the A/V recording and communication device 100, or may be used in conjunction with the A/V recording and communication device 100.

With reference to FIG. 15, the A/V recording and communication device 300 may comprise a processing module 312 that is operatively connected to a first camera 302, a second camera 304, a microphone 306, a speaker 308, and a communication module 310. The processing module 312 may comprise a processor 314, volatile memory 316, and non-volatile memory 318 that includes a camera application 320. The non-volatile memory 318 may also include a first set of capture settings 322 and a second set of capture settings 324 that may be used to configure the first camera 302 and the second camera 304, respectively. In addition, the non-volatile memory 318 may include first image data 326, second image data 328, and composite image data 330. In various embodiments, the camera application 320 may configure the processor 314 to capture the first image data 326 using the first camera 302 configured with the first set of capture settings 322, as further described below. The camera application 320 may also configure the processor 314 to capture the second image data 328 using the second camera 304 configured with the second set of capture settings 324, as further described below. For example, the first and second sets of capture settings 322, 324 may include various settings such as (but not limited to) resolution, exposure, aperture, focus, sensor gain, filters, luminosity, red-blue-green (RBG) channel, contrast, and face recognition settings, as further described below. In various embodiments, the camera application 320 may also configure the processor 314 to perform one or more processes for determining the first and second sets of capture settings 322, 324 and generating composite image data 330 using the first image data 326 and the second image data 328, as further described below. Further, the camera application 320 may configure the processor 314 to transmit the composite image data 330 to a client device 114 (FIG. 1). In alternative embodiments, the camera application 320 may configure the processor 314 to transmit the first and second image data 326, 328 to a server 340 (FIG. 16), as further described below.

In further reference to FIG. 15, the communication module 310 may comprise (but is not limited to) one or more transceivers and/or wireless antennas (not shown) configured to transmit and receive wireless signals. In further embodiments, the communication module 310 may comprise (but is not limited to) one or more transceivers configured to transmit and receive wired and/or wireless signals. In addition, the A/V recording and communication device 300 may be similar in structure and/or function to the A/V recording and communication device 130 (FIGS. 3-14), with the added feature of a second camera. For example, the A/V recording and communication device 300 may include a first camera similar (or identical) in structure and/or function to the camera 154 of the A/V recording and communication device 130, and a second camera. In certain embodiments, the second camera may also be similar (or identical) in structure and/or function to the camera 154 of the A/V recording and communication device 130.

FIG. 16 is a functional block diagram illustrating one embodiment of a server 340 according to various aspects of the present disclosure. In some embodiments, the server 340 may be used with the system illustrated in FIG. 1. For example, the server 340 may take the place of the server 118, or may be used in conjunction with the server 118. The server 340 may also be used in conjunction with the A/V recording and communication device 300 with the system illustrated in FIG. 1. In some embodiments, the server 340 may be in network communication with the A/V recording and communication device 300, where the server 340 may be configured to receive the first image data 326 captured using the first camera 302 configured with the first set of capture settings 322 and/or the second image data 328 captured using the second camera 304 configured with the second set of capture settings 324. In addition, the server 340 may be configured to perform one or more processes for generating composite image data 354, as further described below.

With reference to FIG. 16, the server 340 may comprise a processing module 342 comprising a processor 344, volatile memory 346, a communication module 352, and non-volatile memory 348. The communication module 352 may allow the server 340 to access and communicate with devices connected to the network (Internet/PSTN) 112 (FIG. 1). The non-volatile memory 348 may include a server application 350 that configures the processor 344 to perform processes for generating composite image data 354 using the first image data 326 captured using the first camera 302 and the second image data 328 captured using the second camera 304, as further described below. In various embodiments, the server 340 may receive the first image data 326 and the second image data 328 from the A/V recording and communication device 300 using the communication module 352. Further, the server 340 may save (also referred to as “store”) the first image data 326 and the second image data 328 in the non-volatile memory 348. In alternative embodiments, the first image data 326 and the second image data 328 may be stored in the volatile memory 346, or in a combination of the volatile memory 346 and the non-volatile memory 348.

With further reference to FIGS. 15-16, the image data 326, 328, 330, and 354 may comprise image sensor data such as (but not limited to) exposure values and data regarding pixel values for a particular sized frame. For example, a 1920×1080 frame has 1920 rows and 1080 columns with a pixel located at each intersection of a row and a column. Further, each pixel may have numerical values that correspond to color or chroma component (such as Cb, Cr) and a luma or brightness component (Y). Although different methods of pixel valuations exist, YCbCr is a widely used color space coding scheme. Further, image data 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, image data may also comprise data related to video, where such data may include (but is not limited to) image sequences, frame rates, and the like. Moreover, image data may include data that is analog, digital, uncompressed, compressed, and/or in vector formats. Image data 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.

FIG. 17 is a diagram illustrating an A/V recording and communication device 300 having first and second cameras 302, 304 with substantially coincident fields of view 360, 362 according to various aspects of the present disclosure. In some embodiments, the first camera 302 may comprise a first field of view 360 and the second camera 304 may comprise a second field of view 362. The first and second fields of view 360, 362 may be substantially coincident, or may at least have substantial overlap. For example, the first field of view 360 may capture first image data 326 of a first person 364 and a second person 366. Likewise, the second field of view 362 may capture second image data 328 of the same first person 364 and second person 366. However, the first and second sets of capture settings 322, 324 may configure the first and second cameras 302, 304, respectively, to capture image data that differs from one another in one or more ways. In various embodiments, the first and second sets of capture settings 322, 324 may include various settings such as (but not limited to) resolution, exposure, aperture, focus, sensor gain, filters, luminosity, red-blue-green (RBG) channel, contrast, and face recognition settings, as further described below. For example, the first set of capture settings 322 may include a first focal length capture setting that configures the first camera 302 to capture first image data 326 that is focused on a foreground such as the first person 364. The second set of capture settings 324 may include a second focal length capture setting that configures the second camera 304 to capture second image data 328 that is focused on a background such as the second person 366. In this manner, the A/V recording and communication device 300 may generate composite image data 330 using the first image data 326 and the second image data 328 that allows the A/V recording and communication device 300 to generate high quality image data whether the area of interest is in the foreground or in the background. Thus, the overlapping (or substantially coincident) fields of view 360, 362 may in some embodiments enable the first and second cameras 302, 304 configured with the first and second sets of capture settings 322, 324, respectively, to work in tandem to achieve various advantages, as further described below. Further, in some embodiments, the first and second cameras 302, 304 may be spaced from one another by a distance D, which may result in the fields of view 360, 362 being not completely coincident, and which may also create one or more advantages, as further described below.

FIG. 18 is a flowchart illustrating an embodiment of a process 400 for generating composite image data 330 using a first camera 302 and a second camera 304 according to various aspects of the present disclosure. The process 400 may include configuring (block B402) the first camera 302 using a first set of capture settings 322 and configuring (block B404) the second camera 304 using a second set of capture settings 324. The process 400 may also include capturing (block B406) first image data 326 using the first camera 302 configured using the first set of capture settings 322. The process may also include capturing (block B408) second image data 328 using the second camera 304 configured using the second set of capture settings 324. The first and second sets of capture settings 322, 324 may include a variety of capture settings and may be determined using various processes, as further described below. The process 400 may also include generating (block B410) composite image data 330 using the first image data 326 and the second image data 328. In some embodiments, the composite image data 330 may be generated (block B410) by post-processing the first image data 326 with the second image data 328. In various embodiments, generating (block B410) composite image data 330 may be performed using a variety of processes known to one of ordinary skill in the art including (but not limited to) physical compositing, projection, matting, cropping, and various corrections in color depth, contrast, and exposure. In many embodiments, the first set of capture settings 322 and the second set of capture settings 324 may complement each other for generating composite image data 330 and enhancing the functionalities of the A/V recording and communication device 300, as further described below. In addition, the process 400 may include transmitting (block B412) the composite image data 330 to a client device (such as the client device 114 in FIG. 1) and/or to a server (such as the server 118 in FIG. 1) using the communication module 310. In other embodiments, the A/V recording and communication device 300 may transmit the first and second image data 326, 328 to the server 340 using the communication module 310, where the server 340 may generate the composite image data 354, as further described below.

In reference to FIG. 18, in some embodiments, the first set of capture settings 322 may include a first resolution setting that configures (block B402) the first camera 302 to capture (block B406) the first image data 326 having a first resolution. Similarly, the second set of capture settings 324 may include a second resolution setting that configures (block B404) the second camera 304 to capture (block B408) the second image data 328 having a second resolution. The first and second resolutions may be different, where the first resolution may be higher than the second resolution, or vice versa. The different resolution settings of the first and second cameras 302, 304 may result in the lower resolution camera also consuming less power than the higher resolution camera, thereby allowing for various power-saving configurations of the A/V recording and communication device 300. Further, in some embodiments, the process may generate (block B410) the composite image data 330 by using the image data with higher resolution to clean up and increase the clarity and/or quality of the image data with the lower resolution. In some embodiments, the first set of capture settings 322 may include a first focal length capture setting that configures (block B402) the first camera 302 to capture (block B406) the first image data 326 that is focused on a foreground of the field of view 360, as described above. In addition, the second set of capture settings 324 may include a second focal length capture setting that configures (block B404) the second camera 304 to capture (block B408) the second image data 328 that is focused on a background of the field of view 362, as described above. In some embodiments, the first and second focal length capture settings may configure (blocks B402 and B404) the first and second cameras 302, 304, respectively, to capture (blocks B406 and B408) the first and second image data 326, 328, respectively, that allows for optical zooming on an object of interest.

In further reference to FIG. 18, in some embodiments, the first and second sets of capture settings 322, 324 may configure the first and second cameras 302, 304, respectively, to capture specific image data suitable for generating the composite image data 330, 354. For example, in some embodiments, the first set of capture settings 322 may include a first luminosity setting that configures (block B402) the first camera 302 to capture (block B406) the first image data 326 having first luminosity data. The second set of capture settings 324 may include a second luminosity setting that configures (block B404) the second camera 304 to capture (block B408) the second image data 328 having second luminosity data. In some embodiments, the first set of capture settings 322 may include a first RGB setting that configures (block B402) the first camera 302 to capture (block B406) first image data 326 having first red, blue, and/or green channel data. The second set of capture settings 324 may include a second RGB setting that configures (block B404) the second camera 304 to capture (block B408) second image data 328 having second red, blue, and/or green channel data. In various embodiments, the first set of capture settings 322 may include a first contrast setting that configures (block B402) the first camera 302 to capture (block B406) the first image data 326 having first contrast data. The second set of capture settings 324 may include a second contrast setting that configures (block B404) the second camera 304 to capture (block B408) the second image data 328 having second contrast data. In several embodiments, the first set of capture settings 322 may include a first exposure setting that configures (block B402) the first camera 302 to capture (block B406) the first image data 326 having first exposure data. The second set of capture settings 324 may include a second exposure setting that configures (block B404) the second camera 304 to capture (block B408) the second image data 328 having second exposure data.

In further reference to FIG. 18, in further embodiments, the first and second sets of capture settings 322, 324 may configure the first and second cameras 302, 304, respectively, to capture image data suitable for generating composite image data for particular functionalities. For example, the first set of capture settings 322 may configure (block B402) the first camera 302 to capture (block B406) the first image data 326 that may be used for face recognition. Likewise, the second set of capture settings 324 may configure (block B404) the second camera 304 to capture (block B408) the second image data 328 that may be used for face recognition. In such embodiments, the first and second sets of capture settings 322, 324 may be determined to capture the first and second image data 302, 304 concentrating on facial features that may be compared to a face database in network communication with the A/V recording and communication device 300 and/or the server 340. In another example, the first and second sets of capture settings 322, 324 may configure the first and second cameras 302, 304 to capture image data suitable for generating high-dynamic-range (HDR) image data. In such embodiments, the first set of capture settings 322 may include a first exposure setting that configures the first camera 302 to capture the first image data 326 having a first exposure range. The second set of capture settings 324 may include a second exposure setting that configures the second camera 304 to capture the second image data 328 having a second exposure range, where the second exposure range does not overlap with the first exposure range. In various embodiments, the camera application 320 may configure the processor 314 to generate the composite image data 330 by combining the first image data 326 having the first exposure range with the second image data 328 having the second exposure range to generate HDR image data.

FIG. 19 is a flowchart illustrating an embodiment of a process 430 for determining the first and second sets of capture settings 322, 324 according to various aspects of the present disclosure. The process 430 may include receiving (block B432) a user's input regarding at least one specific capture setting such as (but not limited to) resolution, focal length, luminosity, RBG channel, contrast, and/or exposure. In some embodiments, the process 430 may include receiving (block B432) a user's input regarding a particular A/V recording and communication device functionality such as (but not limited to) face recognition. The process 430 may also include determining (block B434) a first set of capture settings 322 based on the received user's input. The process 430 may also include determining (block B436) a second set of capture settings 324 based on the received user's input. However, in other embodiments, the first and second sets of capture settings 322, 324 may be predetermined without user input.

FIG. 20 is a flowchart illustrating another embodiment of a process 450 for determining the first and second sets of capture settings 322, 324 according to various aspects of the present disclosure. The process 450 may include configuring (block B452) the first camera 302 using a first set of capture settings 322 and capturing (block B454) the first image data 326, as described above. The process 450 may also include determining (block B456) a second set of capture settings 324 based on the first image data 326 and configuring (block B458) the second camera 304 using the second set of capture settings 324. In various embodiments, the A/V recording and communication device 300 may be configured to analyze the first image data 326 and determine suitable settings for the second set of capture settings 324 using processes familiar to one of ordinary skill in the art. For example, if the first image data 326 includes an object of interest that is out of focus, the second set of capture settings 324 may include a second focal length capture setting that configures (block B458) the second camera 304 to capture the second image data 328 that includes the object of interest in focus. In another example, the A/V recording and communication device 300 may be configured to measure exposure using the first image data 326 captured using the first set of capture settings 322 and determine (block B456) an exposure capture setting for the second set of capture settings 324. In some embodiments, the first camera 302 may be powered on before the second camera 304, such that when the second camera 304 is powered on, there is no exposure shift as the second camera 304 has been configured with the exposure capture setting based on the first image data 326.

FIG. 21 is a flowchart illustrating another embodiment of a process 470 for generating the composite image data 354 according to various aspects of the present disclosure. In various embodiments, the process 470 may be performed using the server 340 and include receiving (block B472) the first image data 326 using the communication module 352, where the first image data 326 is captured using the first camera 302 configured with the first set of capture settings 322, as described above. The process 470 may also include receiving (block B474) the second image data 328 using the communication module 352, where the second image data 328 is captured using the second camera 304 configured with the second set of capture settings 324, as described above. The process 470 may further include generating (block B476) the composite image data 354, as described above. The process 470 may also include streaming (block B478) the composite image data 354 to a client device (such as the client device 114 in FIG. 1) and/or to a server (such as the server 118 in FIG. 1) using the communication module 352. In some embodiments, the server 340 may also stream the composite image data 354, first image data 326 and/or the second image data 328 to the client device 114.

FIG. 22 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.

With reference to FIG. 22, 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).). In some embodiments, 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. The memory 804 may include removable memory elements, such as a CompactFlash card, a MultiMediaCard (MMC), and/or a Secure Digital (SD) card. In some embodiments, 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. For example, 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.

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, 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. Thus, the present embodiments are not limited to any specific combination of hardware and software.

FIG. 23 is a functional block diagram of a general-purpose computing system on which the present embodiments may be implemented according to various aspects of the present disclosure. The computer 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 execute at least some of the operations described above. 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. 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 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.

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.

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.

Audio/Video Recording and Communication Devices with Multiple Cameras Having Variable Capture Settings

Information

Publication Number

Date Filed

Date Published

Inventors

Original Assignees

CPC

International Classifications

Abstract

Description

Claims

CROSS-REFERENCE TO RELATED APPLICATION

Provisional Applications (1)