UFS Configuration Data Restoration During Hibernation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The existing Universal Flash Storage (UFS) standard does not specify the process for storing or restoring configuration data during hibernation, leading to inefficiencies and potential errors in power mode transitions.

Innovation Solution

A method and controller for handling configuration data using an index table to store and restore Management Information Base (MIB) attributes during hibernation, allowing flexible ordering to prevent errors, with a hardware protocol engine managing the process across different power domains.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of energy

If configuration data is stored/restored during hibernation using implementation-specific processes, then power consumption is reduced, but reliability deteriorates due to potential errors in data restoration

Engineering Contradiction:
Improvepower consumptionVSAvoidconfiguration data restoration reliability
Core Design Contradiction:
Loss of energyVSReliability

Solution Approach 1:

The patent applies preliminary action by storing configuration data in a specified format with predefined structure and restoration order before hibernation occurs. The index table is prepared in advance with attribute identifiers and restoration sequences, ensuring that when hibernation exits, the data can be restored reliably without ad-hoc processing that could introduce errors.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent changes the parameter of data organization by introducing a specific format definition that includes attribute identifiers, data types, and restoration order. This structured parameter change transforms the configuration data from implementation-specific variable formats to a standardized format that ensures reliable restoration while maintaining power efficiency.

Inventive Principle:
Principle #35Parameter changes

2Reliability

If configuration data is stored/restored using fixed processes, then reliability improves, but adaptability deteriorates due to inability to handle different data types and restoration orders

Engineering Contradiction:
Improveconfiguration data restoration reliabilityVSAvoidhandling flexibility for different attribute data
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent applies segmentation by dividing configuration data into distinct attribute items, each with its own identifier, data type, and restoration order specification. The index table segments the restoration process into discrete steps, allowing each attribute to be handled independently according to its specific requirements while maintaining overall reliability through the structured format.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces dynamics by allowing the restoration order to be specified within the data structure itself rather than being fixed externally. The index table can dynamically adjust the restoration sequence based on attribute dependencies and data types, providing adaptability for different scenarios while maintaining reliability through the predefined format constraints.

Inventive Principle:
Principle #15Dynamics

3Productivity

If configuration data restoration order is fixed, then processing efficiency improves, but reliability deteriorates due to potential errors from incorrect restoration sequences

Engineering Contradiction:
Improveconfiguration data restoration efficiencyVSAvoidrestoration correctness
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent applies preliminary action by pre-defining the restoration order within the configuration data structure itself. The index table includes restoration order specifications that are prepared in advance, allowing the restoration process to proceed efficiently in the correct sequence without requiring complex runtime decision-making or validation.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements feedback by incorporating validation mechanisms that verify the restoration process follows the specified order. The structured format includes checks that ensure attributes are restored in the correct sequence, providing feedback if the order is violated and preventing restoration errors while maintaining processing efficiency.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS12045179B2Method for handling configuration data for an interconnection protocol within hibernate operation, controller, and electronic device
Publication Date: 2024.07.23 SK HYNIX INC
  • US12045179B2 patent drawing
  • US12045179B2 patent drawing
  • US12045179B2 patent drawing

AI summary

A method for handling configuration data for an interconnection protocol within hibernation operation, a controller and an electronic device are provided. The method includes the following steps. In an electronic device, a hibernation entering indication signal indicating entering a hibernation state of the interconnection protocol is received. The electronic device has a memory and an index table, wherein the index table includes attribute identifiers corresponding to management information base (MIB) attributes, which belong to sub-layers of a link layer of the interconnection protocol and are required to be retained during hibernation. In response to the hibernation entering indication signal, MIB attribute storing is performed by a hardware protocol engine for implementing the link layer to read, for each one of the sub-layers, attribute data from the sub-layers according to the attribute identifiers from the index table sequentially and to write the attribute data sequentially to the memory. After the entering the hibernation state, the hardware protocol engine is in a power saving state or off while the memory remains on.