Patent Publication Number: US-11399157-B2

Title: Augmenting and sharing data from audio/video recording and communication devices

Description:
CROSS-REFERENCE TO RELATED APPLICATIONS 
     This application claims priority to and is a continuation application of Ser. No. 15/926,496, filed on Mar. 20, 2018, which is a continuation-in-part of U.S. application Ser. No. 15/857,537, filed on Dec. 28, 2017, which is a continuation-in-part of U.S. application Ser. No. 15/480,214, filed on Apr. 5, 2017, which is a continuation-in-part of U.S. application Ser. No. 15/431,607, filed on Feb. 13, 2017, now U.S. Pat. No. 10,033,780, which issued on Jul. 24, 2018, and U.S. application Ser. No. 15/431,275, filed on Feb. 13, 2017, now U.S. Pat. No. 9,819,713, which issued on Nov. 14, 2017, each of which claims priority to provisional application Ser. No. 62/376,826, filed on Aug. 18, 2016, and provisional application Ser. No. 62/300,547, filed on Feb. 26, 2016. The entire contents of the priority applications are hereby incorporated by reference as if fully set forth. 
    
    
     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 improve the functionality of A/V recording and communication devices by facilitating easy sharing of video footage recorded by such devices. 
     BACKGROUND 
     Home safety is a concern for many homeowners and renters. Those seeking to protect or monitor their homes often wish to have video and audio communications with visitors, for example, those visiting an external door or entryway. Audio/Video (A/V) recording and communication devices, such as doorbells, provide this functionality, and can also aid in crime detection and prevention. For example, audio and/or video captured by an A/V recording and communication 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 apparatus, systems, and methods for augmenting and sharing data from audio/video (A/V) recording and communication devices 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 users of audio/video (A/V) recording and communication devices may from time to time desire to share video footage recorded by their devices. For example, when an A/V recording and communication device records video footage of suspicious activity, or even criminal activity, a user viewing the footage may desire to alert his or her neighbors to the possible danger posed by the person(s) involved in the suspicious or criminal activity. It would be advantageous, then, to enhance the functionality of A/V recording and communication devices by facilitating easy sharing of video footage recorded by such devices with one&#39;s neighbors. In another example, an A/V recording and communication device may record video footage of activity that may be of interest to the user&#39;s friends and family (e.g., images of children playing in the yard). It would be advantageous, then, to enhance the functionality of A/V recording and communication devices by facilitating easy sharing of video footage recorded by such devices with one&#39;s friends and family. In each of the foregoing and additional examples, it would also be advantageous to include comments, such as descriptive text or the like, with the shared video footage. The present embodiments, as described in detail below, provide these, and other, enhancements. In particular, the present embodiments enable video footage captured by A/V recording and communication devices to be readily annotated, uploaded to the cloud, and shared with anyone of the user&#39;s choosing, including neighbors, friends, and family. In addition, the present embodiments improve upon and solve the problem of video footage captured by A/V recording and communication devices being accessible only to the owner of the A/V recording and communication device, which limits the ability of such devices to help stop crime. 
     Another aspect of the present embodiments includes the realization that A/V recording and communication devices, such as A/V recording and communication doorbells, are very well adapted for capturing audio and/or video of criminal activity, but not every person owns such a device. Further, many people who do not own such devices do own other types of devices, including client devices such as smartphones, that are equipped with cameras and microphones and are also capable of capturing audio and/or video of criminal activity. It would be advantageous, then, to provide a network that facilitated the sharing of audio and/or video of criminal activity regardless of what type of device captured the audio and/or video. It would be even more advantageous if such a network enabled communication between users who own A/V recording and communication devices, such as A/V recording and communication doorbells, and users who do not own such devices. And it would be still more advantageous if such a network facilitated the inclusion of textual messages and/or comments, for example, to provide context for shared audio or video. The present embodiments provide such a network. 
     Another aspect of the present embodiments includes the realization that members of a neighborhood (may also be referred to as “network of users”) may benefit from using additional data, e.g., data captured by other users in the network and/or from third party sources, to inform comments for association with data for sharing. In various embodiments, a neighborhood may include a grouping of members (may also be referred to as “users”) sharing information using a neighborhood platform running on each user&#39;s client device. For example, the neighborhood platform may include a neighborhood alert feed that allows members to post videos, photos, and/or texts to alert other members of possible suspicious activity in the neighborhood using a share signal. In some embodiments, a first user may share first image data that includes an entity of interest, such as a person of interest committing a criminal act or acting suspiciously. As part of the sharing, and to facilitate an understanding of the first image data, for example, it may be beneficial to determine a plurality of comments, e.g., based on an analysis of the content of the first image data, which in some instances may also include consideration of data from other users in the network and/or from third party sources. The comments may be presented to the first user, and the first user may select at least one of those messages for sharing with the first image data, e.g., to the network of users. In such embodiments, other users, such as a second user, may be asked for permission to search second image data captured by devices associated with the second user for a match of the entity of interest. Further, if the entity of interest is found in the second image data, the matched second image data may be appended to the first image data of the entity of interest and the associated message(s) and further shared to other users of the network. In other embodiments, a first user may not have video but may still share a text-based description of an entity of interest. In such embodiments, other users, such as the second user, may see the shared text-based description of the entity of interest and be asked for permission to search the second image data for a match of the text-based description of the entity of interest. In addition, if the entity of interest is found in the second image data, the matched second image data may be included with the text-based description of the entity of interest and the associated comment(s) and further shared to other users of the network. In these ways, neighborhood safety may be enhanced by tracking movement and activity of the person of interest and providing multiple data points for users of the network to see suspicious and/or criminal patterns in the neighborhood. The present embodiments provide these advantages and enhancements, as described below. 
     In a first aspect, a method for a network device, the network device communicatively coupled to a plurality of audio/video (A/V) recording and communication devices, includes: receiving, from an A/V recording and communication device of the plurality of A/V recording and communication devices, first data including image data generated by a camera of the A/V recording and communication device; analyzing the first data to determine one or more characteristics of the first data; receiving, from an additional source, second data; analyzing the second data to determine that the second data includes at least one of the one or more characteristics; based on the determining that the second data includes the at least one of the one or more characteristics, determining at least one textual message for association with the first data, the at least one textual message indicative of the at least one of the one or more characteristics; transmitting, to a first client device associated with the A/V recording and communication device, the image data and the at least one textual message; receiving, from the first client device, consent for sharing the image data with a geographic area network, the consent indicating a selection of a textual message from the at least one textual message; and transmitting, to a second client device, the image data and the textual message. 
     In an embodiment of the first aspect, the method further includes: based on the one or more characteristics of the first data, determining that the image data includes an entity of interest; and transmitting, to a third client device, a request to analyze additional image data for the entity of interest, wherein the additional image data comprises the second data and is captured by a camera of a second A/V recording and communication device of the plurality of A/V recording and communication devices associated with the third client device. 
     In another embodiment of the first aspect, the method further includes: receiving, from the third client device, consent for sharing the additional image data with the geographic area network; and′ transmitting, to the second client device, the additional image data. 
     In another embodiment of the first aspect, the additional image data is appended to the image data and the textual message. 
     In another embodiment of the first aspect, at least one of the analyzing the first data or the analyzing the second data comprises using at least one of facial recognition, color matching schemes, or a body build score. 
     In another embodiment of the first aspect, the method further includes receiving confirmation by a human user that the second data includes the at least one of the one or more characteristics. 
     In another embodiment of the first aspect, the at least one textual message comprises a textual description of an entity having the one or more characteristics. 
     In another embodiment of the first aspect, the at least one textual message comprises a textual description of at least one of a time or a location associated with the image data. 
     In another embodiment of the first aspect, the network device comprises at least one of a backend server, an application programming interface (API), a storage device, or a hub device. 
     In another embodiment of the first aspect, the one or more characteristics of the first data comprise at least one characteristic of a person of interest. 
     In another embodiment of the first aspect, the at least one characteristic of the person of interest comprises a physical feature of the person of interest&#39;s body. 
     In another embodiment of the first aspect, the one or more characteristics of the first data comprise at least one characteristic of an object of interest. 
     In another embodiment of the first aspect, the object of interest comprises at least one of a vehicle or an animal. 
     In another embodiment of the first aspect, the additional source comprises a database associated with a law enforcement agency. 
     In another embodiment of the first aspect, the determining the at least one textual message comprises: scoring a plurality of messages based on the one or more characteristics; and selecting a predetermined number of the plurality of messages based on the scoring. 
     In another embodiment of the first aspect, 16: The method of paragraph 15, wherein the selecting the predetermined number of the plurality of messages based on the scoring comprises selecting at least one of a predetermined number of messages having highest scores or selecting a predetermined number of messages having a score equal to or above a threshold score. 
     In a second aspect, a method for a network device, the network device communicatively coupled to an audio/video (A/V) recording and communication device, includes: receiving, from the A/V recording and communication device, image data; analyzing the image data to determine one or more objects depicted in the image data; based on the determination of the one or more objects, determining at least one message for association with the image data; transmitting, to a first client device associated with the A/V recording and communication device, the image data and the at least one message; receiving, from the first client device, consent for sharing the image data with a geographic area network, the consent indicating a selection of a message from the at least one message; and transmitting, to a second client device, the image data and the message. 
     In an aspect of the second embodiment, the analyzing the image data comprises comparing the image data to additional image data. 
     In another embodiment of the second aspect, the method further includes receiving, from an additional source, the additional image data 
     In another embodiment of the second aspect, the additional source comprises a second A/V recording and communication device, and the method further comprising: transmitting, to a third client device associated with the second A/V recording and communication device, a request to at least one of receive or access the additional image data, wherein the additional image data is captured by a camera of the second A/V recording and communication device. 
     In another embodiment of the second aspect, the method further includes: receiving, from the third client device, consent for sharing the additional image data; and transmitting, to the second client device, the additional image data. 
     In another embodiment of the second aspect, the method further includes transmitting, to the first client device, the additional image data and a request to confirm that the additional image data includes the person of interest. 
     In another embodiment of the second aspect, the method further includes receiving, from the first client device, a confirmation that the additional image data includes the person of interest. 
     In another embodiment of the second aspect, the method further includes transmitting the additional image data to a network of users. 
     In another embodiment of the second aspect, the method further includes determining that at least one of the one or more objects is an object of interest, wherein the message is a textual message associated with the object of interest. 
     In another embodiment of the second aspect, the object of interest comprises at least one of a person of interest, a vehicle of interest, or an animal of interest. 
     In another embodiment of the second aspect, the determining that the at least one of the one or more objects is the object of interest comprises comparing the one or more objects to additional image data depicting the object of interest. 
     In another embodiment of the second aspect, the analyzing the image data to determine the one or more objects depicted in the image data comprises using at least one of facial recognition, color matching schemes, or a body build score. 
     In another embodiment of the second aspect, the method further includes receiving confirmation by a human user that the image data depicts the one or more objects. 
     In another embodiment of the second aspect, the at least one message comprises a textual description of the one or more objects. 
     In another embodiment of the second aspect, the method further includes receiving at least one of a time or a location associated with the image data, wherein the at least one message comprises a textual description of at least one of the time or the location associated with the image data. 
     In another embodiment of the second aspect, the method further includes: receiving, from the first client device, additional text; and transmitting, to the second device, the additional text with the image data and the textual message. 
     In another embodiment of the second aspect, the determining the at least one textual message comprises: scoring a plurality of messages based on the one or more objects depicted in the image data; and selecting a predetermined number of the plurality of messages based on the scoring. 
     In another embodiment of the second aspect, the selecting the predetermined number of the plurality of messages based on the scoring comprises selecting at least one of a predetermined number of messages having highest scores or selecting a predetermined number of messages having a score equal to or above a threshold score. 
     In another embodiment of the second aspect, the network device comprises at least one of a backend server, an application programming interface (API), a storage device, or a hub device. 
     In a third aspect, a method for a network device includes: receiving, from an audio/video (A/V) recording and communication device, image data; transmitting, to a first client device associated with the A/V recording and communication device, the image data; receiving, from the first client device, an indication of a request to share the image data with a geographic area network; in response to receiving the indication, analyzing the image data to determine one or more characteristics of the image data; obtaining additional data from an additional data source; analyzing the additional data to determine that the additional data includes at least one of the one or more characteristics from the image data; based on the image data and the additional data, determining at least one textual comment corresponding to the at least one of the one or more characteristics; transmitting, to the first client device, the at least one textual comment; receiving, from the first client device, consent for sharing the image data with the geographic area network, the consent indicating a selection of a comment from the at least one comment; and transmitting, to a second client device, the image data and the comment. 
     In an embodiment of the third aspect, the indication of the request is generated by the first client device in response to a user interaction with a graphical user interface presented on a display of the first client device. 
     In another embodiment of the third aspect, the graphical user interface is configured to promote input of text associated with the image data. 
     In another embodiment of the third aspect, the method further includes: based on the one or more characteristics of the image data, determining that the image data includes an entity of interest; and transmitting, to a third client device, a request to analyze additional image data for the entity of interest, wherein the additional image data is captured by a camera of a second A/V recording and communication device and is associated with the third client device. 
     In another embodiment of the third aspect, the method further includes: receiving, from the third client device, consent for sharing the additional image data with the geographic area network; and′ transmitting, to the second client device, the additional image data. 
     In another embodiment of the third aspect, the additional image data is appended to the image data and the textual message for sharing with the network of users. 
     In another embodiment of the third aspect, at least one of the analyzing the image data and the analyzing the additional data comprises using at least one of facial recognition, color matching schemes, or a body build score. 
     In another embodiment of the third aspect, the method further includes receiving confirmation by a human user that the additional data includes the at least one of the one or more characteristics. 
     In another embodiment of the third aspect, at least one textual message comprises a textual description of an entity having the one or more characteristics. 
     In another embodiment of the third aspect, the method further includes the at least one textual message comprises a textual description of at least one of a time or a location associated with the image data. 
     In another embodiment of the third aspect, the one or more characteristics of the image data comprise at least one characteristic of a person of interest. 
     In another embodiment of the third aspect, the at least one characteristic of the person of interest comprises a physical feature of the person of interest&#39;s body. 
     In another embodiment of the third aspect, the one or more characteristics of the image data comprise at least one characteristic of an object of interest. 
     In another embodiment of the third aspect, the object of interest comprises at least one of a vehicle or an animal. 
     In another embodiment of the third aspect, the determining the at least one textual message comprises: scoring a plurality of messages based on the one or more characteristics; and selecting a predetermined number of the plurality of messages based on the scoring. 
     In another embodiment of the third aspect, the selecting the predetermined number of the plurality of messages based on the scoring comprises selecting at least one of a predetermined number of messages having highest scores or selecting a predetermined number of messages having a score equal to or above a threshold score. 
     In another embodiment of the third aspect, the network device comprises at least one of a backend server, an application programming interface (API), a storage device, or a hub device. 
     In a fourth aspect, a method for a network device includes: receiving, from an audio/video (A/V) recording and communication device, image data representing an image; analyzing the image data to determine one or more objects depicted by the image data; based on the analyzing the image data, determining at least one comment associated with the one or more objects; transmitting, to a first client device associated with the A/V recording and communication device, the image data representing the image and the at least one comment; receiving, from the first client device, consent for sharing the image data with a geographic area network, the consent indicating a selection of a comment from the at least one comment; and transmitting, to a second client device, the image data representing the image and the comment. 
     In an embodiment of the fourth aspect, the analyzing the image data comprises comparing the image data to additional image data. 
     In another embodiment of the fourth aspect, the method further includes: receiving, from an additional source, the additional image data 
     In another embodiment of the fourth aspect, the method further includes: the additional source comprises a second A/V recording and communication device, and the method further comprising: transmitting, to a third client device associated with the second A/V recording and communication device, a request to at least one of receive or access the additional image data, wherein the additional image data is captured by a camera of the second A/V recording and communication device. 
     In another embodiment of the fourth aspect, the method further includes: receiving, from the third client device, consent for sharing the additional image data; and transmitting, to the second client device, the additional image data. 
     In another embodiment of the fourth aspect, the method further includes: determining that at least one of the one or more objects is an object of interest, wherein the message is a textual message associated with the object of interest. 
     In another embodiment of the fourth aspect, the object of interest comprises at least one of a person of interest, a vehicle of interest, or an animal of interest. 
     In another embodiment of the fourth aspect, the determining that the at least one of the one or more objects is an object of interest comprises comparing the one or more objects to additional image data depicting the object of interest. 
     6 In another embodiment of the fourth aspect, the analyzing the image data to determine one or more objects depicted by the image data comprises using at least one of facial recognition, color matching schemes, or a body build score. 
     In another embodiment of the fourth aspect, the method further includes receiving confirmation by a human user that the image data depicts the one or more objects. 
     In another embodiment of the fourth aspect, the at least one message comprises a textual description of the one or more objects. 
     In another embodiment of the fourth aspect, the method further includes receiving at least one of a time or a location associated with the image data, wherein the at least one message comprises a textual description of at least one of the time or the location associated with the image data. 
     In another embodiment of the fourth aspect, the method further includes: receiving, from the first client device, additional text; and transmitting, to the second device, the additional text with the image data and the textual message. 
     In another embodiment of the fourth aspect, the network device comprises at least one of a backend server, an application programming interface (API), a storage device, or a hub device. 
     In another embodiment of the fourth aspect, the method further includes transmitting, to the first client device, the additional image data and a request to confirm that the matched image data includes the person of interest. 
     In another embodiment of the fourth aspect, the method further includes receiving, from the first client device at the backend server, a confirmation that the additional image data includes the person of interest. 
     In another embodiment of the fourth aspect, the method further includes transmitting the additional image data to a network of users. 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
       The various embodiments of the present apparatus, systems, and methods for augmenting and sharing data from audio/video (A/V) recording and communication devices now will be discussed in detail with an emphasis on highlighting the advantageous features. These embodiments depict the novel and non-obvious apparatus, systems, and methods for augmenting and sharing data from A/V recording and communication devices 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 the present embodiments; 
         FIG. 2  is a front view of an A/V recording and communication doorbell according to an aspect of the present disclosure; 
         FIG. 3  is a rear view of the A/V recording and communication doorbell of  FIG. 2 ; 
         FIG. 4  is a left side view of the A/V recording and communication doorbell of  FIG. 2  attached to a mounting bracket according to an aspect of the present disclosure; 
         FIG. 5  is cross-sectional right side view of the A/V recording and communication doorbell of  FIG. 2 ; 
         FIG. 6  is an exploded view of the A/V recording and communication doorbell and the mounting bracket of  FIG. 4 ; 
         FIG. 7  is a rear view of the mounting bracket of  FIG. 4 ; 
         FIGS. 8A and 8B  are top and bottom views, respectively, of the A/V recording and communication doorbell and the mounting bracket of  FIG. 4 ; 
         FIGS. 9A and 9B  are top and front views, respectively, of a passive infrared sensor holder of the A/V recording and communication doorbell of  FIG. 2 ; 
         FIGS. 10A and 10B  are top and front views, respectively, of a passive infrared sensor holder assembly of the A/V recording and communication doorbell of  FIG. 2 ; 
         FIG. 11  is a top view of the passive infrared sensor assembly of  FIG. 10A  and a field of view thereof according to an aspect of the present disclosure; 
         FIG. 12  is a functional block diagram of the components of the A/V recording and communication doorbell of  FIG. 2 ; 
         FIG. 13  is a flowchart illustrating a process for a A/V recording and communication doorbell according to an aspect of the present disclosure; 
         FIG. 14  is a flowchart illustrating another process for a A/V recording and communication doorbell according to an aspect of the present disclosure; 
         FIG. 15  is a flowchart illustrating another process for a A/V recording and communication doorbell according to an aspect of the present disclosure; 
         FIG. 16  is a functional block diagram illustrating a system for sharing video footage from audio/video recording and communication devices according to the present embodiments; 
         FIG. 17  is a top plan view of a neighborhood with a plurality of A/V recording and communication doorbells according to an aspect of the present disclosure; 
         FIG. 18  is a sequence diagram illustrating a process for sharing video footage from an A/V recording and communication doorbell according to an aspect of the present disclosure; 
         FIG. 19  is a flowchart illustrating another process for sharing video footage from an A/V recording and communication doorbell according to an aspect of the present disclosure; 
         FIGS. 20-24  are screenshots of a graphical user interface (GUI) illustrating aspects of a process for sharing video footage from an A/V recording and communication device according to an aspect of the present disclosure; 
         FIGS. 25-29  are screenshots of a graphical user interface (GUI) illustrating aspects of another process for sharing video footage from an A/V recording and communication device according to an aspect of the present disclosure; 
         FIG. 30  is a sequence diagram illustrating another process for sharing video footage from an A/V recording and communication doorbell according to an aspect of the present disclosure; 
         FIG. 31  is a flowchart illustrating another process for sharing video footage from an A/V recording and communication doorbell according to an aspect of the present disclosure; 
         FIGS. 32-37  are screenshots of a graphical user interface (GUI) illustrating aspects of another process for sharing video footage from an A/V recording and communication device according to an aspect of the present disclosure; 
         FIG. 38  is a sequence diagram illustrating another process for sharing video footage from an A/V recording and communication doorbell according to an aspect of the present disclosure; 
         FIG. 39  is a flowchart illustrating another process for sharing video footage from an A/V recording and communication doorbell according to an aspect of the present disclosure; 
         FIG. 40  is a flowchart illustrating another process for sharing video footage from an A/V recording and communication doorbell according to an aspect of the present disclosure; 
         FIG. 41  is a sequence diagram illustrating another process for sharing video footage from an A/V recording and communication doorbell according to an aspect of the present disclosure; 
         FIG. 42  is a flowchart illustrating another process for sharing video footage from an A/V recording and communication doorbell according to an aspect of the present disclosure; 
         FIG. 43  is a functional block diagram illustrating a system for sharing video footage from A/V recording and communication devices according to the present embodiments; 
         FIG. 44  is a functional block diagram of a client device on which the present embodiments may be implemented according to various aspects of the present disclosure; 
         FIG. 45  is a functional block diagram of a general-purpose computing system on which the present embodiments may be implemented according to various aspects of present disclosure; 
         FIG. 46  is a screenshot of a graphical user interface (GUI) illustrating aspects of another process for sharing video footage from an A/V recording and communication device according to an aspect of the present disclosure; 
         FIG. 47  is a functional block diagram illustrating a system for communicating in a network according to various aspects of the present disclosure; 
         FIG. 48  is a functional block diagram illustrating one embodiment of a first A/V recording and communication device according to various aspects of the present disclosure; 
         FIG. 49  is a functional block diagram illustrating one embodiment of a second A/V recording and communication device according to various aspects of the present disclosure; 
         FIG. 50  is a functional block diagram illustrating one embodiment of a first client device according to various aspects of the present disclosure; 
         FIG. 51  is a functional block diagram illustrating one embodiment of a second client device according to various aspects of the present disclosure; 
         FIG. 52  is a functional block diagram illustrating one embodiment of a backend device according to various aspects of the present disclosure; 
         FIGS. 53 and 54  are flowcharts illustrating embodiments of processes for searching second image data for a match of a person of interest provided in first image data according to various aspects of the present disclosure; 
         FIGS. 55 and 56  are flowcharts illustrating embodiments of processes for searching image data for a match of a person of interest provided in a text-based description according to various aspects of the present disclosure; 
         FIGS. 57 and 58  are flowcharts illustrating embodiments of processes for augmenting and sharing data from audio/video (A/V) recording and communication devices and client devices according to various aspects of the present disclosure; 
         FIGS. 59 and 60  are sequence diagrams illustrating embodiments of processes for searching second image data for a match of a person of interest according to various aspects of the present disclosure; and 
         FIG. 61  is a functional block diagram illustrating a system for communicating in a network using various devices according to various aspects of the 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. 
     In some embodiments, this disclosure may include the language, for example, “at least one of [element A] and [element B]”. This language may refer to one or more of the elements. For example, “at least one of A and B” may refer to “A”, “B”, or “A and B”. In other words, “at least one of A and B” may refer to “at least one of A and at least one of B,” or “at least of either A or B.” Additionally, this disclosure may include the language, for example, “[first element], [second element], and/or [third element].” This language may refer to one or more of the elements. For example, “A, B, and/or C” may refer to “A”, “B”, “C”, “A and B” “A and C”, “B and C”, or “A, B, and C”. 
     The embodiments of the present apparatus, systems, and methods for augmenting and sharing data from audio/video (A/V) recording and communication devices and client devices 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) recording and communication device, such as a doorbell  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 functionality of the doorbells described herein, but without the front button and related components. 
     The A/V recording and communication doorbell  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 doorbell  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 doorbell  100  may also include other hardware and/or components, such as a housing, one or more motion sensors (and/or other types of sensors), a button, etc. The A/V recording and communication doorbell  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 doorbell  100  communicates with a user&#39;s network  110 , which may be for example a wired and/or wireless network. If the user&#39;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&#39;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 doorbell  100  may communicate with the user&#39;s client device  114  via the user&#39;s network  110  and the network  112  (Internet/PSTN). The user&#39;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&#39;s client device  114  comprises a display (not shown) and related components capable of displaying streaming and/or recorded video images. The user&#39;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 doorbell  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&#39;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.34bis analog modem connection, a cable modem, an ATM (Asynchronous Transfer Mode) connection, or an FDDI (Fiber Distributed Data Interface) or CDDI (Copper Distributed Data Interface) connection. Furthermore, communications may also include links to any of a variety of wireless networks, including WAP (Wireless Application Protocol), GPRS (General Packet Radio Service), GSM (Global System for Mobile Communication), CDMA (Code Division Multiple Access), TDMA (Time Division Multiple Access), FDMA (Frequency Division Multiple Access), and/or OFDMA (Orthogonal Frequency Division Multiple Access) cellular phone networks, Global Navigation Satellite System (GNSS) (e.g., Global Positioning System (GPS)), CDPD (cellular digital packet data), RIM (Research in Motion, Limited) duplex paging network, Bluetooth radio, or an IEEE 802.11-based radio frequency network. The network can further include or interface with any one or more of the following: RS-232 serial connection, IEEE-1394 (Firewire) connection, Fibre Channel connection, IrDA (infrared) port, SCSI (Small Computer Systems Interface) connection, USB (Universal Serial Bus) connection, or other wired or wireless, digital or analog, interface or connection, mesh or Digi® networking. 
     According to one or more aspects of the present embodiments, when a person (may be referred to interchangeably as “visitor”) arrives at the A/V recording and communication doorbell  100 , the A/V recording and communication doorbell  100  detects the visitor&#39;s presence and begins capturing video images within a field of view of the camera  102 . The A/V recording and communication doorbell  100  may also capture audio through the microphone  104 . The A/V recording and communication doorbell  100  may detect the visitor&#39;s presence using a motion sensor, and/or by detecting that the visitor has depressed the button on the A/V recording and communication doorbell  100 . 
     In response to the detection of the visitor, the A/V recording and communication doorbell  100  sends an alert to the user&#39;s client device  114  ( FIG. 1 ) via the user&#39;s network  110  and the network  112 . The A/V recording and communication doorbell  100  also sends streaming video, and may also send streaming audio, to the user&#39;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 doorbell  100  and the user&#39;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 doorbell  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 doorbell  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. As discussed in further detail below, 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. 
       FIGS. 2-4  illustrate an audio/video (A/V) communication doorbell  130  according to an aspect of present embodiments.  FIG. 2  is a front view,  FIG. 3  is a rear view, and  FIG. 4  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. 3 ). With reference to  FIG. 4 , 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. 2 , 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&#39;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. 2 and 4 , the doorbell  130  further includes an enclosure  131  that engages the faceplate  135 . In the illustrated embodiment, the enclosure  131  abuts an upper edge  135 T ( FIG. 2 ) 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. 3  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. 3 , 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. 4  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. 4 , 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&#39;s physical strength to support a connection to a different element. 
       FIG. 5  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  131 F 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  134   a  of the camera  134  protrudes through an opening in the enclosure  131 . The camera lens  134   a  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&#39;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&#39;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&#39;s  168  as it reflects off objects within the camera&#39;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. 5 , 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. 
     With continued reference to  FIG. 5 , 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. 5 , 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 . 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. 6  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. 6  shows the front side  137 F of the mounting bracket  137 . The mounting bracket  137  is configured to be mounted to the mounting surface such that the back side  137 B 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. 6 , 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&#39;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. 6 and 7  (which is a rear view of the mounting bracket  137 ), the mounting bracket  137  further comprises a bracket PCB  149 . With reference to  FIG. 7 , 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. 8A and 8B  are top and bottom views, respectively, of the doorbell  130 . As described above, the enclosure  131  may extend from the front face  131 F 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  131 F 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  137 R, 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. 8B , the lower end of the enclosure  131  may include security screw apertures  141  configured to receive screws or other fasteners. 
       FIG. 9A  is a top view of the PIR sensor holder  143 . The PIR sensor holder  143  may comprise any suitable material, including, without limitation, metals, metal alloys, or plastics. The PIR sensor holder  143  is configured to mount the PIR sensors  144  behind the lens  132  such that the PIR sensors  144  face out through the lens  132  at varying angles, thereby creating a wide field of view for the PIR sensors  144 , and dividing the field of view into zones, as further described below. With further reference to  FIG. 9A , the PIR sensor holder  143  includes one or more faces  178  within or on which the PIR sensors  144  may be mounted. In the illustrated embodiment, the PIR sensor holder  143  includes three faces  178 , with each of two outer faces  178  angled at 55° with respect to a center one of the faces  178 . In alternative embodiments, the angle formed by adjacent ones of the faces  178  may be increased or decreased as desired to alter the field of view of the PIR sensors  144 . 
       FIG. 9B  is a front view of the PIR sensor holder  143 . In the illustrated embodiment, each of the faces  178  includes a through hole  180  in which the PIR sensors  144  may be mounted. First and second brackets  182 , spaced from one another, extend transversely across the PIR sensor holder  143 . Each of the brackets  182  includes notches  184  at either end. The brackets  182  may be used to secure the PIR sensor holder  143  within the doorbell  130 . In alternative embodiments, the through holes  180  in the faces  178  may be omitted. For example, the PIR sensors  144  may be mounted directly to the faces  178  without the through holes  180 . Generally, the faces  178  may be comprise any structure configured to locate and secure the PIR sensors  144  in place. 
       FIGS. 10A and 10B  are top and front views, respectively, of a PIR sensor assembly  179 , including the PIR sensor holder  143 , the lens  132 , and a flexible power circuit  145 . The PIR sensor holder  143  may be secured to a rear face  132 R of the lens  132 , as shown, with the brackets  182  abutting the rear face  132 R of the lens  132 . The flexible power circuit  145 , which may be any material or component capable of delivering power and/or data to and from the PIR sensors  144 , is secured to a rear face  143 R of the PIR sensor holder  143 , and may be contoured to match the angular shape of the PIR sensor holder  143 . The flexible power circuit  145  may connect to, draw power from, and/or transmit data to and/or from, the power PCB  148  ( FIG. 5 ). 
       FIG. 11  is a top view of the PIR sensor assembly  179  illustrating the fields of view of the PIR sensors  144 . Each PIR sensor  144  includes a field of view, referred to as a “zone,” that traces an angle extending outward from the respective PIR sensor  144 . Zone  1  is the area that is visible only to Passive Infrared Sensor  144 - 1 . Zone  2  is the area that is visible only to the PIR sensors  144 - 1  and  144 - 2 . Zone  3  is the area that is visible only to Passive Infrared Sensor  144 - 2 . Zone  4  is the area that is visible only to the PIR sensors  144 - 2  and  144 - 3 . Zone  5  is the area that is visible only to Passive Infrared Sensor  144 - 3 . The doorbell  130  may be capable of determining the direction that an object is moving based upon which zones are triggered in a time sequence. In the illustrated embodiment, each zone extends across an angle of 110°. In alternative embodiments, each zone may extend across a different angle, such as one greater than or less than 110°. 
       FIG. 12  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. 12 , 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. 6 ). 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&#39;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. 12 , the front PCB  146  may comprise a light sensor  155 , one or more light-emitting components, such as LED&#39;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&#39;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&#39;s  156  may illuminate the light pipe  136  ( FIG. 2 ). 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&#39;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&#39;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. 12 , the power PCB  148  may comprise a power management module  162 , a microcontroller  163 , 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. 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. 12 , 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, such as those described below with reference to  FIG. 14 . 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. 12 , 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, such as those described below with reference to  FIG. 13 . 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. 12 , 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 (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&#39;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&#39;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. 
       FIG. 13  is a flowchart illustrating one embodiment of a process according to an aspect of the present disclosure. At block B 200 , a visitor presses the button  133  on the doorbell  130 . At block B 202 , the communication module  164  sends a request to a network device. Once the network device receives the request, at block B 204  the network device may connect the doorbell  130  to the user&#39;s client device  114  through the user&#39;s network  110  and the network  112 . In block B 206 , the doorbell  130  may record available audio and/or video data using the camera  134 , the microphone  158 , and/or any other sensor available. At block B 208 , the audio and/or video data is transmitted to the user&#39;s client device  114 . At block B 210 , the user may receive a notification on his or her client device  114  prompting him or her to either accept or deny. If the user denies the notification, then the process advances to block B 214 , where the audio and/or video data is recorded and stored at a cloud server. The session then ends at block B 216  and the connection between the doorbell  130  and the user&#39;s client device  114  is terminated. If, however, the user elects to accept the notification, then at block B 212  the user communicates with the visitor through the user&#39;s client device  114  while being provided audio and/or video data captured by the camera  134 , the microphone  158 , and/or other sensors. At the end of the call, the user may terminate the connection between the user&#39;s client device  114  and the doorbell  130  and the session ends at block B 216 . In some embodiments, the audio and/or video data may be recorded and stored at a cloud server even if the user accepts the notification and communicates with the visitor through the user&#39;s client device  114 . 
       FIG. 14  is a flowchart illustrating another embodiment of a process according to an aspect of the present disclosure. At block B 300 , an object may move into the field of view of one or more of the PIR sensors  144 . At block B 302 , the PIR sensors  144  may trigger the microcontroller  163 , which may then trigger the communication module  164  to send a request to a network device. At block B 304 , the network device may connect the doorbell  130  to the user&#39;s client device  114  through the user&#39;s network  110  and the network  112 . At block B 306 , the doorbell  130  may record available audio and/or video data using the camera  134 , the microphone  158 , and/or any other available sensor, and stream the data to the user&#39;s client device  114 . At block B 308 , the user may receive a notification prompting the user to either accept or deny the notification. If the notification is accepted, then at block B 310   a  the live audio/video data may be displayed on the user&#39;s client device  114 , thereby allowing the user surveillance from the perspective of the doorbell  130 . When the user is satisfied with this function, the user may sever the connection at block B 312 , whereby the session ends. If, however, at block B 308  the user denies the notification, or ignores the notification and a specified time interval elapses, then the connection between the doorbell  130  and the user&#39;s client device  114  is terminated and the audio/video data is recorded and stored at a cloud server at block B 310   b , such that the user may view the audio/video data later at their convenience. The doorbell  130  may be configured to record for a specified period of time in the event the notification in block B 308  is denied or ignored. If such a time period is set, the doorbell  130  may record data for that period of time before ceasing operation at block B 312  thereby ending the session. 
       FIG. 15  is a flowchart illustrating another embodiment of a process according to an aspect of the present disclosure. At block B 400 , the user may select a “snooze time-out,” which is a time period during which the doorbell  130  may deactivate or otherwise not respond to stimuli (such as light, sound, or heat signatures) after an operation is performed, e.g. a notification is either accepted or denied/ignored. For example, the user may set a snooze time-out of 15 minutes. At block B 402 , an object moves into the field of view of one or more of the PIR sensors  144 . At block B 404 , the microcontroller  163  may trigger the communication module  164  to send a request to a network device. In block B 406 , the network device may connect the doorbell  130  to the user&#39;s client device  114  through the user&#39;s network  110  and the network  112 . At block B 408 , audio/video data captured by the doorbell  130  may be streamed to the user&#39;s client device  114 . At block B 410 , the user may receive a notification prompting the user to either accept or deny/ignore the request. If the request is denied or ignored, then at block B 412   b  audio/video data may be recorded and stored at a cloud server. After the doorbell  130  finishes recording, the objects may remain in the PIR sensor  144  field of view at block B 414 . In block B 416 , the microcontroller  163  waits for the “snooze time” to elapse, e.g. 15 minutes, before triggering the communication module  164  to submit another request to the network device. After the snooze time, e.g. 15 minutes, elapses, the process moves back to block B 404  and progresses as described above. The cycle may continue like this until the user accepts the notification request at block B 410 . The process then moves to block B 412   a , where live audio and/or video data is displayed on the user&#39;s client device  114 , thereby allowing the user surveillance from the perspective of the doorbell  130 . At the user&#39;s request, the connection may be severed and the session ends at block B 418 . At this point the user may elect for the process to revert back to block B 416 , whereby there may be no further response until the snooze time, e.g. 15 minutes, has elapsed from the end of the previous session, or the user may elect for the process to return to block B 402  and receive a notification the next time an object is perceived by one or more of the PIR sensors  144 . 
     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. 16  illustrates a system  500  for sharing video footage from A/V recording and communication devices according to the present embodiments. The illustrated system  500  includes a first A/V recording and communication doorbell  502  (labeled “A/V Doorbell #1”). The first A/V doorbell  502  may have, for example, similar components and/or functionality as the doorbell  130  described herein. Alternatively, the first A/V doorbell  502  may have different components and/or functionality as the doorbell  130 , but may nevertheless be capable of recording video footage and/or audio and wirelessly transmitting the recorded video footage and/or audio. In certain embodiments, the first A/V doorbell  502  may not be a doorbell at all, but may be, for example, an A/V recording and communication security camera. 
     With further reference to  FIG. 16 , the system  500  further includes a first client device  504  (labeled “Client Device #1”) associated with the first A/V doorbell  502 . The first client device  504  and the first A/V doorbell  502  may be owned by and/or controlled by the same user. The first client device  504  may have, for example, similar components and/or functionality as the user&#39;s client device  114  described herein, and 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 system  500  further includes a network  506 . The network  506 , which may comprise, for example, the Internet and/or a public switched telephone network (PSTN), includes a plurality of network devices, such as one or more servers, routers, switches, storage devices, etc. (not shown). The system  500  further includes a plurality of other A/V doorbells  508 ,  510  (labeled “A/V Doorbell #2” through “A/V Doorbell #N”) and a plurality of other client devices  512 ,  514  (labeled “Client Device #2” through “Client Device #N”). The other client devices  512 ,  514  are each associated with a corresponding one of the other A/V doorbells  508 ,  510 . The other A/V doorbells  508 ,  510  may have, for example, similar components and/or functionality as the first A/V doorbell  502 , and the other client devices  512 ,  514  may have, for example, similar components and/or functionality as the first client device  504 . 
     In the system  500  of  FIG. 16 , any of the A/V doorbells may record video footage from an area within a field of view of the respective doorbell. The owner (or a user) of the doorbell that has recorded video footage may share the video footage with one or more other owners/users of the other A/V doorbells. The determination of which users will receive a notification of the shared video footage may be based on the relative locations of the A/V doorbells associated with the different users. More particularly, a given user (USER X) may receive a notification of the shared video footage if the shared video footage was recorded by one of the A/V doorbells that is located within a predetermined distance of USER X&#39;s own A/V doorbell. Further, in certain embodiments the predetermined distance may be configurable by USER X. Example processes for such sharing of recorded video footage are described below with reference to  FIGS. 17-19 . 
       FIG. 17  illustrates a neighborhood  516  comprising a plurality of buildings  518 , such as homes, offices, retail businesses, warehouses, etc. At least some of the buildings  518  include A/V recording and communication doorbells secured to an exterior surface, such as adjacent the front door. For example,  FIG. 17  illustrates three A/V doorbells (A/V Doorbell #1  520 , A/V Doorbell #2  522 , A/V Doorbell #3  524 ) associated with three different buildings. Each of the A/V doorbells  520 ,  522 ,  524  has a defined area around it represented by the three overlapping circles (Area #1  526 , Area #2  528 , Area #3  530 ). Each circle  526 ,  528 ,  530  represents the area from which the owner/user of the A/V doorbell at the center of the circle will receive notifications of shared video footage recorded by other A/V doorbells within the area. 
     For example, if A/V Doorbell #1  520  records video footage and the owner/user of A/V Doorbell #1  520  shares the recorded video footage, then the owner/user of A/V Doorbell #3  524  will receive a notification of the shared video footage because A/V Doorbell #1  520  is located within Area #3  530 , but the owner/user of A/V Doorbell #2  522  will not receive a notification of the shared video footage because A/V Doorbell #1  520  is located outside of Area #2  528 . In another example, if A/V Doorbell #2  522  records video footage and the owner/user of A/V Doorbell #2  522  shares the recorded video footage, then the owners/users of A/V Doorbells 1 and 3 will both receive a notification of the shared video footage because A/V Doorbell #2  522  is located within both Area #1  526  and Area #3  530 . In another example, if A/V Doorbell #3  524  records video footage and the owner/user of A/V Doorbell #3  524  shares the recorded video footage, then neither of the owners/users of A/V Doorbells 1 and 2 will receive a notification of the shared video footage because A/V Doorbell #3  524  is located outside of both Area #1  526  and Area #2  528 . The determinations of which owners/users will receive share notifications, and which owners/users will not receive share notifications, are summarized in the table at the bottom of  FIG. 17 . 
       FIG. 18  is a sequence diagram illustrating a process for sharing video footage from an A/V recording and communication doorbell (or other A/V recording and communication device) according to an aspect of the present disclosure. An A/V doorbell  520  (A/V Doorbell #1,  FIGS. 17 and 18 ) may record video footage, which may also include audio. For example, the doorbell  520  may begin recording the video footage when a visitor is detected at the doorbell  520 , which may occur, for example, when the doorbell  520  detects motion or when the visitor presses the front button on the doorbell  520 . With further reference to  FIG. 18 , the doorbell  520  sends a first alert signal and a first video signal  540  to the network  542 , and the network  542  receives the first alert signal and the first video signal  540 . The network  542  includes one or more network devices, such as, for example, one or more servers, routers, switches, storage devices, etc. (not shown). At least some of the network devices include a processor and a memory. The first video signal includes images (the video footage) captured by a camera of the doorbell  520 . 
     The network  542  transmits to a first client device  544  (User&#39;s Client Device #1), in response to receiving the first alert signal and the first video signal  540 , a second alert signal and a second video signal  546 . The second alert signal may be, for example, a push notification. A push notification, also called a server push notification, is the delivery of information from a software application to a computing device without a specific request from the client. The second video signal includes the images captured by the camera of the doorbell  520 . The user associated with the first client device  544  may be the owner/user of the doorbell  520  (A/V Doorbell #1). The user, upon receiving the second alert signal, may choose to answer the second alert signal, which may, for example, open a live call between the user and the visitor at the doorbell  520 . Alternatively, the user may ignore the second alert signal (e.g. choose not to answer the call). If the user ignores the second alert signal, he or she may still view the video footage of the second video signal at a later time. 
     After viewing (or while viewing) the video footage on the display of his or her client device  544 , the user may decide to share the video footage with other users. For example, the user may tap a “share” button from within an application executing on his or her client device  544 . The first client device  544  then sends a share signal  548  to the network  542 , and the network  542  receives the share signal  548  from the first client device  544 . In response to receiving the share signal  548  from the first client device  544 , at least one of the network devices in the network  542  determines the other users who are to receive a notification of the shared video footage. For example, the network device(s) may determine that the doorbell  520  that recorded the shared video footage is within a predefined distance from at least one other A/V recording and communication doorbell (or other A/V recording and communication device) from among a plurality of other A/V recording and communication doorbells (or other A/V recording and communication devices). For example, with reference to  FIG. 17 , if the doorbell that recorded the shared video footage is A/V Doorbell #1  520 , then the network device(s) may identify at least one other doorbell, such as A/V Doorbell #3  524 , having a defined area (Area #3  530 ) around it that encompasses the location of the doorbell  520  that recorded the shared video footage. Once the other doorbell(s) has/have been identified, the network device(s) may transmit a share notification signal  550  to each client device associated with the other doorbell(s) identified (including at least User&#39;s Client Device #3  552 ). The share notification signal  550  may be, for example, a push notification. The other user(s), upon receiving the share notification signal  550 , may choose to view the shared video footage. Alternatively, the other user(s) may ignore the share notification signal  550 . If the other user(s) ignores the share notification signal  550 , he or she may still view the shared video footage at a later time. 
     The process described above with reference to  FIG. 18  advantageously enables users of A/V recording and communication devices to share video footage with one another. This feature can help reduce crime by increasing public awareness of suspicious activity. For example, a first user may view video footage that was recorded by his or her doorbell and determine that the person or persons in the video footage are, or may be, engaged in criminal activity. The first user may then share that video footage with other users who, after viewing the shared video footage, may be alerted to be on the lookout for the person or persons in the shared video footage and, if one or more such other users observe the person or persons in the shared video footage engaged in further suspicious activity, they may be more likely to report the person or persons to law enforcement. 
     In the process of  FIG. 18 , as well as in other processes described herein, a determination is made as to which other users will receive a notification of the video footage that is shared by the first user. This determination is based on the relative locations of the A/V recording and communication devices associated with each of the users. And, as described above with reference to  FIG. 17 , whether or not a given user (User X) will receive a share notification is dependent upon the distance (alert radius) set by User X with respect to his or her own A/V recording and communication device(s). If the device that recorded the shared video is located within the area(s) defined by User X around his or her own A/V recording and communication device(s), then User X will receive a share notification. If the device that recorded the shared video is located outside the area(s) defined by User X around his or her own A/V recording and communication device(s), then User X will not receive a share notification. Thus, the determination of which users will receive a share notification is not dependent upon an alert radius set by the owner/user of the A/V recording and communication device that recorded the shared video. Rather, that determination is based on the alert radii set by the owners/users of the A/V recording and communication devices other than the device that recorded the shared video, and many of these alert radii may differ from one another. That is, User X 1  may set an alert radius of one-half mile around his or her doorbell while User X 2  may set an alert radius of three miles around his or her doorbell. If the device that recorded the shared video is within one-half mile of User X 1 &#39;s doorbell, then User X 1  will receive a share notification, and if the device that recorded the shared video is within three miles of User X 2 &#39;s doorbell, then User X 2  will receive a share notification. 
     Further, in some instances a first user may not receive a share notification while a second user may receive a share notification, even though the first user&#39;s doorbell is located closer to the doorbell that recorded the shared video than the second user&#39;s doorbell is. For example, again assume that User X 1  has set an alert radius of one-half mile around his or her doorbell while User X 2  has set an alert radius of three miles around his or her doorbell. If User X 1 &#39;s doorbell is one mile away from the doorbell that recorded the shared video and User X 2 &#39;s doorbell is two miles away from the doorbell that recorded the shared video, then User X 1  will not receive a share notification because the doorbell that recorded the shared video is outside User X 1 &#39;s alert radius, but User X 2  will receive a share notification because the doorbell that recorded the shared video is inside User X 2 &#39;s alert radius. 
     Still further, a given user may have more than one A/V recording and communication device, and at least two of those devices may be in different locations (e.g. not on the same property or attached to the same structure). In such cases, each device may have its own alert radius, and therefore its own defined distance/area for receiving share notifications. Thus, a user may receive a share notification when the device that recorded the shared video is within the defined area around at least one of that user&#39;s devices, even if the device that recorded the shared video is outside the defined area around at least one other of that same user&#39;s devices. 
     In some embodiments, a user may have more than one A/V recording and communication device at the same location (e.g. attached to the same structure, or attached to separate structures that are located on the same property). In such cases, devices that are proximate one another may share an alert area. For example, a user may have an A/V recording and communication doorbell located near his or her front door and an A/V recording and communication security camera located at the rear of his or her home. These devices may share one alert radius/alert area. 
     Still further, users may adjust as desired the size of the defined area(s) around their A/V recording and communication device(s). Information about each A/V recording and communication device in a given set of A/V recording and communication devices may be stored in one or more data structures and accessed when needed to determine which users will receive a share notification whenever a first user shares recorded video footage. When a user adjusts the size of the defined area(s) around his or her A/V recording and communication device(s), the information stored in the data structure(s) may be updated accordingly. 
       FIG. 19  is a flowchart illustrating another process for sharing video footage from an A/V recording and communication doorbell (or other A/V recording and communication device) according to an aspect of the present disclosure. The process of  FIG. 19  is described from the perspective of the network device(s). Thus, at block B 560  the network device(s) receive a first alert signal and a first video signal from a first A/V doorbell. At block B 562 , the network device(s) transmit a second alert signal and a second video signal to the first client device. At block B 564 , the network device(s) receive a share signal from the first client device. At block B 566 , the network device(s) determine at least one second A/V doorbell within at least one predefined distance from the first A/V doorbell. At block B 568 , the network device(s) transmit a share notification signal to the at least one second client device corresponding to the at least one determined second A/V doorbell. 
       FIGS. 20-24  are screenshots of a graphical user interface (GUI)  570  illustrating aspects of a process for sharing video footage from an A/V recording and communication device according to an aspect of the present disclosure. The process of  FIGS. 20-24  is described from the perspective of a user who receives an alert signal and a video signal on his or her client device. Thus, the GUI  570  illustrated in  FIGS. 20-24  is configured to be displayed on a display of the user&#39;s client device, such as a smartphone. 
     With reference to  FIG. 20 , a live call screen  572  is illustrated. When a user&#39;s A/V recording and communication device detects motion, or, in the case of a doorbell, when a visitor presses the front button on the doorbell, the user receives an alert on his or her client device along with streaming video footage recorded by the camera of the A/V recording and communication device. If the user answers the alert, a live call screen  572  such as that shown in  FIG. 20  may be displayed on the user&#39;s client device. The live call screen  572  may include one or more buttons, such as an END button  574  (to terminate or disconnect the call), a volume adjust button  576 , a mute button  578 , a full screen button  580  (to expand the video so that it fills the entire display screen), and/or a menu button  582 . 
     The live call screen  572  may further include a neighborhood share button  584 . If the user selects the neighborhood share button  584  during the live call, the GUI  570  may display a notification  586  that the user will be prompted after the live call to share the video of the call with other users in the user&#39;s “neighborhood,” e.g. those users determined according to the process described above with reference to  FIGS. 18 and 19 . For example, as shown in  FIG. 21 , the notification  586  may appear in a banner portion  588  of the live call screen  572 . Advantageously, displaying the notification  586  in a banner  588  does not interrupt the live call, so that the user and the visitor can continue speaking to one another for as long as desired. 
     If the user selects the neighborhood share button  584  during the live call, then after the call is terminated, such as when the user selects the END button  574  on the live call screen  572  ( FIG. 20 ), a share information screen  590  may be shown on the GUI  570 , as shown in  FIG. 22 . In the illustrated embodiment, the share information screen  590  includes a still image  592  from the video that was recorded during the live call, and textual information  594 . For example, the text  594  may include a phrase such as “Alert your neighborhood,” which informs (or reminds) the user that he or she is about to share the recorded video footage with one or more other users. The text  594  may further include a notice that the video footage will be shared along with a general indication of where the video was recorded. For example, the location information may identify the street name and block number, such as “1300 block of 14 th  Street,” and/or may identify the nearest intersection, such as “Near the intersection of 14 th  Street and Santa Monica Boulevard.” An icon  596 , such as a question mark, may also be displayed. If the user selects the question mark icon  596 , further information about the share feature may be displayed, and/or a help menu may be displayed. 
     The share information screen  590  may further include a text entry box  598 . If the user selects the text entry box  598 , such as by tapping on it if the user&#39;s client device includes a touchscreen display, a keyboard  600  may appear on the display, as shown in  FIG. 23 . The user may then enter text to describe the content of the shared video. After entering text, the user may select a SHARE button  602 , after which the share signal ( FIG. 18 ) is sent to the network and the network identifies one or more other users who will be notified of the shared video and sends out notifications to the identified other users. The share signal may include, or be accompanied by, the text entered by the user in the text entry box  598  of the GUI  570  shown in  FIG. 23 . The user may also decline to enter any text in the text entry box  598 , and may instead simply select the SHARE button  602  from the share information screen  590  of  FIG. 22 , after which the share signal ( FIG. 18 ) is sent to the network and the network identifies one or more other users who will be notified of the shared video and sends out notifications to the identified other users. 
     After the user selects the SHARE button  602 , with or without entering text in the text entry box  598 , a confirmation screen  604  may be displayed on the display of the user&#39;s client device, as shown in  FIG. 24 . The confirmation screen  604  may include text  606 , such as a message confirming that the video has been shared (“Your video has been shared”) and/or a thank you message (“Thanks for helping to keep your neighborhood safe.”). The confirmation screen  604  may further include a button, such as an OK button  608 , which, when selected, may return the user to another screen, such as a menu screen, of the application executing on the user&#39;s client device. With reference to  FIGS. 22-24 , the share information screen  590  ( FIG. 22 ), the text entry screen  610  ( FIG. 23 ), and/or the confirmation screen  604  ( FIG. 24 ) may include a close button  612  (the “X” in the upper right-hand corner). If the user selects the close button  612 , the share operation may be terminated without sharing the video footage from the live call. Further, if the user selects the close button  612 , a popup window (not shown) may be shown on the display asking the user to confirm that the share operation is to be terminated. 
     In further reference to  FIGS. 20-24 , in some embodiments the share signal may be sent to the network, and the network may enable one or more of the identified recipient users to further comment about the shared video and/or the text regarding the shared video. In some embodiments, the further comments may be directed to the user that shared the video, or may be directed to all the users. For example, if a user shares a video depicting a person committing a crime, another user that receives the shared video may recognize the person depicted in the video (the perpetrator). The recipient user may then send identifying information about the perpetrator, which may be useful in apprehending the perpetrator. In some embodiments, the identifying information may be sent directly to the user that shared the information, or it may be posted to the network such that it is visible to all the recipients of the shared video. In another example, if a user shares a video depicting a person committing a crime, and knows (or recognizes) the perpetrator, then users that receive the shared video may request the identifying information about the person directly from the user that shared the video. In some embodiments, the user that shared the video may get a direct message such as (but not limited to) an email requesting the information. The user may then decide whether or not to provide the identifying information to the requesting user. A further example may include the network providing a comment section with the shared video so that the various users may provide comments regarding the shared video. An additional example may include allowing users to post comments and/or send messages regarding the shared video without revealing their personal identity and/or contact information, such as email addresses. In further embodiments, the share signal may include image data and/or audio data that is captured and transmitted to the network in real-time (or near real-time), which may make the share signal a live video feed. In such embodiments, a user may set his or her share features to automatically share particular events and/or types of events to the network. In some embodiments, various users may comment on the shared live video feed, as described above. 
       FIGS. 25-29  are screenshots of a graphical user interface (GUI)  620  illustrating aspects of another process for sharing video footage from an A/V recording and communication device according to an aspect of the present disclosure. The process of  FIGS. 25-29  is described from the perspective of a user who views an earlier-recorded video on his or her client device. Thus, the GUI  620  illustrated in  FIGS. 25-29  is configured to be displayed on a display of the user&#39;s client device, such as a smartphone. In this embodiment, the video displayed on the user&#39;s client device is not a live call, but rather is a recording of a visitor event that took place earlier in time. The recording may be, however, a recording of an earlier live call between the user and the visitor. 
     With reference to  FIG. 25 , a video playback screen  622  is illustrated. When a user&#39;s A/V recording and communication device detects motion, or, in the case of a doorbell, when a visitor presses the front button on the doorbell, the user receives an alert on his or her client device along with streaming video footage recorded by the camera of the A/V recording and communication device. If the user ignores the alert, the motion event or button press event may nevertheless be recorded and stored at a remote network device. When the user later accesses the stored video footage, the video may be displayed on the video playback screen  622  on the user&#39;s client device, as shown in  FIG. 25 . Alternatively, if the user answers the alert and communicates with the visitor but does not share the video from within the live call (as described above with respect to  FIGS. 20-24 ), the user may still view the recorded video footage by accessing it from a menu, as described below. 
     With further reference to  FIG. 25 , the video playback screen  622  may include one or more buttons or controls, such as a volume adjustment slider widget  624 , a rewind button  626 , a play button  628 , a fast forward button  630 , a delete button  632 , and/or a share button  634 . If the user selects the share button  634 , a popup menu (not shown) may be shown on the display offering the user one or more options for sharing the video with his or her contacts and/or via social media. For example, the popup menu (or any other suitable type of interface) may include options for sharing the video via e-mail, via text message, and/or via social media, such as on NEXTDOOR®, FACEBOOK®, INSTAGRAM®, TWITTER®, etc. When the user selects one of the options, a new message (or post, etc.) may then be created including a link to the video to be shared. For example, if the user selects a social media network through which to share the video, the process may create a social media post with a link to the video to be shared. Posting the video to one or more social networks may enable the video to be seen by others, including others who live in the neighborhood where the video was recorded. Those persons may recognize a person in the video, and may be able to help identify that person. Further, the social network post may provide a warning to others who live in the neighborhood where the video was recorded, encouraging those people to be watchful for the person(s) in the video. 
     While the present embodiments are not limited to use with any particular social network, or type of social network, the present embodiments may nevertheless be well adapted for use with a neighborhood-oriented social network, such as NEXTDOOR®. Neighborhood-oriented social networks allow users to connect with people who live in their neighborhood, and/or in nearby neighborhoods, by limiting access to posts to the people in the same neighborhood as the poster, or those nearby. As described above, in some aspects the present embodiments enable a user to share a video to a social network. When the video is posted to a social networking service for neighborhoods, the video is more likely to be seen by people who live in the neighborhood where the video was recorded. The video is thus more likely to be relevant to the people in the neighborhood-oriented social network, because those people are more likely to have also seen the person(s) in the video. The neighborhood-oriented social network members may therefore be able to provide additional information about the person(s) in the video, such as confirming that they too have seen the person(s) in the neighborhood and/or helping to identify the person(s) in the video. If the person(s) in the video has committed criminal acts in the neighborhood, identifying the person(s) may help lead to their capture and conviction. 
     With further reference to  FIG. 25 , the video playback screen  622  may further include a progress bar  636  and a slider widget  638  that indicates what portion of the video is currently playing. For example, a timer  640  at a first end  642  of the progress bar  636  indicates how much of the video has elapsed, and a timer  644  at a second end  646  of the progress bar  636  indicates how much of the video is left to play. As the video plays, the progress slider widget  638  moves from the first end  642  to the second end  646  of the progress bar  636 . If the user wants to jump to a particular portion of the video, he or she may move the slider widget  638  left or right by selecting it, sliding it along the progress bar  636 , and releasing it. The video playback screen  622  may further include a Done button  648 , which, when selected, closes the video and returns the user to a previous screen within the application executing on the user&#39;s client device. 
     With further reference to  FIG. 25 , the video playback screen  622  may further include a neighborhood share button  584 . If the user selects the neighborhood share button  584 , the GUI  620  may display textual information  594 , as shown in  FIG. 26 . For example, the text  594  may include a phrase such as “Alert your neighborhood,” which informs (or reminds) the user that he or she is about to share the recorded video footage with one or more other users. The text  594  may further include a notice that the video footage will be shared along with a general indication of where the video was recorded. For example, the location information may identify the street name and block number, such as “1300 block of 14 th  Street,” and/or may identify the nearest intersection, such as “Near the intersection of 14 th  Street and Santa Monica Boulevard.” An icon  596 , such as a question mark, may also be displayed. If the user selects the question mark icon  596 , further information about the share feature may be displayed, and/or a help menu may be displayed. 
     The GUI  620  of  FIG. 26  may further include a text entry box  598 . If the user selects the text entry box  598 , such as by tapping on it if the user&#39;s client device includes a touchscreen display, a keyboard  600  may appear on the display, as shown in  FIG. 27 . The user may then enter text to describe the content of the shared video. After entering text, the user may select a SHARE button  602 , after which the share signal ( FIG. 18 ) is sent to the network and the network identifies one or more other users who will be notified of the shared video and sends out notifications to the identified other users. The share signal may include, or be accompanied by, the text entered by the user in the text entry box  598  of the GUI  620  shown in  FIG. 27 . The user may also decline to enter any text in the text entry box  598 , and may instead simply select the SHARE button  602  from the share screen  650  of  FIG. 26 , after which the share signal ( FIG. 18 ) is sent to the network and the network identifies one or more other users who will be notified of the shared video and sends out notifications to the identified other users. 
     After the user selects the SHARE button  602 , with or without entering text in the text entry box  598 , a confirmation message  652  may be displayed on the GUI  620  of the user&#39;s client device, as shown in  FIG. 28 . The confirmation message  652  may include text, such as a message confirming that the video has been shared (“Your video has been posted and your neighborhood has been alerted.”). With reference to  FIG. 29 , a popup message  654  may also be shown asking the user if he or she would like to “unshare” the video. The popup message  654  may include text  656  such as “You have already shared this video with your Neighborhood.” and one or more buttons, such as a CANCEL button  658  and/or a YES (or OK) button  660 . If the user selects the YES button  660 , the shared video may be “unshared,” whereas if the user selects the CANCEL button  658 , the shared video will not be “unshared.” With reference to  FIGS. 26-28 , the GUI  620  may include a close button  612  (the “X” in the upper right-hand corner). If the user selects the close button  612 , the share operation may be terminated without sharing the video footage. Further, if the user selects the close button  612 , a popup window (not shown) may be shown on the display asking the user to confirm that the share operation is to be terminated. 
     In some embodiments, video footage recorded by a user&#39;s A/V recording and communication device may not be stored at a remote network device on a long-term basis. In such embodiments, the user may still share video footage from his or her A/V recording and communication device with other users, but only from a live call, such as according to the process described above with reference to  FIGS. 20-24  (and not from a video playback process, such as that described above with reference to  FIGS. 25-29 ). To enable this aspect, all video recorded by the user&#39;s A/V recording and communication device may be temporarily stored at a remote network device so that it is available for sharing if the user shares the video footage from the live call. For example, the video may be temporarily stored at a remote network device as long as the live call is in progress, but if the live call terminates without the user selecting the neighborhood share button  584  ( FIG. 20 ), the video that was temporarily stored at the remote network device may then be deleted. 
     In further reference to  FIGS. 25-29 , and as described above with respect to  FIGS. 20-24 , in some embodiments, the share signal may be sent to the network, and the network may enable one or more of the identified recipient users to further comment about the shared video and/or the text regarding the shared video. In some embodiments, the further comments may be directed to the user that shared the video, or may be directed to all the users. For example, if a user shares a video depicting a person committing a crime, another user that receives the shared video may recognize the person depicted in the video (the perpetrator). The recipient user may then send identifying information about the person, which may be useful in apprehending the perpetrator. In some embodiments, the identifying information may be sent directly to the user that shared the information, or it may be posted to the network such that it is visible to all the recipients of the shared video. In another example, if a user shares a video depicting a person committing a crime, and knows (or recognizes) the perpetrator, then users that receive the shared video may request the identifying information about the person directly from the user that shared the video. In some embodiments, the user that shared the video may get a direct message such as (but not limited to) an email requesting the information. The user may then decide whether or not to provide the identifying information to the requesting user. A further example may include the network providing a comment section with the shared video so that the various users may provide comments regarding the shared video. An additional example may include allowing users to post comments and/or send messages regarding the shared video without revealing their personal identity and/or contact information, such as email addresses. In further embodiments, the share signal may include image data and/or audio data that is captured and transmitted to the network in real-time (or near real-time) which may make the share signal a live video feed. In such embodiments, a user may set his or her share features to automatically share particular events and/or types of events to the network. In some embodiments, various users may comment on the shared live video feed, as described above. 
       FIG. 30  is a sequence diagram illustrating another process for sharing video footage from an A/V recording and communication doorbell according to an aspect of the present disclosure. The process of  FIG. 30  includes aspects of the process of  FIG. 18 , including the doorbell  520  sending a first alert signal and a first video signal  540  to the network (and the network receives the first alert signal and the first video signal  540 ), the network  542  transmitting to a first client device (User&#39;s Client Device #1), in response to receiving the first alert signal and the first video signal, a second alert signal and a second video signal  546 , the first client device  544  sending a share signal  548  to the network (and the network receiving the share signal  548  from the first client device), and the network device(s)  542  transmitting a share notification signal  550  to each client device associated with the other doorbell(s) identified (including at least User&#39;s Client Device #3  552 ). 
     The process of  FIG. 30  further comprises the third client device  552  sending a playback request signal  662  to the network  542  (and the network  542  receiving the playback request signal  662  from the third client device  552 ), and the network device(s)  542 , in response to receiving the playback request signal  662  from the third client device  552 , transmitting a third video signal  664  to the third client device  552 , the third video signal  664  including the shared video footage recorded by A/V Doorbell #1  520 . For example, User&#39;s Client Device #3  552  may receive the share notification signal  550 , which may be, for example, a push notification. The user associated with User&#39;s Client Device #3  552  may then choose to view the shared video footage, such as by selecting a “VIEW NOW” button (or an “OK” button, etc.) in the push notification. Alternatively, the user may ignore the share notification signal  550 , but may subsequently request to view the shared video footage through one or more screens/menus within an application executing on User&#39;s Client Device #3  552 , as described below. The playback request signal  662  is then sent to the network  542 , and the shared video footage is sent to User&#39;s Client Device #3  552  in the third video signal  664 . 
       FIG. 31  is a flowchart illustrating another process for sharing video footage from an A/V recording and communication doorbell according to an aspect of the present disclosure. The process of  FIG. 31  is described from the perspective of the network device(s). Thus, at block B 560  the network device(s) receive a first alert signal and a first video signal from a first A/V doorbell. At block B 562 , the network device(s) transmit a second alert signal and a second video signal to the first client device. At block B 564 , the network device(s) receive a share signal from the first client device. At block B 566 , the network device(s) determine at least one second A/V doorbell within at least one predefined distance from the first A/V doorbell. At block B 568 , the network device(s) transmit a share notification signal to the at least one second client device corresponding to the at least one determined second A/V doorbell. At block B 670 , the network device(s) receive a playback request signal from the second client device. At block B 672 , the network device(s) transmits a third video signal to the second client device. 
       FIGS. 32-35  are screenshots of graphical user interfaces (GUIs) illustrating aspects of another process for sharing video footage from an A/V recording and communication device according to an aspect of the present disclosure.  FIGS. 32-35  are described below from the perspective of a user operating his or her client device. Thus, the GUIs illustrated in  FIGS. 32-35  are configured to be displayed on a display of the user&#39;s client device, such as a smartphone. 
     With reference to  FIG. 32 , the GUI  680  includes buttons for each of the user&#39;s A/V recording and communication devices. For example, the GUI  680  of  FIG. 32  includes a first button  682  for the doorbell located adjacent the user&#39;s front door and a second button  684  for the doorbell located adjacent the user&#39;s back door. The user may view video footage recorded by his or her devices by selecting from among the buttons  682 ,  684  corresponding to each device. The user may further view video footage organized by type by selecting from among a plurality of filter buttons  686 ,  688 ,  690 . For example, the GUI  680  of  FIG. 32  includes a first filter button  686  for ALL ACTIVITY, a second filter button  688  for CALLS (video recorded when the front button on the user&#39;s doorbell is pressed), and a third filter button  690  for MOTION (video recorded when the user&#39;s doorbell detects motion). When the user selects the ALL ACTIVITY filter button  686 , a list  691  may be displayed on the GUI  680  that includes entries for all videos recorded by the user&#39;s device(s), as well as entries for all shared videos recorded by other users&#39; devices in the user&#39;s “neighborhood,” e.g. those devices determined according to the process described above with reference to  FIGS. 18 and 19 . For example, the list  691  of  FIG. 32  includes entries labeled “ACCEPTED RING”  692  and “MISSED RING”  694 , which correspond to videos recorded by the user&#39;s doorbell(s) in response to the button on the doorbell(s) being pressed. The list  691  further includes entries labeled “MISSED MOTION”  696 , which correspond to videos recorded by the user&#39;s device(s) in response to motion being detected. 
     The list  691  of  FIG. 32  further includes an entry labeled “NEIGHBORHOOD ALERT [Suspicious Activity]”  698 . The neighborhood alert entry  698  may further include a neighborhood event icon  700 , which identifies the entry  698  as corresponding to a shared video from another user&#39;s device in the user&#39;s “neighborhood.” The neighborhood alert entry  698  may further include information about the shared video, including the approximate location  702  where it was recorded, the day and time  704  when it was recorded, and a textual description  706  of the video as provided by the user whose device recorded the video. If the user selects the neighborhood alert entry  698 , a playback request signal  662  is sent from the user&#39;s client device to the network ( FIG. 30 ), and a video signal  664  including the requested video is sent from the network to the user&#39;s client device. A GUI similar to that shown in  FIG. 25  (but without the neighborhood share button) may then be shown on the display of the user&#39;s client device and the user may view the shared video. 
     With reference to  FIG. 33 , the GUI  680  may further include a side menu  708 . The side menu  708  may be accessed, for example, by touching the display of the user&#39;s client device and swiping to the right (if the display of the user&#39;s client device is a touchscreen). The side menu  708  may include buttons  710  for various settings, buttons  712  for each of the user&#39;s A/V recording and communication devices, as well as a NEIGHBORHOOD button  714 . The NEIGHBORHOOD button  714  may further include the neighborhood event icon  700 , which is described in the foregoing paragraph. When the user selects the NEIGHBORHOOD button  714 , the NEIGHBORHOOD ACTIVITY screen  716  illustrated in  FIG. 34  may be displayed on the display of the user&#39;s client device. 
     With reference to  FIG. 34 , the NEIGHBORHOOD ACTIVITY screen  716  may include a Neighborhood button  718  and an Alert Settings button  720 . When the user selects the Neighborhood button  718 , a NEIGHBORHOOD ACTIVITY list  722  may be displayed on the GUI  680  that includes neighborhood alert entries  698  (the content and functionality of which is described above with respect to  FIG. 32 ). With further reference to  FIG. 34 , when the user selects the Alert Settings button  720 , if the user has A/V recording and communication devices at more than one location, then a Select a Neighborhood screen  724  may be displayed on the display of the user&#39;s client device, as shown in  FIG. 35 . The Select a Neighborhood screen  724  may include a list  726  having entries corresponding to each location (e.g. each “neighborhood”) where the user has at least one A/V recording and communication device. For example, the list  726  of  FIG. 35  includes a first entry  728  for the user&#39;s home “neighborhood” and a second entry  730  for the user&#39;s office “neighborhood.” In certain embodiments, if the user has more than one A/V recording and communication device at a given location, only one entry may be displayed per location. For example, if the user has two doorbells and one security camera at a given address, only one entry appears in the list  726  for that location, and the entry covers all three devices at that location. If the user has one or more A/V recording and communication devices at another location, another entry appears in the list  726  for that other location. Also in certain embodiments, the entries in the list  726  may comprise addresses rather than, or in addition to, names. For example, rather than the first entry  728  being labeled “Home” and the second entry  730  being labeled “Office,” the first entry  728  may be labeled “123 Main Street” and the second entry  730  may be labeled “456 First Street.” 
     If, however, the user does not have A/V recording and communication devices at more than one location, then when the user selects the Alert Settings button  720  ( FIG. 34 ) a Neighborhood Alert Settings screen  732  may be displayed on the display of the user&#39;s client device, as shown in  FIGS. 36 and 37 . Further, if the user has A/V recording and communication devices at more than one location, then when the user selects one of the locations from the list  726  on the NEIGHBORHOOD ACTIVITY screen  716  of  FIG. 35 , then the Neighborhood Alert Settings screen  732  of  FIGS. 36 and 37  may also be displayed on the display of the user&#39;s client device. 
     With reference to  FIG. 36 , the Neighborhood Alert Settings screen  732  includes an ON/OFF slider widget  734  that enables the user to toggle the video sharing feature on and off. When the ON/OFF slider widget  734  is in the ON position, as shown in  FIG. 36 , the user may receive sharing notifications (alerts) when other users in the user&#39;s “neighborhood” share videos, and shared videos may appear in the list  691  of events on the user&#39;s ALL ACTIVITY screen  736  ( FIG. 32 ), as well as in the list  722  of events on the user&#39;s NEIGHBORHOOD ACTIVITY screen  716  ( FIG. 34 ). In certain embodiments, the ON/OFF slider widget  734  may be in the ON position by default. When the ON/OFF slider widget  734  is in the OFF position, as shown in  FIG. 37 , the user may not receive sharing notifications (alerts) when other users in the user&#39;s “neighborhood” share videos, and shared videos may not appear in the list  691  of events on the user&#39;s ALL ACTIVITY screen  736  ( FIG. 32 ), but shared videos may appear in the list  722  of events on the user&#39;s NEIGHBORHOOD ACTIVITY screen  716  ( FIG. 34 ). The Neighborhood Alert Settings screen  732  further includes a text banner  738  that explains how the video sharing feature functions when the ON/OFF slider widget  734  is in the ON position ( FIG. 36 ) and when the ON/OFF slider widget  734  is in the OFF position ( FIG. 37 ). 
     With reference to  FIG. 36 , the Neighborhood Alert Settings screen  732  further includes a map  740 . An indicator  742  on the map  740  indicates the location of the user&#39;s A/V recording and communication device(s) corresponding to the location selected from the list  724  of  FIG. 35  (or corresponding to the single location at which the user has at least one A/V recording and communication device, if the user does not have A/V recording and communication devices at more than one location). In the illustrated embodiment, the indicator  742  comprises a dot, but in other embodiments the indicator  742  may comprise any other type of indicator, such as a pin, for example. The Neighborhood Alert Settings screen  732  further includes a text banner  744  that provides the street address of the location corresponding to the indicator  742  on the map  740 . 
     With further reference to  FIG. 36 , the Neighborhood Alert Settings screen  732  further includes a slider widget  746  for adjusting the alert radius around the user&#39;s A/V recording and communication device(s) at the location indicated on the map  740 . A circle  748  around the indicator  742  on the map  740  identifies the outer boundary of the area  750  from which the user will receive share notifications from other users. An area  750  within the circle  748  may be shaded, as indicated in  FIG. 36 . To adjust the size of the area  750 , the user adjusts the length of the alert radius by moving the slider widget  746  up or down. In the illustrated embodiment, moving the slider widget  746  up increases the size of the area  750  (and the alert radius), while moving the slider widget  746  down decreases the size of the area  750  (and the alert radius). As the slider widget  746  is moved up and down, the size of the circle  748  around the indicator  742  may increase and decrease to provide the user with a visual representation of the area  750  covered as the length of the alert radius increases and decreases. In some embodiments, the map  740  may have a default scale. As the user moves the slider widget  746  up to increase the size of the alert radius, if the circle  748  reaches the edges of the map  740 , then the map  740  may begin to scale down so that the entire alert area  750  is always visible on the map  740 . 
     When the user adjusts the size of the alert radius, the user&#39;s client device may send an alert radius adjustment signal to the network and the network may update a data structure with the changed size of the user&#39;s alert radius. For example, with further reference to  FIG. 36 , the user may adjust the size of the alert radius by moving the slider widget  746  up or down. To confirm the change, the user may select a back arrow  752  on the GUI  680  to return to the previous screen within the application executing on the user&#39;s client device. When the user selects the back arrow  752 , the alert radius adjustment signal is sent to the network and the network updates the data structure with the changed size of the user&#39;s alert radius. In some embodiments, if the user exits the application without selecting the back arrow  752 , then the adjustment of the alert radius may be discarded (the size of the alert radius may remain unchanged). 
     With further reference to  FIG. 36 , the magnitude of the alert radius may be indicated by a number on the slider widget  746 . For example, in  FIG. 36  the alert radius is set at 0.2 miles, as indicated by the number 0.2 on the slider widget  746 . Maximum and/or minimum magnitudes of the alert radius may be indicated by numbers at opposite ends of the slider widget  746 . For example, in  FIG. 36  the maximum alert radius is indicated as 10 miles at the upper end of the slider widget  746 , while the minimum alert radius is indicated as 0.1 miles at the lower end of the slider widget  746 . It should be appreciated that the maximum and minimum magnitudes shown in  FIGS. 36 and 37  are just examples and are not limiting. 
     In certain embodiments, the magnitude of the alert radius may be dynamically set based on the number of other A/V recording and communication devices around the location indicated on the map  740 . For example, the alert radius may be set such that the resulting defined area  750  around the user&#39;s A/V recording and communication device encompasses at least a minimum threshold number of other A/V recording and communication devices. Alternatively, the alert radius may be set such that the resulting defined area  750  around the user&#39;s A/V recording and communication device encompasses no more than a maximum threshold number of other A/V recording and communication devices. Still further, the alert radius may be set such that the resulting defined area  750  around the user&#39;s A/V recording and communication device encompasses a number of other A/V recording and communication devices that falls within a defined range. In certain embodiments, the magnitude of the alert radius may be dynamically adjusted as the number of other A/V recording and communication devices around the user&#39;s device changes. Thus, as more A/V recording and communication devices are added around the user&#39;s device, the size of the alert radius may be decreased so that the number of other A/V recording and communication devices in the defined area  750  remains about the same. Conversely, as A/V recording and communication devices are removed (or deactivated) from the area  750  around the user&#39;s device, the size of the alert radius may be increased so that the number of other A/V recording and communication devices in the defined area  750  remains about the same. In certain embodiments, the user may override the dynamic setting and/or adjustment of the magnitude of the alert radius by manually selecting the magnitude of the alert radius by moving the slider widget  746  as described above with reference to  FIG. 36 . 
     In some embodiments, the defined alert area about a user&#39;s A/V recording and communication device may not have a circular outer boundary. For example, a user may define an alert area about his or her A/V recording and communication device that has a non-circular shape, such as square, rectangular, or any other shape, including irregular polygons. The shape of the alert area may also extend a greater distance from A/V recording and communication device in one direction than in another direction. For example, if an A/V recording and communication device is located in a coastal area, or on a lakefront, or on an edge of an uninhabited area (such as a desert), or on an edge of a restricted area (such as a military base), then the user may not want the alert area to extend over the water, or desert, or military base, etc., but the user may want the alert area to extend a substantial distance in directions away from the water, or desert, or military base, etc. In such embodiments, the A/V recording and communication device would not be located at the center of the defined alert area. 
       FIG. 38  is a sequence diagram illustrating another process for sharing video footage from an A/V recording and communication doorbell according to an aspect of the present disclosure. In the process of  FIG. 38 , a new A/V recording and communication device is activated and connected to the network. In certain embodiments, some aspects of the activation/setup/connection process may be carried out using an application executing on the user&#39;s client device. Thus, with reference to  FIG. 38 , the user&#39;s client device  754  (User&#39;s Client Device #1) may send to the network  756 , and the network  756  may receive from the user&#39;s client device  754 , information  758  associated with the user&#39;s A/V recording and communication device (A/V Doorbell #1). The information  758  may include, for example, the location of the user&#39;s A/V recording and communication device. The location may comprise the street address of a building with which the user&#39;s A/V recording and communication device is associated, such as being secured thereto, for example. The user&#39;s client device  754  may further send to the network  756 , and the network  756  may further receive from the user&#39;s client device  754 , an enable signal  760  for the video sharing feature of the user&#39;s A/V recording and communication device. For example, during the setup process the user may enable (turn on) the video sharing feature using a GUI such as that illustrated in  FIG. 36 . In some embodiments, the video sharing feature may be enabled by default, such that the user does not have to take any affirmative steps to enable the video sharing feature. 
     With further reference to  FIG. 38 , the user&#39;s client device  754  may further send to the network  756 , and the network  756  may further receive from the user&#39;s client device  754 , a notification distance (alert radius)  762  associated with the video sharing feature of the user&#39;s A/V recording and communication device. For example, during the setup process the user may select an alert radius  762  using a GUI such as that illustrated in  FIG. 36 . In some embodiments, the alert radius  762  may be set automatically to a default value, or may be set automatically according to the criteria described above, such that the user does not have to take any affirmative steps to set the alert radius  762 . The alert radius  762  defines an area around the user&#39;s A/V recording and communication device that encompasses at least one other A/V recording and communication device, which in this example will be referred to as A/V Doorbell #2. A/V Doorbell #2 may record video footage, and the user associated with A/V Doorbell #2 may share the recorded video footage according to a process described herein. Thus, with further reference to  FIG. 38 , the client device associated with A/V Doorbell #2 (User&#39;s Client Device #2  764 ) may send to the network  756 , and the network  756  may receive from User&#39;s Client Device #2  764 , a share signal  766 . The network  756 , after determining that A/V Doorbell #2  764  is within the alert area defined around A/V Doorbell #1, may then send a share notification signal  768  to the client device associated with A/V Doorbell #1 (User&#39;s Client Device #1  754 ). 
       FIGS. 39 and 40  are flowcharts illustrating other processes for sharing video footage from an A/V recording and communication doorbell according to an aspect of the present disclosure.  FIG. 39  is described from the perspective of the user, while  FIG. 40  is described from the perspective of the network device(s). Thus, with reference to  FIG. 39 , at block B 770  the user may activate a new A/V recording and communication device and connect it to the network. As described above, some aspects of the activation/setup/connection process may be carried out using an application executing on the user&#39;s client device. At block B 772 , the user may enable the video sharing feature of the user&#39;s A/V recording and communication device, and at block B 774  the user may set a notification distance (alert radius) associated with the video sharing feature of the user&#39;s A/V recording and communication device. As described above, these aspects of the activation/setup/connection process may be automated, such that the user does not have to take any affirmative steps. The alert radius defines an area around the user&#39;s A/V recording and communication device that encompasses at least one other A/V recording and communication device, which in this example will be referred to as a second A/V doorbell. The second A/V doorbell may record video footage, and the user associated with the second A/V doorbell may share the recorded video footage according to a process described herein. The client device associated with the second A/V doorbell may send to the network, and the network may receive from the second A/V doorbell, a share signal. The network, after determining that the second A/V doorbell is within the alert area defined around A/V Doorbell #1, may then send a share notification signal to the client device associated with A/V Doorbell #1 (first client device). Thus, at block B 776  the first client device may receive the share notification signal, including a link to the video footage recorded by the second A/V doorbell that is within the notification distance (alert radius) of the first A/V doorbell. 
     With reference to  FIG. 40 , at block B 778  the network may receive from the user&#39;s client device information associated with the user&#39;s A/V recording and communication device (first A/V doorbell). The information may include, for example, the location of the first A/V doorbell. The location may comprise the street address of a building with which the first A/V doorbell is associated, such as being secured thereto, for example. At block B 780 , the network may further receive from the user&#39;s client device, an enable signal for the video sharing feature of the first A/V doorbell. For example, during the setup process the user may enable (turn on) the video sharing feature using a GUI such as that illustrated in  FIG. 36 . In some embodiments, the video sharing feature may be enabled by default, such that the user does not have to take any affirmative steps to enable the video sharing feature. 
     With further reference to  FIG. 40 , at block B 782  the network may further receive from the user&#39;s client device a notification distance (alert radius) associated with the video sharing feature of the first A/V doorbell. For example, during the setup process the user may select an alert radius using a GUI such as that illustrated in  FIG. 36 . In some embodiments, the alert radius may be set automatically to a default value, or may be set automatically according to the criteria described above, such that the user does not have to take any affirmative steps to set the alert radius. At block B 784 , the network may update one or more data structures (alert areas) with the information received about the first A/V doorbell, including its location and/or its alert radius. 
     The alert radius defines an area around the first A/V doorbell that encompasses at least one other A/V recording and communication device, which in this example will be referred to as second A/V doorbell. The second A/V doorbell may record video footage, and the user associated with the second A/V doorbell may share the recorded video footage according to a process described herein. Thus, with further reference to  FIG. 40 , at block B 786  the network may receive from the second client device a share signal. The network, after determining, at block B 788 , that the second A/V doorbell is within the alert area defined around the first A/V doorbell, may then send a share notification signal to the client device associated with the first A/V doorbell at block B 790 . 
       FIG. 41  is a sequence diagram illustrating another process for sharing video footage from an A/V recording and communication doorbell according to an aspect of the present disclosure. The process of  FIG. 41  includes aspects of the process of  FIG. 38 , including the user&#39;s client device  754  (User&#39;s Client Device #1) sending to the network  756  (and the network  756  receiving from the user&#39;s client device  754 , information  758  associated with the user&#39;s A/V recording and communication device (A/V Doorbell #1), the user&#39;s client device  754  further sending to the network  756  (and the network  756  further receiving from the user&#39;s client device  754 ) an enable signal  760  for the video sharing feature of the user&#39;s A/V recording and communication device, the user&#39;s client device  754  further sending to the network  756  (and the network  756  further receiving from the user&#39;s client device  754 ) a notification distance (alert radius)  762  associated with the video sharing feature of the user&#39;s A/V recording and communication device, the second client device  764  (User&#39;s Client Device #2) sending a share signal  766  to the network  756  (and the network  756  receiving the share signal  766  from the second client device  764 ), and the network device(s)  756  transmitting a share notification signal  768  to the user&#39;s client device  754 . 
     The process of  FIG. 41  further comprises the user&#39;s client device  754  sending a playback request signal  792  to the network  756  (and the network  756  receiving the playback request signal from the user&#39;s client device  754 ), and the network device(s)  756 , in response to receiving the playback request signal  792  from the user&#39;s client device  754 , transmitting a video signal  794  to the user&#39;s client device  754 , the video signal  794  including the shared video footage recorded by A/V Doorbell #2. For example, User&#39;s Client Device #1  754  may receive the share notification signal  768 , which may be, for example, a push notification. The user associated with User&#39;s Client Device #1  754  may then choose to view the shared video footage, such as by selecting a “VIEW NOW” button (or an “OK” button, etc.) in the push notification. Alternatively, the user may ignore the share notification signal  768 , but may subsequently request to view the shared video footage through one or more screens/menus within an application executing on User&#39;s Client Device #1  754 , as described above. The playback request signal  768  is then sent to the network  756 , and the shared video footage is sent to User&#39;s Client Device #1  754  in the video signal  794 . 
       FIG. 42  is a flowchart illustrating another process for sharing video footage from an A/V recording and communication doorbell according to an aspect of the present disclosure. The process of  FIG. 42  is described from the perspective of the network device(s). Thus, at block B 778  the network receives from the user&#39;s client device information associated with the user&#39;s A/V recording and communication device (first A/V doorbell). The information may include, for example, the location of the first A/V doorbell. The location may comprise the street address of a building with which the first A/V doorbell is associated, such as being secured thereto, for example. At block B 780 , the network may further receive from the user&#39;s client device, an enable signal for the video sharing feature of the first A/V doorbell. For example, during the setup process the user may enable (turn on) the video sharing feature using a GUI such as that illustrated in  FIG. 36 . In some embodiments, the video sharing feature may be enabled by default, such that the user does not have to take any affirmative steps to enable the video sharing feature. 
     With further reference to  FIG. 42 , at block B 782  the network may further receive from the user&#39;s client device a notification distance (alert radius) associated with the video sharing feature of the first A/V doorbell. For example, during the setup process the user may select an alert radius using a GUI such as that illustrated in  FIG. 36 . In some embodiments, the alert radius may be set automatically to a default value, or may be set automatically according to the criteria described above, such that the user does not have to take any affirmative steps to set the alert radius. At block B 784 , the network may update one or more data structures (alert areas) with the information received about the first A/V doorbell, including its location and/or its alert radius. 
     The alert radius defines an area around the first A/V doorbell that encompasses at least one other A/V recording and communication device, which in this example will be referred to as second A/V doorbell. The second A/V doorbell may record video footage, and the user associated with the second A/V doorbell may share the recorded video footage according to a process described herein. Thus, with further reference to  FIG. 40 , at block B 786  the network may receive from the second client device a share signal. The network, after determining, at block B 788 , that the second A/V doorbell is within the alert area defined around the first A/V doorbell, may then send a share notification signal to the client device associated with the first A/V doorbell at block B 790 . At block B 796 , the network receives a playback request signal from the first client device. At block B 798 , the network transmits a video signal to the first client device. 
       FIG. 43  is a functional block diagram illustrating a system  800  for sharing video footage from audio/video recording and communication devices according to the present embodiments. The system  800  may comprise a backend API  802  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  802  illustrated  FIG. 43  may include one or more APIs  804 . 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&#39;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  802  illustrated in  FIG. 43  may further include one or more services  806 ,  808  (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. 
     The backend API  802  illustrated in  FIG. 43  includes an alert areas service  806 . The alert areas service  806  may comprise one or more data structures  810  storing information about a plurality of A/V recording and communication devices. For example, the information may include the location of each device (such as the street address of each device), and the size of the alert radius around each device. The alert areas service  806  may access the information in the data structure(s)  810  when needed to determine which users will receive a share notification when a first user shares recorded video footage, as further described below. The alert areas service  806  may also maintain the information in the data structure(s)  810  and update the information in the data structure(s)  810  when new A/V recording and communication devices are activated, when existing A/V recording and communication devices are deactivated, and/or when the alert radii around existing A/V recording and communication devices are changed. 
     In the system  800  of  FIG. 43 , a first A/V recording and communication device  812  (A/V Doorbell  812  #1) may record video footage, which may also include audio. The doorbell  812  sends a first alert signal and a first video signal  814  to the API  804 , and the API  804  receives the first alert signal and the first video signal  814 . The first video signal includes images (the video footage) captured by a camera of the doorbell  812 . The API  804  transmits to a first client device  816  (User&#39;s Client Device #1), in response to receiving the first alert signal and the first video signal  814 , a second alert signal and a second video signal  818 . The second alert signal may be, for example, a push notification. The second video signal includes the images captured by the camera of the doorbell  812 . The user associated with the first client device  816  may be the owner/user of the doorbell  812  (A/V Doorbell #1). The user, upon receiving the second alert signal, may choose to answer the second alert signal, which may, for example, open a live call between the user and the visitor at the doorbell  812 . Alternatively, the user may ignore the second alert signal (e.g. choose not to answer the call). If the user ignores the second alert signal, he or she may still view the video footage of the second video signal at a later time. After viewing (or while viewing) the video footage on the display of his or her client device  816 , the user may decide to share the video footage with other users. For example, the user may tap a “share” button from within an application executing on his or her client device  816 . The first client device  816  then sends a share signal  820  to the API  804 , and the API  804  receives the share signal  820  from the first client device  816 . The share signal  820  may include text describing the images captured by the camera of the doorbell  812  (A/V Doorbell #1). In response to receiving the share signal  820  from the first client device  816 , the API  804  sends identifying information  822  to the alert areas service  806 . For example, the identifying information  822  may include an identifier for the user associated with A/V Doorbell #1 and an identifier for the video footage that is to be shared with other users. Alternatively, the identifying information  822  may include an identifier for A/V Doorbell #1 (rather than an identifier for the user associated with A/V Doorbell #1) and an identifier for the video footage that is to be shared with other users. The alert areas service  806  accesses the alert areas data structure(s)  810  and determines, based on the identifying information  822 , the other users who are to receive a notification of the shared video footage. For example, the alert areas service  806 , using the information stored in the alert areas data structure(s)  810  may determine that A/V Doorbell #1  812  is within the alert radius defined around at least one other A/V recording and communication device. Once the other device(s) has/have been identified, the alert areas service  806  may transmit a share notification signal  824  to a push notification service  808 . The share notification signal  824  may include the text describing the images captured by the camera of the doorbell  812  (A/V Doorbell #1). The push notification service  808  may then forward one or more push notifications  825  to a plurality of provider push notification services  826 . The provider push notification services  826  are configured to send push notifications to client devices that run different operating systems. For example, Android devices may receive push notifications from an Android push notification service  826 , while iOS devices may receive push notifications from an iOS push notification service  826 . Android is a mobile operating system (OS) developed by Google, based on the Linux kernel. iOS, by contrast, is a mobile operating system created and developed by Apple Inc. and distributed exclusively for Apple hardware. The provider push notification services  826  then send push notifications  828  to the client devices  830  associated with the other doorbell(s) identified by the alert areas service  806 . The other user(s), upon receiving the push notifications  828 , may choose to view the shared video footage. Alternatively, the other user(s) may ignore the push notifications  828 . If the other user(s) ignores the push notifications  828 , he or she may still view the shared video footage at a later time. In either event (viewing the shared video footage right away or viewing the shared video footage at a later time), one or more of the client devices  830  sends a playback request signal (not shown) to the backend API  802  (and the backend API  802  receives the playback request signal from the one or more of the client devices  830 ). In response to receiving the playback request signal from the one or more of the client devices  830 , the backend API  802  transmits a video signal (not shown) to the one or more of the client devices  830 . The video signal includes the shared video footage. In certain embodiments, the alert areas service  806  may receive the playback request signal from the one or more of the client devices  830  and transmit the video signal to the one or more of the client devices  830 . If the other user(s) opens the push notification, which may contain a reference to the shared video footage, the other user(s) client device(s)  830  may use the API  804  to get the URL (Uniform Resource Locator) of the shared video footage and any other metadata (if any) about the shared video footage so that the shared video footage can be played back. If the other user(s) opens the shared video footage from the NEIGHBORHOOD ACTIVITY screen  716  ( FIG. 34 ), a similar process may occur, but the reference to the shared video footage may be in the activity feed item. 
     In some embodiments, an A/V recording and communication device may begin recording video footage not in response to a visitor being detected, but rather when a user accesses the camera of the device to view live video footage using his or her client device (e.g. “on-demand” viewing). In such embodiments, a process for sharing a video may include a step of the user accessing the camera of the device to view live video footage using his or her client device (e.g. “on-demand” viewing), followed by the user sharing the live video footage. For example, the user may select a share button from within an application executing on the user&#39;s client device (similar to the share button  584  described above with respect to  FIGS. 20 and 21 ), and a share signal may then be sent from the user&#39;s client device and received by the network device(s) (similar to step  548  described above with respect to  FIG. 18 ), and a share notification signal may then be sent from the network device(s) and received by another client device(s) (similar to step  550  described above with respect to  FIG. 18 ). Example embodiments of video-on-demand are described in U.S. patent application Serial Nos. 62/267,762 and 62/289,114, both of which are incorporated herein by reference in their entireties as if fully set forth. 
     As described above, the present embodiments advantageously enable users of A/V recording and communication devices to share video footage with one another. This feature can help reduce crime by increasing public awareness of suspicious activity. Users can tailor the number and frequency of alerts (notifications of shared videos) they receive by increasing and decreasing the size of the alert radius around their own A/V recording and communication device(s). Users will only receive alerts that result from videos recorded by other A/V recording and communication devices that are located within the alert area that the user has set. Users may share videos as frequently or as infrequently as desired, and users may view shared videos from other users as frequently or as infrequently as desired. When a user receives an alert, he or she can choose to view the accompanying video immediately, or to ignore the alert. If the user ignores the alert, he or she can still view the video at a later time using one or more menu screens within an application executing on the user&#39;s client device. The present embodiments thus advantageously provide a tool that can be used to reduce crime rates and that can be tailored by each user to meet his or her personal preferences. 
     The present embodiments describe numerous ways for sharing videos, including via social media and/or social network(s). A social network may comprise a third-party network, such as NEXTDOOR®, FACEBOOK®, INSTAGRAM®, TWITTER®, etc. A social network may also comprise a network made up of users of A/V recording and communication devices, such as video doorbells and security cameras. For example, when a user shares a video via the neighborhood share button  584  described above with respect to  FIGS. 20, 21, 25, and 26 , the video is shared with a social network in which the members of the social network are users who have A/V recording and communication devices, such as video doorbells and security cameras. The present embodiments are not limited to any particular kind or type of social network. Further, participants in the social network are not limited to users of A/V recording and communication devices of any particular kind or type. 
     In the present embodiments, some steps shown in one or more of the sequence diagrams and/or flowcharts may be omitted. For example, in the process for sharing video footage from a first A/V recording and communication device, such as shown in  FIGS. 18 and 19 , for example, the steps of transmitting/receiving the first alert signal and the first video signal and transmitting/receiving the second alert signal and the second video signal may be omitted. Such an embodiment might comprise, therefore, just the steps of transmitting/receiving the share signal transmitting/receiving the share notification signal. 
       FIG. 44  is a functional block diagram of a client device  850  on which the present embodiments may be implemented according to various aspects of the present disclosure. The user&#39;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  850 . The client device  850  may comprise, for example, a mobile phone such as a smartphone, or a computing device such as a tablet computer, a laptop computer, a desktop computer, etc. 
     With reference to  FIG. 44 , the client device  850  includes a processor  852 , a memory  854 , a user interface  856 , a communication module  858 , and a dataport  860 . These components are communicatively coupled together by an interconnect bus  862 . The processor  852  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  852  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  854  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  854  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  854  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  852  and the memory  854  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  852  may be connected to the memory  854  via the dataport  860 . 
     The user interface  856  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  858  is configured to handle communication links between the client device  850  and other, external devices or receivers, and to route incoming/outgoing data appropriately. For example, inbound data from the dataport  860  may be routed through the communication module  858  before being directed to the processor  852 , and outbound data from the processor  852  may be routed through the communication module  858  before being directed to the dataport  860 . The communication module  858  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  860  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®/POD® 30-pin connector or LIGHTNING® connector. In other embodiments, the dataport  860  may include multiple communication channels for simultaneous communication with, for example, other processors, servers, and/or client terminals. 
     The memory  854  may store instructions for communicating with other systems, such as a computer. The memory  854  may store, for example, a program (e.g., computer program code) adapted to direct the processor  852  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  852  to perform the process steps described herein, hard-wired circuitry may be used in place of, or in combination with, software/firmware instructions for implementation of the processes of the present embodiments. Thus, the present embodiments are not limited to any specific combination of hardware and software. 
       FIG. 45  is a functional block diagram of a general-purpose computing system on which the present embodiments may be implemented according to various aspects of the present disclosure. The computer system  900  may execute at least some of the operations described above. The computer system  900  may be embodied in at least one of a personal computer (also referred to as a desktop computer)  900 A, a portable computer (also referred to as a laptop or notebook computer)  900 B, and/or a server  900 C. A server is a computer program and/or a machine that waits for requests from other machines or software (clients) and responds to them. A server typically processes data. The purpose of a server is to share data and/or hardware and/or software resources among clients. This architecture is called the client-server model. The clients may run on the same computer or may connect to the server over a network. Examples of computing servers include database servers, file servers, mail servers, print servers, web servers, game servers, and application servers. The term server may be construed broadly to include any computerized process that shares a resource to one or more client processes. 
     The computer system  900  may include at least 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 . 
     In some embodiments, users may tag or categorize their videos when sharing them with other users, and users may set one or more preferences for the type(s) of videos for which they want to receive share notifications. For example,  FIG. 46  illustrates an embodiment of a graphical user interface (GUI)  970  for setting one or more user preferences for the type(s) of videos for which the user wants to receive share notifications. The Neighborhood Alert Settings screen  970  includes a list  972  having a plurality of categories, including, for example, SUSPICIOUS ACTIVITY  974 , BURGLARY  976 , ATTEMPTED BURGLARY  978 , VANDALISM  980 , THEFT  982 , and OTHER  984 . By selecting one or more of the listed categories, a user may limit the type(s) of videos that will be shared with that user. For example, the user may only receive share notifications for shared videos that fall within one or more of the categories that the user has selected. A GUI (not shown) similar to that shown in  FIG. 46  may be provided to users during the video sharing process, so that the shared videos can be tagged or categorized. In some embodiments, a user may choose not to categorize a shared video. In some embodiments, a user who has set preferences for the types of videos he or she wants to be notified about may receive share notifications for uncategorized shared videos. In alternative embodiments, a user who has set preferences for the types of videos he or she wants to be notified about may not receive share notifications for uncategorized shared videos. 
     In some embodiments, users may be able to view shared videos regardless of where their own A/V recording and communication devices are located. In still further embodiments, even users who do not even own any A/V recording and communication devices may be able to view shared videos. For example, shared videos may be available through a publicly accessible forum, such as a website. In another example, shared videos may be accessed by users running an application on their client devices. A user sharing a video may have the option to make the shared video available to the public, or to restrict the shared video to only those users identified through the processes described above, such as the processes of  FIGS. 16-19 . In still further embodiments, a user may be able to view shared videos from any area the user specifies by selecting a location on a map and specifying an alert radius around the location. In still further embodiments, a user may enable “alerts around me.” This feature may work in real-time to provide the user with alerts from within a given radius of the user&#39;s current location. The user&#39;s current location may be determined, for example, using GPS technology and the user&#39;s mobile client device, such as a smartphone. 
     In some embodiments, shared videos may be accessed by law enforcement agencies. For example, a user sharing a video may have the option to make the shared video available to law enforcement through a web portal. Law enforcement may be able to log in through the web portal to view the shared videos. For example, the web portal may include a map view indicating the locations of all of the shared videos. The map view may include selectable markers or icons corresponding to the locations of the shared videos. Selecting one of the icons may open a video player and begin playback of the shared video corresponding to the selected icon. Different law enforcement agencies, departments, or groups may have different logins that grant access to specific zones, such as geographic locations that are within the jurisdiction of each agency, department, or group. 
     In some embodiments, users may be able to block videos from certain other users and/or from certain locations. 
     In some embodiments, when a user attempts to share a video, the video may undergo a review before being shared with other users. For example, with reference to  FIG. 18 , when the network  542  receives the share signal  548 , an administrator may subsequently review the video before the share notification signal  550  may be sent to any client devices of other users. If the video violates any policies, the administrator may prevent the share notification signal  550  from being sent to any client devices of other users. A notification, such as an e-mail, may be sent to the user who shared the video explaining that the video did not comply with one or more policies or guidelines. The requirement for administrator review may apply to all users, or selectively to only some users, such as users who have attempted to share one or more inappropriate videos. In further embodiments, an administrator may ban a user from sharing videos, such as for repeated policy violations (such as attempting to share one or more inappropriate videos). 
     As described above, one aspect of the present embodiments includes the realization that users of audio/video (A/V) recording and communication devices may from time to time desire to share video footage recorded by their devices. For example, when an A/V recording and communication device records video footage of suspicious activity, or even criminal activity, a user viewing the footage may desire to alert his or her neighbors to the possible danger posed by the person(s) involved in the suspicious or criminal activity. It would be advantageous, then, to enhance the functionality of A/V recording and communication devices by facilitating easy sharing of video footage recorded by such devices with one&#39;s neighbors. In another example, an A/V recording and communication device may record video footage of activity that may be of interest to the user&#39;s friends and family (e.g., images of children playing in the yard). It would be advantageous, then, to enhance the functionality of A/V recording and communication devices by facilitating easy sharing of video footage recorded by such devices with one&#39;s friends and family. In each of the foregoing and additional examples, it would also be advantageous to include comments, such as descriptive text or the like, with the shared video footage. The present embodiments, as described in detail below, provide these, and other, enhancements. In particular, the present embodiments enable video footage captured by A/V recording and communication devices to be readily annotated, uploaded to the cloud, and shared with anyone of the user&#39;s choosing, including neighbors, friends, and family. In addition, the present embodiments improve upon and solve the problem of video footage captured by A/V recording and communication devices being accessible only to the owner of the A/V recording and communication device, which limits the ability of such devices to help stop crime. 
     Another aspect of the present embodiments includes the realization that A/V recording and communication devices, such as A/V recording and communication doorbells, are very well adapted for capturing audio and/or video of criminal activity, but not every person owns such a device. Further, many people who do not own such devices do own other types of devices, including client devices such as smartphones, that are equipped with cameras and microphones and are also capable of capturing audio and/or video of criminal activity. It would be advantageous, then, to provide a network that facilitated the sharing of audio and/or video of criminal activity regardless of what type of device captured the audio and/or video. It would be even more advantageous if such a network enabled communication between users who own A/V recording and communication devices, such as A/V recording and communication doorbells, and users who do not own such devices. And it would be still more advantageous if such a network facilitated the inclusion of textual messages and/or comments, for example, to provide context for shared audio or video. The present embodiments provide such a network. 
     Another aspect of the present embodiments includes the realization that members of a neighborhood (may also be referred to as “network of users”) may benefit from using additional data, e.g., data captured by other users in the network and/or from third party sources, to inform comments for association with data for sharing. In various embodiments, a neighborhood may include a grouping of members (may also be referred to as “users”) sharing information using a neighborhood platform running on each user&#39;s client device. For example, the neighborhood platform may include a neighborhood alert feed that allows members to post videos, photos, and/or texts to alert other members of possible suspicious activity in the neighborhood using a share signal. In some embodiments, a first user may share first image data that includes an entity of interest, such as a person of interest committing a criminal act or acting suspiciously. As part of the sharing, and to facilitate an understanding of the first image data, for example, it may be beneficial to determine a plurality of comments, e.g., based on an analysis of the content of the first image data, which in some instances may also include consideration of data from other users in the network and/or from third party sources. The comments may be presented to the first user, and the first user may select at least one of those messages for sharing with the first image data, e.g., to the network of users. In such embodiments, other users, such as a second user, may be asked for permission to search second image data captured by devices associated with the second user for a match of the entity of interest. Further, if the entity of interest is found in the second image data, the matched second image data may be appended to the first image data of the entity of interest and the associated message(s) and further shared to other users of the network. In other embodiments, a first user may not have video but may still share a text-based description of an entity of interest. In such embodiments, other users, such as the second user, may see the shared text-based description of the entity of interest and be asked for permission to search the second image data for a match of the text-based description of the entity of interest. In addition, if the entity of interest is found in the second image data, the matched second image data may be included with the text-based description of the entity of interest and the associated comment(s) and further shared to other users of the network. In these ways, neighborhood safety may be enhanced by tracking movement and activity of the person of interest and providing multiple data points for users of the network to see suspicious and/or criminal patterns in the neighborhood. The present embodiments provide these advantages and enhancements, as described herein. 
       FIG. 47  is a functional block diagram illustrating a system  1000  for communicating in a network using a share signal. In various embodiments, the share signal may include image data and/or a text-based description of an entity of interest, e.g., a person of interest, a vehicle of interest, an animal of interest, or the like, as described herein. For example, a first client device may share first image, audio, and/or text data using a share signal, and the network may receive the share signal. As further described below, the network may include one or more backend devices that may be configured to receive the share signal, identify one or more entities of interest, and search second image, audio, and/or text data from various other users in the network and/or other sources for a match of the entity of interest. In some embodiments, if a match is found, the backend server may determine one or more comments or messages for association with the image. The determined comment(s) (and, in some instances, the first and/or second image, audio, and/or text data) may then be presented on the first client device, such that the user of the first client device can consent for sharing of the first image data, audio data, and/or text data with one or more of the determined comment(s). Moreover, in some embodiments, if a match is found, an alert signal that includes a notification that an entity of interest was matched may be sent to another user associated with the second image, audio, and/or text data. Further, in some embodiments, if a match of the entity of interest is found, the share signal may be appended to include the matched second image, audio, and/or text data. Thus, an entity of interest identified in or from the share signal may be further identified and tracked in captured data from other users and/or other sources beyond the user of the first client device, as further described herein. 
     In reference to  FIG. 47 , the system  1000  may include one or more first audio/video (A/V) recording and communication devices  1002  configured to access a first user&#39;s network  1008  to connect to a network (Internet/PSTN)  1010 . The A/V recording and communication device  1002  may include any or all of the components and/or functionality of the A/V recording and communication doorbell  130  (shown herein in  FIGS. 2-12 ), a security camera  1002 ( a ) and/or a floodlight controller  1002 ( b ). 
     The system  1000  may also include one or more first client devices  1004 ,  1006 , which in various embodiments may be configured to be in network communication with the first A/V recording and communication device  1002 . The first client devices  1004 ,  1006  may comprise, for example, a mobile phone such as a smartphone, or a computing device such as a tablet computer, a laptop computer, a desktop computer, etc. The first client devices  1004 ,  1006  may include any or all of the components and/or functionality of the client device  114  and/or the client device  850  described herein. In some embodiments, the first client devices  1004 ,  1006  may not be associated with a first A/V recording and communication device, as described above. 
     The system  1000  may also include security devices in addition to the A/V recording and communication devices  1002 . For instance, the system  1100  may further include a smart-home hub device  1036  (which may alternatively be referred to herein as the hub device  1036 ) connected to the user&#39;s network  1008 . The smart-home hub device  1036  (also known as a home automation hub, gateway device, etc.), may comprise any device that facilitates communication with and control of the one or more A/V recording and communication devices  1002  as well as other security device  1038 , including sensor  1038 ( a ) and/or automation device  1038 ( b ). For example, the smart-home hub device  1036  may be a component of a home automation system installed at a property. In some embodiments, the A/V recording and communication devices  1002 , the sensors  1038 ( a ), and/or the automation devices  1038 ( b ) may communicate with the smart-home hub device  1036  directly and/or indirectly via the user&#39;s network  1008  and/or the network (Internet/PSTN)  1010 . In some of the present embodiments, the A/V recording and communication devices  1002 , the sensors  1038 ( a ) and/or the automation devices  1038 ( b ) may, in addition to or in lieu of communicating with the smart-home hub device  1036 , communicate with the client devices  1004 ,  1006  and/or one or more of the components of the network of servers/backend devices  1030  directly and/or indirectly via the user&#39;s network  1008  and/or the network (Internet/PSTN)  1010 . 
     Home automation, or smart home, is building automation for the home. It involves the control and automation of various devices and/or systems, such as lighting, heating (such as smart thermostats), ventilation, air conditioning (HVAC), blinds/shades, and security, as well as home appliances, such as washers/dryers, ovens, or refrigerators/freezers. Wi-Fi is often used for remote monitoring and control. Smart home devices (e.g., the hub device  1036 , the sensors  1038 ( a ), the automation devices  1038 ( b ), the A/V recording and communication devices  1002 , etc.), when remotely monitored and controlled via the network (Internet/PSTN)  1010 , may be considered to be components of the Internet of Things. Smart home systems may include switches and/or sensors (e.g., the sensors  1038 ( a ) connected to a central hub such as the smart-home hub device  1036 , sometimes called a gateway, from which the system may be controlled with a user interface. The user interface may include any or all of a wall-mounted terminal (e.g., a keypad, a touchscreen, etc.), software installed on the client devices  1004 ,  1006  (e.g., a mobile application), a tablet computer or a web interface, often but not always via Internet cloud services. The home automation system may use one or more communication protocols, including either or both of wired and wireless protocols, including but not limited to Wi-Fi, X10, Ethernet, RS-485, 6LoWPAN, Bluetooth LE (BTLE), ZigBee, and Z-Wave. 
     The one or more sensors  1038 ( a ) may include, for example, at least one of a door sensor, a window sensor, a contact sensor, a tilt sensor, a temperature sensor, a carbon monoxide sensor, a smoke detector, a light sensor, a glass break sensor, a freeze sensor, a flood sensor, a moisture sensor, a motion sensor, and/or other sensors that may provide the user/owner of the security system a notification of a security event at his or her property. 
     The one or more automation devices  1038 ( b ) may include, for example, at least one of an outdoor lighting system, an indoor lighting system, and indoor/outdoor lighting system, a temperature control system (e.g., a thermostat), a shade/blind control system, a locking control system (e.g., door lock, window lock, etc.), a home entertainment automation system (e.g., TV control, sound system control, etc.), an electronic device, an irrigation control system, a wireless signal range extender (e.g., a Wi-Fi range extender, a Z-Wave range extender, etc.), a doorbell chime, a barrier control device (e.g., an automated door hinge), a smart doormat, and/or other automation devices. 
     In various embodiments, the system  1000  may also include one or more second A/V recording and communication devices  1012  connected to the network (Internet/PSTN)  1010  using a second user&#39;s network  1018  to connect to the network (Internet/PSTN)  1010 . Although an example A/V recording and communication device  1012  is depicted as a video doorbell-type device, A/V recording and communication device  1012  may be any type of device described herein. Moreover, and although not illustrated, second security devices, which may include a second hub device (which may be similar to the hub device  1036 ), one or more second sensor devices (which may be similar to the sensor devices  1038 ( a )), and/or one or more second automation devices (which may be similar to the automation devices  1038 ( b )) may also be in communication with the second user&#39;s network  1018 . The system  1000  may further include one or more second client devices  1014 ,  1016 , which in various embodiments may be configured to be in network communication with the second A/V recording and communication device  1012  and/or the second security devices. The second client devices  1014 ,  1016  may comprise, for example, a mobile phone such as a smartphone, or a computing device such as a tablet computer, a laptop computer, a desktop computer, etc. The second client devices  1014 ,  1016  may include any or all of the components and/or functionality of the client device  114  and/or the client device  850  described herein. In some embodiments, the second client devices  1014 ,  1016  may not be associated with a second A/V recording and communication device, as described above. 
     In some embodiments, the system  1000  may also include one or more third-party A/V recording and communication devices  1020  connected to the network (Internet/PSTN)  1010  using various third-party networks  1026  such as a local network, a wireless network such as a cellular/mobile network and/or a Wi-Fi network, a wired network such as an Ethernet network, a public network, a low-bandwidth network, and/or any other appropriate network to access the network (Internet/PSTN)  1010 . Although the example third-party A/V recording and communication device  1020  is depicted as a video doorbell-type device, the third-party A/V recording and communication device  1020  may be any type of device described herein. Moreover, and although not illustrated, third-party security devices, which may include a third-party hub device (which may be similar to the hub device  1036 ), one or more third-party sensor devices (which may be similar to the sensor devices  1038 ( a )), and/or one or more third-party automation devices (which may be similar to the automation devices  1038 ( b )) may also be in communication with the third-party networks  1026 . The system  1000  may further include one or more third-party client devices  1022 ,  1024 , which in various embodiments may be configured to be in network communication with the third-party A/V recording and communication device  1020 . The third-party client devices  1022 ,  1024  may comprise, for example, a mobile phone such as a smartphone, or a computing device such as a tablet computer, a laptop computer, a desktop computer, etc. The third-party client devices  1022 ,  1024  may include any or all of the components and/or functionality of the client device  114  and/or the client device  850  described herein. In some embodiments, the third-party client devices  1022 ,  1024  may not be associated with a third-party A/V recording and communication device, as described above. 
     With further reference to  FIG. 47 , the system  1000  may also include various backend devices such as (but not limited to) storage devices  1032 , backend servers  1030 , and backend APIs  1028  in network communication with the first, second, and third-party A/V communication devices  1002 ,  1012 ,  1020  and their respective client devices  1004 ,  1006 ,  1014 ,  1016 ,  1022 ,  1024 . In some embodiments, the storage devices  1032  may be a separate device from the backend servers  1030  (as illustrated) or may be an integral component of the backend servers  1030 . In addition, the first user&#39;s network  1008  and the network  1010  may be similar in structure and/or function to the user&#39;s network  110  and the network  112  ( FIG. 1 ), respectively. In some embodiments, the first and second A/V recording and communication devices  1002 ,  1012  may be similar in structure and/or function to the A/V doorbell  100  ( FIG. 1 ) and/or the A/V recording and communication doorbell  130  ( FIGS. 2-12 ). In some embodiments, the first user&#39;s client devices  1004 ,  1006  may be similar in structure and/or function to the user&#39;s client device  114  ( FIG. 1 ) and/or the user&#39;s client device  850  ( FIG. 44 ). Further, the second user&#39;s network  1018  may be similar in structure and/or function to the user&#39;s network  110  ( FIG. 1 ). In some embodiments, the second user&#39;s client devices  1014 ,  1016  may also be similar in structure and/or function to the user&#39;s client device  114  ( FIG. 1 ) and/or the user&#39;s client device  850  ( FIG. 44 ). Also, the storage devices  1032  may be similar in structure and/or function to the storage device  116  ( FIG. 1 ). In addition, in some embodiments, the backend servers  1030  and backend APIs  1028  may be similar in structure and/or function to the server  118  and the backend API  120  ( FIG. 1 ), respectively. 
     In various embodiments, the first user&#39;s client devices  1004 ,  1006  and/or the second client devices  1014 ,  1016  may connect to the network (Internet/PSTN)  1010  using any network, including, without limitation, a local network, a wireless network such as a cellular/mobile network and/or a Wi-Fi network, a wired network such as an Ethernet network, a public network, a low-bandwidth network, and/or any other appropriate network to access the network (Internet/PSTN)  1010 . 
       FIG. 48  is a functional block diagram illustrating an embodiment of the first A/V recording and communication device  1002  according to various aspects of the present disclosure. The first A/V recording and communication device  1002  may comprise a processing module  1050  that is operatively connected to a camera  1040 , a microphone  1042 , a speaker  1044 , and a communication module  1046 . The processing module  1050  may comprise a processor  1052 , volatile memory  1054 , and non-volatile memory  1056  that includes a camera application  1058 . In various embodiments, the camera application  1058  may configure the processor  1052  to capture first image data  1060  using the camera  1040  and first audio data  1062  using the microphone  1042 . In some embodiments, the camera application  1058  may also configure the processor  1052  to generate first text data  1064  describing the first image data  1060  and/or the first audio data  1062 . In other embodiments, the first text data  1064  describing the first image data  1060  may be generated by a user using the first client device  1004 ,  1006  associated with the first A/V recording and communication device  1002 , as described above. In some embodiments, the first text data  1064  describing the first audio data  1062  may be a transcription of the first audio data  1062 . In addition, the camera application  1058  may configure the processor  1052  to transmit the first image data  1060 , the first audio data  1062 , and/or the text data  1064  to the first client device  1004 ,  1006  using the communication module  1046 , and the first client device  1004 ,  1006  may generate and transmit a share signal  1048  using the first image data  1060 , the first audio data  1062 , and/or the text data  1064  to the backend server  1030 , as described above. In other embodiments, the camera application  1058  may configure the processor  1052  to directly generate and transmit a share signal  1048  using the first image data  1060 , the first audio data  1062 , and/or the text data  1064  to the backend server  1030  using the communication module  1046 . As further described below, the backend server  1030  may identify an entity of interest in the share signal  1048  and/or match the entity of interest in second image data, as further described below. In some embodiments, the backend server  1030  may also identify an object of interest in the share signal  1048  and match the object of interest in second image data provided by the second A/V recording and communication device  1012 . Further, in some embodiments, the share signal  1048  may only include first text data  1064  that includes a text-based description of a person and/or object of interest and the backend server  1030  may use the first text data  1064  to search and match the text-based description in the second image data, as further described below. In addition, in some embodiments, the share signal  1048  may only include first audio data  1062  associated with an entity of interest and the backend server  1030  may use the first audio data  1062  to search and match the entity of interest using second audio data, as further described below. 
       FIG. 49  is a functional block diagram illustrating an embodiment of the second A/V recording and communication device  1012  according to various aspects of the present disclosure. The second A/V recording and communication device  1012  may comprise a processing module  1080  that is operatively connected to a camera  1070 , a microphone  1072 , a speaker  1074 , and a communication module  1076 . The processing module  1080  may comprise a processor  1082 , volatile memory  1084 , and non-volatile memory  1086  that includes a camera application  1088 . In some embodiments, the camera application  1088  may configure the processor  1082  to capture second image data  1090  using the camera  1070  and second audio data  1092  using the microphone  1072 . In some embodiments, the camera application  1088  may also configure the processor  1082  to generate second text data  1094  describing the second image data  1090  and/or the second audio data  1092 . In other embodiments, the second text data  1094  describing the second image data  1090  may be generated by a user using the second client device  1014 ,  1016  associated with the second A/V recording and communication device  1012 , as described above. In some embodiments, the second text data  1094  describing the second audio data  1092  may be a transcription of the second audio data  1092 . In various embodiments, the camera application  1088  may also configure the processor to generate and transmit an output signal  1096  that may include the second image data  1090 , the second audio data  1092 , and/or the second text data  1094 . In some embodiments, the output signal  1096  may be transmitted, using the communication module  1076 , to the second client device  1014 ,  1016  and/or to a second hub device, and the second client device  1014 ,  1016  and/or the second hub device may send the output signal  1096  to the backend server  1030 . In other embodiments, the output signal  1096  may be transmitted directly to the backend server  1030  using the communication module  1076 . In embodiments described herein, the backend server  1030  may search the output signal  1096  to find a match of the entity of interest identified in the share signal, as further described below. For example, in some embodiments, the backend server  1030  may receive first image data  1060  of an entity of interest and may search and find a match of the entity of interest in the second image data  1090 . In a further example, in some embodiments, the backend server  1030  may receive a text-based  1064  description of an entity of interest and may search and find a match of the entity of interest in second image data  1090 . In some embodiments, the backend server  1030  may first transmit to a second client device  1014 ,  1016  associated with the second A/V recording and communication device  1012 , e.g., via a second hub device, a request to check the second image data  1090  for an entity of interest before searching the second image data  1090 , as further described below. 
       FIG. 50  is a functional block diagram illustrating one embodiment of the first client device(s)  1004 ,  1006  according to various aspects of the present disclosure. As described herein, the first client device(s)  1004 ,  1006  may be configured to facilitate sharing of video footage captured by the first A/V recording and communication device  1002  with a geographic network, e.g., using a share signal  1048 . The first client device(s)  1004 ,  1006  may include a processing module  1100  that is operatively connected to an input interface  1102 , which may include a display  1104 , one or more microphones  1106 , one or more speakers  1108 , and/or a camera  1110 . The processing module  1100  may comprise a processor  1112 , volatile memory  1114 , and non-volatile memory  1116 . The non-volatile memory  1116  may include a client application  1118  that configures the processor  1112  to capture the first image data  1060  using the camera  1110  and the first audio data  1062  using the microphone  1106 . The first client device(s)  1004 ,  1006  may also include a communication module  1120  for network communication with the first A/V recording and communication device  1002  and/or the backend server  1030 . In some embodiments, the first client device(s)  1004 ,  1006  may receive the first image data  1060 , the first audio data  1062 , and or the first text data  1064  from the first A/V recording and communication device(s)  1002 . Further, the first client device(s)  1004 ,  1006  may be configured to receive the first text data  1064  input by a first user, e.g., via the input interface  1102 . For example, the first text data  1064  may be a textual input that describes the first image data  1060  and/or the first audio data  1062 . In various embodiments, the share signal  1048  may include the first image data  1060 , first audio data  1062 , and/or the first text data  1064 , whether captured by the first A/V recording and communication device  1002  or the first client device(s)  1004 ,  1006 . Thus, as used herein, the first image data  1060 , the first audio data  1062 , and/or the first text data  1064  may refer to data originating from the first user, e.g., data transmitted via the first user&#39;s network  1008  to the backend server device  1030 , whether that data is captured by the first A/V recording and communication device  1002 , the first client device  1004 ,  1006 , and/or some other device associated with the first user. Further, the first client device(s)  1004 ,  1006  may transmit the share signal  1048  to the backend server  1030 , where the contents of the share signal may be provided to members of a neighborhood using client devices such as (but not limited to) first client devices  1004 ,  1006  and second client devices  1014 ,  1016 , as further described herein. 
     The first client device  1004 ,  1006 , may also be configured to present one or more user interfaces  1120  to a user, e.g., using the display  1104 . For example, the client application  1118  may be configured to generate and/or present a graphical user interface  1120  that allows a user to share one or more of the first image data  1060 , the first audio data  1062 , and the first text data  1064 . For the example, the user interface  1120  may display the first image data  1060  (e.g., images and/or video footage depicted by the first image data  1060 ) along with a user control, such as a button or selectable icon. User interaction with the user control may cause the client application  1118  to configure the processor  1112  to generate the share signal  1048 , for instance. An additional example user interface  1120  may be configured to display a plurality of comments (described below) generated for association with captured data, and allow a user to select one or more of the comments for sharing with the data, e.g., to other users. Selection of the comment(s) may cause the client application  1118  to configure the processor  1112  to generate an output signal  1122  that transmits the comment selection to the backend server  1030 . In implementations of this disclosure, the display  1104  may include a touchscreen, such that the user of the first client device  1004 ,  1006  may provide inputs directly to the display  1104  (e.g., a request for access to the A/V recording and communication device  1102 ). In some embodiments, the first client device  1004 ,  1006  may not include a touchscreen. In such embodiments, and in embodiments where the second client device  1004 ,  1006  includes the touchscreen, the user may provide an input using any input device, such as, without limitation, a mouse, a trackball, a touchpad, a joystick, a pointing stick, a stylus, buttons, dials, or other controls, microphones, cameras, motion sensors, etc. 
     In further reference to  FIG. 50 , the first client device  1004 ,  1006  may also transmit (e.g., as one or more of the output signals  1122 ) to the backend server  1030  the first text data  1064  that includes a text-based description of an entity of interest, as further described herein. In some embodiments, the backend server  1030  may search for and match second image data  1090  and/or additional image data  1060  to the text-based description, and transmit the matched second image data  1090  and/or additional image data  1060  and a confirmation of entity request signal (e.g., as an output signal  1190 , described below) to the first client device  1004 ,  1006 . In such embodiments, a user of the first client device  1004 ,  1006  may review the matched second image data  1090 , e.g., via a user interface  1120  on the display  1104  and transmit a confirmation of entity acknowledgment signal (e.g., as one of the output signals  1122 ) to the backend server  1030  verifying that the second image data  1090  and/or the additional data  1060  does include the entity of interest as described in the first text data  1064  of the text-based description of the entity of interest, as further described herein. 
       FIG. 51  is a functional block diagram illustrating one embodiment of the second client device(s)  1014 ,  1016  according to various aspects of the present disclosure. In many embodiments, the second client device  1014 ,  1016  may include a processing module  1126  that is operatively connected to an input interface  1128 , which may include a display  1130 , one or more microphones  1132 , one or more speakers  1134 , and/or a camera  1136 . The processing module  1126  may comprise a processor  1138 , volatile memory  1140 , and non-volatile memory  1142 . The non-volatile memory  1142  may include a client application  1144  that configures the processor  1138  to capture the second image data  1090  using the camera  1132  and/or the second audio data  1092  using the microphone(s)  1132 . The second client device  1014 ,  1016  may also include a communication module  1146  for network communication with the second A/V recording and communication device  1012 . For example, in some embodiments, the second client device  1014 ,  1016  may receive the second image data  1090  and the second audio data  1092  from the second A/V recording and communication device  1012  using the communication module  1130 . Thus, as used herein, the second image data  1090 , the second audio data  1092 , and/or the second text data  1094  may refer to data originating from the second user, e.g., data transmitted via or associated with the second user&#39;s network  1018  to the backend server device  1030 , whether that data is captured by the second A/V recording and communication device  1012 , the second client device  1014 ,  1016 , and/or some other device associated with the second user. Further, the second client device  1014 ,  1016  may be configured to receive second text data  1094  provided by a second user that describes the second image data  1090  and/or the second audio data  1092 . In some embodiments, the second client device  1014 ,  1016  may transmit the second image data  1090 , second audio data  1092 , and/or the second text data  1094  to the backend server  1030 . In other embodiments, the second A/V recording and communication device  1012  may directly transmit the second image data  1090 , second audio data  1092 , and/or the second text data  1094  to the backend server  1030  via the output signal  1096 , as described herein. 
     In further reference to  FIG. 51 , the second client device  1014 ,  1016  may receive from the backend server  1030  the first image data  1060  that includes an entity of interest and a second image data access request signal (as one or more input signals  1148 ) that includes a request to check the second image data  1090  for the entity of interest. If the second user grants permission, e.g., via input to a user interface  1150 , then the second client device  1014 ,  1016  may generate and transmit to the backend server  1030  a locate entity command signal (e.g., as one or more output signals  1152 ) in response to the request to check the second image data  1090  for the entity of interest. If the entity of interest is matched in the second image data  1090 , the second client device  1014 ,  1016  may also receive an alert signal (as another of the input signals  1148 ) that includes a notification that the person of interest was matched in the second image data  1090 . In some embodiments, the alert signal may also include a request to share (e.g., as another of the input signals  1148 ) that requests permission to share the second image data  1090  of the matched person of interest with the network of users. In other embodiments, the request to share the second image data may be separate, e.g., a separate signal, from the alert signal. In some embodiments, if the second user grants permission, then the second client device  1014 ,  1016  may generate and transmit an append signal (as another of the output signals  1152 ) that includes a command to append the second image data  1090  of the matched entity of interest onto the shared first image data  1060  of the entity of interest, as further described herein. In some embodiments, if the second user grants permission to share the second image data  1090 , then the second client device  1014 ,  1016  may transmit a second image data share acknowledgment signal (e.g., as another of the output signals  1152 ) that includes a confirmation to share the matched second image data  1090  with the first client device(s)  1004 ,  1006 , and/or the network of users. Although the foregoing embodiments generally describe reviewing, transmitting, receiving, and sharing the first image data  1060  and the second image data  1090 , in implementations of this disclosure, other data may be similarly used. For example, the foregoing operations may pertain to the first audio data  1062 , the first text data  1064 , the second audio data  1092 , the second text data  1094 , and/or other data generated, captured, accessed, and/or sensed by one or more devices associated with the first user or the second user. 
     The second client device  1014 ,  1016 , may also be configured to present the one or more user interfaces  1150  to the second user, e.g., using the display  1130 . For example, the client application  1144  may be configured to generate and/or present a graphical user interface (GUI)  1150  that allows the second user to view or otherwise consume (watch, listen, read, etc.) the first image data  1060 , the first audio data  1062 , and the first text data  1064 . For the example, the user interface  1120  may display the first image data  1060  along with an indication of the entity of interest and a user control, such as a button or selectable icon. User interaction with the user control may cause the client application  1144  to configure the processor  1138  to generate a signal that authorizes the backend server  1030  to access the second data. In implementations of this disclosure, the display  1130  may include a touchscreen, such that the user of the second client device  1014 ,  1016  may provide inputs directly to the display  1130  (e.g., a request for access to the second A/V recording and communication device  1012 ). In some embodiments, the second client device  1014 ,  1016  may not include a touchscreen. In such embodiments, and in embodiments where the second client device  1014 ,  1016  includes the touchscreen, the user may provide an input using any input device, such as, without limitation, a mouse, a trackball, a touchpad, a joystick, a pointing stick, a stylus, buttons, dials, or other controls, microphones, cameras, motion sensors, etc. 
     In reference to  FIGS. 48, 49, 50, and 51 , the image data  1060 ,  1090  may comprise image sensor data such as (but not limited to) exposure values and data regarding pixel values for a particular sized grid. 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. In addition, a communication module, such as the communication modules  1046 ,  1076 ,  1112 ,  1146  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 modules  1046 ,  1076  may comprise (but are not limited to) one or more transceivers configured to transmit and receive wired and/or wireless signals. 
       FIG. 52  is a functional block diagram illustrating one embodiment of a backend server  1030  according to various aspects of the present disclosure. The backend server  1030  may comprise a processing module  1170  comprising a processor  1172 , volatile memory  1174 , a network interface (or communication module)  1119 , and non-volatile memory  1176 . The network interface  1119  may allow the backend server  1030  to access and communicate with devices connected to the network (Internet/PSTN)  1010  (e.g., the A/V recording and communication devices  1002 ,  1012 , the third-party networks  1026 , the client devices  1004 ,  1006 ,  1014 ,  1016 ,  1022 ,  1024 , and the like). The non-volatile memory  1176  may include a server application  1178 , a data analysis module  1182 , and a comment determination module  1184 . 
     In various embodiments, the server application  1178  may configure the processor  1172  to receive and/or retrieve the first image data  1060 , the first audio data  1062 , and/or the first text data  1064 , e.g., from the first A/V recording and communication device  1002 . For example, the backend server  1030  may receive the first image data  1060 , the first audio data  1062 , and/or the first text data  1064  from the first A/V recording and communication device  1002  in response to motion being detected by the A/V recording and communication device  1002 . In addition, the backend server  1030  may configure the processor  1172  to receive the first image data  1060 , the first audio data  1062 , and/or the first text data  1064  from the first client device  1004 ,  1006 . In some examples, the first text data  1064  may be a textual description of an entity of interest and/or the first image data  1060  may be images (e.g., still digital images, live images, video images, etc.) of an entity of interest captured using a camera associated with the first client device  1004 ,  1006 , or image downloaded, uploaded or otherwise obtained by the first client device  1004 ,  1006 . The server application  1178  may also configure the processor  1172  to receive (or retrieve) the second image data  1090 , the second audio data  1092 , and/or the second text data  1094  (e.g., from the second A/V recording and communication device  1012  and/or the second client device  1014 ,  1016 ). In some example embodiments, the server application  1178  may also configure the processor  1172  to receive (or retrieve additional data, e.g., from a third-party, which additional data may include additional image data  1160 , additional audio data  1162 , and/or additional text data  1164 . The server application  1178  may also configure the processor  1172  to receive the share signal  1048 . 
     In example implementations of this disclosure, the data analysis module  1182  may configure the processor  1172  to perform processes for searching for and/or identifying additional instances of an entity of interest, as further described herein. In various embodiments, the share signal  1048  may include the first image data  1060 , the first audio data  1062 , and/or the first text data  1068  received from the first client device  1004 ,  1006  and/or the first A/V recording and communication device  1002 . The share signal  1048  may indicate that the first user believes the data associated with the share signal  1048  may include an entity of interest, which the user would like to share with more users, e.g., in a geographic area. Upon receipt of the share signal  1048  (and associated first data to be shared), the data analysis module  1182  may configure the processor  1172  to identify one or more characteristics or features in the data. For example, without limitation, the processor  1172  of the backend server  1030  may utilize computer vision processing and/or image processing to determine that the first image data  1060  depicts one or more physical features indicative of an entity or object. For example, the first image data  1060  may be analyzed to determine a presence of living objects, e.g., people, animals, or the like, and/or types of inanimate objects, e.g., vehicles, packages, or the like. In some embodiments, to determine the object type, the processor  1172  may compare the first image data  1060  to entity data (not shown), where the entity data includes image data depicting various entities and/or data indicating types of entities. While it may be sufficient to determine an entity type, in some embodiments the data analysis module  1182  may configure the processor  1172  to identify the entity with more specificity. For example, analyzing the first image data  1060  may include determining an identification of a person or a license plate number of a vehicle, e.g., using image processing and/or computer vision processing. 
     By way of further example, the server application  1178  may configure the processor  1172  to analyze the first image data  1060  in order to determine if the first image data  1060  depicts an object. Objects may include, but are not limited to, people, vehicles, streets, curbs, street lines, signs (e.g., street signs, such as parking signs), fire hydrants, driveways, and/or any other type of object that can be depicted by the first image data  1060 . In some examples, the processor  1172  of the backend server  1030  may analyze the first image data  1060  whenever the camera  1040  of the first A/V recording and communication device  1002  is generating the first image data  1060 . In some examples, the camera  1040  of the first A/V recording and communication device  1002  may generate the first image data  1060  based on the first A/V recording and communication device  1002  detecting motion. In some examples, the processor  1172  of the backend server  1030  may analyze the first image data  1060  at given time intervals (e.g., every second, ten seconds, a minute, ten minutes, etc.). Still, in some examples, the processor  1172  of the backend server  1030  may analyze the first image data  1060  based on receiving requests from the first client device  1004 ,  1006 , and/or the hub device  1036 . Moreover, although the backend server  1030  is described as analyzing the first image data  1060 , the second image data  1090 , and/or the additional image data  1160 , the analysis may be carried out by the first A/V recording and communication device  1002 , the first client device  1004 ,  1006 , and/or the hub device  1036 , or a combination of the server and devices. By way of non-limiting example, the first A/V recording and communication device  1002  may do some initial analysis, e.g., to identify an entity in first image data  1060  in the field of view of the first A/V recording and communication device  1002 , but the first image data  1060  may be further processed by the backend server  1030 , e.g., to determine additional attributes of the first image data  1060  and/or to compare the first image data  1060  to the second image data  1090 , the additional image data  1160 , and/or other data. 
     In addition to determining whether the first image data  1060 , the second image data  1090 , and/or the additional image data  1160  contains an object, in any of the present embodiments, the data may be analyzed to determine object data  1196 . In some of the present embodiments, one or more of the image data  1060 ,  1090 ,  1160 , the audio data  1062 ,  1092 ,  1162 , the text data  1064 ,  1094 ,  1164 , and/or motion data may be used to determine the object data  1196 . The computer vision and/or image processing may be executed using computer vision and/or image processing algorithms. Examples of computer vision and/or image processing algorithms may include, without limitation, spatial gesture models that are 3D model-based and/or appearance based. 3D model-based algorithms may include skeletal and volumetric, where volumetric may include NURBS, primitives, and/or super-quadrics, for example. 
     In some embodiments, the processor  1172  of the backend server  1030  (or the processor  1052  of the first A/V recording and communication device  1002 ) may compare the object data  1196  to an object database (not shown) to determine what, if any, object(s) the image data  1196  depicts in the field of view of the A/V recording and communication device  1002  (and/or in the field of view of the camera  1040 ). For example, the object database may store image data corresponding to images and/or video footage that depict various objects, where the image data may be labeled (e.g., tagged, such as in the form of metadata) to indicate an object type (alternatively referred to herein as the “type of object”) depicted by each image and/or video footage. For a first example, the object database may store image data depicting a vehicle, where the image data is labeled to indicate that the type of object includes a vehicle. For a second example, the object database may store image data depicting a street, where the image data is labeled to indicate that the type of object is the street. For a third example, the object database may store image data depicting a curb, where the image data is labeled to indicate the type of object includes the curb. For a fourth example, the object database may store image data depicting a street sign, where the image data is labeled to indicate the type of object includes the street sign. Still, for a fifth example, the object database may store image data depicting a fire hydrant, where the image data is labeled to indicate the type of object includes the fire hydrant. 
     Based on the comparing, the processor  1172  of the backend server  1030  (or the processor  1052  of the first A/V recording and communication device  1002 ) may match the object data  1196  from the first image data  1060  to the image data stored in the object database. The processor  1172  of the backend server  1030  (or the processor  1052  of the first A/V recording and communication device  1002 ) may then use the match to determine that the object data  1196  represents an object and/or to determine the type of object that the object data  1196  represents. For example, if the processor  1172  of the backend server  1030  (or the processor  1052  of the first A/V recording and communication device  1002 ) matches the object data  1096  from the image data  1060  to image data stored in the object database that represents a vehicle, then the processor  1172  of the backend server  1030  (or the processor  1052  of the first A/V recording and communication device  1002 ) may determine that the image data  1060  depicts an object and/or that the image data  1060  depicts a vehicle. In some examples, when the object data  1096  represents multiple objects, the processor  1172  of the backend server  1030  (or the processor  1052  of the first A/V recording and communication device  1002 ) may perform a similar analysis to identify each object represented by the object data  1096  and/or the respective type of object associated with each of the objects represented by the object data  1096 . 
     In some examples, in addition to, or alternatively from, comparing the image data  1060  to the image data stored in the object database, features and/or characteristics of various objects may be stored in the object database, and the features and/or characteristics of the objects in the image data  1060  may be determined (e.g., using computer vision processing, image processing, or the like) and compared against the features and/or characteristics from the object database. For example, sizes, volumes, weights, colors, movement types, and/or other features and/or characteristics of various objects may be stored in the object database. The size, volume, weight, color, movement type, and/or other features and/or characteristics of an object depicted by the image data  1060  may then be compared to the sizes, volumes, weights, colors, movement types, and/or other features and/or characteristics stored in the object database to identify the type of object depicted by the image data  1224 . 
     Similarly, the data analysis module  1182  may configure the processor to analyze the first audio data  1062  and/or the first text data  1068 . For example, the first audio data  1062  may be analyzed to determine a source of the audio, e.g., by comparing an audio signature from the first audio data  1062  with stored audio information. Similarly, in some embodiments, the first text data  1068  may include a text-based description of an entity of interest, and the textual description may be compared with image data or other textual descriptions of entities of interest. Broadly, the data analysis module  1182  may be configured to determine characteristics, features, and/or entities from input data. 
     In some embodiments, based on determining the characteristics, features, and/or entities from input data, the comment determination module  1184  may determine comments  1186  for association with the analyzed data. For example, the comments  1186  may be text- or image-based messages intended to comment on or describe the characteristics, features, and/or entities determined from the input data. In some embodiments, the comments  1186  may include an identification of the determined entity(ies) or characteristic(s). For example, when image data from a video doorbell is analyzed, and determined to include a person, a generated comment  1186  may be “there&#39;s a person at the front door.” Other example comments  1186  for association with image data may include “this dog just entered my yard,” “this person was walking in my driveway,” “this car idled in front of my house for seven minutes,” and the like. As will be appreciated, the comments  1186  may vary in scope and detail, e.g., depending upon the capabilities of the data analysis module  1182  and/or available data. For example, when facial recognition and/or other identification techniques are used, it may be possible to identify a person, and include specific information about the person (e.g., a name) in the comment. Similarly, a specific vehicle may be identified by its license plate number, make and/or model. in addition to features and/or entities determined by analyzing input data, contextual data may also be used to determine one or more comments. By way of non-limiting example, contextual data may include time, location, and/or other data that may not be readily available from the image/audio/text data. In some examples, the contextual data may be determined based on metadata or tags associated with received data and/or by investigating source identifying data  1180 , described further below. For example, the source identifying data  1180  may identify the first A/V recording and communication device  1002 , the hub device  1036 , the first client device  1004 ,  1006 , and/or other components of the security system. Additionally, in some examples, the source identifying data  1180  may be used by the processor  1172  of the backend server  1030  to determine locations of the client devices  1004 ,  1006 , the A/V recording and communication devices  1002 , the hub device  1036 , and/or other sensors of the security system at the site. In still further embodiments, the source identification data  1180  may not be limited to information associated with the first user. By way of non-limiting example, the source identification data  1180  may include information about the second user and/or devices associated with third-parties. 
     To generate the comments  1186 , the comment determination module  1184  may access comment data  1188 , which may include a number of predetermined text- or image-based images. For example, the comment data  1188  may include a number of pre-determined textual phrases or words and image features with which those phrases/words are to be associated. In some examples, the comment data  1188  may include predetermined comments  1186  and one or more scores associated with each comment  1186 . For instance, a score may be determined for each comment  1186 , with comments  1186  above a threshold score or a predetermined number of comments  1186  with the highest scores being chosen for association with the data. For example, the score may be based on a number of times the comment  1186  is used, e.g., transmitted to users and/or selected by users (as described in more detail herein), user-specific criteria, e.g., based on the number of times the user associated with the source of the data has selected the comment  1186 , how relevant the comment is to the image data, e.g., if the comment describes one or more objects and/or characteristics depicted by the image data, or other criteria. 
     To determine the one or more comments, the data analysis module  1182  and/or the comment determination module  1184  may also configure the processor  1172  to consider additional data. For example, the data analysis module  1182  may configure the processor  1172  to compare the input data, e.g., the first image data  1060 , the first audio data  1062 , and/or the first text data  1064  to data from the second A/V recording and communication device  1012 , including but not limited to the second image data  1090 , the second text data  1094 , and/or the second audio data  1092 . In a non-limiting example of this disclosure, the data analysis module  1182  may configure the processor  1172  to analyze the first image data  1060  with the analysis resulting in recognition of a person in the image data. The data analysis module  1182  may then configure the processor  1172  to compare characteristics of the person to the second image data  1090 , e.g., to determine whether the person was also included in the second image data  1090  captured by the second A/V recording and communication device  1012 . Having determined that the person was (or was not) found in the second image data  1090  may inform the comments  1186 . For example, the comment determination module  1184  may determine one or more comments  1186  that indicate that the person in the first image data  1060  was also spotted in the second image data  1090  at a different time (and, in some instances, include in the comment(s) contextual information associated with the second image data  1090 , e.g., a location, time, or the like). 
     In still further embodiments, the data analysis module  1182  may configure the processor  1172  to analyze the input data, e.g., the first image data  1060 , the first audio data  1062 , and/or the first text data  1064  relative to additional data from a third-party. For example, the additional data may include, but is not limited to, the additional image data  1160 , the additional audio data  1162 , and/or the additional text data  1164 . The third party may be any source of information including, but not limited to, third party A/V recording and communication devices, third party client devices, third party databases, and the like. Continuing the example from above, in which a person is detected in the first image data  1060 , portions of the first image data  1060  may be compared to the additional image data  1060  to determine additional information about the person. For example, the person may have been spotted in a different geographic region by the third-party A/V recording and communication device  1020 . Alternatively, the person may be included in a database associated with a law enforcement agency (e.g., the person may be a missing person or a person of interest). Similarly, characteristics of the first image data  1160  may be compared to the additional text data  1064 , e.g., to determine whether the person matches a written description 
     In implementations of this disclosure, the server application  1178  may also configure the processor  1172  to generate output signals  1190  to transmit information, e.g., using the network interface  1119 . For instance, in embodiments discussed in more detail herein, the first image data  1160  may be transmitted via an output signal  1190  to the first client device  1004 ,  1006  along with a plurality of comments  1186 . Similarly, output signals  1190  may generated to transmit data and/or comments to other devices. For example, in some embodiments, the backend server  1030  may also generate output signals  1190  to interact with the first user, e.g., via the first client device  1004 ,  1006 . In one non-limiting example, the backend server  1030  may receive a text-based description of an entity of interest, e.g., as first text data  1064 . In such embodiments, the data analysis module  1180  may configure the processor  1172  to search image data such as (but not limited to) the second image data  1090  and/or the additional image data  1060  for a match of the text-based description of the person of interest. Upon a match, the backend server  1030  may transmit the matched second image data  1090  with a confirmation of entity request, as the output signal  1190 , requesting confirmation from the first user that the matched second image data  1090  includes the entity of interest. The backend server  1030  may receive a confirmation of entity acknowledgment signal (e.g., as an input signal  1192 ) from the first client device(s)  1004 ,  1006  confirming that the matched second image data  1090  and/or the matched additional data  1060  includes the entity of interest. As further described below, in some embodiments, the backend server  1030  may receive the share signal  1048  (which may be one of the input signals  1192 ) with the first image data  1060  that includes an entity of interest. In such embodiments, the backend server  1030  may transmit a second image data access request signal (e.g., as the output signal  1190 ) to the second client device(s)  1014 ,  1016  requesting permission to access the second image data  1090  for the entity of interest found in the first image data  1060 . In some embodiments, the first image data  1060  may be transmitted with the second image data access request signal. If the request is permitted, the backend server  1030  may receive a locate entity command signal (e.g., as one of the input signals  1192 ), as further described below. In addition, if the entity of interest is matched in the second image data  1090  and/or the additional image data  1060 , the backend server  1030  may generate and transmit an alert signal (e.g., as an output signal  1190 ) that includes a notification that the entity of interest was matched in the second image data  1090  and/or the additional image data  1060 . In some embodiments, the backend server  1030  may also send a second image data share request signal (e.g., as an output signal  1190 ) seeking permission to share the matched second image data  1090 . In some embodiments, the backend server  1030  may receive an append signal (e.g., as one of the input signals  1192 ) from the second client device(s)  1014 ,  1016  that includes a command to append the second image data  1090  onto the shared first image data  1060  of the entity of interest, as further described below. In some embodiments, the backend server  1030  may also receive a second image data share acknowledgment signal (e.g., as one of the input signals  1192 ) that includes a confirmation to share the matched second image data  1090  with the first client device(s)  1004 ,  1006  and/or the network of users. In some embodiments, the second image data  1090 , the second audio data  1092 , the second text data  1094 , the additional image data  1060 , the additional audio data  1062 , and/or the additional text data  1064  may be separately stored at the backend databases  1032 , where the backend server  1030  may search and match an entity of interest found in the first image data  1060 , first audio data  1062 , and/or the first text data  1064  by comparing the first image data  1060 , the first audio data  1062 , and/or the text data  1064  to information stored at the databases  1032 , as further described herein. 
     In further reference to  FIG. 52 , and as discussed above, the non-volatile memory  1176  may also include the source identifying data  1180  that may be used to identify, and/or determine locations of, the first A/V recording and communication device  1002 , the second A/V recording and communication device  1012 , and/or the third-party A/V recording and communication device  1020 . In addition, the source identifying data  1180  may be used to identify, and/or determine locations of, the first client device(s)  1004 ,  1006 , the second client device(s)  1014 ,  1016 , and/or the third-party device(s)  1022 ,  1024 . In some embodiments, the server application  1178  may configure the processor  1172  to generate and transmit a report signal (e.g., as the output signal  1190 ) to a third-party client device  1022 ,  1024  and/or a law enforcement agency that includes information indicating an approximate location of where the first image data  1060  was captured and/or where the second image data  1090  was captured, as further described below. 
     In the illustrated embodiment of  FIGS. 48-52 , the various components including (but not limited to) the processing modules  1050 ,  1080 ,  1100 ,  1120 ,  1170 , the communication modules  1046 ,  1076 ,  1112 ,  1146 , and the network interface  1119  are represented by separate boxes. The graphical representations depicted in each of  FIGS. 48-52  are, however, merely examples, and are not intended to indicate that any of the various components of the first A/V recording and communication device  1002 , the second A/V recording and communication device  1012 , the first client device(s)  1004 ,  1006 , the second client device(s)  1014 ,  1016 , or the backend server  1030  are necessarily physically separate from one another, although in some embodiments they might be. In other embodiments, however, the structure and/or functionality of any or all of the components of first A/V recording and communication device  1002  may be combined. In addition, in some embodiments the communication module  1046  may include its own processor, volatile memory, and/or non-volatile memory. Likewise, the structure and/or functionality of any or all of the components of the second A/V recording and communication device  1012  may be combined. In addition, in some embodiments the communication module  1076  may include its own processor, volatile memory, and/or non-volatile memory. In other embodiments, the structure and/or functionality of any or all of the components of first client device  1004 ,  1006  may be combined. In addition, in some embodiments the communication module  1112  may include its own processor, volatile memory, and/or non-volatile memory. Likewise, the structure and/or functionality of any or all of the components of the second client device(s)  1014 ,  1016  may be combined. In addition, in some embodiments the communication module  1146  may include its own processor, volatile memory, and/or non-volatile memory. Further, the structure and/or functionality of any or all of the components of the backend server  1030 , may be combined. In addition, in some embodiments the network interface  1119  may include its own processor, volatile memory, and/or non-volatile memory. 
     Some of the present embodiments may comprise computer vision for one or more aspects. For example, the data analysis module  1182  may use aspects of computer vision for entity and/or feature recognition. Computer vision includes methods for acquiring, processing, analyzing, and understanding images and, in general, high-dimensional data from the real world in order to produce numerical or symbolic information, e.g., in the form of decisions. Computer vision seeks to duplicate the abilities of human vision by electronically perceiving and understanding an image. Understanding in this context means the transformation of visual images (the input of the retina) into descriptions of the world that may interface with other thought processes and elicit appropriate action. This image understanding may be seen as the disentangling of symbolic information from image data using models constructed with the aid of geometry, physics, statistics, and learning theory. Computer vision has also been described as the enterprise of automating and integrating a wide range of processes and representations for vision perception. As a scientific discipline, computer vision is concerned with the theory behind artificial systems that extract information from images. The image data may take many forms, such as video sequences, views from multiple cameras, or multi-dimensional data from a scanner. As a technological discipline, computer vision seeks to apply its theories and models for the construction of computer vision systems. 
     One aspect of computer vision comprises determining whether or not the image data contains some specific object, feature, or activity. Different varieties of computer vision recognition include: Object Recognition (also called object classification)—One or several pre-specified or learned objects or object classes may be recognized, usually together with their 2D positions in the image or 3D poses in the scene. Identification—An individual instance of an object is recognized. Examples include identification of a specific person&#39;s face or fingerprint, identification of handwritten digits, or identification of a specific vehicle. Detection—The image data are scanned for a specific condition. Examples include detection of possible abnormal cells or tissues in medical images or detection of a vehicle in an automatic road toll system. Detection based on relatively simple and fast computations is sometimes used for finding smaller regions of interesting image data that may be further analyzed by more computationally demanding techniques to produce a correct interpretation. 
     Several specialized tasks based on computer vision recognition exist, such as: Optical Character Recognition (OCR)—Identifying characters in images of printed or handwritten text, usually with a view to encoding the text in a format more amenable to editing or indexing (e.g., ASCII). 2D Code Reading—Reading of 2D codes such as data matrix and QR codes. Facial Recognition. Shape Recognition Technology (SRT)—Differentiating human beings (e.g., head and shoulder patterns) from objects. 
     Typical functions and components (e.g., hardware) found in many computer vision systems are described in the following paragraphs. The present embodiments may include at least some of these aspects. For example, embodiments of the present A/V recording and communication devices  1002  may include a computer vision module. The computer vision module may include any of the components (e.g., hardware) and/or functionality described herein with respect to computer vision, including, without limitation, one or more cameras, sensors, and/or processors. In some of the present embodiments, a microphone  524 , a camera  316 , and/or an imager may be components of the computer vision module. 
     Image acquisition—A digital image is produced by one or several image sensors, which, besides various types of light-sensitive cameras, may include range sensors, tomography devices, radar, ultra-sonic cameras, etc. Depending on the type of sensor, the resulting image data may be a 2D image, a 3D volume, or an image sequence. The pixel values may correspond to light intensity in one or several spectral bands (gray images or color images), but may also be related to various physical measures, such as depth, absorption or reflectance of sonic or electromagnetic waves, or nuclear magnetic resonance. 
     Pre-processing—Before a computer vision method may be applied to image data in order to extract some specific piece of information, it is usually beneficial to process the data in order to assure that it satisfies certain assumptions implied by the method. Examples of pre-processing include, but are not limited to re-sampling in order to assure that the image coordinate system is correct, noise reduction in order to assure that sensor noise does not introduce false information, contrast enhancement to assure that relevant information may be detected, and scale space representation to enhance image structures at locally appropriate scales. 
     Feature extraction—Image features at various levels of complexity are extracted from the image data. Typical examples of such features are: Lines, edges, and ridges; Localized interest points such as corners, blobs, or points; More complex features may be related to texture, shape, or motion. 
     Detection/segmentation—At some point in the processing a decision may be made about which image points or regions of the image are relevant for further processing. Examples are: Selection of a specific set of interest points; Segmentation of one or multiple image regions that contain a specific object of interest; Segmentation of the image into nested scene architecture comprising foreground, object groups, single objects, or salient object parts (also referred to as spatial-taxon scene hierarchy). 
     High-level processing—At this step, the input may be a small set of data, for example a set of points or an image region that is assumed to contain a specific object. The remaining processing may comprise, for example: Verification that the data satisfy model-based and application-specific assumptions; Estimation of application-specific parameters, such as object pose or object size; Image recognition—classifying a detected object into different categories; Image registration—comparing and combining two different views of the same object. 
     Decision making—Making the final decision required for the application, for example match/no-match in recognition applications. 
     One or more of the present embodiments may include a vision processing unit (not shown separately, but may be a component of the computer vision module  552 ). A vision processing unit is an emerging class of microprocessor; it is a specific type of AI (artificial intelligence) accelerator designed to accelerate machine vision tasks. Vision processing units are distinct from video processing units (which are specialized for video encoding and decoding) in their suitability for running machine vision algorithms such as convolutional neural networks, SIFT, etc. Vision processing units may include direct interfaces to take data from cameras (bypassing any off-chip buffers), and may have a greater emphasis on on-chip dataflow between many parallel execution units with scratchpad memory, like a manycore DSP (digital signal processor). But, like video processing units, vision processing units may have a focus on low precision fixed-point arithmetic for image processing. 
     Some of the present embodiments may use facial recognition hardware and/or software, as a part of the computer vision system. Various types of facial recognition exist, some or all of which may be used in the present embodiments. 
     Some face recognition identify facial features by extracting landmarks, or features, from an image of the subject&#39;s face. For example, an algorithm may analyze the relative position, size, and/or shape of the eyes, nose, cheekbones, and jaw. These features are then used to search for other images with matching features. Other algorithms p a gallery of face images and then compress the face data, only saving the data in the image that is useful for face recognition. A probe image is then compared with the face data. One of the earliest successful systems is based on template matching techniques applied to a set of salient facial features, providing a sort of compressed face representation. 
     Recognition algorithms may be divided into two main approaches, geometric, which looks at distinguishing features, or photometric, which is a statistical approach that distills an image into values and compares the values with templates to eliminate variances. 
     Popular recognition algorithms include principal component analysis using eigenfaces, linear discriminant analysis, elastic bunch graph matching using the Fisherface algorithm, the hidden Markov model, the multilinear subspace learning using tensor representation, and the neuronal motivated dynamic link matching. 
     Further, a newly emerging trend, claimed to achieve improved accuracy, is three-dimensional face recognition. This technique uses 3D sensors to capture information about the shape of a face. This information is then used to identify distinctive features on the surface of a face, such as the contour of the eye sockets, nose, and chin. 
     One advantage of 3D face recognition is that it is not affected by changes in lighting like other techniques. It may also identify a face from a range of viewing angles, including a profile view. Three-dimensional data points from a face vastly improve the precision of face recognition. 3D research is enhanced by the development of sophisticated sensors that do a better job of capturing 3D face imagery. The sensors work by projecting structured light onto the face. Up to a dozen or more of these image sensors may be placed on the same CMOS chip—each sensor captures a different part of the spectrum. 
     Another variation is to capture a 3D picture by using three tracking cameras that point at different angles; one camera pointing at the front of the subject, a second one to the side, and a third one at an angle. All these cameras work together to track a subject&#39;s face in real time and be able to face detect and recognize. 
     Another emerging trend uses the visual details of the skin, as captured in standard digital or scanned images. This technique, called skin texture analysis, turns the unique lines, patterns, and spots apparent in a person&#39;s skin into a mathematical space. 
     Another form of taking input data for face recognition is by using thermal cameras, which may only detect the shape of the head and ignore the subject accessories such as glasses, hats, or make up. 
     Further examples of automatic identification and data capture (AIDC) and/or computer vision that may be used in the present embodiments to verify the identity and/or authorization of a person include, without limitation, biometrics. Biometrics refers to metrics related to human characteristics. Biometrics authentication (or realistic authentication) is used in various forms of identification and access control. Biometric identifiers are the distinctive, measurable characteristics used to label and describe individuals. Biometric identifiers may be physiological characteristics and/or behavioral characteristics. Physiological characteristics may be related to the shape of the body. Examples include, but are not limited to, fingerprints, palm veins, facial recognition, three-dimensional facial recognition, skin texture analysis, DNA, palm prints, hand geometry, iris recognition, retina recognition, and odor/scent recognition. Behavioral characteristics may be related to the pattern of behavior of a person, including, but not limited to, typing rhythm, gait, and voice recognition. 
     The present embodiments may use any one, or any combination of more than one, of the foregoing biometrics to identify and/or authenticate a person who is either suspicious or who is authorized to take certain actions with respect to a property or expensive item of collateral. 
       FIG. 53  is a flowchart illustrating an embodiment of a process  1300  for searching second image data for a match of a person of interest provided in first image data according to various aspects of the present disclosure. In some embodiments, a first client device(s)  1004 ,  1006 , may transmit a share signal  1048  that includes first image data  1060  to the backend server  1030 , where the first image data  1060  may include images of a person of interest. In various embodiments, the first image data  1060  may be captured by a first A/V recording and communication device  1002  or by the first client device(s)  1004 ,  1006 , as described above. Further, a second A/V recording and communication  1012  and/or second client device(s)  1014 ,  1016  may capture second image data  1090  and transmit the second image data  1090  to the backend server  1030 . As further described below, the second image data  1090  may be searched for a match of the person of interest. 
     In reference to  FIG. 53 , the process  1300  may include the backend server  1030  receiving (block B 1302 ), from a first client device  1004 ,  1006 , a share signal  1048  including first image data  1060  captured by a camera  1040  of the first A/V recording and communication device  1002 , the first image data including a person of interest, as described above. In some embodiments, the share signal  1048  may include first audio data  1062  captured by a microphone  1042  of the first A/V recording and communication device  1002  associated with the first client device  1004 ,  1006 . Further, the share signal  1048  may also include first text data  1064  that describes the first image data  1060  and/or the first audio data  1062 . For example, the first text data  1064  may describe that the person of interest has committed a criminal act or is behaving suspiciously, as depicted in the first image data  1060  and/or the first audio data  1062 . In alternative embodiments, and as described above, the share signal  1048  may include the first audio data  1062  and/or the first text data  1064  without the first image data  1060 . In addition, the share signal may also include a command to share the first image data  1060  (and/or the first audio data  1062  and/or the text data  1064 ) with a network of users. For example, the share signal  1048  may comprise a neighborhood alert that notifies other users of a possible danger posed by the person of interest. 
     The process  1300  may also include receiving (block B 1304 ) second image data  1090  captured by a camera  1070  of the second A/V recording and communication device  1012 , as described above. Further, in some embodiments, the backend server  1030  may receive second audio data  1092  captured by a microphone  1072  of the second A/V recording and communication device  1012  and/or second text data  1094  that describes the second image data  1090  and/or the second audio data  1092 . In many embodiments, the second image data  1090  may be received (block B 1304 ) before receiving (block B 1302 ) the share signal  1048 , and stored in either a database(s)  1032  and/or in the non-volatile memory  1176  storage of the backend server  1030  where it may be searched upon receiving the share signal  1048 . Upon receiving the share signal  1048 , the process  1300  may further include transmitting (block B 1306 ) a request, to the second client device(s)  1014 ,  1016  using a second image data access request signal, to check the second image data  1090  for the person of interest. In some embodiments, the backend server  1030  may also transmit the first image data  1060  that includes the person of interest along with the request to check the second image data for the person of interest. For example, one or more second users may receive on their second client device(s)  1014 ,  1016  a video shared by a first user that includes a request to check second image data  1090  captured by their respective second A/V recording and communication device  1012 . If the second user grants permission, then the process  1300  may include receiving (block B 1308 ), from the second client device(s)  1014 ,  1016 , a locate person command signal, in response to the request to check the second image data  1090  for the person of interest. In some embodiments, a second user may choose to grant permission for access in advance for future share signals  1048  that may include a person of interest. In such embodiments, the backend server  1030  may receive an automatic locate command signal, and in response activate a setting for automatically identifying a further person of interest and searching the second image data  1090  each time a new share signal  1048  is received including the further person of interest. 
     In further reference to  FIG. 53 , the process  1300  may include searching (block B 1310 ) the second image data  1090  for a match (block B 1312 ) of the person of interest in the first image data  1060 . In many embodiments, the search (block B 1310 ) of the second image data  1090  for a match (block B 1312 ) of the person of interest in the first image data  1060  may be automated using various imaging processing techniques and/or machine learning processes. For example, in some embodiments, searching (block B 1310 ) the second image data  1090  for the match (block B 1312 ) of the person of interest may be performed using facial recognition processes, color matching schemes, and/or using a body build score. In some embodiments, a match (block B 1312 ) of the person of interest in the second image data  1090  may be confirmed by a human operator. In addition, searching (block B 1310 ) the second image data  1090  for the match (block B 1314 ) of the person of interest may be restricted to a subset of the second image data  1090 , such as a subset of the second image data captured during a predetermined length of time before and/or the capture of the first image data  1060  that includes the person of interest. In many embodiments, when a match (block B 1312 ) of the person of interest is not found, the process  1300  may include continuing to search (block B 1310 ) the second image data  1090 . If, after continued searching of the second image data  1090  at block B 1310 , no match of the person of interest is found, the process  1300  may return a notification to the second client device(s)  1014 ,  1016 , wherein the notification indicates that no match of the person of interest was found. However, when a match (block B 1312 ) of the person of interest is found in the second image data  1090 , then process  1300  may include generating and transmitting (block B 1314 ) an alert signal to the second client device(s)  1014 ,  1016 , wherein the alert signal includes a notification that the person of interest was matched in the second image data  1090 . 
       FIG. 54  is a flowchart illustrating another embodiment of a process  1350  for searching second image data for a match of a person of interest provided in first image data according to various aspects of the present disclosure. In many embodiments, the process  1350  may continue from block B 1314  of process  1300 , as described above with respect to  FIG. 53 . In some embodiments, the alert signal that is transmitted to the second client device(s)  1014 ,  1016  may include the second image data  1090  of the matched person of interest. Further, the alert signal may include a request for permission to share the second image data  1090  of the matched person of interest with the network of users or the request for permission to share the second image data  1090  may be transmitted to the second client device(s)  1014 ,  1016  using a second image data share request signal. If permission is granted by the second user, the process  1350  may include receiving (block B 1352 ) an append signal, from the second client device(s)  1014 ,  1016 , wherein the append signal includes a command to append the second image data  1090  of the matched person of interest onto the shared first image data  1060  of the person of interest. The process  1350  may also include transmitting (block B 1354 ) the first image data  1060  and the second image data  1090  of the matched person of interest to the network of users. By including the second image data  1090  of the matched person of interest, the person of interest captured in the first image data  1060  may be tracked and his or her whereabouts and actions captured for various users to increase neighborhood safety. 
       FIG. 55  is a flowchart illustrating an embodiment of a process  1400  for searching image data for a match of a person of interest provided in a text-based description according to various aspects of the present disclosure. In some embodiments, a first client device(s)  1004 ,  1006 , may transmit a share signal  1048  that includes first text data  1064  to the backend server  1030 , where the first text data  1064  may include a text-based description of a person of interest. In various embodiments, the first text data  1064  may be provided by a first user using the first client device(s)  1004 ,  1006  that may be associated with the first A/V recording and communication device  1002 , as described above. Further, as described above, a second A/V recording and communication  1012  and/or second client device(s)  1014 ,  1016  may capture second image data  1090  and transmit the second image data  1090  to the backend server  1030 . In many embodiments, the first user may not have first image data  1060  and/or first audio data  1062  of the person of interest. Thus, the text-based description may be used to search image data captured by various other users for a match of the person of interest, as further described below. 
     In reference to  FIG. 55 , the process  1400  may include receiving (block B 1402 ), at the backend server  1030 , a text-based description (may also be referred to as “first text data  1064 ”) of a person of interest from a first client device(s)  1004 ,  1006 . The process  1400  may also include receiving (block B 1404 ), from an A/V recording and communication device such as (but not limited to) the second A/V recording and communication device  1012 , image data such as (but not limited to) second image data  1090  captured by a camera  1070  of the second A/V recording and communication device  1012 , as described above. Further, in some embodiments, the backend server  1030  may also receive second audio data  1092  captured by a microphone  1072  of the second A/V recording and communication device  1012  and/or second text data  1094  that describes the second image data  1090  and/or the second audio data  1092 . In many embodiments, the second image data  1090 , second audio data  1092 , and/or second text data  1094 , may be received (block B 1404 ) before receiving (block B 1402 ) the text-based description of the person of interest, and stored in either a database(s)  1032  and/or in the non-volatile memory  1176  storage of the backend server  1030  where it may be searched upon receiving the first text data  1064 . The process  1400  may further include searching (block B 1406 ) the second image data  1090  for a match of the text-based description of the person of interest. In some embodiments, the searching (block B 1406 ) the second image data  1090  for a match of the text-based description of the person of interest may be performed using natural language processing. In some embodiments, the searching (block B 1406 ) the second image data  1090  for a match of the text-based description of the person of interest may be performed by comparing a text-based description of the second image data  1090  with the received text-based description of the person of interest. If a match (block B 1408 ) of the person of interest is not found, then the process  1400  may continue to search (block B 1406 ) the second image data  1090 . If, after continued searching of the second image data  1090  at block B 1408 , no match of the person of interest is found, the process  1400  may return a notification to the second client device(s)  1014 ,  1016 , wherein the notification indicates that no match of the person of interest was found. However, if a match (block B 1408 ) is found, then the process  1400  may include transmitting (block B 1410 ), from the backend server  1030  to a second client device(s)  1014 ,  1016 , associated with the second A/V recording and communication device  1012 , the matched second image data  1090  and a request to confirm that the matched second image data  1090  includes the person of interest using a confirmation of person request signal. In some embodiments, the backed server  1030  may also send the text based-description along with the matched second image data  1090  and the confirmation of person request signal. Further, the process  1400  may include receiving (block B 1412 ) a confirmation of person acknowledgment signal, from the second client device(s)  1014 ,  1016 , confirming that the matched second image data  1090  includes the person of interest. In some embodiments, the process  1400  may include transmitting, to the first client device(s)  1004 ,  1006 , the matched second image data  1090  and a request to confirm that the matched second image data  1090  includes the person of interest. In such embodiments, the process  1400  may further include receiving, from the first client device(s)  1004 ,  1006 , a confirmation that the matched second image data  1090  includes the person of interest. 
       FIG. 56  is a flowchart illustrating another embodiment of a process  1450  for searching image data for a match of a person of interest provided in a text-based description according to various aspects of the present disclosure. In many embodiments, the process  1450  may continue from block B 1412  of process  1400 , as described above with respect to  FIG. 55 . In various embodiments, the process  1450  may include transmitting (block B 1452 ), from the backend server  1030  to the second client device(s)  1014 ,  1016 , a second image data share request signal. In some embodiments, the second image data share request signal may include a request to share the matched second image data  1090  with a first user associated with the first client device(s)  1004 ,  1006  and/or a network of users. The process  1450  may also include receiving (block B 1454 ), from the second client device(s)  1014 ,  1016 , a second image data share acknowledgment signal that includes confirmation to share the matched second image data  1090  with the first client device(s)  1004 ,  1006  and/or the network of users. In addition, the process  1450  may include transmitting (block B 1456 ) the matched second image data  1090  to the network of users. 
       FIG. 57  is a flowchart illustrating an embodiment of a process  5700  for augmenting and sharing data from A/V recording and communication devices and client devices. With reference to  FIG. 57 , the process  5700 , at block B 5702 , receives first data. For example, the processor  1172  of the backend server  1030  may receive, using the communication module  1119 , the first image data  1060 , the first audio data  1062 , and/or the first text data  1064  from the first A/V recording and communication device  1002  and/or the first client device  1004 ,  1006 . In example implementations, the data may be received in connection with receipt of the share signal  1048 , which may be generated in response to a first user inputting a request to share the first data. In other implementations, the first A/V recording and communication device  1002  may detect motion of an entity, such as a person, animal, or other moving object, that is in the field of view of a sensor (in embodiments where the first A/V recording and communication device  1002  includes a motion sensor). 
     The process  5700 , at block B 5704 , analyzes the first data to determine one or more characteristics of the first data. For example, the processor  1172  of the backend server  1030  may be configured by the data analysis module  1182  to analyze the first image data  1160  using, for example, image processing and/or computer visions processing, to determine that the first image data  1160  depicts an entity. When the first data includes the first audio data  1062 , the processor  1172  of the backend server  1030  may use audio processing techniques, including but not limited to natural language processing, voice identification techniques, speech to text processing, or the like to determine an entity of interest and/or characteristics. Additionally, when the first data includes the first text data  1064 , the processor  1172  of the backend server  1030  may use natural language processing and/or other text-based analyses to determine an entity of interest and/or characteristics. In some example implementations, the data analysis module  1182  may configure the processor  1172  of the backend server  1030  to compare the first data to other data, e.g., to compare aspects of the first data to recognize the characteristics. For instance, the data analysis module  1182  may configure the processor  1172  of the backend server  1030  to compare the first image data  1060  to an entity database storing images of various entities, e.g., people, animals, vehicles. Based on this comparison, the data analysis module  1182  may configure the processor  1172  of the backend server  1030  to determine that the first image data  1062  includes an entity of interest. 
     The process  5700 , at block B 5706 , determines one or more textual messages for association with the first data. For example, the comment determination module  1184  may configure the processor  1172  of the backend server  1030  to determine one or more comments  1186  that describe or otherwise relate to the first data. In some embodiments, when the first data is analyzed to determine a person, the comments  1186  may include an identity of the person, a description of an activity being undertaken by the person, or the like. When the first data is analyzed to determine characteristics of a vehicle, the comments  1186  may include a description of the vehicle, identifying characteristics of the vehicle, and the like. Moreover, the comments  1186  may include contextual data, such as the location at which the entity of interest was detected, the time at which the entity of interest was detected, and/or the like. For example, contextual data may be determined based on the source identification data  1180 , based on metadata or other data included with the first data, and/or based on other data. 
     At block B 5706 , a plurality of different comments  1186  may be determined for the same data. For example, the comment determination module  1184  may configure the processor  1172  of the backend server  1030  to select the one or more comments  1186  from predetermined comments, which may be stored in a database. For example, the database may store comments  1186  in relation to certain entity types. For example, the database may include a plurality of comments associated with a generic person, vehicle, animal or entity, and/or a plurality of comments associated with a specific animal, e.g., a coyote, a specific person, e.g., a person previously identified, and/or a specific vehicle, e.g., a make/model and/or license plate. In examples, the comment determination module  1184 , having determined a person in the first image data, may access comments in the database relative to the detection of the person. The comments  1186  may be relatively generic, e.g., “This person was spotted,” or more specific, e.g., “John Doe was outside my front door at 4:15 this afternoon.” As will be appreciated, the specificity of the comments  1186  may be dependent upon information available. In the foregoing example, both the comments  1186  “this person was spotted” and “John Doe was outside my front door at 4:15 this afternoon” are descriptive of the same first image data  1060  and thus, both may be determined at block B 5706 . In some implementations, it may be desirable to determine a predetermined number of comments (e.g., two or three) for association with the first data. When more than that number are available, the comment determination module  1184  may configure the processor  1172  of the backend server  1030  to select a subset of a larger number of applicable comments  1186 . For example, each of the comments  1186  in a larger set may be scored, with the comments  1186  having the highest scores and/or scores above a threshold score being determined at block B 5706 . For example, the scores may be determined based on their specificity (e.g., with more specific comments being more highly scored), based on their preference to users (e.g., with comments that have been shared more frequently by users in the network and/or the first user being more highly scored), and/or based on other criteria. 
     The process  5700 , at block B 5708 , transmits the first data and the textual message(s) to a first client device associated with the source of the first data. For example, the server application  1178  may configure the processor  1172  of the backend server  1030  to generate an output signal  1190  that includes the first image data  1060 , the first audio data  1062 , and/or the first text data  1064 . The server application  1178  may then configure the processor of the backend server to transmit, using the communication module  1119 , the output signal  1190  to the first client device  1004 ,  1006  along with the determined comments  1186 . In some examples, the output signal  1190  may configure the first client device  1004 ,  1006  to display a user interface  1120  that includes a rendering of the first data and the comments. 
     The process  5700 , at block  5710 , receives consent for sharing the image data, the consent including a selection of one of the textual message(s). For example, the processor  1172  of the backend server  1030  may receive, using the communication module  1119 , an input signal  1192  that includes a selection of one of the comments  1186  and authorizes the backend server  1030  to share the first data with the network of users together with the selected comment  1186 . As noted above, the first client device  1004 ,  1006 , may be configured to display a user interface  1120  that includes a rendering of the first data and the comments  1186 . The user interface  1120  may prompt and/or enable the first user to select one (or more) of the suggested comments  1186 . Selection of the comment(s)  1186  may cause the processor  1112  of the first client device  1004 ,  1006 , to generate and transmit an output signal  1112  that authorizes the sharing of the first data and the comment  1186 . In other implementations, the user interface  1120  may provide separate prompts for selecting a comment  1186  and authorizing sharing of the first data with the selected comment  1186 . In some implementations, the user interface  1120  may further prompt the user to input text or other data for association with the first data, e.g., in addition to or instead of the suggested comment(s)  1186 . 
     The process  5700 , at block  5712 , shares the first data and the textual message(s). For example, the processor  1172  of the backend server  1030  may upload, using the communication module  1119 , the first image data  1060 , the first audio data  1062 , and/or the first text data  1064  and the selected comment(s)  1186  to a storage device. For example, the storage device may be accessible by other network users and/or third parties. In other example embodiments, the processor  1172  of the backend server  1030  may transmit, using the communication module  1119 , the first image data  1060 , the first audio data  1062 , and/or the first text data  1064  and the selected comment(s) to a client device associated with other users of the network and/or to client device(s) associated with one or more third parties. 
     According to the foregoing example process  5700 , the captured or provided data may be enhanced based on the inclusion of one or more user-comments. The process  5700  of  FIG. 57  may be implemented in a variety of embodiments, including those discussed above. However, the below-detailed embodiments are not intended to be limiting, and are provided merely as example embodiments of the present disclosure. Other embodiments similar to those outlined herein may also fall within the scope of the present disclosure. 
     For example, and with reference to  FIGS. 48-52 , an unexpected guest may be recorded by the first A/V recording and communication device  1002 . In response, the backend server  1030  (and/or the hub device  1036 ) may receive the first image data  1060  recorded by the camera  1040  of the first A/V recording and communication device  1002  (at block B 5702 ). The backend server  1030  may then analyze the first image data  1060  using one or more of image processing and/or computer vision processing (e.g., to determine that the image data  1224  depicts the unexpected guest) (at block B 5704 ). For example, based on the analysis, the backend server  1030  may determine that the first image data  1060  depicts the unexpected guest. Based on determining that the first image data  1060  depicts the unexpected guest, the backend server  1030  may determine comments for association with the first image data (at block B 5706 ). For example, based on an analysis of the image data, the comment determination module  1184  may determine comments such as, “unexpected visitor,” “this person was spotted at my front door,” and “this delivery person was here.” Each of these comments may be determined to describe the first image data (at block B 5706 ) and may be transmitted along with the first image data  1060  to the first client device  1004 ,  1006  (at block B 5708 ). The first client device  1004 ,  1006  may then present the first image data  1060  and the three comments  1186 , and the user may select one or more of the three comments  1186 . This selection may constitute consent to share the first image data  1060  along with the selected comment(s)  1186 , which consent is received by the backend server  1030  (at block B 5710 ). Having received the consent, the backend server  1030  may then share the first image data  1060  and the comment(s)  1186  with a network of users (at block  5712 ), e.g., by making the first image data  1060  and the comment(s)  1186  accessible to the users of the network. 
       FIG. 58  is a flowchart illustrating an embodiment of another process  5800  for augmenting and sharing data from A/V recording and communication devices and client devices. With reference to  FIG. 58 , the process  5800 , at block B 5802  receives first data including image data generated by a camera of an A/V recording and communication device. For example, the processor  1172  of the backend server  1030  may receive, using the communication module  1119 , the first image data  1060  from the first A/V recording and communication device  1002  (which may be via the hub device  1036 ). In example implementations, the data may be received in connection with receipt of the share signal  1048 , which may be generated in response to a first user inputting a request to share the first data. In other implementations, the first A/V recording and communication device  1002  may detect motion of an entity, such as a person, animal, or other moving object, that is in the field of view of a sensor (in embodiments where the first A/V recording and communication device  1002  includes a motion sensor), and this detection of motion may cause the first A/V recording and communication device  1002  to transmit first data including the first image data  1060  to the backend server  1030 . 
     The process  5800 , at block B 5804 , analyzes the first data to determine one or more characteristics of the first data. For example, the processor  1172  of the backend server  1030  may be configured by the data analysis module  1182  to analyze the first image data  1060  using, for example, image processing and/or computer vision processing, to determine that the first image data  10600  depicts an entity. When the first data includes the first audio data  1062 , the processor  1172  of the backend server  1030  may use audio processing techniques, including but not limited to natural language processing, voice identification techniques, speech to text processing, or the like, and when the first data includes the first text data  1064 , the processor  1172  of the backend server  1030  may use natural language processing and/or other text-based analyses, to determine an entity of interest and/or characteristics. In some example implementations, the data analysis module  1182  may configure the processor  1172  of the backend server  1030  to compare the first data to other data, e.g., to compare aspects of the first data to recognize the characteristics. For instance, the data analysis module  1182  may configure the processor  1172  of the backend server  1030  to compare the first image data  1060  to an entity database storing images of various entities, e.g., people, animals, vehicles. Based on this comparison, the data analysis module  1182  may configure the processor  1172  of the backend server  1030  to determine that the first image data  1062  includes an entity of interest. 
     The process  5800 , at block  5806 , receives second data. For example, the processor  1172  of the backend server  1030  may be configured to receive second data, which may include the second image data  1090 , the second audio data  1092 , the second text data  1094 , the additional image data  1160 , the additional audio data  1162 , the additional text data  1194 , and/or other data. In some example implementations, the processor  1172  of the backend server  1030  may generate one or more request signals (e.g., as output signals  1190 ) for transmission to the second user and/or a third party to request the second data. For example, the request may include the first data, and indicate that the backend server  1030  would like to access the second data to determine whether one or more characteristics of the first image data (e.g., determined at block B 5804 ) are present in the second data. 
     The process  5800 , at block B 5808 , analyzes the second data. For example, the processor  1172  of the backend server  1030  may be configured by the data analysis module  1182  to analyze the second image data  1090  using, for example, image processing and/or computer vision processing, to determine that the second image data  1090  depicts the entity and/or characteristic(s) identified by analyzing the first image data  1060 . As noted above, the second data may be data from the second A/V recording and communication device  1012 , such as the second image data  1090 , which facilitates a search for instances of the entity in the geographic area, e.g., in the neighborhood. Alternatively, and/or additionally, the second data may be obtained from a third-party, such as the additional image data  1160 , which may be a missing persons directory or a criminal database, for example. 
     The process  5800 , at block  5810 , determines whether the second data includes the one or more characteristics. For example, and as noted above, the processor  1172  of the backend server  1030  may be configured by the data analysis module  1182  to determine whether the entity identified in the first image data  1060  has been identified in any other data. In some examples, the entity identified in the first image data may not be identified in second data, in which case the backend server  1030  may continue to search additional data sources (e.g., by requesting information from different A/V recording and communication devices) for matches. 
     The process  5800 , at block B 5812 , determines one or more textual messages for association with the first data. For example, the comment determination module  1184  may configure the processor  1172  of the backend server  1030  to determine one or more comments  1186  that describe or otherwise relate to the first data. In some embodiments, when the first data is analyzed to determine a person, the comments  1186  may include an identity of the person, a description of an activity being undertaken by the person, or the like. When the first data is analyzed to determine characteristics of a vehicle, the comments  1186  may include a description of the vehicle, identifying characteristics of the vehicle, and the like. Moreover, the comments  1186  may include contextual data, such as the location at which the entity of interest was detected, the time at which the entity of interest was detected, and/or the like. For example, contextual data may be determined based on the source identification data  1180 , based on metadata or other data included with the first data, and/or based on other data. Moreover, because the entity may have been identified by other data, e.g., the second image data  1090  and/or additional image data  1160 , at block B 5810 , the comment may include information about the additional instances. For instance, other dates, times, locations, and the like, may be incorporated into the comments  1186 . 
     At block B 5812 , a plurality of different comments  1186  may be determined for the same data. For example, the comment determination module  1184  may configure the processor  1172  of the backend server  1030  to select the one or more comments  1186  from predetermined comments, which may be stored in a database. For example, the database may store comments  1186  in relation to certain entity types. For example, the database may include a plurality of comments associated with a generic person, vehicle, animal or entity, and/or a plurality of comments associated with a specific animal, e.g., a coyote, a specific person, e.g., a person previously identified, and/or a specific vehicle, e.g., a make/model and/or license plate. In examples, the comment determination module  1184 , having determined a person in the first image data, may access comments in the database relative to the detection of the person. The comments may be relatively generic, e.g., “This person was spotted,” or more specific, e.g., “John Doe was outside my front door at 4:15 this afternoon and was outside the Flanders&#39;s house at 3:12 this morning.” As will be appreciated, the specificity of the comments  1186  may be dependent upon information available. In the foregoing example, both the comments “this person was spotted” and “John Doe was outside my front door at 4:15 this afternoon and was outside the Flanders&#39;s house at 3:12 this morning” are descriptive of the same first image data  1060  and thus, both may be determined at B 5706 . As will also be appreciated, the latter comment includes information gleaned from investigating the second image data  1090 , in addition to the first image data  1060 . In some implementations, it may be desirable to determine a predetermined number of comments (e.g., two or three) for association with the first data. When more than that number are available, the comment determination module  1184  may configure the processor  1172  of the backend server  1030  to select a subset of a larger number of applicable comments  1186 . For example, each of the comments  1186  in a larger set may be scored, with the comments  1186  having the highest scores and/or scores above a threshold score being determined at block B 5706 . For example, the scores may be determined based on their specificity (e.g., with more specific comments being more highly scored), based on their preference to users (e.g., with comments that have been shared more frequently by users in the network and/or the first user being more highly scored), and/or based on other criteria. 
     The process  5800 , at block B 5814 , transmits the first data and the textual message(s) to a first client device associated with the first A/V recording and communication device. For example, the server application  1178  may configure the processor  1172  of the backend server  1030  to generate at output signal  1190  that includes at least the first image data  1060  (and/or the determined comments  1186 ). The server application  1178  may then configure the processor  1172  of the backend server  1030  to transmit, using the communication module  1119 , the output signal  1190  along with the determined comments  1186  to the first client device  1004 ,  1006 . In some examples, the output signal  1190  may configure the first client device  1004 ,  1006  to display a user interface  1120  that includes a rendering of the first image data  1060  and the comments  1186 . In some instances, the second image data  1090  and/or the additional image data  1160  that informed the comments  1186 , e.g., matched during analysis of the second data, may also be transmitted to the first client device  1004 ,  1006 . 
     The process  5800 , at block B 5816 , receives consent for sharing the image data, the consent including a selection of one of the textual message(s). For example, the processor  1172  of the backend server  1030  may receive, using the communication module  1119 , an input signal  1192  that includes a selection of one of the comments  1186  and authorizes the backend server  1030  to share the first data with the network of users together with the selected comment  1186 . As noted above, the first client device  1004 ,  1006 , may be configured to display a user interface  1120  that includes a rendering of the first data and the comments  1186 . The user interface  1120  may prompt and/or enable the first user to select one (or more) of the suggested comments  1186 . Selection of the comment(s)  1186  may cause the processor  1112  of the first client device  1004 ,  1006 , to generate and transmit an output signal  1112  that authorizes the sharing of the first data and the comment  1186 . In other implementations, the user interface  1120  may provide separate prompts for selecting a comment  1186  and authorizing sharing of the first data with the selected comment  1186 . In some implementations, the user interface  1120  may further prompt the user to input text or other data for association with the first data, e.g., in addition to or instead of the suggested comment(s)  1186 . 
     The process  5800 , at block  5818 , shares the first data and the textual message(s). For example, the processor  1172  of the backend server  1030  may upload, using the communication module  1119 , the first image data  1060 , the first audio data  1062 , and/or the first text data  1064  and the selected comment(s)  1186  to a storage device. For example, the storage device may be accessible by other network users and/or third parties. In other example embodiments, the processor  1172  of the backend server  1030  may transmit, using the communication module  1119 , the first image data  1060 , the first audio data  1062 , and/or the first text data  1064  and the selected comment(s) to a client device associated with other users of the network and/or to client device(s) associated with one or more third parties. Assuming the backend server  1030  has permission, the second image data  1090  may also be shared with the first data and the comments  1186 . 
       FIG. 59  is a sequence diagram illustrating an embodiment of another process for searching second image data  1090  for a match of a person of interest according to various aspects of the present disclosure. The process may include a first client device(s)  1004 ,  1006 , a second A/V recording and communication device  1012 , a backend device such as the backend server  1030 , a second client device(s)  1014 ,  1016 , and a network of users. At a time T 1 , the first client device  1004 ,  1006  may transmit a share signal  1048  including first image data  1060  that includes a person of interest, to the backend server  1030 , as described above. In addition, at a time T 2 , the second A/V recording and communication device  1012  may transmit to the backend server  1030  second image data  1090  captured using a camera  1070 , as described above. In many embodiments, the second A/V recording and communication device  1012  may transmit the second image data  1090  before the first client device(s)  1004 ,  1006  transmits the share signal  1048 . In this manner, the backend server  1030  may have second image data  1090  that has been stored and can be searched for a match of the person of interest found in the first image data  1060 . However, the order of timing of T 1  or T 2  is inconsequential so long as the backend server  1030  has received the second image data  1090  prior to searching the second image data  1090  for a match of the person of interest. In many embodiments, the backend server may transmit a second image data access request signal  1151  to the second client device(s)  1014 ,  1016  at a time T 3 , as described above. If access is granted, the second client device(s)  1014 ,  1016 , may transmit a locate person command signal  1153  at a time T 4 , in response to receiving the second image data access request signal  1151 , as described above. Upon searching and finding a match of the person of interest in the second image data  1090 , the backend server  1030  may transmit an alert signal  1157  at a time T 5 , wherein the alert signal  1157  includes a notification that the person of interest was matched in the second image data  1090 . In some embodiments, the second client device(s)  1014 ,  1016 , may then transmit an append signal  1155  at a time T 6 , that includes a command to append the second image data  1090  of the matched person of interest onto the shared first image data  1060  of the person of interest. At a time T 7 , the backend server  1030 , may transmit the first and second image data  1060 ,  1090  of the matched person of interest to the network of users. 
       FIG. 60  is a sequence diagram illustrating an embodiment of another process for searching second image data  1090  for a match of a person of interest according to various aspects of the present disclosure. The process may include a first client device(s)  1004 ,  1006 , a second A/V recording and communication device  1012 , a backend device such as the backend server  1030 , a second client device(s)  1014 ,  1016 , and a network of users. At a time T 1 , the first client device  1004 ,  1006  may transmit a share signal  1048  including first text data  1064  that includes a text-based description of a person of interest, to the backend server  1030 , as described above. In addition, at a time T 2 , the second A/V recording and communication device  1012  may transmit to the backend server  1030  second image data  1090  captured using a camera  1070 , as described above. In many embodiments, the second A/V recording and communication device  1012  may transmit the second image data  1090  before the first client device(s)  1004 ,  1006  transmits the share signal  1048 . In this manner, the backend server  1030  may have second image data  1090  that has been stored and can be searched for a match of the person of interest described in the first text data  1064 . As described above, the order of timing of T 1  or T 2  is inconsequential so long as the backend server  1030  has received the second image data  1090  prior to searching the second image data  1090  for a match of the person of interest. Upon finding a match of the text-based description of the person of interest in the second image data  1090 , the backend server may transmit the matched second image data  1090 , the text-based description of the person of interest, and a confirmation of person request signal  1161  to the second client device(s)  1014 ,  1016  at a time T 3 , as described above. If a second user associated with the second client device(s)  1014 ,  1016  agrees that the matched second image data  1090  appears to match the text-based description of the person of interest, the second client device(s)  1014 ,  1016 , may transmit a confirmation of person acknowledgment signal  1163  at a time T 4 , as described above. In some embodiments, the backend server  1030  may transmit a second image data share request signal  1167  at a time T 5 , to the second client device(s)  1014 ,  1016 , seeking permission to share the second image data  1090  with other users. The second user may grant permission and transmit using the second client device(s)  1014 ,  1016  a second image data share acknowledgment signal  1165  at a time T 6 . In some embodiments, upon finding a match of the text-based description of the person of interest in the second image data  1090 , the backend server  1030  may also transmit the matched second image data  1090  and a confirmation of person request signal  1161  to the first client device(s)  1004 ,  1006  at a time T 7 . If a first user associated with the first client device(s)  1004 ,  1006  agrees that the matched second image data  1090  appears to match the text-based description of the person of interest, the first client device(s)  1004 ,  1006  may transmit a confirmation of person acknowledgment signal  1163  at a time T 8 , as described above. At a time T 9 , the backend server  1030 , may transmit the first text data  1064  and second image data  1090  of the matched person of interest to the network of users. 
       FIG. 61  is a functional block diagram illustrating a system for communicating in a network using various signals. In some embodiments, the share signals may include image data and/or a text-based description of a person of interest according to various aspects of the present disclosure, as further described below. In some embodiments, first client device(s)  1004 ,  1006  may transmit a share signal  1048  to backend devices that may include information about a person of interest, as described above. However, in other embodiments, various other devices, such as (but not limited to) third-party devices, may transmit various signals that may include various data including (but not limited to) image data, audio data, and/or text data to the backend devices that may include information about a person of interest that may be used to search and match to image data stored at the backend devices such as (but not limited to) the backend server and/or the databases. 
     In reference to  FIG. 61 , the system  1200  may include one or more first audio/video (A/V) recording and communication devices  1202  configured to access a first user&#39;s network  1208  to connect to a network (Internet/PSTN)  1210 . The system  1200  may also include one or more first client devices  1204 ,  1206 , which in various embodiments may be configured to be in network communication with the first A/V recording and communication device  1202 . The first client devices  1204 ,  1206  may comprise, for example, a mobile phone such as a smartphone, or a computing device such as a tablet computer, a laptop computer, a desktop computer, etc. The first client devices  1204 ,  1206  may include any or all of the components and/or functionality of the first client devices  1004 ,  1006 , client device  114 , and/or the client device  850  described herein. In some embodiments, the first client devices  1204 ,  1206  may not be associated with a first A/V recording and communication device. 
     In various embodiments, the system  1200  may also include one or more second A/V recording and communication devices  1212  connected to the network (Internet/PSTN)  1210  using a second user&#39;s network  1218  to connect to a network (Internet/PSTN)  1210 . The system  1200  may further include one or more second client devices  1214 ,  1216 , which in various embodiments may be configured to be in network communication with the second A/V recording and communication device  1212 . The second client devices  1214 ,  1216  may comprise, for example, a mobile phone such as a smartphone, or a computing device such as a tablet computer, a laptop computer, a desktop computer, etc. The second client devices  1214 ,  1216  may include any or all of the components and/or functionality of the second client devices  1014 ,  1016 , client device  114 , and/or the client device  850  described herein. In some embodiments, the second client devices  1214 ,  1216  may not be associated with a second A/V recording and communication device. 
     In some embodiments, the system  1200  may also include one or more third-party A/V recording and communication devices  1220  connected to the network (Internet/PSTN)  1210  using various third-party networks  1226  such as a local network, a wireless network such as a cellular/mobile network and/or a Wi-Fi network, a wired network such as an Ethernet network, a public network, a low-bandwidth network, and/or any other appropriate network to access the network (Internet/PSTN)  1210 . The system  1200  may further include one or more third-party client devices  1222 ,  1226 , which in various embodiments may be configured to be in network communication with the third-party A/V recording and communication device  1220 . The third-party client devices  1222 ,  1226  may comprise, for example, a mobile phone such as a smartphone, or a computing device such as a tablet computer, a laptop computer, a desktop computer, etc. The third-party client devices  1222 ,  1226  may include any or all of the components and/or functionality of the first client devices  1004 ,  1006 , second client devices  1014 ,  1016 , client device  114 , and/or the client device  850  described herein. In some embodiments, the third-party client devices  1222 ,  1226  may not be associated with a third-party A/V recording and communication device. 
     With further reference to  FIG. 61 , the system  1200  may also include law enforcement A/V recording and communication devices  1228 ,  1230  connected to the network (Internet/PSTN)  1210  using a law enforcement network  1236  such as a local network, a wireless network such as a cellular/mobile network and/or a Wi-Fi network, a wired network such as an Ethernet network, a public network, a low-bandwidth network, and/or any other appropriate network to access the network (Internet/PSTN)  1210 . In addition, the law enforcement A/V recording and communication devices  1228 ,  1230  may be configured to capture image data, audio data, and/or text data and be associated with law enforcement client devices  1232 ,  1234 . In the illustrated embodiment, the law enforcement A/V recording and communication devices include a body camera  1228  and a dashboard camera  1230 , but the illustrated devices are only examples and are not limiting. 
     In further reference to  FIG. 61 , the system  1200  may also include various backend devices such as (but not limited to) storage devices  1242 , backend servers  1240 , and backend APIs  1238  in network communication with the law enforcement A/V recording and communication devices  1228 ,  1230 , the first and second A/V recording and communication devices  1202 ,  1212 , and the third-party A/V recording and communication devices  1220 . Further, the various backend devices  1238 ,  1240 ,  1242  may be in network communication with the law enforcement client devices  1232 ,  1234 , the first client devices  1204 ,  1206 , the second client devices  1214 ,  1216 , and the third-party client devices  1222 ,  1224 . In some embodiments, the storage devices  1242  may be a separate device from the backend servers  1240  (as illustrated) or may be an integral component of the backend servers  1240 . In addition, the first user&#39;s network  1208  and the second user&#39;s network  1218  may be similar in structure and/or function to the user&#39;s network  1008  and network  1018  ( FIG. 47 ), respectively. Further, the network  1210  may be similar in structure and/or function to the network  1010  ( FIG. 47 ). As described above, the backend devices such as the backend servers  1240  may be configured to receive a share signal from the first client devices  1204 ,  1206  comprising image data and/or a text-based description of a person of interest that may be used to search stored image data for a match of the person of interest. Further, the backend devices such as the backend servers  1240  may also be configured to receive various signals having image data and/or a text-based description of a person of interest from any A/V recording and communication device, such as the third-party A/V recording and communication device  1220  and/or the law enforcement A/V recording and communication devices  1228 ,  1230 , using the processes described above. In addition, the backend devices such as the backend server  1240  may receive the various signals having image data and/or a text-based description of a person of interest from third-party client devices  1222 ,  1224 , and law enforcement client devices  1232 ,  1234 . In some embodiments, the backend devices such as the backend server  1240  may receive the various signals having image data and/or a text-based description of a person of interest from third-party social networks that may include any social media service or platform that uses computer-mediated tools that allow participants to create, share, and/or exchange information in virtual communities and/or networks, such as (but not limited to) social networking websites and/or applications running on participant devices. Non-limiting examples of social networks include NEXTDOOR®, FACEBOOK®, INSTAGRAM®, SNAPCHAT®, TWITTER®, etc. In some embodiments, the backend devices such as the backend server  1240  may receive the various signals from third parties, such as the general public, where a member of the public may transmit a signal that includes image data and/or a text-based description of a person of interest using their third-party device(s)  1222 ,  1224 , such as, but not limited to, a smartphone, where the signal transmitted by the member of the public may include image data, audio data, and/or text data. 
     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.