Video recording doorbell
By using segmented radiator and mechanical waterproofing system in the video doorbell, the problems of clumsy and complex installation of traditional electronic doorbells are solved, and more efficient thermal management and waterproofing are achieved, improving user experience and security.
Patent Information
- Application Number
- CN202280095803.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2022-08-01
- Publication Date
- 2024-12-03
AI Technical Summary
Traditional electronic doorbells are bulky, difficult to manage thermally, poor waterproofness and complex installation, which affect user experience and security.
A compact video recording doorbell is designed with a radiator divided into separate sections for thermal control, combining a mechanically mobile waterproof system and an easy-to-install safety locking mechanism, using a separate radiator section and a printed circuit board section for improved heat Manage and waterproofness and simplify the installation process by installing studs and locking sheets.
It achieves more efficient thermal management and waterproofness, simplifies the installation process, and improves user experience and equipment safety and reliability.
Smart Images

Figure CN119072919A_ABST
Abstract
Description
Background Art
[0001] With the advancement of electronic doorbells for capturing images and / or videos, many users have begun to rely on their doorbell image data to see and / or identify people approaching the user's doorstep, or to determine whether a package has been delivered or picked up. Many traditional electronic doorbells can be large and bulky, which can detract from the user's experience. Some challenges that arise when building an electronic doorbell with a small form factor can include thermal management, waterproofing, power supply, and installation. Summary of the invention
[0002] This document describes a video doorbell. In various aspects, the video doorbell provides a compact, space-saving electronic doorbell camera device. Thermal control is enhanced by dividing the heat sink into separate sections for different heat dissipation subassemblies. The video doorbell includes a robust waterproof system, a portion of which enables mechanical movement of the button when the user presses the button to initiate the ring event. To enhance the user experience, the video doorbell also includes a mounting system that is easy to install and provides additional anti-theft security.
[0003] According to one aspect, a video doorbell includes a housing having a front outer surface and an opposite rear outer surface. In some implementations, the height of the housing along the y-axis is greater than the width along the x-axis and the depth along the z-axis, and the front outer surface is perpendicular to the z-axis. In some implementations, the front outer surface has a first opposite end and a second opposite end along the y-axis. The video doorbell may also include a camera module disposed at a first end (e.g., an upper end) of the housing. In some implementations, the camera module is configured to operate an image sensor and associated circuits to capture video data. The video doorbell may also include a printed circuit board disposed in the housing and having a circuit configured to continuously record and interpret video data. In addition, the video doorbell may include a button subassembly disposed at a second end (e.g., a lower end) of the housing and configured to be pressed by a person to initiate a ring event. In addition, the video doorbell may include a radiator having a separate first section and a second section. In some implementations, the first section of the radiator is disposed adjacent to the printed circuit board, and the second section of the radiator is disposed adjacent to the camera module. In some implementations, the first segment is positioned adjacent to the second segment with a predefined gap in the direction of the y-axis.
[0004] According to one aspect, a video doorbell includes a housing having a front outer surface and an opposite rear outer surface. The video doorbell may also include a camera module. In some implementations, the camera module is configured to operate an image sensor and associated circuits to capture video data. In some implementations, the camera module has a camera lens. The video doorbell may also include a printed circuit board disposed within the housing and having a circuit configured to continuously record video data. In addition, the video doorbell may include a button subassembly configured to be pressed by a person to initiate a ring event. The button subassembly may include: a button plate having an electrical pattern for initiating a ring event; a dome configured to complete a circuit when forced to contact the electrical pattern; an elastic button that can be folded to apply force to the dome so that the dome contacts the electrical pattern and completes the circuit; and a button cap that forms a depressible button on the front outer surface of the housing. The video doorbell device may further include: a first seal disposed between the button plate and the front housing component of the housing; and a second seal disposed between the button plate and the elastic button. The first seal and the second seal can prevent water entering the housing between the housing and the button cap of the button subassembly from reaching the electrical pattern on the button board.
[0005] According to one aspect, a video doorbell includes a housing having a front outer surface and an opposite rear outer surface. The video doorbell may also include a camera module. In some implementations, the camera module is configured to operate an image sensor and associated circuitry to capture video data. The video doorbell may also include a printed circuit board disposed within the housing and having a circuit configured to continuously record video data. In addition, the video doorbell may include a button subassembly configured to be pressed by a person to initiate a ring event. The video doorbell device may further include one or more mounting studs disposed on the rear outer surface of the housing. Wherein, a corresponding mounting stud of the one or more mounting studs may be fixed to a fastener disposed within the housing. The corresponding mounting stud may include a shaft extending outward from the rear outer surface of the housing; and a head having a diameter greater than the diameter of the shaft.
[0006] According to one aspect, a video doorbell includes a housing having a front outer surface and an opposite rear outer surface. The video doorbell may also include a camera module. In some implementations, the camera module is configured to operate an image sensor and associated circuits to capture video data. In some implementations, the camera module has a camera lens. The video doorbell may also include a printed circuit board that is disposed within the housing and has a circuit configured to continuously record video data. In addition, the video doorbell may include a button subassembly that is configured to be pressed by a person to initiate a ring event within a predefined duration. The button subassembly may further include: a button plate having an electrical pattern for initiating a ring event; and a dome that is configured to complete a circuit when forced to contact the electrical pattern, the circuit being configured to route line power to a buzzer within a predefined duration. Moreover, the video doorbell may include a battery frame that is configured to accommodate a battery for powering the circuit during a ring event.
[0007] This Summary is provided to introduce simplified concepts of a video doorbell that is further described in the Detailed Description below. This Summary is not intended to identify key features of the claimed subject matter, nor is it intended to be used to determine the scope of the claimed subject matter. BRIEF DESCRIPTION OF THE DRAWINGS
[0008] This document describes details of one or more aspects of the video doorbell with reference to the following drawings. Throughout the drawings, the same numbers are used to reference similar features and components: Figure 1A It is an example network environment that can implement various aspects of the video doorbell; Figure 1B The example environment of Figure 1 is shown in more detail; Figure 2A An example residence area network system is shown in which various aspects of a video doorbell may be implemented; Figure 2B An example operating environment is shown in which a server system interacts with a client device and a smart device according to some implementations; Figure 3 is a block diagram illustrating an example video server system according to some implementations; Figure 4A is a block diagram illustrating an example client device according to some implementations; Figure 4B shows a representative system architecture including a video source, a server system, and a client device according to some implementations; Figure 5 is a block diagram illustrating a representative client device associated with a user account according to some implementations; Figure 6 shows an isometric view of an example video recording doorbell according to some implementations; Figure 7 Shows Figure 6 A front elevation view of the example doorbell in FIG. Figure 8 According to some implementations, Figure 6 A right side elevation view of the example doorbell in FIG. Fig. 9 Shows Figure 6 A rear elevation view of the example doorbell in FIG. Fig.10 Shows Figure 6 An exploded view of the example doorbell in ; Fig.11 Shows Fig.10 An exploded view portion of the heat sink, showing a rear side of the heat sink, a main logic board subassembly, and a battery subassembly; Fig.12 Shown along Figure 7 The line AA in Figure 7 A cross-sectional view of the doorbell in FIG. Fig.13 Shows Fig.12 a portion of a cross-sectional view of the embodiment of the present invention, the portion including an example stack-up of a button subassembly; Fig.14 Shown along Figure 7 The line CC in Figure 7 A cross-sectional view of an example doorbell in FIG. Fig.15 Shown along Figure 7 A perspective cross-sectional view of the button side end of the doorbell taken along line AA in FIG. 1 , and an enlarged view of a portion of the cross-sectional view with mounting stud 904; Fig.16 Shown along Figure 7 The line CC in Figure 7 A cross-sectional view of an example doorbell in FIG. 1 ; and Fig.17A , Fig. 17B and Fig. 17C The locking mechanism for securing the doorbell to the wall plate is shown. DETAILED DESCRIPTION
[0009] This document describes a video doorbell. The technology described herein provides a video doorbell device including a housing, a button, and a camera module. The doorbell has enhanced passive thermal control and more robust waterproofing than many traditional video doorbells, as well as a mounting system that is simple to install and has improved anti-theft security.
[0010] In various aspects, a video doorbell includes a heat sink having separate sections, one section corresponding to the camera module and another section corresponding to the printed circuit board (PCB) (e.g., main logic board (MLB)) of the doorbell. Separating the heat sink into different sections for different heat-generating components and / or subassemblies significantly reduces the temperature compared to conventional doorbell devices that use a single heat sink for both the MLB and the camera module. The separate sections also prevent the heat of some components from spreading to other susceptible components.
[0011] To provide water resistance, the video doorbell includes water-resistant seals at locations within the housing of the doorbell. Based on the location of these seals, water may enter some areas behind the button from around the edges of the button (e.g., between the button and the housing), but will not reach areas or components susceptible to water damage, including circuitry. The placement of these seals allows the button and light ring features to move mechanically without risking water damage to circuitry (e.g., circuitry that triggers a ring event).
[0012] For installation, the video doorbell includes a mounting system for securing the doorbell to a surface and preventing movement in any direction. In various aspects, the doorbell includes a mounting stud extending from the rear exterior surface of the doorbell and including a wide head. The mounting stud is inserted into the wall plate through a hole, and the doorbell is slid into place to overlap the head of the mounting stud behind the wall plate. The wall plate also includes a locking tab that extends into a recessed volume defined in the rear exterior surface of the doorbell. A locking fastener is then inserted into the housing of the doorbell through the hole and fastened to the locking tab to prevent the doorbell from moving relative to the wall plate.
[0013] Additionally, the video doorbell is line powered, but includes a battery for powering the device during a ring event (e.g., based on a user pressing a button to activate the ring). Since the battery is only used during the ring event, the battery may be smaller than a conventional battery-powered video doorbell that requires continuous battery power for a longer period of time. The smaller size of the battery enables a smaller form factor for the doorbell than many conventional battery-powered video doorbells.
[0014] Thus, more efficient techniques for installation, water ingress prevention, and passive thermal control are provided for computing systems and devices.These disclosed systems and devices thereby improve the effectiveness, efficiency, and user satisfaction of such systems and devices.
[0015] While the features and concepts of the described technology for recording doorbells can be implemented in any number of different environments, various aspects are described in the context of the following examples.
[0016] Example Device
[0017] Figure 1AAn example network environment 100 (e.g., a network environment) in which a video doorbell can be implemented is shown. The network environment 100 includes a residential area network (HAN). The HAN includes wireless network devices 102 (e.g., electronic devices) arranged around a structure 104 such as a house and connected by one or more wireless and / or wired network technologies, as described below. The HAN includes a border router 106 that connects the HAN to an external network 108 such as the Internet through a residential router or access point 110.
[0018] To provide users with access to functionality implemented using wireless network devices 102 in the HAN, a cloud service 112 connects to the HAN via a border router 106, via a secure tunnel 114 through an external network 108 and access point 110. The cloud service 112 facilitates communication between the HAN and an Internet client 116, such as an app on a mobile device, using a web-based application programming interface (API) 118. The cloud service 112 also manages a home graph that describes the connections and relationships between wireless network devices 102, elements of the fabric 104, and users. As described in more detail below, the cloud service 112 hosts a controller that coordinates and arbitrates the home automation experience.
[0019] The HAN may include one or more wireless network devices 102 that act as a hub 120. The hub 120 may be a general home automation hub, or an application-specific hub such as a security hub, an energy management hub, a heating, ventilation and air conditioning (HVAC) hub, etc. The functionality of the hub 120 may also be integrated into any wireless network device 102, such as a smart thermostat device or a border router 106. In addition to hosting controllers on the cloud service 112, controllers may also be hosted on any hub 120 in the structure 104, such as a border router 106. Controllers hosted on the cloud service 112 may be dynamically moved to a hub 120 in the structure 104, such as moving an HVAC zone controller to a newly installed smart thermostat.
[0020] Hosting functionality on the hub 120 in the fabric 104 may improve reliability when a user's Internet connection is unreliable, may reduce latency for operations that would typically have to connect to the cloud service 112 , and may satisfy system and regulatory constraints surrounding local access between wireless network devices 102 .
[0021] The wireless network devices 102 in the HAN may be from a single manufacturer that also provides cloud services 112, or the HAN may include wireless network devices 102 from partners. These partners may also provide partner cloud services 122 that provide services related to their wireless network devices 102 through partner Web APIs 124. The partner cloud services 122 may alternatively or additionally provide services to Internet clients 116 via Web-based APIs 118, cloud services 112, and secure tunnels 114.
[0022] The network environment 100 can be implemented on various hosts such as battery powered microcontroller based devices, line powered devices, and servers hosting cloud services. The protocols operating in the wireless network devices 102 and the cloud services 112 provide a number of services that support the operation of the home automation experience in the distributed computing environment 100. These services include, but are not limited to, real-time distributed data management and subscription, command and response control, real-time event notification, historical data logging and preservation, cryptographically controlled security groups, time synchronization, network and service pairing, and software updates.
[0023] Figure 1B An example environment 130 is shown in which the Figure 1A The described home area network, and aspects of the video doorbell. In general, the environment 130 includes a home area network (HAN) implemented as part of a residence or other type of structure, which has any number of wireless network devices (e.g., wireless network devices 102) configured to communicate in a wireless network. For example, the wireless network devices may include a thermostat 132, a hazard detector 134 (e.g., for smoke and / or carbon monoxide), a camera 136 (e.g., indoors and outdoors), a lighting unit 138 (e.g., indoors and outdoors), and any other type of wireless network device 140 implemented inside and / or outside the structure 142 (e.g., in a residential environment). In this example, the wireless network devices may also include any of the previously described devices, such as the border router 106, and a mobile device (e.g., a smartphone) with an Internet client 116.
[0024] In environment 130, any number of wireless network devices may be implemented to wirelessly interconnect to communicate and interact with each other wirelessly. The wireless network devices are modular, intelligent, multi-sensing, network-connected devices that can be seamlessly integrated with each other and / or with a central server or cloud computing system to provide any of a variety of useful automation goals and implementations. Figures 6 to 17C Examples of wireless network devices are shown and described that may be implemented as any of the devices described herein.
[0025] In an implementation, the thermostat 132 may include a Nest® learning thermostat that detects ambient climate characteristics (e.g., temperature and / or humidity) in a residential environment and controls the HVAC system 144. The learning thermostat 132 and other network-connected devices "learn" by capturing the occupant settings of the device. For example, the thermostat learns preferred temperature set points in the morning and evening, as well as when the occupants of the structure go to sleep or wake up, and when the occupants are typically away or at home.
[0026] The hazard detectors 134 may be implemented to detect the presence of hazardous materials or materials indicative of hazardous materials (e.g., smoke, fire, or carbon monoxide). In an example of wireless interconnection, the hazard detectors 134 may detect the presence of smoke, which indicates a fire in a structure, in which case the hazard detector that first detects the smoke may broadcast a low-power wake-up signal to all connected wireless network devices. Other hazard detectors 134 may then receive the broadcasted wake-up signal and initiate wireless communications for a high-power state for hazard detection and receive an alarm message. In addition, the lighting unit 138 may receive the broadcasted wake-up signal and activate in an area of detected danger to illuminate and identify the problem area. In another example, the lighting unit 138 may be activated with one lighting color to indicate a problem area or zone in a structure, such as a problem area or zone for a detected fire or break-in, and activated with a different lighting color to indicate a safe zone and / or an escape route from the structure.
[0027] In various configurations, the wireless network device 140 may include an entrance interface device 146 that works in coordination with a network-connected door lock system 148 and detects and responds to a person approaching or leaving a location such as an exterior door of a structure 142. The entrance interface device 146 may interact with other wireless network devices based on whether a person approaches or enters a smart home environment. The entrance interface device 146 may control doorbell functionality, announce the approach or departure of a person via audio or visual means, and control settings on a security system, such as to activate or deactivate the security system when a resident enters or exits. The wireless network device 140 may also include other sensors and detectors, such as to detect ambient lighting conditions, detect room occupancy status (e.g., using an occupancy sensor 150), and control the power and / or dimming state of one or more lights. In some cases, sensors and / or detectors may also control the power state or speed of a fan such as a ceiling fan 152. In addition, sensors and / or detectors may detect occupancy in a room or enclosure and control the power supply to an electrical outlet or device 154, such as if the room or structure is not occupied.
[0028] Wireless network devices 140 may also include connected appliances and / or controlled systems 156, such as refrigerators, stoves and ovens, washers, dryers, air conditioners, pool heaters 158, irrigation systems 160, security systems 162, etc., and other electronic and computing devices, such as televisions, entertainment systems, computers, intercom systems, garage door openers 164, ceiling fans 152, control panels 166, etc. When plugged into a power source, the appliance, device, or system may announce itself to a home area network as described above, and may automatically integrate with controls and devices of a home area network, such as in a residence. It should be noted that wireless network devices 140 may include devices physically located outside of a structure but within wireless communication range, such as devices controlling a pool heater 158 or an irrigation system 160.
[0029] As described above, the HAN includes a border router 106 that interfaces to communicate with an external network outside the HAN. The border router 106 is connected to an access point 110 that is connected to an external network 108 such as the Internet. Cloud services 112 connected via the external network 108 provide services related to devices within the HAN and / or provide services using devices within the HAN. For example, the cloud services 112 may include applications for connecting end-user devices 168 such as smart phones, tablet computers, etc. to devices in a residential area network, processing data acquired in the HAN and presenting the data to end users, linking one or more devices in the HAN to a user account of the cloud service 112, configuring and updating devices in the HAN, etc. For example, a user can use a network-connected computer or a portable device such as a mobile phone or tablet computer device to control a thermostat 132 and other wireless network devices in a residential environment. In addition, the wireless network devices can transmit information to any central server or cloud computing system via the border router 106 and the access point 110. Data communications may occur using any of a variety of custom or standard wireless protocols (e.g., Wi-Fi, low-power ZigBee, 6LoWPAN, Thread, etc.) and / or by using any of a variety of custom or standard wired protocols (CAT6 Ethernet, HomePlug, etc.).
[0030] Any of the wireless network devices in the HAN can be used as a low power and communication node to create a HAN in a residential environment. Individual low power nodes of the network can periodically send out messages about what they are sensing, and other low power nodes in the environment - in addition to sending out their own messages - can also repeat the message, thereby transmitting the message from node to node (e.g., from device to device) throughout the residential area network. The wireless network devices can be implemented to save power, especially when powered by batteries, so as to receive messages using low power communication protocols, convert messages to other communication protocols, and send the converted messages to other nodes and / or a central server or cloud computing system. For example, the occupancy sensor 150 and / or the ambient light sensor 170 can detect occupants in a room and measure ambient light, and activate a light source when the ambient light sensor 170 detects that the room is dark and when the occupancy sensor 150 detects that someone is in the room. In addition, the sensor can include a low-power wireless communication chip (e.g., an IEEE 802.15.4 chip, a Thread chip, a ZigBee chip) that periodically sends out messages about the occupancy of the room and the amount of light in the room, including instant messages that coincide with the occupancy sensor detecting the presence of a person in the room. As described above, these messages can be sent wirelessly from node to node (e.g., network-connected device to network-connected device) within a residential environment using a home area network, as well as to a central server or cloud computing system via the Internet.
[0031] In other configurations, various wireless network devices in the wireless network device can act as a "tripwire" for the alarm system in the residential environment. For example, in the case where the criminal circumvents the detection of the alarm sensors located at the windows, doors and other entry points of the structure or environment, the alarm can still be triggered by receiving occupancy, motion, heat, sound, etc. messages from one or more of the low-power mesh nodes in the residential area network. In other implementations, the residential area network can be used to automatically turn on and off the lighting units 138 as people move from room to room in the structure. For example, the wireless network device can detect the movement of people through the structure and transmit corresponding messages via the nodes of the residential area network. Using the message indicating which rooms are occupied, other wireless network devices that receive the message can be activated and / or deactivated accordingly. As described above, the residential area network can also be used to provide exit lighting in an emergency, such as by turning on the appropriate lighting unit 138 leading to the safe exit. The lighting unit 138 can also be turned on to indicate the direction along the exit route that the person should travel to safely leave the structure.
[0032] Various wireless network devices may also be implemented to integrate and communicate with the wearable computing device 172, such as may be used to identify and locate occupants of a structure and adjust temperature, lighting, sound systems accordingly, etc. In other implementations, radio frequency identification (RFID) sensing (e.g., a person with an RFID bracelet, necklace, or keychain), synthetic vision technology (e.g., a camera and facial recognition processor), audio technology (e.g., voice, sound pattern, vibration pattern recognition), ultrasonic sensing / imaging technology, and infrared or near field communication (NFC) technology (e.g., a person wearing an infrared or NFC-enabled smartphone), and rule-based inference engines or artificial intelligence technology may draw useful conclusions about the location of occupants in a structure or environment from the sensed information.
[0033] In other implementations, personal comfort zone networks, personal health zone networks, personal safety zone networks, and / or other such human-oriented functionality of service robots can be enhanced by logical integration with other wireless network devices and sensors in the environment based on rule-based inference techniques or artificial intelligence techniques to achieve better performance of these functionalities. In an example involving a personal health area, the system can detect whether a family pet is moving toward the current location of the resident (e.g., using any of the wireless network devices and sensors, as well as rule-based inference and artificial intelligence techniques. Similarly, a hazard detector service robot can be notified that the temperature and humidity levels in the kitchen are rising, and any small increase in the ambient smoke level will most likely be due to cooking activities rather than due to a real dangerous condition. The hazard detection threshold, such as the smoke detection threshold, can be temporarily increased. Any service robot configured for any type of monitoring, detection, and / or service can be implemented as a mesh node device on a residential area network, conforming to a wireless interconnection protocol for communicating on the residential area network.
[0034] The wireless network device 140 may also include a network-connected alarm clock 174 for each of the individual occupants of the structure in the residential environment. For example, the occupant may customize and set the alarm device for a wake-up time, such as for the next day or the next week. Artificial intelligence may be used to consider the occupant's reaction to the alarm when it sounds, and to make inferences about preferred sleep patterns over time. Individual occupants may then be tracked in the residential area network based on a unique signature of the person, which is determined based on data obtained from sensors located in the wireless network device, such as sensors including ultrasonic sensors, passive IR sensors, and the like. The unique signature of the occupant may be based on a combination of movement patterns, voice, height, body shape, and the like, as well as using facial recognition technology.
[0035] In an example of wireless interconnection, an individual's wake-up time can be associated with a thermostat 132 to control the HVAC system in an efficient manner to preheat or cool the structure to desired sleeping and waking temperature settings. Preferred settings can be learned over time, such as by capturing the temperature set in the thermostat before the person falls asleep and when they wake up. The collected data can also include biometric indications of the person, such as breathing patterns, heart rate, movement, etc., based on which inferences are made in combination with data indicating when the person actually wakes up. Other wireless network devices can use this data to provide other automation goals, such as adjusting the thermostat 132 to preheat or cool the environment to the desired setting and turning on or off the lighting unit 138.
[0036] In implementations, the wireless network devices may also be used for sound, vibration, and / or motion sensing, such as to detect running water and determine inferences about water usage in a residential environment based on algorithms and mapping of water usage and consumption. This may be used to determine the characteristics or fingerprints of each water source in a residence, and is also referred to as "audio fingerprint water usage." Similarly, the wireless network devices may be used to detect subtle sounds, vibrations, and / or motion of unwanted pests, such as mice and other rodents, as well as termites, cockroaches, and other insects. The system may then notify occupants of suspected pests in the environment, such as with a warning message to help promote early detection and prevention.
[0037] Environment 130 may include one or more wireless network devices that act as a hub 176. Hub 176 (e.g., hub 120) may be a general home automation hub, or an application-specific hub such as a security hub, energy management hub, HVAC hub, etc. The functionality of hub 176 may also be integrated into any wireless network device such as a network-connected thermostat device or edge router 106. Hosting functionality on hub 176 in fabric 142 may improve reliability when a user's Internet connection is unreliable, may reduce latency for operations that would typically have to connect to cloud services 112, and may satisfy system and regulatory constraints around local access between wireless network devices.
[0038] In addition, the example environment 130 includes a network-connected speaker 178. The network-connected speaker 178 provides voice assistant services, including providing voice control of network-connected devices. The functionality of the hub 176 may be hosted in the network-connected speaker 178. The network-connected speaker 178 may be configured to communicate via a HAN, which may include a wireless mesh network, a Wi-Fi network, or both.
[0039] Figure 2A1 is a block diagram showing a representative network architecture 200 including a residential area network 202 (HAN 202) according to some implementations. In some implementations, smart devices 204 (e.g., wireless network devices 102) in the network environment 100 are combined with the hub 176 to create a mesh network in the HAN 202. In some implementations, one or more of the smart devices 204 in the HAN 202 operate as a smart home controller. Additionally and / or alternatively, the hub 176 can operate as a smart home controller. In some implementations, the smart home controller has more powerful computing capabilities than other smart devices. The smart home controller can process inputs (e.g., from the smart devices 204, the end-user devices 168, and / or the server system 206) and send commands (e.g., to the smart devices 204 in the HAN 202) to control the operation of the network environment 100. In various aspects, some smart devices 204 in the HAN 202 (e.g., in a mesh network) are "spokesperson" nodes (e.g., 204-1, 204-2), while other smart devices are "low-power" nodes (e.g., 204-n). Some smart devices in the network environment 100 may be battery-powered, while other smart devices may have a conventional and reliable power source, such as via line power (e.g., to a 120V line voltage line). Smart devices with a conventional and reliable power source are referred to as "spokesperson" nodes. These nodes are typically equipped with the ability to use wireless protocols to facilitate two-way communication with various other devices in the network environment 100 and a server system 206 (e.g., cloud services 112, partner cloud services 122). In some implementations, one or more "spokesperson" nodes operate as smart home controllers. On the other hand, battery-powered devices are "low-power" nodes. These nodes tend to be smaller than spokesperson nodes and typically communicate using only wireless protocols that require little power, such as Zigbee, ZWave, 6LoWPAN, Thread, Bluetooth, etc.
[0040] Some low-power nodes may not be able to perform two-way communication. These low-power nodes send messages, but cannot "listen". Therefore, other devices in the network environment 100 (such as a speaker node) cannot send information to these low-power nodes.
[0041] Some low-power nodes may only be capable of limited two-way communication. Due to this limited two-way communication, other devices may only be able to communicate with these low-power nodes during specific time periods.
[0042] As described above, in some implementations, smart devices act as low-power and speaker nodes to create a mesh network in the network environment 100. In some implementations, individual low-power nodes in the network environment periodically send out messages about what they are sensing, and other low-power nodes in the network environment—in addition to sending out their own messages—relay the messages, thereby propagating the messages from node to node (e.g., from device to device) throughout the HAN 202. In some implementations, a speaker node in the HAN 202 is capable of communicating using a relatively high-power communication protocol (e.g., IEEE 802.11), is capable of switching to a relatively low-power communication protocol (e.g., IEEE 802.15.4) to receive these messages, convert the messages to other communication protocols, and send the converted messages to other speaker nodes and / or the server system 206 (using, for example, a relatively high-power communication protocol). Thus, low-power nodes using a low-power communication protocol are capable of sending and / or receiving messages across the entire HAN 202 and to the server system 206 via the Internet (e.g., network 108). In some implementations, the mesh network enables the server system 206 to periodically receive data from most or all of the smart devices in the residence, make inferences based on the data, facilitate state synchronization across devices inside and outside the HAN 202, and send commands to one or more of the smart devices to perform tasks in the network environment.
[0043] As described above, the speaker node and some low-power nodes are capable of "listening". Thus, a user, other device, and / or server system 206 can communicate control commands to the low-power nodes. For example, a user can use an end-user device 168 (e.g., a smart phone) to send a command to the server system 206 over the Internet, which then relays the command to one or more speaker nodes in the HAN 202. The speaker node can use a low-power protocol to communicate the command to the low-power nodes throughout the HAN 202, as well as other speaker nodes that do not receive commands directly from the server system 206.
[0044] In some implementations, the lighting unit 138 ( Figure 1B) can be a low-power node. In addition to housing a light source, the lighting unit 138 can also house an occupancy sensor (e.g., occupancy sensor 150), such as an ultrasonic or passive IR sensor, and an ambient light sensor (e.g., ambient light sensor 170), such as a photoresistor or a single-pixel sensor that measures light in a room. In some implementations, the lighting unit 138 is configured to activate the light source when its ambient light sensor detects that the room is dark and when its occupancy sensor detects that someone is in the room. In other implementations, the lighting unit 138 is only configured to activate the light source when its ambient light sensor detects that the room is dark. In addition, in some implementations, the lighting unit 138 includes a low-power wireless communication chip (e.g., a ZigBee chip) that periodically sends out messages about the occupancy of the room and the amount of light in the room, including instant messages at the same time as the occupancy sensor detects the presence of a person in the room. As described above, these messages can be sent wirelessly (e.g., using a mesh network) from node to node (e.g., smart device to smart device) within the HAN 202, and sent to the server system 206 via the Internet (e.g., network 108).
[0045] Other examples of low-power nodes include battery-powered versions of hazard detectors 134. These hazard detectors 134 are typically located in areas where a constant and reliable power source is not available, and may include any number and type of sensors, such as smoke / fire / heat sensors (e.g., thermal radiation sensors), carbon monoxide / carbon dioxide sensors, occupancy / motion sensors, ambient light sensors, ambient temperature sensors, humidity sensors, etc. In addition, the hazard detectors 134 may send messages corresponding to each of the corresponding sensors to other devices and / or the server system 206, such as by using a mesh network as described above.
[0046] Examples of speaker nodes include entry interface devices 146 (e.g., smart doorbells), thermostats 132, control panels 166, power outlets or devices 154, and other wireless network devices 140. These devices are typically 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 various protocols.
[0047] In some implementations, the network environment 100 includes a controlled system 156, such as a service robot, that is configured to perform any of a variety of household tasks in an autonomous manner.
[0048] As reference Figure 1BAs explained, in some implementations, the network environment 100 includes a hub device (e.g., hub 176) that is communicatively coupled to the network 108 directly or via a network interface 208 (e.g., access point 110). The hub 176 is further communicatively coupled to one or more of the smart devices 204 using a radio communication network available at least in the network environment 100. The communication protocols used by the radio communication network include, but are not limited to, ZigBee, Z Wave, Insteon, EuOcean, Thread, OSIAN, Bluetooth Low Energy, etc. In some implementations, the hub 176 not only converts the data received from each smart device to meet the data format requirements of the network interface 208 or the network 108, but also converts the information received from the network interface 208 or the network 108 to meet the data format requirements of the corresponding communication protocol associated with the target smart device. In some implementations, in addition to data format conversion, the hub 176 further preliminarily processes the data received from the smart device or the information received from the network interface 208 or the network 108. For example, the hub 176 can integrate inputs from multiple sensors / connected devices (including sensors / devices of the same and / or different types), perform higher-level processing on those inputs—for example, to assess the overall environment and coordinate operations among different sensors / devices—and / or provide instructions to different devices based on the collection and programmatic processing of the inputs. It should also be noted that in some implementations, the network interface 208 and the hub 176 are integrated into one network device. The functionality described herein represents a specific implementation of a smart device, a control application running on a representative electronic device (e.g., a smart phone), a hub 176, and a server system 206 coupled to the hub 176 via the Internet or other wide area network. All or part of this functionality and associated operations can be performed by any element of the described system—for example, all or part of the functionality described herein performed by an implementation of the hub can be performed in whole or in part on a server, one or more connected smart devices and / or control applications, or different combinations thereof in different system implementations.
[0049] Figure 2B A representative operating environment 220 is shown in which a server system 206 provides data processing to monitor and facilitate review of events (e.g., motion, audio, security, etc.) in a video stream captured by a camera 136 (e.g., a video camera, a doorbell camera). Figure 2BAs shown, the server system 206 receives video data from video sources 222 (including cameras 224 or video doorbells 226) located at various physical locations (e.g., residences, restaurants, stores, streets, parking lots, and / or within or near the network environment 100 of FIG. 1). Each video source 222 can be linked to one or more reviewer accounts, and the server system 206 provides video surveillance data of the video source 222 to the client device 228 associated with the reviewer account. For example, the portable end-user device 168 is an example of a client device 228. In some implementations, the server system 206 is a video processing server that provides video processing services to the video sources and the client devices 228.
[0050] In some implementations, the server system 206 receives non-video data (e.g., audio data, metadata, digital data, etc.) from one or more smart devices 204. The non-video data can be analyzed to provide context for motion events detected by the camera 224 and / or the video doorbell 226. In some implementations, the non-video data indicates that an audio event (e.g., detected by an audio device such as an audio sensor integrated into a network-connected speaker 178), a security event (e.g., detected by a perimeter surveillance device such as a camera 136 and / or a motion sensor), a hazard event (e.g., detected by a hazard detector 134), a medical event (e.g., detected by a health monitoring device), etc., has occurred within the network environment 100.
[0051] In some implementations, multiple reviewer accounts are linked to a single network environment 100. For example, multiple occupants of a network environment 100 may have accounts that like the network environment 100. In some implementations, each reviewer account is associated with a particular access level. In some implementations, each reviewer account has personalized notification settings. In some implementations, a single reviewer account is linked to multiple network environments 100 (e.g., multiple different HANs). For example, a person may own or possess, or be assigned to review and / or manage multiple network environments 100. In some implementations, the reviewer account has different access levels and / or notification settings for each network environment.
[0052] In some implementations, each of the video sources 222 includes one or more cameras 224 or video doorbells 226 that capture video and send the captured video to the server system 206 in substantially real time. In some implementations, each of the video sources 222 includes one or more doorbells 226 that capture video and send the captured video to the server system 206 in real time (e.g., within 1 second, 10 seconds, 30 seconds, or 1 minute). Each of the doorbells 226 may include a camera that captures video and sends the captured video to the server system 206 in real time. In various aspects, the video sources 222 include a controller device (not shown) that acts as an intermediary between the one or more doorbells 226 and the server system 206. The controller device receives video data from the one or more doorbells 226, optionally performs some preliminary processing on the video data, and sends the video data and / or the results of the preliminary processing to the server system 206 on behalf of the one or more doorbells 226 (e.g., in real time). In some implementations, each camera has its own onboard processing capability to perform certain preliminary processing on the captured video data before sending the video data (e.g., along with metadata obtained through the preliminary processing) to the controller device and / or server system 206. In some implementations, one or more of the cameras are configured to optionally store the video data locally (e.g., for later transmission if requested by a user). In some implementations, the cameras are configured to perform certain processing on the captured video data and, based on the processing, send the video data in substantially real time, store the video data locally, or ignore the video data.
[0053] According to some implementations, the client device 228 includes a client-side module 230. In some implementations, the client-side module communicates with a server-side module 232 executed on the server system 206 via one or more networks 108. The client-side module provides client-side functionality for event monitoring and review processing and communication with the server-side module. The server-side module provides server-side functionality for event monitoring and review processing for any number of client-side modules that are each resident on a corresponding client device 228 (e.g., any one of the client devices 228-1 to 228-m). In some implementations, the server-side module 232 also provides server-side functionality for video processing and camera control for any number of video sources 222, including any number of control devices, cameras 136, and doorbells 226.
[0054] In some implementations, the server system 206 includes one or more processors 234, a video storage database 236, an account database 238, an input / output (I / O) interface 240 to one or more client devices 228, and an I / O interface 242 to one or more video sources 222. The I / O interface 242 to the one or more client devices 228 facilitates client-oriented input and output processing. The account database 238 stores multiple profiles of reviewer accounts registered in the video processing server, wherein the corresponding user profile includes account credentials of the corresponding reviewer account, and one or more video sources linked to the corresponding reviewer account. The I / O interface 242 to the one or more video sources 222 facilitates communication with one or more video sources 222 (e.g., one or more doorbells 226, cameras 136, and groups of associated controller devices). The video storage database 236 stores raw video data received from the video sources 222, as well as various types of metadata, such as motion events, event categories, event classification models, event filters, and event masks, for data processing for event monitoring and review of each reviewer account.
[0055] Examples of representative client devices 228 include handheld computers, wearable computing devices, personal digital assistants (PDAs), tablet computers, laptop computers, desktop computers, cellular telephones, smart phones, enhanced general packet radio service (EGPRS) mobile phones, media players, navigation devices, game consoles, televisions, remote controls, point of sale (POS) terminals, in-vehicle computers, e-book readers, or a combination of any two or more of these or other data processing devices.
[0056] Examples of one or more networks 108 include local area networks (LANs) and wide area networks (WANs), such as the Internet. One or more networks 108 are implemented using any known network protocols, 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 (VoIP), Wi-MAX, or any other suitable communication protocol.
[0057] In some implementations, the server system 206 is implemented on one or more independent data processing devices or a distributed computer network. The server system 206 may also employ the services of various virtual devices and / or third-party service providers (e.g., third-party cloud service providers) to provide the underlying computing resources and / or infrastructure resources of the server system 206. In some implementations, the server system 206 includes, but is not limited to, a server computer, 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.
[0058] Figure 2B The server-client environment shown includes a client side part (e.g., a client side module) and a server side part (e.g., a server side module). The functional division between the client part and the server part of the operating environment may be different in different implementations. Similarly, the functional division between the video source 222 and the server system 206 may be different in different implementations. For example, in some implementations, the client side module is a thin client that only provides user-oriented input and output processing functions, and all other data processing functionalities are delegated to the back-end server (e.g., the server system 206). Similarly, in some implementations, the corresponding video source in the video source 222 is a simple video capture device that continuously captures video data and streams the video data (e.g., continuous video recording (CVR)) to the server system 206, and the video data is subjected to limited local preliminary processing or no local preliminary processing. In some implementations, a respective one of the video sources 222 is an intelligent video capture device that captures video data in response to detection of an event (e.g., event-based recording (EBR)) and streams the video data to the server system 206. Although many aspects of the present technology are described from the perspective of the server system 206, those skilled in the art will appreciate the corresponding actions performed by the client device 228 and / or the video source 222. Similarly, some aspects of the present technology may be described from the perspective of the client device 228 or the video source 222, and those skilled in the art will appreciate the corresponding actions performed by the video server. In addition, some aspects of the present technology may be performed by the server system 206, the client device 228, and the video source 222 in collaboration.
[0059] In some aspects, a video source 222 (e.g., a camera 224 or doorbell 226 having an image sensor) sends one or more video data streams 244 to a server system 206. In some implementations, the one or more streams include multiple streams of raw video captured by the image sensor, the multiple streams having corresponding resolutions and / or frame rates. In some implementations, the multiple streams include: a "main" stream (e.g., 244-1) having a particular resolution and frame rate, the "main" stream corresponding to the raw video captured by the image sensor; and one or more additional streams (e.g., 244-2 through 244-q). The additional streams are optionally the same video stream as the "main" stream, but with a different resolution and / or frame rate, or streams that capture portions of the "main" stream (e.g., cropped to include a portion of the field of view or pixels of the main stream) at the same or different resolution and / or frame rate as the "main" stream. In some implementations, the main stream and / or additional streams are encoded dynamically (e.g., based on network conditions, server operating conditions, camera operating conditions, data characterization in the stream (e.g., whether motion is present), user preferences, etc.).
[0060] In some implementations, one or more of the streams 244 are sent directly from the video source 222 to the client device 228 (e.g., without being routed to or processed by the server system 206). In some implementations, one or more of the streams are stored in local memory of the doorbell 226 and / or at a local storage device (e.g., a dedicated recording device) such as a digital video recorder (DVR). For example, according to some implementations, the doorbell 226 stores the last 24 hours of video clips recorded by the camera. In some implementations, portions of one or more streams are stored at the doorbell 226 and / or the local storage device (e.g., portions corresponding to particular events or times of interest).
[0061] In some implementations, the server system 206 sends one or more video data streams 246 to the client device 228 to facilitate event monitoring by the user. In some implementations, the one or more streams may include multiple streams of the same video source with corresponding resolutions and / or frame rates. In some implementations, the multiple streams include: a "main" stream (e.g., 246-1) corresponding to the video source with a specific resolution and frame rate; and one or more additional streams (e.g., 246-2 to 246-t). The additional streams are optionally the same video stream as the "main" stream, but with a different resolution and / or frame rate, or streams that show a portion of the "main" stream (e.g., a portion cropped to include the field of view or pixels of the main stream) at the same or different resolution and / or frame rate as the "main" stream.
[0062] Figure 3A is a block diagram showing a server system 206 according to some implementations. The server system 206 typically includes one or more processors 302, one or more network interfaces 304 (e.g., including an I / O interface 240 to one or more client devices and an I / O interface 242 to one or more electronic devices), a memory 306, and one or more communication buses 308 for interconnecting these components (sometimes referred to as a chipset). The memory 306 includes a high-speed random access memory, such as DRAM, SRAM, DDR SRAM or other random access solid-state memory devices; and optionally includes a 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. The memory 306 optionally includes one or more storage devices located away from the one or more processors 302. The memory 306 or alternatively the non-volatile memory within the memory 306 includes a non-transitory computer-readable storage medium. In some implementations, the memory 306 or the non-transitory computer-readable storage medium of the memory 306 stores the following programs, modules and data structures or a subset or superset thereof: • an operating system 310 , which includes processes for handling various basic system services and for performing hardware-related tasks; • a network communication module 312 for connecting the server system 206 to other systems and devices (e.g., client devices, electronic devices, and systems connected to one or more networks 108) via one or more network interfaces 304 (wired or wireless); • Server-side modules 314, which provide server-side functionality for device control, data processing, and data review, including but not limited to: An account management module 316 for creating reviewer accounts, performing camera registration processing to establish associations between video sources and their corresponding reviewer accounts, and providing account login services to the client device 228; ○ Data receiving module 316, which is used to receive data from an electronic device (e.g., from Figure 2B 222 in the video source), and preparing the received data for further processing and storage in a data storage database (e.g., data storage database 332); o a device control module 320 for generating and sending server-initiated control commands to modify an operating mode of an electronic device (e.g., a device of the network environment 100), and / or receiving (e.g., from a client device 228) and forwarding user-initiated control commands to modify an operating mode of an electronic device; o A data processing module 322 for processing data provided by an electronic device and / or preparing and sending processed data to a device for review (e.g., to a client device 228 for user review); ○ An event detection module 324 for detecting motion event candidates in the video stream from each of the video sources 222, including motion trajectory identification, false alarm suppression, and event mask generation and caching; ○ An event classification module 326, which is used to classify motion events detected in the received video stream; and o a person identification module 328 for identifying features associated with human presence in a received video stream; and • Server database 330, which provides server-side storage of data associated with device control, data processing, and data review, including but not limited to: ○ A data storage database 332 for storing data (e.g., raw / processed image data) associated with each electronic device (e.g., each video source 222) for each user account, as well as data processing models, processed data results, and other relevant metadata associated with the data (e.g., name of the data result, location of the electronic device, creation time, duration, settings of the electronic device, etc.), wherein (optionally) all or part of the data and / or processing associated with the hub 176 or smart device is securely stored; and ○ Account database 334, which is used to store account information of user accounts, including user account information, such as user profiles, information and settings of linked hub devices and electronic devices (e.g., hub device identification), hub device-specific secrets, related user and hardware characteristics (e.g., service layer, device model, storage capacity, processing power, etc.), user interface settings, data review preferences, etc., wherein the information of the associated electronic devices includes but is not limited to one or more device identifiers (e.g., media access control (MAC) addresses and universally unique identifiers (UUID)), device-specific secrets, and displayed titles.
[0063] Each of the elements identified above can be stored in one or more of the aforementioned memory devices, and can correspond to an instruction set for performing the above functions. The modules or programs (e.g., instruction sets) identified above do not need to be implemented as separate software programs, processes, or modules, so each subset of these modules can be combined or otherwise rearranged in various implementations. In some implementations, memory 306 optionally stores a subset of the modules and data structures identified above. In addition, memory 306 optionally stores additional modules and data structures not described above.
[0064] Figure 4A 1 is a block diagram illustrating an example smart device 204 according to some implementations. In some implementations, the smart device 204 (e.g., any device of the network environment 100 in FIG. 1, including the end-user device 168) includes one or more processors 402 (e.g., CPU, ASIC, FPGA, microprocessor, etc.), one or more communication interfaces 404 with a radio transceiver 406, an image sensor 408, a user interface 410, a sensor 412, a memory 414, and one or more communication buses 416 for interconnecting these components (sometimes referred to as a chipset). In some implementations, the user interface 410 includes one or more output devices 418 that enable presentation of media content, including one or more speakers and / or one or more visual displays. In some implementations, the user interface 410 includes one or more input devices 420, including user interface components that facilitate user input, such as a keyboard, a mouse, a voice command input unit or a microphone, a touch screen display, a touch-sensitive input pad, a gesture capture camera, or other input buttons or controls. In some implementations, the input device 420 of the doorbell 226 is a tactile or touch-sensitive doorbell button. In addition, some smart devices 204 use microphones and voice recognition or cameras and gesture recognition to supplement or replace keyboards.
[0065] Sensors 422 include, for example, one or more thermal radiation sensors, ambient temperature sensors, humidity sensors, infrared (IR) sensors (such as passive infrared (PIR) sensors), proximity sensors, range sensors, occupancy sensors (e.g., using RFID sensors), ambient light sensors (ALS), motion sensors 422, location sensors (e.g., global positioning satellite (GPS) sensors), accelerometers and / or gyroscopes.
[0066] In some implementations, the smart device 204 includes an energy storage component 424 (e.g., one or more batteries and / or capacitors). In some implementations, the energy storage component 424 includes a power management integrated circuit (IC). In some implementations, the energy storage component 424 includes a circuit for harvesting energy from a signal received via an antenna (e.g., a radio transceiver 406) of the smart device. In some implementations, the energy storage component 424 includes a circuit for collecting thermal energy, vibration energy, electromagnetic energy, and / or solar energy received by the smart device. In some implementations, the energy storage component 424 includes a circuit for monitoring the stored energy level and adjusting operations and / or generating notifications based on changes in the stored energy level.
[0067] The communication interface 404 includes, for example, hardware capable of communicating data 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.5A, 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 that have not yet been developed as of the filing date of this document. The radio transceiver 406 enables one or more radio communication networks in the network environment 100 and enables the smart device 204 to communicate with other devices. In some implementations, the radio transceiver 406 is capable of communicating data 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.5A, WirelessHART, MiWi, etc.).
[0068] The memory 414 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. The memory 414 or alternatively the non-volatile memory within the memory 414 includes a non-transitory computer-readable storage medium. In some implementations, the memory 414 or the non-transitory computer-readable storage medium of the memory 414 stores the following programs, modules, and data structures, or a subset or superset thereof: • Operational logic 426, which includes procedures for handling various basic system services and for performing hardware-related tasks; • a communication module 428 for coupling to and communicating with other network devices (e.g., network interfaces 208, such as routers providing Internet connectivity, networked storage devices, network routing devices, server systems 206, other smart devices 204, client devices 228, etc.) connected to one or more networks 108 via one or more communication interfaces 404 (wired or wireless); • an input processing module 430 for detecting one or more user inputs or interactions from one or more input devices 420 and interpreting the detected inputs or interactions; • a user interface module 432 for providing and presenting a user interface in which settings, captured data, and / or other data of one or more devices (e.g., smart device 204, and / or other devices in network environment 100) may be configured and / or viewed; • one or more applications 434 for execution by the smart device (e.g., games, social networking applications, smart home applications, and / or other web-based or non-web applications) for controlling the device (e.g., executing commands, sending commands, and / or configuring settings of the smart device 204 and / or other client / electronic devices) and for reviewing data captured by the device (e.g., device status and settings, captured data, or other information about the smart device 204 and / or other client / electronic devices); • Device-side modules 436, which provide device-side functions for device control, data processing, and data review, including but not limited to: o A command module 438 for receiving, forwarding and / or executing instructions and control commands for operating the smart device 204 (e.g., from the client device 228, from the server system 206, from user input detected at the user interface 410, etc.); and o A data processing module 440 for processing data captured or received by one or more inputs (e.g., input device 420, image sensor 408, sensor 412, interfaces (e.g., communication interface 404, radio 406), and / or other components of smart device 204, and for preparing and sending the processed data to a remote device (e.g., client device 228) for user review; • a camera module 442 for operating the image sensor 408 and associated circuitry, e.g., for enabling and disabling the image sensor 408 based on data from one or more low-power sensors 412 (e.g., data from a PIR sensor or an ALS), the camera module including an encoding module 444 for adjusting encoding of raw image data captured by the image sensor 408 (e.g., adjusting format, resolution, and / or frame rate); • a transmission access module 446 for granting or denying transmission access to one or more radio transceiver devices 406 (eg, based on detected control signals and transmission requests); • An event analysis module 448, which is used to analyze the captured sensor data, for example to detect and / or identify approaching visitors and context information, and includes but is not limited to: o A motion detection module 450 for detecting events in the network environment (eg, motion events in video data), such as an approaching guest; and o a context sensing module 452 for detecting contextual data about an approaching guest, such as based on behavioral characteristics, object recognition, facial recognition, voice recognition, timing information, and user data associated with a user profile of a user (e.g., an occupant); o A characterization module 454 for characterizing entities, persons (e.g., approaching guests), and / or events detected by or associated with the smart device 204; • Device data 456, which stores data associated with a device (e.g., smart device 204), including but not limited to: ○ Account data 458, which stores information related to a user account linked to the smart device 204, including, for example, cached login credentials, smart device identifiers (e.g., MAC address and UUID), user interface settings, display preferences, authentication tokens and tags, cryptographic keys, etc.; o A local data storage device 460 for selectively storing raw data or processed data associated with the smart device 204, such as event data and / or video data captured by the image sensor 408; o Entity data 462, which stores information related to detected people and other entities, such as characterization information (e.g., characterization data 468) and associated images; o Power parameters 464, which store energy information, such as information related to the energy storage component 424 (e.g., estimated battery life), power settings of the smart device 204, power states of the smart device 204, power preferences of a user of the smart device 204, etc.; o Category information 466 detailing event categories used (eg, in conjunction with event analysis module 448) to categorize events detected by or involving a smart device; and ○ Characterization data 468 for entities, persons, and / or events detected by or associated with the smart device 204 (eg, data generated or used by the characterization module 454).
[0069] Each element in the elements identified above can be stored in one or more memory devices in the previously mentioned memory devices, and corresponds to the instruction set for performing the functions described above. The modules or programs (e.g., instruction sets) identified above do not need to be implemented as separate software programs, processes or modules, so each subset of these modules can be combined or otherwise rearranged in various implementations. In some implementations, memory 414 optionally stores a subset of the modules and data structures identified above. In addition, memory 414 optionally stores additional modules and data structures not described above, such as a sensor management module for managing the operation of sensor 412.
[0070] Figure 4BA representative system architecture 470 is shown according to some implementations, which includes a video source 222, a server system 206, and a client device 228. In some implementations, the server system 206 includes functional modules for an event processor 472, an event classifier 474, an entity recognition module 326, and a user-facing front end 476 (e.g., a server-side module 314). The event processor 472 obtains event candidates (e.g., by processing a video stream 478, by receiving event start information from the video source 222, or by detecting a user pressing a doorbell button of a video doorbell device 226). In some implementations, the event candidates include motion event candidates. In some implementations, the event candidates include audio event candidates. In some implementations, the event candidates include a user pressing a doorbell button of a video doorbell device 226. In some implementations, the event candidates include audio, electromagnetic, olfactory, and / or visual aspects. In some implementations, the event candidates include motion events, proximity detection, and announcement detection. The event classifier 474 classifies event candidates into different event categories (e.g., based on data from the event processor and / or entity identifier). The user-facing front end 476 generates event alerts and notifications and facilitates reviewers to review detected entities and events through a review interface on the client device 228. The user-facing front end 476 also receives user edits to event and entity categories, user preferences for alert and event filters, partition definitions of interest partitions, etc. The event classifier 474 optionally modifies event classification models and results based on user edits received by the user-facing front end 476. The entity recognition module 326 optionally modifies entity classifications and / or labels based on user edits received by the user-facing front end 476. The server system 206 also includes a database for storing video source data 480, personnel data 482, event classification models 484, and event data and event masks 486. In an implementation, the personnel data 482 is stored in a personnel database (e.g., the personnel database 358). In some implementations, each of these databases is part of the server database 340 (eg, part of the data storage database 330 ).
[0071] The server system 206 receives one or more video streams 478 from the video source 222, and optionally receives event candidate information 488, such as preliminary characterization information of detected entities and events (e.g., entity and event metadata from processing performed at the doorbell device 226), and source information 488 such as device settings of the doorbell device 226 (e.g., the device profile 350 of the doorbell device 226). In some implementations, the event processor 472 communicates with the video source 222 and / or one or more other devices of the network environment, for example, to request additional image data, audio data, and sensor data, such as high-definition images or metadata of the video stream 478. The server system sends an alert 491 for the event, an alert 492 for the detected person, event timeline information 493, and / or video data 494 (e.g., still images or video clips corresponding to the detected person and / or event) to the client device 228. In some implementations, the alert distinguishes a guest approach event from other types of motion events. In some implementations, the alert distinguishes motion events captured at the doorbell device 226 from motion events captured by other smart devices (e.g., camera 136). Server system 206 optionally receives user information from client device 228, such as event data 495 (e.g., compilation of event categories), zone definitions 496, and personnel data 497 (e.g., classification of detected personnel).
[0072] The data processing pipeline processes video information (e.g., live video feeds) received from video sources 222 (e.g., including doorbell devices 226 and optional controller devices) and / or audio information received from one or more smart devices in real time (e.g., within 10 seconds, 30 seconds, or 2 minutes) to identify and classify events occurring in the network environment, and sends real-time event alerts (e.g., within 10 seconds, 20 seconds, or 30 seconds) and / or refreshed event timelines (e.g., within 30 seconds, 1 minute, or 3 minutes) to client devices 228 associated with reviewer accounts of the network environment. The data processing pipeline also processes stored information (such as stored video feeds from video sources 222) to re-evaluate and / or re-classify events as needed (such as when new information about the event is obtained and / or when new information about the event category is obtained (e.g., new activity zone definitions are obtained from users)).
[0073] After the video and / or audio data is captured at the smart device, the data is processed to determine if there are any potential event candidates or persons. In some implementations, the data is initially processed at the smart device (e.g., video source 222, camera 136, or doorbell device 226). Therefore, in some implementations, the smart device sends event candidate information 488, such as event start information, to the server system 206. In some implementations, the data is processed at the server system 206 for event start detection. In some implementations, the video and / or audio data is stored at the server system 206 (e.g., stored in a video storage database 236). In some implementations, the visual / audio data is stored at a server distinct from the server system 206. In some implementations, after the start of motion is detected, the relevant portion of the video stream is retrieved from the storage device (e.g., from the video storage database 236).
[0074] In some implementations, the event recognition process includes segmenting the video stream into multiple segments and then classifying event candidates within each segment. In some implementations, classifying event candidates includes aggregation of background factors, entity detection and recognition, motion vector generation for each moving entity, entity features and scene features to generate motion features for event candidates. In some implementations, the event recognition process further includes classifying each segment, generating or updating event records based on the classification of the segments, generating alarms for events based on the classification of the segments, classifying complete events, updating event records based on complete events, and generating alarms for events based on complete events. In some implementations, the classification is based on the determination that the event occurs within a specific partition of interest. In some implementations, the classification is based on the determination that the event candidate involves one or more partitions of interest. In some implementations, the classification is based on audio data and / or audio event representations.
[0075] The event analysis and classification process can be performed by the intelligent device (e.g., video source 222) and the server system 206 in collaboration, and the division of tasks can be different in different implementations for different equipment capability configurations, power parameters, and / or for different network, device, and server load conditions. After the server system 206 classifies the event candidates, the results of the event detection and classification can be sent to a reviewer associated with the network environment.
[0076] In some implementations, the server system 206 stores raw or compressed video source data 480 (e.g., stored in the video storage database 236), event classification models 484 (e.g., stored in the classification model database 360), and event masks and other event metadata (e.g., stored in the event information database 352) for each of the video sources 222. In some implementations, the video data is stored at one or more display resolutions such as 480p, 780p, 1080i, 1080p, etc.
[0077] In some implementations, video source 222 (e.g., doorbell device 226) transmits a real-time video feed to remote server system 206 via one or more networks (e.g., network 108). In some implementations, the transmission of video data is continuous as the video data is captured by doorbell device 226. In some implementations, the transmission of video data is independent of the content of the video data, and uploading video data from video source 222 to server system 206 for storage is independent of whether any motion events have been captured in the video data. In some implementations, video data is stored in a local storage device of video source 222 by default, and only portions of the video corresponding to motion event candidates detected in the video stream are uploaded to server system 206 (e.g., in real time or upon request by a user).
[0078] In some implementations, video source 222 dynamically determines at what display resolution to upload the video stream to server system 206. In some implementations, video source 222 dynamically determines which portions of the video stream to upload to server system 206. For example, in some implementations, depending on the current server load and network conditions, video source 222 optionally prioritizes uploading of a portion of the video corresponding to a newly detected motion event candidate over other portions of the video stream that do not contain any motion event candidates; or, video source 222 uploads a portion of the video corresponding to a newly detected motion event candidate at a higher display resolution than other portions of the video stream. This upload prioritization helps ensure that motion events of interest can be detected in real time and alerted to reviewers even when network conditions and server load are less than ideal. In some implementations, video source 222 implements two parallel upload connections, one for uploading a continuous video stream captured by doorbell device 226, and another for uploading a portion of the video corresponding to a detected motion event candidate. At any given time, Video Source 222 determines whether it is necessary to temporarily pause the upload of the continuous video stream to ensure that sufficient bandwidth is given to the upload of the video segment corresponding to the newly detected motion event candidate.
[0079] In some implementations, the video stream uploaded for cloud storage is of lower quality (eg, lower resolution, lower frame rate, higher compression, etc.) than the video clips uploaded for motion event processing.
[0080] like Figure 4B As shown, the video source 222 optionally includes a video doorbell device 226 and an optional controller device 498. In some implementations, the doorbell device 226 includes sufficient onboard processing power to perform all necessary local video processing tasks (e.g., cue point detection for motion event candidates, video upload prioritization, network connection management, etc.), and the doorbell device 226 communicates directly with the server system 206 without any controller device as an intermediary. In some implementations, the doorbell device 226 captures video data and sends the video data to the controller device for necessary local video processing tasks. The controller device 498 optionally performs local processing tasks for multiple cameras. For example, there may be multiple cameras in a network environment (e.g., the network environment 100 of FIG. 1), and a single controller device 498 receives video data from each camera and processes the video data to detect motion event candidates in the video stream from each camera. The controller device 498 is responsible for allocating sufficient outgoing network bandwidth to send video clips containing motion event candidates from each camera to the server system 206 before using the remaining bandwidth to send the video stream from each camera to the server system 206. In some implementations, a continuous video stream is sent and stored at one server facility, while video segments containing motion event candidates are sent to and processed at a different server facility.
[0081] In some implementations, the smart device sends additional source information 490 to the server system 206. The additional source information 490 can include information about the state of the device (e.g., IR mode, automatic exposure (AE) mode) and / or information about the environment in which the device is located (e.g., indoors, outdoors, night, day, etc.). In some implementations, the source information 490 is used by the server system 206 to perform event detection, entity recognition, and / or classify event candidates. In some implementations, the additional source information 490 includes one or more preliminary results from video processing performed by the video source 222 (e.g., the doorbell device 226), such as classification, object / entity recognition, motion mask, etc.
[0082] In some implementations, the portion of the video after the event start event is detected is divided into multiple segments. In some implementations, segmentation continues until event end information (sometimes referred to as an "event end signal") is obtained. In some implementations, segmentation occurs within the server system 206 (e.g., by the event processor 472). In some implementations, segmentation includes generating overlapping segments. For example, a 10-second segment is generated every second so that the new segment overlaps the previous segment by 9 seconds.
[0083] In some implementations, each of the plurality of segments has the same or similar duration (e.g., each segment has a duration of 10 to 12 seconds). In some implementations, a first segment has a shorter duration than a subsequent segment. Keeping the first segment short allows for real-time initial classification and alerting based on processing the first segment. The initial classification can then be revised based on processing of subsequent segments. In some implementations, a new segment is generated if the moving entity enters a new zone of interest.
[0084] In some implementations, after the event processor module obtains the video portion corresponding to the event candidate, the event processor 472 obtains background factors and performs motion entity detection identification, motion vector generation for each motion entity, and feature identification. Once the event processor 472 completes these tasks, the event classifier 474 gathers all information and generates classification for the motion event candidate. In some implementations, the event processor 472 and the event classifier 474 are parts of the video processing module 322. In some implementations, before submitting the motion event candidate for event classification, false positive example suppression is optionally performed to reject some motion event candidates. In some implementations, determining whether the motion event candidate is a false positive example includes determining whether the motion event candidate occurs in a specific partition. In some implementations, determining whether the motion event candidate is a false positive example includes analyzing the importance score of the motion event candidate. The importance score of the motion event candidate is optionally based on the interested partition, background features, motion vector, scene features, entity features, motion features, motion trajectory, etc. involved in the motion event candidate.
[0085] In some implementations, video source 222 has sufficient processing power to perform and does perform entity detection, person recognition, background estimation, moving entity recognition, motion vector generation, and / or feature recognition.
[0086] Figure 52 is a block diagram showing a representative client device 228 associated with a user account according to some implementations. The client device 228 typically includes one or more processing units (CPUs) 502, one or more network interfaces 504, a memory 506, and one or more communication buses 508 for interconnecting these components (sometimes referred to as a chipset). Optionally, the client device also includes a user interface 510 and one or more built-in sensors 512 (e.g., accelerometers and gyroscopes). The user interface 510 includes one or more output devices 514 that implement the presentation of media content, and the one or more output devices include one or more speakers and / or one or more visual displays. The user interface 510 also includes one or more input devices 516, which include user interface components that facilitate user input, such as a keyboard, a mouse, a voice command input unit or a microphone, a touch screen display, a touch-sensitive input pad, a gesture capture camera, or other input buttons or controls. In addition, some client devices use microphones and voice recognition or cameras and gesture recognition to supplement or replace keyboards. In some implementations, the client device includes one or more cameras, scanners, or light sensor units (not shown) for capturing images. Optionally, the client device includes a location detection device 518, such as a GPS sensor or other geo-location receiver, for determining the location of the client device.
[0087] The memory 506 includes high-speed random access memory, such as DRAM, SRAM, DDR SRAM 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. The memory 506 optionally includes one or more storage devices located away from the one or more processing units 502. The memory 506 or alternatively the non-volatile memory within the memory 506 includes a non-transitory computer-readable storage medium. In some implementations, the memory 506 or the non-transitory computer-readable storage medium of the memory 506 stores the following programs, modules and data structures or a subset or superset thereof: • an operating system 520 , which includes processes for handling various basic system services and for performing hardware-related tasks; • a network communication module 522 for connecting the client device 228 to other systems and devices (eg, client devices, electronic devices, and systems connected to one or more networks 108) via one or more network interfaces 504 (wired or wireless); • an input processing module 524 for detecting one or more user inputs or interactions from one of the one or more input devices 516 and interpreting the detected inputs or interactions; • One or more applications 526 (e.g., games, social networking applications, smart home applications, and / or other web-based or non-web applications) for execution by the client device, which are used to control the device (e.g., send commands to the hub device and / or other client or electronic devices, configure settings, etc.), and to review data captured by the device (e.g., device status and settings, captured data, or other information about the hub device or other connected devices); • a user interface module 528 for providing and displaying a user interface in which settings, captured data, and / or other data of one or more devices (e.g., smart devices 204 in the network environment 100) may be configured and / or viewed; • Client-side modules 530, which provide client-side functionality for device control, data processing, and data review, including but not limited to: ○ A device control module 532, which is used to generate control commands for modifying the operation mode of the smart device (and optionally other electronic devices) according to user input; o A video analytics module 534 for analyzing captured video data, e.g., to detect and / or identify persons, objects, animals, and events; o A data review module 536, which is used to provide a user interface for reviewing data from the server system 206 or the video source 222, and includes but is not limited to: ■ an event review module 538 for reviewing events (eg, motion and / or audio events) and optionally enabling a user to edit and / or update the events; and ■ a people review module 540 for reviewing data and / or images regarding detected people and other entities, and optionally enabling a user to edit and / or update the people data; o a presentation module 542 for presenting a user interface and response options for interacting with the smart device 204 and / or the server system 206; and o A remote interaction module 544 for interacting with a remote person (eg, a visitor to the network environment 100 ), for example, via the smart device 204 and / or the server system 206 ; and • Client data 546, which stores data associated with the user account and electronic device, including but not limited to: ○ Account data 548, which stores information related to both the user account loaded on the client device and the electronic device (e.g., of video source 222) associated with the user account, wherein such information includes cached login credentials, hub device identifiers (e.g., MAC address and UUID), electronic device identifiers (e.g., MAC address and UUID), user interface settings, display preferences, authentication tokens and tags, cryptographic keys, etc.; and o A local data storage database 550 for selectively storing raw or processed data associated with an electronic device (eg, a video source 222 such as a doorbell 226), optionally including entity data as previously described.
[0088] Each of the elements identified above can be stored in one or more of the aforementioned memory devices, and can correspond to an instruction set for performing the above functions. The modules or programs (e.g., instruction sets) identified above do not need to be implemented as separate software programs, processes, modules, or data structures, and therefore each subset of these modules can be combined or otherwise rearranged in various implementations. In some implementations, memory 506 optionally stores a subset of the modules and data structures identified above. In addition, memory 506 optionally stores additional modules and data structures not described above.
[0089] Example Implementation
[0090] Figure 6 An isometric view 600 of an example video doorbell (e.g., doorbell 226) according to some implementations is shown. Doorbell 226 is shown having a longitudinal axis 602 (e.g., y-axis), a transverse axis 604 (e.g., x-axis), and a central axis 606 (e.g., z-axis). Doorbell 226 can be elongated along the longitudinal axis such that the height of doorbell 226 along longitudinal axis 602 is significantly greater than the width along transverse axis 604 (at least two orders of magnitude greater), and the width is greater than the depth along central axis 606 (at least 1.5 times greater). Doorbell 226 includes a camera-side end 608 and a button-side end 610, which are located at opposite ends of a first surface (e.g., front exterior surface 612) of the housing. The camera side end 608 of the doorbell 226 includes an IR cover 614, which includes a portion that is substantially transparent (e.g., 70%, 80%, 90%, 100% transparent) or translucent (e.g., between 31% and 69% transparent) to IR light and another portion that is substantially opaque (e.g., 70%, 80%, 90%, 100% opaque) to IR light.
[0091] In various aspects, the IR cover extends outwardly from the front exterior surface 612 of the housing of the doorbell 226. The IR cover 614 forms an annular shape with a central aperture for a camera module (e.g., Figure 4A The camera lens 616 of the camera module 442 in the housing (e.g., the camera module 442 in the housing) extends through the central aperture. The annular shape is generally elliptical, and in some cases, the shape can be circular when the major axis and the minor axis of the annular shape are equal. A retainer 618 (e.g., a lens retainer) surrounds the camera lens 616 in the xy plane and extends through the central aperture of the IR cover 614 to protrude from the outer surface of the IR cover 614. In an example, the retainer 618 has a substantially tubular shape (with an elliptical cross-section, such as a circular cross-section), and the camera lens 616 is positioned within the central region of the retainer 618. Both the retainer 618 and the camera lens 616 extend outwardly from the front outer surface 612 of the housing, including extending outwardly from the outer surface of the IR cover 614. In some implementations, the camera lens 616 protrudes slightly (along the z-axis) from the end of the retainer 618. The retainer 618 reduces and / or prevents IR light from leaking through the IR cover 614 into the camera lens 616. The IR light can be provided by an IR illuminator (e.g., an IR LED) disposed behind the IR cover 614 and configured to direct the IR light through one or more apertures 620 in the IR cover 614. In addition, the IR light can be received from the surrounding environment through the IR cover and captured by a sensor (e.g., an image sensor, a passive infrared (PIR) sensor). Thus, the retainer 618 prevents IR light from leaking from the IR cover 614 into the sides or edges of the camera lens 616.
[0092] The button-side end 610 of the doorbell 226 includes a button 622 that can be pressed by a user to initiate a notification (e.g., a ring). In various aspects, the button 622 can be surrounded by a halo 624 that can be substantially flush with the front exterior surface 612 of the doorbell 226. The button 622 and / or halo 624 can have a shape and / or size that substantially matches the profile and / or size of the IR cover 614. In one example, the button 622 can have a diameter that is substantially equal to the outer diameter of the IR cover 614. In another example, the halo 624 has an outer diameter that is substantially the same as the outer diameter of the IR cover 614.
[0093] Figure 7 Shows Figure 6 700 of the front elevation view of the example doorbell 226 in FIG. As shown, the camera module 442 ( Figure 7The camera lens 616 (not shown) is centered relative to the IR cover 614 and surrounded by the holder 618. In the xy plane (e.g., a cross section of the holder 618), the button 622 has an elliptical shape, wherein its major and minor axes are different (e.g., forming an ellipse) or equal to each other (e.g., forming a circle). The IR cover 614 can have an elliptical shape similar to the button 622. In addition, in the examples described herein, the doorbell 226 has an oblong shape. However, the doorbell 226 can have any suitable shape and is not limited to the exact shape described herein.
[0094] Figure 8 According to some implementations, Figure 6 800 of a right side elevation view of the example doorbell 226 in FIG. As shown, the retainer 618 extends outwardly (in the z-direction) from the IR cover 614, which prevents IR light traveling through the IR cover 614 from leaking into the camera lens 616. The camera lens 616 may extend outwardly (in the z-direction) from the retainer 618 so that an image sensor (e.g., Figure 4A The field of view of the image sensor 408 in the image sensor 408 is maximized. In various aspects, the doorbell 226 includes a housing formed by a front housing member 802 fixed to a rear housing member 804.
[0095] Fig. 9 Shows Figure 6 900 of a rear elevation view of an example doorbell 226 in FIG. In the illustrated example, the doorbell 226 includes a rear exterior surface 902 of a rear housing member 804 that includes one or more features for mounting the doorbell 226 to a surface such as a wall. As described in more detail herein, the doorbell 226 includes one or more mounting studs 904 disposed on the rear exterior surface 902 of the doorbell 226. The mounting studs 904 can be used to mount the doorbell to a wall plate, a bracket, or other portion connected to a wall. The rear exterior surface 902 also includes or defines a recessed volume 906 that accommodates a locking tab of the wall plate to secure the doorbell 226 to the wall plate. Further discussion of this feature and other features will be provided in more detail below. Additional fasteners 908 can be used to secure the rear housing component 804 to one or more internal components (e.g., a heat sink, a printed circuit board) and / or the front housing component 802.
[0096] Fig.10 Shows Figure 6 1000 of an exploded view of an example doorbell 226 in FIG. The front housing component 802 and the rear housing component 804 are connected together to form a housing that surrounds the various components of the doorbell 226. The IR cover 614 is assembled to an outer surface (e.g., a first surface, i.e., a first surface) of the front housing component 802. Figure 6 The front outer surface 612 in FIG.
[0097] At the button side end 610, the doorbell 226 includes a button subassembly 1002 (also referred to as button 622), which is a partial halo for displaying an animation when the button subassembly 1002 is being pressed. In addition, the button subassembly 1002 is waterproof and sealed to prevent water from entering the interior of the device through the button subassembly 1002 or around the button subassembly. The button subassembly 1002 can include a button cap 1004, a first reflector 1006, a button foam 1008, a button flange 1010, a light guide 1012, a resilient button web 1014, a dome 1016, a second reflector 1018, and a button PCB (e.g., a button board 1020). One or more fasteners (e.g., fastener 1022) can be used to assemble the components of the button subassembly 1002 together. Pressing the button cap 1004 on the button subassembly 1002 completes the circuit on the button board 1020, thereby enabling the presence of a person to be detected.
[0098] The doorbell 226 also includes a speaker subassembly 1024 and one or more antennas 1026, which are assembled near each other and near the button subassembly 1002. The doorbell 226 includes a battery 1028, which can be housed in a battery frame 1030. A heat sink 1032 (e.g., graphite) can be wrapped around the battery 1028 to evenly distribute heat to the battery 1028 and maintain the temperature gradient of the battery 1028 within a desired level when the doorbell 226 is exposed to a cold environment (e.g., sub-zero temperatures). The heat sink 1032 is also configured to equalize the heat generated by the thermal resistor (e.g., Fig.11 Heating occurs when a resistor 1104 in the doorbell 226 is activated or when an external load from the sun (e.g., a solar load) applies heat to one side of the doorbell 226.
[0099] At the camera side end 608, the doorbell 226 may include a PCB 1034, which may be a subassembly for an IR sensor (passive infrared sensor), an IR LED, and / or an audio sensor (e.g., a microphone). A pressure sensitive adhesive (PSA) 1036 may be disposed between the PCB 1034 and the front housing component 802. In addition, a grid 1038 for an audio sensor (e.g., a microphone) may be disposed adjacent to the audio sensor. In addition, an IR flexible printed circuit (FPC) 1040 may connect the PCB 1034 to the camera module 442. The camera module 442 includes a camera subassembly 1042 and a PCB (e.g., a camera board 1044). The camera subassembly 1042 is aligned with the IR cover 614. In various aspects, one or more thermal interface materials (TIMs) 1046 may be disposed adjacent to the camera board 1044 to transfer heat generated by one or more integrated circuit components (including an image sensor) on the camera board 1044. Fasteners 1048 may be used to secure the camera board 1044 to the camera subassembly 1042 and / or the front housing component.
[0100] The main FPC 1050 can be used to connect the camera board 1044 to the main logic board (MLB) subassembly 1052 of the doorbell 226. The MLB subassembly 1052 is positioned toward the rear of the product assembly to avoid coupling of heat generated by the MLB subassembly 1052 with heat loads from external sources (e.g., solar loads from the sun). A heat sink 1054 is disposed adjacent to the MLB subassembly 1052 and the camera board 1044 to passively distribute heat away from the MLB subassembly 1052 and the camera board 1044 and transfer the heat toward the housing, including the rear housing component 804. In addition, the heat sink 1054 serves as a ground plane for multiple electrical components within the doorbell 226.
[0101] The heat sink 1054 includes a plurality of sections (e.g., a first section 1054-1, a second section 1054-2). The first section 1054-1 and the second section 1054-2 are both nested in the rear housing component 804. In various aspects, the first section 1054-1 is disposed adjacent to the MLB subassembly 1052 and is configured to absorb and distribute heat from the MLB subassembly 1052. The first section 1054-1 transfers the heat generated by the MLB subassembly 1052 to the lower portion of the housing, including the button side end 610. The first section 1054-1 is also coupled to the antenna 1026 to electrically ground the antenna 1026. The second section 1054-2 is disposed adjacent to the camera subassembly 1042 and is configured to absorb and distribute heat from the camera subassembly 1042. Specifically, the image sensor (e.g., image sensor 408) is cooled through the back side of the camera board 1044 with TIM 1046 (e.g., thermally conductive gel) and graphite, where the graphite is placed within an electromagnetic interference (EMI) shield to spread the heat before transferring it to a larger camera heat sink (e.g., second section 1054-2). Thus, the heat sink 1054 enables the amount of heat sink necessary for the camera subassembly 1042 to be separated from the amount of heat sink necessary for the MLB subassembly 1052. Dividing the heat sink 1054 into separate sections for different heat generating subassemblies significantly reduces the temperature compared to conventional doorbell devices that use a single heat sink for both the MLB and camera modules, thereby enhancing passive thermal control.
[0102] In some implementations, the two portions of the heat sink 1054 form a substantially oblong shape (in the xy plane). The first segment 1054-1 is significantly longer along the y-axis (at least 2 times longer, e.g., 2, 2.5, 3, 3.5, 4 times longer) than the second segment 1054-2. In addition, the first segment 1054-1 includes a base surface and sidewalls extending from the base surface in the z-axis direction (e.g., toward the front of the doorbell 226). In some aspects, the base surface can be substantially planar. The sidewalls of the first segment 1054-1 help transfer heat generated by the MLB subassembly 1052 toward the lateral sides of the housing (e.g., the left and right lateral sides relative to the front exterior surface 612 of the front housing component 802). During cold ambient temperatures, the sidewalls of the first segment 1054-1 help transfer heat from the heat sink components on the MLB subassembly 1052 to the internal air of the assembly to warm up the battery 1028 (with respect to Fig.11 Further details of warming battery 1028 are described).
[0103] A gasket 1056 (e.g., an O-ring) can be disposed between the rear housing component 804 and the front housing component 802 to form a seal and prevent water ingress along the seam between the housing components 802 and 804. The doorbell 226 can also include a label plate 1058 for adding and / or exchanging one or more labels. An electrical connector 1060 (e.g., wiring, a dongle) is used to connect the doorbell 226 to line power. In order to mount the doorbell 226 to a surface (e.g., a wall), a wall plate 1062 and / or a wedge 1064 can be used. The wall plate 1062 and the wedge 1064 can be fixed to the surface (e.g., a wall). The wall plate 1062 can include any suitable rigid material, including a metal sheet (e.g., made of stainless steel). In some aspects, a gasket is used between the wall plate 1062 and the wedge 1064 to help prevent the wall plate 1062 from bending or getting stuck during assembly to the wedge 1064. The wedge 1064 is configured with non-parallel front and rear surfaces that provide an angle relative to the wall. Thus, by securing the wedge 1064 to the wall and securing the doorbell 226 (including the wall plate 1062) to the wedge 1064, the doorbell 226 can be tilted relative to the wall. In this way, the wedge can provide a lateral (left and right) tilt angle or a downward (toward the ground) tilt angle to enable the camera of the doorbell (e.g., camera subassembly 1042) to tilt downward along the user's front doorway path (e.g., porch, front stairs). In some implementations, the downward or lateral tilt angle can be in the range of 10 degrees to 30 degrees (e.g., 20 degrees) relative to the wall.
[0104] The doorbell 226 includes one or more mounting studs 904 that are attached to the rear housing component 804 and are configured to hook onto the wall plate 1062 to secure the doorbell 226 to the surface to which the wall plate 1062 is secured. Specifically, the mounting studs 904 can be inserted into the wall plate 1062 through the openings 1066 (e.g., holes) and then slidably moved in the direction of the plane defined by the front surface of the wall plate 1062. This positioning and movement causes a portion of the head of the mounting stud 904 to be tucked behind the wall plate 1062, so that a portion of the wall plate 1062 is located between the head of the mounting stud 904 and the rear housing component 804. Therefore, the mounting studs 904 assembled to the wall plate 1062 in this manner prevent the doorbell 226 from moving relative to the wall plate 1062 (and the surface to which the wall plate 1062 is secured) along the z-axis (e.g., a direction perpendicular to the surface of the wall plate 1062). After the doorbell 226 is assembled to the wall plate 1062, the doorbell 226 can be further secured to the wall plate 1062 using a locking fastener 1068. The locking fastener 1068 can be inserted and tightened into place using a hexagonal wrench 1070 (e.g., an Allen wrench) or other suitable tool.
[0105] Fig.11 Shows Fig.10 1000, which shows the heat sink 1054, the MLB subassembly 1052, and the back side of the battery subassembly 1102. The battery subassembly 1102 includes a battery 1028 housed in a battery frame 1030. When assembled, the doorbell 226 includes an air gap ( Fig.11 ), where the air gap is specifically set to prevent the solar load from affecting the battery 1028, by, for example, effectively isolating the battery 1028 from the external load. This air gap also provides space for the battery 1028 to expand, which may occur as the battery 1028 ages.
[0106] In some implementations, the battery 1028 may also be wrapped in a heat sink 1032 (e.g., graphite). The battery 1028 is used when a ringing event occurs. For example, when the button is pressed, the circuit is actually closed and power is routed to the buzzer (a separate device electrically connected to the doorbell 226). Therefore, when the circuit is closed, the doorbell 226 does not receive line power for a predefined duration. Instead, the doorbell 226 runs on battery power for a predefined duration (e.g., 10 seconds) while the bell is ringing. Therefore, during cold temperatures (e.g., sub-zero temperatures), the battery 1028 (without a heating mechanism) has a high resistance and may not be able to support the doorbell 226 when the bell is ringing.
[0107] In general, the battery 1028 has an operating temperature range for optimal performance. A battery temperature sensor (e.g., a thermistor) can be implemented on the battery subassembly 1102 to monitor the battery temperature. At high temperatures, the battery may experience degradation due to excessive battery chemistry. At low temperatures (e.g., sub-zero temperatures), conventional batteries perform poorly due to the slow chemical reactions of the battery chemistry caused by the cold. Different batteries may have different operating temperature ranges. For example, the low temperature boundary of the operating temperature range of some batteries is 10°C (e.g., a range from 10°C to 80°C). The low temperature boundary of the operating temperature range of some batteries is 5°C (e.g., a range from 5°C to 85°C). Therefore, an ambient temperature of, for example, -20°C with a wind speed of about 1.5 m / s can cause the temperature of the battery 1028 to drop below the low temperature boundary of the operating temperature range, resulting in the battery being substantially inoperable. However, under such environmental conditions, one or more heating mechanisms can be used to heat the battery 1028. In one example, a heat sink 1032 may be wrapped around the battery 1028 to distribute the heat generated by the heating mechanism in a manner that maintains the gradient across the battery 1028 within a certain level (e.g., less than 5° C.) However, at some sub-zero ambient temperatures, many conventional battery heaters (e.g., flexible circuit heaters) may not be sufficient to maintain the battery temperature at or above the low temperature boundary.
[0108] In various aspects, one or more heating mechanisms may include a resistor 1104 disposed on a side of the MLB subassembly 1052 that interfaces with the heat sink 1054. The illustrated example shows six (6) resistors 1104 on the MLB subassembly 1052. However, any suitable number of resistors 1104 may be disposed on the MLB subassembly 1052 at any suitable location on the MLB subassembly 1052. In one example, the resistor 1104 is disposed toward one end of the MLB subassembly 1052. In the illustrated example, the resistor 1104 is disposed along the longitudinal axis 1106 of the MLB subassembly 1052 at an area approximately one-quarter of the length of the MLB subassembly 1052. The resistor 1104 is a plate resistor heater. In various aspects, the MLB subassembly 1104 includes a controller configured to control current flowing to the resistor 1104 based on a battery temperature. In one example, a battery sensor provides a detected battery temperature to the controller to enable the controller to determine whether the battery 1028 is within its operating temperature range. In some implementations, a controller on the MLB subassembly 1104 causes current to be provided to the resistor 1104 to overdrive the resistor 1104 and dissipate heat from the resistor 1104. Any appropriate amount of current or power may be used to overdrive the resistor 1104. In one example, power in the range of 3 watts (W) to 5 W (including 4 W) is driven into the resistor 1104 to dissipate heat from the resistor 1104. During a ringing event (e.g., when a button is pressed), power may be provided by the battery 1028. During low temperatures (e.g., sub-zero ambient temperatures), the resistor 1104 may be overdriven in this manner. In one example, below a low temperature threshold (e.g., 10° C., 5° C.), the resistor 1104 remains activated or turned on to maintain the battery 1028 at the minimum temperature required for the battery 1028 to discharge to achieve a ringing event.
[0109] When assembled, the resistor 1104 is thermally connected to the heat sink 1054 via a thermal interface material 1108 (e.g., thermally conductive gel) to provide heat to indirectly heat the battery 1028. For example, the resistor 1104 provides heat that is transferred to the heat sink 1054. The heat sink 1054 then transfers the heat to the interior air of the doorbell 226, thereby warming the battery 1028. In addition, the heat sink 1032 (e.g., graphite) distributes the heat from the interior air across multiple surfaces of the battery 1028 to maintain the gradient across the battery 1028 within a desired level. Thus, using the resistor 1104 described herein allows the battery 1028 to be heated to within its operating temperature range during cold ambient temperatures in a manner that maintains the temperature of the battery 1028 within its operating temperature range.
[0110] Fig.12 Shown along Figure 7 The line AA in Figure 7 Cross-sectional view 1200 of doorbell 226. Fig.13 Portion 1202 of cross-sectional view 1200 is shown in more detail, illustrating an example stacking of button subassembly 1002 at button-side end 610 of doorbell 226. Portion 1204 is shown in more detail in FIGS.
[0111] The speaker subassembly 1024 may cause friction and hum when producing audio output at certain frequencies. To reduce or prevent friction and hum, an elastic material (e.g., rubber, foam) may be provided between the battery frame 1030 and the front housing component 802. In the example shown, a strip or block 1206 of elastic material is arranged along the x-axis and separates the front housing component 802 from the battery frame 1030. In some aspects, the block 1206 provides a seal between the front housing component 802 and the battery frame 1030. In addition, the block 1206 divides the internal air chamber of the doorbell 226 to protect the friction and hum risk area from the resonant frequency of the speaker subassembly 1024, which uses the rest of the doorbell 226 as its rear volume.
[0112] Fig.13 Shows Fig.12 1200 in cross-sectional view, which includes an example stack-up of the button subassembly 1002. The button subassembly 1002 is constructed and integrated into the doorbell 226 in a manner that: (i) enables the button cap 1004 to be pressed anywhere on its outer surface to activate the electrical components behind it, (ii) enables the button subassembly 1002 to function as a light guide, and (iii) meets regulatory water resistance standards (e.g., at least the Water Ingress Protection (IPX) standard, including an IPX5 rating).
[0113] In the example shown, a dome 1016 (e.g., a snap dome) is disposed on the button plate 1020 above the electrical pattern, and when the dome 1016 is forced to contact the electrical pattern, the dome 1016 completes the electrical pattern. Completing the electrical pattern triggers a ringing event. In some implementations, the elastic button web 1014 includes a silicone rubber sheet that can be folded to apply force to the head of the dome 1016, so that the dome 1016 contacts the electrical pattern and completes the circuit. The elastic button web 1014 can include any suitable elastic material, including plastic, foam, etc. Above the elastic button web 1014 is a light guide 1012. The light guide 1012 has a specific angle geometry to guide the light emitted by the LED on the button plate 1020 to the side of the button cap 1004. For example, the LED generally provides light in the direction of the z-axis, and the light guide 1012 guides the light in the direction of the xy plane. The light passes through the light guide 1012 and enters the button flange 1010 , which directs the light toward the edge of the button cap 1004 .
[0114] The button cap 1004 forms a depressible button on the front outer surface 612 of the housing. The button cap 1004 is a multi-shot molded material that includes a first shot and a second shot (e.g., a first shot 1004-1 and a second shot 1004-2) of an injection molded material. The first shot 1004-1 forms the center of the button cap 1004 and is substantially opaque to at least visible light. The second shot 1004-2 forms the edge of the button cap 1004 and is substantially transparent to visible light so that light from the LED can be emitted from the front of the doorbell 226. Specifically, the second shot 1004-2 of the button cap 1004 scatters light, and the light is emitted from the second shot 1004-2 generally in the z-axis direction (e.g., from the front of the doorbell 226). In some implementations, the second shot 1004-2 of the button cap 1004 evenly distributes the scattered light around the button cap 1004.
[0115] Due to a mix of the types of materials used and the geometry of the light guide 1012 itself, the button subassembly 1002 prevents hot spots or dark spots from occurring in the light guide 1012, thereby diffusing the light.
[0116] Since the button subassembly 1002 acts as a depressible mechanical button, the button cap 1004 can move relative to the front housing component 802, thereby creating an area (around the button cap 1004) that is prone to water ingress. The path of water ingress is indicated by arrow 1300. For example, water can enter the device from around the edge of the button cap 1004 and pass through the space around the button flange 1010 to reach the portion of the button plate 1020. However, seals 1302 and 1304 can prevent water from further ingress. The seal 1302 is disposed between the front housing component 802 and the button plate 1020. In some implementations, the seal 1302 can be a PSA. The seal 1304 is disposed between the button plate 1020 and the elastic button web 1014 to prevent water from reaching and damaging the circuit on the button plate 1020. Having internal seals (eg, seals 1302 and 1304) enables mechanical movement of button cap 1004 relative to front housing component 802 and also allows some water ingress but prevents any areas where water ingress could cause damage.
[0117] In addition, the button plate 1020 has a certain thickness, which provides strength against high pressing forces applied to the button cap 1004. Many conventional video doorbells include a battery behind the button plate 1020, but the doorbell 226 described herein does not include a battery, which provides additional space within the device to increase the thickness of the button plate 1020.
[0118] Fig.14 Shown along Figure 7 The line CC in Figure 71400 of a doorbell 226 in FIG. 1400. Specifically, the cross-sectional view 1400 is taken through the button subassembly 1002 along the x-axis. As shown, the button subassembly 1002 is disposed toward the front of the device. Below the button plate 1020 is a layer of speaker foam 1402 that separates the button plate 1020 from the speaker subassembly 1024. The speaker foam 1402 is implemented to reduce friction and hum caused by movement of the speaker subassembly 1024 relative to the button plate 1020 along the z-axis. The speaker subassembly 1024 is fastened to the heat sink 1054 via one or more fasteners 1022. The heat sink 1054, and in particular the first section 1054-1 of the heat sink 1054, is separated from the speaker subassembly 1024 by a gap, which enables the speaker subassembly 1024 to move in the direction of the z-axis relative to the first section 1054 of the heat sink 1054. The heat sink 1054 is adjacent to the rear housing component 804 to transfer heat to the rear housing component 804, thereby passively cooling the device. The front housing component 802 can be connected to the rear housing component 804 via any suitable connection mechanism, which includes protrusions and recesses that enable the housing components to snap together. Attached to the rear housing component 804 is a mounting stud 904, which includes a shaft 1404 connected to a head 1406. The head 1406 is wider relative to the shaft 1404 because the diameter of the head 1406 is greater than the diameter of the shaft 1404. Therefore, the head 1406 extends outward from the shaft 1404 in the xy plane. The shaft creates a gap 1408 between the rear housing component 804 and the head 1406 of the mounting stud 904. When the doorbell 226 is assembled to the wall plate 1062, portions of the wall plate 1062 are slidably moved (in the direction of the y-axis) into the gap 1408 to limit or prevent movement of the doorbell 226 in the direction of the z-axis relative to the wall plate 1062 (and relative to the surface to which the wall plate 1062 is fixed). Due to the shape and orientation of the mounting studs 904 and the wall plate 1062 when assembled together, the doorbell 226 is fixed in the direction of the x-axis and both z-axis, which reduces or prevents the doorbell 226 from swaying or rocking relative to the wall plate 1062. Fig.15 Describe further details.
[0119] Fig.15 Shown along Figure 7 A perspective cross-sectional view 1500 of the button side end 610 of the doorbell 226 taken along line AA in FIG. 1 and an enlarged view 1502 of a portion of the cross-sectional view 1500 with the mounting stud 904. Fig.15As shown, the mounting stud 904 is fastened to a fastener 1504 (e.g., a screw, a bolt) that is located within the housing and extends through the heat sink 1054 and the rear housing component 804. For example, the mounting stud 904 can have a threaded inner surface to which the fastener 1504 is screwed. In addition, a seal 1506 is disposed around the shaft 1404 of the mounting stud 904 (e.g., surrounding the shaft) to provide a seal to prevent water from entering the interior of the doorbell 226 through the space between the rear housing component 804 and the shaft 1404 of the mounting stud 904.
[0120] In addition, a non-conductive separator 1508 (e.g., a washer, a shoulder washer) is adjacent to the fastener 1504 to isolate water and electricity. The fastener 1504 is inserted into the separator 1508 through the aperture to separate and insulate the fastener 1504 from the heat sink 1054. Since the mounting stud 904, the fastener 1504, and the heat sink 1054 are conductive metal parts, there is a risk that an electrical short circuit applied to the mounting stud 904 may be conducted through the mounting stud 904 to the fastener 1504, through the fastener 1504 to the heat sink 1054, and through the heat sink 1054 to the main board (e.g., MLB subassembly 1052) or other circuits. In order to prevent these components from establishing a conductive path in this manner, the separator 1508 is provided between the fastener 1504 and the heat sink 1054. Separator 1508 is a non-conductive material (eg, plastic, rubber) to prevent grounding or shorting between mounting stud 904 and heat sink 1054 via fastener 1504 .
[0121] Fig.16 Shown along Figure 7 The line CC in Figure 716. Cross-sectional view 1600 of an example doorbell 226 in FIG. Cross-sectional view 1600 shows the stacking of doorbell 226 at camera side end 608. Mounting studs 904 are at the rear of doorbell 226, which are connected to rear housing member 804. Heat sink 1054 is seated or nested within rear housing member 804. Rear housing member 804 is removably attached (e.g., snapped) to front housing member 802 at multiple locations around the perimeter of rear housing member 804. In various aspects, the outer surface of rear housing member 804 is attached to the inner surface of front housing member 802. In this way, in a front elevation view of doorbell 226, rear housing member 804 is visually hidden by front housing member 802. Stacked above heat sink 1054 at camera side end 608 is camera module 442, which includes camera board 1044, image sensor 408, camera lens 616, and retainer 618, among other components. Adjacent to the holder 618 is an IR cover 614 that surrounds the holder 618 and the camera lens 616 in the xy plane and covers the PCB 1034 that may include an IR LED.
[0122] Fig.17A , Fig. 17B and Fig. 17C A locking mechanism is shown for securing the doorbell 226 to the wall plate 1062. Fig.17A Initially, the doorbell 226 is placed adjacent to the wall plate 1062 such that the mounting studs 904 are inserted into the wall plate 1062 through the openings 1066 (e.g., along the z-axis). The wall plate 1062 includes a front surface configured to abut the rear exterior surface of the rear housing component 804. The wall plate 1062 also has a locking tab 1700 that extends outwardly from the front surface and is configured to be inserted into the recessed volume 906 of the rear housing component 804. The doorbell 226 is then slidably moved downward (in the -y direction) such that the wall plate 1062 slides upward relative to the doorbell 226 (in a direction toward the top of the doorbell 226, e.g., toward the y-axis of the locking fastener 1068).
[0123] continue Fig. 17B, the locking tab 1700 of the wall plate 1062 is now disposed adjacent to one side of the recessed volume 906, which includes the aperture 1704 into which the locking fastener 1068 is inserted. Additionally, the mounting stud 904 overlaps a portion of the wall plate. For example, the wall plate 1062 includes a portion 1706 that is now disposed between the head 1406 of the mounting stud 904 and the rear housing component 804, thereby preventing the doorbell 226 from moving in the direction of the z-axis relative to the wall plate 1062. In this manner, the head 1406 of the mounting stud 904 is disposed between the wall plate 1062 and the surface to which the wall plate 1062 is secured. Due to the shape of the head 1406 of the mounting stud 904 and the shape of the opening 1066 in the wall plate 1062 after the mounting stud 904 is slidably moved into position, the doorbell 226 is also prevented from moving in the direction of the x-axis. For example, when assembled to the wall plate 1062, the head 1406 of the mounting stud 904 overlaps the wall plate 1062 in at least the x-dimension. In some implementations, when assembled to the wall plate 1062, the mounting stud 904 overlaps the wall plate 1062 in both the x-dimension and the y-dimension. The locking fastener 1068 is then inserted into the locking tab 1700 of the wall plate 1062 through the aperture 1708.
[0124] continue Fig. 17C , the locking fastener 1068 is fastened (e.g., threaded) to the locking tab 1700 of the wall plate 1062 to fix the rear housing component 804 to the wall plate 1062 in the direction of the y-axis (e.g., the horizontal axis 604). This fastening prevents the doorbell 226 from moving relative to the wall plate 1062 along the y-axis.
[0125] These and other capabilities and configurations, as well as the manner in which the entities of FIGS. 1 and 2 act and interact, are described in more detail below. These entities may also be further divided, combined, etc. The environment 100 of FIG. 1 and FIGS. 2 to 3 may be further divided, combined, etc. Fig. 17C The detailed diagrams illustrate some of the many possible environments, devices, and methods in which the described techniques can be employed, either alone or in combination with each other.
[0126] Some examples are described below:
[0127] A video doorbell includes: a housing, the housing having a front outer surface and an opposite rear outer surface, the height of the housing along the y-axis being greater than the width along the x-axis and the depth along the z-axis, the front outer surface being perpendicular to the z-axis, the front outer surface having a first opposite end and a second opposite end along the y-axis; a camera module, the camera module being disposed at the first end of the housing, the camera module being configured to operate an image sensor and associated circuitry to capture video data, the camera module having a camera lens extending outwardly from the front outer surface of the housing and exposed to the environment surrounding the video doorbell; and a printed circuit board, the printed circuit board A circuit board is disposed within the housing and has a circuit configured to continuously record the video data; a button subassembly, which is disposed at the second end of the housing and is configured to be pressed by a person to initiate a ringing event within a predefined duration; a battery, which is configured to provide power to the circuit during the ringing event; and a heat sink, which has separate first and second sections, the first section of the heat sink being disposed adjacent to the printed circuit board, the second section of the heat sink being disposed adjacent to the camera module, and the first section being positioned adjacent to the second section in the direction of the y-axis.
[0128] The video doorbell may further include an infrared cover disposed at the first end of the housing, the infrared cover being configured to be transparent to infrared light, and the camera lens extending through an opening in the infrared cover.
[0129] The camera module may have a lens holder disposed between the camera lens and the infrared cover.
[0130] The first section of the heat sink may be at least twice longer than the second section along the y-axis.
[0131] The first section of the heat sink may include a base surface and sidewalls extending outwardly from the base surface along the z-axis, the sidewalls configured to transfer heat toward lateral sides of the housing separated by a width of the housing.
[0132] The button subassembly may include: a button plate having an electrical pattern for initiating a ringing event; a dome configured to complete a circuit when forced to contact the electrical pattern; a resilient button that can be folded to apply force to the dome so that the dome contacts the electrical pattern and completes the circuit; a light guide disposed adjacent to the resilient button; and a button cap forming a depressible button on the front outer surface of the housing.
[0133] The video doorbell may further include: a first seal, which is arranged between the button plate and the front shell component of the shell; and a second seal, which is arranged between the button plate and the elastic button, wherein the first seal and the second seal prevent water ingress in the shell between the shell and the button cap of the button subassembly from reaching the electrical pattern on the button plate.
[0134] The video doorbell may further include one or more board resistor heaters disposed on the printed circuit board and configured to dissipate heat to a heat sink to indirectly warm the battery based on the heat sink transferring heat to the battery via the internal air of the video doorbell.
[0135] The board resistor heater may be thermally connected to a heat sink.
[0136] The board resistor heater may be configured to generate heat to maintain the temperature of the battery within an operating temperature range.
[0137] The video doorbell may further include a heat sink disposed adjacent to the battery and configured to distribute heat from the internal air over multiple surfaces of the battery.
[0138] The video doorbell may further include one or more mounting studs, which are arranged on the rear outer surface of the shell, wherein: a corresponding mounting stud among the one or more mounting studs is fixed to a fastener arranged in the shell; and the corresponding mounting stud includes: a shaft extending outward from the rear outer surface of the shell; and a head having a diameter greater than the diameter of the shaft.
[0139] The video doorbell may further include a wall plate configured to be secured to a surface and to support the housing, wherein corresponding mounting studs are configured to be inserted into the wall plate through the opening and overlap a portion of the wall plate to secure the housing to the wall plate.
[0140] The overlap between the mounting studs and portions of the wall plate prevents movement of the housing along the z-axis as well as along the x-axis.
[0141] The wall panel may include a front surface and a locking plate extending outward from the front surface; the rear outer surface of the shell may define a recessed volume, which is configured to accommodate the locking plate of the wall panel; and the shell may be fastened to the wall panel by a fastener, which is inserted into the shell through the orifice and fixed to the locking plate of the wall panel to prevent the shell from moving relative to the wall panel along the y-axis.
[0142] in conclusion
[0143] Although aspects of the video doorbell have been described in language specific to features and / or methods, the subject matter of the appended claims is not necessarily limited to the specific features or methods described. Rather, the specific features and methods are disclosed as example implementations of the technology for the video doorbell, and other equivalent features and methods are intended to fall within the scope of the appended claims. In addition, various different aspects are described, and it should be understood that each described aspect may be implemented independently or in combination with one or more other described aspects.
Claims
1. A video doorbell, comprising: a housing having a front outer surface and an opposite rear outer surface, the housing having a height along the y-axis greater than the width along the x-axis and the depth along the z-axis, the front outer surface being perpendicular to the z-axis, the front outer surface having first and second opposite ends along the y-axis; a camera module disposed at the first end of the housing, the camera module configured to operate an image sensor and associated circuitry to capture video data; a printed circuit board disposed within the housing and having circuitry configured to continuously record the video data; a button subassembly disposed at the second end of the housing and configured to be pressed by a person to initiate a ringing event; as well as A heat sink having a separate first section and a second section, wherein the first section of the heat sink is disposed adjacent to the printed circuit board, the second section of the heat sink is disposed adjacent to the camera module, and the first section is positioned adjacent to the second section in the direction of the y-axis.
2. The video doorbell of claim 1, further comprising an infrared cover disposed at the first end of the housing, the infrared cover being configured to be transparent to infrared light, and the camera lens extending through an opening in the infrared cover.
3. The video doorbell as claimed in claim 2, wherein the camera module has a lens holder disposed between the camera lens and the infrared cover.
4. The video doorbell of any one of the preceding claims, wherein the first section of the heat sink is at least twice longer than the second section along the y-axis.
5. A video doorbell as described in any of the preceding claims, wherein the first section of the heat sink includes a base surface and side walls extending outward from the base surface along the z-axis, and the side walls are configured to transfer heat toward lateral sides of the housing separated by the width of the housing.
6. The video doorbell according to any one of the preceding claims, wherein the button subassembly comprises: a button pad having an electrical pattern for initiating the ringing event; a dome configured to complete an electrical circuit when forced into contact with the electrical pattern; a resilient button capable of folding to apply a force to the dome so that the dome contacts the electrical pattern and completes the circuit; a light guide disposed adjacent to the elastic button; as well as A button cap forms a depressible button on the front outer surface of the housing.
7. The video doorbell as claimed in claim 6, further comprising: a first seal disposed between the button plate and a front housing component of the housing; as well as A second seal is provided between the button plate and the elastic button, wherein the first seal and the second seal prevent water ingress in the housing between the housing and a button cap of the button subassembly from reaching the electrical pattern on the button plate.
8. The video doorbell according to any one of the preceding claims, further comprising: a battery frame configured to receive a battery for providing power to the circuit during the ringing event; as well as One or more board resistor heaters are disposed on the printed circuit board, and the one or more board resistor heaters are configured to dissipate heat to the heat sink to indirectly warm the battery based on the heat sink transferring the heat to the battery via the internal air of the video doorbell.
9. The video doorbell of claim 8, wherein the board resistor heater is thermally connected to the heat sink.
10. The video doorbell according to claim 8 or claim 9, further comprising: a temperature sensor configured to detect a battery temperature of the battery; as well as A controller is configured to control current flowing to the board resistor heater based on the battery temperature, wherein the board resistor heater is configured to generate heat to maintain the temperature of the battery within an operating temperature range.
11. The video doorbell of any one of claims 8 to 10, further comprising a heat sink disposed adjacent to the battery and configured to distribute the heat from the internal air over multiple surfaces of the battery.
12. The video doorbell of any of the preceding claims, further comprising one or more mounting studs disposed on a rear exterior surface of the housing, wherein: a respective one of the one or more mounting studs being secured to a fastener disposed within the housing; and The corresponding mounting studs include: a shaft extending outwardly from the rear outer surface of the housing; as well as A head portion has a diameter greater than a diameter of the shaft.
13. The video doorbell of claim 12, further comprising a wall plate configured to be secured to a surface and to support the housing, wherein the corresponding mounting studs are configured to be inserted into the wall plate through the opening and overlap a portion of the wall plate to secure the housing to the wall plate.
14. The video doorbell of claim 13, wherein the overlap between the mounting studs and the portion of the wall plate prevents movement of the housing along the z-axis and along the x-axis.
15. The video doorbell according to any one of claims 12 to 14, wherein: The wall plate includes a front surface and a locking tab extending outwardly from the front surface; the rear exterior surface of the housing defining a recessed volume configured to receive the locking tab of the wall plate; and The housing is configured to be fastened to the wall plate by a fastener that is inserted into the housing through an aperture and secured to the locking tab of the wall plate to prevent movement of the housing relative to the wall plate along the y-axis.
