Sharing video footage from audio/video recording and communication devices
Video footage captured by A/V recording and communication devices may be readily uploaded to the cloud and shared with a requesting party, such as a law enforcement agency. When a request is received from a requesting party for video footage, a set of videos meeting the criteria specified by the requesting party may be determined. Consent requests may then be sent to users associated with each of the A/V recording and communication devices that recorded the videos meeting the criteria specified by the requesting party. When user consents to share the videos are received, the video footage may be provided to the requesting party.
Latest Amazon Patents:
This application claims priority to provisional application Ser. No. 62/288,971, filed on Jan. 29, 2016, provisional application Ser. No. 62/271,186, filed on Dec. 22, 2015, and provisional application Ser. No. 62/270,373, filed on Dec. 21, 2015. The entire contents of the priority applications are hereby incorporated by reference as if fully set forth.
TECHNICAL FIELDThe 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.
BACKGROUNDHome 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.
SUMMARYThe various embodiments of the present apparatus, systems, and methods for sharing video footage from audio/video 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 audio/video (A/V) recording and communication devices may from time to time record video footage of criminal activity and/or of criminal perpetrators. This video footage may be useful to law enforcement agencies, not only because it may be evidence of the commission of a crime and of the person(s) responsible for the crime (if the crime is caught on video), but also because it may provide information about a location of a criminal perpetrator (if, for example, the crime is not caught on video, but a person wanted for questioning in connection with a crime is recorded by the A/V recording and communication device). 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 law enforcement. The present embodiments, as described in detail below, provide this enhancement. In particular, the present embodiments enable video footage captured by A/V recording and communication devices to be readily uploaded to the cloud and shared with a requesting party, such as a law enforcement agency. The footage from these A/V recording and communication devices, which may contain images of the perpetrator(s) of the crime and/or other valuable information, may then be used in identifying and/or capturing the perpetrator(s), thereby making communities safer.
In a first aspect, a method is provided, the method comprising receiving a request from a requesting party for video footage recorded by one or more audio/video (A/V) recording and communication devices in a specified area during a specified time window, wherein each of the A/V recording and communication devices includes a camera; determining videos that were recorded by at least a subset of the A/V recording and communication devices in the specified area during the specified time window; sending consent requests to users associated with each of the A/V recording and communication devices in the subset; receiving at least one user consent to share at least one of the videos recorded by the A/V recording and communication devices in the subset; and providing the video footage corresponding to the at least one user consent to the requesting party.
In an embodiment of the first aspect, the specified time window includes an ending date and/or time that is in the future.
In another embodiment of the first aspect, determining the videos comprises taking as criteria the specified area and the specified time window, and using the criteria to search through video metadata to identify videos that meet the criteria.
In another embodiment of the first aspect, determining the videos returns a set of video metadata records.
In another embodiment of the first aspect, the consent requests comprise push notifications sent to client devices associated with each of the users.
In another embodiment of the first aspect, the push notifications comprise an indicator of the specified time window.
In another embodiment of the first aspect, the push notifications comprise an indicator of the requesting party.
In another embodiment of the first aspect, the push notifications comprise a listing of the videos that are associated with the request.
In another embodiment of the first aspect, the users may view the videos in the listing.
In another embodiment of the first aspect, the push notifications comprise three response options, including an option to share all videos meeting criteria provided by the requesting party, an option to share no videos, and an option to share some videos meeting the criteria provided by the requesting party and withhold others.
In another embodiment of the first aspect, the requesting party is a law enforcement agency.
In another embodiment of the first aspect, a server performs at least one of receiving the request, determining the videos, sending the consent requests, receiving the at least one user consent, and providing the video footage.
In a second aspect, a method is provided, the method comprising receiving a request from a requesting party for video footage recorded by one or more audio/video (A/V) recording and communication devices in a specified area during a specified time window, wherein the specified time window includes a defined start date and/or time, but does not include a defined end date or time, and wherein each of the A/V recording and communication devices includes a camera, determining videos that were recorded by at least a subset of the A/V recording and communication devices in the specified area after the defined start date and/or time; sending consent requests to users associated with each of the A/V recording and communication devices in the subset; receiving at least one user consent to share at least one of the videos recorded by the A/V recording and communication devices in the subset; and providing the video footage corresponding to the at least one user consent to the requesting party.
In an embodiment of the second aspect, the defined start date and/or time is in the past.
In another embodiment of the second aspect, the defined start date and/or time correspond to a time that the request is received.
In another embodiment of the second aspect, determining the videos comprises taking as criteria the specified area and the defined start date and/or time, and using the criteria to search through video metadata to identify videos that meet the criteria.
In another embodiment of the second aspect, determining the videos returns a set of video metadata records.
In another embodiment of the second aspect, the consent requests comprise push notifications sent to client devices associated with each of the users.
In another embodiment of the second aspect, the push notifications comprise an indicator of the defined start date and/or time.
In another embodiment of the second aspect, the push notifications comprise an indicator of the requesting party.
In another embodiment of the second aspect, the push notifications comprise a listing of the videos that are associated with the request.
In another embodiment of the second aspect, the users may view the videos in the listing.
In another embodiment of the second aspect, the push notifications comprise three response options, including an option to share all videos meeting criteria provided by the requesting party, an option to share no videos, and an option to share some videos meeting the criteria provided by the requesting party and withhold others.
In another embodiment of the second aspect, the requesting party is a law enforcement agency.
In another embodiment of the second aspect, a server performs at least one of receiving the request, determining the videos, sending the consent requests, receiving the at least one user consent, and providing the video footage.
In a third aspect, a method is provided, the method comprising displaying, on a display of a client device, a graphical user interface (GUI) for enabling a requester to request video footage from one or more audio/video (A/V) recording and communication devices; receiving as an input an address that identifies a location from around which the requester wishes to gather the video footage; displaying, on the GUI on the display of the client device, a map of an area around the input address; identifying, on the map, the location of the input address; identifying, on the map, locations of the one or more A/V recording and communication devices; receiving as an input an area of interest and indicating the area of interest on the map; identifying, on the map, locations of a subset of the A/V recording and communication devices that are within the area of interest; receiving as an input an execute command; and returning as an output the video footage from the subset of the A/V recording and communication devices that are within the area of interest.
In an embodiment of the third aspect, the client device comprises a desktop computer, a laptop computer, a tablet computer, a mobile telephone, a cellular telephone, a smartphone, or a personal digital assistant (PDA).
In another embodiment of the third aspect, the location of the input address is indicated on the map with an icon of a first type.
In another embodiment of the third aspect, the locations of the one or more A/V recording and communication devices are indicated on the map with icons of a second type.
Another embodiment of the third aspect further comprises receiving as an input a range of dates and/or times.
Another embodiment of the third aspect further comprises restricting the video footage provided to the requester to the range of dates and/or times.
In another embodiment of the third aspect, receiving the input of the area of interest comprises receiving an input of a polygon drawn on the map of the GUI.
In another embodiment of the third aspect, receiving the input of the area of interest comprises receiving an input of a radius around the address.
Another embodiment of the third aspect further comprises receiving as an input a case number or an incident number.
Another embodiment of the third aspect further comprises receiving as an input an incident type.
Another embodiment of the third aspect further comprises, after returning as an output the video footage from the subset of the A/V recording and communication devices that are within the area of interest, indicating with icons on the map the locations of the subset of the A/V recording and communication devices that have the video footage meeting the requester's criteria, wherein each icon includes a number that indicates a number of videos associated with that A/V recording and communication device that meet all criteria input by the requester.
In another embodiment of the third aspect, returning as an output the video footage from the subset of the A/V recording and communication devices that are within the area of interest comprises displaying, on the GUI on the display of the client device, a list of videos.
In another embodiment of the third aspect, each video in the list includes identifying information, including the address where the A/V recording and communication device that recorded each video is located, and the date and time that each video was recorded.
In another embodiment of the third aspect, each video in the list includes a download icon or button that, when selected, causes the selected video to be downloaded to the client device.
In another embodiment of the third aspect, each video in the list includes a flag icon or button that, when selected, causes the selected video to be added to a group of flagged videos.
In another embodiment of the third aspect, the method further comprises receiving as an input a command to narrow the list of videos to only those videos that are in the group of flagged videos.
In a fourth aspect, a computer program product is provided, the computer program product being embodied in code executable by a processor, which when executed causes the processor to display, on a display of a client device, a graphical user interface (GUI) for enabling a requester to request video footage from one or more audio/video (A/V) recording and communication devices; receive as an input an address that identifies a location from around which the requester wishes to gather the video footage; display, on the GUI on the display of the client device, a map of an area around the input address; identify, on the map, the location of the input address; identify, on the map, locations of the one or more A/V recording and communication devices; receive as an input an area of interest and indicate the area of interest on the map; identify, on the map, locations of a subset of the A/V recording and communication devices that are within the area of interest; receive as an input an execute command; and return as an output the video footage from the subset of the A/V recording and communication devices that are within the area of interest.
In an embodiment of the fourth aspect, the location of the input address is indicated on the map with an icon of a first type.
In another embodiment of the fourth aspect, the locations of the one or more A/V recording and communication devices are indicated on the map with icons of a second type.
In another embodiment of the fourth aspect, the code, when executed by the processor, further causes the processor to receive as an input a range of dates and/or times.
In another embodiment of the fourth aspect, the code, when executed by the processor, further causes the processor to restrict the video footage provided to the requester to the range of dates and/or times.
In another embodiment of the fourth aspect, receiving the input of the area of interest comprises receiving an input of a polygon drawn on the map of the GUI.
In another embodiment of the fourth aspect, receiving the input of the area of interest comprises receiving an input of a radius around the address.
In another embodiment of the fourth aspect, the code, when executed by the processor, further causes the processor to receive as an input a case number or an incident number.
In another embodiment of the fourth aspect, the code, when executed by the processor, further causes the processor to receive as an input an incident type.
In another embodiment of the fourth aspect, the code, when executed by the processor, further causes the processor to, after returning as an output the video footage from the subset of the A/V recording and communication devices that are within the area of interest, indicate with icons on the map the locations of the subset of the A/V recording and communication devices that have the video footage meeting the requester's criteria, wherein each icon includes a number that indicates a number of videos associated with that A/V recording and communication device that meet all criteria input by the requester.
In another embodiment of the fourth aspect, returning as an output the video footage from the subset of the A/V recording and communication devices that are within the area of interest comprises displaying, on the GUI on the display of the client device, a list of videos.
In another embodiment of the fourth aspect, each video in the list includes identifying information, including the address where the A/V recording and communication device that recorded each video is located, and the date and time that each video was recorded.
In another embodiment of the fourth aspect, each video in the list includes a download icon or button that, when selected, causes the selected video to be downloaded to the client device.
In another embodiment of the fourth aspect, each video in the list includes a flag icon or button that, when selected, causes the selected video to be added to a group of flagged videos.
In another embodiment of the fourth aspect, the code, when executed by the processor, further causes the processor to receive as an input a command to narrow the list of videos to only those videos that are in the group of flagged videos.
The various embodiments of the present apparatus, systems, and methods for sharing video footage from audio/video 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 sharing video footage from audio/video 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:
The following detailed description describes the present embodiments with reference to the drawings. In the drawings, reference numbers label elements of the present embodiments. These reference numbers are reproduced below in connection with the discussion of the corresponding drawing features.
The embodiments of the present apparatus, systems, and methods for sharing video footage from audio/video recording and communication 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
The A/V recording and communication doorbell 100 is typically 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
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
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'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'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's client device 114 (
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 (
With further reference to
The backend API 120 illustrated
The backend API 120 illustrated in
One aspect of the present embodiments includes the realization that audio/video (A/V) recording and communication devices may from time to time record video footage of criminal activity and/or of criminal perpetrators. This video footage may be useful to law enforcement agencies, not only because it may be evidence of the commission of a crime and of the person(s) responsible for the crime (if the crime is caught on video), but also because it may provide information about a location of a criminal perpetrator (if, for example, the crime is not caught on video, but a person wanted for questioning in connection with a crime is recorded by the A/V recording and communication device). 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 law enforcement. The present embodiments, as described in detail below, provide this enhancement. In particular, the present embodiments enable video footage captured by A/V recording and communication devices to be readily uploaded to the cloud and shared with a requesting party, such as a law enforcement agency. The footage from these A/V recording and communication devices, which may contain images of the perpetrator(s) of the crime and/or other valuable information, may then be used in identifying and/or capturing the perpetrator(s), thereby making communities safer.
With further reference to
The requester may specify the area 308 from which video footage will be gathered in any of a variety of ways. For example, the requester may draw a polygon of any shape and size on the map 302 of the GUI 300 by specifying locations of vertices 314 of the polygon, such as by touching the locations of the vertices 314, if the requester's client device includes a touchscreen, or by using a pointing device, such as a mouse or a trackball, and an onscreen pointer to specify the locations of the vertices 314. In certain embodiments, the polygon specified by the requester may not have any vertices 314, such as a circle. The requester in such an embodiment may specify an area of interest by providing a radius around the address (indicated on the map 302 by the icon of the first type 304) that the requester has entered.
With further reference to
After the requester specifies an area 308, and optionally a date range 310/312 and/or any other criteria, as described above, the process identifies the video footage meeting the criteria specified by the requester, and returns the identified video footage to the requester. For example,
With further reference to
With reference to
With further reference to
With reference to
For example, with reference to
With further reference to
Referring back to
As described above, in some embodiments the requesting party may enter an ending date and/or time that is in the future, or the requester may not provide an ending date and/or time.
With further reference to
Referring back to
While not shown in
In certain other embodiments, a user may provide consent to share videos prospectively. For example, when a user sets up a new A/V doorbell, one step in the setup process may present the user with a request to provide consent (to “opt-in”) to share all videos recorded and uploaded by that A/V doorbell. In another example, a user may be required to provide consent to share all videos recorded and uploaded by that A/V doorbell as a condition of receiving the A/V doorbell. For example, a law enforcement agency may offer to provide A/V doorbells to users free of charge with the condition that any videos recorded and uploaded by that A/V doorbell be shared with the law enforcement agency that provided the A/V doorbell to the user.
As described above, the present embodiments advantageously enable a requesting party, such as a law enforcement agency, to request that users of A/V doorbells share video footage recorded and uploaded (to the cloud) by those A/V doorbells. Such footage can be useful to law enforcement for solving crimes and apprehending perpetrators, and for stopping crimes that may be currently in progress.
With reference to
With reference to
With further reference to
The camera PCB 147 may be secured within the doorbell with any suitable fasteners, such as screws, or interference connections, adhesives, etc. The camera PCB 147 comprises various components that enable the functionality of the camera 134 of the doorbell 130, as described below. Infrared light-emitting components, such as infrared LED's 168, are coupled to the camera PCB 147 and may be triggered to activate when a light sensor detects a low level of ambient light. When activated, the infrared LED's 168 may emit infrared light through the enclosure 131 and/or the camera 134 out into the ambient environment. The camera 134, which may be configured to detect infrared light, may then capture the light emitted by the infrared LED's 168 as it reflects off objects within the camera's 134 field of view, so that the doorbell 130 can clearly capture images at night (may be referred to as “night vision”).
With continued reference to
With continued reference to
With continued reference to
With continued reference to
With reference to
With further reference to
With further reference to
The speakers 157 and the microphone 158 may be coupled to the camera processor 170 through an audio CODEC 161. For example, the transfer of digital audio from the user's client device 114 and the speakers 157 and the microphone 158 may be compressed and decompressed using the audio CODEC 161, coupled to the camera processor 170. Once compressed by audio CODEC 161, digital audio data may be sent through the communication module 164 to the network 112, routed by one or more servers 118, and delivered to the user's client device 114. When the user speaks, after being transferred through the network 112, digital audio data is decompressed by audio CODEC 161 and emitted to the visitor via the speakers 157.
With further reference to
With further reference to
With further reference to
With further reference to
The present embodiments have been described with reference to the doorbell 130 illustrated in
With reference to
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®/IPOD® 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.
The computer system 1000 may include at least one processor 1010, memory 1020, at least one storage device 1030, and input/output (I/O) devices 1040. Some or all of the components 1010, 1020, 1030, 1040 may be interconnected via a system bus 1050. The processor 1010 may be single- or multi-threaded and may have one or more cores. The processor 1010 may execute instructions, such as those stored in the memory 1020 and/or in the storage device 1030. Information may be received and output using one or more I/O devices 1040.
The memory 1020 may store information, and may be a computer-readable medium, such as volatile or non-volatile memory. The storage device(s) 1030 may provide storage for the system 1000, and may be a computer-readable medium. In various aspects, the storage device(s) 1030 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 1040 may provide input/output operations for the system 1000. The I/O devices 1040 may include a keyboard, a pointing device, and/or a microphone. The I/O devices 1040 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 1060.
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).
Claims
1. A method, comprising:
- receiving, at a server, a video request signal from a requesting device of a requesting party for video footage recorded by one or more audio/video (A/V) recording and communication devices installed at one or more properties located within a specified area during a specified time window, wherein the specified time window includes a start time and an end time, and wherein each of the A/V recording and communication devices includes a camera configured to capture video footage;
- in response to the received request signal, identifying, at the server, video footage recorded by at least a subset of the A/V recording and communication devices in the specified area recorded between the start time and the end time;
- in response to the identifying, sending, from the server, a consent request signal to at least one client device associated with at least one of the A/V recording and communication devices in the subset;
- receiving a share consent signal from the at least one client device granting consent to share the video footage recorded by the at least one A/V recording and communication device in the subset associated with the at least one client device; and
- transmitting the video footage recorded by the at least one A/V recording and communication device in the subset to the requesting device.
2. The method of claim 1, wherein the end time is in the future.
3. The method of claim 1, wherein identifying, at the server, the video footage comprises taking as criteria the specified area and the specified time window, and using the criteria to search through video metadata to identify video footage that meets the criteria.
4. The method of claim 3, wherein identifying, at the server, the video footage returns a set of video metadata records.
5. The method of claim 1, wherein the consent request signal comprises push notifications sent to the at least one client device associated with the at least one A/V recording and communication device in the subset.
6. The method of claim 5, wherein the push notifications comprise an indicator of the specified time window.
7. The method of claim 5, wherein the push notifications comprise an indicator of the requesting party.
8. The method of claim 5, wherein the push notifications comprise a listing of video footage that is/are associated with the video request signal.
9. The method of claim 8, wherein a user may view the video footage in the listing.
10. The method of claim 5, wherein the push notifications comprise three response options, including an option to share all video footage meeting criteria provided by the requesting party, an option to share no video footage, and an option to share some video footage meeting the criteria provided by the requesting party and withhold other video footage.
11. The method of claim 1, wherein the requesting party is a law enforcement agency.
12. The method of claim 1, wherein the server performs at least one of receiving the share consent signal and transmitting the video footage.
13. A method, comprising:
- receiving, at a server, a video request signal from a requesting device of a requesting party for video footage recorded by one or more audio/video (A/V) recording and communication devices installed at one or more properties located within a specified area during a specified time window, wherein the specified time window includes a defined start date and/or time, but does not include a defined end date and/or time, and wherein each of the A/V recording and communication devices includes a camera configured to capture video footage;
- in response to the received request signal, identifying, at the server, video footage recorded by at least a subset of the A/V recording and communication devices in the specified area recorded after the defined start date and/or time;
- in response to the identifying, sending, from the server, a consent request signal to at least one client device associated with at least one of the A/V recording and communication devices in the subset;
- receiving a share consent signal from the at least one client device granting consent to share the video footage recorded by the at least one A/V recording and communication device in the subset associated with the at least one client device; and
- transmitting the video footage recorded by the at least one A/V recording and communication device in the subset to the requesting device.
14. The method of claim 13, wherein the defined start date and/or time is in the past.
15. The method of claim 13, wherein the defined start date and/or time correspond to a time that the video request signal is received.
16. The method of claim 13, wherein identifying, at the server, the video footage comprises taking as criteria the specified area and the defined start date and/or time, and using the criteria to search through video metadata to identify videos that meet the criteria.
17. The method of claim 16, wherein identifying, at the server, the video footage returns a set of video metadata records.
18. The method of claim 13, wherein the consent request signal comprises push notifications sent to the at least one client device associated with the at least one A/V recording and communication device in the subset.
19. The method of claim 18, wherein the push notifications comprise an indicator of the defined start date and/or time.
20. The method of claim 18, wherein the push notifications comprise an indicator of the requesting party.
21. The method of claim 18, wherein the push notifications comprise a listing of video footage that is/are associated with the video request signal.
22. The method of claim 21, wherein a user may view the video footage in the listing.
23. The method of claim 18, wherein the push notifications comprise three response options, including an option to share all video footage meeting criteria provided by the requesting party, an option to share no video footage, and an option to share some video footage meeting the criteria provided by the requesting party and withhold other video footage.
24. The method of claim 13, wherein the requesting party is a law enforcement agency.
25. The method of claim 13, wherein the server performs at least one receiving the at least one user consent and providing the video footage.
4764953 | August 16, 1988 | Chern et al. |
5428388 | June 27, 1995 | von Bauer et al. |
5760848 | June 2, 1998 | Cho |
6072402 | June 6, 2000 | Kniffin et al. |
6192257 | February 20, 2001 | Ray |
6271752 | August 7, 2001 | Vaios |
6429893 | August 6, 2002 | Xin |
6456322 | September 24, 2002 | Marinacci |
6476858 | November 5, 2002 | Ramirez Diaz et al. |
6542078 | April 1, 2003 | Script et al. |
6633231 | October 14, 2003 | Okamoto et al. |
6658091 | December 2, 2003 | Naidoo et al. |
6698021 | February 24, 2004 | Amini |
6753774 | June 22, 2004 | Pan et al. |
6828909 | December 7, 2004 | Script et al. |
6970183 | November 29, 2005 | Monroe |
7062291 | June 13, 2006 | Ryley et al. |
7065196 | June 20, 2006 | Lee |
7085361 | August 1, 2006 | Thomas |
7109860 | September 19, 2006 | Wang |
7304572 | December 4, 2007 | Sheynman et al. |
7382249 | June 3, 2008 | Fancella |
7450638 | November 11, 2008 | Iwamura |
7529411 | May 5, 2009 | Haupt et al. |
7643056 | January 5, 2010 | Silsby |
7683924 | March 23, 2010 | Oh et al. |
7683929 | March 23, 2010 | Elazar et al. |
7710452 | May 4, 2010 | Lindberg |
7738917 | June 15, 2010 | Ryley et al. |
8494340 | July 23, 2013 | Wang et al. |
8531522 | September 10, 2013 | Horovitz et al. |
8593511 | November 26, 2013 | Ikeda et al. |
8619136 | December 31, 2013 | Howarter et al. |
8780201 | July 15, 2014 | Scalisi et al. |
8823795 | September 2, 2014 | Scalisi et al. |
8842180 | September 23, 2014 | Kasmir et al. |
8872915 | October 28, 2014 | Scalisi et al. |
8887050 | November 11, 2014 | Siracusano, Jr. |
8937659 | January 20, 2015 | Scalisi et al. |
8941736 | January 27, 2015 | Scalisi et al. |
8947530 | February 3, 2015 | Scalisi |
8953040 | February 10, 2015 | Scalisi et al. |
8970349 | March 3, 2015 | Gutierrez et al. |
9013575 | April 21, 2015 | Scalisi |
9041812 | May 26, 2015 | Billau |
9049352 | June 2, 2015 | Scalisi et al. |
9053622 | June 9, 2015 | Scalisi |
9055202 | June 9, 2015 | Scalisi et al. |
9058738 | June 16, 2015 | Scalisi |
9060103 | June 16, 2015 | Scalisi |
9060104 | June 16, 2015 | Scalisi |
9065987 | June 23, 2015 | Kasmir et al. |
9087386 | July 21, 2015 | Morris et al. |
9094584 | July 28, 2015 | Scalisi et al. |
9109378 | August 18, 2015 | Scalisi |
9113051 | August 18, 2015 | Scalisi |
9113052 | August 18, 2015 | Scalisi et al. |
9118819 | August 25, 2015 | Scalisi et al. |
9142214 | September 22, 2015 | Scalisi |
9160987 | October 13, 2015 | Kasmir et al. |
9165444 | October 20, 2015 | Scalisi |
9172920 | October 27, 2015 | Kasmir et al. |
9172921 | October 27, 2015 | Scalisi et al. |
9172922 | October 27, 2015 | Kasmir et al. |
9179107 | November 3, 2015 | Scalisi et al. |
9179108 | November 3, 2015 | Scalisi et al. |
9179109 | November 3, 2015 | Kasmir et al. |
9196133 | November 24, 2015 | Scalisi et al. |
9197867 | November 24, 2015 | Scalisi et al. |
9230424 | January 5, 2016 | Scalisi et al. |
9237318 | January 12, 2016 | Kasmir et al. |
9247219 | January 26, 2016 | Kasmir et al. |
9253455 | February 2, 2016 | Harrison et al. |
9342936 | May 17, 2016 | Scalisi |
9508239 | November 29, 2016 | Harrison et al. |
9819972 | November 14, 2017 | Vantalon |
20020094111 | July 18, 2002 | Puchek et al. |
20020131768 | September 19, 2002 | Gammenthaler |
20020147982 | October 10, 2002 | Naidoo et al. |
20030043047 | March 6, 2003 | Braun |
20030185296 | October 2, 2003 | Masten, Jr. |
20040085205 | May 6, 2004 | Yeh |
20040085450 | May 6, 2004 | Stuart |
20040086093 | May 6, 2004 | Schranz |
20040095254 | May 20, 2004 | Maruszczak |
20040135686 | July 15, 2004 | Parker |
20050111660 | May 26, 2005 | Hosoda |
20060010199 | January 12, 2006 | Brailean et al. |
20060022816 | February 2, 2006 | Yukawa |
20060139449 | June 29, 2006 | Cheng et al. |
20060156361 | July 13, 2006 | Wang et al. |
20060190262 | August 24, 2006 | Roskind |
20060279628 | December 14, 2006 | Fleming |
20070008081 | January 11, 2007 | Tylicki et al. |
20070199076 | August 23, 2007 | Rensin |
20090015672 | January 15, 2009 | Clapp |
20090031381 | January 29, 2009 | Cohen |
20100066835 | March 18, 2010 | Colciago |
20100085431 | April 8, 2010 | Trapani |
20100225455 | September 9, 2010 | Claiborne et al. |
20110058034 | March 10, 2011 | Grass |
20120124203 | May 17, 2012 | Richards |
20120203925 | August 9, 2012 | Curcio |
20120284202 | November 8, 2012 | Dalby |
20130117365 | May 9, 2013 | Padmanabhan |
20140047074 | February 13, 2014 | Chung |
20140101781 | April 10, 2014 | Bouknight |
20140132772 | May 15, 2014 | Billau |
20140133831 | May 15, 2014 | Billau |
20140160250 | June 12, 2014 | Pomerantz |
20140267716 | September 18, 2014 | Child et al. |
20150163463 | June 11, 2015 | Hwang et al. |
20150242444 | August 27, 2015 | Campbell |
20150290808 | October 15, 2015 | Renkis |
20150319402 | November 5, 2015 | Abuelsaad |
20160014176 | January 14, 2016 | Ariav |
20160105644 | April 14, 2016 | Smith et al. |
20160112461 | April 21, 2016 | Othmer |
20160224837 | August 4, 2016 | Lipert |
20170155737 | June 1, 2017 | Jannink |
2585521 | November 2002 | CN |
2792061 | November 2004 | CN |
0944883 | February 1997 | EP |
1480462 | November 2004 | EP |
2286283 | August 1995 | GB |
2354394 | March 2001 | GB |
2357387 | June 2001 | GB |
2400958 | October 2004 | GB |
2001-103463 | April 2001 | JP |
2002-033839 | January 2002 | JP |
2002-125059 | April 2002 | JP |
2002-342863 | November 2002 | JP |
2002-344640 | November 2002 | JP |
2002-354137 | December 2002 | JP |
2002-368890 | December 2002 | JP |
2003-283696 | October 2003 | JP |
2004-128835 | April 2004 | JP |
2005-341040 | December 2005 | JP |
2006-147650 | June 2006 | JP |
2006-262342 | September 2006 | JP |
2009-008925 | January 2009 | JP |
9839894 | September 1998 | WO |
0113638 | February 2001 | WO |
0193220 | December 2001 | WO |
02085019 | October 2002 | WO |
03028375 | April 2003 | WO |
06038760 | April 2006 | WO |
2006067782 | June 2006 | WO |
03096696 | September 2006 | WO |
2007125143 | November 2007 | WO |
- Cook, John; Draw your own neighborhood home search on a map with Zillow's updated iPhone app. GeekWire.com Nov. 28, 2011. (14 pages).
- International Application No. PCT/US2016/068088; International Filing Date: Dec. 21, 2016. Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration. (25 pages).
Type: Grant
Filed: Dec 21, 2016
Date of Patent: Oct 15, 2019
Patent Publication Number: 20170180457
Assignee: Amazon Technologies, Inc. (Seattle, WA)
Inventors: Aaron Harpole (Santa Monica, CA), Joshua Roth (Pacific Palisades, CA), James Simonoff (Pacific Palisades, CA), Darrell Sommerlatt (Los Angeles, CA)
Primary Examiner: David E Harvey
Application Number: 15/387,444
International Classification: H04N 5/18 (20060101); H04N 5/77 (20060101); H04L 29/08 (20060101); G06K 9/00 (20060101); G11B 27/19 (20060101); H04N 21/235 (20110101); H04N 21/239 (20110101); H04N 21/2743 (20110101); H04N 21/482 (20110101); H04N 21/845 (20110101); H04N 7/18 (20060101); H04N 21/218 (20110101); H04N 21/2187 (20110101); H04N 21/258 (20110101); H04N 21/431 (20110101); H04N 21/472 (20110101); H04N 21/6587 (20110101);