Adaptive Storage Power Management via Dynamic Timeout Control
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Modern electronic devices face inefficiencies in power management, particularly due to unnecessary storage activation and deactivation, which can lead to increased power consumption and reduced battery life, especially when applications do not optimize storage access and power management effectively.
Innovation Solution
Implementing a dual storage power management scheme where the operating system controls storage access and power management for its requests, and a unified application-level storage access and power management component manages storage for application requests, using timeout periods and device operation events to optimize power usage.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of energy
If storage is deactivated after a fixed period of inactivity, then power consumption is reduced, but storage may be left on when unnecessary or switched off just before access is needed
Solution Approach 1:
The patent implements dynamic storage power management by transitioning from static fixed-time deactivation to adaptive timeout periods that adjust based on operational context. The system monitors operational components and modifies storage timeout settings dynamically, allowing longer timeouts when sequential operations are detected and shorter timeouts when inactivity is confirmed, thus resolving the contradiction between power savings and availability reliability
Solution Approach 2:
The system employs feedback mechanisms where operational components provide status information about their storage access patterns and operational state. This feedback enables the power management system to adjust timeout parameters in real-time based on actual usage patterns, preventing both premature deactivation and unnecessary power consumption while maintaining storage availability when needed
2Adaptability or versatility
If each application program controls storage activation independently, then application-specific power management is achieved, but erroneous maintenance of activated state by one application causes continuous power consumption
Solution Approach 1:
The patent merges individual application-level storage control with unified operating system-level coordination. While applications can request storage activation, the OS consolidates control by implementing a unified timeout management system that coordinates across all applications. This prevents individual applications from causing continuous power consumption while preserving application-specific access needs through structured request handling and timeout coordination
3Duration of action of moving object
If storage timeout period is extended to reduce power consumption, then battery life is improved, but storage remains active longer than necessary
Solution Approach 1:
The system dynamically changes the timeout parameter based on operational conditions rather than using a fixed value. When sequential storage access operations are detected, the timeout period is extended to accommodate the operational sequence, preventing premature deactivation. When inactivity is confirmed, the timeout is reduced to minimize power consumption. This adaptive parameter adjustment resolves the contradiction between extending battery life and minimizing energy loss
Data Source
AI summary
Devices and methods for storage power management that depend at least partly on the operational component requesting access to the storage. For example, an electronic device may include storage and data processing circuitry. The storage may be capable of being activated and deactivated. The data processing circuitry may be configured to include several operational components and to obtain data from the storage upon request by the operational components. Additionally, the data processing circuitry may manage when the storage is activated and deactivated. In particular, the data processing circuitry may manage when the storage is activated and deactivated according to a first storage power management scheme when a first of the operational components (e.g., an operating system component) requests the data and according to a second storage power management scheme when a second of the operational components (e.g., an application program component) requests the data.


