Patent Grant
11048397
The disclosed implementations relate generally to video monitoring, including, but not limited, to monitoring and reviewing video feeds and histories of videos saved from the video feeds.
The advancement of internet and mobile technologies has enabled the adoption of remote video surveillance by users. Users can now monitor an area under video surveillance using a website or a mobile application. Such web sites or mobile apps typically allow a user to view live video and/or saved video recordings, but otherwise provide little or no additional information regarding the videos. Furthermore, the user interfaces for viewing these live videos or saved video recordings occupy large amounts of display space and have a user control flow that is poor at maintaining context for the user. Thus, more efficient, informative, and user-friendly presentations of live and saved video surveillance are needed.
Accordingly, there is a need for presentations of live and/or saved video with a more efficient user control flow and more useful information. Such methods optionally complement or replace conventional methods for presenting live and/or saved video from video streams.
In accordance with some implementations, a method includes, in an application executing at a client device having one or more processors and memory storing one or more programs for execution by the one or more processors: receiving a plurality of video feeds, each video feed of the plurality of video feeds corresponding to a respective remote camera of a plurality of remote cameras, where the video feeds are received concurrently by the device from a server system communicatively coupled to the remote cameras; displaying a first user interface, the first user interface including a plurality of user interface objects, each user interface object of the plurality of user interface objects being associated with a respective remote camera of the remote cameras; and displaying in each user interface object of the plurality of user interface objects the video feed corresponding to the respective remote camera with which the user interface object is associated, where at least one of the video feeds is displayed with cropping.
In accordance with some implementations, a method includes, at a server system having one or more processors and memory storing one or more programs for execution by the one or more processors: receiving a video feed from a camera with an associated field of view; receiving one or more alert events; identifying as a camera event a portion of the video feed associated in time with the one or more alert events; determining a start time and a duration of the camera event; determining a chronological order of the alert events; and saving, in a history associated with the camera, information associated with the camera event, including: a video clip and/or a frame from the portion of the video feed, and the chronological order of the alert events.
In accordance with some implementations, a method includes, at a client device having one or more processors and memory storing one or more programs for execution by the one or more processors: displaying a video feed from a camera or a frame from the video feed; and concurrently with displaying the video feed or the frame, displaying a camera history timeline, including: displaying a representation of a camera event associated with one or more alert events in the camera history timeline as a bar overlaid on the event history timeline, the event bar having a length reflecting a duration of the camera event; and displaying, proximate to the event bar, one or more alert event indicators, each of the alert event indicators corresponding to a respective alert event of the alert events associated with the camera event, where each respective alert event indicator has a respective visually distinctive display characteristic associated with the corresponding respective alert event.
In accordance with some implementations, a method includes, at a client device having one or more processors and memory storing one or more programs for execution by the one or more processors: displaying a camera history timeline, including: displaying a chronologically ordered sequence of event identifiers, each event identifier corresponding to a respective camera event, each respective camera event associated with one or more respective alert events; and displaying, for a respective event identifier, one or more alert event indicators, each of the alert event indicators corresponding to an alert event associated with the camera event corresponding to the respective event identifier, each of the alert event indicators displayed with a visually distinctive display characteristic associated with a corresponding alert event.
In accordance with some implementations, a method includes, at a client device having one or more processors and memory storing one or more programs for execution by the one or more processors, in an application executing on the client device: displaying a camera event history provided by a remote server system, where the camera event history is presented as a chronologically-ordered set of event identifiers, each event identifier corresponding to a respective event for which a remote camera has captured an associated video; receiving a user selection of a displayed event identifier; and in response to receiving the user selection of the displayed event identifier: expanding the selected event identifier into a video player window, the video player window consuming a portion of the displayed camera event history; and playing, in the video player window, the captured video associated with the selected event identifier; and in response to terminating playback of the captured video associated with the selected event identifier or user de-selection of the displayed event identifier, collapsing the video player window into the selected event identifier thereby stopping the playing of the captured video associated with the selected event identifier.
In accordance with some implementations, a system includes a plurality of electronic devices, wherein at least one of the plurality of electronic devices has one or more processors and memory storing one or more programs for execution by the processor, the one or more programs including instructions for performing the operations of the method described above. In accordance with some implementations, an electronic device has one or more processors and memory storing one or more programs for execution by the processor, the one or more programs including instructions for performing the operations of the method described above. In accordance with some implementations, a computer readable storage medium has stored therein one or more programs having instructions which, when executed by an electronic device having one or more processors, cause the electronic device to perform the operations of the method described above.
Thus, computing systems are provided with more efficient methods for presenting live and/or saved video and related information, thereby increasing the effectiveness, efficiency, and user satisfaction with such systems. Such methods may complement or replace conventional methods for presenting live and/or saved video.
The patent or application file contains at least one drawing executed in color. Copies of this patent or patent application publication with color drawing(s) will be provided by the Office upon request and payment of the necessary fee.
For a better understanding of the various described implementations, reference should be made to the Description of Implementations below, in conjunction with the following drawings in which like reference numerals refer to corresponding parts throughout the figures.
Like reference numerals refer to corresponding parts throughout the several views of the drawings.
Reference will now be made in detail to implementations, examples of which are illustrated in the accompanying drawings. In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the various described implementations. However, it will be apparent to one of ordinary skill in the art that the various described implementations may be practiced without these specific details. In other instances, well-known methods, procedures, components, circuits, and networks have not been described in detail so as not to unnecessarily obscure aspects of the implementations.
It will also be understood that, although the terms first, second, etc. are, in some instances, used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first user interface could be termed a second user interface, and, similarly, a second user interface could be termed a first user interface, without departing from the scope of the various described implementations. The first user interface and the second user interface are both types of user interfaces, but they are not the same user interface.
The terminology used in the description of the various described implementations herein is for the purpose of describing particular implementations only and is not intended to be limiting. As used in the description of the various described implementations and the appended claims, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term “and/or” as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms “includes,” “including,” “comprises,” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
As used herein, the term “if” is, optionally, construed to mean “when” or “upon” or “in response to determining” or “in response to detecting” or “in accordance with a determination that,” depending on the context. Similarly, the phrase “if it is determined” or “if [a stated condition or event] is detected” is, optionally, construed to mean “upon determining” or “in response to determining” or “upon detecting [the stated condition or event]” or “in response to detecting [the stated condition or event]” or “in accordance with a determination that [a stated condition or event] is detected,” depending on the context.
It is to be appreciated that “smart home environments” may refer to smart environments for homes such as a single-family house, but the scope of the present teachings is not so limited. The present teachings are also applicable, without limitation, to duplexes, townhomes, multi-unit apartment buildings, hotels, retail stores, office buildings, industrial buildings, and more generally any living space or work space.
It is also to be appreciated that while the terms user, customer, installer, homeowner, occupant, guest, tenant, landlord, repair person, and the like may be used to refer to the person or persons acting in the context of some particularly situations described herein, these references do not limit the scope of the present teachings with respect to the person or persons who are performing such actions. Thus, for example, the terms user, customer, purchaser, installer, subscriber, and homeowner may often refer to the same person in the case of a single-family residential dwelling, because the head of the household is often the person who makes the purchasing decision, buys the unit, and installs and configures the unit, and is also one of the users of the unit. However, in other scenarios, such as a landlord-tenant environment, the customer may be the landlord with respect to purchasing the unit, the installer may be a local apartment supervisor, a first user may be the tenant, and a second user may again be the landlord with respect to remote control functionality. Importantly, while the identity of the person performing the action may be germane to a particular advantage provided by one or more of the implementations, such identity should not be construed in the descriptions that follow as necessarily limiting the scope of the present teachings to those particular individuals having those particular identities.
The depicted structure 150 includes a plurality of rooms 152, separated at least partly from each other via walls 154. The walls 154 may include interior walls or exterior walls. Each room may further include a floor 156 and a ceiling 158. Devices may be mounted on, integrated with and/or supported by a wall 154, floor 156 or ceiling 158.
In some implementations, the integrated devices of the smart home environment 100 include intelligent, multi-sensing, network-connected devices that integrate seamlessly with each other in a smart home network (e.g., 202
In some implementations, the one or more smart thermostats 102 detect ambient climate characteristics (e.g., temperature and/or humidity) and control a HVAC system 103 accordingly. For example, a respective smart thermostat 102 includes an ambient temperature sensor.
The one or more smart hazard detectors 104 may include thermal radiation sensors directed at respective heat sources (e.g., a stove, oven, other appliances, a fireplace, etc.). For example, a smart hazard detector 104 in a kitchen 153 includes a thermal radiation sensor directed at a stove/oven 112. A thermal radiation sensor may determine the temperature of the respective heat source (or a portion thereof) at which it is directed and may provide corresponding blackbody radiation data as output.
The smart doorbell 106 and/or the smart door lock 120 may detect a person's approach to or departure from a location (e.g., an outer door), control doorbell/door locking functionality (e.g., receive user inputs from a portable electronic device 166-1 to actuate bolt of the smart door lock 120), announce a person's approach or departure via audio or visual means, and/or control settings on a security system (e.g., to activate or deactivate the security system when occupants go and come).
The smart alarm system 122 may detect the presence of an individual within close proximity (e.g., using built-in IR sensors), sound an alarm (e.g., through a built-in speaker, or by sending commands to one or more external speakers), and send notifications to entities or users within/outside of the smart home network 100. In some implementations, the smart alarm system 122 also includes one or more input devices or sensors (e.g., keypad, biometric scanner, NFC transceiver, microphone) for verifying the identity of a user, and one or more output devices (e.g., display, speaker). In some implementations, the smart alarm system 122 may also be set to an “armed” mode, such that detection of a trigger condition or event causes the alarm to be sounded unless a disarming action is performed.
In some implementations, the smart home environment 100 includes one or more intelligent, multi-sensing, network-connected wall switches 108 (hereinafter referred to as “smart wall switches 108”), along with one or more intelligent, multi-sensing, network-connected wall plug interfaces 110 (hereinafter referred to as “smart wall plugs 110”). The smart wall switches 108 may detect ambient lighting conditions, detect room-occupancy states, and control a power and/or dim state of one or more lights. In some instances, smart wall switches 108 may also control a power state or speed of a fan, such as a ceiling fan. The smart wall plugs 110 may detect occupancy of a room or enclosure and control supply of power to one or more wall plugs (e.g., such that power is not supplied to the plug if nobody is at home).
In some implementations, the smart home environment 100 of
In some implementations, the smart home environment 100 includes one or more network-connected cameras 118 that are configured to provide video monitoring and security in the smart home environment 100. In some implementations, cameras 118 also capture video when other conditions or hazards are detected, in order to provide visual monitoring of the smart home environment 100 when those conditions or hazards occur. The cameras 118 may be used to determine occupancy of the structure 150 and/or particular rooms 152 in the structure 150, and thus may act as occupancy sensors. For example, video captured by the cameras 118 may be processed to identify the presence of an occupant in the structure 150 (e.g., in a particular room 152). Specific individuals may be identified based, for example, on their appearance (e.g., height, face) and/or movement (e.g., their walk/gait). For example, cameras 118 may additionally include one or more sensors (e.g., IR sensors, motion detectors), input devices (e.g., microphone for capturing audio), and output devices (e.g., speaker for outputting audio).
The smart home environment 100 may additionally or alternatively include one or more other occupancy sensors (e.g., the smart doorbell 106, smart door locks 120, touch screens, IR sensors, microphones, ambient light sensors, motion detectors, smart nightlights 170, etc.). In some implementations, the smart home environment 100 includes radio-frequency identification (RFID) readers (e.g., in each room 152 or a portion thereof) that determine occupancy based on RFID tags located on or embedded in occupants. For example, RFID readers may be integrated into the smart hazard detectors 104.
The smart home environment 100 may include one or more sound and/or vibration sensors for detecting abnormal sounds and/or vibrations. These sensors may be integrated with any of the devices described above. The sound sensors detect sound above a decibel threshold. The vibration sensors detect vibration above a threshold directed at a particular area (e.g., vibration on a particular window when a force is applied to break the window).
Conditions detected by the devices described above (e.g., motion, sound, vibrations, hazards) may be referred to collectively as alert events.
The smart home environment 100 may also include communication with devices outside of the physical home but within a proximate geographical range of the home. For example, the smart home environment 100 may include a pool heater monitor 114 that communicates a current pool temperature to other devices within the smart home environment 100 and/or receives commands for controlling the pool temperature. Similarly, the smart home environment 100 may include an irrigation monitor 116 that communicates information regarding irrigation systems within the smart home environment 100 and/or receives control information for controlling such irrigation systems.
By virtue of network connectivity, one or more of the smart home devices of
As discussed above, users may control smart devices in the smart home environment 100 using a network-connected computer or portable electronic device 166. In some examples, some or all of the occupants (e.g., individuals who live in the home) may register their device 166 with the smart home environment 100. Such registration may be made at a central server to authenticate the occupant and/or the device as being associated with the home and to give permission to the occupant to use the device to control the smart devices in the home. An occupant may use their registered device 166 to remotely control the smart devices of the home, such as when the occupant is at work or on vacation. The occupant may also use their registered device to control the smart devices when the occupant is actually located inside the home, such as when the occupant is sitting on a couch inside the home. It should be appreciated that instead of or in addition to registering devices 166, the smart home environment 100 may make inferences about which individuals live in the home and are therefore occupants and which devices 166 are associated with those individuals. As such, the smart home environment may “learn” who is an occupant and permit the devices 166 associated with those individuals to control the smart devices of the home.
In some implementations, in addition to containing processing and sensing capabilities, devices 102, 104, 106, 108, 110, 112, 114, 116, 118, 120, and/or 122 (collectively referred to as “the smart devices”) are capable of data communications and information sharing with other smart devices, a central server or cloud-computing system, and/or other devices that are network-connected. Data communications may be carried out using any of a variety of custom or standard wireless protocols (e.g., IEEE 802.15.4, Wi-Fi, ZigBee, 6LoWPAN, Thread, Z-Wave, Bluetooth Smart, ISA100.11a, WirelessHART, MiWi, etc.) and/or any of a variety of custom or standard wired protocols (e.g., Ethernet, HomePlug, etc.), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document.
In some implementations, the smart devices serve as wireless or wired repeaters. In some implementations, a first one of the smart devices communicates with a second one of the smart devices via a wireless router. The smart devices may further communicate with each other via a connection (e.g., network interface 160) to a network, such as the Internet 162. Through the Internet 162, the smart devices may communicate with a smart home provider server system 164 (also called a central server system and/or a cloud-computing system herein). The smart home provider server system 164 may be associated with a manufacturer, support entity, or service provider associated with the smart device(s). In some implementations, a user is able to contact customer support using a smart device itself rather than needing to use other communication means, such as a telephone or Internet-connected computer. In some implementations, software updates are automatically sent from the smart home provider server system 164 to smart devices (e.g., when available, when purchased, or at routine intervals).
In some implementations, the network interface 160 includes a conventional network device (e.g., a router), and the smart home environment 100 of
In some implementations, some low-power nodes are incapable of bidirectional communication. These low-power nodes send messages, but they are unable to “listen”. Thus, other devices in the smart home environment 100, such as the spokesman nodes, cannot send information to these low-power nodes.
In some implementations, some low-power nodes are capable of only a limited bidirectional communication. For example, other devices are able to communicate with the low-power nodes only during a certain time period.
As described, in some implementations, the smart devices serve as low-power and spokesman nodes to create a mesh network in the smart home environment 100. In some implementations, individual low-power nodes in the smart home environment regularly send out messages regarding what they are sensing, and the other low-powered nodes in the smart home environment—in addition to sending out their own messages—forward the messages, thereby causing the messages to travel from node to node (i.e., device to device) throughout the smart home network 202. In some implementations, the spokesman nodes in the smart home network 202, which are able to communicate using a relatively high-power communication protocol, such as IEEE 802.11, are able to switch to a relatively low-power communication protocol, such as IEEE 802.15.4, to receive these messages, translate the messages to other communication protocols, and send the translated messages to other spokesman nodes and/or the smart home provider server system 164 (using, e.g., the relatively high-power communication protocol). Thus, the low-powered nodes using low-power communication protocols are able to send and/or receive messages across the entire smart home network 202, as well as over the Internet 162 to the smart home provider server system 164. In some implementations, the mesh network enables the smart home provider server system 164 to regularly receive data from most or all of the smart devices in the home, make inferences based on the data, facilitate state synchronization across devices within and outside of the smart home network 202, and send commands to one or more of the smart devices to perform tasks in the smart home environment.
As described, the spokesman nodes and some of the low-powered nodes are capable of “listening.” Accordingly, users, other devices, and/or the smart home provider server system 164 may communicate control commands to the low-powered nodes. For example, a user may use the electronic device 166 (e.g., a smart phone) to send commands over the Internet to the smart home provider server system 164, which then relays the commands to one or more spokesman nodes in the smart home network 202. The spokesman nodes may use a low-power protocol to communicate the commands to the low-power nodes throughout the smart home network 202, as well as to other spokesman nodes that did not receive the commands directly from the smart home provider server system 164.
In some implementations, a smart nightlight 170 (
Other examples of low-power nodes include battery-operated versions of the smart hazard detectors 104. These smart hazard detectors 104 are often located in an area without access to constant and reliable power and may include any number and type of sensors, such as smoke/fire/heat sensors (e.g., thermal radiation sensors), carbon monoxide/dioxide sensors, occupancy/motion sensors, ambient light sensors, ambient temperature sensors, humidity sensors, and the like. Furthermore, smart hazard detectors 104 may send messages that correspond to each of the respective sensors to the other devices and/or the smart home provider server system 164, such as by using the mesh network as described above.
Examples of spokesman nodes include smart doorbells 106, smart thermostats 102, smart wall switches 108, and smart wall plugs 110. These devices are often located near and connected to a reliable power source, and therefore may include more power-consuming components, such as one or more communication chips capable of bidirectional communication in a variety of protocols.
In some implementations, the smart home environment 100 includes service robots 168 (
As explained above with reference to
In some implementations, the devices and services platform 300 communicates with and collects data from the smart devices of the smart home environment 100. In addition, in some implementations, the devices and services platform 300 communicates with and collects data from a plurality of smart home environments across the world. For example, the smart home provider server system 164 collects home data 302 from the devices of one or more smart home environments 100, where the devices may routinely transmit home data or may transmit home data in specific instances (e.g., when a device queries the home data 302). Example collected home data 302 includes, without limitation, power consumption data, blackbody radiation data, occupancy data, HVAC settings and usage data, carbon monoxide levels data, carbon dioxide levels data, volatile organic compounds levels data, sleeping schedule data, cooking schedule data, inside and outside temperature humidity data, television viewership data, inside and outside noise level data, pressure data, video data, etc.
In some implementations, the smart home provider server system 164 provides one or more services 304 to smart homes and/or third parties. Example services 304 include, without limitation, software updates, customer support, sensor data collection/logging, remote access, remote or distributed control, and/or use suggestions (e.g., based on collected home data 302) to improve performance, reduce utility cost, increase safety, etc. In some implementations, data associated with the services 304 is stored at the smart home provider server system 164, and the smart home provider server system 164 retrieves and transmits the data at appropriate times (e.g., at regular intervals, upon receiving a request from a user, etc.).
In some implementations, the extensible devices and services platform 300 includes a processing engine 306, which may be concentrated at a single server or distributed among several different computing entities without limitation. In some implementations, the processing engine 306 includes engines configured to receive data from the devices of smart home environments 100 (e.g., via the Internet 162 and/or a network interface 160), to index the data, to analyze the data and/or to generate statistics based on the analysis or as part of the analysis. In some implementations, the analyzed data is stored as derived home data 308.
Results of the analysis or statistics may thereafter be transmitted back to the device that provided home data used to derive the results, to other devices, to a server providing a webpage to a user of the device, or to other non-smart device entities. In some implementations, usage statistics, usage statistics relative to use of other devices, usage patterns, and/or statistics summarizing sensor readings are generated by the processing engine 306 and transmitted. The results or statistics may be provided via the Internet 162. In this manner, the processing engine 306 may be configured and programmed to derive a variety of useful information from the home data 302. A single server may include one or more processing engines.
The derived home data 308 may be used at different granularities for a variety of useful purposes, ranging from explicit programmed control of the devices on a per-home, per-neighborhood, or per-region basis (for example, demand-response programs for electrical utilities), to the generation of inferential abstractions that may assist on a per-home basis (for example, an inference may be drawn that the homeowner has left for vacation and so security detection equipment may be put on heightened sensitivity), to the generation of statistics and associated inferential abstractions that may be used for government or charitable purposes. For example, processing engine 306 may generate statistics about device usage across a population of devices and send the statistics to device users, service providers or other entities (e.g., entities that have requested the statistics and/or entities that have provided monetary compensation for the statistics).
In some implementations, to encourage innovation and research and to increase products and services available to users, the devices and services platform 300 exposes a range of application programming interfaces (APIs) 310 to third parties, such as charities 314, governmental entities 316 (e.g., the Food and Drug Administration or the Environmental Protection Agency), academic institutions 318 (e.g., university researchers), businesses 320 (e.g., providing device warranties or service to related equipment, targeting advertisements based on home data), utility companies 324, and other third parties. The APIs 310 are coupled to and permit third-party systems to communicate with the smart home provider server system 164, including the services 304, the processing engine 306, the home data 302, and the derived home data 308. In some implementations, the APIs 310 allow applications executed by the third parties to initiate specific data processing tasks that are executed by the smart home provider server system 164, as well as to receive dynamic updates to the home data 302 and the derived home data 308.
For example, third parties may develop programs and/or applications (e.g., web applications or mobile applications) that integrate with the smart home provider server system 164 to provide services and information to users. Such programs and applications may be, for example, designed to help users reduce energy consumption, to preemptively service faulty equipment, to prepare for high service demands, to track past service performance, etc., and/or to perform other beneficial functions or tasks.
In some implementations, processing engine 306 includes a challenges/rules/compliance/rewards paradigm 410d that informs a user of challenges, competitions, rules, compliance regulations and/or rewards and/or that uses operation data to determine whether a challenge has been met, a rule or regulation has been complied with and/or a reward has been earned. The challenges, rules, and/or regulations may relate to efforts to conserve energy, to live safely (e.g., reducing the occurrence of heat-source alerts) (e.g., reducing exposure to toxins or carcinogens), to conserve money and/or equipment life, to improve health, etc. For example, one challenge may involve participants turning down their thermostat by one degree for one week. Those participants that successfully complete the challenge are rewarded, such as with coupons, virtual currency, status, etc. Regarding compliance, an example involves a rental-property owner making a rule that no renters are permitted to access certain owner's rooms. The devices in the room having occupancy sensors may send updates to the owner when the room is accessed.
In some implementations, processing engine 306 integrates or otherwise uses extrinsic information 412 from extrinsic sources to improve the functioning of one or more processing paradigms. Extrinsic information 412 may be used to interpret data received from a device, to determine a characteristic of the environment near the device (e.g., outside a structure that the device is enclosed in), to determine services or products available to the user, to identify a social network or social-network information, to determine contact information of entities (e.g., public-service entities such as an emergency-response team, the police or a hospital) near the device, to identify statistical or environmental conditions, trends or other information associated with a home or neighborhood, and so forth.
In some implementations, the smart home provider server system 164 or a component thereof serves as the hub device server system 508; the hub device server system 508 is a part or component of the smart home provider server system 164. In some implementations, the hub device server system 508 is a dedicated video processing server that provides video processing services to video sources and client devices 504 independent of other services provided by the hub device server system 508. An example of a video processing server is described below with reference to
In some implementations, each of the video sources 522 includes one or more video cameras 118 that capture video and send the captured video to the hub device server system 508 substantially in real-time. In some implementations, each of the video sources 522 optionally includes a controller device (not shown) that serves as an intermediary between the one or more cameras 118 and the hub device server system 508. The controller device receives the video data from the one or more cameras 118, optionally performs some preliminary processing on the video data, and sends the video data to the hub device server system 508 on behalf of the one or more cameras 118 substantially in real-time. In some implementations, each camera has its own on-board processing capabilities to perform some preliminary processing on the captured video data before sending the processed video data (along with metadata obtained through the preliminary processing) to the controller device and/or the hub device server system 508.
In some implementations, a camera 118 of a video source 522 captures video at a first resolution (e.g., 720P and/or 1080P) and/or a first frame rate (24 frames per second), and sends the captured video to the hub device server system 508 at both the first resolution (e.g., the original capture resolution(s), the high-quality resolution(s) such as 1080P and/or 720P) and the first frame rate, and at a second, different resolution (e.g., 180P) and/or a second frame rate (e.g., 5 frames per second or 10 frames per second). For example, the camera 118 captures a video 523-1 at 720P and/or 1080P resolution (the camera 118 may capture a video at 1080P and create a downscaled 720P version, or capture at both 720P and 1080P). The video source 522 creates a second (or third), rescaled (and optionally at a different frame rate than the version 523-1) version 525-1 of the captured video at 180P resolution, and transmits both the original captured version 523-1 (i.e., 1080P and/or 720P) and the rescaled version 525-1 (i.e., the 180P version) to the hub device server system 508 for storage. In some implementations, the rescaled version has a lower resolution, and optionally a lower frame rate, than the original captured video. The hub device server system 508 transmits the original captured version or the rescaled version to a client 504, depending on the context. For example, the hub device server system 508 transmits the rescaled version when transmitting multiple videos to the same client device 504 for concurrent monitoring by the user, and transmits the original captured version in other contexts. In some implementations, the hub device server system 508 downscales the original captured version to a lower resolution, and transmits the downscaled version.
In some other implementations, a camera 118 of a video source 522 captures video at a first resolution (e.g., 720P and/or 1080P) and/or a first frame rate, and sends the captured video to the hub device server system 508 at the first resolution (e.g., the original capture resolution(s); the high-quality resolution(s) such as 1080P and/or 720P) and first frame rate for storage. When the hub device server system 508 transmits the video to a client device, the hub device server system 508 may downscale the video to a second, lower resolution (e.g., 180P) and/or second, lower frame rate for the transmission, depending on the context. For example, the hub device server system 508 transmits the downscaled version when transmitting multiple videos to the same client device 504 for concurrent monitoring by the user, and transmits the original captured version in other contexts.
As shown in
In some implementations, the server-side module 506 includes one or more processors 512, a video storage database 514, device and account databases 516, an I/O interface to one or more client devices 518, and an I/O interface to one or more video sources 520. The I/O interface to one or more clients 518 facilitates the client-facing input and output processing for the server-side module 506. In some implementations, the I/O interface to clients 518 or a transcoding proxy computer (not shown) rescales (e.g., downscales) and/or changes the frame rate of video for transmission to a client 504. The databases 516 store a plurality of profiles for reviewer accounts registered with the video processing server, where a respective user profile includes account credentials for a respective reviewer account, and one or more video sources linked to the respective reviewer account. The I/O interface to one or more video sources 520 facilitates communications with one or more video sources 522 (e.g., groups of one or more cameras 118 and associated controller devices). The video storage database 514 stores raw video data received from the video sources 522, as well as various types of metadata, such as motion events, event categories, event category models, event filters, and event masks, for use in data processing for event monitoring and review for each reviewer account.
In some implementations, the server-side module 506 receives information regarding alert events detected by other smart devices 204 (e.g., hazards, sound, vibration, motion). In accordance with the alert event information, the server-side module 506 instructs one or more video sources 522 in the smart home environment 100 where the alert event is detected to capture video and/or associate with the alert event video, received from the video sources 522 in the same smart home environment 100, that is contemporaneous or proximate in time with the alert event.
Examples of a representative client device 504 include, but are not limited to, a handheld computer, a wearable computing device, a personal digital assistant (PDA), a tablet computer, a laptop computer, a desktop computer, a cellular telephone, a smart phone, an enhanced general packet radio service (EGPRS) mobile phone, a media player, a navigation device, a game console, a television, a remote control, a point-of-sale (POS) terminal, vehicle-mounted computer, an ebook reader, or a combination of any two or more of these data processing devices or other data processing devices. For example, client devices 504-1, 504-2, and 504-m are a smart phone, a tablet computer, and a laptop computer, respectively.
Examples of the one or more networks 162 include local area networks (LAN) and wide area networks (WAN) such as the Internet. The one or more networks 162 are, optionally, implemented using any known network protocol, including various wired or wireless protocols, such as Ethernet, Universal Serial Bus (USB), FIREWIRE, Long Term Evolution (LTE), Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Wi-Fi, voice over Internet Protocol (VoW), Wi-MAX, or any other suitable communication protocol.
In some implementations, the hub device server system 508 is implemented on one or more standalone data processing apparatuses or a distributed network of computers. In some implementations, the hub device server system 508 also employs various virtual devices and/or services of third party service providers (e.g., third-party cloud service providers) to provide the underlying computing resources and/or infrastructure resources of the hub device server system 508. In some implementations, the hub device server system 508 includes, but is not limited to, a handheld computer, a tablet computer, a laptop computer, a desktop computer, or a combination of any two or more of these data processing devices or other data processing devices.
The server-client environment 500 shown in
It should be understood that operating environment 500 that involves the hub device server system 508, the video sources 522 and the video cameras 118 is merely an example. Many aspects of operating environment 500 are generally applicable in other operating environments in which a server system provides data processing for monitoring and facilitating review of data captured by other types of electronic devices (e.g., smart thermostats 102, smart hazard detectors 104, smart doorbells 106, smart wall plugs 110, appliances 112 and the like).
The electronic devices, the client devices or the server system communicate with each other using the one or more communication networks 162. In an example smart home environment, two or more devices (e.g., the network interface device 160, the hub device 180, and the client devices 504-m) are located in close proximity to each other, such that they could be communicatively coupled in the same sub-network 162A via wired connections, a WLAN or a Bluetooth Personal Area Network (PAN). The Bluetooth PAN is optionally established based on classical Bluetooth technology or Bluetooth Low Energy (BLE) technology. This smart home environment further includes one or more other radio communication networks 162B through which at least some of the electronic devices of the video sources 522-n exchange data with the hub device 180. Alternatively, in some situations, some of the electronic devices of the video sources 522-n communicate with the network interface device 160 directly via the same sub-network 162A that couples devices 160, 180 and 504-m. In some implementations (e.g., in the network 162C), both the client device 504-m and the electronic devices of the video sources 522-n communicate directly via the network(s) 162 without passing the network interface device 160 or the hub device 180.
In some implementations, during normal operation, the network interface device 160 and the hub device 180 communicate with each other to form a network gateway through which data are exchanged with the electronic device of the video sources 522-n. As explained above, the network interface device 160 and the hub device 180 optionally communicate with each other via a sub-network 162A.
In some implementations, the hub device 180 is omitted, and the functionality of the hub device 180 is performed by the hub device server system 508, video server system 552, or smart home provider server system 164.
In some implementations, the hub device server system 508 is, or includes, a dedicated video processing server.
In some implementations, the smart home provider server system 164 or a component thereof serves as the video server system 552; the video server system 552 is a part or component of the smart home provider server system 164. In some implementations, the video server system 552 is separate from the smart home provider server system 164, and provides video processing services to video sources 522 and client devices 504 independent of other services provided by the smart home provider server system 164. In some implementations, the smart home provider server system 164 and the video server system 552 are separate but communicate information with each other to provide functionality to users. For example, a detection of a hazard may be communicated by the smart home provider server system 164 to the video server system 552, and the video server system 552, in accordance with the communication regarding the detection of the hazard, records, processes, and/or provides video associated with the detected hazard.
In some implementations, each of the video sources 522 includes one or more video cameras 118 that capture video and send the captured video to the video server system 552 substantially in real-time. In some implementations, each of the video sources 522 optionally includes a controller device (not shown) that serves as an intermediary between the one or more cameras 118 and the video server system 552. The controller device receives the video data from the one or more cameras 118, optionally, performs some preliminary processing on the video data, and sends the video data to the video server system 552 on behalf of the one or more cameras 118 substantially in real-time. In some implementations, each camera has its own on-board processing capabilities to perform some preliminary processing on the captured video data before sending the processed video data (along with metadata obtained through the preliminary processing) to the controller device and/or the video server system 552.
In some implementations, a camera 118 of a video source 522 captures video at a first resolution (e.g., 720P and/or 1080P) and/or a first frame rate (24 frames per second), and sends the captured video to the video server system 552 at both the first resolution (e.g., the original capture resolution(s), the high-quality resolution(s)) and the first frame rate, and a second, different resolution (e.g., 180P) and/or a second frame rate (e.g., 5 frames per second or 10 frames per second). For example, the camera 118 captures a video 523-1 at 720P and/or 1080P resolution (the camera 118 may capture a video at 1080P and create a downscaled 720P version, or capture at both 720P and 1080P). The video source 522 creates a second (or third), rescaled (and optionally at a different frame rate than the version 523-1) version 525-1 of the captured video at 180P resolution, and transmits both the original captured version 523-1 (i.e., 1080P and/or 720P) and the rescaled version 525-1 (i.e., the 180P version) to the video server system 552 for storage. In some implementations, the rescaled version has a lower resolution, and optionally a lower frame rate, than the original captured video. The video server system 552 transmits the original captured version or the rescaled version to a client 504, depending on the context. For example, the video server system 552 transmits the rescaled version when transmitting multiple videos to the same client device 504 for concurrent monitoring by the user, and transmits the original captured version in other contexts. In some implementations, the video server system 552 downscales the original captured version to a lower resolution, and transmits the downscaled version.
In some other implementations, a camera 118 of a video source 522 captures video at a first resolution (e.g., 720P and/or 1080P)) and/or a first frame rate, and sends the captured video to the video server system 552 at the first resolution (e.g., the original capture resolution(s), the high-quality resolution(s) such as 1080P and/or 720P) and the first fame rate for storage. When the video server system 552 transmits the video to a client device, the video server system 552 may downscale the video to a second, lower resolution (e.g., 180P) and/or second, lower frame rate for the transmission, depending on the context. For example, the video server system 552 transmits the downscaled version when transmitting multiple videos to the same client device 504 for concurrent monitoring by the user, and transmits the original captured version in other contexts.
As shown in
In some implementations, the video server 554 includes one or more processors 512, a video storage database 514, and device and account databases 516. In some implementations, the video server system 552 also includes a client interface server 556 and a camera interface server 558. The client interface server 556 provides an I/O interface to one or more client devices 504, and the camera interface server 558 provides an I/O interface to one or more video sources 520. The client interface server 556 facilitates the client-facing input and output processing for the video server system 552. For example, the client interface server 556 generates web pages for reviewing and monitoring video captured by the video sources 522 in a web browser application at a client 504. In some implementations, the client interface server 556 or a transcoding proxy computer rescales (e.g., downscales) and/or changes the frame rate of video for transmission to a client 504. In some implementations, the client interface server 504 also serves as the transcoding proxy. The databases 516 store a plurality of profiles for reviewer accounts registered with the video processing server, where a respective user profile includes account credentials for a respective reviewer account, and one or more video sources linked to the respective reviewer account. The camera interface server 558 facilitates communications with one or more video sources 522 (e.g., groups of one or more cameras 118 and associated controller devices). The video storage database 514 stores raw video data received from the video sources 522, as well as various types of metadata, such as motion events, event categories, event category models, event filters, event masks, alert events, and camera histories, for use in data processing for event monitoring and review for each reviewer account.
In some implementations, the video server system 552 receives information regarding alert events detected by other smart devices 204 (e.g., hazards, sound, vibration, motion. In accordance with the alert event information, the video server system 552 instructs one or more video sources 522 in the smart home environment 100 where the alert event is detected to capture video and/or associate with the alert event video, received from the video sources 522 in the same smart home environment 100, that is contemporaneous or proximate in time with the alert event.
Examples of a representative client device 504 include, but are not limited to, a handheld computer, a wearable computing device, a personal digital assistant (PDA), a tablet computer, a laptop computer, a desktop computer, a cellular telephone, a smart phone, an enhanced general packet radio service (EGPRS) mobile phone, a media player, a navigation device, a game console, a television, a remote control, a point-of-sale (POS) terminal, vehicle-mounted computer, an ebook reader, or a combination of any two or more of these data processing devices or other data processing devices. For example, client devices 504-1, 504-2, and 504-m are a smart phone, a tablet computer, and a laptop computer, respectively.
Examples of the one or more networks 162 include local area networks (LAN) and wide area networks (WAN) such as the Internet. The one or more networks 162 are, optionally, implemented using any known network protocol, including various wired or wireless protocols, such as Ethernet, Universal Serial Bus (USB), FIREWIRE, Long Term Evolution (LTE), Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Wi-Fi, voice over Internet Protocol (VoW), Wi-MAX, or any other suitable communication protocol.
In some implementations, the video server system 552 is implemented on one or more standalone data processing apparatuses or a distributed network of computers. In some implementations, the video server 554, the client interface server 556, and the camera interface server 558 are each respectively implemented on one or more standalone data processing apparatuses or a distributed network of computers. In some implementations, the video server system 552 also employs various virtual devices and/or services of third party service providers (e.g., third-party cloud service providers) to provide the underlying computing resources and/or infrastructure resources of the video server system 552. In some implementations, the video server system 552 includes, but is not limited to, a handheld computer, a tablet computer, a laptop computer, a desktop computer, or a combination of any two or more of these data processing devices or other data processing devices.
The server-client environment 550 shown in
It should be understood that operating environment 550 that involves the video server system 552, the video sources 522 and the video cameras 118 is merely an example. Many aspects of operating environment 550 are generally applicable in other operating environments in which a server system provides data processing for monitoring and facilitating review of data captured by other types of electronic devices (e.g., smart thermostats 102, smart hazard detectors 104, smart doorbells 106, smart wall plugs 110, appliances 112 and the like).
The electronic devices, the client devices or the server system communicate with each other using the one or more communication networks 162. In an example smart home environment, two or more devices (e.g., the network interface device 160, the hub device 180, and the client devices 504-m) are located in close proximity to each other, such that they could be communicatively coupled in the same sub-network 162A via wired connections, a WLAN or a Bluetooth Personal Area Network (PAN). The Bluetooth PAN is optionally established based on classical Bluetooth technology or Bluetooth Low Energy (BLE) technology. This smart home environment further includes one or more other radio communication networks 162B through which at least some of the electronic devices of the video sources 522-n exchange data with the hub device 180. Alternatively, in some situations, some of the electronic devices of the video sources 522-n communicate with the network interface device 160 directly via the same sub-network 162A that couples devices 160, 180 and 504-m. In some implementations (e.g., in the network 162C), both the client device 504-m and the electronic devices of the video sources 522-n communicate directly via the network(s) 162 without passing the network interface device 160 or the hub device 180.
In some implementations, during normal operation, the network interface device 160 and the hub device 180 communicate with each other to form a network gateway through which data are exchanged with the electronic device of the video sources 522-n. As explained above, the network interface device 160 and the hub device 180 optionally communicate with each other via a sub-network 162A.
In some implementations, a video source 522 may be private (e.g., its captured videos and history are accessible only to the associated user/account), public (e.g., its captured videos and history are accessible by anyone), or shared (e.g., its captured videos and history are accessible only to the associated user/account and other specific users/accounts with whom the associated user has authorized access (e.g., by sharing with the other specific users)). Whether a video source 522 is private, public, or shared is configurable by the associated user.
In some implementations, the camera 118 also performs preliminary motion detection on video captured by the camera 118. For example, the camera 118 analyzes the captured video for significant changes in pixels. When motion is detected by the preliminary motion detection, the camera 118 transmits information to the hub device server system 508 or video server system 552 informing the server system of the preliminary detected motion. The hub device server system 508 or video server system 552, in accordance with the information of the detected motion, may activate sending of a motion detection notification to a client device 504, log the preliminary detected motion as an alert event, and/or perform additional analysis of the captured video to confirm and/or classify the preliminary detected motion.
The hub device 180 optionally includes one or more built-in sensors (not shown), including, for example, one or more thermal radiation sensors, ambient temperature sensors, humidity sensors, IR sensors, occupancy sensors (e.g., using RFID sensors), ambient light sensors, motion detectors, accelerometers, and/or gyroscopes.
The radios 640 enables one or more radio communication networks in the smart home environments, and allows a hub device to communicate with smart devices. In some implementations, the radios 640 are capable of data communications using any of a variety of custom or standard wireless protocols (e.g., IEEE 802.15.4, Wi-Fi, ZigBee, 6LoWPAN, Thread, Z-Wave, Bluetooth Smart, ISA100.11a, WirelessHART, MiWi, etc.) custom or standard wired protocols (e.g., Ethernet, HomePlug, etc.), and/or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document.
Communication interfaces 604 include, for example, hardware capable of data communications using any of a variety of custom or standard wireless protocols (e.g., IEEE 802.15.4, Wi-Fi, ZigBee, 6LoWPAN, Thread, Z-Wave, Bluetooth Smart, ISA100.11a, WirelessHART, MiWi, etc.) and/or any of a variety of custom or standard wired protocols (e.g., Ethernet, HomePlug, etc.), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document.
Memory 606 includes high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid state memory devices; and, optionally, includes non-volatile memory, such as one or more magnetic disk storage devices, one or more optical disk storage devices, one or more flash memory devices, or one or more other non-volatile solid state storage devices. Memory 606, or alternatively the non-volatile memory within memory 606, includes a non-transitory computer readable storage medium. In some implementations, memory 606, or the non-transitory computer readable storage medium of memory 606, stores the following programs, modules, and data structures, or a subset or superset thereof:
Each of the above identified elements (e.g., modules stored in memory 206 of hub device 180) may be stored in one or more of the previously mentioned memory devices (e.g., the memory of any of the smart devices in smart home environment 100,
Each of the above identified elements may be stored in one or more of the previously mentioned memory devices, and corresponds to a set of instructions for performing a function described above. The above identified modules or programs (i.e., sets of instructions) need not be implemented as separate software programs, procedures, or modules, and thus various subsets of these modules may be combined or otherwise re-arranged in various implementations. In some implementations, memory 706, optionally, stores a subset of the modules and data structures identified above. Furthermore, memory 706, optionally, stores additional modules and data structures not described above.
Video data stored in the video storage database 7320 includes high-quality versions 7321 and low-quality versions 7322 of videos associated with each of the video sources 522. High-quality video 7321 includes video in relatively high resolutions (e.g., 720P and/or 1080P) and relatively high frame rates (e.g., 24 frames per second). Low-quality video 7322 includes video in relatively low resolutions (e.g., 180P) and relatively low frame rates (e.g., 5 frames per second, 10 frames per second).
Each of the above identified elements may be stored in one or more of the previously mentioned memory devices, and corresponds to a set of instructions for performing a function described above. The above identified modules or programs (i.e., sets of instructions) need not be implemented as separate software programs, procedures, or modules, and thus various subsets of these modules may be combined or otherwise re-arranged in various implementations. In some implementations, memory 722, optionally, stores a subset of the modules and data structures identified above. Furthermore, memory 722, optionally, stores additional modules and data structures not described above.
Each of the above identified elements may be stored in one or more of the previously mentioned memory devices, and corresponds to a set of instructions for performing a function described above. The above identified modules or programs (i.e., sets of instructions) need not be implemented as separate software programs, procedures, or modules, and thus various subsets of these modules may be combined or otherwise re-arranged in various implementations. In some implementations, memory 738, optionally, stores a subset of the modules and data structures identified above. Furthermore, memory 738, optionally, stores additional modules and data structures not described above.
Each of the above identified elements may be stored in one or more of the previously mentioned memory devices, and corresponds to a set of instructions for performing a function described above. The above identified modules or programs (i.e., sets of instructions) need not be implemented as separate software programs, procedures, or modules, and thus various subsets of these modules may be combined or otherwise re-arranged in various implementations. In some implementations, memory 752, optionally, stores a subset of the modules and data structures identified above. Furthermore, memory 752, optionally, stores additional modules and data structures not described above.
In some implementations, at least some of the functions of the video server 554, client interface server 556, and camera interface server 558 are performed by the hub device server system 508, and the corresponding modules and sub-modules of these functions may be included in the hub device server system 508. In some implementations, at least some of the functions of the hub device server system 508 are performed by the video server 554, client interface server 556, and/or camera interface server 558, and the corresponding modules and sub-modules of these functions may be included in the video server 554, client interface server 556, and/or camera interface server 558.
Memory 806 includes high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid state memory devices; and, optionally, includes non-volatile memory, such as one or more magnetic disk storage devices, one or more optical disk storage devices, one or more flash memory devices, or one or more other non-volatile solid state storage devices. Memory 806, optionally, includes one or more storage devices remotely located from one or more processing units 802. Memory 806, or alternatively the non-volatile memory within memory 806, includes a non-transitory computer readable storage medium. In some implementations, memory 806, or the non-transitory computer readable storage medium of memory 806, stores the following programs, modules, and data structures, or a subset or superset thereof:
Video data cache 8304 includes cached video/image data for respective cameras associated with a user of the client device 804. For example, as shown in
Blurred image data 832 includes sets of progressively blurred images for respective cameras. For example, as shown in
In some implementations, the client device 504 caches camera history as well as video data 8304. For example, whenever the client device 504 receives camera events history 7328 data from the video server 554, the most recent camera events history (e.g., history from the past two hours, the most recent 20 events) is cached at the client device (e.g., in client data 830). This cached history data may be accessed for quick display of camera history information (e.g., in user interface 1304 (
In some implementations, the client-side module 502 and user interface module 826 are parts, modules, or components of a particular application 824 (e.g., a smart home management application).
Each of the above identified elements may be stored in one or more of the previously mentioned memory devices, and corresponds to a set of instructions for performing a function described above. The above identified modules or programs (i.e., sets of instructions) need not be implemented as separate software programs, procedures, modules or data structures, and thus various subsets of these modules may be combined or otherwise re-arranged in various implementations. In some implementations, memory 806, optionally, stores a subset of the modules and data structures identified above. Furthermore, memory 806, optionally, stores additional modules and data structures not described above.
In some implementations, at least some of the functions of the hub device server system 508 or the video server system 552 are performed by the client device 504, and the corresponding sub-modules of these functions may be located within the client device 504 rather than the hub device server system 508 or video server system 552. In some implementations, at least some of the functions of the client device 504 are performed by the hub device server system 508 or video server system 552, and the corresponding sub-modules of these functions may be located within the hub device server system 508 or video server system 552 rather than the client device 504. The client device 504 and the hub device server system 508 or video server system 552 shown in
The built-in sensors 990 include, for example, one or more thermal radiation sensors, ambient temperature sensors, humidity sensors, IR sensors, occupancy sensors (e.g., using RFID sensors), ambient light sensors, motion detectors, accelerometers, and/or gyroscopes.
The radios 940 enable one or more radio communication networks in the smart home environments, and allow a smart device 204 to communicate with other devices. In some implementations, the radios 940 are capable of data communications using any of a variety of custom or standard wireless protocols (e.g., IEEE 802.15.4, Wi-Fi, ZigBee, 6LoWPAN, Thread, Z-Wave, Bluetooth Smart, ISA100.11a, WirelessHART, MiWi, etc.) custom or standard wired protocols (e.g., Ethernet, HomePlug, etc.), and/or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document.
Communication interfaces 904 include, for example, hardware capable of data communications using any of a variety of custom or standard wireless protocols (e.g., IEEE 802.15.4, Wi-Fi, ZigBee, 6LoWPAN, Thread, Z-Wave, Bluetooth Smart, ISA100.11a, WirelessHART, MiWi, etc.) and/or any of a variety of custom or standard wired protocols (e.g., Ethernet, HomePlug, etc.), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document.
Memory 906 includes high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid state memory devices; and, optionally, includes non-volatile memory, such as one or more magnetic disk storage devices, one or more optical disk storage devices, one or more flash memory devices, or one or more other non-volatile solid state storage devices. Memory 906, or alternatively the non-volatile memory within memory 906, includes a non-transitory computer readable storage medium. In some implementations, memory 906, or the non-transitory computer readable storage medium of memory 906, stores the following programs, modules, and data structures, or a subset or superset thereof:
Each of the above identified elements may be stored in one or more of the previously mentioned memory devices, and corresponds to a set of instructions for performing a function described above. The above identified modules or programs (i.e., sets of instructions) need not be implemented as separate software programs, procedures, or modules, and thus various subsets of these modules may be combined or otherwise re-arranged in various implementations. In some implementations, memory 906, optionally, stores a subset of the modules and data structures identified above. Furthermore, memory 906, optionally, stores additional modules and data structures not described above.
Communication interfaces 944 include, for example, hardware capable of data communications using any of a variety of custom or standard wireless protocols (e.g., IEEE 802.15.4, Wi-Fi, ZigBee, 6LoWPAN, Thread, Z-Wave, Bluetooth Smart, ISA100.11a, WirelessHART, MiWi, etc.) and/or any of a variety of custom or standard wired protocols (e.g., Ethernet, HomePlug, etc.), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document.
Memory 946 includes high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid state memory devices; and, optionally, includes non-volatile memory, such as one or more magnetic disk storage devices, one or more optical disk storage devices, one or more flash memory devices, or one or more other non-volatile solid state storage devices. Memory 946, or alternatively the non-volatile memory within memory 946, includes a non-transitory computer readable storage medium. In some implementations, memory 946, or the non-transitory computer readable storage medium of memory 946, stores the following programs, modules, and data structures, or a subset or superset thereof:
Each of the above identified elements may be stored in one or more of the previously mentioned memory devices, and corresponds to a set of instructions for performing a function described above. The above identified modules or programs (i.e., sets of instructions) need not be implemented as separate software programs, procedures, or modules, and thus various subsets of these modules may be combined or otherwise re-arranged in various implementations. In some implementations, memory 946, optionally, stores a subset of the modules and data structures identified above. Furthermore, memory 946, optionally, stores additional modules and data structures not described above. Additionally, camera 118, being an example of a smart device 204, optionally includes components and modules included in smart device 204 as shown in
Each of the above identified elements may be stored in one or more of the previously mentioned memory devices, and corresponds to a set of instructions for performing a function described above. The above identified modules or programs (i.e., sets of instructions) need not be implemented as separate software programs, procedures, or modules, and thus various subsets of these modules may be combined or otherwise re-arranged in various implementations. In some implementations, memory 1006, optionally, stores a subset of the modules and data structures identified above. Furthermore, memory 1006, optionally, stores additional modules and data structures not described above.
Furthermore, in some implementations, the functions of any of the devices and systems described herein (e.g., hub device 180, hub device server system 508, video server system 552, client device 504, smart device 204, camera 118, smart home provider server system 164) are interchangeable with one another and may be performed by any other devices or systems, where the corresponding sub-modules of these functions may additionally and/or alternatively be located within and executed by any of the devices and systems. As one example, generating of user interfaces may be performed by the user interface module 74610 (which may be located at the client interface server 556 or at the video server 554) or by the user interface module 826, depending on whether the user is accessing the video feeds and corresponding histories through a web browser 823 or an application 824 (e.g., a dedicated smart home management application) at the client device 504. The devices and systems shown in and described with respect to
The menu and settings objects 1106 and 1108, when activated by the user, provides access to an options menu or interface and a settings menu or interface for the smart home application, respectively. In some implementations, the menu object 1106 is displayed as a 3-line “hamburger menu” icon (e.g., as shown in
Thermostat objects 1112-A and 1112-B correspond to respective smart thermostats 102 in the smart home environment 100 and display the current detected temperatures and/or the set temperatures at the corresponding smart thermostats 102. “Protect” object 1114 provides access to a history of alert events (e.g., detected hazards, detected sounds, detected vibrations, operation of smart door lock 120, etc.) associated with the smart home environment 100. The user accesses the “Protect” history by activating the “Protect” object 1114 (e.g., by tapping on the “Protect” object 1114 on the touch screen 1102).
The camera objects 1116-A, 1116-B, and 1116-C correspond to respective video sources 522 (or, more particularly, respective cameras 118) within the smart home environment 100. The labels 1118-A, 1118-B, and 1118-C indicate the respective video sources 522 to which the respective camera objects 1116 correspond. For example, the camera object 1116-A corresponds to a camera 118 labeled “Outside” 1118-A.
Within a respective camera object 1116, a view of a video feed or stream from the corresponding camera is displayed. For example, a view 1120 of the video feed from the “Outside” 1118-A camera is displayed in camera object 1116-A, a view 1122 of the video feed from the “Front door” 1118-B camera is displayed in camera object 1116-B, and a view 1124 of the video feed from the “Dining room” 1118-C camera is displayed in camera object 1116-C. In some implementations, the view of a video feed is displayed in a camera object 1116 as a real-time (or near real-time), live video stream from the corresponding camera or as periodically refreshed (e.g., at a rate less than typical frame rates for video) still images. In some implementations, the view is displayed at a resolution different from the original resolution and/or frame rate in which the video was captured. For example, the video views displayed in the camera objects 1116 are displayed at an 180P (180 horizontal lines progressive scan) resolution and at a frame rate of 5 or 10 frames per second, which is different from the original capture resolution (e.g., 720P or 1080P) and the original frame rate.
In some implementations, the view displayed in a camera object 1116 is cropped from the original video to fit the size and shape of the camera object 1116, and the cropping is positioned to focus on a particular portion of the video for display. For example, view 1120 is cropped to view 1120-1 to fit into circle-shaped object 1116-A, view 1122 is cropped to view 1122-1 to fit into circle-shaped object 1116-B, and view 1124 is cropped to view 1124-1 to fit into circle-shaped object 1116-C. The cropping and focus is further illustrated in
It should be appreciated that while the camera objects 1116 are shown as circular in the drawings, the camera objects 1116 may be in other shapes (e.g., square, rectangle, etc.) or each camera object 1116 may have a distinct shape (e.g., one camera object 1116 has a circular shape, another camera object 1116 has a square shape, and so on).
Additionally, as shown in
Continuing in
In some implementations, after the view change in response to the gesture or orientation change, the views stay in their post-change states (i.e., as 1120-2, 1122-2, and 1124-2, respectively) even when the user input triggering the change is terminated (e.g., the contact 1126 is no longer detected on the touch screen 1102, the orientation of client device 504 stops changing) (e.g., as shown in
In some other implementations, after the view change in response to the gesture or orientation change, the views 1120, 1122, and 1124 automatically return or reset to their pre-change states (i.e., return to 1120-1, 1122-1, and 1124-1, respectively) even when the user input triggering the change is terminated (e.g., the contact 1126 is no longer detected on the touch screen 1102, the orientation of client device 504 stops changing). For example, the views 1120, 1122, and 1124 automatically return to views 1120-1, 1122-1, and 1124-1, respectively, after a delay (e.g., 3 seconds) after the contact 1126 is lifted off the touch screen 1102 to complete the gesture 1128. In some implementations, to prevent the automatic return to the pre-change views, the user may perform another user input during the delay period (e.g., a single tap gesture with contact 1127 near where contact 1126 was last detected). In accordance with the another user input, the views 1120-2, 1122-2, and 1124-2 are maintained. In some implementations, the user may perform an input (e.g., single tap gesture, a voice command) on a camera object 1116 to selectively maintain the view displayed in that camera object 1116 in the post-change state, while the remainder of the views return or reset to their pre-change states.
Continuing in
While the user interface objects 1134 and 1136 are displayed, the user may select the user interface object corresponding to the non-active mode to change the views 1120, 1122, and 1124 to that mode. For example, in
The user may want to adjust the view(s) displayed in particular camera objects 1116, rather than adjusting all of the views. In some implementations, the smart home application facilitates selection of particular camera objects 1116 by the user.
Multiple camera objects 1116 may be selected, as shown in
After one or more camera objects 1116 are selected, a user input to adjust the views in the selected camera objects 1116 may be performed. For example, a swipe gesture (e.g., swipe gesture 1148 just below the camera objects 1116 with contact 1146) or a change 1149 in the orientation of the client device 504 may be detected. In response to the user input, the views 1120-1 and 1122-1 in camera objects 1116-A and 1116-B, respectively, are changed to views 1120-2 and 1122-2, respectively. View 1124-1, displayed in the not-selected camera object 1116-C, is maintained.
In some implementations, after the view change in response to the gesture or orientation change, the selected camera objects 1116 are deselected and the changed views stay in their post-change states (i.e., as 1120-2 and 1122-2, respectively) even when the user input triggering the change is terminated (e.g., the contact 1146 is no longer detected on the touch screen 1102, the orientation of client device 504 stops changing). In some implementations, the user may perform an input (e.g., shaking the client device 504 (detected by the accelerometer 892), a predefined gesture (e.g., double tap or a tap and hold in an area in user interface 1104 near and away from the camera objects 1116), a voice command) to force the smart home application to reset the changed views back to views 1120-1 and 1122-1. In some implementations, the user may perform an input (e.g., single tap gesture, a voice command) on a camera object 1116 to selectively reset the changed view displayed in that camera object 1116 back to the pre-change state, while the remainder of the changed views remain in their post-change states.
In some other implementations, after the view change in response to the gesture or orientation change, the selected camera objects 1116 are deselected and the views 1120 and 1122 automatically return or reset to their pre-change states (i.e., return to 1120-1 and 1122-1, respectively) even when the user input triggering the change is terminated (e.g., the contact 1146 is no longer detected on the touch screen 1102, the orientation of client device 504 stops changing). For example, the views 1120 and 1122 automatically return to views 1120-1 and 1122-1, respectively, after a delay (e.g., 3 seconds) after the contact 1146 is lifted off the touch screen 1102 to complete the gesture 1148. In some implementations, to prevent the automatic return to the pre-change views for particular ones of the selected camera objects 1116, the user may perform one or more user inputs during the delay period on the camera object(s) 1116 with the views the user wishes to maintain in the post-change state. For example, in
While one or more of the camera objects 1116 are selected, the display mode of the views in the selected camera objects 1116 may be changed.
While the user interface objects 1134 and 1136 are displayed, the user may select the user interface object corresponding to the non-active mode to change the views displayed in the selected camera objects 1116-A and 1116-B to that mode. For example, in
In some implementations, a user may freeze a video feed displayed in a camera object 1116.
Each of the camera objects 1116 are associated with a respective camera and its corresponding video feed. A user may perform a gesture on one of the camera objects 1116 to access a user interface that shows the video corresponding to that camera object uncropped. For example, in
The user interface 1166 also includes various controls, such as previous clip affordance 1182-A for skipping to a chronologically preceding video clip captured by the “Dining room” 1118-C camera, rewind affordance 1182-B for rewinding back in the video shown in the video region 1180, fast forward affordance 1182-C for fast forwarding in the video shown in the video region 1180, next clip affordance 1182-D for skipping to a chronologically succeeding video clip captured by the “Dining room” 1118-C camera, and live affordance 1182-E for jumping directly to the live video stream from the captured by the “Dining room” 1118-C camera. The user interface 1166 also includes a talk affordance 1184 for initiating voice functionality that includes voice input from the user that will be output by the “Dining room” 1118-C camera, an enhance affordance 1186 for initiating enhancement of the video displayed in the video region 1180, a quality indicator/affordance 1188 for switching or toggling the video quality (e.g., resolution and/or frame rate) of the video displayed in the video region 1180, and history affordance 1190 for accessing a history of camera events for the “Dining room” 1118-C camera. In response to a gesture on the history affordance (e.g., a single tap gesture on history affordance 1190 with contact 1192), a camera history user interface 1304 (
In some implementations, the views in the camera objects 1116 are displayed with blurring transitions. For example, when the smart home application is opened, the views in the camera objects 1116 are shown with a blurring transition, as shown in
In some implementations, the blurring/de-blurring includes displaying a set of progressively blurred images (e.g., 16 or 24 blurred images) from cached video/image data 8304 for the pertinent camera, and displaying these images sequentially. For example, when the smart home application is opened and a camera is connected, a de-blurring transition from a blurred view 11100 to an unblurred view 11102 involves starting from a blurred cached image from the camera and then displaying, in sequence, progressively less blurry images in the set of blurred images. Meanwhile, as the blurred images are displayed in sequence, the client device 504 receives the video feed from the camera and inserts images from the video feed under (e.g., in a lower z-layer) the blurred image. After the last blurred image is displayed, the blurred image is removed, revealing the updated images from the video feed. The set of progressively blurred images are generated from cached video/image data 8304 for the camera (in some implementations, the smart home application caches the most recent (e.g., in the last hour) video/image data from each associated camera at the client device 504 as cached video/image data 8304) using well-known blurring techniques (e.g., Gaussian blur, bokeh). For example, as shown in
In some implementations, one or more of the views displayed within the camera objects 1116 may be zoomed in or out. The zooming in or out includes zooming in or out the frames of the video feed from which the view is derived, and cropping the zoomed in/out frames if needed, thus deriving the zoomed in/out view. A view may be zoomed out to fit the video frames entirely within the camera object 1116 without cropping, or zoomed in to further focus on a particular portion of the frames.
In some implementations, the sizes of the camera objects 1116 are static; the camera objects 1116 have a fixed size. In some other implementations, the camera objects 1116 have sizes that may change. For example, the hub device server system 508 or video server system 552 analyzes the video feeds from the cameras 118 to detect motion activity occurring in the video feeds. The camera object 1116 corresponding to the video feed with the most detected activity (e.g., currently detected activity, historically detected activity over predefined period of time (e.g., within the last hour, within the last 12 hours, within the last 24 hours, etc.)) is displayed at a larger size than the other camera objects 1116. In some implementations, the sizes of camera objects 1116 are individually configurable by the user (e.g., in a settings interface accessible from the settings affordance 1108). For example, the user can configure the camera objects 1116 corresponding to cameras 118 whose video feeds he wishes to give more attention to be larger. In some implementations, the size of a camera object 1116 is automatically configured by the smart home application based on, for example, how many times the user has accessed the video feed corresponding to the camera object 1116 (e.g., by tapping on the camera object 1116 and opening the interface 1166 for the corresponding video feed, as in
In some implementations, the user interfaces illustrated in
Outside of the video region 1206, the user interface 1204 includes additional user interface objects and information. For example, the user interface 1204 includes a timeline 1208 for displaying camera events and their corresponding times and durations; a calendar affordance 1230 to jump to a particular calendar day in the timeline 1208; a time scale selector 1231 for selecting a level of detail in the timeline 1208; arrows 1232 and 1234 for scrolling backward and forward in the timeline, respectively; an activity zone affordance 1229 for accessing a list of alert event types and user-defined zones of interest for filtering the timeline by alert event type and/or zone of interest, as well as options to create or edit a zone of interest in the area monitored by the associated camera; and video clip affordance 1233 for accessing a user interface for creating user-custom video clips from video captured by the associated camera. The defining of zones of interest is described in the following U.S. patent applications filed on Oct. 8, 2014, which are incorporated by reference herein in their entirety: Ser. Nos. 14/509,999; 14/510,050; 14/510,015; 14/510,029; 14/510,007; 14/510,040; 14/510,030; 14/510,042; and 14/510,059.
The timeline 1208 shows a chronology of camera events associated with the associated camera. A camera event includes a corresponding video, one or more alert events that are associated with the video, and the chronology of the associated alert events. The alert events may be any event detected in the smart home environment 100 by a smart device 204 (e.g., detected hazard, detected sound, detected vibration, operation of a smart door lock 120, detected motion, etc.); the smart home environment 100 is configured to log and/or alert the user of detection of such events. In some implementations, alert events include motion events detected non-visually (e.g., detected by motion detectors) as well as motion events detected through video captured by a camera 118 (e.g., motion through or in a user-defined zone of interest). Detection of motion activity in a zone of interest is described in the following U.S. patent applications filed on Oct. 8, 2014, which were incorporated by reference above: Ser. Nos. 14/509,999; 14/510,050; 14/510,015; 14/510,029; 14/510,007; 14/510,040; 14/510,030; 14/510,042; and 14/510,059. In some implementations, each zone of interest is its own type of alert event; motion detected in one zone of interest and motion detected in another zone of interest are considered different types of alert events.
In some implementations, when an alert event is detected, one or more cameras 118 proximate to the detected event or proximate to the smart devices 204 that detected the event are instructed to capture video, so as to capture a visual state of one or more areas proximate in location to, and contemporaneous (or otherwise proximate in time) with, the detected alert event. The alert event is associated with the captured video.
The smart devices 204 may detect concurrent, overlapping, or sequenced alert events. Any two alert events that are in sequence with a less than a threshold amount of time (e.g., 2 seconds) between them, concurrent, or overlapping are associated with the same camera event. Thus, a camera event and its corresponding video may be associated with multiple alert events (e.g., detected sound and vibration at same time, motion detected across multiple zones of interest in sequence).
A time marker 1236 is displayed on the timeline 1208. The time marker 1236 indicates the time in focus on the timeline 1208 and in the video region 1206. In
Camera events are represented on the timeline by bars 1238 displayed over (e.g., overlaid on) the timeline 1208. Each bar 1238 has a length reflecting the duration of the camera event. For example, the camera event 1238-A is longer than the camera event 1238-B. In some implementations, the duration of a camera event is from the start of the earliest alert event in the camera event to the end of the last alert event in the camera event.
It should be appreciated that camera events may or may not be displayed as bars 1238, depending on the fineness of the time scale of the timeline 1208. For example, camera events that are too short in duration to be displayed as bars for a particular time scale (e.g., a 5 second camera event at the hours scale) may be displayed as a shaped dot on the timeline 1208.
In some implementations, one or more icons 1240 corresponding to types of alert events are displayed in or near respective camera event bars 1238 to indicate the alert events associated with the respective alert events. For example, icons 1240-A, 1240-B, and 1240-C are displayed in camera event bar 1238-A; and icons 1240-A, 1240-B, and 1240-C, and 1240-D are displayed in camera event bar 1238-B. Each icon corresponds to a respective type of alert event, and visually distinct from each other. In some implementations, the visual distinction is based on shape. For example, as shown in
In some implementations, the shape or color definitions for the icons 1240 may be automatically defined and/or user-defined. For example, shapes or colors for icons 1240 corresponding to predefined alert event types (e.g., hazard, sound, vibration, non-visual motion) are defined according to a default scheme, and shapes or colors for icons 1240 corresponding to user-defined zones of interest are defined according to the default scheme or user definition.
In some implementations, if multiple instances of a particular type of alert event were detected during a camera event, the icon 1240 corresponding to that particular type is displayed just once within the camera event bar 1238.
In some implementations, the icons 1240 displayed within a camera event bar 1238 are ordered within the camera event bar 1238. In some implementations, the ordering is based on the chronological order of the alert events in the camera event. For example, in
In some implementations, the icons 1240 within a camera event bar 1238 are ordered based on the chronological order of the most recent instances of each detected type of alert event, as just one icon is displayed for each type of alert event detected. Within the camera event bar 1238-A, an instance of the alert event of the type corresponding to icon 1240-C is the most recent alert event for the corresponding camera event and is more recent than the most recent instance of the alert event type corresponding to icon 1240-B detected for the corresponding camera event. As another example, within the camera event bar 1238-B, the most recent instance of the alert event type corresponding to icon 1240-D is more recent than the most recent instance of the alert event type corresponding to icon 1240-A, and thus icon 1240-D is displayed to the right of icon 1240-A.
In some implementations, if alert event type icons 1240 are distinguished based on color, and a camera event includes just one alert event type, then the corresponding camera event bar 1238 may be displayed with the color corresponding to the alert event type.
A user may click on (e.g., with a mouse) or tap on (e.g., with a contact on a touch screen) or hover over (e.g., with a mouse pointer) a camera event 1238 to view additional information about the camera event. For example, in
In some implementations, the time marker 1236 may be moved (e.g., dragged) along the timeline 1208 by the user to “scrub” the timeline 1208 and manually jump to a desired time in the timeline 1208.
In some implementations, the user-defined zones of interest may be displayed in the video region 1206 over the video feed 1207. For example, when affordance 1229 is activated, a filtering list of user-defined zones of interest and alert event types is displayed, as well as options to edit and create, respectively, a zone of interest (not shown). The user may select one or more of the zones and alert event types for filtering of the timeline 1208 and the camera events therein by the selected zones and alert event types. The user may also select the option to edit a zone. In response to the user selecting the option to edit a zone, the defined zones are displayed in the video region 1206 while the video feed 1207 continues to be played in video region 1206, along with a prompt for the user to select a zone for editing. For example,
In some other implementations, instead of being an affordance for opening a user interface for filtering zones of interest and alert event types, the affordance 1229 is an affordance for toggling between showing and not showing zones of interest in the video region 1206, aside from any filtering of the timeline 1208 or any option edit or create a zone of interest.
As described above, icons 1240 may be displayed within or near a camera event bar 1238.
Each camera event entry 1322, which corresponds to a respective camera event associated with the respective camera 118, includes a thumbnail 1328 (e.g., a still frame from the video associated with the camera event), an activity type identifier 1330, a timestamp 1332 and a duration indicator 1334. For example, the camera event entry 1332-A has the thumbnail 1328-A. The corresponding camera event includes motion activity (as indicated by activity type identifier 1330-A), started at 12:49 PM (as indicated by timestamp 1332-A), and lasted 12 seconds (as indicated by duration indicator 1334-A). As another example, the camera event entry 1332-B has the thumbnail 1328-B. The corresponding camera event includes motion activity (as indicated by activity type identifier 1330-B), started at 12:10 PM (as indicated by timestamp 1332-B), and lasted 29 seconds (as indicated by duration indicator 1334-B).
The activity type identifier 1330 for a camera event identifies the type of the only or primary alert event detected for the camera event. For example, in
In the separator bar 1312, the hour indicator 1316 identifies the hour of the day identified by date indicator 1314 in which the camera events corresponding to the camera event entries 1322 displayed highest (i.e., closet to the separator bar 1312) in the scrollable list at the moment are detected. Hour separator bars 1324, each of which includes an hour indicator 1326, are displayed to separate camera event entries 1322 by hour. For example, camera event entries 1322-A and 1322-B correspond to camera events that occur in the 12 PM hour, and camera event entries 1322-C, 1322-D, 1322-E, and 1322-F correspond to camera events that occur in the 11 AM hour.
As described above, the list of camera event entries 1322 is scrollable. For example, in
An individual camera event entry 1322 may be expanded to display further information about the corresponding camera event. For example,
The video player interface 1342 also displays information on the types of alert events associated with the corresponding camera event, i.e., types of alert events (including zones of interest) detected and associated with the camera event. The alert event type information includes alert event type identifiers 1350 and corresponding icons 1352. For example, in the video player interface 1342, alert event types (including zones of interest) “Table,” “Window,” and “Sound” are associated with the camera event corresponding to camera event entry 1322-E; alert events of the types “Table,” “Window,” and “Sound” were detected and associated with the corresponding video 1354 and the corresponding camera event. As with icons 1240, icons 1352 may be distinguished by shape or color associated with respective alert event types and zones. If the icons 1352 are distinguished based on color, the corresponding labels 1350 may also be displayed in the corresponding associated colors as well.
The video player interface 1342 includes the video 1354 associated with the corresponding camera event. In
In some implementations, playback of the video 1354 is automatically started when the camera event entry 1322-E is expanded into the video player interface 1342. In some other implementations, playback is manually started; playback affordance 1364 is displayed over the video 1354, as shown in
When playback of the video 1354 is complete (as indicated by the playback progress bar 1356 being completely filled 1358; in some other implementations the playback progress bar 1356 is omitted from display when the playback is complete), replay affordance 1370 and continue affordance 1372 are displayed over the video 1354. The user may perform a gesture (e.g., a single tap) on the replay affordance 1370 to have the video 1354 replayed from the start.
In some implementations, the user may perform a gesture (e.g., a single tap) on the continue affordance 1372 to replace the user interface 1304 with user interface 1166 for the associated camera 118 and play the next video from the associated camera 118 in the user interface 1166 from where the video 1354 left off.
The user may collapse the video player interface 1342 back to the camera event entry 1322-E by performing a gesture (e.g., a single tap) on an area in the video player interface 1342 outside of the video 1354 (e.g., single tap gesture with contact 1374 outside of video 1354, as shown in
In some implementations, the list of camera event entries 1322 may be filtered to highlight particular alert event types (e.g., particular zones of interest).
Each filtering criterion 1380 includes an identifier of the corresponding alert event type 1350 and icon 1352. In
In some implementations, a user selects a filtering criterion by performing a gesture (e.g., a single tap) over the desired criterion. For example, a single tap gesture with contact 1382 is detected over criterion 1380-A. In response to detecting the gesture, criterion 1380-A is checked, indicating selection, as shown in
In response to detecting the gesture on the “Done” affordance 1384, the selected filtering criteria are applied. For example, in
Multiple criteria may be selected for filtering. For example,
Entries 1322-E and 1322-F include both icons 1352-A and 1352-B, indicating that the camera events corresponding to these entries have motion detected in the “Table” 1350-A zone of interest and in the “Window” 1350-B zone of interest. In some implementations, when multiple filtering criteria are applied and an entry 1322 meets more than one of the filtering criteria, the icons 1352 corresponding to the met criteria are displayed in an order. The order is a chronological order similar to that used for icons 1240 (
As described above, the filtering criteria 1380 are alert even types, where respective zones of interest are considered as distinct alert event types.
In some other implementations, alert event type and/or zone labels 1350 and icons 1352 are displayed for each entry 1322 by default, even before any filtering. In other words, by default, each entry 1322 is displayed with its associated alert event types and zones information displayed as well. When filtering, entries that satisfy the filtering criteria are displayed with all of their associated alert event types and zones (i.e., none are omitted and none are specifically highlighted), and entries that do not meet the filtering criteria 1322 (i.e., not associated with at least one alert event type or zone selected for the filtering criteria) are not displayed. Thus for example, in
In some implementations, one or more of the functionalities described above in relation to
In an application executing at the electronic device (e.g., client device 504), the electronic device receives a plurality of video feeds, each video feed of the plurality of video feeds corresponding to a respective remote camera of a plurality of remote cameras, wherein the video feeds are received concurrently by the device from a server system communicatively coupled to the remote cameras (1402). The client device 504, for example, receives respective video feeds from multiple cameras 118 through the hub device server system 508 or video server system 552. Each of the received video feeds corresponds to a respective camera 118.
The electronic device displays a first user interface, the first user interface including a plurality of user interface objects, each user interface object of the plurality of user interface objects being associated with a respective remote camera of the remote cameras (1404). The client device 504 displays a user interface 1104 that includes one or more camera objects 1116 (
The electronic device displays in each user interface object of the plurality of user interface objects the video feed corresponding to the respective remote camera with which the user interface object is associated, wherein at least one of the video feeds is displayed with cropping (1408). The client device 504 displays in each camera object 1116 the video feed from the respective associated camera 118. For example, the video feed from the “Outside” 1118-A camera is displayed in the camera object 1116-A as view 1120, the video feed from the “Front door” 1118-B camera is displayed in the camera object 1116-B as view 1122, and the video feed from the “Dining room” 1118-C camera is displayed in the camera object 1116-C as view 1124. Each of the video feeds is displayed with cropping (e.g., as described above in relation to
In some implementations, each respective remote camera of the plurality of remote cameras has a respective field of view, and a user interface object associated with a respective remote camera has a virtual field of view relatively smaller than the respective field of view of the associated respective remote camera (1406). As shown in
In some implementations, displaying in each user interface object of the plurality of user interface objects the video feed corresponding to the respective remote camera with which the user interface object is associated comprises displaying, in a respective user interface object, periodically refreshed still images corresponding to frames from the corresponding video feed (1410). One or more of the video feeds may be displayed in their respective camera objects 1116 as periodically refreshed (e.g., at 1 image per second, 1 image per two seconds, etc.) images (e.g., still frames from the video feed).
In some implementations, the electronic device receives a first user input to adjust a cropping of one or more of the video feeds displayed in the user interface objects (1414). In response to receiving the first user input, the electronic device adjusts the cropping of the one or more video feeds displayed in the user interface objects (1422). The client device 504, for example, while displaying the video feeds in the camera objects 1116, receives an input to adjust the views 1120, 1122, and 1124 of the video feeds (e.g., gesture 1138, orientation change 1129, a predefined voice input (not shown)). In response to the input, the views 1120, 1122, and 1124 of the video feeds are adjusted, as shown in
In some implementations, the views displayed in the camera objects 1116 are selectively adjustable. For example,
In some implementations, the mobile device comprises an accelerometer, and the first user input comprises a change, by a user, of an orientation of the mobile device. The electronic device receives a first user input to adjust a cropping of one or more of the video feeds displayed in the user interface objects by detecting the change of the orientation of the mobile device using the accelerometer (1416). The electronic device adjusts the cropping in response to receiving the first user input by adjusting the cropping of the one or more video feeds in accordance with the orientation change (1424). For example, as shown in
In some implementations, the mobile device comprises a touch-sensitive display, and the first user input comprises a gesture performed on the touch-sensitive display. The electronic device receives a first user input to adjust a cropping of one or more of the video feeds displayed in the user interface objects by detecting the gesture on the touch-sensitive display (1418). The electronic device adjusts the cropping in response to receiving the first user input by adjusting the cropping in accordance with the gesture (1426). For example, as shown in
In some implementations, the mobile device comprises an audio input device, and the first user input comprises a voice command. The electronic device receives a first user input to adjust a cropping of one or more of the video feeds displayed in the user interface objects by detecting the voice command using the audio input device (1420). The electronic device adjusts the cropping in response to receiving the first user input by adjusting the cropping in accordance with the voice command (1428). For example, the user may issue a predefined voice command instructing the smart home application running on the client device 504 to adjust the views displayed in the camera objects 1116. In response to detecting the voice command, the views 1120, 1122, and 1124 in the camera objects 1116 are changed in accordance with the voice command.
In some implementations, prior to receiving the first input, the electronic device receive a second user input selecting one or more user interface objects of the plurality of the user interface objects (1412). Adjusting the cropping in response to receiving the first user input comprises adjusting the cropping of only the video feeds displayed in the selected user interface objects in accordance with the first user input (1430). For example, the client device 504 may receive one or more inputs (e.g., gestures with contacts 1142 and 1144,
In some implementations, the electronic device receives a third user input to lock the cropping of the one or more of the video feeds (1432). In response to receiving the third user input, the electronic device maintains the adjustment of the cropping of the one or more of the video feeds (1434). In
In some implementations, the electronic device detects a termination of the first user input (1436), and in response to detecting the termination of the first user input, maintains the adjustment of the cropping (1438). In
In some implementations, the electronic device detects a termination of the first user input (1440), and in response to detecting the termination of the first user input, ceases the adjustment of the cropping (1442). In
In some implementations, while the application is in a foreground, the video feeds are received and displayed in the user interface objects as video streams; and while the application is in a background, the video feeds are received as periodically refreshed still images corresponding to frames from the video feeds (1444). The smart home application may be in the foreground (and its user interface displayed) or in the background (and not displayed) at any given moment. When the smart home application is in the foreground, the smart home application may receive the video feeds for the camera objects 1116 as video streams. When the smart home application is in the background, the smart home application may receive the video feeds for the camera objects 1116 in the background as periodically refreshed images instead of video streams.
In some implementations, each respective video feed of the plurality of video feeds comprises a first version at a first resolution and a second version at a second resolution higher than first resolution, and both the first version and the second version are received from the server system (1446). In some implementations, the client device 504 receives each video feed from the hub device server system 508 or the video server system 552 in both an original capture resolution (e.g., 720P or 1080P) version and a lower-resolution version (e.g., 180P).
In some implementations, the video feeds displayed in the user interface objects are the first versions (1448). The lower-resolution version (e.g., the 180P version) is displayed in the camera objects 1116.
In some implementations, the first version of a respective video feed is displayed in an associated user interface object (1450). The electronic device receives user selection of the associated user interface object (1452), and in response to receiving the user selection, ceases display of the first user interface and displays a second user interface, the second user interface including the second version of the respective video feed, wherein within the second user interface the respective video feed is uncropped (1454). As described above, the lower-resolution version of a video feed is displayed in the corresponding camera object 1116. For example, the 180P version of the “Dining room” 1118-C camera video feed is displayed in the camera object 1116-C. As shown in
In some implementations, the cropping of the at least one of the video feeds is performed at the mobile device in accordance with instructions from the server system, wherein the cropping instructions are generated by the server system based on an analysis of the at least one of the video feeds by the server system to determine a portion of the at least one of the video feed of potential interest to a user (1456). The cropping may be performed by the hub device server system 508 or the video server system 552. The hub device server system 508 or the video server system 552 crops a video feed before transmitting the video feed to a client device 504. In some implementations, the cropping by the server system 508 or 552 is based on an analysis by the server system 508 or 552 of a video feed to be cropped to determine which portion of the video feed (e.g., which portion of the frame) is of potential interest to the user. For example, the servers system 508 or 522 may, based on an analysis of the video feed, determine that there is motion occurring in the video, and crops the video feed to focus on that motion (e.g., crop the video feed to focus on the area where the motion occurred).
In some implementations, a plurality of the video feeds is displayed with cropping, and each of the cropped video feeds is cropped in accordance with a same cropping mask (1458). For example, in
The server system receives a video feed from a camera with an associated field of view (1502). The hub device server system 508 or video server system 552 (e.g., the video data receiving module 7302) receives video feeds from one or more cameras 118. Each camera 118 has a respective field of view.
The server system receives one or more alert events (1504). The hub device server system 508 or video server system 552 (e.g., the alert events module 73022) receives detected alert events from smart devices 204. For example, whenever a smart device 204 detects an alert event (e.g., a hazard, sound, etc.), the hub device server system 508 or video server system 552 receives information corresponding to the detected alert event (e.g., start time and end time of the alert event, alert event type).
The server system identifies as a camera event a portion of the video feed associated in time with the one or more alert events (1512). For example, the hub device server system 508 or video server system 552 (e.g., the camera events module 73024) correlates alert events or sequences of alert events with portions of the video feed based on when the alert events start and end, and from the correlation identify camera events, which include a portion of the video feed (e.g., captured video from the video feed from a start date/time to an end date/time) and an associated set of one or more alert events; the alert events are proximate in time (e.g., contemporaneous) with the associated video. In some implementations, two alert events are associated with the same camera event if the alert events overlap or occur in succession with a time gap (i.e., time elapsed between one alert event ending and the next alert event starting) between the two consecutive alert events being less than a threshold amount.
The server system determines a start time and duration of the camera event (1514). The hub device server system 508 or video server system 552 (e.g., the camera events module 73024) determines the start time and duration of the camera event based on the times of the associated alert events. For example, the start time of the earliest alert event of the associated alert events is determined to be the start time of the camera event, and the end time of the alert event of the associated alert events that ends latest is determined to be the end time of the camera event. With these start and end times, the duration of the camera event may be determined. Also, the video that is associated with the camera event has these start and end times (and optionally plus some slack time in either direction (e.g., 1-5 seconds before the start time and/or 1-5 seconds after the end time)).
The server system determines a chronological order of the alert events (1516). The hub device server system 508 or video server system 552 (e.g., the alert events module 73022) determines the chronological sequence of the alert events associated with the camera event. In some implementations, the chronological order is determined based on the start times of the alert events (i.e., when the respective alert events are first detected). In some implementations, the chronological order is determined based on the end times of the alert events (i.e., when the respective alert events are last detected).
The server system saves, in a history associated with the camera, information associated with the camera event, including a video clip and/or a frame from the portion of the video feed, and the chronological order of the alert events (1518). The hub device server system 508 or video server system 552 saves, in the server database 732 (e.g., in camera events history 7328 and video storage database 7320), the information associated with the camera event. The camera events information (e.g., the associated alert events and corresponding chronology, camera event times and durations, etc.) is stored in the camera events history 7328, and the camera events information references video stored in the video storage database 7320.
In some implementations, the alert events include one or more of: a hazard alert event, an audio alert event, a vibration alert event, and a motion alert event (1506). The alert events may be detected hazards (e.g., detected by smart hazard detectors 104), detected sound above a minimum decibel threshold (e.g., detected by any smart device 204 with audio input), detected vibrations above a minimum threshold (e.g., detected by any smart device 204 with vibration sensors), and detected motion (e.g., detected in video captured by a camera 118 or detected by non-camera sensors, such as motion sensors).
In some implementations, the motion alert event corresponds to motion detected in a defined spatial zone associated with the field of view (1508). The motion alert event may correspond to motion detected in video by the camera 118, where the motion is occurring in a defined zone of interest in the scene or area monitored by the camera 118. The zone of interest is a zone designating a space in the scene or area monitored by the camera 118 for which detected motion is treated as a distinct alert event type in addition to being treated as detected motion generally.
In some implementations, the spatial zone is defined by a user (1510). The spatial zone may be defined by a user. The user may enter into a user interface which shows video captured by the camera 118 and mark off a portion in the video as the zone of interest. For example, if the camera is monitoring a scene that includes a door, the user may mark off the door as the zone of interest (e.g., by marking a zone boundary around the door); motion detected in the door zone is treated as a distinct alert event type. In some implementations, the user is associated with the camera 118; the camera 118 is tied to the user's account (e.g., in account database 7324 and device information database 7326).
In some implementations, the server system associates each of the alert events with a respective visually distinctive display characteristic (1520). The hub device server system 508 or video server system 552 associates each alert event type with a visually distinctive display characteristic, so that, when indicators (e.g., icons) of alert events are displayed, the user can identify and differentiate between alert event types based on the distinctive display characteristics, which the indicators adopt. In some implementations, these associations are made per user. Multiple users may have the same mappings of alert event types to display characteristics, but it is sufficient that for any one respective user each alert event type is mapped to a distinct display characteristic. For example,
In some implementations, the display characteristic is visually distinctive based on color (1522). In some implementations, the display characteristic is visually distinctive based on shape (1524). The alert event types may be distinct based on the color or shape of their corresponding indicators. For example, for a respective user, the hazard alert event type is assigned red, the sound alert event type is assigned blue, the vibration alert event type is assigned orange, the general motion event type is assigned brown, and motion in a particular user-defined zone of interest is assigned green. Then, for that user, icons indicating hazard alert events are red, icons indicating sound alert events are blue, icons indicating vibration alert events are orange, etc. Similarly, icons indicating different alert event types may have different shapes. For example,
In some implementations, the server system, responsive to a request from a client device, transmits contents of the history to the client device for display in a desktop browser application at the client device, where the contents of the history is formatted for display in the desktop browser application as a camera history timeline (1526). For example, when interface 1204 or 1304 is accessed, a request is made to the hub device server system 508 or video server system 552 for the history of the camera 118. In response to the request, the hub device server system 508 or video server system 552 transmits camera history information to the client device 504 for display. The camera history information may be displayed differently depending on the interface (e.g., displayed differently in interface 1204 than in 1304). For example, in interface 1204, the camera history information is displayed in a linear timeline 1208.
In some implementations, the camera history timeline comprises an event bar corresponding to the camera event, where a length of the event bar reflects the duration of the camera event; and one or more alert event indicators proximate to the event bar, each of the alert event indicators corresponding to a respective alert event associated with the camera event, wherein each respective alert event indicator has a respective visually distinctive display characteristic associated with the corresponding respective alert event (1528). The timeline 1208 may include an event bar 1238 for each camera event. The length of the event bar 1238, which is to scale relative to timeline 1208, indicates a duration of the camera event. One or more alert event icons 1240 are displayed in proximity to the event bar 1238 (e.g., within the event bar 1238 (
In some implementations, the alert event indicators are ordered in accordance with the chronological order of the alert events (1530). The icons 1240 are ordered, while displayed, based on the chronological order of the alert events indicated. In some implementations, the icons 1240 are ordered based on the chronological order of the most recent instance of each alert event type for that camera event.
In some implementations, responsive to a request from a client device, the serve system transmits contents of the history to the client device for display in a mobile application at the device, where the contents of the history is formatted for display in the mobile application as a scrollable camera history list, the scrollable camera history list including one or more chronologically ordered event identifiers, each event identifier corresponding to a respective camera event (1532). For example, when interface 1204 or 1304 is accessed, a request is made to the hub device server system 508 or video server system 552 for the history of the camera 118. In response to the request, the hub device server system 508 or video server system 552 transmits camera history information to the client device 504 for display. The camera history information may be displayed differently depending on the interface (e.g., displayed differently in interface 1204 than in 1304). For example, in interface 1304, the camera history information is displayed as a scrollable list of event identifiers 1322 (which may still be viewed as a timeline, because the event identifiers are chronologically ordered and separated by hour).
In some implementations, the scrollable camera history list comprises an event identifier corresponding to the camera event; and one or more alert event indicators, each of the alert event indicators corresponding to a respective alert event associated with the camera event, where each respective alert event indicator has a respective visually distinctive display characteristic associated with the corresponding respective alert event (1534). The scrollable list of event identifiers 1322 displayed in interface 1304 includes event identifiers 1322 corresponding to respective camera events. Alert event icons 1350 may be displayed in the event identifiers when a filter is applied (e.g., as in
In some implementations, the alert event indicators are ordered in accordance with the chronological order of the alert events (1536). The icons 1350 are ordered, while displayed, based on the chronological order of the alert events indicated. In some implementations, the icons 1350 are ordered based on the chronological order of the most recent instance of each alert event type for that camera event.
The client device displays a video feed from a camera or a frame from the video feed (1602). For example, in interface 1204, the client device 504 displays a video feed 1207 (or a frame from the video feed 1207 (e.g., if the video is paused)) in the video region 1206.
The client device, concurrently with displaying the video feed or the frame, displays a camera history timeline (1604), including: displaying a representation of a camera event associated with one or more alert events in the camera history timeline as a bar overlaid on the event history timeline, the event bar having a length reflecting a duration of the camera event (1606); and displaying, proximate to the event bar, one or more alert event indicators, each of the alert event indicators corresponding to a respective alert event of the alert events associated with the camera event, wherein each respective alert event indicator has a respective visually distinctive display characteristic associated with the corresponding respective alert event (1608). In interface 1204, the client device 504 displays, concurrently with the video 1207, a timeline 1208 with camera event bars 1238 corresponding to respective camera events and icons 1240 indicating alert events associated with the camera events 1238. The length of a camera event bar 1238 indicates a duration of the corresponding camera event. The icons 1240 are displayed in the camera event bars 1238 (as in
In some implementations, the display characteristic is visually distinctive based on color (1610). In some implementations, the display characteristic is visually distinctive based on shape (1612). The icons 1240 have distinctive shapes and/or colors mapped to alert event types; the user can identify the alert event types indicated by the icons 1240 based on the shapes and/or colors.
In some implementations, the activity alert indicators are ordered in accordance with a chronological order of the corresponding alert events (1614). The icons 1240 are ordered, while displayed, based on the chronological order of the alert events indicated. In some implementations, the icons 1240 are ordered based on the chronological order of the most recent instance of each alert event type for that camera event.
The client device displays a camera history timeline (1702), including: displaying a chronologically ordered sequence of event identifiers, each event identifier corresponding to a respective camera event, each respective camera event associated with one or more respective alert events (1704); and displaying, for a respective event identifier, one or more alert event indicators, each of the alert event indicators corresponding to an alert event associated with the camera event corresponding to the respective event identifier, each of the alert event indicators displayed with a visually distinctive display characteristic associated with a corresponding alert event (1706). For example, in interface 1304, camera history information is displayed as a scrollable list of event identifiers 1322 (which may still be viewed as a timeline, because the event identifiers are chronologically ordered and separated by hour). The scrollable list of event identifiers 1322 displayed in interface 1304 includes event identifiers 1322 corresponding to respective camera events. Alert event icons 1350 may be displayed in the event identifiers when a filter is applied (e.g., as in
In some implementations, the camera history timeline is displayed as a scrollable list, and the event identifiers are items in the scrollable list (1708). The event identifiers 1322 are displayed in a scrollable list (
In some implementations, for the respective event identifier, the alert event indicators are ordered in accordance with a chronological order of the corresponding alert events (1710). The icons 1350 are ordered, while displayed, based on the chronological order of the alert events indicated. In some implementations, the icons 1350 are ordered based on the chronological order of the most recent instance of each alert event type for that camera event.
The client device, in an application executing on the client device, displays a camera event history provided by a remote server system, where the camera event history is presented as a chronologically-ordered set of event identifiers, each event identifier corresponding to a respective event for which a remote camera has captured an associated video (1802). For example, the smart home application displays, in interface 1304, camera history information as a scrollable list of chronologically-ordered event identifiers 1322 (which may still be viewed as a timeline, because the event identifiers are chronologically ordered and separated by hour). The scrollable list of event identifiers 1322 displayed in interface 1304 includes event identifiers 1322 corresponding to respective camera events with associated video from a camera 118.
The client device receives a user selection of a displayed event identifier (1814). As shown in
The client device, in response to receiving the user selection of the displayed event identifier, expands the selected event identifier into a video player window, the video player window consuming a portion of the displayed camera event history; and plays, in the video player window, the captured video associated with the selected event identifier (1816). In response to detecting the gesture on the event identifier 1322-E, the smart home application expands the event identifier 1322 inline into a video player interface 1342 (
In some implementations, the video player window consumes only a portion of the displayed camera event history. The video player interface 1342, for example, consumes a portion of the scrollable list; other event identifiers (e.g., identifiers 1322-D and 1322-F,
In some implementations, the playback of video 1354 is automatically initiated when the event identifier 1322 expands into the video player interface 1342. In some implementations, the playback of video 1354 needs to be manually initiated after the event identifier 1322 expands into the video player interface 1342. For example, the user manually activates playback by performing a gesture on the playback affordance 1364 (
In response to terminating playback of the captured video associated with the selected event identifier or user de-selection of the displayed event identifier, the client device collapses the video player window into the selected event identifier thereby stopping the playing of the captured video associated with the selected event identifier (1818). The user may de-select the event identifier 1322-E by performing a gesture in the video player interface 1342 away from the video 1354 (e.g., gesture with contact 1374 in an empty area in video player interface 1342,
In some implementations, the set of event identifiers are displayed as a scrollable list of the event identifiers (1804). The event identifiers 1322 are displayed in a scrollable list (
In some implementations, a respective event corresponding to the displayed event identifier is a non-camera event, and a video associated with the respective event is captured by the remote camera during the non-camera event (1806). An event identifier 1322 may corresponding to a camera event where motion is not detected in the video itself, but one or more non-camera alert event(s) (e.g., hazard, sound, vibration, etc.) are detected, and video associated with the camera event is captured during the non-camera alert event(s).
In some implementations, each event identifier has a thumbnail image associated with the corresponding respective event (1808). Each event identifier 1322 includes a thumbnail 1328, which may be a frame of the associated video or the associated video in thumbnail-size.
In some implementations, a video associated with a respective event and captured by the remote camera is contemporaneous with the associated respective event (1810). For example, when the alert event(s) for a camera event are non-camera alert event(s), the associated video is video captured proximate in time with the alert event(s). Video captured proximate in time with the alert event(s) may be captured while the alert event(s) are detected or immediately after the alert event(s) is last detected (e.g., for instantaneous alert events such as sounds).
In some implementations, a video associated with a respective event is saved at the remote server system (1812). Video associated with camera events are saved and stored at the hub device server system 508 or video server system 552 (e.g., in video storage database 7320).
In some implementations, for the displayed event identifier, the client device displays one or more alert event icons, each alert event icon corresponding to a respective alert event triggered in response to a respective event corresponding to the displayed event identifier (1820). For example, when a filter is applied, icons 1350 may be displayed in event identifiers 1322 (
In some implementations, within the displayed event identifier, the alert event icons are visually distinctive from each other based on icon color (1822). In some implementations, within the displayed event identifier, the alert event icons are visually distinctive from each other based on icon shape (1824). The icons 1350 have distinctive shapes and/or colors mapped to alert event types; the user can identify the alert event types indicated by the icons 1350 based on the shapes and/or colors.
In some implementations, within the displayed event identifier, the alert event icons are ordered in accordance with a chronological order in which the triggered alert events were triggered in response to the respective event corresponding to the displayed event identifier (1826). Within an event identifier 1322, the icons 1350 are ordered by the chronological order of the instances of alert events to which the displayed icons 1350 correspond. For example, in
In some implementations, the client device displays in the displayed event identifier information regarding a most recently triggered alert event of the triggered alert events (1828). The activity type identifier 1330 of an event identifier identifies, in some implementations, the alert event type of the most recent alert event associated with the corresponding camera event. For example, in
The scrollable list may be filtered to show just camera events that satisfy particular filtering criteria (e.g., camera events that have particular alert event types).
In some implementations, additional controls and affordances are displayed when a mouse pointer is hovered over the video. For example,
For situations in which the systems discussed above collect information about users, the users may be provided with an opportunity to opt in/out of programs or features that may collect personal information (e.g., information about a user's preferences or usage of a smart device). In addition, in some implementations, certain data may be anonymized in one or more ways before it is stored or used, so that personally identifiable information is removed. For example, a user's identity may be anonymized so that the personally identifiable information cannot be determined for or associated with the user, and so that user preferences or user interactions are generalized (for example, generalized based on user demographics) rather than associated with a particular user.
Although some of various drawings illustrate a number of logical stages in a particular order, stages that are not order dependent may be reordered and other stages may be combined or broken out. While some reordering or other groupings are specifically mentioned, others will be obvious to those of ordinary skill in the art, so the ordering and groupings presented herein are not an exhaustive list of alternatives. Moreover, it should be recognized that the stages could be implemented in hardware, firmware, software or any combination thereof.
The foregoing description, for purpose of explanation, has been described with reference to specific implementations. However, the illustrative discussions above are not intended to be exhaustive or to limit the scope of the claims to the precise forms disclosed. Many modifications and variations are possible in view of the above teachings. The implementations were chosen in order to best explain the principles underlying the claims and their practical applications, to thereby enable others skilled in the art to best use the implementations with various modifications as are suited to the particular uses contemplated.
This application is a continuation of U.S. patent application Ser. No. 15/194,528, titled “Methods and Systems for Presenting Alert Event Indicators,” filed Jun. 27, 2016, which is a continuation of U.S. patent application Ser. No. 14/739,412, titled “Methods and Systems for Presenting Alert Event Indicators,” filed Jun. 15, 2015, now U.S. Pat. No. 9,380,274, issued on Jun. 28, 2016, which is a continuation of U.S. patent application Ser. No. 14/738,930, titled “Methods and Systems for Presenting Multiple Live Video Feeds in a User Interface,” filed Jun. 14, 2015, now U.S. Pat. No. 9,361,011, issued on Jun. 7, 2016, all of which are hereby incorporated by reference herein in their entirety. This application is related to the following applications, which are hereby incorporated by reference herein in their entirety: U.S. patent application Ser. No. 14/738,928, titled “Methods and Systems for Smart Home Automation Using a Multifunction Status and Entry Point Icon,” filed Jun. 14, 2015; and U.S. patent application Ser. No. 14/739,427, titled “Methods and Systems for Presenting a Camera History,” filed Jun. 15, 2015.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5625410 | Washino et al. | Apr 1997 | A |
| 5765485 | Thoman et al. | Jun 1998 | A |
| D403313 | Peppel | Dec 1998 | S |
| D424036 | Arora et al. | May 2000 | S |
| D456293 | Tsumura et al. | Apr 2002 | S |
| 6593956 | Potts | Jul 2003 | B1 |
| D488818 | Lee et al. | Apr 2004 | S |
| D500047 | Sevdermish | Dec 2004 | S |
| 6948131 | Neven et al. | Sep 2005 | B1 |
| 6954498 | Lipton | Oct 2005 | B1 |
| D550227 | Sato et al. | Sep 2007 | S |
| 7382244 | Donovan | Jun 2008 | B1 |
| D590416 | Kochackis | Apr 2009 | S |
| D597864 | Sakuma et al. | Aug 2009 | S |
| D607004 | Kordus et al. | Dec 2009 | S |
| D619612 | Pueyo et al. | Jul 2010 | S |
| D621730 | Driver et al. | Aug 2010 | S |
| D626131 | Kruzeniski et al. | Oct 2010 | S |
| 7877708 | Zinn et al. | Jan 2011 | B2 |
| 7884855 | Ortiz | Feb 2011 | B2 |
| 7903115 | Platzer et al. | Mar 2011 | B2 |
| 7996771 | Girgensohn et al. | Aug 2011 | B2 |
| D647809 | Driver | Nov 2011 | S |
| D656157 | Khan et al. | Mar 2012 | S |
| D658674 | Shallcross et al. | May 2012 | S |
| 8184069 | Rhodes | May 2012 | B1 |
| D661701 | Brown et al. | Jun 2012 | S |
| D662508 | Kim | Jun 2012 | S |
| D664966 | Shallcross et al. | Aug 2012 | S |
| D664978 | Tanghe et al. | Aug 2012 | S |
| D672364 | Reyna et al. | Dec 2012 | S |
| 8340654 | Bratton et al. | Dec 2012 | B2 |
| D677269 | Scott et al. | Mar 2013 | S |
| D678898 | Walsh et al. | Mar 2013 | S |
| 8390684 | Piran | Mar 2013 | B2 |
| D681653 | Bitran et al. | May 2013 | S |
| D681660 | Matas | May 2013 | S |
| D684164 | Friedlander et al. | Jun 2013 | S |
| D686221 | Brinda et al. | Jul 2013 | S |
| D686635 | Cranfill et al. | Jul 2013 | S |
| D689892 | Perry et al. | Sep 2013 | S |
| D689895 | DeLuca | Sep 2013 | S |
| D692450 | Convay et al. | Oct 2013 | S |
| 8570375 | Srinivasan | Oct 2013 | B1 |
| D694255 | Jones, Jr. | Nov 2013 | S |
| 8589374 | Chaudhri | Nov 2013 | B2 |
| D696677 | Corcoran et al. | Dec 2013 | S |
| 8615511 | Jones | Dec 2013 | B2 |
| D697930 | Crabtree et al. | Jan 2014 | S |
| D697940 | Bitran et al. | Jan 2014 | S |
| 8665375 | Moore et al. | Mar 2014 | B2 |
| D702700 | Thompson | Apr 2014 | S |
| D702704 | Santos et al. | Apr 2014 | S |
| D705255 | Gerssen et al. | May 2014 | S |
| D707245 | Bruck et al. | Jun 2014 | S |
| D708197 | Pasceri et al. | Jul 2014 | S |
| D708204 | Pasceri et al. | Jul 2014 | S |
| D711415 | Simister et al. | Aug 2014 | S |
| 8806320 | Abdo | Aug 2014 | B1 |
| D712928 | Brener et al. | Sep 2014 | S |
| D714334 | Cojuangco et al. | Sep 2014 | S |
| 8830193 | Shah | Sep 2014 | B2 |
| 8843239 | Mighdoll et al. | Sep 2014 | B2 |
| D715835 | Montgomery et al. | Oct 2014 | S |
| D716334 | Lee at al. | Oct 2014 | S |
| D717809 | Tsuru et al. | Nov 2014 | S |
| D717823 | Brotman et al. | Nov 2014 | S |
| 8917274 | Ma et al. | Dec 2014 | B2 |
| D720765 | Xie et al. | Jan 2015 | S |
| D720766 | Mandal et al. | Jan 2015 | S |
| D721382 | Brinda et al. | Jan 2015 | S |
| D723576 | Jones | Mar 2015 | S |
| D724603 | Williams et al. | Mar 2015 | S |
| D725666 | Tseng et al. | Mar 2015 | S |
| 8984436 | Tseng et al. | Mar 2015 | B1 |
| 8988232 | Sloo et al. | Mar 2015 | B1 |
| D726735 | Asai | Apr 2015 | S |
| D727336 | Allison et al. | Apr 2015 | S |
| D727928 | Allison et al. | Apr 2015 | S |
| D736223 | Park | Aug 2015 | S |
| D736792 | Brinda et al. | Aug 2015 | S |
| D737131 | Frandsen | Aug 2015 | S |
| D737278 | Shin et al. | Aug 2015 | S |
| D737283 | Scalisi | Aug 2015 | S |
| D739429 | Veilleux et al. | Sep 2015 | S |
| D739864 | Kang | Sep 2015 | S |
| 9140572 | Millington | Sep 2015 | B2 |
| D740300 | Lee et al. | Oct 2015 | S |
| 9158974 | Laska et al. | Oct 2015 | B1 |
| 9170707 | Laska et al. | Oct 2015 | B1 |
| D745527 | Wang | Dec 2015 | S |
| 9207844 | Snibbe | Dec 2015 | B2 |
| D746828 | Arai et al. | Jan 2016 | S |
| D746849 | Anzures et al. | Jan 2016 | S |
| D747333 | Supino et al. | Jan 2016 | S |
| D748666 | Heeter et al. | Feb 2016 | S |
| D749620 | Jones | Feb 2016 | S |
| D751090 | Hu et al. | Mar 2016 | S |
| D752061 | Ahn et al. | Mar 2016 | S |
| D752072 | Song | Mar 2016 | S |
| D752107 | Yun et al. | Mar 2016 | S |
| D752605 | Wang et al. | Mar 2016 | S |
| 9274696 | Mierau | Mar 2016 | B1 |
| D753132 | Cuthbert et al. | Apr 2016 | S |
| D753151 | Lee et al. | Apr 2016 | S |
| D753703 | Villamor et al. | Apr 2016 | S |
| D753708 | Yang et al. | Apr 2016 | S |
| D754713 | Zhang et al. | Apr 2016 | S |
| D754714 | Zhang et al. | Apr 2016 | S |
| D755193 | Sun et al. | May 2016 | S |
| D756379 | Apodaca et al. | May 2016 | S |
| D756401 | Soldner et al. | May 2016 | S |
| D757090 | Myung | May 2016 | S |
| D757746 | Lee | May 2016 | S |
| D757747 | Butcher et al. | May 2016 | S |
| D757784 | Lee at al. | May 2016 | S |
| D758386 | Zhang | Jun 2016 | S |
| D758422 | Zhao | Jun 2016 | S |
| D759688 | Wu | Jun 2016 | S |
| 9361011 | Burns | Jun 2016 | B1 |
| D760769 | Ishii et al. | Jul 2016 | S |
| D760792 | Liu et al. | Jul 2016 | S |
| D761277 | Harvell | Jul 2016 | S |
| 9386230 | Duran | Jul 2016 | B1 |
| D762655 | Kai | Aug 2016 | S |
| D763271 | Everette et al. | Aug 2016 | S |
| D763306 | Lee et al. | Aug 2016 | S |
| D763308 | Wang et al. | Aug 2016 | S |
| D763869 | Wang et al. | Aug 2016 | S |
| D763888 | Patel | Aug 2016 | S |
| D763895 | Chaudhri et al. | Aug 2016 | S |
| 9417637 | Matsuoka et al. | Aug 2016 | B2 |
| D765674 | Kim | Sep 2016 | S |
| D765678 | Goux | Sep 2016 | S |
| D766958 | Salazar Cardozo et al. | Sep 2016 | S |
| 9454820 | Kirmani | Sep 2016 | B1 |
| D768687 | Bae et al. | Oct 2016 | S |
| D769897 | Li | Oct 2016 | S |
| D769930 | Agrawal | Oct 2016 | S |
| 9471452 | McElhinney et al. | Oct 2016 | B2 |
| D770517 | Peng et al. | Nov 2016 | S |
| D771645 | Jewitt et al. | Nov 2016 | S |
| D772257 | Furutani et al. | Nov 2016 | S |
| D772894 | Zhao et al. | Nov 2016 | S |
| D773531 | Toth et al. | Dec 2016 | S |
| D775165 | Sun et al. | Dec 2016 | S |
| 9513642 | Rogers et al. | Dec 2016 | B2 |
| D775658 | Luo et al. | Jan 2017 | S |
| D776126 | Lai et al. | Jan 2017 | S |
| D776130 | Contreras et al. | Jan 2017 | S |
| D776680 | Bae et al. | Jan 2017 | S |
| D776690 | Tsujimoto et al. | Jan 2017 | S |
| D776702 | Huang et al. | Jan 2017 | S |
| D777744 | Wang et al. | Jan 2017 | S |
| D779504 | Cabrera, Jr. et al. | Feb 2017 | S |
| D779533 | Liu | Feb 2017 | S |
| D780785 | Hansen et al. | Mar 2017 | S |
| D781299 | Yun et al. | Mar 2017 | S |
| D783641 | Elston et al. | Apr 2017 | S |
| D783652 | Guan et al. | Apr 2017 | S |
| D784363 | Fleming et al. | Apr 2017 | S |
| D784400 | Jol | Apr 2017 | S |
| 9619984 | Donovan | Apr 2017 | B2 |
| D786932 | Kim et al. | May 2017 | S |
| D795927 | Bischoff et al. | May 2017 | S |
| D790581 | Chaudhri et al. | Jun 2017 | S |
| D791806 | Brewington et al. | Jul 2017 | S |
| D794047 | Gandhi et al. | Aug 2017 | S |
| D795292 | Loosli et al. | Aug 2017 | S |
| D795919 | Bischoff et al. | Aug 2017 | S |
| D796535 | Gaur et al. | Sep 2017 | S |
| D796540 | McLean et al. | Sep 2017 | S |
| D797131 | Mizono et al. | Sep 2017 | S |
| D797772 | Mizono et al. | Sep 2017 | S |
| D800747 | Lee et al. | Oct 2017 | S |
| D800752 | Hersh et al. | Oct 2017 | S |
| 9778830 | Dubin | Oct 2017 | B1 |
| D803233 | Wilberding | Nov 2017 | S |
| D803241 | Mizono et al. | Nov 2017 | S |
| D803242 | Mizono et al. | Nov 2017 | S |
| D805548 | King et al. | Dec 2017 | S |
| D806114 | Kim et al. | Dec 2017 | S |
| 9838602 | Duran | Dec 2017 | B2 |
| D807376 | Mizono et al. | Jan 2018 | S |
| D809522 | Mizono et al. | Feb 2018 | S |
| D810116 | McLean et al. | Feb 2018 | S |
| 9898175 | Fiedler | Feb 2018 | B2 |
| D815144 | Feng et al. | Apr 2018 | S |
| D817337 | Wei | May 2018 | S |
| D817357 | Barajas et al. | May 2018 | S |
| D818000 | Lee et al. | May 2018 | S |
| D819047 | Bates et al. | May 2018 | S |
| D819075 | Tsuji et al. | May 2018 | S |
| 9979862 | Xiong et al. | May 2018 | B1 |
| D821407 | Wilberding | Jun 2018 | S |
| D821410 | Vinna et al. | Jun 2018 | S |
| D821441 | Wilberding et al. | Jun 2018 | S |
| D821443 | Jang et al. | Jun 2018 | S |
| D823867 | Berlow | Jul 2018 | S |
| D823891 | Lupei et al. | Jul 2018 | S |
| D824416 | Memmelaar, Jr. et al. | Jul 2018 | S |
| D824926 | De La Garza | Aug 2018 | S |
| D831673 | O'Rourke et al. | Oct 2018 | S |
| 10091020 | Han et al. | Oct 2018 | B2 |
| 10120530 | Snibbe | Nov 2018 | B2 |
| 10133443 | Von Dehsen et al. | Nov 2018 | B2 |
| 10145577 | Bruck et al. | Dec 2018 | B2 |
| 10156959 | Fulker et al. | Dec 2018 | B2 |
| D837237 | Fraser et al. | Jan 2019 | S |
| D841659 | Mehta et al. | Feb 2019 | S |
| D842867 | Jedrzejowicz et al. | Mar 2019 | S |
| D842874 | Tashiro et al. | Mar 2019 | S |
| D842891 | MacLean et al. | Mar 2019 | S |
| D843398 | Stewart et al. | Mar 2019 | S |
| D844668 | Lee et al. | Apr 2019 | S |
| D849030 | Shook et al. | May 2019 | S |
| 10281507 | Schuh et al. | May 2019 | B2 |
| 10353576 | Coffman et al. | Jul 2019 | B2 |
| 10386999 | Burns | Aug 2019 | B2 |
| D868797 | Blum et al. | Dec 2019 | S |
| 10708550 | Glazer | Jul 2020 | B2 |
| 20020049979 | White et al. | Apr 2002 | A1 |
| 20020116120 | Ruiz et al. | Aug 2002 | A1 |
| 20040113770 | Falk et al. | Jun 2004 | A1 |
| 20040177149 | Zullo et al. | Sep 2004 | A1 |
| 20040260427 | Wimsatt | Dec 2004 | A1 |
| 20050046723 | Bean et al. | Mar 2005 | A1 |
| 20050104958 | Egnal et al. | May 2005 | A1 |
| 20050289615 | Nishitani | Dec 2005 | A1 |
| 20060288392 | Fleming | Dec 2006 | A1 |
| 20070024706 | Brannon | Feb 2007 | A1 |
| 20070025688 | Pejhan | Feb 2007 | A1 |
| 20070033632 | Baynger et al. | Feb 2007 | A1 |
| 20070103548 | Carter | May 2007 | A1 |
| 20080088706 | Girgensohn et al. | Apr 2008 | A1 |
| 20080174570 | Jobs et al. | Jul 2008 | A1 |
| 20080181498 | Swenson et al. | Jul 2008 | A1 |
| 20080263468 | Cappione et al. | Oct 2008 | A1 |
| 20090002157 | Donovan | Jan 2009 | A1 |
| 20090002492 | Velipasalar | Jan 2009 | A1 |
| 20090021583 | Salgar et al. | Jan 2009 | A1 |
| 20090075694 | Kim et al. | Mar 2009 | A1 |
| 20090164439 | Nevins | Jun 2009 | A1 |
| 20090178007 | Matas et al. | Jul 2009 | A1 |
| 20090220206 | Kisliakov | Sep 2009 | A1 |
| 20090284601 | Eledath | Nov 2009 | A1 |
| 20090288011 | Piran | Nov 2009 | A1 |
| 20100023865 | Fulker | Jan 2010 | A1 |
| 20100061446 | Hands et al. | Mar 2010 | A1 |
| 20100105406 | Luo | Apr 2010 | A1 |
| 20100124274 | Cheok et al. | May 2010 | A1 |
| 20100131457 | Heimendinger | May 2010 | A1 |
| 20100321183 | Donovan | Dec 2010 | A1 |
| 20110040760 | Fleishman et al. | Feb 2011 | A1 |
| 20110185269 | Finkelstein et al. | Jul 2011 | A1 |
| 20110199517 | Laberge | Aug 2011 | A1 |
| 20110205435 | Lee | Aug 2011 | A1 |
| 20110316697 | Krahnstoever | Dec 2011 | A1 |
| 20120036480 | Warner et al. | Feb 2012 | A1 |
| 20120066608 | Sundermeyer et al. | Mar 2012 | A1 |
| 20120130513 | Hao et al. | May 2012 | A1 |
| 20120317299 | Sathianathan et al. | Dec 2012 | A1 |
| 20120323930 | Kennberg et al. | Dec 2012 | A1 |
| 20130016122 | Bhatt et al. | Jan 2013 | A1 |
| 20130067365 | Shrufi et al. | Mar 2013 | A1 |
| 20130072308 | Peck et al. | Mar 2013 | A1 |
| 20130090767 | Bruck et al. | Apr 2013 | A1 |
| 20130091432 | Shet et al. | Apr 2013 | A1 |
| 20130097093 | Kolber | Apr 2013 | A1 |
| 20130102372 | Lutnick | Apr 2013 | A1 |
| 20130129307 | Choe et al. | May 2013 | A1 |
| 20130132908 | Lee et al. | May 2013 | A1 |
| 20130145270 | Piran | Jun 2013 | A1 |
| 20130173064 | Fadell et al. | Jul 2013 | A1 |
| 20130179836 | Han et al. | Jul 2013 | A1 |
| 20130182107 | Anderson | Jul 2013 | A1 |
| 20130185150 | Crum | Jul 2013 | A1 |
| 20130191776 | Harris | Jul 2013 | A1 |
| 20130211783 | Fisher et al. | Aug 2013 | A1 |
| 20130251150 | Chassagne | Sep 2013 | A1 |
| 20130263034 | Bruck et al. | Oct 2013 | A1 |
| 20130268129 | Fadell et al. | Oct 2013 | A1 |
| 20130282421 | Graff et al. | Oct 2013 | A1 |
| 20130311909 | Howard et al. | Nov 2013 | A1 |
| 20130325332 | Rhee et al. | Dec 2013 | A1 |
| 20130328997 | Desai | Dec 2013 | A1 |
| 20130332886 | Cranfill et al. | Dec 2013 | A1 |
| 20140012574 | Pasupalak et al. | Jan 2014 | A1 |
| 20140013243 | Flynn, III et al. | Jan 2014 | A1 |
| 20140026061 | Kim et al. | Jan 2014 | A1 |
| 20140028011 | Yamauchi | Jan 2014 | A1 |
| 20140033071 | Gruber et al. | Jan 2014 | A1 |
| 20140043485 | Bateman et al. | Feb 2014 | A1 |
| 20140047074 | Chung | Feb 2014 | A1 |
| 20140050455 | Ni | Feb 2014 | A1 |
| 20140064738 | Chen et al. | Mar 2014 | A1 |
| 20140098247 | Rao et al. | Apr 2014 | A1 |
| 20140189518 | Kim et al. | Jul 2014 | A1 |
| 20140189586 | Waldman et al. | Jul 2014 | A1 |
| 20140218517 | Kim | Aug 2014 | A1 |
| 20140222424 | Hartford et al. | Aug 2014 | A1 |
| 20140232873 | Meganathan | Aug 2014 | A1 |
| 20140277795 | Matsuoka et al. | Sep 2014 | A1 |
| 20140313032 | Sager | Oct 2014 | A1 |
| 20140313377 | Hampton | Oct 2014 | A1 |
| 20140328570 | Cheng | Nov 2014 | A1 |
| 20140333530 | Agnetta | Nov 2014 | A1 |
| 20140333776 | Dedeoglu | Nov 2014 | A1 |
| 20140365019 | Gourlay et al. | Dec 2014 | A1 |
| 20140375819 | Larsen | Dec 2014 | A1 |
| 20150023650 | Austin et al. | Jan 2015 | A1 |
| 20150035987 | Fernandez | Feb 2015 | A1 |
| 20150038121 | Koum | Feb 2015 | A1 |
| 20150058709 | Zaletel | Feb 2015 | A1 |
| 20150058730 | Dubin et al. | Feb 2015 | A1 |
| 20150097689 | Logue et al. | Apr 2015 | A1 |
| 20150113432 | Jung et al. | Apr 2015 | A1 |
| 20150113461 | Kasten et al. | Apr 2015 | A1 |
| 20150117513 | Sarafa et al. | Apr 2015 | A1 |
| 20150143239 | Birkbeck et al. | May 2015 | A1 |
| 20150149180 | Lee | May 2015 | A1 |
| 20150173846 | Schneider et al. | Jun 2015 | A1 |
| 20150193127 | Chai et al. | Jul 2015 | A1 |
| 20150208205 | Chan et al. | Jul 2015 | A1 |
| 20150227196 | Fujii et al. | Aug 2015 | A1 |
| 20150242404 | Underwood, IV et al. | Aug 2015 | A1 |
| 20150248270 | Lang | Sep 2015 | A1 |
| 20150248275 | Gallo | Sep 2015 | A1 |
| 20150248919 | Homma | Sep 2015 | A1 |
| 20150269643 | Riley et al. | Sep 2015 | A1 |
| 20150287310 | Deliuliis et al. | Oct 2015 | A1 |
| 20150288877 | Glazer | Oct 2015 | A1 |
| 20150310280 | Bentley et al. | Oct 2015 | A1 |
| 20150339002 | Arnold | Nov 2015 | A1 |
| 20150350265 | O'Brien | Dec 2015 | A1 |
| 20150350611 | Pearson | Dec 2015 | A1 |
| 20160004390 | Laska et al. | Jan 2016 | A1 |
| 20160026329 | Fadell et al. | Jan 2016 | A1 |
| 20160034574 | Kang | Feb 2016 | A1 |
| 20160043905 | Fiedler | Feb 2016 | A1 |
| 20160417241 | Kirkby et al. | Feb 2016 | |
| 20160086038 | Scanlon et al. | Mar 2016 | A1 |
| 20160088326 | Solomon et al. | Mar 2016 | A1 |
| 20160105331 | Han et al. | Apr 2016 | A1 |
| 20160105466 | Allen | Apr 2016 | A1 |
| 20160105644 | Smith | Apr 2016 | A1 |
| 20160105747 | Cheng | Apr 2016 | A1 |
| 20160105847 | Smith | Apr 2016 | A1 |
| 20160110064 | Shapira | Apr 2016 | A1 |
| 20160139671 | Jun et al. | May 2016 | A1 |
| 20160139747 | Kocienda et al. | May 2016 | A1 |
| 20160147406 | Yi | May 2016 | A1 |
| 20160155315 | McElhinney et al. | Jun 2016 | A1 |
| 20160220743 | Guthrie et al. | Aug 2016 | A1 |
| 20160260414 | Yang | Sep 2016 | A1 |
| 20160306509 | Jeon et al. | Oct 2016 | A1 |
| 20160335139 | Hurley et al. | Nov 2016 | A1 |
| 20160349936 | Cho et al. | Dec 2016 | A1 |
| 20160358436 | Wautier | Dec 2016 | A1 |
| 20160364114 | Von Dehsen et al. | Dec 2016 | A1 |
| 20160366330 | Boliek et al. | Dec 2016 | A1 |
| 20170003720 | Robinson et al. | Jan 2017 | A1 |
| 20170010790 | Glover et al. | Jan 2017 | A1 |
| 20170017376 | Han et al. | Jan 2017 | A1 |
| 20170017384 | Lee | Jan 2017 | A1 |
| 20170017392 | Castaneda et al. | Jan 2017 | A1 |
| 20170034430 | Fu et al. | Feb 2017 | A1 |
| 20170060374 | Murrells et al. | Mar 2017 | A1 |
| 20170060399 | Hough et al. | Mar 2017 | A1 |
| 20170070775 | Taxier | Mar 2017 | A1 |
| 20170089739 | Gallo | Mar 2017 | A1 |
| 20170126975 | Duran | May 2017 | A1 |
| 20170133053 | Kardashov | May 2017 | A1 |
| 20170186079 | Kim et al. | Jun 2017 | A1 |
| 20170201850 | Raleigh et al. | Jul 2017 | A1 |
| 20170207949 | Donovan | Jul 2017 | A1 |
| 20170286913 | Liu et al. | Oct 2017 | A1 |
| 20170308390 | Venis et al. | Oct 2017 | A1 |
| 20170329511 | Ueno et al. | Nov 2017 | A1 |
| 20170336920 | Chan et al. | Nov 2017 | A1 |
| 20170357439 | Lemay et al. | Dec 2017 | A1 |
| 20180018081 | Dattilo-Green | Jan 2018 | A1 |
| 20180019889 | Burns | Jan 2018 | A1 |
| 20180048819 | Duran | Feb 2018 | A1 |
| 20180101297 | Yang et al. | Apr 2018 | A1 |
| 20180113577 | Burns et al. | Apr 2018 | A1 |
| 20180129380 | Suh et al. | May 2018 | A1 |
| 20180136819 | Lee | May 2018 | A1 |
| 20180136947 | Choi | May 2018 | A1 |
| 20180144615 | Kinney et al. | May 2018 | A1 |
| 20180187954 | Yang et al. | Jul 2018 | A1 |
| 20180211693 | Iwanami | Jul 2018 | A1 |
| 20180233013 | Nishikado | Aug 2018 | A1 |
| 20180311582 | Gerhard et al. | Nov 2018 | A1 |
| 20180338120 | Lemberger | Nov 2018 | A1 |
| Number | Date | Country |
|---|---|---|
| WO 2006120596 | Nov 2006 | WO |
| WO 2013009828 | Jan 2013 | WO |
| WO 2014137372 | Sep 2014 | WO |
| Entry |
|---|
| Ahmed, Nafees, “5 Best Video Editing Apps for Android Devices”, posted at techbuzzes.com, Mar. 23, 2013, (site visited Jun. 3, 2016), Available from Internet: http://techbuzzes.com/2013/03/best-video-editing-apps-for-android, 7 pgs. |
| Blatner, WiCam: Wireless iPhone Camera, Rochester Institute of Technology, Spring 2010, 1 pg, www.ce/rit/edu/research/projects/2010_spring/WICam/index.html. |
| TechBitar, Bluetooth-conrolled Pan/Tilt Servo Platform Using Android as Remote, downloaded Jul. 15, 2015, 9 pgs, www.techbitar.com/bluetooth-controlled-pan-tilt-servo.html. |
| EyeSpyFX, Viewer for D-Link Cams, IOS Version 3.1.2, 2013, 19 pgs, www.eyespyfx.com/dlink.php. |
| Netgear, Home Security Systems / Security Cameras / Arlo, downloaded Jul. 15, 2015, 6 pgs, arlo.com/en-us. |
| CNET, Netgear Arlo Smart Home Security review, downloaded Jul. 15, 2015, 5 pgs, www.cnet.com/products/netgear-arlo-smart-home-security-kit. |
| Arlo on the App Store on iTunes, downloaded Jul. 15, 2015, 2 pgs, itunes.apple.com/us/app/arlo/id925911312?mt=8. |
| AppCrawlr, ipCam FC-IP camera surveillance (ios), downloaded Jul. 15, 2015, 2 pgs, apperawlr.com/ios/ipcam-fc-ip-camera-surveillance. |
| Siml, ipCamFC-IP camera surveillance, downloaded Jul. 15, 2015, 2 pgs, itunes.apple.com/us/app/ipcam-fc-ip-camera-surveillance/id548480721?mt=8. |
| D-Link Corporation, mydlink Lite, downloaded Jul. 15, 2015, 2 pgs, itunes.apple.com/us/app/mydlink-lite/id372571229?mt=8. |
| D-Link Corporation, mydlink+, downloaded Jul. 15, 2015, 2 pgs, itunes.apple.com/us/app/mydlink/id479832296?mt=8. |
| D-Link Corporation, mydlink App, downloaded Jul. 15, 2015, 4 pgs, www.mydlink.com/apps. |
| “Dropcam”, posted at play.google.com, Aug. 20, 2015, [site visited Jan. 17, 2017]. Available from Internet: <https://play.google.com/store/apps/details?id=com.dropcam.android>. |
| Wollerton, Turn your old iPod into a security camera for free, CNET, Dec. 17, 2014, 5 pgs, www.cnet.com/how-to/turn-your-old-ipod-into-a-security-camera-for-free. |
| Nunal, Paul, “Best Android apps for videographers and video editors”, posted at androidauthority.com, May 3, 2012, (site visited Jun. 3, 2016), Available from Internet: http://www.androidauthority.com/best-android-apps-videograhers-video-videography-80338, 4 pgs. |
| Fitzer, Michael, “Editing Effects Software to Make Your Video Sing”, posted at videomaker.com, May 3, 2012, (site visited Jun. 3, 2016) Available from Internet: https://www.videomaker.com/article/c3/15366-editing-effects-software-to-make-your-video-sing), 3 pgs. |
| Features > Button Bars, posted at webbookbinder.com, May 8, 2011, [site visited Sep. 13, 2016]. Available from Internet: <http://www.webbookbinder.com/Website/020New/buttonbars.asp>. |
| “Foto de archivo”, posted at es.123rf.com, Apr. 23, 2015, [site visited Jan. 17, 2017]. Available from Internet: <http://es.123rf.com/photo_37507296_diseno-transparente-plantilla-de-interfaz-de-usuario-movil-disposicion-para-el-movil-o-pagina-web-il.html>. |
| Hoang, Le, “YouTube: How to Find Previously Watched Videos”, posted at tech-recipes.com, Feb. 15, 2011, [site visited Jan. 17, 2017]. Available from Internet: <http://www.tech-recipes.com/rx/11104/youtube-how-to-find-all-the-previously-watched-videos>. |
| Stock Vector—Web Site Interface Icons // Button Bar Series, posted at alamy.com, Aug. 2, 2010, [site visited Sep. 13, 2016]. Available from Internet: <http://www.alamy.com/stock-photo-web-site-interface-icons-button-bar-series-64003090.html>. |
| Visavadia, Jay, “i0S7 Wireframe”, posted at dribbble.com, Dec. 19, 2013, [site visited Sep. 14, 2016]. Available from Internet: <https://dribbble.com/shots/1352315-i057-Wireframe>. |
| “Wireframe toolkit for Keynote and Powerpoint”, posted at raizlabs.com, Jun. 29, 2011, [site visited Jan. 17, 2017]. Available from Internet: <https://www.raizlabs.com/blog/2011/06/wireframe-toolkit-for-keynote-and-powerpoint>. |
| Holly, Russell, “Nest Aware, and why the Nest Cam subscription makes sense”, posted at androidcentral.com, Jul. 3, 2015, [site visited Sep. 30, 2016]. Available from Internet: <http://www.androidcentral.com/nest-aware-and-and-why-nest-cam-subscription-makes-sense>. |
| Vector Video Player, posted at shutterstock.com, Aug. 21, 2014, [site visited Mar. 17, 2017]. Available from Internet: <https://www.shutterstock.comffr/image-vector/vector-audio-video-player-web-101573365>. |
| “Mini UI toolkit PSD Download”, posted at freepsds123.com, Jun. 21, 2014, [site visited Mar. 17, 2017]. Available from Internet: <http://www.freepsds123.com/2014/06/21/min i-u i-toolkit-psd-down load>. |
| “Octopussy (1983)—Cancelled” posted at mi6-hq.com, Oct. 2, 2014, [site visited Mar. 17, 2017]. Available from Internet: <https://wvvw.mi6-hq.com/sections/games/octopussy_l 983>. |
| Metal fence on a dark background, [online], uploaded on Feb. 28, 2013, retrieved on Aug. 8, 2018. Retrieved from, <URL: https:// stockfresh.conn/innage/2626471/nnetal-fence-on-a-dark-background>, 1 page. |
| Google image search of Nest Icon, [online], images uploaded before Jul. 12, 2016, retrieved on Aug. 8, 2018. Retrieved from, <URL: https://www.google.conn/search?q=nest+icon&rlz=1C1GCEB enUS799US799&biw=1920&bih=1109&source=Int&tbs=cdr%3A1% 2Ccd nnin%3A%2Ccdnnax%3A7%2>, 2 pages. |
| U. A. Lipton, H. Fujiyoshi, and R. S. Patil, “Moving Target Classification and Tracking from Real-Time Video,” Proc. IEEE WACV '98 , Princeton, N.J., 1998, pp. 8-14 (Year: 1998). |
| Google, LLC, ISR/WO, PCT/US2018/020919, dated Jun. 11, 2018, 26 pgs. |
| Tenon, Biff. “Abstract background with animation . . . ” shutterstock.conn. Date not available. Accessed Sep. 1, 2018. Available online at URL: <https://www.shutterstock.conn/video/clip-24321839-stock-footage-abstract-background-with-aninnation-of-flicker-and-nnoving-patterns-fronn-clear-colorful-circles.htnnl>. |
| Paul Viola and Michael Jones, “Rapid Object Detection using a Boosted Cascade of Simple Features“, Conference on Computer Vision and Pattern Recognition ”CVPR” 2001 (Year: 2001), 9 pgs. |
| “Pulsating Animation.” dribbble.com. Published Jan. 15, 2017. Accessed Apr. 8, 2019. Available online. at Url: <https://dribbble.com/shots /3218158-Pulsating-animation> (Year: 2017), 1 pg. |
| Baer, Drake. “Apple Has Reportedly . . .” Published Apr. 12, 2017. Accessed Apr. 8, 2019. Available online at URL: <https://medium.com/ thrive-global/apple-has-reportedly-stopped-banning-this-mindfulness-app-from-the-app-store-e712e83d90e5> (Year: 2017), 2 pgs. |
| Mooij, Andre. “Tap to Begin.” dribbble.com. Published Nov. 22, 2016. Accessed Apr. 8, 2019. Available online at URL: <https:// dribbble.conn/shots/3113672-Tap-to-Begin> (Year: 2016), 1 pg. |
| Google LLC, International Preliminary Report on Patentability, PCT/US2018/020919, dated Nov. 12, 2019, 8 pgs. |
| Google Inc., International Search Report, PCT/US2016/037417, dated Sep. 15, 2016, 11 pgs. |
| Phillip Ian Wilson and John Fernandez, “Facial Feature Detection Using Haar Classifiers”, Consortium for Computing Sciences in Colleges 2006 (Year: 2006). |
| Stephen J. McKenna, Sumer Jabri, Zoran Duric, Azriel Rosenfeld, and Harry Wechsler, “Tracking Groups of People”, Computer Vision and Image Understanding 2000 (Year: 2000). |
| Number | Date | Country | |
|---|---|---|---|
| 20190243535 A1 | Aug 2019 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 15194528 | Jun 2016 | US |
| Child | 16385944 | US | |
| Parent | 14739412 | Jun 2015 | US |
| Child | 15194528 | US | |
| Parent | 14738930 | Jun 2015 | US |
| Child | 14739412 | US |
