Process Power Management for Connected Standby Wake-Up
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional power conservation techniques in computing devices often lead to prolonged wake-up times and stale data upon transitioning from a low power state to an execution state, compromising user experience and battery life due to inefficient management of processes.
Innovation Solution
Implementing a power management classification system that assigns processes as exempt, suspendable, or throttleable based on criticality and functionality, allowing essential processes to remain active while non-critical ones are suspended or throttled, enabling quick and responsive transitions between low power states and execution states.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Use of energy by moving object
If conventional hibernation/sleep policies are implemented to conserve battery life, then power consumption is reduced, but the computing system takes a significant amount of time to reawaken and provide up-to-date functionality
Solution Approach 1:
The patent segments processes into three categories (exempt, suspendable, throttleable) based on their criticality and resource consumption characteristics. This segmentation allows selective suspension of non-critical processes while maintaining critical ones, enabling faster wake-up times without sacrificing battery life conservation.
Solution Approach 2:
The patent applies different power management treatments to different processes based on their individual characteristics. Critical processes receive exempt status and continue running, while non-critical processes are suspended or throttled. This localized quality approach optimizes both wake-up performance and power consumption on a per-process basis.
2Use of energy by moving object
If all processes are suspended to maximize power conservation, then battery life is extended, but user experience degrades due to stale data and prolonged wake-up times
Solution Approach 1:
The patent dynamically adjusts process execution states based on system conditions and process characteristics. Instead of a static all-or-nothing suspension approach, the system continuously monitors and adjusts which processes are exempt, suspendable, or throttleable, optimizing both power consumption and user experience in real-time.
Solution Approach 2:
The patent changes the operational parameters of processes by assigning different power management classifications. This parameter change allows the system to control resource allocation and process execution states, balancing power conservation with maintaining up-to-date functionality for user-facing applications.
3Speed
If critical system processes are allowed to execute during connected standby state, then wake-up time is reduced, but power consumption increases
Solution Approach 1:
The patent applies partial action by allowing only certain critical processes to execute during connected standby state while suspending or throttling non-critical ones. This selective execution of processes provides sufficient wake-up speed without the excessive power consumption that would result from allowing all processes to run.
Solution Approach 2:
The patent maintains continuity of useful action for critical processes that need to run during connected standby state, while interrupting or throttling non-essential processes. This ensures that wake-up functionality remains responsive without continuously consuming power for all system operations.
Data Source
AI summary
One or more techniques and/or systems are provided for assigning power management classifications to a process, transitioning a computing environment into a connected standby state based upon power management classifications assigned to processes, and transitioning the computing environment from the connected standby state to an execution state. That is, power management classifications, such as exempt, throttle, and/or suspend, may be assigned to processes based upon various factors, such as whether a process provides desired functionality and/or whether the process provides functionality relied upon for basic operation of the computing environment. In this way, the computing environment may be transitioned into a low power connected standby state that may continue executing desired functionality, while reducing power consumption by suspending and/or throttling other functionality. Because some functionality may still execute, the computing environment may transition into the execution state in a responsive manner to quickly provide a user with up-to-date information.