Selective Data Recovery for Power State Latency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current power management systems face high exit latency when transitioning from non-operational power states, particularly in battery-powered devices, where L2 resume latencies are too high and L1 power savings are insufficient for rapid and frequent power state switching.

Innovation Solution

The solution involves identifying recently utilized data in databases and storing a recovery code before transitioning to a non-operational power state, allowing only specific data to be recovered upon returning to an operational state, rather than recovering the entire database, thereby reducing latency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of time

If all data is stored in always-on memory for rapid recovery, then exit latency is reduced, but power consumption increases

Engineering Contradiction:
Improveexit latencyVSAvoidpower consumption
Core Design Contradiction:
Loss of timeVSUse of energy by moving object

Solution Approach 1:

The patent segments the data storage and recovery process by dividing data into two categories: frequently accessed data stored in always-on memory for rapid recovery, and less frequently accessed data stored in power-off memory. A recovery code identifies which specific data portions need to be recovered, enabling selective recovery rather than recovering entire databases. This segmentation allows the system to reduce exit latency for critical data while avoiding the power consumption penalty of keeping all data in always-on memory.

Inventive Principle:
Principle #1Segmentation

2Use of energy by moving object

If L2 power state is used for deep power savings, then power consumption is reduced, but resume latency becomes too high

Engineering Contradiction:
Improvepower consumptionVSAvoidresume latency
Core Design Contradiction:
Use of energy by moving objectVSLoss of time

Solution Approach 1:

The patent applies preliminary action by pre-identifying and pre-storing frequently accessed data in always-on memory before the device transitions to the L2 power state. Additionally, a recovery code is pre-generated to identify which specific data portions will be needed upon resume. This preliminary preparation ensures that when the device wakes from L2, only the necessary data portions need to be recovered, significantly reducing resume latency while maintaining the power savings benefits of the L2 state.

Inventive Principle:
Principle #10Preliminary action

3Loss of time

If L1 power state is used for rapid switching, then resume latency is reduced, but power savings are insufficient

Engineering Contradiction:
Improveresume latencyVSAvoidpower consumption
Core Design Contradiction:
Loss of timeVSUse of energy by moving object

Solution Approach 1:

The patent introduces dynamics by creating hybrid power states (L1.1 and L1.2) that combine characteristics of both L1 and L2 states. These dynamic power states allow the device to adjust its recovery strategy based on current needs: using selective recovery from always-on memory when rapid resume is needed, or transitioning to deeper L2 states when maximum power savings are required. This dynamic approach enables the system to optimize the balance between resume latency and power consumption in real-time.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS11966613B2Selective device power state recovery method
Publication Date: 2024.04.23 SANDISK TECHNOLOGIES LLC
  • US11966613B2 patent drawing
  • US11966613B2 patent drawing
  • US11966613B2 patent drawing

AI summary

The present disclosure generally relates to reducing exit latency when transitioning from non-operational power states. Before entering a non-operational power state, specific data in databases and/or tables can be identified as being recently utilized by the host device. In addition to saving the databases and/or tables, a recovery code is also stored to identify that specific data. Upon transitioning back to an operational power state, the recovery code is detected and the specific data can be recovered rather than recovering the entire database and/or table. Data not identified in the recovery code need not be recovered from always-on memory. In so doing, when transitioning back to an operational power state, the latency will be reduced compared to a situation where all data is stored in always-on memory.