System and method for managing power consumption of device subsystem

By maintaining the application constraint metrics on the device and adjusting the subsystem power according to the application type, the problem of improper power consumption management in the existing technology is solved, intelligent power management is realized, and device performance and user experience are improved.

CN119013638APending Publication Date: 2024-11-22CTRL-LABS CORP
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380033576.5
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-04-12
Filing Date
2023-04-11
Publication Date
2024-11-22

AI Technical Summary

Technical Problem

The existing power/thermal management systems are mainly at the hardware control level, reactive, and it is difficult to effectively manage the power consumption of the device subsystem, resulting in a decline in device performance and user experience.

Method used

By maintaining the application constraint metric on the device, specifying the corresponding power level for multiple subsystems according to the application type, reducing the power level operation and adjusting the power consumption of the subsystem when the device meets the thermal or power threshold criteria.

Benefits of technology

Implement application-based intelligent power management, avoiding the negative impact of global power reduction on user experience, and improving device performance and reliability.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119013638A_ABST
    Figure CN119013638A_ABST
Patent Text Reader

Abstract

Systems and methods for managing power consumption of a device subsystem include a device that maintains one or more constraint metric tables for applications that can be executed on the device. Each of the one or more constraint metric tables may specify a respective power level for a plurality of subsystems of the device according to a respective application or an application type of the respective application. The device may determine to operate the device at a reduced power level for the first application based on a condition of the device satisfying at least one of a thermal threshold criterion or a power threshold criterion when the device is operating at a full power level. The device may apply constraint metrics in response to determining to operate at the reduced power level to cause a subset of the plurality of subsystems to adjust the power consumption level according to a first table of constraint metrics corresponding to the first application.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates generally to power management, including but not limited to managing power consumption of device subsystems. Background Art

[0002] Devices such as battery-powered devices or wireless devices often include some power / thermal management system. However, these systems are usually implemented at the hardware control level and are reactive in nature. As a result, these systems can generally reduce power consumption across the hardware components of the device. Summary of the invention

[0003] In one aspect, the present disclosure relates to a method. The method may include: maintaining, by a device, one or more constraint metric tables for applications that can be executed on the device, each of the one or more constraint metric tables may specify a corresponding power level for multiple subsystems of the device according to the corresponding application or the type of the corresponding application. The method may include: determining, by the device, to operate the device at a reduced power level for a first application based on a condition of the device satisfying at least one of a thermal threshold standard or a power threshold standard when the device is operating at a full power level. The method may include: applying, by the device in response to determining to operate at a reduced power level, a constraint metric so that a subset of the multiple subsystems adjusts the power consumption level according to a first constraint metric table corresponding to the first application.

[0004] In some embodiments, applying a constraint metric includes: transmitting, by a controller of the device, the constraint metric to each of a plurality of subsystems of the device. In some embodiments, the controller is part of or includes an operating system for the device. In some embodiments, the method includes: identifying, by a first subsystem, a first constraint metric table in one or more constraint metric tables based on at least one of the following: a first application or an applied constraint metric; and modifying, by the first subsystem, a power consumption level of the first subsystem based on a power level specified for the first subsystem in the first constraint metric table. In some embodiments, the power level is a first power level of the first subsystem, and the method may include: identifying, by a second subsystem, the first constraint metric table. The method may include: determining, by the second subsystem, that a current power consumption level of the second subsystem is within a second power level specified for the second subsystem in the first constraint metric table.

[0005] In some embodiments, the one or more constraint metric tables include a first constraint metric table for a first application and a second constraint metric table for a second application, the first constraint metric table may specify a first power level for the first subsystem, and the second constraint metric table may specify a second power level for the first subsystem, the second power level being different from the first threshold power level. In some embodiments, the first constraint metric table is associated with a plurality of applications having the same application type as the first application. In some embodiments, the constraint metric causes a first subsystem of the plurality of subsystems to adjust a power consumption level of the first subsystem by a first degree; and causes a second subsystem to not adjust a power consumption level of the second subsystem, or to adjust a power consumption level of the second subsystem by a second degree, the second degree being different from the first degree. In some embodiments, when the device is operating at a full power level, the condition satisfies at least one of a thermal threshold criterion or a power threshold criterion, including: when the device is operating at a full power level, the power consumption of the device is greater than or equal to the power threshold, or the temperature or thermal output of the device is greater than or equal to the thermal threshold. In some embodiments, the multiple subsystems include at least one of the following: an audio subsystem; a camera subsystem; a sensor subsystem; a communication subsystem; a display unit subsystem; a central processing unit (CPU) subsystem; or a graphics processing unit (GPU) subsystem.

[0006] On the other hand, the present disclosure relates to a device. The device may include multiple subsystems. The device may include one or more constraint metric tables for applications that can be executed on the device, each of the one or more constraint metric tables specifying a corresponding power level for one or more subsystems in the multiple subsystems according to the corresponding application or the application type of the corresponding application. The device may include one or more processors, which are communicatively coupled to the multiple subsystems. The one or more processors may be configured to: determine to operate the device at a reduced power level for a first application based on the condition of the device satisfying at least one of a thermal threshold standard or a power threshold standard when the device is running at full power level. The one or more processors may be configured to: apply constraint metrics in response to determining to operate the device at a reduced power level so that a subset of the multiple subsystems adjusts the power consumption level according to a first constraint metric table corresponding to the first application.

[0007] In some embodiments, one or more processors are configured to: transmit a constraint metric to each subsystem in a plurality of subsystems of a device. In some embodiments, a first subsystem in the plurality of subsystems is configured to: identify a constraint metric table in one or more constraint metric tables based on a first application; and may modify a power consumption level based on a power level specified for the first subsystem in the first constraint metric table. In some embodiments, the power level is a first power level for the first subsystem. A second subsystem in the plurality of subsystems may be configured to: identify the first constraint metric table; and may determine that a current power consumption level of the second subsystem is within a second power level specified for the second subsystem in the first constraint metric table specified for the second subsystem.

[0008] In some embodiments, the one or more constraint metric tables include a first constraint metric table for a first application and a second constraint metric table for a second application. The first constraint metric table may specify a first power level for the first subsystem, and the second constraint metric table may specify a second power level for the first subsystem, the second power level being different from the first threshold power level. In some embodiments, the constraint metric table is associated with a plurality of applications having the same application type as the first application. In some embodiments, the constraint metric causes a first subsystem of the plurality of subsystems to adjust a power consumption level of the first subsystem by a first degree, and causes a second subsystem to not adjust a power consumption level of the second subsystem or to adjust a power consumption level of the second subsystem by a second degree, the second degree being different from the first degree. In some embodiments, when the device is running at full power level, the condition satisfies at least one of a thermal threshold criterion or a power threshold criterion, including: when the device is running at full power level, the power consumption of the device is greater than or equal to the power threshold, or the temperature or heat output of the device is greater than or equal to the thermal threshold. In some embodiments, the plurality of subsystems include at least one of the following: an audio subsystem; a camera subsystem; a sensor subsystem; a communication subsystem; a display unit subsystem; a central processing unit (CPU) subsystem; or a graphics processing unit (GPU) subsystem.

[0009] In another aspect, the present disclosure relates to a non-transitory computer-readable medium storing a plurality of instructions that, when executed by one or more processors of a device, cause the one or more processors to execute an operating system of the device. The operating system may be configured to determine to operate the device at a reduced power level for a first application based on a condition of the device satisfying at least one of a thermal threshold criterion or a power threshold criterion when the device is operating at a full power level. The one or more processors may be configured to apply a constraint metric in response to determining to operate the device at a reduced power level so that a subset of a plurality of subsystems of the device adjust a power consumption level according to a first constraint metric table corresponding to the first application. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] The accompanying drawings are not intended to be drawn to scale. Like reference numbers and names in the various drawings refer to like elements. For clarity, not every component may be labeled in every drawing.

[0011] Figure 1 is a schematic diagram of a system environment including an artificial reality system according to an example implementation of the present disclosure.

[0012] Figure 2 is a schematic diagram of a head mounted display according to an example implementation of the present disclosure.

[0013] Figure 3 is a block diagram of a computing environment according to an example implementation of the present disclosure.

[0014] Figure 4 is a block diagram of a device according to an example implementation of the present disclosure.

[0015] FIG. 5A to FIG. 5C is an example graph showing constraint metrics and corresponding power levels for different application types according to an example implementation of the present disclosure.

[0016] Figure 6 is a diagram showing constraint metrics and (e.g., Figure 4 An example chart of corresponding power levels for different subsystems of a device.

[0017] Figure 7 is a flow chart illustrating a method of managing power consumption of a device subsystem according to an example implementation of the present disclosure. DETAILED DESCRIPTION

[0018] Before turning to the drawings showing certain embodiments in detail, it should be understood that the present disclosure is not limited to the details or methods set forth in the specification or shown in the drawings. It should also be understood that the terminology used herein is for descriptive purposes only and should not be considered as limiting.

[0019] In order to read the following description of various embodiments, the following description of the various parts of the specification and their corresponding contents may be helpful:

[0020] Section A discloses an artificial reality system suitable for practicing the embodiments described herein;

[0021] Section B discloses computing systems that can be used to implement aspects of the present disclosure; and

[0022] Part C discloses systems and methods for managing power consumption of device subsystems.

[0023] A. Artificial Reality Systems

[0024] Disclosed herein are systems and methods for facilitating distribution of artificial reality (eg, augmented reality (AR), virtual reality (VR), or mixed reality (MR)) content. Figure 1 is a block diagram of an example artificial reality system environment 100. In some embodiments, the artificial reality system environment 100 includes a head wearable display (HWD) 150 worn by a user, and a console 110 that provides content of the artificial reality to the HWD 150. The HWD 150 can detect its position and / or orientation of the HWD 150, and provide the detected position and / or orientation of the HWD 150 to the console 110. The console 110 can generate image data indicating the artificial reality image based on the detected position and / or orientation of the HWD 150 and the user input for the artificial reality, and send the image data to the HWD 150 for presentation.

[0025] In some embodiments, the artificial reality system environment 100 includes Figure 1 More, fewer, or more of the components shown may be included. Figure 1 In some embodiments, the functionality of one or more components in the artificial reality system environment 100 may be distributed among the components in a manner different from that described herein. For example, some functions of the console 110 may be performed by the HWD 150. For example, some functions of the HWD 150 may be performed by the console 110. In some embodiments, the console 110 is integrated as part of the HWD 150.

[0026] In some embodiments, HWD 150 is an electronic component that can be worn by a user and can present or provide an artificial reality experience to the user. HWD 150 may be referred to as, include, or be part of a head mounted display (HMD); a head mounted device (HMD); a head wearable device (HWD); a head worn display (HWD); or a head worn device (HWD). HWD 150 may render one or more images, videos, audio, or some combination thereof to provide an artificial reality experience to the user. In some embodiments, audio is presented via an external device (e.g., a speaker and / or headphones) that receives audio information from HWD 150, console 110, or both, and presents audio based on the audio information. In some embodiments, HWD 150 includes sensor 155, eye tracker 160, hand tracker 162, communication interface 165, image renderer 170, electronic display 175, lens 180, and compensator 185. These components can work together to detect the position of HWD 150 and the gaze direction of the user wearing HWD 150, and render an image of the field of view in the artificial reality corresponding to the detected position and / or orientation of HWD 150. In other embodiments, HWD 150 includes more than Figure 1 More, fewer, or more of the components shown may be included. Figure 1 The parts shown are different parts.

[0027] In some embodiments, sensor 155 includes electronic components, or a combination of electronic components and software components, that detect the position and orientation of HWD 150. Examples of sensor 155 may include: one or more imaging sensors, one or more accelerometers, one or more gyroscopes, one or more magnetometers, or another suitable type of sensor that detects motion and / or position. For example, one or more accelerometers may measure translational motion (e.g., forward / backward, up / down, left / right), and one or more gyroscopes may measure rotational motion (e.g., pitch, left-right sway, roll). In some embodiments, sensor 155 detects translational motion and rotational motion and determines the orientation and position of HWD 150. In one aspect, sensor 155 may detect translational motion and rotational motion relative to a previous orientation and position of HWD 150, and determine a new orientation and / or position of HWD 150 by accumulating or integrating the detected translational motion and / or rotational motion. For example, assuming that HWD 150 is oriented at a direction 25 degrees from a reference direction, sensor 155 may determine that HWD 150 is now facing or heading toward a direction 45 degrees from the reference direction in response to detecting that HWD 150 has turned 20 degrees. For another example, assuming that HWD 150 is located two feet from a reference point in a first direction, sensor 155 may determine that HWD 150 is now located at the vector product of two feet in the first direction and three feet in the second direction in response to detecting that HWD 150 has moved three feet in a second direction.

[0028] In some embodiments, the eye tracker 160 includes an electronic component, or a combination of electronic components and software components, that determines the gaze direction of the user of the HWD 150. In some embodiments, the HWD 150, the console 110, or a combination thereof can generate image data for artificial reality in conjunction with the gaze direction of the user of the HWD 150. In some embodiments, the eye tracker 160 includes two eye trackers, each of which captures an image of a corresponding eye and determines the gaze direction of the eye. In one example, the eye tracker 160 determines the angular rotation of the eye, the translation of the eye, the torsion change of the eye, and / or the shape change of the eye based on the captured image of the eye, and determines the relative gaze direction relative to the HWD 150 based on the determined angular rotation, translation, and torsion change of the eye. In one method, the eye tracker 160 can illuminate or project a predetermined reference pattern or structured pattern on a portion of the eye, and capture an image of the eye to analyze the pattern projected on the portion of the eye, thereby determining the relative gaze direction of the eye relative to the HWD 150. In some embodiments, eye tracker 160 determines the gaze direction of the user in combination with the orientation of HWD 150 and the relative gaze direction with respect to HWD 150. For example, assuming that HWD 150 is oriented at a direction 30 degrees from a reference direction, and the relative gaze direction of HWD 150 is -10 degrees (or 350 degrees) with respect to HWD 150, eye tracker 160 may determine that the gaze direction of the user is 20 degrees from the reference direction. In some embodiments, the user of HWD 150 may configure HWD 150 (e.g., through user settings) to enable or disable eye tracker 160. In some embodiments, the user of HWD 150 is prompted to enable or disable eye tracker 160.

[0029] In some embodiments, hand tracker 162 includes electronic components, or a combination of electronic components and software components, that track the user's hands. In some embodiments, hand tracker 162 includes or is coupled to an imaging sensor (e.g., a camera) and an image processor that can detect the shape, position, and orientation of the hand. Hand tracker 162 can generate hand tracking measurements that indicate the shape, position, and orientation of the detected hand.

[0030] In some embodiments, the communication interface 165 includes an electronic component or a combination of an electronic component and a software component that communicates with the console 110. The communication interface 165 can communicate with the communication interface 115 of the console 110 via a communication link. The communication link can be a wireless link. Examples of the wireless link can include a cellular communication link, a near field communication link, Wi-Fi, Bluetooth, a 60 GHz wireless link, or any wireless communication link for communication. Through the communication link, the communication interface 165 can transmit the following data to the console 110: the data indicates the determined position and / or orientation of the HWD 150, the determined gaze direction of the user, and / or hand tracking measurement results. In addition, through the communication link, the communication interface 165 can receive instructions from the console 110 or image data corresponding to the image to be rendered, as well as additional data associated with the image.

[0031] In some embodiments, the image renderer 170 includes, for example, an electronic component that generates one or more images for display according to a change in the field of view in the space of the artificial reality, or a combination of electronic components and software components. In some embodiments, the image renderer 170 is implemented as a processor (or a graphical processing unit (GPU)) that executes instructions to perform the various functions described herein. The image renderer 170 may receive image data describing an artificial reality image to be rendered, and additional data associated with the image through the communication interface 165, and may render the image through the electronic display 175. In some embodiments, the image data from the console 110 may be encoded, and the image renderer 170 may decode the image data to render the image. In some embodiments, the image renderer 170 receives object information and depth information in the additional data from the console 110, the object information indicating a virtual object in the artificial reality space, and the depth information indicating the depth of the virtual object (or the distance from the HWD 150). In one aspect, the image renderer 170 may perform shading, reprojection, and / or blending based on the artificial reality image, object information, depth information, and / or updated sensor measurements from the sensor 155 to update the artificial reality image to correspond to the updated position and / or orientation of the HWD 150. Assuming that the user turns his head after the initial sensor measurement, the image renderer 170 may generate a small portion (e.g., 10%) of the image corresponding to the updated field of view in the artificial reality based on the updated sensor measurements, and append the portion to the image in the image data from the console 110 by reprojection, rather than reconstructing the entire image in response to the updated sensor measurements. The image renderer 170 may perform shading and / or blending on the additional edges. Thus, the image renderer 170 may generate an artificial reality image without reconstructing the artificial reality image based on the updated sensor measurements. In some embodiments, the image renderer 170 receives hand model data indicating the shape, position, and orientation of a hand model corresponding to the user's hand, and overlays the hand model on the image of the artificial reality. Such a hand model can be presented as visual feedback to allow the user to provide various interactions within the artificial reality.

[0032] In some embodiments, the electronic display 175 is an electronic component that displays an image. The electronic display 175 may be, for example, a liquid crystal display or an organic light emitting diode display. The electronic display 175 may be a transparent display that allows the user to see through. In some embodiments, when the user wears the HWD 150, the electronic display 175 is located near the user's eyes (e.g., less than 3 inches). In one aspect, the electronic display 175 emits light or projects light toward the user's eyes according to the image generated by the image renderer 170.

[0033] In some embodiments, lens 180 is a mechanical component that changes the light received from electronic display 175. Lens 180 can magnify the light from electronic display 175 and correct optical errors associated with the light. Lens 180 can be a Fresnel lens, a convex lens, a concave lens, a filter, or any suitable optical component that changes the light from electronic display 175. Although electronic display 175 is very close to both eyes, light from electronic display 175 can still pass through lens 180 to the pupil so that the user can see the image displayed by electronic display 175.

[0034] In some embodiments, compensator 185 includes an electronic component or a combination of electronic and software components that performs compensation to compensate for any distortion or aberration. In one aspect, lens 180 introduces optical aberrations (e.g., chromatic aberration), pincushion distortion, barrel distortion, etc. Compensator 185 can determine compensation (e.g., pre-distortion) to be applied to the image to be rendered from image renderer 170 to compensate for the distortion caused by lens 180, and apply the determined compensation to the image from image renderer 170. Compensator 185 can provide the pre-distorted image to electronic display 175.

[0035] In some embodiments, the console 110 is an electronic component, or a combination of electronic components and software components, that provides content to be rendered to the HWD 150. In one aspect, the console 110 includes a communication interface 115 and a content provider 130. These components can work together to determine the field of view of the artificial reality corresponding to the position of the HWD 150 and the gaze direction of the user of the HWD 150 (e.g., the user's field of view (FOV)), and can generate image data indicating the artificial reality image corresponding to the determined field of view. In addition, these components can work together to generate additional data associated with the image. The additional data can be information associated with presenting or rendering artificial reality in addition to the artificial reality image. Examples of additional data include hand model data, mapping information (or simultaneous localization and mapping (SLAM) data) for converting the position and orientation of the HWD 150 in the physical space to the virtual space, motion vector information, depth information, edge information, object information, etc. The console 110 can provide image data and additional data to the HWD 150 for presenting artificial reality. In other embodiments, the console 110 includes Figure 1 More, fewer, or more of the components shown may be included. Figure 1 In some embodiments, console 110 is integrated as part of HWD 150 .

[0036] In some embodiments, the communication interface 115 is an electronic component, or a combination of an electronic component and a software component, that communicates with the HWD 150. The communication interface 115 may be a counterpart of the communication interface 165, which communicates with the communication interface 115 of the console 110 via a communication link (e.g., a wireless link). Through the communication link, the communication interface 115 may receive data from the HWD 150 indicating the determined position and / or orientation of the HWD 150, the determined gaze direction of the user, and hand tracking measurements. In addition, through the communication link, the communication interface 115 may transmit image data describing the image to be rendered and additional data associated with the artificial reality image to the HWD 150.

[0037] The content provider 130 is a component that generates content to be rendered based on the position and / or orientation of the HWD 150. In some embodiments, the content provider 130 can combine the gaze direction of the user of the HWD 150 and the user interaction in the artificial reality based on the hand tracking measurement results to generate the content to be rendered. In one aspect, the content provider 130 determines the field of view of the artificial reality based on the position and / or orientation of the HWD 150. For example, the content provider 130 maps the position of the HWD 150 in the physical space to the position in the artificial reality space, and determines the field of view of the artificial reality space from the drawn position in the artificial reality space, along the direction corresponding to the mapped orientation. The content provider 130 can generate image data describing the image of the field of view of the determined artificial reality space, and transmit the image data to the HWD 150 through the communication interface 115. The content provider 130 can also generate a hand model corresponding to the hand of the user of the HWD 150 based on the hand tracking measurement results, and generate hand model data indicating the shape, position and orientation of the hand model in the artificial reality space. In some embodiments, the content provider 130 may generate additional data associated with the image (the additional data includes motion vector information, depth information, edge information, object information, hand model data, etc.), and transmit the additional data and the image data to the HWD 150 through the communication interface 115. The content provider 130 may encode the image data describing the image, and may transmit the encoded data to the HWD 150. In some embodiments, the content provider 130 generates image data periodically (e.g., every 11 ms) and provides the image data to the HWD 150.

[0038] Figure 2 1 is a schematic diagram of HWD 150 according to an example embodiment. In some embodiments, HMD 150 includes front rigid body 205 and strap 210. Front rigid body 205 includes electronic display 175 ( Figure 2 Not shown), lens 180 ( Figure 2 (not shown)), sensor 155, eye tracker 160A, 160B, communication interface 165 and image renderer 170. Figure 2 In the illustrated embodiment, the communication interface 165, image renderer 170, and sensor 155 are located within the front rigid body 205 and may not be visible to the user. In other embodiments, the HWD 150 may have a Figure 2 For example, the communication interface 165, the image renderer 170, the eye tracker 160A, 160B and / or the sensor 155 may be located in a different configuration than that shown. Figure 2 In some embodiments, HWD 150 may include multiple communication interfaces 165. Similarly, Figure 1The console 110 may include multiple communication interfaces 115. As described in more detail below in Section B, one or more of the communication interfaces 115, 165 may be configured to selectively perform beamforming to optimize the communication channel between the console 110 and the HWD 150. Similarly, the console 110 and the HWD 150 may dynamically and intelligently switch between one or more active and idle communication interfaces 115, 165 to optimize the communication channel between the console 110 and the HWD 150.

[0039] B. Computing System

[0040] Various operations described herein can be implemented on a computer system. Figure 3 A block diagram of a representative computing system 314 that can be used to implement the present disclosure is shown. In some embodiments, Figure 1 The console 110, HWD 150, or both are implemented by a computing system 314. For example, the computing system 314 can be implemented as, for example, a consumer device (e.g., a smartphone, other mobile phone, tablet computer, wearable computing device (e.g., smart watch, glasses, head mounted display), desktop computer, laptop computer) or through a distributed computing device. The computing system 314 can be implemented to provide a VR experience, an AR experience, or an MR experience. In some embodiments, the computing system 314 may include conventional computer components, such as a processor 316, a storage device 318, a network interface 320, a user input device 322, and a user output device 324.

[0041] The network interface 320 can provide a connection to a wide area network (e.g., the Internet) to which the WAN interface of the remote server system is also connected. The network interface 320 can include a wired interface (e.g., Ethernet) and / or a wireless interface that implements various radio frequency (RF) data communication standards, such as Wi-Fi, Bluetooth, or cellular data network standards (e.g., 3G, 4G, 5G, 60GHz, LTE, etc.).

[0042] User input device 322 may include any device (or devices) via which a user may provide signals to computing system 314; computing system 314 may interpret these signals as indicating a particular user request or information. User input device 322 may include any or all of the following: a keyboard; a touch pad; a touch screen; a mouse or other pointing device; a scroll wheel; a click wheel; a knob; a button; a switch; a keypad; a microphone; a sensor (e.g., a motion sensor, an eye tracking sensor, etc.), etc.

[0043] User output device 324 may include any device through which computing system 314 can provide information to a user. For example, user output device 324 may include a display to display images generated by or transmitted to computing system 314. The display may combine various image generation technologies (e.g., liquid crystal display (LCD)), light-emitting diodes (LED) including organic light-emitting diodes (OLED), projection systems or cathode ray tubes (CRT), etc. with supporting electronic devices (e.g., digital-to-analog converters or analog-to-digital converters, or signal processors, etc.). Devices such as touch screens may be used as both input devices and output devices. Output device 324 may be provided in addition to or in place of a display. Examples include indicator lights, speakers, tactile "display" devices, printers, etc.

[0044] Some embodiments include electronic components, such as microprocessors, storage devices and memories, that store computer program instructions in computer-readable storage media (e.g., non-transient computer-readable media). Many functions described in this specification can be implemented as the following process: these processes are designated as a group of program instructions encoded on a computer-readable storage medium. When these program instructions are executed by one or more processors, these program instructions cause the processor to perform the various operations indicated in these program instructions. Examples of program instructions or computer codes include machine codes, such as generated by a compiler, and files including higher-level codes executed by a computer, electronic components or microprocessors using an interpreter. Through suitable programming, processor 316 can provide various functions for computing system 314, including any functions described herein performed by a server or client, or other functions associated with a message management service.

[0045] It will be appreciated that computing system 314 is illustrative and various variations and modifications may be made. The computer system used in conjunction with the present disclosure may have other functions not explicitly described herein. In addition, although computing system 314 is described with reference to a specific block, it should be understood that these blocks are defined for the convenience of description and are not intended to imply a specific physical arrangement of component parts. For example, different blocks may be located in the same facility, in the same server rack, or on the same motherboard. In addition, these blocks do not need to correspond to physically different components. Each block may be configured to perform various operations (e.g., by programming a processor or providing a suitable control circuit), and each block may or may not be reconfigurable, depending on the manner in which the initial configuration is obtained. Each embodiment of the present disclosure may be implemented in a variety of devices, including electronic devices implemented using any combination of circuits and software.

[0046] C. Systems and Methods for Managing Power Consumption of Device Subsystems

[0047] Now refer to Figure 4 , depicted is a device 400 according to an example implementation of the present disclosure. The device 400 is shown to include various device units or subsystems 401 (e.g., processing / functional units / blocks / components) including: a central processing unit (CPU) 402; a graphics processing unit (GPU) 404; a display interface 406; a sensing unit 408; a compression unit 410; and / or various other units 412, such as a camera unit, an input / output (I / O) unit, a decoder / encoder, and / or other processing units of the device. In use, each of these device units may consume power at various rates and amounts / levels, which may depend on the specific application 414 or resource being accessed on the device 400. For example, during a video call or conference using the corresponding application 414, some units / subsystems 401 (e.g., display interface 406, camera unit, communication unit, and GPU 404) may consume more power than other units or subsystems 401 (e.g., sensing unit 406, I / O unit, etc.) based on the functions or tasks to be performed by these units. As another example, when the device 400 is executing a local game application 414, some units / subsystems 401 (e.g., display interface 406, CPU 402, GPU 404, sensing unit 408) may consume more power than other units or subsystems 401 (e.g., compression unit 410, decoder / encoder, etc.).

[0048] Some devices may include one or more hardware controllers that monitor the device's heat dissipation level or power consumption level. In the event that the heat dissipation level or power consumption level increases too quickly or exceeds a threshold, the one or more hardware controllers may generally reduce the power consumption on each device subsystem in multiple device subsystems. For example, one or more hardware controllers may reduce or save the overall power consumption of the device (e.g., reducing or saving the overall power consumption of the device by 20%), so that each device subsystem in multiple device subsystems reduces its power consumption by 20%. One or more hardware controllers may act as a protective measure to prevent damage to the device (e.g., due to thermal output / overheating, burning, etc. of the device). However, by generally reducing the power consumption on each device subsystem in multiple device subsystems, the user experience may be reduced because the overall device performance will be reduced.

[0049] According to the system and method of the present solution, the device 400 may be configured to maintain one or more constraint metric tables 426 for applications 414 that may be executed on the device or supported by the device. The constraint metric table 426 may be configured to specify a power level for a subsystem 401 of the device 400 according to a corresponding application 414 or an application type of the application 414 executed on the device 400. The device 400 may be configured to determine to operate the device 400 at a reduced power level for a first application 414 based on the condition 420 of the device 400 satisfying a thermal threshold criterion or a power threshold criterion when the device 400 is operating at a full level. The device 400 may apply the constraint metric 422 in response to determining to operate at a reduced power level. By applying the constraint metric, at least a subset of the plurality of subsystems 401 may be configured to adjust the power consumption level of the subsystem 401 according to the first constraint metric table 426 corresponding to (or configured / established for) the first application 414.

[0050] As shown in FIG. 5 , device 400 may include an operating system (OS) 416. Operating system 416 may be or include system-level software deployed or otherwise executed on device 404 that manages device hardware, software, and / or provides services for device 400. In some embodiments, operating system 416 may include / execute controller 418. Controller 418 may be part of operating system 416, or controller 418 may include / include operating system 416. In other words, controller 418 may be a processor / processing component / hardware that deploys operating system 416 or otherwise executes operating system 416. Controller 418 may be configured to execute instructions from a memory of device 400 to provide operating system 416. Controller 418 may be configured to execute instructions as part of providing operating system 416 to manage power consumption at the subsystem 401 level.

[0051] The device 400 may include one or more sensors 424. The one or more sensors 424 may be or include any device, component, element, or hardware configured to sense, monitor, measure, detect, or otherwise identify one or more various conditions 420 of the device 400. The one or more sensors 424 may be configured to identify the condition 420 of the device 400 when the subsystem 401 is executed on the device 400 or otherwise performs a function of the device 400. The one or more sensors 424 may include one or more temperature sensors 424 (e.g., thermometers) configured to identify the temperature or thermal condition / level of the device 400. The one or more sensors 424 may include one or more power sensors (e.g., power meters, current sensors configured to identify the power consumption condition of the device 400. The power consumption condition may include the overall (e.g., total) power, average power, etc. of the device 400 on some or all of the multiple subsystems 401 of the device 400.

[0052] Device 400 may be configured to execute one or more applications 414. Device 400 may be configured to execute one or more applications 414 in response to a user request (e.g., to an I / O unit or subsystem of device 400) that selects / activates an icon corresponding to application 414 or otherwise launches application 414. Device 400 may be configured to execute different types of applications 414. For example, device 400 may be configured to execute video / audio streaming applications 414, video / audio conferencing applications 414, gaming applications 414, messaging applications 414, data storage applications 414, and the like. In some embodiments, each application 414 may include or otherwise maintain information indicating an application type of application 414. For example, applications 414 may be tagged with their application types (e.g., by an application developer). When a user of device 400 installs, deploys, or otherwise executes application 414 on device 400, device 400 may be configured to determine the application type of application 414.

[0053] The controller 418 may be configured to receive, identify, or otherwise determine a condition 420 of the device 400 (e.g., temperature or thermal condition / level, application speed / response / latency, battery / power level, average / peak power consumption level / rate). The controller 418 may be configured to determine the condition 420 of the device 400 based on sensor data from one or more sensors 424 of the device 400. The controller 418 may be configured to determine the condition 420 of the device 400 when the device 400 executes / implements / supports the application 414. The controller 418 may be configured to determine the condition 420 of the device 400 when the device 400 (e.g., the subsystem 401 of the device 400) executes / implements / supports the application 414.

[0054] Controller 418 may be configured to maintain or otherwise access one or more thresholds. These thresholds may include, for example, thermal thresholds and / or power thresholds. Controller 418 may be configured to compare condition 420 of device 400 with thermal thresholds and / or power thresholds. In some embodiments, controller 418 may be configured to compare thermal conditions (e.g., heat / energy / heat output / level measured or otherwise detected by one or more temperature sensors 424) with thermal thresholds. Controller 418 may be configured to determine whether thermal conditions meet thermal threshold criteria based on the comparison. For example, thermal conditions may meet thermal threshold criteria in response to the thermal conditions (e.g., temperature) being greater than or equal to the thermal threshold.

[0055] Controller 418 may be configured to determine to run at a reduced power level for an application executing on the device. In some embodiments, controller 418 may be configured to determine to run at a reduced power level from a full (or maximum / unlimited) power level when application 414 is executed by device 400. In some embodiments, controller 418 may be configured to determine to run at a reduced power level based on a condition of device 400 compared to one or more thresholds maintained by device 400.

[0056] In some embodiments, the controller 418 may be configured to compare a power condition (e.g., measured by one or more power sensors / one or more current sensors 424 or otherwise detected) with a power threshold. The controller 418 may be configured to determine whether the power condition meets a power threshold criterion based on the comparison. For example, the power condition may meet the power threshold criterion in response to the power condition (e.g., average / peak / instantaneous power consumption, current consumption, current power consumption, etc.) being greater than or equal to a power threshold. In some embodiments, the controller 418 may be configured to determine whether a thermal threshold criterion and / or a power threshold criterion are met / conformed to / exceeded.

[0057] The controller 418 may be configured to generate, establish, set or otherwise determine the constraint metric 422. The controller 418 may be configured to determine the constraint metric 422 in response to determining to operate the device 400 at a reduced power level. The constraint metric may be a value set by the controller 418 and may be used by each of the one or more subsystems 401 to selectively adjust their power consumption levels. In some embodiments, the constraint metric 422 may be a device-wide value (e.g., a subsystem-wide value) set by the controller 418. The constraint metric 422 may be a value proportional to the amount / difference / degree of the power condition / thermal condition exceeding / exceeding the power threshold / thermal threshold, a value generated relative to these amounts / differences / degrees, or a value otherwise corresponding to these amounts / differences / degrees. For example, when the power condition exceeds the power threshold to a greater extent, the controller 418 may reduce the constraint metric 422 to a greater extent. In some embodiments, the constraint metric 422 may be a subsystem-specific value. For example, the controller 418 may be configured to calculate, set, define, generate, or otherwise determine a constraint metric 422 for each individual subsystem 401 of the device 400. The controller 418 may be configured to determine the constraint metric 422 for each subsystem 401 of the plurality of subsystems 401 based on, for example, an application 414 executing on or supported by the device 400, or an application type of the application 414 executing on or supported by the device 400.

[0058] The controller 418 may be configured to transmit, send, provide, or otherwise apply a constraint metric 422. In some embodiments, the controller 418 may be configured to apply the constraint metric 422 in response to determining to operate the device 400 at a reduced power level. In some embodiments, the controller 418 may be configured to apply the constraint metric 422 by transmitting or providing the constraint metric 422 to a single subsystem 401. In some embodiments, the controller 418 may be configured to provide the constraint metric 422 having or including an application identifier (ID) or application type of an application 414 executed on the device 400. The subsystem 401 may use the application ID and / or application type to determine, select, or otherwise identify a constraint metric table 426 that will be used, for example, to selectively adjust the power of the subsystem 401 for a particular application. The constraint metric may include / indicate an index, entry, or other lookup value for accessing information in the constraint metric table 426. In some embodiments, controller 418 may be configured to apply constraint metric 422 by setting a lookup value for a data entry corresponding to constraint metric 422 in constraint metric table 426 .

[0059] Subsystem 401 may be configured to determine a value for constraint metric 422 (e.g., in response to a value received from controller 418, in response to performing a lookup of constraint metric 422, etc.). In some embodiments, subsystem 401 may be configured to select, determine, or otherwise identify a constraint metric table 426 from a plurality of constraint metric tables 426 that will be used to select a threshold power level for a corresponding subsystem 401 and / or adjust a power consumption level of a corresponding subsystem 401. In some embodiments, constraint metric table 401 may be specific to a particular application. For example, each application 414 executable on device 400 may have a corresponding application constraint metric table 426. Subsystem 401 may be configured to determine an application 414 executing on device 400 (e.g., using an application ID received from controller 418, by querying OS 416, etc.). Subsystem 401 may be configured to select an application constraint metric table 426 for application 414 (e.g., using an application ID and matching the application ID with an ID of an application constraint metric table 426).

[0060] In some embodiments, the constraint metric table 401 may be specific to a particular type of application. FIG. 5A to FIG. 5C, depicted is a diagram showing, representing, or corresponding to different constraint metric tables 500A-500C for different application types. For example, a device 400 may maintain, include, incorporate, or otherwise access a first constraint metric table 500A for a first application type (e.g., a video conferencing application 414), a second constraint metric table 500B for a second application type (e.g., a gaming application 414), a third constraint metric table 500C for a third application type (e.g., a streaming media application 414), etc. A device 400 may maintain any number of constraint metric tables 500 for applications 414 of any number of application types that may be executed on the device 400. In some embodiments, the constraint metric tables 500 may be generated for each device 400 (e.g., by a device manufacturer) and may be loaded / programmed onto the device 400 at the time of deployment / manufacturing. In some embodiments, the constraint metric table 500 can be generated and maintained at the operating system level 416 so that the constraint metric table 500 can be updated from time to time (e.g., by updating / upgrading the OS 416 of the device 400 or as part of updating / upgrading the OS 416 of the device 400). For each constraint metric, the constraint metric table can include / indicate / specify corresponding threshold power levels for each subsystem of the device. For example, a particular constraint metric can be used to index into the constraint metric table to access / determine a corresponding set of threshold power levels for multiple subsystems. The individual threshold power (power consumption) levels for a particular subsystem can vary with the value of the constraint metric and can be represented by a threshold chart (or graph / curve). Although the constraint metrics and corresponding threshold power levels of the subsystems are similar in value to the constraint metric, the constraint metrics and corresponding threshold power levels of the subsystems can be represented by a threshold chart (or graph / curve). FIG. 5A to FIG. 5C 401. Although shown as a continuous or substantially continuous graph in FIG. 402, it should be noted that the constraint metrics and corresponding threshold power levels of the subsystems may have various step sizes or granularity levels. As described in more detail below, a given subsystem 401 may receive a constraint metric from controller 418, identify a constraint metric table corresponding to an application executed / provided by the device, and use the constraint metric as an index to identify a power threshold level for the subsystem.

[0061] like FIG. 5A to FIG. 5CAs shown, the constraint metric table 500 may include / represent / indicate subsystem-specific thresholds, which may be represented by a first threshold chart (represented by a solid line) of the first subsystem 401, a second threshold chart (represented by a dashed line) of the second subsystem 401, a third threshold chart (represented by a dashed line) of the third subsystem 401, and a fourth threshold chart (represented by a dotted line) of the fourth subsystem 401. Although the constraint metric table 500 is shown as four threshold charts, it is noted that the constraint metric table 500 may include / represent a threshold chart for each of the multiple subsystems 401 of the device 400. Each of the multiple threshold charts may indicate or include a (threshold) power level for a particular constraint metric 422. The power level may be a maximum (e.g., not to be exceeded, an upper limit, etc.) power level of the subsystem 401 for the particular constraint metric 422. The threshold power levels may be selected or otherwise defined to optimize / improve the user experience when the power of the device 400 is reduced.

[0062] Each of the plurality of subsystems 401 may be configured to identify a constraint metric table 426 from the plurality of constraint metric tables 426 based on the application type of the application 414 executed on the device 400. In some embodiments, the subsystem 401 may be configured to determine the application type of the application 414 using an application identifier of the application 414. For example, the device 400 may be configured to maintain a database or other data structure that includes an application identifier for each of the plurality of applications 414 executable / supported / accessible on the device 400 and an identifier of a corresponding constraint metric table 426 for the application 414. The device 400 may be configured to perform a lookup in the database using the application identifier to identify the corresponding identifier of the constraint metric table 426. As another example, each constraint metric table 426 may include various tags that will be used to match the application tags with the corresponding constraint metric table 426. As described above, the application 414 may be tagged by the application developer (e.g., when the application 414 is deployed). Subsystem 401 may be configured to use the tag of application 414 to match application 414 with a corresponding constraint metric table. For example, a "VIDEO CONFERENCE" tag may be added to video conferencing application 414. Similarly, a "VIDEO CONFERENCE" tag may be added to constraint metric table 426 of the video conferencing application. Subsystem 401 may be configured to identify one or more tags of application 414 (e.g., video conferencing application 414) executed on device 400, and select constraint metric table 426 for the video conferencing application in response to a tag match.

[0063] Now refer to Figure 6, depicted is a chart 600 showing an example application of a constraint metric 422 at a subsystem 401 level according to an example implementation of the present disclosure. Chart 600 may represent / illustrate threshold power levels for various subsystems at various constraint metric values. After receiving the constraint metric 422 and identifying the constraint metric table 426 for the application 414 executing on the device 400, the plurality of subsystems 401 may be configured to determine / calculate / estimate their respective power consumption levels (e.g., by determining voltage consumption and current consumption as inputs to the subsystem 401). The subsystems 401 may be configured to determine a threshold power level for the respective subsystem 401 at a corresponding constraint metric 422 (e.g., received from the controller 418 or otherwise identified by each of the plurality of subsystems 401). For example, the subsystem 401 may be configured to use an identifier (e.g., a subsystem ID) and / or the constraint metric of the subsystem 401 to perform a lookup function in the constraint metric table 426 / perform a lookup function of the constraint metric table 426 to identify or determine the threshold power level. As Figure 6 As shown and described above, each subsystem 401 may have a different threshold power level based on the specific application 414 executing / accessed / supported on the device 400 and / or based on the specific value of the constraint metric 422 .

[0064] Each subsystem 401 may be configured to compare its corresponding threshold power level with the corresponding (actual / estimated / measured) power consumption level of the subsystem 401. Thus, each subsystem 401 may make this comparison on a subsystem-by-subsystem basis. A subsystem 401 may be configured to determine whether its power consumption level exceeds a corresponding threshold power level from a constraint metric table 426 under a constraint metric 422 set by the controller 418. Figure 6 As shown, the power consumption levels of some subsystems 401 (e.g., the first subsystem, the second subsystem, and the third subsystem) may exceed the threshold power level of the subsystem 401 under the constraint metric 422 set by the controller 418, while the power consumption levels of other subsystems 401 (e.g., the fourth subsystem) may be less than the threshold power level of the subsystem 401 under the constraint metric 422 set by the controller 418.

[0065] In the case where the power consumption level of subsystem 401 is less than (or equal to) the threshold power level under constraint metric 422, subsystem 401 may be configured to operate at the current power consumption level. In this regard, when subsystem 401 is within or operating at the threshold power level, subsystem 401 may be configured to forgo adjusting any power consumption level of subsystem 401. In this way, even in the case of operating device 400 at a reduced power level, some subsystems 401 may not be implicated / affected by the reduction in power consumption.

[0066] In the case where the power consumption level of subsystem 401 is greater than the threshold power level under constraint metric 422, subsystem 401 may be configured to adjust the power consumption level of the subsystem 401. Subsystem 401 may be configured to reduce the power consumption level so that the power consumption level is less than or equal to the threshold power level under constraint metric 422. In some embodiments, multiple subsystems 401 may be configured to adjust the power consumption level differently. For example, display interface 406 subsystem 401 may be configured to adjust the power consumption level by reducing the screen resolution of the display, while compression unit 410 subsystem 401 may be configured to adjust the power consumption level by reducing the complexity / degree of encoding / decoding of compressed data. As another example, central processing unit 402 subsystem 401 may be configured to adjust the power consumption level by reducing the clock frequency, while sensing unit 408 subsystem 401 may be configured to adjust the power consumption level by reducing the sensing sampling rate. Thus, in some embodiments, each subsystem 401 may be pre-configured with steps or actions to be performed to reduce the power consumption level of the subsystem 401. Each of the plurality of subsystems 401 whose power consumption level exceeds a threshold power level can be configured to adjust its power consumption level to within its corresponding threshold, thereby reducing the overall power consumption of the device. Such an implementation can provide an application-based power management system that avoids hardware-based (e.g., global) power reduction techniques that may reduce / affect the overall user experience.

[0067] Now refer to Figure 7 , depicted is a flow chart illustrating a method 700 for managing power consumption of a device subsystem according to an example implementation of the present disclosure. Figure 7 As shown, some steps (e.g., steps 702 to 708) can be performed by the controller 418 (e.g., at the operating system 416 level), while other steps (e.g., steps 710 to 716) can be performed by the corresponding subsystem 401 at the subsystem 401 level. As a brief overview, in step 702, the controller 418 determines the initial state of the device 400. In step 704, the subsystem 401 operates at an unconstrained level. In step 706, the controller 418 determines whether the threshold criteria are met / reached. In step 708, the subsystem 401 operates at a constrained level (e.g., in response to meeting / reaching the threshold criteria). In step 710, the subsystem 401 calculates the average power. In step 712 (which can be part of step 708), the subsystem 401 determines whether its average power exceeds the power threshold. If not, the subsystem can continue its existing power consumption (step 714, which can be part of or a result of step 708). If so, the subsystem may change 401 its power consumption (step 716, which may be part of or a result of step 708).

[0068] At step 702, the controller 418 determines a condition of the device 400. In some embodiments, the controller 418 determines the condition of the device 400 when the device 400 executes the application 414. The controller 418 may determine the condition of the device (e.g., at step 704) when it is operating at an unconstrained level. In other words, step 702 and step 704 may be performed at the same time, simultaneously, in overlapping (or partially overlapping) time periods, etc. In some embodiments, the controller 418 may determine the condition using one or more various sensor measurements of the device 400. For example, the condition may be the power consumption of the device 400 over a period of time or the power consumption on the device 400 over a period of time (e.g., the power consumption on multiple subsystems 401 of the device 400), the thermal output or thermal condition of the device 400, etc. when the device 400 executes / supports the application. In other words, the condition may be or include a subsystem-wide (or overall) power consumption level of the device 400 and / or a temperature or thermal output of the device 400. The controller 418 may determine the condition based on, according to, or using sensor data from one or more sensors of the device 400 (e.g., one or more power measurement sensors, one or more thermal sensors / temperature sensors, etc.). In some embodiments, the controller 418 may determine the condition at various intervals. For example, the controller 418 may periodically determine the condition of the device 400 while the device 400 executes the application 414. In some embodiments, the controller 418 is part of the operating system 416 of the device or includes the operating system 418. In other words, the controller 418 may be implemented at the operating system level or otherwise provided.

[0069] At step 706, the controller 418 determines whether the threshold criteria are met. In some embodiments, the controller 418 may determine to operate the device 414 at a reduced power level for the first application based on the condition of the device 400 (e.g., identified at step 702) meeting at least one threshold criterion. The controller 418 may determine / predict that the condition meets the threshold criteria in response to, for example, when / if the device 400 (e.g., each of the plurality of subsystems 401 of the device 400) (e.g., at step 704) is operating at a full power level or at an unconstrained level, the temperature / thermal output / power consumption exceeds (or is equal to) a thermal threshold of the thermal threshold criterion or a power threshold of the power threshold criterion. The controller 418 may maintain the thermal threshold and / or power threshold of the device 400. When the subsystem 401 of the device 400 is executing / operating in an unconstrained manner (e.g., operating at full utilization / consumption of power), the controller 418 may compare the (e.g., actual / determined / expected) condition of the device 400 (e.g., identified at step 702) to the thermal threshold and / or power threshold.

[0070] In some embodiments, the threshold criteria may be met in response to the corresponding device power or device thermal condition either exceeding a power threshold or exceeding a thermal threshold (e.g., exceeding either a power threshold and a thermal threshold). If at step 706 the controller 418 determines that the threshold criteria are not met / reached (e.g., the device power consumption is less than the device power threshold, or the device thermal condition is less than the device thermal threshold), the method 700 may return to step 704 (e.g., where the subsystem 401 operates in an unconstrained manner). On the other hand, if at step 706 the controller 418 determines that the threshold criteria are met, the method 700 may proceed to step 708.

[0071] At step 708, at least some of the plurality of subsystems 401 may be (caused / configured to) operate at a constrained level (e.g., in response to meeting / reaching a threshold criterion, such as exceeding a power threshold / thermal threshold). In some embodiments, the controller 418 may determine the constraint metric to apply in response to determining to operate at a reduced power level. In some embodiments, the controller 418 may determine the constraint metric based on a difference between a threshold and a condition (e.g., a difference between a device power consumption level and a device power threshold, or a difference between a device thermal condition / temperature condition and a device temperature threshold). In some embodiments, the constraint metric may be inversely proportional to the difference. For example, as the difference increases in a positive direction (e.g., the device power consumption level increases beyond the device power threshold), the controller 418 may proportionally reduce / tighten the constraint metric (the value of). The controller 418 may apply the constraint metric in response to determining to operate at a reduced power level. The controller 418 may apply the constraint metric by setting a value used by each of the plurality of subsystems 401 to selectively adjust its power consumption level. The controller 418 may apply a constraint metric that is agnostic to the individual subsystems 401. For example, the controller 418 may apply a global (e.g., device-wide) constraint metric or value to each of the plurality of subsystems 401, and the subsystems 401 may use the global constraint metric to adjust their power consumption. In at least some of these embodiments, the constraint metric may be a device-wide value set by the controller 418 and may be used by at least some of the subsystems 401 in conjunction with a specific constraint metric table corresponding to an application executed on the device to adjust the power consumption of the subsystem 401.

[0072] In some embodiments, the controller 418 can set, identify, or otherwise determine a constraint metric based on an application executed, deployed, or otherwise supported by the device 400. For example, the controller 418 can include one or more constraint metrics for different applications or for applications of different application types that can be executed on the device. The constraint metric can be pre-calibrated or otherwise pre-configured for the application (e.g., to save power consumption at the subsystem level or otherwise reduce power consumption). The controller 418 can determine an application (or an application type of the application) executed on the device and select a constraint metric corresponding to the application / application type.

[0073] In some embodiments, the controller 418 may set, identify or otherwise determine the constraint metric based on the difference between the condition of the device and the corresponding threshold. The controller 418 may calculate the constraint metric based on the condition of the device 400, which is separate from the application executed on the device 400 or unknown to the application. In other words, when the device 400 executes or otherwise deploys the application, the controller 418 may determine the condition of the device and use the condition to determine or calculate the constraint metric. However, the controller 418 may not consider the application (or application type) as part of determining the constraint metric. The controller 418 may set the constraint metric for each of the multiple subsystems and provide (for example, alone or in combination with setting the constraint metric) an indication of the application (or application type of the application) executed on the device 400. In this sense, the constraint metric may be the following value or index: the value or index is used by the subsystem 401 to selectively adjust the power consumption level of the subsystem 401 using the constraint metric and the constraint metric table corresponding to the application executed on the device / the application type of the application.

[0074] In some embodiments, the controller 418 may apply the constraint metric by transmitting, sending, or otherwise providing the constraint metric to each of the plurality of subsystems 401 of the device 400. In some embodiments, the device 400 may access, include, or otherwise maintain one or more constraint metric tables for applications executable / supported on the device 400. For example, the application may be executed on the device 400 (e.g., on a CPU of the device 400), may be provided to the device in whole or in part from one or more remote sources, or may otherwise be executed on the device 400, supported by the device 400, or otherwise provided by the device 400. The constraint metric table may specify corresponding power levels for the plurality of subsystems 401 of the device 400. The constraint metric table may be specific to the application type of the corresponding application or one or more applications that may be executed on the device 400. In some embodiments, the device 400 may maintain an application-specific constraint metric table that may be used for a specific / individual application. In some embodiments, device 400 may maintain an application-type-specific constraint metric table that may be used for several applications 414 that have / share or are characterized by a common application type. FIG. 5A to FIG. 5C As described, the device 400 may maintain several constraint metric tables for different applications / application types. The constraint metric table may specify power levels under different constraint metrics (e.g., constraint metric values) for different subsystems 401. For different applications / application types, the power level may be pre-calibrated or otherwise pre-configured for each of the multiple subsystems 401. For example, assuming that the same constraint metric is applied to two different applications (e.g., one application 414 is executed at one time, and then different applications 414 are executed later at different times) at two points in time, a given subsystem 401 may have different power levels (or power threshold levels) based on different applications 414 executed on the device 400 at different times, respectively. In other words, the device 400 may maintain a first constraint metric table and a second constraint metric table, the first constraint metric table specifying a first power level for the subsystem for the first application 414, and the second constraint metric table specifying a second power level for the same subsystem for the second application 414.

[0075] As described in more detail below, multiple subsystems 401 of the device can use constraint metrics and constraint metric tables corresponding to applications 414 executed on the device 400 to selectively modify their respective power consumption levels. Multiple subsystems 401 can each identify (e.g., from one or more constraint metric tables maintained by the device 400) a constraint metric table corresponding to an application 414 executed / running / supported on the device. In some embodiments, the subsystem 401 can identify the constraint metric table in response to receiving a constraint metric from the controller 418. In some embodiments, the subsystem 401 can identify the constraint metric table in response to the application 414 being launched (e.g., by a user of the device 400) and / or constraint metrics. As described above, the subsystem 401 can identify the constraint metric table using a lookup of an application name / application identifier of the application 414, using a tag of the application 414, etc.

[0076] In step 710, the subsystem 401 may calculate the average power. In some embodiments, the first subsystem 401 calculates the average power / peak power / instantaneous power (e.g., average power consumption / peak power consumption / instantaneous power consumption) of the first subsystem 401. In some embodiments, the first subsystem 401 may calculate the average power of the first subsystem 401 over a time period (e.g., a few seconds, a few minutes, etc.). The first subsystem 401 may calculate the average power of the first subsystem 401 using the current consumption and the voltage level of the first subsystem 401 over the time period. Note that although each of the plurality of subsystems 401 is described as the first subsystem 401 hereinafter, each of the plurality of subsystems 401 may perform steps 710 to 716 separately (e.g., in parallel / simultaneously / etc.).

[0077] At step 712, the subsystem 401 may determine whether its average power / peak power / instantaneous power exceeds a power threshold. In some embodiments, the first subsystem 401 may identify a power threshold corresponding to the first subsystem 401 and a constraint metric (e.g., set by the controller at step 708 as described above). For example, the first subsystem 401 may identify the power threshold by performing a lookup in a constraint metric table corresponding to the identified application 414 executed on the device 400. The first subsystem 401 may perform a lookup using the constraint metric set by the controller 418 and an identifier of the first subsystem 401 to identify a power level corresponding to the first subsystem 401. The first subsystem 401 may compare the average power / peak power / instantaneous power (e.g., determined for the first subsystem 401 at step 710) with a threshold power level from the constraint metric table.

[0078] If, at step 712, for the first subsystem, the average power / peak power / instantaneous power is within the threshold power level from the constraint metric table (e.g., less than or equal to the threshold power level), the first subsystem 401 can continue to operate with the existing power consumption or without constraints on its power consumption (step 714). At this point, the first subsystem 401 can determine that the current power consumption level is within the power level of the first subsystem specified in the constraint metric table. On the other hand, if, at step 712, for the first subsystem, the average power / peak power / instantaneous power is outside the threshold power level from the constraint metric table (e.g., greater than the threshold power level), the first subsystem 401 can change, modify, update, reduce, constrain or otherwise modify the power consumption level according to the threshold power level specified for the first subsystem 401 in the constraint metric table (step 716). In some embodiments, each subsystem 401 can modify its respective power consumption level in different ways depending on the function performed by the respective subsystem 401.

[0079] As described above, each of the plurality of subsystems 401 may perform steps 710 to 716 in response to the controller 418 setting / assigning / transmitting the constraint metric. Since the constraint metric table specifies different power levels for each of the plurality of subsystems 401 according to the application 414 executed on the device 400 / the application type of the application 414, each subsystem 401 may be affected to a different degree. For example, a given constraint metric may cause a first subsystem 401 of the device 400 to adjust the power consumption level of the first subsystem to a different degree (e.g., percentage or absolute amount) than a second subsystem 401 of the device according to the application 414 executed on the device. For example, one subsystem 401 may not adjust the power consumption level of the subsystem 401 based on the constraint metric and the corresponding power level from the constraint metric table of the application 414, while another subsystem 401 may reduce the power consumption level of the other subsystem based on the same constraint metric (because the power consumption level of the subsystem 401 in this example will exceed the power level from the constraint metric table).

[0080] Now that some illustrative embodiments have been described, it is apparent that the foregoing, which has been presented as examples, is exemplary and not limiting. Specifically, although many of the examples presented herein involve specific combinations of method actions or system elements, these actions and these elements may be combined in other ways to achieve the same purpose. The actions, elements, and features discussed in conjunction with one embodiment are not intended to be excluded from other embodiments or similar roles in the embodiments.

[0081] The hardware and multiple data processing components for implementing the various processes, operations, illustrative logic, logic blocks, modules and circuits described in conjunction with the embodiments disclosed herein can be implemented or executed using the following components designed to perform the functions described herein: a general-purpose single-chip processor or a general-purpose multi-chip processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic, a discrete hardware component, or any combination thereof. A general-purpose processor can be a microprocessor, or any conventional processor, controller, microcontroller or state machine. The processor can also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a combination of multiple microprocessors, one or more microprocessors in combination with a DSP core, or any other such configuration. In some embodiments, specific processes and methods can be performed by circuits dedicated to a given function. The memory (e.g., memory, storage unit, storage device, etc.) may include one or more devices (e.g., random access memory (RAM), read-only memory (ROM), flash memory, hard disk storage, etc.) for storing data and / or computer code, which is used to complete or facilitate the various processes, layers and modules described in the present disclosure. The memory may be or include volatile memory or non-volatile memory, and may include database components, object code components, script components, or any other type of information structure for supporting the various activities and information structures described in the present disclosure. According to an exemplary embodiment, the memory is communicatively connected to the processor via a processing circuit and includes computer code for executing (e.g., by a processing circuit and / or a processor) one or more processes described herein.

[0082] The present disclosure contemplates a variety of methods, systems, and program products on any machine-readable medium for implementing various operations. The various embodiments of the present disclosure may be implemented using an existing computer processor, or may be implemented by a dedicated computer processor for a suitable system that is combined for this and other purposes, or may be implemented by a hardwired system. The various embodiments within the scope of the present disclosure include program products that include machine-readable media for carrying or storing machine-executable instructions or data structures thereon. Such machine-readable media may be any available medium that can be accessed by a general-purpose computer or a special-purpose computer, or other machine with a processor. As an example, such machine-readable media may include: RAM; ROM; Erasable Programmable Read-Only Memory (EPROM); Electronic Erasable Read-Only Memory (EEPROM); or other optical disk storage, magnetic disk storage; or other magnetic storage device; or any other medium that can be used to carry or store the desired program code in the form of machine-executable instructions or data structures, and can be accessed by a general-purpose computer or a special-purpose computer, or other machine with a processor. Each combination of the above is also included in the scope of machine-readable media. Machine-executable instructions comprise, for example, instructions and data which cause a general purpose computer, special purpose computer, or special purpose processing machines to perform a certain function or group of functions.

[0083] The words and terms used herein are for descriptive purposes and should not be considered limiting. The use of "comprising," "including," "having," "containing," "involving," "characterized by," "characterized by," and variations thereof herein is meant to encompass the items listed thereafter, their equivalents and additions, and including alternative embodiments specifically constructed from the items listed thereafter. In one embodiment, the systems and methods described herein are composed of one, various combinations of more than one, or all of the described elements, actions, or components.

[0084] Any reference to an embodiment or element or action of the system and method mentioned herein in the singular may also encompass an embodiment including a plurality of these elements, and any reference to any embodiment or element or action herein in the plural may also encompass an embodiment including only a single element. Reference in the singular or plural form is not intended to limit the system or method of the present disclosure, their parts, actions or elements to a singular configuration or a plural configuration. Reference to any action or element based on any information, action or element may include that the action or element is based at least in part on an embodiment of any information, action or element.

[0085] Any embodiment disclosed herein may be combined with any other embodiment or example, and references to "an embodiment," "some embodiments," or "an embodiment," etc. are not necessarily mutually exclusive, but are intended to indicate that a particular feature, structure, or characteristic described in conjunction with the embodiment may be included in at least one embodiment or example. These terms as used herein do not necessarily all refer to the same embodiment. Any embodiment may be combined, inclusively or exclusively, with any other embodiment in any manner consistent with the various aspects and embodiments disclosed herein.

[0086] Where technical features in the drawings, detailed description or any claims are followed by reference numerals, these reference numerals have been included to increase the intelligibility of the drawings, detailed description and claims. Thus, the presence or absence of these reference numerals has no limiting effect on the scope of any claim element.

[0087] Without departing from the characteristics of the systems and methods described herein, the systems and methods described herein may be implemented in other specific forms. Unless otherwise expressly noted, references to terms of "approximately," "about," "substantially," or other degrees include a change of plus / minus 10% (+ / -10%) from a given measurement, unit, or range. The coupled elements may be directly electrically, mechanically, or physically coupled to each other, or may be electrically, mechanically, or physically coupled to each other through intermediate elements. Therefore, the scope of the systems and methods described herein is indicated by the appended claims rather than the preceding description, and changes within the meaning and scope of the equivalents of the claims are included therein.

[0088] The term "coupled" and variations thereof include two members being directly or indirectly connected to one another. Such connection may be constant (e.g., permanent or fixed) or movable (e.g., removable or releasable). Such connection may be achieved by the two members being directly coupled to one another or coupled to one another, by the two members being coupled to one another using a separate intermediate member, and by any additional intermediate member being coupled to one another, or by the two members being coupled to one another using an intermediate member that is integrally formed as a single, unitary body with one of the two members. If "coupled" or variations thereof are modified by additional terms (e.g., directly coupled), the general definition of "coupled" provided above is modified by the plain language meaning of the additional terms (e.g., "directly coupled" means the connection of two members without any separate intermediate member), thereby producing a narrower definition than the general definition of "coupled" provided above. Such coupling may be mechanical, electrical, or fluidic.

[0089] References to "or" may be interpreted as inclusive, such that any term described using "or" may mean any of a single, more than one, and all of all of the described terms. References to "at least one of 'A' and 'B'" may include only 'A', only 'B', and both 'A' and 'B'. Such references used in conjunction with "including" or other public terms may include additional items.

[0090] Without departing substantially from the teachings and advantages of the subject matter disclosed herein, the elements and actions described may be modified, such as variations in size, dimensions, structure, shape, and proportion of various elements, variations in parameter values, mounting arrangements, use of materials, colors, orientations. For example, an element shown as integrally formed may be composed of multiple parts or elements, the positions of which may be reversed or otherwise changed, and the nature or number or position of discrete elements may be altered or varied. Other substitutions, modifications, changes, and omissions may also be made in the design, operating conditions, and arrangement of the disclosed elements and operations without departing from the scope of the present disclosure.

[0091] References herein to the positions of elements (e.g., "top," "bottom," "above," "below") are only used to describe the orientation of the various elements in the drawings. According to other exemplary embodiments, the orientation of the various elements may be different, and these variations are intended to be encompassed by the present disclosure.

Claims

1. A method comprising: maintaining, by a device, one or more constraint metric tables for applications executable on the device, each of the one or more constraint metric tables specifying a respective power level for a plurality of subsystems of the device according to a respective application or a type of the respective application; determining, by the device, to operate the device at a reduced power level for a first application based on a condition of the device satisfying at least one of a thermal threshold criterion or a power threshold criterion when the device is operating at a full power level; as well as A constraint metric is applied by the device in response to determining to operate at the reduced power level such that a subset of the plurality of subsystems adjusts power consumption levels according to a first constraint metric table corresponding to the first application.

2. The method according to claim 1, wherein: Applying the constraint metric includes transmitting, by a controller of the device, the constraint metric to each of the plurality of subsystems of the device.

3. The method according to claim 2, wherein: The controller is part of or includes an operating system for the device.

4. The method according to claim 1, further comprising: The first constraint metric table of the one or more constraint metric tables is identified, by the first subsystem, based on at least one of: the first application; or the measure of said constraint applied; as well as The power consumption level of the first subsystem is modified by the first subsystem according to the power level specified for the first subsystem in the first constraint metric table.

5. The method according to claim 4, wherein: The power level is a first power level of the first subsystem, the method further comprising: identifying, by a second subsystem, the first constraint metric table; and A determination is made, by the second subsystem, that a current power consumption level of the second subsystem is within a second power level specified for the second subsystem in the first constraint metric table.

6. The method according to claim 1, wherein: The one or more constraint metric tables include a first constraint metric table for a first application and a second constraint metric table for a second application, wherein the first constraint metric table specifies a first power level for a first subsystem and the second constraint metric table specifies a second power level for the first subsystem, wherein the second power level is different from the first threshold power level.

7. The method according to claim 1, wherein: The first constraint metric table is associated with a plurality of applications having the same application type as the first application.

8. The method according to claim 1, wherein: The constraint metric causes a first subsystem among the multiple subsystems to adjust the power consumption level of the first subsystem by a first degree; and causes a second subsystem not to adjust the power consumption level of the second subsystem, or to adjust the power consumption level of the second subsystem by a second degree, the second degree being different from the first degree.

9. The method according to claim 1, wherein: When the device is operating at the full power level, the condition satisfies at least one of the thermal threshold criteria or the power threshold criteria including: When the device is operating at the full power level, the power consumption of the device is greater than or equal to a power threshold, or the temperature or heat output of the device is greater than or equal to a thermal threshold.

10. The method according to claim 1, wherein: The multiple subsystems include at least one of the following: an audio subsystem; a camera subsystem; a sensor subsystem; a communication subsystem; a display unit subsystem; a central processing unit (CPU) subsystem; or a graphics processing unit (GPU) subsystem.

11. A device comprising: Multiple subsystems; one or more constraint metric tables for applications executable on the device, each of the one or more constraint metric tables specifying a respective power level for one or more of the plurality of subsystems based on a respective application or an application type of the respective application; as well as One or more processors; the one or more processors are communicatively coupled to the plurality of subsystems, the one or more processors being configured to: determining to operate the device at a reduced power level for a first application based on a condition of the device satisfying at least one of a thermal threshold criterion or a power threshold criterion when the device is operating at a full power level; as well as A constraint metric is applied in response to determining to operate the device at the reduced power level such that a subset of the plurality of subsystems adjusts power consumption levels according to a first constraint metric table corresponding to the first application.

12. The device according to claim 11, wherein The one or more processors are further configured to transmit the constraint metric to each subsystem of the plurality of subsystems of the device.

13. The device according to claim 11, wherein: The first subsystem of the plurality of subsystems is configured as: identifying the constraint metric table of the one or more constraint metric tables based on the first application; as well as The power consumption level is modified according to the power level specified for the first subsystem in the first constraint metric table.

14. The device according to claim 13, wherein: The power level is a first power level of the first subsystem, and wherein a second subsystem of the plurality of subsystems is configured to: identifying the first constraint metric table; and A determination is made that a current power consumption level of the second subsystem is within a second power level specified for the second subsystem in the first constraint metric table.

15. The apparatus according to claim 11, wherein: The one or more constraint metric tables include a first constraint metric table for a first application and a second constraint metric table for a second application, wherein the first constraint metric table specifies a first power level for a first subsystem and the second constraint metric table specifies a second power level for the first subsystem, wherein the second power level is different from the first threshold power level.

16. The apparatus according to claim 11, wherein: The constraint metric table is associated with a plurality of applications having the same application type as the first application.

17. The apparatus according to claim 11, wherein: The constraint metric causes a first subsystem among the multiple subsystems to adjust the power consumption level of the first subsystem by a first degree, and causes a second subsystem to not adjust the power consumption level of the second subsystem or to adjust the power consumption level of the second subsystem by a second degree, the second degree being different from the first degree.

18. The apparatus according to claim 11, wherein: When the device is operating at the full power level, the condition satisfies at least one of the thermal threshold criteria or the power threshold criteria including: When the device is operating at a full power level, the power consumption of the device is greater than or equal to a power threshold, or the temperature or heat output of the device is greater than or equal to a thermal threshold.

19. The apparatus according to claim 11, wherein: The multiple subsystems include at least one of the following: an audio subsystem; a camera subsystem; a sensor subsystem; a communication subsystem; a display unit subsystem; a central processing unit (CPU) subsystem; or a graphics processing unit (GPU) subsystem.

20. A non-transitory computer-readable medium storing instructions that, when executed by one or more processors of a device, cause the one or more processors to: Execute an operating system of the device, the operating system being configured to: determining to operate the device at a reduced power level for a first application based on a condition of the device satisfying at least one of a thermal threshold criterion or a power threshold criterion when the device is operating at a full power level; and A constraint metric is applied in response to determining to operate the device at the reduced power level such that a subset of the plurality of subsystems of the device adjust power consumption levels according to a first constraint metric table corresponding to the first application.