Electronic device with adjustable illumination

Information

  • Patent Grant
  • 11596039
  • Patent Number
    11,596,039
  • Date Filed
    Tuesday, December 28, 2021
    2 years ago
  • Date Issued
    Tuesday, February 28, 2023
    a year ago
Abstract
This application discloses an electronic device (e.g., a camera) that a plurality of light sources and a light source driver. The light sources are configurable to a plurality of light source subsets to illuminate a field of view. At least two of the light source subsets include distinct light source members and are configured to illuminate different regions of the field of view. The light source driver is coupled to the plurality of light sources and configured to drive the plurality of light source subsets. In some embodiments, the electronic device includes or is coupled to a camera module configured to capture visual data of the field of view, and the plurality of light sources is configured to provide illumination for the camera module.
Description
TECHNICAL FIELD

This application relates generally to semiconductor devices and circuits, including but not limited to methods and systems for driving light emitting devices for illumination at two or more operational modes associated with different device configurations.


BACKGROUND

Light emitting diodes (LEDs) are applied to provide a wide variety of illumination solutions, e.g., environmental lighting and backlight in mobile devices, because they offer advantages on energy consumption, lifetime, physical robustness, size and switching rate. The LEDs are electrically coupled to a certain configuration (e.g., a string or an array) to enable a desirable illumination level. Oftentimes, the LEDs are driven by an enhanced LED voltage that is raised from a regular power supply voltage by a boost type voltage regulator. The enhanced LED voltage is specifically determined according to the configuration and operation voltages of the LEDs. This boost type voltage regulator is implemented as a switch mode power supply (SMPS). When its duty cycle varies, the SMPS allows the enhanced LED voltage to be modulated within a voltage range thereof, thereby enabling the dimming effect on illumination delivered by the LEDs.


However, the boost type voltage regulator merely allows a limited voltage variation for the enhanced LED voltage, and cannot be used to drive the LEDs and provide a desirable illumination level when the coupling configuration of the LEDs varies (e.g., the number of the LEDs coupled within a string or array increases or decreases). For example, when a subset of LEDs are decoupled from a LED string, the enhanced LED voltage has to be reduced by one or more diode junction voltages, which could not be provided by the small voltage variation of the enhanced LED voltage. In this situation, the voltage regulator would fail to drive the LEDs having the new coupling configuration, because the enhanced LED voltage would overdrive and damage the LEDs. It would be beneficial to have a more flexible and tolerant LED driver than the current practice.


SUMMARY

Accordingly, there is a need for driving a plurality of LEDs that has more than one coupling configuration in association with different operation modes (e.g., a boost mode and a bypass mode). Specifically, such LEDs are driven by a boost voltage converter that provides a drive voltage according to each of the more than one coupling configuration. This LED driving method optionally complements or replaces conventional methods of using a single drive voltage with a limited voltage variation to enable dimmable LED illumination by a specific LED coupling configuration.


In accordance with one aspect of this application, a LED illumination system operates in a boost mode and a bypass mode. The LED illumination system includes a plurality of LEDs, a plurality of bypass elements, a boost converter, a first current sink and a second current sink. The plurality of LEDs is coupled in series to form a LED string. Each bypass element is coupled in parallel with a respective group of one or more of the LEDs, and configured to bypass selectively the respective group of LEDs in the bypass mode. The boost converter is coupled to the plurality of LEDs, and configured to generate a drive voltage to drive the plurality of LEDs. The boost converter includes a boost controller that is configured to enable the boost mode in response to a boost enable signal. The first and second current sinks are coupled to the plurality of LEDs, and configured to provide two drive currents to drive the LEDs in the boost mode and the bypass mode, respectively. In the boost mode, the boost controller is electrically coupled to control the boost converter to drive the LED string by a boosted drive voltage. Alternatively, in the bypass mode, the boost controller is deactivated to allow the boost converter to drive a subset of the plurality of LEDs by a regular drive voltage that is substantially lower than the boosted drive voltage.


In accordance with another aspect of this application, a camera device operates in two or more modes. The camera device includes a camera portion and a LED illumination system that operates in a boost mode and a bypass mode that are associated with a first mode and a second mode of the two or more modes of the camera device, respectively. The LED illumination system further includes a plurality of LEDs, a plurality of bypass elements, and a boost converter. The plurality of LEDs is coupled in series to form a LED string. Each bypass element is coupled in parallel with a respective group of one or more of the LEDs, and configured to bypass selectively the respective group of LEDs in the bypass mode. The boost converter is coupled to the plurality of LEDs, and configured to generate a drive voltage to drive the plurality of LEDs. The boost converter includes a boost controller that is configured to enable the boost mode in response to a boost enable signal. In the boost mode, the boost controller is electrically coupled to control the boost converter to drive the LED string by a boosted drive voltage. Alternatively, in the bypass mode, the boost controller is deactivated to allow the boost converter to drive a subset of the plurality of LEDs by a regular drive voltage that is substantially lower than the boosted drive voltage.


In accordance with another aspect of this application, a method is applied to manufacture a LED illumination system that operates in a boost mode and a bypass mode. The method includes providing a plurality of LEDs that is coupled in series to form a LED string, and providing a plurality of bypass elements. The operation of providing a plurality of bypass elements further includes coupling each of the plurality of bypass elements in parallel with a respective group of one or more of the LEDs to bypass selectively the respective group of LEDs in the bypass mode. The method further includes coupling a boost converter to the plurality of LEDs, and the boost converter is configured to generate a drive voltage to drive the plurality of LEDs. The boost converter includes a boost controller that is configured to enable the boost mode in response to a boost enable signal. In the boost mode, the boost controller is electrically coupled to control the boost converter to drive the LED string by a boosted drive voltage. In the bypass mode, the boost controller is deactivated to allow the boost converter to drive a subset of the plurality of LEDs by a regular drive voltage that is substantially lower than the boosted drive voltage.





BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the various described implementations, reference should be made to the Description of Implementations below, in conjunction with the following drawings in which like reference numerals refer to corresponding parts throughout the figures.



FIG. 1 is a circuit diagram illustrating a LED illumination system that operates in a boost mode and a bypass mode in accordance with some implementations.



FIG. 2A is a block diagram illustrating a microcontroller unit (MCU) and its output interface in accordance with some implementations.



FIG. 2B is a temporal diagram of a plurality of boost-bypass control signals and a generated LED drive voltage associated with a LED illumination system in accordance with some implementations.



FIGS. 3A and 3B illustrate two examples of a top view of a camera module that includes a plurality of LEDs in accordance with some implementations, respectively.



FIGS. 3C and 3D illustrate two sets of exemplary LED illumination patterns associated with a depth imaging mode of the camera shown in FIG. 3A in accordance with some implementations, respectively.



FIG. 4 is a circuit diagram illustrating an exemplary bypass element for bypassing one or more LEDs within a LED string in accordance with some implementations.



FIG. 5 is a circuit diagram illustrating a current sink that is electrically coupled in a LED illumination system in accordance with some implementations.



FIG. 6 is a flow diagram illustrating a method of manufacturing a LED illumination system that operates in a boost mode and a bypass mode in accordance with some implementations.





Like reference numerals refer to corresponding parts throughout the several views of the drawings.


DESCRIPTION OF IMPLEMENTATIONS

A smart home environment is created at a venue by integrating a plurality of devices, including intelligent, multi-sensing, network-connected devices, seamlessly with each other in a local area network and/or with a central server or a cloud-computing system to provide a variety of useful smart home functions. In some implementations, the smart home environment includes one or more network-connected cameras that are configured to provide video monitoring and security in the smart home environment. In addition to video recording at the daytime, such a camera needs to operate at a night vision mode to detect any trespass or burglary activities that often happen at night when visible light illumination is unavailable. In some situations, the camera also operates at a depth imaging mode to develop a depth map related to an interior view of a room, and this depth imaging mode is preferably implemented at night when the activity level is relatively low in the room. Under some circumstances, given that visible light illumination is limited or unavailable at night, the camera therefore has to incorporate a series of infrared LEDs to illuminate the room when it operates under the night vision mode or the depth imaging mode. Such infrared LEDs are coupled differently according to the operation mode of the camera.


In accordance with various implementations of the application, a series of LEDs of an electronic device could be arranged according to different LED coupling configurations, when the electronic device operates under different modes (e.g., when a camera operates in the night vision mode and the depth imaging mode). In a specific example, eight or more infrared LEDs are coupled in series to form a LED string in a first operation mode, and only two of these eight or more infrared LEDs are coupled and involved (i.e., six of the LEDs are bypassed) in a second operation mode. When the operation voltage of each LED is assumed to be 1.5V and above, a corresponding drive voltage that drives the LEDs could vary between 12V and 4V when the electronic device operates at the two distinct operation modes. As explained below with reference to FIGS. 1-6, a LED illumination system is configured to accommodate the relatively large variation of the drive voltage caused by the variation of LED coupling configurations.


Specifically, in some implementations, a plurality of boost-bypass controls is determined according to an operation mode of an electronic device, and controls a LED illumination system to operate in one of a boost mode and a bypass mode. In the boost mode, a series of LEDs including a first number of LEDs are electrically coupled in series to form a LED string, and a boost controller is coupled to control a boost converter to drive the whole LED string by a boosted voltage. In the bypass mode, a subset of the series of LEDs is electrically coupled according to a different LED coupling configuration, and the other LEDs of the series of LEDs are bypassed. The subset of LEDs including a second number of LEDs, and the second number is substantially smaller than the first number. The boost controller is deactivated to allow the boost converter to drive the subset of LEDs by a regular drive voltage that is substantially lower than the boosted drive voltage. The boost-bypass controls are generated by a microcontroller unit (MCU), and thereby applied to control one or more of: bypassing of LEDs in the LED string, deactivating the boost controller, and selecting a current sink according to the operation mode.



FIG. 1 is a circuit diagram illustrating a LED illumination system 100 that operates in a boost mode and a bypass mode in accordance with some implementations. The LED illumination system 100 includes a plurality of LEDs (LED1-LED8), a plurality of bypass elements 102, a boost converter 104, a first current sink 108 and a second current sink 110. The boost converter 104 further includes a boost controller 106. The LED illumination system 100 further includes a plurality of boost-bypass control signals, e.g., BP1-BP8, BS and BP, which are synchronized to control the components 102-110 and enable the boost or bypass mode for the LED illumination system 100.


The plurality of LEDs is electrically coupled in series to form a LED string 120. Each of the plurality of bypass elements 102 is coupled in parallel with a respective group of one or more of the plurality of LEDs, and configured to bypass selectively the respective group of LEDs in the bypass mode. In the specific implementations as shown in FIG. 1, each of the plurality of LEDs is coupled in parallel with a respective bypass element. The respective bypass element 102 receives a LED bypass control signal, and is configured to selectively bypass the corresponding LED from the LED string 120 when the LED illumination system 100 operates in the bypass mode. In some implementations not shown in FIG. 1, one of the plurality of bypass elements is arranged in parallel with a series of two or more LEDs in the LED string 120, and selectively bypasses the series of two or more LEDs in the bypass mode. More details on the coupling configuration of the plurality of LEDs are explained below with reference to FIGS. 3A-3D. In some implementations, the plurality of LEDs is infrared LEDs.


The boost converter 104 is coupled to the plurality of LEDs, and configured to generate a drive voltage VDR for driving the plurality of LEDs. In some implementations, the boost converter 104 is implemented as a switch mode power supply. The boost converter 104 receives a power supply voltage VSUP and a pulse width control signal PWC, and generates a boosted drive voltage VBDR. The boost drive voltage VBDR is substantially higher than the power supply voltage VSUP, and varies within a fixed voltage range. The pulse width control signal PWC has a variable duty cycle, and determines the variation of the drive voltage VDR. Specifically, in some implementations, the boost converter 104 includes an inductor 112, a diode 114, a load capacitor 116, and a switching component 118. The pulse width control signal PWC is used to control the switching component 118 to enable charging and discharging of the load capacitor 116, and thereby renders the boosted and variable drive voltage VBDR.


The boost controller 106 of the boost converter 104 is configured to enable the boost mode in response to a boost enable signal BS of the plurality of boost-bypass control signals. In some implementations, the boost controller 106 is driven by the power supply voltage VSUP that drives the boost converter 104. In the boost mode, the boost enable signal BS is enabled, and the boost controller 106 is activated. The activated boost controller 106 thereby controls the boost converter 104 to drive the LED string 120 by the boosted drive voltage VBDR. For example, when the boost converter 104 is implemented as a switch mode power supply, the boost controller 106 generates the pulse width control signal PWC and varies its duty cycle for the purposes of controlling the boost converter 104 to generate a desirable drive voltage level.


Conversely, in the bypass mode, the boost enable signal BS is disabled, and the bypass enable signal BP is enabled. The boost controller 106 is deactivated to allow the boost converter 104 to drive a subset of the plurality of LEDs by a regular drive voltage VRDR that is substantially lower than the boosted drive voltage VBDR. In some implementations, in accordance with the deactivation of the boost controller 106, the pulse width control signal PWC has a null duty cycle, and the boost converter 104 generates a regular drive voltage VRDR substantially equal to the power supply voltage VSUP that drives the boost converter 104 or the entire LED illumination system 100.


The first current sink 108 and the second current sink 110 are coupled to the plurality of LEDs, and configured to provide two drive currents to drive the LEDs in the boost mode and the bypass mode, respectively. The first current sink 108 and the second current sink 110 are controlled by the boost enable signal BS and another bypass enable signal BP of the plurality of boost-bypass control signals. In some implementations, the first current sink 108 is part of the boost controller 106. In the boost mode, the first current sink is electrically coupled to the whole LED string 120, and enables a first drive current. Alternatively, in the bypass mode, the second current sink is electrically coupled to a subset of the plurality of LEDs, and enables a second drive current.


Optionally, the two drive currents provided by the first and second current sinks 108 and 110 are substantially equal. Optionally, the two drive currents are distinct. In an example, the first current sink 108 provides to the whole LED string 120 the first drive current that is substantially equal to 50 mA in the boost mode. The second current sink 110 provides to the subset of selected LEDs the second drive current that is substantially equal to 100 mA in the bypass mode. As such, the distinct drive current levels at the boost and bypass modes are associated with distinct LED coupling configurations and render distinct brightness levels for each coupled LED. When the LED illumination system 100 is applied in a camera, the boost and bypass modes could be associated with different camera operation modes, and the camera could achieve unique camera features based on the illumination configuration and brightness level associated with the boost or bypass mode of the LEDs.


In some implementations, the boost converter 104, the first current sink 108, and the second current sink 110 are integrated on an integrated circuit substrate. In some implementations, one or more of the boost converter 104, the first current sink 108, and the second current sink 110 are off-the-shelf components, and assembled on a printed circuit board substrate.


It is also noted that the LED illumination system 100 could also operate at an idle mode that is distinct from the boost mode and the bypass mode. In the idle mode, none of the plurality of LEDs is enabled to provide illumination. When the LED illumination system 100 is part of a camera, the idle mode is activated to disable infrared LED illumination during the daytime.



FIG. 2A is a block diagram illustrating a microcontroller unit (MCU) 200 and its output interface in accordance with some implementations. In some implementations, the MCU 200 is configured to generate the plurality of boost-bypass control signals in a synchronous manner for the purposes of configuring the LED illumination system 100 to operate in a boost mode or a bypass mode. Specifically, the MCU 200 is configured to generate the boost enable signal BS, and a plurality of LED bypass control signals BP1-BP8. The boost enable signal BS is applied to enable the boost controller 106 and activate the first current sink 108 in the boost mode. Each of the plurality of LED bypass controls is applied to control one of the plurality of bypass elements for bypassing the corresponding group of LEDs in the bypass mode. In some implementations, the MCU 200 is also configured to generate a bypass enable signal BP that enables the second current sink in the bypass mode. Optionally, the bypass enable signal BP is a complementary signal of the boost enable signal BS, and in some implementations, can be generated internally from the boost enable signal BS within the LED illumination system 100. Optionally, the bypass enable signal BP is enabled with a delay or an overlap with an active cycle of the bypass enable signal BS.


In some implementations, the first current sink 108 is controlled by the boost enable signal BS to enable and disable the first drive current in the boost and bypass modes, respectively. The first current sink 108 is thus enabled during the active cycles of the boost enable signal BS to provide the first drive current, and disabled from providing the first drive current during the inactive cycles of the boost enable signal BS. Alternatively, in some implementations, the first current sink 108 is controlled by both the boost enable signal BS and the bypass enable signal BP. The first current sink 108 is enabled by the boost enable signal BS to provide the first drive current, but disabled by the bypass enable signal BP from providing the first drive current. Similarly, in some implementations, the second current sink 110 is controlled by the bypass enable signal BP to enable and disable the second drive current in the bypass and boost modes, respectively. As such, the second current sink 110 is enabled during the active cycles of the bypass enable signal BP to provide the second drive current, and disabled from providing the second drive current during the inactive cycles of the bypass enable signal BP. In some implementations, the second current sink 110 is controlled by both the boost enable signal BS and the bypass enable signal BP. The second current sink 110 is enabled by the bypass enable signal BP to provide the second drive current, but disabled by the boost enable signal BS from providing the second drive current.



FIG. 2B is a temporal diagram of a plurality of boost-bypass control signals and a generated LED drive voltage associated with a LED illumination system 100 in accordance with some implementations. In some implementations, when the LED illumination system 100 transitions between the boost mode and the bypass mode, the MCU 200 introduces delay times among the plurality of boost-bypass control signals to avoid the LEDs or the current sinks from being overstressed. For example, when the LED illumination system 100 switches from the boost mode to the bypass mode, both the boost controller 106 and the first current sink 108 are deactivated, and the second current sink 110 is electrically coupled to the whole LED string 120. The MCU 200 does not enable the bypass of a subset of unselected LEDs to follow the enable signals BS and BP immediately. Rather, the MCU 200 introduces one or more delay times (e.g., T1 and T2) to delay the bypass of the unselected LEDs, such that the boost drive voltage VBDR does not drop on and overstress a subset of selected LEDs having a smaller number of LEDs than the whole LED string 120.


In some implementations, the one or more delay times (e.g., T1 and T2) are associated with a plurality of bypass factors, e.g., a boost control delay during which the boost controller 106 converts an input bypass enable signal to the pulse width control signal PWC for the purposes of controlling the boost converter 104. In an example, a delay time is substantially small, when the boost controller 106 introduces a substantially small or negligible boost control delay for converting the input bypass enable signal to the pulse width control signal PWC. Additionally, another example bypass factor that affects the delay times is a discharge period during which the boost converter 104 is gradually discharged for reducing the voltage level of the drive voltage at its output. A large load capacitor 116 contains more charges, and takes a longer time to discharge. As such, the delay times are associated with the length of the discharge period of the boost converter 104 which is further associated with the capacitance of its load capacitor 116.


In some implementations, the MCU 200 introduces a uniform delay time to LED bypass controls corresponding to all unselected LEDs of the LED string 120 in the bypass mode. The LED bypass controls are enabled after the delay time passes with respect to the transition edges of the boost enable signal BS and bypass enable BP. This delay time represents a length of a predetermined discharge period in which the boost drive voltage VBDV could drop to a tolerable drive voltage that is safe for biasing the subset of selected LEDs. Optionally, the tolerable drive voltage is substantially equal to the regular drive voltage VRDR. Optionally, the tolerable drive voltage is larger than the regular drive voltage VRDR, but safe for biasing the selected LEDs.


In some implementations, the MCU 200 introduces two or more delay times to the LED bypass controls corresponding to the unselected LEDs of the LED string 120. The unselected LEDs are bypassed sequentially for the purposes of reducing the number of the LEDs biased under the drive voltage sequentially. When the subset of the plurality of LEDs that are selected for illumination in the bypass mode includes a first subset of LEDs, a second subset of the plurality of LEDs are electrically coupled to the boost converter during the predetermined discharge period. The second subset of LEDs including more LEDs than the first subset of LEDs.


As shown in FIG. 2B, in some implementations, two LEDs (LED3 and LED4) need to be selected for illumination in the bypass mode. When the LED illumination system 100 switches from the boost mode to the bypass mode, the boost enable signal BS is disabled and the bypass enable BP is enabled. A first delay time T1 is introduced to the LED bypass signals BP5-BP8 with respect to the enable signals BS and BP. The LED bypass signals BP5-BP8 are therefore enabled after the delay time T1 to bypass a first set of unselected LEDs (LED5-LED8). An exemplary delay time T1 is equal to 40 ms, and the drive voltage VDR drops from a boost drive voltage of 15 V to a first intermediate voltage V1 (e.g., 7.5 V). Then, a second delay time T2 is introduced to the LED bypass signals BP1 and BP2 with respect to the bypass signals BP5-BP8. The LED bypass signals BP1 and BP2 are therefore enabled to bypass a second set of unselected LEDs (LED1 and LED2). An exemplary delay time T2 is equal to 2 ms, and the drive voltage VDR drops further to a second intermediate voltage V2 (e.g., 5 V) that does not overstress the selected LEDs (LED3 and LED4). Optionally, the intermediate voltage V2 is substantially equal to the regular drive voltage VRDR. Optionally, the intermediate voltage V2 is higher than the regularly drive voltage VRDR, but safe for biasing the selected LEDs.


On the other hand, in some implementations, when the LED illumination system 100 transitions from the bypass mode to the boost mode, the MCU 200 introduces delays to the boost enable signal BS and the bypass enable BP with respect to the LED bypass control signals. The LED bypass control signals are disabled for the unselected LEDs in the bypass mode, and the plurality of LEDs is electrically coupled within the LED string 120 and biased by the drive voltage generated by the boost converter 104. Then, the boost enable signal BS is enabled to activate the boost controller 108 after a predetermined delay time passes with respect to the transition edge of the boost enable signal BS. The boost converter 108 increases the drive voltage from the regular drive voltage VRDR to the boost drive voltage VBDR, and the whole LED string 120 is biased under the increased drive voltage.


Under some circumstances, when the boost enable signal BS is enabled to activate the boost controller 108, the boost converter 108 increases the drive voltage from the regular drive voltage VRDR to the boost drive voltage VBDR at a relatively slow rate. The MCU 200 does not need to introduce the delay times to the boost enable signal BS and the bypass enable BP with respect to the LED bypass control signals. In some implementations, when the boost enable signal BS is enabled to activate the boost controller 108, the LED bypass control signals transitions substantially concurrently with the boost enable signal BS.



FIGS. 3A and 3B illustrate two examples of a top view of a camera module 300 that includes a plurality of LEDs in accordance with some implementations, respectively. In some implementations, the camera module 300 includes camera lens 302, high definition image sensors, a microphone, a speaker, and one or more antennas. In accordance a regular monitor mode, the camera module 300 is configured to provide video monitoring and security in a smart home environment that is illuminated by visible light sources (e.g., the sun or light bulbs). The camera module 300 captures multimedia data (video and audio data) in real-time, and communicates raw or processed multimedia data to its users via a remote surveillance server. The captured raw multimedia data are optionally processed locally in the camera module 300 or remotely within the remote surveillance server.


In some implementations, the camera module 300 includes alternative operation modes, such as a night vision mode and a depth imaging mode. Each of the alternative operation modes is associated with a respective illumination condition. For example, in the night vision mode, the camera module 300 is configured to capture activities in the smart home environment at night when no or limited visible light illumination is available. In the depth imaging mode, the camera module 300 is configured to create a depth map or image for the corresponding field of view in the smart home environment. The depth map could be subsequently used in the regular monitor mode for accurate identification of objects in the smart home environment. In some implementations, the depth image is created based on one or more images captured when part of the field of view is selectively illuminated. Therefore, in some implementations, the camera module 300 is configured to include a LED illumination system 100 as shown in FIG. 1, and use it as an internal light source to provide illumination in the smart home environment according to the respective illumination condition associated with each alternative operation mode of the camera module 300.


Specifically, in some implementations, the plurality of LEDs includes infrared LEDs. The infrared LEDs are enclosed within a dark-colored, infrared-transparent plastic cover of the camera module 300, and therefore invisible from the exterior of the camera module 300. Given that the plastic cover permits infrared light to pass through it, the camera module 204 could rely on the infrared LEDs 308 to provide illumination at night. In the night vision mode, the plurality of LEDs is powered on to illuminate the field of view with infrared light at night. The camera module 300 includes infrared image sensors that capture infrared images or video clips of the field of view.


Alternatively, in some implementations, the plurality of LEDs is a mix of infrared and visible light LEDs, including at least one infrared LED and at least one visible light LED. In the night vision mode, the at least one infrared LED of the plurality of LEDs is powered on to illuminate the field of view with infrared light.


In some implementations, as shown in FIG. 3A, the plurality of LEDs of the LED illumination system 100 is disposed on an internal assembly structure of the camera module 300, and configured to surround the camera lens 302 of the camera module 300. In this example, the plurality of LEDs includes eight LEDs that are grouped in four pairs of LEDs. The four pairs of LEDs are disposed symmetrically within four quadrants surrounding the camera lens 302. In some implementations, a mechanical or electrical component 304 is placed between two LED pairs or between two LEDs within a LED pair. In another example, the plurality of LEDs includes six LEDs. Three LEDs are disposed on one side of the camera lens 302, and three LEDs are disposed on the other side. Also, it is noted that the camera lens 302 could be surrounded by a number of LEDs having a physical arrangement that is distinct from those of the above implementations or examples (e.g., the camera lens 302 is surround by a hundred LEDs distributed uniformly in three layers surrounding the camera lens 302).


In some implementations, as shown in FIG. 3B, each LED is optionally tilted with an angle with respect to the optical axis that passes through a center 306 of the camera lens 302. Here, the optical axis is perpendicular to the lens surface at the center 306 of the camera lens 302. In some implementations, each LED is tilted away from the optical axis of the camera with the angle in the range of 20-40 degrees.


In some implementations related to the depth imaging mode, the plurality of LEDs is grouped into a number of LED sets, and each LED set is selectively powered up to illuminate respective part of a field of view associated with a venue where the camera module 300 is located. Images captured in association with these LED sets are combined to generate a depth map of the entire field of view at the venue. The camera module 300 operates in this depth imaging mode, when the camera module 300 is not busy with other operation modes (e.g., the regular monitor mode). Thus, in some implementations, the camera module 300 operates the depth imaging mode at night using infrared LED illumination without interrupting normal camera operations or disturbing regular human activities.



FIGS. 3C and 3D illustrate two sets of exemplary LED illumination patterns 320 and 340 associated with a depth imaging mode of the camera 300 shown in FIG. 3A in accordance with some implementations, respectively. The plurality of LEDs includes eight LEDs that are grouped in four pairs of LEDs. The four pairs of LEDs are disposed symmetrically within four quadrants surrounding the camera lens 302. The eight LEDs are electrically coupled in series to form a LED string 120, and driven in a LED illumination system 100 as shown in FIG. 1. In some implementations, the LED illumination system 100 operates at a boost mode, and the boost controller 106 is electrically coupled to control the boost converter 104 to drive the LED string 120 by a boosted drive voltage VBDR. In accordance with that the whole LED string 120 are powered up, the plurality of LEDs illuminates the field of view at the venue where the camera module 300 is located, and the camera module 300 could operate at a night vision mode to capture images or video clips of the entire field of view.


Alternatively, in the depth imaging mode, the LED illumination system 100 powers up the four LED pairs in the four quadrants (LED1 and LED2 in quadrant I, LED3 and LED4 in quadrant II, LED5 and LED6 in quadrant III, and LED7 and LED8 in quadrant IV) separately. Each LED pair illuminates their respective part of the field of view associated with the corresponding quadrant. Such partial illumination involves subsets of selected LEDs, and is enabled by controlling the bypass elements 102 in the LED illumination system 100. For example, the bypass elements 102 for LED3-LED8 are enabled by the LED bypass controls BP3-BP8 to bypass LED3-LED8, when the LED1-LED2 pair is electrically coupled and driven to illuminate the part of the field of view associated with quadrant I.


In some implementations, the plurality of LEDs is grouped according to another coupling configuration to provide a distinct illumination pattern. For example, as shown in FIG. 3D, the plurality of LEDs is still grouped into four LED pairs, but are paired up differently: LED2 and LED3, LED4 and LED5, LED6 and LED7, and LED 8 and LED1. In the depth imaging mode, the LED illumination system 100 powers up these four LED pairs to illuminate part of the field of view that is distinct from that associated with FIG. 3A. This distinct illumination pattern of FIG. 3D is also enabled by controlling the bypass elements 102 in the LED illumination system 100. For example, the bypass elements 102 for LED1, and LED4-LED8 are enabled by the LED bypass controls BP1, and BP4-BP8 to bypass LED1, and LED4-LED8, respectively, when the LED2-LED3 pair is electrically coupled and driven to illuminate the corresponding part of the field of view.


It is noted that when a subset of the plurality of LEDs (e.g., LED1 and LED2 in FIG. 3C) is powered for illumination, the LED illumination system 100 operates in a bypass mode in association with an exemplary depth imaging mode of the camera module 300. As explained above, in the bypass mode, the boost controller 106 of the LED illumination system 100 is deactivated to allow the boost converter 104 to drive a subset of the plurality of LEDs by a regular drive voltage VRDR that is substantially lower than the boosted drive voltage VBDR associated with the boost mode. More details on the LED illumination system 100 are explained above with reference to FIGS. 1, 2A and 2B.



FIG. 4 is a circuit diagram illustrating an exemplary bypass element 102 for bypassing one or more LEDs within a LED string 120 in accordance with some implementations. The bypass element 102 is coupled in parallel with the one or more LEDs, and configured to bypass the one or more LEDs by shorting two end terminals thereof. The bypass element 102 includes an N-type metal-oxide-semiconductor field effect transistor (MOSFET) 402, a P-type MOSFET 404, and two resistors R1 and R2. The MOSFET 402 is coupled to receive a LED bypass control signal BPn, where n identifies the one or more LEDs of the LED string 120. When the LED bypass control signal BPn is enabled, the MOSFET 402 is switched off, and the MOSFET 404 is switched on. The MOSFET 404 shorts two terminals of the one or more LEDs, and thereby bypasses the one or more LEDs from the LED string 120. As such, the bypass element 102 is enabled by the corresponding LED bypass control to provide a low impedance path for bypassing the one or more LEDs.



FIG. 5 is a circuit diagram illustrating a current sink 500 that is electrically coupled in a LED illumination system 100 in accordance with some implementations. The current sink 500 is optionally implemented as the first current sink 108 or the second current sink 110. In accordance with the operation mode of the LED illumination system 100 (the boost mode or the bypass mode), the current sink 500 is enabled by a boost enable signal BS or a bypass enable signal BP, respectively. The current sink includes a voltage source 502, an operational amplifier (OPAMP) 504, a MOSFET 506 and a resistor R3. In some implementations, the voltage source 502 is a resistive voltage divider driven between a power supply VSUP and the ground. The voltage source 502 generates a DC voltage VIN, and the resistor RI has resistance RI. As such, the current sink provides a current level that is substantially equal to VIN/RI.


It is noted that FIGS. 4 and 5 merely illustrate examples of a bypass element 102 and a current sink used in the LED illumination system 100, and that implementations of the bypass element and the current sink are not limited to these examples.



FIG. 6 is a flow diagram illustrating a method 600 of manufacturing a LED illumination system 100 that operates in a boost mode and a bypass mode in accordance with some implementations. A plurality of LEDs is provided (602), and coupled in series to form a LED string 120. In some implementations, the plurality of LEDs is disposed in a camera module to surround a camera lens, and each LED is tilted with an angle with respect to the optical axis of the camera lens. Further, in some implementations, each LED is tilted away from the optical axis of the camera with the angle in the range of 20-40 degrees. In some implementations, the plurality of LEDs includes infrared LEDs.


A plurality of bypass elements 102 are provided (604), such that each of the plurality of bypass elements 102 is coupled in parallel with a respective group of one or more of the LEDs to bypass selectively the respective group of LEDs in the bypass mode. In some implementations, each of the plurality of LEDs is coupled in parallel with a respective bypass element configurable to bypass the respective LED in the bypass mode.


A boost converter 104 is coupled (606) to the plurality of LEDs, and configured to generate a drive voltage to drive the plurality of LEDs. The boost converter 104 further includes a boost controller 106 for controlling the boost converter 104 and enabling the boost mode in response to a boost enable signal. In the boost mode, the boost controller is electrically coupled (610) to control the boost converter to drive the LED string by a boosted drive voltage, and in the bypass mode the boost controller is deactivated (612) to allow the boost converter to drive a subset of the plurality of LEDs by a regular drive voltage that is substantially lower than the boosted drive voltage. In some implementations, the voltage level of the regular drive voltage is substantially equal to that of a power supply of the LED illumination system.


In some implementations, a first current sink and a second current sink are provided (614) for coupling to the plurality of LEDs and providing two drive currents to drive the LEDs in the boost mode and the bypass mode, respectively. In some implementations, the first current sink is part of the boost controller. In the boost mode, the first current sink is electrically coupled to the whole LED string and enables a first drive current, and in the bypass mode, the second current sink is electrically coupled to the subset of the plurality of LEDs and enables a second drive current. In some implementations, the first and second drive currents are distinct.


In some implementations, the boost converter, the boost controller, and the first and second current sinks are integrated on an integrated circuit substrate.


In some implementations, the method 600 further includes providing a MCU 200 that is configured to generate the boost enable signal and a plurality of LED bypass controls. The boost enable signal is applied to control the boost controller and select one of the first and second current sinks, and each of the plurality of LED bypass controls is applied to control one of the plurality of bypass elements for bypassing the corresponding group of LEDs in the bypass mode.


In some implementations, the plurality of LEDs includes eight LEDs. In the bypass mode, six of the eight LEDs are bypassed, and two remaining LEDs are coupled in series between the boost converter and the second current sink.


In some implementations, the plurality of LEDs are grouped into four subsets of LEDs that are configured to illuminate four quadrants of a field of view, respectively, and depth information of the field of view is recovered at night time according to the variation of the field of view illuminated by these four subsets of LEDs.


In some implementations, when the LED system switches from the boost mode to the bypass mode, both the boost controller and the first current sink are deactivated, and the second current sink is electrically coupled to the whole LED string for at least a predetermined discharge period, before the subset of the plurality of LEDs are electrically coupled and biased by the regular drive voltage. Further, in some implementations, the predetermined discharge period is substantially equal to or longer than 40 msec. Alternatively, in some implementations, the subset of the plurality of LEDs include a first subset of LEDs, and a second subset of the plurality of LEDs are electrically coupled to the boost converter during the predetermined discharge period. The second subset of LEDs includes more LEDs than the first subset of LEDs.


It is noted that the LED illumination system 100 could also operate at an idle mode that is distinct from the boost mode and the bypass mode. In the idle mode, none of the plurality of LEDs is enabled to provide illumination.


Reference will now be made in detail to implementations, examples of which are illustrated in the accompanying drawings. In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the various described implementations. However, it will be apparent to one of ordinary skill in the art that the various described implementations may be practiced without these specific details. In other instances, well-known methods, procedures, components, circuits, and networks have not been described in detail so as not to unnecessarily obscure aspects of the implementations.


It will also be understood that, although the terms first, second, etc. are, in some instances, used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first current sink could be termed a second current sink, and, similarly, a second current sink could be termed a first current sink, without departing from the scope of the various described implementations. The first current sink and the second current sink are both current sinks, but they are not the same current sink.


The terminology used in the description of the various described implementations herein is for the purpose of describing particular implementations only and is not intended to be limiting. As used in the description of the various described implementations and the appended claims, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term “and/or” as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms “includes,” “including,” “comprises,” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.


As used herein, the term “if” is, optionally, construed to mean “when” or “upon” or “in response to determining” or “in response to detecting” or “in accordance with a determination that,” depending on the context. Similarly, the phrase “if it is determined” or “if [a stated condition or event] is detected” is, optionally, construed to mean “upon determining” or “in response to determining” or “upon detecting [the stated condition or event]” or “in response to detecting [the stated condition or event]” or “in accordance with a determination that [a stated condition or event] is detected,” depending on the context.


It is to be appreciated that “smart home environments” may refer to smart environments for homes such as a single-family house, but the scope of the present teachings is not so limited. The present teachings are also applicable, without limitation, to duplexes, townhomes, multi-unit apartment buildings, hotels, retail stores, office buildings, industrial buildings, and more generally any living space or work space.


The foregoing description, for purpose of explanation, has been described with reference to specific implementations. However, the illustrative discussions above are not intended to be exhaustive or to limit the scope of the claims to the precise forms disclosed. Many modifications and variations are possible in view of the above teachings. The implementations were chosen in order to best explain the principles underlying the claims and their practical applications, to thereby enable others skilled in the art to best use the implementations with various modifications as are suited to the particular uses contemplated.

Claims
  • 1. A camera, comprising: a plurality of light sources configured to illuminate a field of view and configurable into a plurality of light source subsets;a light source driver coupled to the plurality of light sources and configured to drive the plurality of light sources with a first drive voltage at a first mode and with a second drive voltage at a second mode, the second drive voltage being lower than the first drive voltage; anda microcontroller configured to: illuminate a first quadrant of a field of view of the camera, using a first subset of the plurality of light sources, by applying a first drive voltage; andilluminate a second quadrant of the field of view of the camera, using a second subset of the plurality of light sources, by applying a second drive voltage.
  • 2. The camera of claim 1, wherein in the first mode, the plurality of light sources is electrically coupled in series to form a string that is driven by the first drive voltage.
  • 3. The camera of claim 1, wherein each of the plurality of light source subsets includes one or more light source members, further comprising: a bypass circuit coupled to the plurality of light sources and configured to enable each of the plurality of light source subsets by bypassing a respective set of light sources that are distinct from the respective one or more light source members of the respective light source subset, allowing the respective one or more light source members to be electrically coupled in series and form the respective light source subset.
  • 4. The camera of claim 3, wherein the bypass circuit includes a plurality of bypass elements, and each light source is coupled in parallel with one of the plurality of bypass elements configurable to bypass the respective light source in the second mode.
  • 5. The camera of claim 1, wherein the plurality of light sources includes eight light sources, and in the second mode, six of the eight light sources are bypassed, and two remaining light sources are coupled in series and driven by the second drive voltage.
  • 6. The camera of claim 1, wherein the plurality of light sources includes a plurality of light emitting diodes (LEDs).
  • 7. The camera of claim 6, further comprising a camera lens configured to capture visual data of the field of view, and wherein the plurality of LEDs is disposed to surround the camera lens.
  • 8. The camera of claim 7, wherein each LED is tilted with an angle with respect to an optical axis of the camera lens.
  • 9. The camera of claim 8, wherein each LED is tilted away from the optical axis of the camera with the angle in a range of 20 to 40 degrees.
  • 10. The camera of claim 7, wherein the plurality of light sources is disposed symmetrically with respect to the camera lens.
  • 11. An electronic device, comprising: a plurality of light sources configured to illuminate a field of view and configurable into a plurality of light source subsets;a light source driver coupled to the plurality of light sources and configured to drive the plurality of light sources with a first drive voltage at a first mode and with a second drive voltage at a second mode, the second drive voltage being lower than the first drive voltage; anda microcontroller configured to: illuminate a first quadrant of a field of view of the electronic device, using a first subset of the plurality of light sources, by applying a first drive voltage; andilluminate a second quadrant of the field of view of the electronic device, using a second subset of the plurality of light sources, by applying a second drive voltage.
  • 12. The electronic device of claim 11, further comprising: a camera lens configured to capture visual data of the field of view.
  • 13. The electronic device of claim 11, wherein the plurality of light sources includes a plurality of infrared LEDs.
  • 14. The electronic device of claim 13, further comprising: a dark-colored infrared-transparent cover enclosing the plurality of infrared LEDs, wherein the plurality of infrared LEDs is not visible from an exterior of the electronic device.
  • 15. The electronic device of claim 13, wherein in a night mode associated with the second mode, one or more of the plurality of infrared light sources is driven to illuminate at least part of the field of view with infrared light.
  • 16. A method of providing a camera, comprising: providing a camera lens configured to capture visual data of a field of view;providing a plurality of light sources configured to illuminate a field of view;coupling a light source driver to the plurality of light sources, the light source driver being configured to drive the plurality of light sources with a first drive voltage at a first mode and with a second drive voltage at a second mode, the second drive voltage being lower than the first drive voltage; andproviding a microcontroller configured to: illuminate a first quadrant of a field of view of the camera, using a first subset of the plurality of light sources, by applying a first drive voltage; andilluminate a second quadrant of the field of view of the camera, using a second subset of the plurality of light sources, by applying a second drive voltage.
  • 17. The method of claim 16, further comprising: providing a camera lens configured to capture visual data of the field of view, image sensors, a microphone, a speaker, and one or more antennas, wherein the camera is configured to communicate the visual data to a client device via a remote surveillance server in real time while capturing the visual data.
  • 18. The method of claim 16, wherein the plurality of light sources is grouped into four subsets of light sources that are configured to illuminate four quadrants of the field of view, respectively.
  • 19. The method of claim 18, wherein depth information of the field of view is recovered at night time according to a variation of the field of view illuminated by the four subsets of light sources.
  • 20. The method of claim 16, wherein: when driven by the first drive voltage in the first mode, the plurality of light sources is associated with a first drive current; andwhen driven by the second drive voltage in the second mode, a selected one of the plurality of light source subsets is associated with a second drive current that is distinct from the first drive voltage.
RELATED APPLICATIONS

This application is a continuation of and claims priority to U.S. patent application Ser. No. 16/552,748, filed Aug. 27, 2019, titled “Electronic Device with Adjustable Illumination,” which is a continuation of U.S. patent application Ser. No. 16/268,396, filed Feb. 5, 2019, titled “Camera Illumination,” now U.S. Pat. No. 10,397,490, issued on Aug. 27, 2019, which is a continuation of U.S. patent application Ser. No. 15/863,567, filed Jan. 5, 2018, titled “Camera with LED Illumination,” now U.S. Pat. No. 10,218,916, issued on Feb. 26, 2019, which is a continuation of U.S. patent application Ser. No. 15/403,132, filed Jan. 10, 2017, titled “Multi-Mode LED Illumination System,” now U.S. Pat. No. 9,866,760, issued on Jan. 9, 2018, which is a continuation of U.S. patent application Ser. No. 14/723,276, filed May 27, 2015, titled “Multi-Mode LED Illumination System,” now U.S. Pat. No. 9,544,485, issued on Jan. 10, 2017, all of which are incorporated by reference herein in their entireties.

US Referenced Citations (304)
Number Name Date Kind
2997935 Scheffold Aug 1961 A
3782260 Ettischer et al. Jan 1974 A
D349914 Usui Aug 1994 S
D357267 Yotsuya Apr 1995 S
D372490 Sheffield et al. Aug 1996 S
5604534 Hedges Feb 1997 A
D385571 Abrams Oct 1997 S
5862428 An Jan 1999 A
5963253 Dwyer Oct 1999 A
5978028 Yamane Nov 1999 A
5995273 Chandrasekhar Nov 1999 A
6033592 Chandrasekhar Mar 2000 A
6088470 Camus Jul 2000 A
D429269 Renkis Aug 2000 S
D429743 Renkis Aug 2000 S
6141052 Fukumitsu Oct 2000 A
6147701 Tamura Nov 2000 A
D442202 Pfeifer May 2001 S
D445123 Shen Jul 2001 S
6268882 Elberbaum Jul 2001 B1
D446534 Zimmer Aug 2001 S
6271752 Vaios Aug 2001 B1
D447758 Lin et al. Sep 2001 S
D449630 Rak et al. Oct 2001 S
D452259 Choi Dec 2001 S
6357936 Elberbaum Mar 2002 B1
D455164 Tsang et al. Apr 2002 S
6462781 Arnold Oct 2002 B1
D467952 Nakamura Dec 2002 S
D469775 Bradley Feb 2003 S
D470874 Chiu Feb 2003 S
D470875 Liao Feb 2003 S
6515275 Hunter et al. Feb 2003 B1
6634804 Toste et al. Oct 2003 B1
6650694 Brown et al. Nov 2003 B1
6678001 Elberbaum Jan 2004 B1
6714236 Wada Mar 2004 B1
6714286 Wheel Mar 2004 B1
6727954 Okada et al. Apr 2004 B1
D489388 Saito et al. May 2004 S
6741286 Meek et al. May 2004 B2
6762790 Matko et al. Jul 2004 B1
D511352 Oliver et al. Nov 2005 S
7034884 Misawa Apr 2006 B2
7066664 Sitoh et al. Jun 2006 B1
7076162 Yamashita Jul 2006 B2
D527755 Wu Sep 2006 S
7151565 Wada Dec 2006 B1
D534938 Beasley et al. Jan 2007 S
D537097 Freeman Feb 2007 S
D542320 Cheng May 2007 S
D552649 Logan et al. Oct 2007 S
D552659 Stephens et al. Oct 2007 S
D555692 Liu et al. Nov 2007 S
7290740 Joy et al. Nov 2007 B2
D558250 Hsia Dec 2007 S
D563446 Stephens et al. Mar 2008 S
D575316 Liu et al. Aug 2008 S
7443446 Seo Oct 2008 B2
7552340 Ooi et al. Jun 2009 B2
7586537 Konishi et al. Sep 2009 B2
D606105 Hinkel Dec 2009 S
7646425 Bohaker et al. Jan 2010 B2
7649472 Paterno Jan 2010 B1
D610601 Melder Feb 2010 S
D614223 Kim et al. Apr 2010 S
7705882 Engel et al. Apr 2010 B2
7741788 Ito Jun 2010 B2
D627815 Oba Nov 2010 S
D628223 Kao Nov 2010 S
7874917 Marks et al. Jan 2011 B2
7930369 Marriott et al. Apr 2011 B2
D638461 Kim et al. May 2011 S
7986369 Burns Jul 2011 B1
D648766 Chen Nov 2011 S
D651229 Tan et al. Dec 2011 S
D651230 Tan et al. Dec 2011 S
8072536 Campbell Dec 2011 B1
D651633 Park et al. Jan 2012 S
8139122 Rolston Mar 2012 B2
D657410 Helaoui et al. Apr 2012 S
8165146 Melick et al. Apr 2012 B1
8174972 Cernius et al. May 2012 B2
8359622 Everson Jan 2013 B1
8363157 Han Jan 2013 B1
D678929 Hancock Mar 2013 S
8402145 Holden et al. Mar 2013 B2
8432485 Martinez et al. Apr 2013 B1
D687085 Manson Jul 2013 S
8504707 Toebes et al. Aug 2013 B2
8520069 Haler Aug 2013 B2
D694305 Katori et al. Nov 2013 S
D697119 Park et al. Jan 2014 S
8625024 Hsu Jan 2014 B2
D700232 Ramsay Feb 2014 S
8817107 Matsumoto et al. Aug 2014 B2
D719205 Matsumoto Dec 2014 S
D729296 Shelton May 2015 S
D730422 Kim et al. May 2015 S
9071740 Duffy et al. Jun 2015 B1
D733781 Chen Jul 2015 S
D734801 Yang Jul 2015 S
9102055 Konolige et al. Aug 2015 B1
D740871 Moon et al. Oct 2015 S
D742954 Simonelli et al. Nov 2015 S
D743465 Aglassinger et al. Nov 2015 S
D745916 Oh Dec 2015 S
D746350 Li Dec 2015 S
D748709 Jeong Feb 2016 S
D755880 Luo et al. May 2016 S
9330307 Litvak et al. May 2016 B2
9386230 Duran Jul 2016 B1
9544485 Conner Jan 2017 B2
9838602 Duran et al. Dec 2017 B2
9866760 Dorai et al. Jan 2018 B2
9875718 Basehore et al. Jan 2018 B1
10218916 Dorai et al. Feb 2019 B2
10397490 Dorai et al. Aug 2019 B2
11219107 Dorai et al. Jan 2022 B2
20010015760 Fellegara Aug 2001 A1
20010022550 Steffel Sep 2001 A1
20020003575 Marchese Jan 2002 A1
20020056794 Ibrahim May 2002 A1
20020107591 Gabai et al. Aug 2002 A1
20020118114 Ohba et al. Aug 2002 A1
20020141418 Ben-Dor et al. Oct 2002 A1
20020159270 Lynam et al. Oct 2002 A1
20020160724 Arai et al. Oct 2002 A1
20020171754 Lai et al. Nov 2002 A1
20020186317 Kayanuma Dec 2002 A1
20020191082 Fujino et al. Dec 2002 A1
20030164881 Ohe et al. Sep 2003 A1
20030169354 Aotsuka Sep 2003 A1
20030193409 Crank Oct 2003 A1
20030216151 Kitano et al. Nov 2003 A1
20040130655 Yanakawa et al. Jul 2004 A1
20040132489 Ryley et al. Jul 2004 A1
20040211868 Holmes et al. Oct 2004 A1
20040246341 Lee et al. Dec 2004 A1
20040247203 Dell'Eva Dec 2004 A1
20040257431 Girish et al. Dec 2004 A1
20050062720 Rotzoll et al. Mar 2005 A1
20050068423 Bear et al. Mar 2005 A1
20050073575 Thacher et al. Apr 2005 A1
20050088537 Nakamura et al. Apr 2005 A1
20050128336 Toledano et al. Jun 2005 A1
20050146792 Schofield et al. Jul 2005 A1
20050149213 Guzak et al. Jul 2005 A1
20050151042 Watson Jul 2005 A1
20050200751 Weaver Sep 2005 A1
20050212958 Su et al. Sep 2005 A1
20050227217 Wilson Oct 2005 A1
20050230583 Wu Oct 2005 A1
20050237425 Lee et al. Oct 2005 A1
20050243022 Negru Nov 2005 A1
20050243199 Bohaker et al. Nov 2005 A1
20050275723 Sablak et al. Dec 2005 A1
20060017842 Jun Jan 2006 A1
20060024046 Jones Feb 2006 A1
20060086871 Joseph et al. Apr 2006 A1
20060109375 Ho et al. May 2006 A1
20060109613 Chen May 2006 A1
20060123129 Toebes et al. Jun 2006 A1
20060123166 Toebes et al. Jun 2006 A1
20060150227 Julia et al. Jul 2006 A1
20060210259 Matsumoto Sep 2006 A1
20060238707 Elvesjo Oct 2006 A1
20060244583 Kawada et al. Nov 2006 A1
20060262194 Swain Nov 2006 A1
20060282866 Kuo Dec 2006 A1
20070001087 Shyu et al. Jan 2007 A1
20070011375 Kumar Jan 2007 A1
20070036539 Martinez et al. Feb 2007 A1
20070050828 Renzi et al. Mar 2007 A1
20070083791 Panesar et al. Apr 2007 A1
20070219686 Plante Sep 2007 A1
20070222888 Xiao et al. Sep 2007 A1
20080001547 Negru Jan 2008 A1
20080005432 Kagawa Jan 2008 A1
20080012980 Yamane Jan 2008 A1
20080026793 Teegan et al. Jan 2008 A1
20080031161 Osthus Feb 2008 A1
20080056709 Huang Mar 2008 A1
20080074535 Ohsuga Mar 2008 A1
20080151052 Erel et al. Jun 2008 A1
20080152218 Okada et al. Jun 2008 A1
20080186150 Kao Aug 2008 A1
20080189352 Mitchell et al. Aug 2008 A1
20080198225 Gal et al. Aug 2008 A1
20080231699 Konishi et al. Sep 2008 A1
20080291260 Dignan et al. Nov 2008 A1
20080309765 Dayan et al. Dec 2008 A1
20080315778 Tatsukawa Dec 2008 A1
20080316594 Hashiguchi et al. Dec 2008 A1
20090019187 Okuma Jan 2009 A1
20090027570 Fujinawa Jan 2009 A1
20090069633 Orihara et al. Mar 2009 A1
20090102715 Lou et al. Apr 2009 A1
20090141918 Chris et al. Jun 2009 A1
20090141939 Chambers et al. Jun 2009 A1
20090158373 Belz et al. Jun 2009 A1
20090175612 Wen Jul 2009 A1
20090195655 Pandey Aug 2009 A1
20090245268 Pugliese, IV Oct 2009 A1
20090248918 Diab et al. Oct 2009 A1
20090289921 Michelson et al. Nov 2009 A1
20090296735 Cernius et al. Dec 2009 A1
20090309969 Wendler Dec 2009 A1
20100026811 Palmer Feb 2010 A1
20100039253 Zang Feb 2010 A1
20100076600 Cross et al. Mar 2010 A1
20100085749 Bezgachev Apr 2010 A1
20100109878 Desrosiers May 2010 A1
20100180012 Heo et al. Jul 2010 A1
20100199157 Takaoka et al. Aug 2010 A1
20100271503 Safaee-Rad et al. Oct 2010 A1
20100306399 Khgosravi et al. Dec 2010 A1
20100314508 Bevirt et al. Dec 2010 A1
20100328460 Merkel et al. Dec 2010 A1
20100328475 Thomas et al. Dec 2010 A1
20100330843 Gao Dec 2010 A1
20110007159 Camp et al. Jan 2011 A1
20110102438 Mathe et al. May 2011 A1
20110102588 Trundle et al. May 2011 A1
20110134243 Siann et al. Jun 2011 A1
20110134313 Kato Jun 2011 A1
20110158637 Jung Jun 2011 A1
20110161076 Davis et al. Jun 2011 A1
20110193964 McLeod Aug 2011 A1
20110193967 Matsumorto et al. Aug 2011 A1
20110205965 Sprigg et al. Aug 2011 A1
20110231903 Springer et al. Sep 2011 A1
20110234803 Nakajima et al. Sep 2011 A1
20110255289 Krah Oct 2011 A1
20110267492 Prentice et al. Nov 2011 A1
20110285813 Girdzijauskas et al. Nov 2011 A1
20110293137 Gumnan et al. Dec 2011 A1
20110299728 Markovic et al. Dec 2011 A1
20120004956 Huston et al. Jan 2012 A1
20120026325 Bunker et al. Feb 2012 A1
20120081009 Shteynberg Apr 2012 A1
20120086815 Cooper et al. Apr 2012 A1
20120105632 Renkis May 2012 A1
20120106037 Diebel May 2012 A1
20120127270 Zhang et al. May 2012 A1
20120140068 Monroe et al. Jun 2012 A1
20120162416 Su et al. Jun 2012 A1
20120194650 Izadi et al. Aug 2012 A1
20120235884 Miller et al. Sep 2012 A1
20120236373 Oyama Sep 2012 A1
20120246359 Scragg et al. Sep 2012 A1
20120262575 Champagne et al. Oct 2012 A1
20120263447 Fransson Oct 2012 A1
20120263450 Totani Oct 2012 A1
20120311686 Medina et al. Dec 2012 A1
20120328259 Seibert et al. Dec 2012 A1
20120328358 Akiyama Dec 2012 A1
20130007099 Lee et al. Jan 2013 A1
20130053657 Ziarno et al. Feb 2013 A1
20130156260 Craig Jun 2013 A1
20130162629 Huang et al. Jun 2013 A1
20130314544 Ban Nov 2013 A1
20130321564 Smith et al. Dec 2013 A1
20130342653 McCloskey et al. Dec 2013 A1
20140032796 Krause Jan 2014 A1
20140047143 Bateman et al. Feb 2014 A1
20140049609 Wilson et al. Feb 2014 A1
20140119604 Mai et al. May 2014 A1
20140168421 Xu et al. Jun 2014 A1
20140241387 Ortiz Aug 2014 A1
20140267874 Ratcliff et al. Sep 2014 A1
20140270387 Hoof et al. Sep 2014 A1
20140333726 Tokui et al. Nov 2014 A1
20140375635 Johnson et al. Dec 2014 A1
20150049324 Tan et al. Feb 2015 A1
20150052029 Wu et al. Feb 2015 A1
20150077737 Belinsky et al. Mar 2015 A1
20150120389 Zhang et al. Apr 2015 A1
20150154467 Feng et al. Jun 2015 A1
20150170371 Muninder et al. Jun 2015 A1
20150181198 Baele et al. Jun 2015 A1
20150185592 Eineren et al. Jul 2015 A1
20150228114 Shapira et al. Aug 2015 A1
20150304470 Cheatham Oct 2015 A1
20160012588 Taguchi et al. Jan 2016 A1
20160022181 Valsan et al. Jan 2016 A1
20160027262 Skotty et al. Jan 2016 A1
20160029102 Daily Jan 2016 A1
20160094763 Patel Mar 2016 A1
20160094829 Georgiev et al. Mar 2016 A1
20160142681 Yu May 2016 A1
20160205318 Wang et al. Jul 2016 A1
20160255153 Ayers et al. Sep 2016 A1
20160261829 Olsson Sep 2016 A1
20160353531 Conner et al. Dec 2016 A1
20170126949 Dorai et al. May 2017 A1
20170238401 Sadwick et al. Aug 2017 A1
20170328997 Silverstein et al. Nov 2017 A1
20170343801 Dabic et al. Nov 2017 A1
20180052376 Burrows et al. Feb 2018 A1
20180113331 Wang et al. Apr 2018 A1
20180167543 Dorai et al. Jun 2018 A1
20190174048 Dorai et al. Jun 2019 A1
20200053269 Dorai et al. Feb 2020 A1
Foreign Referenced Citations (3)
Number Date Country
2492833 Jan 2013 GB
2005004035 Jan 2005 WO
2005034505 Apr 2005 WO
Non-Patent Literature Citations (46)
Entry
“0308 Brand USB 2.0 HD Night Vision Webcarn Web Carn Camera Webcarnera With Microphone Sucker Stand for PC Computer Laptop Notebook”, Dec. 18, 2015, 13 pages.
“720p TF Card IP Wireless Camera Indoor Built-In Microphone Support Two Way Intercom for Smart Horne Life and Unique PIR Alarm”, Dec. 18, 2015, 3 pages.
“Android USB Port Forwarding—Parent”, http://www.codeproject.com/Articles/191930/Android-Usb-Port-Forwarding, Dec. 26, 2011, 7 pages.
“Belkin F7D7601AU, Net Carn IP WIFI Baby Pet Monitor Camera Security Night Vision”, Ebay, Dec. 15, 2015, 5 pages.
“Buy Svb Ladybird Tripod Webcarn 4 Mega Pixel—4 Megapixel Web Carn Online”, Best Prices in India: Rediff Shopping, Dec. 16, 2015, 3 pages.
“Drivers—Video Carn: Download Drivers for (Genius VideoCAM NB) VisualNideo Camera”, Computer Question Help, Jul. 3, 2008, 2 pages.
“Final Office Action”, U.S. Appl. No. 16/552,748, dated May 21, 2021, 8 pages.
“Goods in Stock PC Camera USB Plug and Play Free Driver Digital Webcam Stand Web Camera”, Dec. 18, 2015, 2 pages.
“International Preliminary Report on Patentability”, Application No. PCT/US2016/037069, dated Dec. 12, 2017, 7 pages.
“International Preliminary Report on Patentability”, Application No. PCT/US2016/034462, dated Nov. 28, 2017, 8 pages.
“International Search Report and Written Opinion”, Application No. PCT/US216/034462, dated Nov. 11, 2016, 10 pages.
“International Search Report and Written Opinion”, Application No. PCT/US2018/048780, dated Mar. 18, 2019, 11 pages.
“International Search Report and Written Opinion”, Application No. PCT/US216/037069, dated Aug. 24, 2016, 9 pages.
“IconArchive, Device WebCam Icon, Phuzion Iconset”, KYO-TUX, Jun. 8, 2010, 3 pages.
“Linksys Wireless-N Internet Horne Monitoring Camera: Horne Security Systems: Camera & Photo, Amazon.com”, Dec. 15, 2015, 7 pages.
“Logi Circle: Portable Home Surveillance Camera from Logitech (video)”, AppleApple.Top World News, Feb. 10, 2015, 5 pages.
“Lot of 2 USB WebCam Web Cam Camera Logitech Quickcam HP Hewlett Packard,”, Ebay, Dec. 16, 2015, 3 pages.
“Mini Universal Tripod Stand for Digital Camera and Webcam A33-in Tripods from Consumer Electronics on Aliexpress.com,”, Alibaba Group, Store: Angel One-Stop Shopping Center, Dec. 16, 2015, 3 pages.
“Motorola MBP421 Digital Video & Sound Rechargeable Baby Monitor 1.8″ LCD Screen,”, Ebay, Dec. 15, 2015, 5 pages.
“New Smallest Mini Camera Camcorder Video Recorder DVR Spy Hidden Pinhole Web Cam,”, Ebay, Dec. 2, 2015, 4 pages.
“Non-Final Office Action”, U.S. Appl. No. 16/552,748, dated Feb. 12, 2021, 11 pages.
“Notice of Allowance”, U.S. Appl. No. 16/552,748, dated Aug. 27, 2021, 9 pages.
“Restore.Solutions, Numus Software, USB/VID, Syntek Web Cam Device Drivers”, Dec. 12, 2015, 10 pages.
“Restriction Requirement”, U.S. Appl. No. 16/552,748, dated Oct. 23, 2020, 6 pages.
“The Home Pro Wi-Fi Wireless Cloud Video Monitoring Security Camera (Black): Camera & Photo”, Ion Camera, Dec. 15, 2015, 6 pages.
“Tripod Support for a QuickCam ( or other webcam )”, Instructables, 2015, 3 pages.
“USB/IP Project—USB Request Over IP Network”, http://web.archive.org/web/20111227171215/http://usbip.sourceforge.net/ , Dec. 27, 2011, 5 pages.
“Web Camera 6 Stock Photo—Dreamstime”, Dec. 16, 2015, 2 pages.
“What is USB for Remote Desktop—FabulaTech”, http://web.archive.org/web/20111212070644/http://www.usb-over-network.com/usb-for-remote-desktop.html, Dec. 12, 2011, 2 pages.
“What is USB over Network—FabulaTech”, hftp://web.archive.org/web/20111217080253/http://www.usb-over-network.com/usb-over-network.html, Dec. 17, 2011, 2 pages.
Adipranata, Rudy et al., “Fast method for multiple human face segmentation in color image”, Feb. 2009, 14 pages.
Ai-Ball, Siv “Very Small Hidden IP Network Camera Battery Powered Wireless IP Camera”, Alibaba.com, 1999-2015, 7 pages.
Darty, Tanna “Input Devices on Pintrest, Computers, Mice and Apples”, Dec. 15, 2015, 1 page.
Hampapur, Arun et al., “Smart surveillance: applications, technologies and implications”, Dec. 2003, 6 pages.
Heo, Jingu “Fusion of Visual and Thermal Face Recognition Techniques: A Comparative Study”, Oct. 2003, 75 pages.
Johnson, Joel “Glowdoodle Turns Your Crappy Webcam in a Crappier Webcam (in a good way)”, webcam—Boing Boing, Dec. 16, 2015, 8 pages.
Lewis, John “Samsung SEB-1019RW Add-On Night Vision Baby Monitor Camera”, Dec. 15, 2015, 2 pages.
Silberman, Nathan et al., “Indoor Segmentation and Support Inference from RGBD Images”, Oct. 2012, pp. 746-780.
Techallianz,“How to Pick the Right Webeam”,Satyakam, Jan. 22, 2013, 4 pages.
Trek, “Ai-Ball Mini WiFi Spy Cam IP Wireless Camera for Iphone / Android /Ipad”, Tmart, www.tmart.com, Dec. 18, 2015, 6 pages.
“Non-Final Office Action”, U.S. Appl. No. 15/403,132, dated Mar. 30, 2017, 12 pages.
“Non-Final Office Action”, U.S. Appl. No. 15/863,567, dated Jun. 14, 2018, 12 pages.
“Notice of Allowance”, U.S. Appl. No. 16/268,396, dated Apr. 10, 2019, 8 pages.
“Notice of Allowance”, U.S. Appl. No. 14/723,276, dated Aug. 31, 2016, 8 pages.
“Notice of Allowance”, U.S. Appl. No. 15/403,132, dated Sep. 1, 2017, 5 pages.
“Notice of Allowance”, U.S. Appl. No. 15/863,567, dated Oct. 3, 2018, 5 pages.
Related Publications (1)
Number Date Country
20220124889 A1 Apr 2022 US
Continuations (5)
Number Date Country
Parent 16552748 Aug 2019 US
Child 17646203 US
Parent 16268396 Feb 2019 US
Child 16552748 US
Parent 15863567 Jan 2018 US
Child 16268396 US
Parent 15403132 Jan 2017 US
Child 15863567 US
Parent 14723276 May 2015 US
Child 15403132 US