This disclosure relates generally to electronic user devices and, more particularly, to apparatus and methods for thermal management of electronic user devices.
During operation of an electronic user device (e.g., a laptop, a tablet), hardware components of the device, such as a processor, a graphics card, and/or battery, generate heat. Electronic user devices include one or more fans to promote airflow to cool the device during use and prevent overheating of the hardware components.
The figures are not to scale. In general, the same reference numbers will be used throughout the drawing(s) and accompanying written description to refer to the same or like parts.
Descriptors “first,” “second,” “third,” etc. are used herein when identifying multiple elements or components which may be referred to separately. Unless otherwise specified or understood based on their context of use, such descriptors are not intended to impute any meaning of priority, physical order or arrangement in a list, or ordering in time but are merely used as labels for referring to multiple elements or components separately for ease of understanding the disclosed examples. In some examples, the descriptor “first” may be used to refer to an element in the detailed description, while the same element may be referred to in a claim with a different descriptor such as “second” or “third.” In such instances, it should be understood that such descriptors are used merely for ease of referencing multiple elements or components.
During operation of an electronic user device (e.g., a laptop, a tablet), hardware components disposed in a body or housing of the device, such as a processor, graphics card, and/or battery, generate heat. Heat generated by the hardware components of the user device can cause a temperature of one or more portions of an exterior surface, or skin, of the device housing to increase and become warm or hot to a user's touch. To prevent overheating of the hardware components, damage to the device, and/or discomfort to the user of the device when the user touches or places one or more portions of the user's body proximate to the skin of the device and/or components of the device accessible via the exterior surface of the housing such as a touchpad, the user device includes one or more fans to exhaust hot air generated within the body of the device and cool the device.
Some known electronic user devices are configured with one or more thermal constraints to control the temperature of the hardware components of the user device and/or of the skin of the device. The thermal constraints(s) can define, for instance, a maximum temperature of a hardware component such as a processor to prevent overheating of the processor. The thermal constraint(s) can define a maximum temperature of the skin of the device to prevent discomfort to a user touching and/or holding the device. In known user devices, operation of the fan(s) of the user device and/or management of power consumed by the device are controlled based on the thermal constraint(s). For instance, if a temperature of a hardware component of the device is approaching a maximum temperature as defined by the thermal constraint for the component, rotational speed(s) (e.g., revolutions per minute (RPMs)) of the fan(s) can be increased to exhaust hot air and reduce a temperature of the component. Additionally or alternatively, power consumption by one or more components of the device (e.g., the graphics card) may be reduced to reduce the amount of heat generated by the component and, thus, the device.
In some known user devices, the thermal constraint(s) define that a temperature of the skin of the device should not exceed, for instance, 45° C., to prevent user discomfort when the user is physically touching the device (e.g., typing on a keyboard of a laptop, scrolling on a touchscreen, etc.). Temperature of the skin of the device can be controlled by controlling power consumption of the hardware component(s) disposed within the device body to manage the amount of heat generated by the component(s) transferred to the skin of the device. However, such thermal constraint(s) can affect performance of the user device. For instance, some known user devices can operate in a high performance mode, or a mode that favors increased processing speeds over energy conservation (e.g., a mode in which processing speeds remain high for the duration that the device is in use, the screen remains brightly lit, and other hardware components do not enter power-saving mode when those components are not in use). The processor consumes increased power to accommodate the increased processing speeds associated with the high performance mode and, thus, the amount of heat generated by the processor is increased. As a result, a temperature of the skin of the user device can increase due to the increased amount of heat generated within the device housing. In some known devices, the processor may operate at lower performance speeds to consume less power and, thus, prevent the skin of the device from exceeding the maximum skin temperature defined by the thermal constraint. Thus, in some known devices, processing performance is sacrificed in view of thermal constraint(s).
Higher fan speeds can be used to facilitate of cooling of hardware component(s) of a device to enable the component(s) to operate in, for instance, a high performance mode without exceeding the thermal constraint(s) for the hardware competent(s) and/or the device skin. However, operation of the fan(s) at higher speeds increases audible acoustic noise generated by the fan(s). Thus, in some known user devices, the fan speed(s) and, thus, the amount of cooling that is provided by the fan(s), are restricted to avoid generating fan noise levels over certain decibels. Some know devices define fan noise constraints that set, for instance, a maximum noise level of 35 dBA during operation of the fan(s). As a result of the restricted fan speed(s), performance of the device may be limited to enable the fan(s) to cool the user device within the constraints of the fan speed(s).
In some instances, cooling capabilities of the fan(s) of the device degrade over time due to dust accumulating in the fan(s) and/or heat sink. Some known user devices direct the fan(s) to reverse airflow direction (e.g., as compared to the default airflow direction to exhaust hot air from the device) to facilitate heatsink and fan shroud cleaning, which helps to de-clog dust from the airflow path and maintain device performance over time. However, operation of the fan(s) in the reverse direction increases audible acoustics generated by the fan(s), which can disrupt the user's experience with the device.
Although thermal constraint(s) are implemented in a user device to prevent discomfort to the user when the user is directly touching the device (e.g., physically touching one or more components of the device accessible via the exterior housing of the device, such a keyboard and/or touchpad of a laptop, a touchscreen of a tablet, etc.), there are instances in which a temperature of the skin of the device can be increased without affecting the user's experience with the device. For instance, a user may view a video on the user device but not physically touch the user device; rather, the device may be resting on a table. In some instances, the user may interact with the user device via external accessories communicatively coupled to the device, such as an external keyboard and/or an external mouse. In such instances, because the user is not directly touching the device (i.e., not directly touching the skin of the device housing and/or component(s) accessible via the exterior surface of the housing), an increase in a temperature of the skin of the device would not be detected by the user. However, known user devices maintain the skin temperature of the device at the same temperature as if the user were directly touching the user device regardless of whether the user is interacting with the device via external accessories.
In some instances, the user device is located in a noisy environment (e.g., a coffee shop, a train station). Additionally, or alternatively, in some instances, the user may be interacting with the user device while wearing headphones. In such instances, the amount of fan noise heard by the user is reduced because of the loud environment and/or the use of headphones. However, in known user devices, the rotational speed of the fan(s) of the device are maintained at a level that minimizes noise from the fan(s) regardless of the surrounding ambient noise levels and/or whether or not the user is wearing headphones.
Disclosed herein are example user devices that provide for dynamic adjustment of thermal constraints and/or fan acoustic noise levels of the user device. Example disclosed herein use a multi-tier determination to control operation of fan(s) of the device and/or to adjust a performance level of the device and, thus, control heat generated by hardware component(s) of the device based on factors such as a presence of a user proximate to the device, user interaction(s) with the device (e.g., whether the user is using an on-board keyboard of the device or an external keyboard), and/or ambient noise levels in an environment in which the device is located. Example user devices disclosed herein include sensors to detect user presence (e.g., proximity sensor(s), image sensor(s)), device configuration (e.g., sensor(s) to detect user input(s) received via an external keyboard, sensor(s) to detect device orientation), and/or conditions in the ambient environment in which the device is located (e.g., ambient noise sensor(s)). Based on the sensor data, examples disclosed herein determine whether a temperature of the skin of the device housing can be increased relative to a default thermal constraint, where the default thermal constraint corresponds to a skin temperature for the device when the user is directly touching the device (e.g., touching one or more components of the device accessible via the exterior housing of the device such as keyboard or touchpad of a laptop). Examples disclosed herein selectively control an amount of power provided to hardware component(s) of the user device and/or fan speed level(s) (e.g., RPMs) based on the selected thermal constraint (e.g., the default thermal constraint or a thermal constraint permitting a higher skin temperature for the device relative to the default thermal constraint).
In some examples disclosed herein, power consumption by one or more component(s) of the user device (e.g., the processor) is increased when the user is determined to be providing inputs to the user device via, for instance, an external keyboard. Because the user is not physically touching the exterior surface of the device housing when the user is providing inputs via the external keyboard, the temperature of the skin of the device can be increased without adversely affecting the user (e.g., without causing discomfort to the user). In some examples disclosed herein, rotational speed(s) (e.g. RPM(s)) of the fan(s) of the user device are increased when sensor data from the ambient noise sensor(s) indicates that the user is in a loud environment. In such examples, because the user device is located in a noisy environment, the resulting increase in fan acoustics from the increased rotational speed(s) of the fan(s) is offset by the ambient noise. In some other examples, the rotational direction of the fan(s) of the user device is reversed (e.g., to facilitate heatsink and fan shroud cleaning) when sensor data from the ambient noise sensor(s) indicate that the user device is in a loud environment and/or is that the user is not present or within a threshold distance of the device. Thus, the user is not interrupted by the increased fan noise and the device can be cooled and/or cleaned with increased efficiency. Rather than maintaining the thermal constraint(s) of the device and/or the fan noise constraint(s) at respective default levels during operation of the device, examples disclosed herein dynamically adjust the constraints and, thus, the performance of the device, based on user and/or environmental factors. As a result, performance of the device can be selectively increased in view of the opportunities for increased device skin temperature and/or audible fan noise levels in response to user interactions with the device.
In some examples, the user device 102 additionally or alternatively includes one or more external devices communicatively coupled to the device 102, such as an external keyboard 108, external pointing device(s) 110 (e.g., wired or wireless mouse(s)), and/or headphones 112. The external keyboard 108, the external pointing device(s) 110, and/or the headphones 112 can be communicatively coupled to the user device 102 via one or more wired or wireless connections. In the example of
The example user device 102 includes a processor 130 that executes software to interpret and output response(s) based on the user input event(s) (e.g., touch event(s), keyboard input(s), etc.). The user device 102 of
In the example of
The example user device 102 of
The example user device 102 of
The user presence detection sensor(s) 118 are carried by the example user device 102 such that the user presence detection sensor(s) 118 can detect changes in an environment in which the user device 102 is located that occur with a range (e.g., a distance range) of the user presence detection sensor(s) 118 (e.g., within 10 feet of the user presence detection sensor(s) 118, within 5 feet, etc.). For example, the user presence detection sensor(s) 118 can be mounted on a bezel of the display screen 103 and oriented such that the user presence detection sensor(s) 118 can detect a user approaching the user device 102. The user presence detection sensor(s) 118 can additionally or alternatively be at any other locations on the user device 102 where the sensor(s) 118 face an environment in which the user device 102 is located, such as on a base of the laptop (e.g., on an edge of the base in front of a keyboard carried by base), a lid of the laptop, on a base of the laptop supporting the display screen 103 in examples where the display screen 103 is a monitor of a desktop or all-in-one PC, etc.
In some examples, the user presence detection sensor(s) 118 are additionally or alternatively mounted at locations on the user device 102 where the user's arm, hand, and/or finger(s) are likely to move or pass over as the user brings his or her arm, hand, and/or finger(s) toward the display screen 103, the keyboard 104, and/or other user input device (e.g., the pointing device(s) 106). For instance, in examples in which the user device 102 is laptop or other device including a touchpad, the user presence detection sensor(s) 118 can be disposed proximate to the touchpad of the device 102 to detect when a user's arm is hovering over the touchpad (e.g., as the user reaches for the screen 103 or the keyboard 104).
In the example of
The example user device 102 of
In the example of
The example user device 102 of
The example user device 102 includes one or more semiconductor-based processors to process sensor data generated by the user presence detection sensor(s) 118, the device configuration sensor(s) 120, the image sensor(s) 122, the motion sensor(s) 123, the microphone(s) 124, and/or the temperature sensor(s) 126. For example, the sensor(s) 118, 120, 122, 123, 124, 126 can transmit data to the on-board processor 130 of the user device 102. In other examples, the sensor(s) 118, 120, 122, 123, 124, 126 can transmit data to a processor 127 of another user device 128, such as such as a smartphone or a wearable device such as a smartwatch. In other examples, the sensor(s) 118, 120, 122, 123, 124, 126 can transmit data to a cloud-based device 129 (e.g., one or more server(s), processor(s), and/or virtual machine(s)).
In some examples, the processor 130 of the user device 102 is communicatively coupled to one or more other processors. In such an example, the sensor(s) 118, 120, 122, 123, 124, 126 can transmit the sensor data to the on-board processor 130 of the user device 102. The on-board processor 130 of the user device 102 can then transmit the sensor data to the processor 127 of the user device 128 and/or the cloud-based device(s) 129. In some such examples, the user device 102 (e.g., the sensor(s) 118, 120, 122, 123, 124, 126 and/or the on-board processor 130) and the processor(s) 127, 130 are communicatively coupled via one or more wired connections (e.g., a cable) or wireless connections (e.g., cellular, Wi-Fi, or Bluetooth connections). In other examples, the sensor data may only be processed by the on-board processor 130 (i.e., not sent off the device).
In the example system 100 of
In the example of
Based on the sensor data generated by the user presence detection sensor(s) 118, the thermal constraint manager 132 determines whether or not a subject is present within the range of the user presence detection sensor(s) 118. In some examples, if the thermal constraint manager 132 determines that the user is not within the range of the user presence detection sensor(s) 118, the thermal constraint manager 132 determines that the rotational speed of the fan(s) 114 can be increased, as the user is not present to hear the increased acoustic noise generated by the fan(s) 114 operating at an increased speed. The thermal constraint manager 132 generates instructs for the fan(s) 114 to increase the rotational speed at which the fan(s) 114 operate. The fan(s) 114 can continue to operate at the increased rotational speed to provide efficient until, for instance, the processor 130 of the device 102 determines that no user input(s) have been received at the device 102 for a period of time and the device 102 should enter a low power state (e.g., a standby or sleep state).
In the example of
If the thermal constraint manager 132 determines that the user is within the range of the user presence detection sensor(s) 118 but is not providing input(s) at the device 102 and/or has not provided an input within a threshold period of time, the thermal constraint manager 132 infers a user intent to interact with the device. The thermal constraint manager 132 can use data from multiple types of sensors to predict whether the user is likely to interact with the device.
For example, the thermal constraint manager 132 can determine a distance of the user from the device 102 based on data generated by the user presence detection sensor(s) 118. If the user is determined to be outside of a predefined threshold range of the device 102 (e.g., farther than 1 meter from the device 102), the thermal constraint manager 132 determines that the rotational speed of the fan(s) 114 of the device 102 and, thus, the fan acoustics, can be increased because the increased fan noise will not disrupt the user in view of the user's distance from the device 102. Additionally or alternatively, the thermal constraint manager 132 determines that the power level of the power source(s) 116 of the device 102 and, thus, the device skin temperature, can be increased because the increased skin temperature will not cause discomfort to the user based on the user's distance from the device 102.
In some examples, thermal constraint manager 132 analyzes image data generated by the image sensor(s) 122 to determine a position of the user's eyes relative to the display screen 103 of the device 102. In such examples, if thermal constraint manager 132 identifies both of the user's eyes in the image data, the thermal constraint manager 132 determines that the user is looking at the display screen 103. If the thermal constraint manager 132 identifies one of the user's eyes or none of the user's eyes in the image data, the thermal constraint manager 132 determines that the user is not engaged with the device 102. In such examples, the thermal constraint manager 132 can instruct the fan(s) 114 to increase rotational speed(s) to cool the device 102. Because the user is not engaged or not likely engaged with the device 102 as determined based on eye tracking, the thermal constraint manager 132 permits increased fan noise to be generated by the fan(s) 114 to efficiently cool the device 102 while the user is distracted relative to the device 102. Additionally or alternatively, the thermal constraint manager 132 can instruct the power source(s) 116 to increase the power provided to the hardware component(s) of the user device 102 (and, thus, resulting in increased the skin temperature of the user device 102).
In some examples, the thermal constraint manager 132 analyzes the image data generated by the image data sensor(s) 122 and/or the motion sensor(s) 123 to identify gesture(s) being performed by the user. If the thermal constraint manager 132 determines that the user is, for instance, looking away from the device 102 and talking on the phone based on the image data and/or the motion sensor data (e.g. image data and/or motion sensor data indicating that the user has moved his or her hand proximate to his or her ear), the thermal constraint manager 132 determines that the fan acoustics can be increased because the user is not likely to interact with the device 102 while the user is looking away and talking on the phone.
The example thermal constraint manager 132 of
Additionally or alternatively, the thermal constraint manager 132 can determine whether the user is wearing headphones based on, for example, image data generated by the image sensor(s) 122 and/or data from the device configuration sensor(s) 120 indicating that headphones are connected to the device 102 (e.g., via wired or wireless connection(s)). In such examples, the thermal constraint manager 132 instructs the fan(s) 114 to rotate at increased speed(s) to increase cooling of the device 102 because the resulting increased fan noise is unlikely to be detected by the user who is wearing headphones.
The thermal constraint manager 132 dynamically adjusts the thermal constraint(s) and/or fan noise levels for the device 102 based on the inferred user intent to interact with the device and/or conditions in the environment. In some examples, the thermal constraint manager 132 determines that the user likely to interact with the device after previously instructing the fan(s) to increase rotational speed(s) based on, for example, data from the user presence detection sensor(s) 118 indicating that the user is moving toward the device 102 and/or reaching for the on-board keyboard. In such examples, the thermal constraint manager 132 instructs the fan(s) 114 to reduce the rotation speed and, thus, the fan noise in view of the expectation that the user is going to interact with the device 102.
As another example, if the thermal constraint manager 132 determines that the user is providing input(s) via the external device(s) 108, 110 and, thus, selects a thermal constraint for the device 102 that increases the temperature of the skin of the device. If, at later time, the thermal constraint manager 132 determines that the user is reaching for the display screen 103 (e.g., based on data from the user presence detection sensor(s) 118, the image sensor(s) 122, and/or the motion sensor(s) 123), the thermal constraint manager selects a thermal constraint that results in decreased temperature of the device skin. In such examples, power consumption by the hardware component(s) of the device 102 and/or fan speed(s) can be adjusted to cool the device 102.
As another example, if the thermal constraint manager 132 determines at a later time that the user is no longer wearing the headphones 112 (e.g., based on the image data) after previously determining that the user was wearing the headphones 112, the thermal constraint manager 132 instructs the fan(s) 114 to reduce rotational speed to generate less noise.
In some examples, the thermal constraint manager 132 dynamically adjusts the thermal constraint(s) and/or fan acoustic constraint(s) based on temperature data generated by the temperature sensor(s) 126. For example, if data from the temperature sensor(s) 126 indicates that skin temperature is approaching the threshold defined by a selected thermal constraint, the thermal constraint manager 132 generates instructions to maintain or reduce the skin temperature by adjusting power consumption of the hardware component(s) and/or by operation of the fan(s) 114.
As illustrated in
The thermal constraint manager 132 includes a user presence detection analyzer 214. In this example, the user presence detection analyzer 214 provides means for analyzing the sensor data 200 generated by the user presence detection sensor(s) 118. In particular, the user presence detection analyzer 214 analyzes the sensor data 200 to determine if a user is within the range of the user presence detection sensor(s) 118 and, thus, is near enough to the user device 102 to suggest that the user is about to use the user device 102. In some examples, the user presence detection analyzer 214 determines if the user is within a particular distance from the user device 102 (e.g., within 0.5 meters of the device 102, within 0.75 meters of the device 102). The user presence detection analyzer 214 analyzes the sensor data 200 based on one or more user presence detection rule(s) 216. The user presence detection rule(s) 216 can be defined based on user input(s) and stored in the database 212.
The user presence detection rule(s) 216 can define, for instance, threshold time-of-flight (TOF) measurements by the user presence detection sensor(s) 118 that indicate presence of the user is within a range from the user presence detection sensor(s) 118 (e.g., measurements of the amount of time between emission of a wave pulse, reflection off a subject, and return to the sensor). In some examples, the user presence detection rule(s) 216 define threshold distance(s) for determining that a subject is within proximity of the user device 102. In such examples, the user presence detection analyzer 214 determines the distance(s) based on the TOF measurement(s) in the sensor data 200 and the known speed of the light emitted by the sensor(s) 118. In some examples, the user presence detection analyzer 214 identifies changes in the depth or distance values over time and detects whether the user is approaching the device 102 or moving away from the user device 102 based on the changes. The threshold TOF measurement(s) and/or distance(s) for the sensor data 200 can be based on the range of the sensor(s) 118 in emitting pulses. In some examples, the threshold TOF measurement(s) and/or distances are based on user-defined reference distances for determining that a user is near or approaching the user device 102 as compared to simply being in the environment in which the user device 102 and the user are both present.
The example thermal constraint manager 132 of
The device configuration analyzer 218 analyzes the sensor data 202 based on one or more device configuration rule(s) 219. The device configuration rule(s) 219 can be defined based on user input(s) and stored in the database 212. The device configuration rule(s) 219 can define, for example, identifiers for recognizing when external device(s) such as the headphones 112 of
The example thermal constraint manager 132 of
In the example of
In the example of
The example training manager 224 of
The example thermal constraint manager 132 of
The example thermal constraint manager 132 of
In the example of
The thermal constraint manager 132 of
The thermal constraint manager 132 of
The example thermal constraint manager 132 of
In some examples, the sensor activation rule(s) 250 define rule(s) for activating the sensor(s) to conserve power consumption by the device 102. For example, the sensor activation rule(s) 250 can define that the user presence detection sensor(s) 118 should remain active while the device 102 is operative (e.g., in a working power state) and that the image sensor(s) 122 should be activated when the user presence detection analyzer 214 determines that a user is within the range of the user presence detection sensor(s) 118. Such a rule can prevent unnecessary power consumption by the device 102 when, for instance, the user is not proximate to the device 102. In other examples, the sensor manager 248 selectively activates the image sensor(s) 122 to supplement data generated by the motion sensor(s) 123 to increase an accuracy with which the gesture(s) of the user are detected. In some examples, the sensor manager 248 deactivates the image sensor(s) 122 if the image data analyzer 220 does not predict a likelihood of a user interaction with the device and/or the device 102 does not receive a user input within a time threshold defined by the timer 244 to conserve power.
The example thermal constraint manager 132 of
For example, the thermal constraint selection rule(s) 254 can include a first rule that if the device configuration analyzer 218 determines that the user is providing input(s) via a keyboard or touch screen of the device 102, a first, or default thermal constraint for the temperature of the skin of the housing device 102 should be assigned to the user device 102 to prevent discomfort to the user when touching the device 102. The default thermal constraint for the skin temperature can be for, for example, 45° C. The thermal constraint selection rule(s) 254 can include a second rule that if the device configuration analyzer 218 determines that the user is providing input(s) via the external keyboard 108, a second thermal constraint should be assigned to the device 102, where the second thermal constraint provides for an increased skin temperature of the device as compared to the first (e.g., default) thermal constraint. For example, the second thermal constraint can define a skin temperature limit of 48° C.
The example thermal constraint manager 132 of
For example, the fan acoustic constraint selection rule(s) 260 can include a first or default rule for the fan noise level based on data from the user presence detection analyzer 214 indicating that the user is within a first range of the user presence detection sensor(s) 118 (e.g., 0.5 meters from the device 102). The first rule can define a sound pressure level corresponding to 35 dBA for noise generated by the fan(s). The fan acoustic constraint selection rule(s) 260 can include a second rule for the fan noise level based on data from the user presence detection analyzer 214 indicating that the user is within a second range of the user presence detection sensor(s) 118 (e.g., 1 meter from the device 102), where the second rule defines a sound pressure level corresponding to a sound pressure level (e.g., 41 dBA) for noise generated by the fan(s) 114 that is greater than the sound pressure level defined by the first rule. The fan acoustic constraint selection rule(s) 260 can include a third rule for the fan noise level based on data from the image data analyzer 220 indicating that the user is turned away from the user device 102. The third rule can define a fan speed and, thus, acoustic noise level, that is increased relative to the fan speed and associated acoustic noise defined by the first or default fan acoustic rule in view of the determination that the user is not interacting or not likely interacting with the device 102. The fan acoustic constraint selection rule(s) 260 can include a fourth rule indicating that if the device configuration analyzer 218 determines that an angle of a display screen of the device 102 is within a particular angle range relative to, for instance, a base of a laptop, the user is sitting when interacting with the device 102 and, thus, located closer to the device than if the user is standing. In such examples, the fourth rule can define a reduced fan acoustic noise level as compared to if the user is standing or located farther from the device 102.
The fan acoustic constraint selection rule(s) 260 can include a fifth rule indicating that if the device configuration analyzer 218 that headphones are coupled to the device 102 and/or the image data analyzer 220 determine that the user is wearing headphones, the fan acoustic noise can be increased relative to the default fan noise level. The fan acoustic constraint selection rule(s) 260 can include a fifth rule indicating that if the ambient noise analyzer 234 determines that the fan noise exceeds an ambient noise threshold, the fan acoustic noise can be increased relative to the default fan noise level. The fan acoustic constraint selection rule(s) 260 can include a sixth rule indicating that if the device configuration analyzer 218, the image data analyzer 220, and/or the motion data analyzer 222 do not detect a user input and/or a predict a likelihood of a user interaction with the device 102 within the time interval threshold(s) 246 as monitored by the timer 244, the fan acoustic noise should be increased because the user is not likely interacting with the device 102.
In the example of
The thermal constraint manager 132 of
The example thermal constraint manager 132 of
In some examples, the fan acoustic constraint selector 258 selects a fan acoustic constraint associated with increased fan acoustic noise when the user presence detection analyzer 214 does not detect the presence of a user within the range of the user presence detection sensor(s) 118 or when the user presence detection analyzer 214 determines that the user is a predefined distance from the device 102 to facilitate heatsink and fan shroud cleaning of heatsink(s) and fan shroud(s) of the device 102 (e.g., to remove accumulated dust). Because heatsink and fan shroud cleaning can increase acoustic generated by the fan(s) 114 when rotation of the fan(s) 114 are reversed to perform the cleaning, the fan acoustic constraint selector 258 can select a fan acoustic constraint for the device 102 and communicate with the fan speed manager 240 to perform the cleaning when user(s) are not proximate to the device 102. In such examples, the acoustic noise of the fan(s) 114 can be increased without disrupting a user interacting with the device 102 and longevity of the device performance can be increased though periodic cleanings.
The example thermal constraint selector 252 of
In some examples, the thermal constraint selector 252 and/or the fan acoustic constraint selector 258 selectively adjust the constraint(s) applied to the device 102 based on temperature data generated by the temperature sensor(s) 126 during operation of the device. For example, if increased power is provided to the hardware component(s) of the device 102 in response to selection of a thermal constraint the permits increased skin temperature of the housing of the device 102, the fan speed manager 240 can instruct the fan(s) 114 to increase rotational speed to prevent the skin temperature from exceeding the selected thermal constraint based on data from the temperature sensor(s) 126.
Although the example thermal constraint manager 132 of
While an example manner of implementing the thermal constraint manager 132 of
While an example manner of implementing the training manager 224 is illustrated in
A flowchart representative of example hardware logic, machine readable instructions, hardware implemented state machines, and/or any combination thereof for implementing the example training manager 224 of
The example instructions of
The example trainer 226 of
The example trainer 226 of
The example trainer 226 of
The example trainer 226 can continue to train the thermal constraint manager 132 using different datasets and/or datasets having different levels of specificity (block 606). For example, the trainer 226 can generate a first gesture data model 223 to determine if the user is interacting with the keyboard 104 of the user device 102, 400 and a second gesture data model 223 to determine if the user is interacting with the pointing device(s) 106 of the user device 102, 400. The example instructions end when there is no additional training to be performed (e.g., based on user input(s)) (block 608).
The example instructions of
A flowchart representative of example hardware logic, machine readable instructions, hardware implemented state machines, and/or any combination thereof for implementing the thermal constraint manager 132 of
In the example instructions of
The example user presence detection analyzer 214 determines whether the user is within a threshold distance of the user device 102 (block 700). For example, the user presence detection analyzer 214 detects a user is approaching the user device 102, 400 based on data generated by the user presence detection sensor(s) 118 (e.g., TOF data, etc.) indicating that the user is within the range of the user presence detection sensor(s) 118. In some examples, the user presence detection analyzer 214 determines if the user is within a predefined distance of the device 102 (e.g., within 1 meter, within 0.5 meters, etc.).
In the example of
At block 704, the device configuration analyzer 218 determines whether the user input(s) are received via external user input device(s) or on-board input device(s). For example, the device configuration analyzer 218 detects user input(s) via the external keyboard 108 and/or the external pointing device(s) 110 or via the on-board keyboard 104 and/or the on-board pointing device(s) 106.
If the device configuration analyzer 218 determines that the user input(s) are received via an external user input device, the thermal constraint selector 252 of the example thermal constraint manager 132 of
If the device configuration analyzer 218 determines that the user input(s) are being received by the device 102, 400 via on-board user input device(s) such as the on-board keyboard 104, the thermal constraint selector 252 of the example thermal constraint manager 132 of
In some examples, in view of the thermal constraint(s) assigned to the device 102, 400 at blocks 706, 708, the temperature analyzer 236 monitors the temperature of the hardware component(s) of the user device 102 based on the data generated by the temperature sensor(s) 126 and the fan speed manager 240 controls operation of the fan(s) 114 (e.g., increase fan level to exhaust hot air to cool the user device 102) to prevent the skin temperature from exceeding the selected thermal constraint at blocks 706 and/or 708.
Control proceeds to block 718 from blocks 706, 708. At block 718, the device configuration analyzer 218 determines whether the user who is interacting with the device 102, 400 is wearing headphones 112. For example, the device configuration analyzer 218 detects whether headphones 112 are coupled with the user device 102 (e.g., via wired or wireless connection(s)) and audio output(s) are being provided via the device 102, 400. In some examples, the image data analyzer 220 determines whether the user is wearing headphones 112 based on image data generated by the image sensor(s) 122. If the device configuration analyzer 218 and/or the image data analyzer 220 determine the user is wearing headphones 112, the fan constraint selector 258 selects a fan acoustic constraint that permits the fan(s) 114 to rotate at increased speeds and, thus, generate more noise (e.g., 36 dBA) in view of the use of headphones 112 by the user and the fan speed manager 240 instructs the fan(s) to increase rotational speed(s) (block 720). If the device configuration analyzer 218 and/or the image data analyzer 220 determine the user is not wearing headphones, control proceeds to block 724.
At block 724, the ambient noise analyzer 234 analyzes microphone data generated by the microphone(s) 124 to determine an ambient noise level for an environment in which the user device 102, 400 is located. The ambient noise analyzer 234 determines whether the ambient noise level exceeds a threshold (e.g., based on the ambient noise rule(s) 235) (block 726). If the ambient noise level exceeds the threshold, the fan constraint selector 258 selects a fan acoustic constraint that permits the fan(s) 114 to rotate at increased speeds and, thus, generate more noise in view of the noisy surrounding environment and the fan speed manager 240 instructs the fan(s) to increase rotational speed(s) (block 728). If the ambient noise level does not exceed the threshold, the fan acoustic constraint selector 258 selects a default fan acoustic constraint (e.g., based on the fan acoustic constraint selection rule(s) 260) for the fan(s) 114 and the fan speed manager 240 of the example thermal constraint manager 132 of
In the examples of
For example, the image data analyzer 220 analyzes image data generated by the image sensor(s) 122 to detect, for instance, a user's posture and/or eye gaze direction. Additionally or alternatively, the motion data analyzer 222 can analyze gesture data generated by the motion sensor(s) 123 to determine user gesture(s) (e.g., raising an arm, reaching a hand away from the user's body). In the example of
If the image data analyzer 220 and/or the motion data analyzer 222 determines the user is not likely to interact with the user device 102 within the threshold time, the fan constraint selector 258 selects a fan acoustic constraint that permits the fan(s) 114 to rotate at increased speeds and, thus, generate more noise to more efficiently cool the device 102, 400 (e.g., while the device 102, 400 is in a working power state) and/or to clean the fan(s) 114 (block 716). Also, if the user presence detection analyzer 214 does not detect the presence of a user within the range of sensor(s) 118 (block 700), the fan constraint selector 258 selects a fan acoustic constraint that permits the fan(s) 114 to rotate at increased speeds and, thus, generate more noise to more efficiently cool the device 102, 400 (e.g., while the device 102, 400 is in a working power state) and/or to clean the fan(s) 114. Control proceeds to block 722.
At block 722, one or more of the user presence detection analyzer 214, the device configuration analyzer 218, the image data analyzer 220, and/or the motion data analyzer 222 determines whether there is a change in user interaction with the user device 102 and/or a change in a likelihood that the user will interact with the user device 102 (block 722). For example, the user presence detection analyzer 214 can detect whether a user is no longer present based on the data generated by the user presence detection sensor(s) 118. In some other examples, the motion data analyzer 222 detects a user is reaching for the pointing device(s) 106 based on the data generated by the motion sensor(s) 123 and the gesture data model(s) 223 after a period of time in which the user was not interacting with the device 102, 400. If the one or more of the user presence detection analyzer 214, the device configuration analyzer 218, the image data analyzer 220, and/or the motion data analyzer 222 detect a change in user interaction with the user device 102 and/or a change in a likelihood of a user interaction with the user device 102, control returns to block 710 to analyzer user behavior relative to the device 102. If no change in user interaction with the device 102 and/or likelihood of user interaction is detected, control proceeds to block 734.
The example instructions of
The machine readable instructions described herein in connection with
In another example, the machine readable instructions may be stored in a state in which they may be read by a computer, but require addition of a library (e.g., a dynamic link library (DLL)), a software development kit (SDK), an application programming interface (API), etc. in order to execute the instructions on a particular computing device or other device. In another example, the machine readable instructions may need to be configured (e.g., settings stored, data input, network addresses recorded, etc.) before the machine readable instructions and/or the corresponding program(s) can be executed in whole or in part. Thus, the disclosed machine readable instructions and/or corresponding program(s) are intended to encompass such machine readable instructions and/or program(s) regardless of the particular format or state of the machine readable instructions and/or program(s) when stored or otherwise at rest or in transit.
The machine readable instructions described herein can be represented by any past, present, or future instruction language, scripting language, programming language, etc. For example, the machine readable instructions may be represented using any of the following languages: C, C++, Java, C#, Perl, Python, JavaScript, HyperText Markup Language (HTML), Structured Query Language (SQL), Swift, etc.
As mentioned above, the example processes of
“Including” and “comprising” (and all forms and tenses thereof) are used herein to be open ended terms. Thus, whenever a claim employs any form of “include” or “comprise” (e.g., comprises, includes, comprising, including, having, etc.) as a preamble or within a claim recitation of any kind, it is to be understood that additional elements, terms, etc. may be present without falling outside the scope of the corresponding claim or recitation. As used herein, when the phrase “at least” is used as the transition term in, for example, a preamble of a claim, it is open-ended in the same manner as the term “comprising” and “including” are open ended. The term “and/or” when used, for example, in a form such as A, B, and/or C refers to any combination or subset of A, B, C such as (1) A alone, (2) B alone, (3) C alone, (4) A with B, (5) A with C, (6) B with C, and (7) A with B and with C. As used herein in the context of describing structures, components, items, objects and/or things, the phrase “at least one of A and B” is intended to refer to implementations including any of (1) at least one A, (2) at least one B, and (3) at least one A and at least one B. Similarly, as used herein in the context of describing structures, components, items, objects and/or things, the phrase “at least one of A or B” is intended to refer to implementations including any of (1) at least one A, (2) at least one B, and (3) at least one A and at least one B. As used herein in the context of describing the performance or execution of processes, instructions, actions, activities and/or steps, the phrase “at least one of A and B” is intended to refer to implementations including any of (1) at least one A, (2) at least one B, and (3) at least one A and at least one B. Similarly, as used herein in the context of describing the performance or execution of processes, instructions, actions, activities and/or steps, the phrase “at least one of A or B” is intended to refer to implementations including any of (1) at least one A, (2) at least one B, and (3) at least one A and at least one B.
As used herein, singular references (e.g., “a”, “an”, “first”, “second”, etc.) do not exclude a plurality. The term “a” or “an” entity, as used herein, refers to one or more of that entity. The terms “a” (or “an”), “one or more”, and “at least one” can be used interchangeably herein. Furthermore, although individually listed, a plurality of means, elements or method actions may be implemented by, e.g., a single unit or processor. Additionally, although individual features may be included in different examples or claims, these may possibly be combined, and the inclusion in different examples or claims does not imply that a combination of features is not feasible and/or advantageous.
The processor platform 800 of the illustrated example includes a processor 224. The processor 224 of the illustrated example is hardware. For example, the processor 224 can be implemented by one or more integrated circuits, logic circuits, microprocessors, GPUs, DSPs, or controllers from any desired family or manufacturer. The hardware processor may be a semiconductor based (e.g., silicon based) device. In this example, the processor implements the example trainer 226 and the example machine learning engine 228.
The processor 224 of the illustrated example includes a local memory 813 (e.g., a cache). The processor 224 of the illustrated example is in communication with a main memory including a volatile memory 814 and a non-volatile memory 816 via a bus 818. The volatile memory 814 may be implemented by Synchronous Dynamic Random Access Memory (SDRAM), Dynamic Random Access Memory (DRAM), RAMBUS® Dynamic Random Access Memory (RDRAM®) and/or any other type of random access memory device. The non-volatile memory 816 may be implemented by flash memory and/or any other desired type of memory device. Access to the main memory 814, 816 is controlled by a memory controller.
The processor platform 800 of the illustrated example also includes an interface circuit 820. The interface circuit 820 may be implemented by any type of interface standard, such as an Ethernet interface, a universal serial bus (USB), a Bluetooth® interface, a near field communication (NFC) interface, and/or a PCI express interface.
In the illustrated example, one or more input devices 822 are connected to the interface circuit 820. The input device(s) 822 permit(s) a user to enter data and/or commands into the processor 224. The input device(s) can be implemented by, for example, an audio sensor, a microphone, a camera (still or video), a keyboard, a button, a mouse, a touchscreen, a track-pad, a trackball, isopoint and/or a voice recognition system.
One or more output devices 824 are also connected to the interface circuit 820 of the illustrated example. The output devices 824 can be implemented, for example, by display devices (e.g., a light emitting diode (LED), an organic light emitting diode (OLED), a liquid crystal display (LCD), a cathode ray tube display (CRT), an in-place switching (IPS) display, a touchscreen, etc.), a tactile output device, a printer and/or speaker. The interface circuit 820 of the illustrated example, thus, typically includes a graphics driver card, a graphics driver chip and/or a graphics driver processor.
The interface circuit 820 of the illustrated example also includes a communication device such as a transmitter, a receiver, a transceiver, a modem, a residential gateway, a wireless access point, and/or a network interface to facilitate exchange of data with external machines (e.g., computing devices of any kind) via a network 826. The communication can be via, for example, an Ethernet connection, a digital subscriber line (DSL) connection, a telephone line connection, a coaxial cable system, a satellite system, a line-of-site wireless system, a cellular telephone system, etc.
The processor platform 800 of the illustrated example also includes one or more mass storage devices 828 for storing software and/or data. Examples of such mass storage devices 828 include floppy disk drives, hard drive disks, compact disk drives, Blu-ray disk drives, redundant array of independent disks (RAID) systems, and digital versatile disk (DVD) drives.
The machine executable instructions 832 of
The processor platform 900 of the illustrated example includes a processor 132. The processor 132 of the illustrated example is hardware. For example, the processor 132 can be implemented by one or more integrated circuits, logic circuits, microprocessors, GPUs, DSPs, or controllers from any desired family or manufacturer. The hardware processor may be a semiconductor based (e.g., silicon based) device. In this example, the processor implements the example user presence detection analyzer 214, the example device configuration analyzer 218, the example image data analyzer 220, the example motion data analyzer 222, the example ambient noise analyzer 234, the example temperature analyzer 236, the example power source manager 238, the example fan speed manager 240, the example timer 244, the example sensor manager 248, the example thermal constraint selector 252, and the example fan acoustic constraint selector 258.
The processor 132 of the illustrated example includes a local memory 913 (e.g., a cache). The processor 132 of the illustrated example is in communication with a main memory including a volatile memory 914 and a non-volatile memory 916 via a bus 918. The volatile memory 914 may be implemented by Synchronous Dynamic Random Access Memory (SDRAM), Dynamic Random Access Memory (DRAM), RAMBUS® Dynamic Random Access Memory (RDRAM®) and/or any other type of random access memory device. The non-volatile memory 916 may be implemented by flash memory and/or any other desired type of memory device. Access to the main memory 914, 916 is controlled by a memory controller.
The processor platform 900 of the illustrated example also includes an interface circuit 920. The interface circuit 920 may be implemented by any type of interface standard, such as an Ethernet interface, a universal serial bus (USB), a Bluetooth® interface, a near field communication (NFC) interface, and/or a PCI express interface.
In the illustrated example, one or more input devices 922 are connected to the interface circuit 920. The input device(s) 922 permit(s) a user to enter data and/or commands into the processor 132. The input device(s) can be implemented by, for example, an audio sensor, a microphone, a camera (still or video), a keyboard, a button, a mouse, a touchscreen, a track-pad, a trackball, isopoint and/or a voice recognition system.
One or more output devices 924 are also connected to the interface circuit 920 of the illustrated example. The output devices 924 can be implemented, for example, by display devices (e.g., a light emitting diode (LED), an organic light emitting diode (OLED), a liquid crystal display (LCD), a cathode ray tube display (CRT), an in-place switching (IPS) display, a touchscreen, etc.), a tactile output device, a printer and/or speaker. The interface circuit 920 of the illustrated example, thus, typically includes a graphics driver card, a graphics driver chip and/or a graphics driver processor.
The interface circuit 920 of the illustrated example also includes a communication device such as a transmitter, a receiver, a transceiver, a modem, a residential gateway, a wireless access point, and/or a network interface to facilitate exchange of data with external machines (e.g., computing devices of any kind) via a network 926. The communication can be via, for example, an Ethernet connection, a digital subscriber line (DSL) connection, a telephone line connection, a coaxial cable system, a satellite system, a line-of-site wireless system, a cellular telephone system, etc.
The processor platform 900 of the illustrated example also includes one or more mass storage devices 928 for storing software and/or data. Examples of such mass storage devices 928 include floppy disk drives, hard drive disks, compact disk drives, Blu-ray disk drives, redundant array of independent disks (RAID) systems, and digital versatile disk (DVD) drives.
The machine executable instructions 932 of
From the foregoing, it will be appreciated that example methods, apparatus and articles of manufacture have been disclosed that provide for dynamic control of thermal constraints and/or fan acoustic constraints of an electronic user device (e.g., a laptop, a tablet). Examples disclosed herein analyze sensor data indicative of, for instance, user interaction(s) with the device, other user activities (e.g., talking on a phone), and ambient noise to determine if a temperature of a skin of the device can be increased and/or if audible noises associated with rotation of the fan(s) of the device can be increased. Examples disclosed herein detect opportunities for increased skin temperature (e.g., when a user is interacting with the device via an external keyboard) and/or increased fan noise (e.g., when a user is located a threshold distance from the device or in a noisy environment). By permitting the skin temperature of the device to increase, example disclosed herein enable increased power to be provided to the hardware component(s) of the device and, thus, can improve performance (e.g., processing performance) of the device. By allowing the fan(s) to rotate at increased speed(s) and, thus, generate more noise, examples disclosed herein provide for efficient cooling of the device. The disclosed methods, apparatus and articles of manufacture improve the efficiency of using a computing device by selectively managing thermal constraint(s) for the device to optimize device performance and cooling in view user interactions with the device and/or ambient conditions. The disclosed methods, apparatus and articles of manufacture are accordingly directed to one or more improvement(s) in the functioning of a computer.
Example methods, apparatus, systems, and articles of manufacture to implement thermal management of electronic user devices are disclosed herein. Further examples and combinations thereof include the following:
Example 1 includes an electronic device including a housing, a fan, a first sensor, a second sensor, and a processor to at least one of analyze first sensor data generated by the first sensor to detect a presence of a subject proximate to the electronic device or analyze second sensor data generated by the second sensor to detect a gesture of the subject, and adjust one or more of an acoustic noise level generated the fan or a temperature of an exterior surface of the housing based on one or more of the presence of the subject or the gesture.
Example 2 includes the electronic device of example 1, wherein the second sensor includes a camera.
Example 3 includes the electronic device of examples 1 or 2, wherein the processor is to adjust the acoustic noise level by generating an instruction to increase a rotational speed of the fan.
Example 4 includes the electronic device of any of examples 1-3, wherein the processor is to adjust the temperature of the exterior surface of the device by controlling a power source of the device.
Example 5 includes the electronic device of any of examples 1-4, further including a microphone, the processor to analyze third sensor data generated by the microphone to detect ambient noise in an environment including the device, and adjust the acoustic noise level of the fan based on the ambient noise.
Example 6 includes the electronic device of example 1, further including a keyboard carried by the housing, wherein the processor is to detect an input via the keyboard and adjust the temperature of the exterior surface of the housing based on the detection of the input.
Example 7 includes the electronic device of example 1, further including a keyboard external to the housing, wherein the processor is to detect an input via the keyboard and adjust the temperature of the exterior surface of the housing based on the detection of the input.
Example 8 includes the electronic device of example 1, wherein the processor is to adjust one the acoustic noise level to during cleaning of the fan and based on the distance of the user being within a threshold distance from the electronic device.
Example 9 includes an apparatus including a user presence detection analyzer, an image data analyzer, a motion data analyzer, at least one of (a) the user presence detection analyzer to identify a presence of a user relative to an electronic device based on first sensor data generated by a first sensor of the electronic device or (b) at least one of the image data analyzer or the motion data analyzer to determine a gesture of the user relative to the device based on second sensor data generated by a second sensor of the electronic device, a thermal constraint selector to select a thermal constraint for a temperature of an exterior surface of the electronic device based on one or more of the presence of the user or the gesture, and a power source manager to adjust a power level for a processor of the electronic device based on the thermal constraint.
Example 10 includes the apparatus of example 9, further including a device configuration analyzer to detect a presence of an external user input device communicatively coupled to the electronic device.
Example 11 includes the apparatus of example 10, wherein the external device is at least one of a keyboard, a pointing device, or headphones.
Example 12 includes the apparatus of example 9, wherein the second sensor data is image data and the image data analyzer is to determine the gesture based on a machine learning model.
Example 13 includes the apparatus of examples 9 or 12, wherein the second sensor data is image data and wherein the image data analyzer is to detect a position of an eye of the user relative to a display screen of the electronic device.
Example 14 includes the apparatus of example 9, further including a fan acoustic constraint selector to select a fan acoustic constraint for a noise level to be generated by a fan of the electronic device during operation of the fan.
Example 15 includes the apparatus of example 14, further including an ambient noise analyzer to determine an ambient noise level based on ambient noise data generated by a microphone of the electronic device, the fan acoustic constraint selector to select the fan acoustic constraint based on the ambient noise level.
Example 16 includes the apparatus of example 14, wherein the user presence detection sensor is further to determine a distance of the user from the electronic device, the fan acoustic constraint selector to select the fan acoustic constraint based on the distance.
Example 17 includes the apparatus of example 14, wherein the fan acoustic constraint selector is to select the fan acoustic constraint for the noise level to be generated by the fan during cleaning of the fan.
Example 18 includes the apparatus of example 14, wherein the image data analyzer is to detect that the user is wearing headphones based on image data generated by the second sensor, the fan acoustic constraint selector to select the fan acoustic constraint based on the ambient noise level based on the detection of the headphones.
Example 19 includes at least one non-transitory computer readable storage medium including instructions that, when executed, cause a machine to at least identify one or more of (a) a presence of a user relative to an electronic device based on first sensor data generated by a first sensor of the electronic device, (b) a facial feature of the user based on second sensor data generated by a second sensor of the electronic device, or (c) a gesture of the user based on the second sensor data, select a thermal constraint for a temperature of an exterior surface of the electronic device based on one or more of the presence of the user, the facial feature, or the gesture, and adjust a power level for a processor of the electronic device based on the thermal constraint.
Example 20 includes the at least one non-transitory computer readable storage medium of example 19, wherein the instructions, when executed, further cause the machine to detect a presence of an external user input device communicatively coupled to the electronic device.
Example 21 includes the at least one non-transitory computer readable storage medium of example 19, wherein the instructions, when executed, further cause the machine to identify the gesture based on a machine learning model.
Example 22 includes the at least one non-transitory computer readable storage medium of examples 19 or 21, wherein the facial feature includes an eye position and wherein the instructions, when executed, further cause the machine to detect a position of an eye of the user relative to a display screen of the electronic device.
Example 23 includes the at least one non-transitory computer readable storage medium of examples 19 or 20, wherein the instructions, when executed, further cause the machine to select a fan acoustic constraint for a noise level to be generated by a fan of the electronic device during operation of the fan.
Example 24 includes the at least one non-transitory computer readable storage medium of example 23, wherein the instructions, when executed, further cause the machine to determine an ambient noise level based on ambient noise data generated by a microphone of the electronic device, the fan acoustic constraint selector to select the fan acoustic constraint based on the ambient noise level.
Example 25 includes the at least one non-transitory computer readable storage medium of example 23, wherein the instructions, when executed, further cause the machine to detect that the user is wearing headphones based on image data generated by the second sensor, the fan acoustic constraint selector to select the fan acoustic constraint based on the detection of the headphones.
Example 26 includes the at least one non-transitory computer readable storage medium of example 23, wherein the instructions, when executed, further cause the machine to determine a distance of the user from the electronic device and select the fan acoustic constraint based on the distance.
Example 27 includes the at least one non-transitory computer readable storage medium of example 23, wherein the instructions, when executed, further cause the machine to select the fan acoustic constraint for the noise level to be generated by the fan during cleaning of the fan.
Example 28 includes a method including at least one of (a) identifying a presence of a user relative to an electronic device based on first sensor data generated by a first sensor of the electronic device, (b) identifying a facial feature of the user based on second sensor data generated by a second sensor of the electronic device, or (c) identifying a gesture of the user based on the second sensor data, selecting a thermal constraint for a temperature of an exterior surface of the electronic device based on one or more of the presence of the user, the facial feature, or the gesture, and adjusting a power level for a processor of the electronic device based on the thermal constraint.
Example 29 includes the method of example 28, further including detecting a presence of an external user input device communicatively coupled to the electronic device.
Example 30 includes the method of example 28, further including determining the one or more of the facial feature or the gesture based on a machine learning model.
Example 31 includes the method of examples 28 or 30, wherein the facial feature includes eye position and further including detecting a position of an eye of the user relative to a display screen of the electronic device.
Example 32 includes the method of examples 28 or 29, further including selecting a fan acoustic constraint for a noise level to be generated by a fan of the electronic device.
Example 33 includes the method of example 32, further including determining an ambient noise level based on ambient noise data generated by a microphone of the electronic device, the fan acoustic constraint selector to select the fan acoustic constraint based on the ambient noise level.
Example 34 includes the method of example 32, further including detecting detect that the user is wearing headphones based on image data generated by the second sensor, the fan acoustic constraint selector to select the fan acoustic constraint based on the detection of the headphones.
Example 35 includes the method of example 32, further including determining a distance of the user from the electronic device and selecting the fan acoustic constraint based on the distance.
Example 36 includes the method of example 32, further including selecting the fan acoustic constraint for the noise level to be generated by the fan during cleaning of the fan.
Although certain example methods, apparatus and articles of manufacture have been disclosed herein, the scope of coverage of this patent is not limited thereto. On the contrary, this patent covers all methods, apparatus and articles of manufacture fairly falling within the scope of the claims of this patent.
The following claims are hereby incorporated into this Detailed Description by this reference, with each claim standing on its own as a separate embodiment of the present disclosure.
This patent arises from a continuation of U.S. patent application Ser. No. 16/728,774 (now U.S. Pat. No. 11,360,528), which was filed on Dec. 27, 2019. U.S. patent application Ser. No. 16/728,774 is hereby incorporated herein by reference in its entirety. Priority to U.S. patent application Ser. No. 16/728,774 is hereby claimed.
Number | Name | Date | Kind |
---|---|---|---|
D324036 | Wakasa | Feb 1992 | S |
5173940 | Lantz et al. | Dec 1992 | A |
D359275 | Yamazaki | Jun 1995 | S |
D376791 | Schreiner | Dec 1996 | S |
D388774 | Guintoli | Jan 1998 | S |
D389129 | Guintoli | Jan 1998 | S |
5835083 | Nielsen et al. | Nov 1998 | A |
D433024 | Oross | Oct 2000 | S |
D434773 | Suzuki | Dec 2000 | S |
D444462 | Tsuji | Jul 2001 | S |
D449307 | Amano | Oct 2001 | S |
D453508 | Shibata | Feb 2002 | S |
D454126 | Bliven et al. | Mar 2002 | S |
D462967 | Suzuki | Sep 2002 | S |
6591198 | Pratt | Jul 2003 | B1 |
D478089 | Yokota | Aug 2003 | S |
D480089 | Skinner et al. | Sep 2003 | S |
6657647 | Bright | Dec 2003 | B1 |
6760649 | Cohen | Jul 2004 | B2 |
D494161 | Sawaquchi | Aug 2004 | S |
D504129 | Loew et al. | Apr 2005 | S |
D517542 | Lee et al. | Mar 2006 | S |
D518042 | Kanayama | Mar 2006 | S |
D534531 | Ogasawara | Jan 2007 | S |
7386799 | Clanton et al. | Jun 2008 | B1 |
D577013 | Harris | Sep 2008 | S |
D591737 | Morooka | May 2009 | S |
7559034 | Paperny et al. | Jul 2009 | B1 |
D607449 | Morisawa | Jan 2010 | S |
D608380 | Nagase et al. | Jan 2010 | S |
D611043 | Andre et al. | Mar 2010 | S |
D611045 | Andre et al. | Mar 2010 | S |
D612830 | Kim et al. | Mar 2010 | S |
D614180 | Gou | Apr 2010 | S |
D616433 | Morishita et al. | May 2010 | S |
7725547 | Albertson et al. | May 2010 | B2 |
D616882 | Denhez | Jun 2010 | S |
D631039 | Sakai et al. | Jan 2011 | S |
7971156 | Albertson et al. | Jun 2011 | B2 |
7974743 | Nakashima et al. | Jul 2011 | B2 |
D645857 | Cho et al. | Sep 2011 | S |
8139032 | Su et al. | Mar 2012 | B2 |
D659134 | Ahn et al. | May 2012 | S |
D672765 | Masui | Dec 2012 | S |
D673558 | Cruz et al. | Jan 2013 | S |
D674382 | Andre et al. | Jan 2013 | S |
D684570 | Akana et al. | Jun 2013 | S |
D687831 | Kim | Aug 2013 | S |
8566696 | Hamon et al. | Oct 2013 | B1 |
D692875 | Lawrence | Nov 2013 | S |
8581974 | Lin et al. | Nov 2013 | B2 |
D698348 | Ilchan et al. | Jan 2014 | S |
D704185 | Bowers et al. | May 2014 | S |
8717318 | Anderson et al. | May 2014 | B2 |
D706767 | Kawai et al. | Jun 2014 | S |
D706768 | Kawai | Jun 2014 | S |
D706769 | Kawai et al. | Jun 2014 | S |
D706772 | Koyama et al. | Jun 2014 | S |
D708178 | Honda et al. | Jul 2014 | S |
D708179 | Andre et al. | Jul 2014 | S |
D709491 | Kurimoto et al. | Jul 2014 | S |
8812831 | Cheng et al. | Aug 2014 | B2 |
D712971 | Huang | Sep 2014 | S |
D715793 | Tsao et al. | Oct 2014 | S |
D716795 | Huang et al. | Nov 2014 | S |
D718818 | Sumii et al. | Dec 2014 | S |
D720712 | Park et al. | Jan 2015 | S |
8954884 | Barger | Feb 2015 | B1 |
D724576 | Wolff et al. | Mar 2015 | S |
8994847 | Chen et al. | Mar 2015 | B2 |
D727314 | Fukuoka | Apr 2015 | S |
D729227 | Fukuoka | May 2015 | S |
D729228 | Kawai | May 2015 | S |
D729229 | Kurimoto et al. | May 2015 | S |
D729791 | Adamson et al. | May 2015 | S |
D729792 | Kurimoto et al. | May 2015 | S |
D731475 | Mehandjiysky et al. | Jun 2015 | S |
D739398 | Adamson et al. | Sep 2015 | S |
D739399 | Adamson et al. | Sep 2015 | S |
D739400 | Adamson et al. | Sep 2015 | S |
D740278 | Bowers et al. | Oct 2015 | S |
D741318 | Oakley | Oct 2015 | S |
9183845 | Gopalakrishnan et al. | Nov 2015 | B1 |
D746809 | Takada et al. | Jan 2016 | S |
9268434 | Sultenfuss | Feb 2016 | B2 |
D751062 | Chang | Mar 2016 | S |
9311909 | Giaimo, III et al. | Apr 2016 | B2 |
9436241 | Tang et al. | Sep 2016 | B2 |
D769251 | Chen | Oct 2016 | S |
D771684 | Kim | Nov 2016 | S |
D780173 | Matsuoka | Feb 2017 | S |
9575559 | Andrysco | Feb 2017 | B2 |
D780760 | Ironmonger et al. | Mar 2017 | S |
D788767 | Magi | Jun 2017 | S |
D794027 | Ironmonger et al. | Aug 2017 | S |
9721383 | Horowitz et al. | Aug 2017 | B1 |
9740290 | Rosenberg et al. | Aug 2017 | B2 |
9766700 | Lyons et al. | Sep 2017 | B2 |
9785234 | Horesh | Oct 2017 | B2 |
D801945 | Cho et al. | Nov 2017 | S |
D803946 | Matsuda | Nov 2017 | S |
9846471 | Arora | Dec 2017 | B1 |
D810069 | Hishiki | Feb 2018 | S |
D810071 | Hishiki | Feb 2018 | S |
D813235 | Rosenberg et al. | Mar 2018 | S |
D814469 | Rundberg | Apr 2018 | S |
D816083 | Wu | Apr 2018 | S |
9936195 | Horesh | Apr 2018 | B2 |
9996638 | Holz et al. | Jun 2018 | B1 |
D823850 | Lim et al. | Jul 2018 | S |
10027662 | Mutagi et al. | Jul 2018 | B1 |
D825435 | Yu | Aug 2018 | S |
10101817 | Hsin et al. | Oct 2018 | B2 |
10234928 | Chen | Mar 2019 | B2 |
10254178 | Carbone et al. | Apr 2019 | B2 |
10262599 | Lang et al. | Apr 2019 | B2 |
10304209 | Alonso | May 2019 | B2 |
10415286 | Porcella et al. | Sep 2019 | B1 |
D867460 | Yan et al. | Nov 2019 | S |
D873835 | Chan | Jan 2020 | S |
10551888 | North et al. | Feb 2020 | B1 |
D878475 | Jetter | Mar 2020 | S |
D879777 | Cho | Mar 2020 | S |
10620457 | Ain-Kedem | Apr 2020 | B2 |
10620786 | Veeramani et al. | Apr 2020 | B2 |
D886112 | Yeh et al. | Jun 2020 | S |
10725510 | Ho et al. | Jul 2020 | B2 |
10740912 | Ren et al. | Aug 2020 | B2 |
10768724 | Han | Sep 2020 | B1 |
10819920 | Hamlin et al. | Oct 2020 | B1 |
10884479 | Chen | Jan 2021 | B2 |
D914010 | Yeh et al. | Mar 2021 | S |
D914021 | Magi et al. | Mar 2021 | S |
D916076 | Seoc et al. | Apr 2021 | S |
D916078 | Akana et al. | Apr 2021 | S |
11153472 | Konicek | Oct 2021 | B2 |
D934856 | Yeh et al. | Nov 2021 | S |
11194398 | Bernhart | Dec 2021 | B2 |
11360528 | Mishra et al. | Jun 2022 | B2 |
11379016 | Cooper et al. | Jul 2022 | B2 |
11543873 | Sengupta et al. | Jan 2023 | B2 |
D982575 | Bae et al. | Apr 2023 | S |
11733761 | Sinah et al. | Aug 2023 | B2 |
20020089190 | Wang et al. | Jul 2002 | A1 |
20020091738 | Rohrabaugh et al. | Jul 2002 | A1 |
20030043174 | Hinckley et al. | Mar 2003 | A1 |
20030174149 | Fujisaki et al. | Sep 2003 | A1 |
20040120113 | Rapaich | Jun 2004 | A1 |
20040158739 | Wakai et al. | Aug 2004 | A1 |
20040175020 | Bradski et al. | Sep 2004 | A1 |
20040252101 | Wilk | Dec 2004 | A1 |
20050071698 | Kangas | Mar 2005 | A1 |
20050094823 | Kobori et al. | May 2005 | A1 |
20060146030 | Kim | Jul 2006 | A1 |
20060192775 | Nicholson | Aug 2006 | A1 |
20070027580 | Ligtenberg | Feb 2007 | A1 |
20070228138 | Huang et al. | Oct 2007 | A1 |
20080046425 | Perski | Feb 2008 | A1 |
20080112571 | Bradicich et al. | May 2008 | A1 |
20080158144 | Schobben et al. | Jul 2008 | A1 |
20080301300 | Toub | Dec 2008 | A1 |
20090092261 | Bard | Apr 2009 | A1 |
20090092262 | Costa et al. | Apr 2009 | A1 |
20090092293 | Lin | Apr 2009 | A1 |
20090165125 | Brown et al. | Jun 2009 | A1 |
20100039376 | Wang | Feb 2010 | A1 |
20100079508 | Hodge et al. | Apr 2010 | A1 |
20100100716 | Scott et al. | Apr 2010 | A1 |
20100281432 | Geisner et al. | Nov 2010 | A1 |
20100295839 | Nagaya et al. | Nov 2010 | A1 |
20110035606 | Lovicott | Feb 2011 | A1 |
20110055752 | Rubinstein et al. | Mar 2011 | A1 |
20110154266 | Friend et al. | Jun 2011 | A1 |
20110175932 | Yu et al. | Jul 2011 | A1 |
20110298702 | Sakata et al. | Aug 2011 | A1 |
20110248918 | Yoo et al. | Oct 2011 | A1 |
20110251733 | Atkinson et al. | Oct 2011 | A1 |
20110252339 | Lemonik et al. | Oct 2011 | A1 |
20110273546 | Lin et al. | Nov 2011 | A1 |
20110296163 | Abernethy et al. | Dec 2011 | A1 |
20110298967 | Clavin et al. | Dec 2011 | A1 |
20120032894 | Parivar et al. | Feb 2012 | A1 |
20120054670 | Rainisto | Mar 2012 | A1 |
20120062470 | Chang | Mar 2012 | A1 |
20120123680 | Wipplinger et al. | May 2012 | A1 |
20120171656 | Shen | Jul 2012 | A1 |
20120172085 | Vuppu et al. | Jul 2012 | A1 |
20120249429 | Anderson et al. | Oct 2012 | A1 |
20120268893 | Yin | Oct 2012 | A1 |
20120300061 | Osman et al. | Nov 2012 | A1 |
20120319997 | Majumder | Dec 2012 | A1 |
20130007096 | Pahlavan et al. | Jan 2013 | A1 |
20130007590 | Rivera et al. | Jan 2013 | A1 |
20130021265 | Selim | Jan 2013 | A1 |
20130021750 | Senatori | Jan 2013 | A1 |
20130080807 | Theocharous et al. | Mar 2013 | A1 |
20130120460 | Adams et al. | May 2013 | A1 |
20130158999 | Maruta et al. | Jun 2013 | A1 |
20130173946 | Rotem et al. | Jul 2013 | A1 |
20130174016 | Glazer et al. | Jul 2013 | A1 |
20130185633 | Bunker et al. | Jul 2013 | A1 |
20130207895 | Lee et al. | Aug 2013 | A1 |
20130212462 | Athas et al. | Aug 2013 | A1 |
20130222329 | Larsby et al. | Aug 2013 | A1 |
20130283213 | Guendelman et al. | Oct 2013 | A1 |
20130289792 | Cheng | Oct 2013 | A1 |
20130321265 | Bychkov et al. | Dec 2013 | A1 |
20130321271 | Bychkov et al. | Dec 2013 | A1 |
20130332760 | Reece et al. | Dec 2013 | A1 |
20140006830 | Kamhi et al. | Jan 2014 | A1 |
20140028548 | Bychkov et al. | Jan 2014 | A1 |
20140050360 | Lin et al. | Feb 2014 | A1 |
20140085451 | Kamimura et al. | Mar 2014 | A1 |
20140089865 | Gay et al. | Mar 2014 | A1 |
20140094973 | Giaimo, III et al. | Apr 2014 | A1 |
20140129937 | Jarvinen et al. | May 2014 | A1 |
20140132508 | Hodge et al. | May 2014 | A1 |
20140132514 | Kuzara et al. | May 2014 | A1 |
20140139456 | Wigdor et al. | May 2014 | A1 |
20140149935 | Johnson et al. | May 2014 | A1 |
20140189579 | Rimon et al. | Jul 2014 | A1 |
20140191995 | Karpin et al. | Jul 2014 | A1 |
20140201690 | Holz et al. | Jul 2014 | A1 |
20140208260 | Kawahara et al. | Jul 2014 | A1 |
20140258942 | Kutliroff et al. | Sep 2014 | A1 |
20140267021 | Lee et al. | Sep 2014 | A1 |
20140267034 | Krulce et al. | Sep 2014 | A1 |
20140281918 | Wei et al. | Sep 2014 | A1 |
20140313120 | Kamhi | Oct 2014 | A1 |
20140344599 | Branover et al. | Nov 2014 | A1 |
20140361977 | Stafford et al. | Dec 2014 | A1 |
20140372511 | Kapadia et al. | Dec 2014 | A1 |
20140380075 | Pulapaka et al. | Dec 2014 | A1 |
20150009238 | Kudalkar | Jan 2015 | A1 |
20150015688 | Yang | Jan 2015 | A1 |
20150042572 | Lombardi et al. | Feb 2015 | A1 |
20150058649 | Song et al. | Feb 2015 | A1 |
20150100884 | Ryu et al. | Apr 2015 | A1 |
20150121193 | Beveridge et al. | Apr 2015 | A1 |
20150121287 | Fermon | Apr 2015 | A1 |
20150177843 | Kwon | Jun 2015 | A1 |
20150185909 | Gecnuk | Jul 2015 | A1 |
20150193395 | Nicolaou et al. | Jul 2015 | A1 |
20150220149 | Plagemann et al. | Aug 2015 | A1 |
20150220150 | Plagemann et al. | Aug 2015 | A1 |
20150248167 | Turbell et al. | Sep 2015 | A1 |
20150264572 | Turgeman | Sep 2015 | A1 |
20150360567 | Sannomiya et al. | Dec 2015 | A1 |
20150363070 | Katz | Dec 2015 | A1 |
20150378443 | Luo | Dec 2015 | A1 |
20150378748 | Cheng et al. | Dec 2015 | A1 |
20160013745 | North et al. | Jan 2016 | A1 |
20160034019 | Seo et al. | Feb 2016 | A1 |
20160062584 | Cohen et al. | Mar 2016 | A1 |
20160087981 | Dorresteijn | Mar 2016 | A1 |
20160109961 | Parshionikar | Apr 2016 | A1 |
20160116960 | Kwak et al. | Apr 2016 | A1 |
20160091938 | Edwards et al. | May 2016 | A1 |
20160132099 | Grabau et al. | May 2016 | A1 |
20160170617 | Shi et al. | Jun 2016 | A1 |
20160179767 | Mavinakuli et al. | Jun 2016 | A1 |
20160180762 | Bathiche et al. | Jun 2016 | A1 |
20160187994 | La et al. | Jun 2016 | A1 |
20160202750 | Pulapaka et al. | Jul 2016 | A1 |
20160212317 | Alameh et al. | Jul 2016 | A1 |
20160232701 | Drozdyuk | Aug 2016 | A1 |
20160259467 | Nayyar et al. | Sep 2016 | A1 |
20160297362 | Tijerina et al. | Oct 2016 | A1 |
20160335989 | Ooi et al. | Nov 2016 | A1 |
20160370860 | Bychkov et al. | Dec 2016 | A1 |
20170010654 | Chen | Jan 2017 | A1 |
20170018234 | Na et al. | Jan 2017 | A1 |
20170028548 | Nagano | Feb 2017 | A1 |
20170034146 | Sugya | Feb 2017 | A1 |
20170039170 | Tunali et al. | Feb 2017 | A1 |
20170045936 | Kakapuri | Feb 2017 | A1 |
20170075479 | Tsukamoto | Mar 2017 | A1 |
20170085790 | Bohn | Mar 2017 | A1 |
20170090585 | Bernhart | Mar 2017 | A1 |
20170147879 | Alameh et al. | May 2017 | A1 |
20170201254 | Hanssen et al. | Jul 2017 | A1 |
20170219240 | Cassini et al. | Aug 2017 | A1 |
20170269725 | Kang | Sep 2017 | A1 |
20170321856 | Keates | Sep 2017 | A1 |
20180039410 | Kim et al. | Feb 2018 | A1 |
20180039990 | Lindemann | Feb 2018 | A1 |
20180136719 | Chen | May 2018 | A1 |
20180157815 | Salama et al. | Jun 2018 | A1 |
20180164942 | Huffman et al. | Jun 2018 | A1 |
20180166076 | Higuchi et al. | Jun 2018 | A1 |
20180188774 | Ent et al. | Jul 2018 | A1 |
20180188803 | Sharma et al. | Jul 2018 | A1 |
20180189547 | Daniels et al. | Jul 2018 | A1 |
20180224871 | Sahu et al. | Aug 2018 | A1 |
20180321731 | Alfano et al. | Nov 2018 | A1 |
20180373292 | Perelli | Dec 2018 | A1 |
20190004764 | Son et al. | Jan 2019 | A1 |
20190034609 | Yang et al. | Jan 2019 | A1 |
20190079572 | Yamamoto | Mar 2019 | A1 |
20190129473 | Hu et al. | May 2019 | A1 |
20190147875 | Stemmer et al. | May 2019 | A1 |
20190155364 | Chen | May 2019 | A1 |
20190155368 | Branover | May 2019 | A1 |
20190174419 | Schillings et al. | Jun 2019 | A1 |
20190236390 | Guo et al. | Aug 2019 | A1 |
20190239384 | North et al. | Aug 2019 | A1 |
20190250691 | Lee et al. | Aug 2019 | A1 |
20190258785 | Alameh | Aug 2019 | A1 |
20190265831 | Sinnot et al. | Aug 2019 | A1 |
20190278339 | Cooper et al. | Sep 2019 | A1 |
20190361501 | Park et al. | Nov 2019 | A1 |
20190371326 | Bocklet et al. | Dec 2019 | A1 |
20190371342 | Tukka et al. | Dec 2019 | A1 |
20200012331 | De Cesare et al. | Jan 2020 | A1 |
20200026342 | Sengupta et al. | Jan 2020 | A1 |
20200033920 | Nielsen et al. | Jan 2020 | A1 |
20200134151 | Magi et al. | Jan 2020 | A1 |
20200092817 | Bai | Mar 2020 | A1 |
20200125158 | Giusti et al. | Apr 2020 | A1 |
20200125179 | Okuley | Apr 2020 | A1 |
20200133358 | Mishra et al. | Apr 2020 | A1 |
20200133374 | Sinha | Apr 2020 | A1 |
20200142471 | Azam et al. | May 2020 | A1 |
20200175944 | Sun et al. | Jun 2020 | A1 |
20200213501 | Sohn | Jul 2020 | A1 |
20200259638 | Carmignani et al. | Aug 2020 | A1 |
20200348745 | Hamlin et al. | Nov 2020 | A1 |
20210025976 | Chandel et al. | Jan 2021 | A1 |
20210096237 | Patole et al. | Apr 2021 | A1 |
20210109585 | Fleming et al. | Apr 2021 | A1 |
20210240254 | Hamlin et al. | Aug 2021 | A1 |
20210318743 | Partiwala et al. | Oct 2021 | A1 |
20210327394 | Bui et al. | Oct 2021 | A1 |
20220147142 | Bui et al. | May 2022 | A1 |
20220334620 | Cooper et al. | Oct 2022 | A1 |
20230205307 | Han et al. | Jun 2023 | A1 |
Number | Date | Country |
---|---|---|
102197349 | Sep 2011 | CN |
102231255 | Nov 2011 | CN |
107077184 | Aug 2017 | CN |
112558056 | Mar 2021 | CN |
2518586 | Oct 2012 | EP |
3285133 | Jan 2019 | EP |
H0651901 | Feb 1994 | JP |
H10-240389 | Sep 1998 | JP |
2001255854 | Sep 2001 | JP |
2002071833 | Mar 2002 | JP |
2005221907 | Aug 2005 | JP |
2010060746 | Mar 2010 | JP |
2010271339 | Dec 2010 | JP |
2011137874 | Jul 2011 | JP |
2016517087 | Jun 2016 | JP |
20130093962 | Aug 2013 | KR |
20150022673 | Mar 2015 | KR |
20180029370 | Mar 2018 | KR |
20190027930 | Mar 2019 | KR |
2010071631 | Jun 2010 | WO |
2014131188 | Sep 2014 | WO |
2014186294 | Nov 2014 | WO |
2014205227 | Dec 2014 | WO |
2015026203 | Feb 2016 | WO |
2017010654 | Jan 2017 | WO |
2020191643 | Jan 2020 | WO |
2021258395 | Dec 2021 | WO |
2022139895 | Jun 2022 | WO |
Entry |
---|
“Dell's New Latitude 7400 2-in-1 Can Detect Your Presence and Automatically Wake the System,” MSPowerUser, Jan. 4, 2019, available at https://mspoweruser.com/dells-new-latitude-7400-2-in-1-can-detect-your-presence-and-automatically-wake-the-system/ (20 pages). |
Brian Reads, “Microsoft Windows Vista SideShow—In-Depth (pics)”, Notebook Review, available at www.notebookreview.com/news/microsoft-windows-vista-sideshow-in-depth-pics/ (retrieved May 6, 2019), Jan. 11, 2006, 7 pages. |
Chethan, “Proximity Sensing with CapSense,” Cypress AN92239, 2016, 62 pages. |
Cravotta, Nicholas, “Optimizing Proximity Sensing for Consumer Electronics Applications,” Digi-Key Electronics, Apr. 26, 2012, 9 pages. |
Cutress, “Asus ZenBook Pro 15(UX580): A 5.5-inch Screen in the Touchpad”, retrieved from https://www.anandtech.com/show/12880/asus-zenbook-pro-15-ux580-a-55inch-screen-in-the-touchpad, Jun. 5, 2018, 5 pages. |
European Patent Office, “Extended European Search Report” issued in connection with European Patent Application No. 20194494.9, dated Feb. 17, 2021, 62 pages. |
European Patent Office, “Extended European Search Report,” issued in connection with European Patent Application No. 20164273.3, dated Oct. 9, 2020, 14 pages. |
European Patent Office, “Extended European Search Report,” issued in connection with European Patent Application No. 20197335.1, dated Jul. 16, 2021, 11 pages. |
European Patent Office, “Extended European Search Report,” issued in connection with European Patent Application No. 20197337.7, dated Mar. 9, 2021, 11 pages. |
European Patent Office, “Extended Search Report,” issued in connection with European Patent Application No. 20181123.9, dated Dec. 4, 2020, 11 pages. |
European Patent Office, “Rule 62a(1) Communication,” issued in connection with European Patent Application No. 20197335.1, dated Mar. 17, 2021, 2 pages. |
Gajitz, “Open Sesame! Gesture-Controlled Motorized Laptop Lid”, available at https://gajitz.com/open-sesame-gesture-controlled-motorized-laptop-lid/ (retrieved May 6, 2019), Sep. 2012, 3 pages. |
Indiegogo, “Cosmo Communicator”, available at https://www.indiegogo.com/projects/cosmo-communicator#/ (retrieved May 6, 2019), 2018, 18 pages. |
International Searching Authority, “International Preliminary Report on Patentability,” issued in connection with PCT/US2016/048953, dated Mar. 27, 2018, 10 pages. |
International Searching Authority, “International Search Report,” issued in connection with PCT Application No. PCT/US2016/048953, dated Nov. 23, 2016. |
International Searching Authority, “Search Report and Written Opinion ,” issued in connection with PCT Application No. PCT/CN2020/098326, dated Mar. 29, 2021, 9 pages. |
International Searching Authority, “Search Report,” issued in connection with application No. PCT/CN2019/079790, dated Jan. 3, 2020, 4 pages. |
International Searching Authority, “Written Opinion of the International Searching Authority,” issued in connection with PCT Application No. PCT/US2016/048953, dated Nov. 23, 2016. |
International Searching Authority, “Written Opinion,” issued in connection with application No. PCT/CN2019/079790, dated Jan. 3, 2020, 4 pages. |
“Jack Purcher,” Google Patents a Motorized Pixelbook Lid that Opens and Closes with a Simple Touch & Auto. |
Aligns the Display to the user's Face, Patently Mobile, available at https://www.patentlymobile.com/2017/11/google-patents-a-motorized-pixelbook-lid-that-opens-and-closes-with-a-simple-touch-auto-aligns-the-display-to-the-users-fa.html (retrieved May 6, 2019), Nov. 25, 2017, 6 pages. |
Kul Bushan, “CES 2019_ Dell's new laptop can sense your presence and wake itself” Hindustan Times, available at https://www.hindustantimes.com/tech/ces-2019-dell-latitude-7400-2-in-1-laptop-launched-price-specifications-features/story-CiRoU1GoHHsHq3K3qtPZWJ.html (retrieved May 6, 2019), Jan. 5, 2019, 8 pages. |
Monica Chin, “Alexa on Windows 10 Hands-On: Useful, with 1 Big Catch”, Laptop Magazine, available at https://www.laptopmag.com/articles/alexa-windows-10-hands-on (retrieved May 6, 2019), Nov. 14, 2018, 6 pages. |
Notebook Review, “CES 2007: Vista SideShow in HP, Fujitsu, LG and Asus Notebooks,” Notebook Review, available at www.notebookreview.com/news/ces-2007-vista-sideshow-in-hp-fujitsu-lg-and-asus-notebooks/ (retrieved May 6, 2019), Jan. 8, 2007, 8 pages. |
NVIDIA “PDK User's Guide: Preface Personal Media Device,” Manual, published Sep. 4, 2007, 39 pages. |
NVIDIA, “NVIDIA and ASUS Deliver World's First Notebook with Windows Sideshow Secondary Display,” Press Release, available at https://www.nvidia.com/object/IO_38772.html (retrieved May 6, 2019), Jan. 8, 2007, 5 pages. |
NVIDIA, “NVIDIA® Preface™ Platform Enables Windows Vista on the Go,” Press Release, available at https://www.nvidia.com/object/IO_38775.html (retrieved May 6, 2019), Jan. 8, 2007, 5 pages. |
United States Patent and Trademark Office, “Advisory Action” issued in connection with U.S. Appl. No. 14/866,894, dated Aug. 17, 2020, 3 pages. |
United States Patent and Trademark Office, “Advisory Action” issued in connection with U.S. Appl. No. 14/866,894, dated Nov. 5, 2019, 6 pages. |
United States Patent and Trademark Office, “Corrected Notice of Allowability” issued in connection with U.S. Appl. No. 16/586,225, dated Mar. 16, 2022, 3 pages. |
United States Patent and Trademark Office, “Corrected Notice of Allowability,” issued in connection with U.S. Appl. No. 16/586,225, dated Dec. 16, 2021, 3 pages. |
United States Patent and Trademark Office, “Final Office Action” issued in connection with U.S. Appl. No. 14/866,894, dated Jul. 29, 2019, 27 pages. |
United States Patent and Trademark Office, “Final Office Action” issued in connection with U.S. Appl. No. 14/866,894, dated Jun. 23, 2020, 33 pages. |
United States Patent and Trademark Office, “Final Office Action,” issued in connection with U.S. Appl. No. 14/866,894, dated May 11, 2021, 17 pages. |
United States Patent and Trademark Office, “Non Final Office Action” issued in connection with U.S. Appl. No. 14/866,894, dated Feb. 21, 2020, 30 pages. |
United States Patent and Trademark Office, “Non Final Office Action” issued in connection with U.S. Appl. No. 14/866,894, dated Oct. 8, 2020, 40 pages. |
United States Patent and Trademark Office, “Non-Final Office Action” issued in connection with U.S. Appl. No. 14/866,894, dated Dec. 14, 2018, 24 pages. |
United States Patent and Trademark Office, “Non-Final Office Action” issued in connection with U.S. Appl. No. 16/728,899, dated Dec. 8, 2021, 9 pages. |
United States Patent and Trademark Office, “Non-Final Office Action,” issued in connection with U.S. Appl. No. 16/586,225, dated Jun. 15, 2021, 28 pages. |
United States Patent and Trademark Office, “Non-Final Office Action,” issued in connection with U.S. Appl. No. 16/725,467, dated Apr. 7, 2022, 19 pages. |
United States Patent and Trademark Office, “Notice of Allowance and Fee(s) Due” issued in connection with U.S. Appl. No. 16/421,217, dated Mar. 9, 2022, 14 pages. |
United States Patent and Trademark Office, “Notice of Allowance and Fee(s) Due,” issued in connection with U.S. Appl. No. 14/866,894, dated Jul. 30, 2021, 8 pages. |
United States Patent and Trademark Office, “Notice of Allowance,” issued in connection with U.S. Appl. No. 16/586,225, dated Dec. 8, 2021, 6 pages. |
Bogdan Popa, “Intel Considering Microsoft Surface Killer with Curved Display,” Feb. 6, 2017, retrieved on May 26, 2023, retrieved from https://news.softpedia.com/news/intel-considering-microsoft -surface-killer -with-curved-display-512636.shtml, 2 pages. |
European Patent Office, “Communication pursuant to Article 71(3) EPC,” issued in connection with European Patent Application No. 20164273.3, dated Dec. 23, 2022, 78 pages. |
European Patent Office, “Communication pursuant to Article 94(3) EPC,” issued in connection with European Patent Application No. 20164273.3, dated Sep. 28, 2021 9 pages. |
European Patent Office, “Communication pursuant to Article 94(3) EPC,” issued in connection with European Patent Application No. 20194494.9, dated Jan. 24, 2023, 6 pages. |
European Patent Office, “Extended European Search Report,” issued in connection with European Patent Application No. 19921860.3, dated Oct. 10, 2022, 8 pages. |
Intellectual Property India, “Examination Report,” issued in connection with Indian Patent Application No. 202147037534, dated Feb. 2, 2023, 6 pages. |
International Searching Authority, “International Preliminary Report on Patentability,” issued in connection with application No. PCT/CN2019/079790, dated Sep. 28, 2021, 5 pages. |
International Searching Authority, “International Search Report”, issued in connection with PCT. Application No. PCT/US2021/049649, dated Jan. 14, 2022, 5 pages. |
International Searching Authority, “International Search Report,” issued in connection with PCT Application No. PCT/CN2022/084726, dated Jan. 4, 2023, 4 pages. |
International Searching Authority, “Invitation to Pay Additional Fees,” issued in connection with PCT/US2021/049649, dated Nov. 26, 2021, 7 pages. |
International Searching Authority, “Written Opinion”, issued in connection with PCT. Application No. PCT/US2021/049649, dated Jan. 14, 2022, 9 pages. |
International Searching Authority, “Written Opinion,” issued in connection with PCT Application No. PCT/CN2022/084726, dated Jan. 4, 2023, 4 pages. |
Japanese Patent Office, “Notice of Reasons for Rejection,” issued in connection with Japanese Patent Application No. 2021-538701, dated Feb. 21, 2023, 7 pages (English translation included). |
The Netherlands Patent Office, “Office Action,” issued in connection with Netherlands Application No. 2029823, dated Mar. 15, 2023, 14 pages (Written Opinion Provided in English). |
United States Patent and Trademark Office, “Non-Final Office Action,” issued in connection with U.S. Appl. No. 16/421,217, dated Oct. 27, 2021, 42 pages. |
United States Patent and Trademark Office, “Advisory Action,” issued in connection with U.S. Appl. No. 16/725,467, dated Jan. 4, 2023, 3 pages. |
United States Patent and Trademark Office, “Advisory Action,” issued in connection with U.S. Appl. No. 16/728,899, dated Oct. 5, 2022, 2 pages. |
United States Patent and Trademark Office, “Corrected Notice of Allowability,” issued in connection with U.S. Appl. No. 16/421,217, dated May 27, 2022, 2 pages. |
United States Patent and Trademark Office, “Corrected Notice of Allowability,” issued in connection with U.S. Appl. No. 16/586,225, dated Dec. 7, 2022, 3 pages. |
United States Patent and Trademark Office, “Corrected Notice of Allowability,” issued in connection with U.S. Appl. No. 16/586,225, dated May 18, 2022, 3 pages. |
United States Patent and Trademark Office, “Corrected Notice of Allowability,” issued in connection with U.S. Appl. No. 16/586,225, dated Sep. 19, 2022, 2 pages. |
United States Patent and Trademark Office, “Corrected Notice of Allowability,” issued in connection with U.S. Appl. No. 17/856,587, dated Feb. 14, 2023, 2 pages. |
United States Patent and Trademark Office, “Corrected Notice of Allowability,” issued in connection with U.S. Appl. No. 17/856,587, dated Jan. 10, 2023, 2 pages. |
United States Patent and Trademark Office, “Final Office Action,” issued in connection with U.S. Appl. No. 16/725,467, dated Aug. 18, 2022, 29 pages. |
United States Patent and Trademark Office, “Final Office Action,” issued in connection with U.S. Appl. No. 16/728,774, dated Sep. 22, 2021, 20 pages. |
United States Patent and Trademark Office, “Final Office Action,” issued in connection with U.S. Appl. No. 16/728,899, dated Jun. 24, 2022, 10 pages. |
United States Patent and Trademark Office, “Final Office Action,” issued in connection with U.S. Appl. No. 17/434,603, dated Feb. 8, 2023, 17 pages. |
United States Patent and Trademark Office, “Non-Final Office Action” issued in connection with U.S. Appl. No. 16/728,899, dated Oct. 20, 2022, 9 pages. |
United States Patent and Trademark Office, “Non-Final Office Action,” issued in connection with U.S. Appl. No. 16/728,774, dated May 3, 2021, 12 pages. |
United States Patent and Trademark Office, “Non-Final Office Action,” issued in connection with U.S. Appl. No. 17/129,465, dated Jan. 5, 2023, 12 pages. |
United States Patent and Trademark Office, “Non-Final Office Action,” issued in connection with U.S. Appl. No. 17/434,603, dated Jul. 5, 2022, 15 pages. |
United States Patent and Trademark Office, “Notice of Allowability,” issued in connection with U.S. Appl. No. 29/673,785 dated Feb. 19, 2021, 2 pages. |
United States Patent and Trademark Office, “Notice of Allowance and Fee(s) Due” issued in connection with U.S. Appl. No. 16/421,217, dated Mar. 24, 2022, 3 pages. |
United States Patent and Trademark Office, “Notice of Allowance and Fee(s) Due,” issued in connection with U.S. Appl. No. 16/586,225, dated Apr. 29, 2022, 6 pages. |
United States Patent and Trademark Office, “Notice of Allowance and Fee(s) Due,” issued in connection with U.S. Appl. No. 16/586,225, dated Aug. 31, 2022, 5 pages. |
United States Patent and Trademark Office, “Notice of Allowance and Fee(s) Due,” issued in connection with U.S. Appl. No. 16/725,467, dated Feb. 23, 2023, 9 pages. |
United States Patent and Trademark Office, “Notice of Allowance and Fee(s) Due,” issued in connection with U.S. Appl. No. 16/728,774, dated Feb. 2, 2022, 9 pages. |
United States Patent and Trademark Office, “Notice of Allowance and Fee(s) Due,” issued in connection with U.S. Appl. No. 17/856,587, dated Dec. 9, 2022, 9 pages. |
United States Patent and Trademark Office, “Notice of Allowance and Fee(s) Due,” issued in connection with U.S. Appl. No. 16/728,899, dated Apr. 3, 2023, 10 pages. |
United States Patent and Trademark Office, “Notice of Allowance,” issued in connection with U.S. Appl. No. 29/673,785, dated Nov. 16, 2020, 8 pages. |
United States Patent and Trademark Office, “Requirement for Restriction,” issued in connection with U.S. Appl. No. 29/673,785, dated Aug. 27, 2020, 4 pages. |
United States Patent and Trademark Office, “Supplemental Notice of Allowability,” issued in connection with U.S. Appl. No. 16/725,467, dated Apr. 26, 2023, 3 pages. |
United States Patent and Trademark Office, “Supplemental Notice of Allowability,” issued in connection with U.S. Appl. No. 16/725,467, dated Mar. 1, 2023, 3 pages. |
United States Patent and Trademark Office, “Notice of Allowance and Fee(s) Due”, issued in connection with U.S. Appl. No. 18/160,419, dated Aug. 23, 2023, 11 pages. |
GSMArena team, “Samsung Galaxy Fold review,” GSMARENA, dated Apr. 26, 2019, retrieved from https://www.Jsmarena.com/samsung_galaxy_fold-review-1926p4.php on Jun. 8, 2023, 8 pages. |
Samsung, “Samsung Galaxy Fold Now Available,” Samsung Global Newsroom, retrieved rom https://news.samsung.com/global/samsung-galaxy-fold-now-available on Jun. 8, 2023, dated Sep. 5, 2019, 7 pages. |
GSMARENA Team, “Samsung Galaxy Fold Long-Term Review,” GSMARENA, retrieved from https://www.gsmarena.com/samsung_galaxy_fold_long_term-review-1996p7.php on Jun. 8, 2023, dated Nov. 9, 2019, 8 pages. |
European Patent Office, “Communication Pursuant to Article 94(3) EPC,” issued in connection with European Patent Application No. 20197337.7-1218, dated Aug. 10, 2023, 10 pages. |
International Searching Authority, “International Search Report and Written Opinion,” issued in connection with International Application No. PCT/US2022/022196, dated Jun. 30, 2022, 10 pages. |
United States Patent and Trademark Office, “Final Office Action,” issued in connection with U.S. Appl. No. 17/129,465, dated Jul. 7, 2023, 15 pages. |
United States Patent and Trademark Office, “Notice of Allowance,” issued in connection with U.S. Appl. No. 16/725,467, dated Jun. 29, 2023, 6 pages. |
International Searching Authority, “International Preliminary Report on Patentability,” issued in connection with International application No. PCT/US2021/049649, dated Jun. 13, 2023, 10 pages. |
Japanese Patent Office, “Decision of Refusal,” issued in connection with Japanese Patent Application No. 2021-538701, dated Jun. 6, 2023, 6 pages. [English Translation Included]. |
Japanese Patent Center, “Search Report,” issued in connection with Japanese Patent Application No. 2021-538701, dated Feb. 15, 2023, 58 pages (English Translation Included). |
European Patent Office, “Communication under Rule 71(3) EPC,” in connection with European Patent Application No. 20164273.3-1224 , dated Jul. 29, 2022, 5 pages. |
International Bureau, “International Preliminary Report on Patentability,” issued in connection with PCT No. PCT/CN2020/098326, dated Dec. 13, 2022, 5 pages. |
United States Patent and Trademark Office, “Non-Final Office Action,” issued in connection with U.S. Appl. No. 29/771,488, dated Oct. 11, 2023, 6 pages. |
Japanese Patent Office, “Notice of Reasons for Rejection,” issued in connection with Japanese Patent Application No. 2021-538701, dated Mar. 3, 2023, 8 pages ( English translation included). |
European Patent Office, “Extended European Search Report,” in connection with European Patent Application No. 23154752.2-1224 , dated May 4, 2023, 14 pages. |
United States Patent and Trademark Office, “Corrected Notice of Allowability,” issued in connection with U.S. Appl. No. 17/856,587, dated Jul. 3, 2023, 2 pages. |
United States Patent and Trademark Office, “Corrected Notice of Allowability,” issued in connection with U.S. Appl. No. 17/856,587, dated Sep. 5, 2023, 2 pages. |
United States Patent and Trademark Office, “Non-Final Office Action,” issued in connection with U.S. Appl. No. 17/434,603, dated Sep. 7, 2023, 17 pages. |
European Patent Office, “Communication pursuant to Article 94(3) EPC,” issued in connection with European Patent Application No. 20197335.1-1224, dated Oct. 5, 2023, 5 pages. |
United States Patent and Trademark Office, “Notice of Allowability” issued in connection with U.S. Appl. No. 18/160,419, dated Dec. 13, 2023, 2 pages. |
United States Patent and Trademark Office, “Notice of Allowance and Fee(s) Due,” issued in connection with U.S. Appl. No. 17/434,603, dated Dec. 26, 2023, 9 pages. |
United States Patent and Trademark Office, “Notice of Allowance and Fee(s) Due,” issued in connection with U.S. Appl. No. 17/132,838, dated Mar. 6, 2024, 8 pages. |
Number | Date | Country | |
---|---|---|---|
20220350385 A1 | Nov 2022 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 16728774 | Dec 2019 | US |
Child | 17732173 | US |