Nonvolatile RAM Data Management for Reboot Coherency

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Nonvolatile RAMs used as main memory in user devices face issues with data retention during power interruptions, leading to reboot coherency problems and infinite reboot failures due to retained errant data.

Innovation Solution

Implementing a data management method that designates code page data stored in a nonvolatile RAM into standby and in-use areas, allowing for temporary storage and selective invalidation of data during reboots, ensuring only errant data is reset while retaining valid data, thus preventing infinite reboot loops.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Duration of action of stationary object

If nonvolatile RAM is used as main memory to retain data during power interruption, then data retention capability is improved, but reboot coherency problems occur due to retained errant data

Engineering Contradiction:

Improvedata retention capabilityVSAvoidreboot coherency

Core Design Contradiction:

Duration of action of stationary objectVSReliability

Solution Approach 1:

The nonvolatile RAM is segmented into multiple areas: a standby area for holding code page data during power interruption, and a working area for active operations. This segmentation allows the system to retain valid data in the standby area while excluding errant data from the working area, thereby maintaining reboot coherency while preserving data retention capability.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

Different areas of the nonvolatile RAM are assigned different functional qualities: the standby area maintains data retention quality for valid code page data, while the working area provides clean slate quality for active operations. This local differentiation resolves the contradiction by allowing selective retention of only valid data during power interruption.

Inventive Principle:

Principle #3Local quality

2Duration of action of stationary object

If all code page data is retained in nonvolatile RAM during reboot, then data retention is improved, but infinite reboot failures occur due to errant data

Engineering Contradiction:

Improvedata retentionVSAvoidreboot efficiency

Core Design Contradiction:

Duration of action of stationary objectVSProductivity

Solution Approach 1:

The patent extracts errant code page data from the nonvolatile RAM during reboot operations. By identifying and removing only the problematic data while retaining valid data in the standby area, the system achieves clean reboot without losing valuable data, thereby improving reboot efficiency while maintaining data retention.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The patent converts the harmful effect of retained errant data into a beneficial selective retention mechanism. By using the standby area to retain only valid code page data and excluding errant data through the working area, the system transforms the potential harm of data retention into a benefit of selective data preservation.

Inventive Principle:

Principle #22Blessing in disguise (Convert harm into benefit)

3Speed

If code page data is copied from standby area to in-use area, then data accessibility is improved, but data management complexity increases

Engineering Contradiction:

Improvedata access speedVSAvoiddata management complexity

Core Design Contradiction:

SpeedVSDevice complexity

Solution Approach 1:

The patent implements preliminary action by pre-designating code page data as either standby or in-use during normal operation. This preliminary classification eliminates the need for complex real-time data management during reboot, as the system simply needs to transfer data according to pre-established designations, thereby reducing operational complexity while maintaining fast access.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent introduces dynamic data management through the ability to switch code page data between standby and in-use areas based on system state. This dynamic reconfiguration allows the system to adapt data locations to current needs, improving access speed when required while managing complexity through automated state-based transitions.

Inventive Principle:

Principle #15Dynamics

Data Source

PatentUS9110784B2Nonvolatile random access memory and data management method

Publication Date: 2015.08.18 SAMSUNG ELECTRONICS CO LTD

AI summary

A data management method for a main memory including a memory controller and a nonvolatile RAM includes; designating code page data temporarily stored in a standby area of the nonvolatile RAM as set, copying the code page data from the standby area to an in-use area of the nonvolatile RAM, designating the code page data stored in the in-use area as reset, and thereafter, during rebooting of a user device incorporating the main memory, invalidating the reset code page data while retaining the set code page data in the nonvolatile RAM.