Lossless Software Reset Synchronization via Parameter Backup

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Software resets in computer systems often lead to loss of contact with connected devices, resulting in inefficient and time-consuming resynchronization, which can slow down computing operations and cause data loss due to deadlock conditions.

Innovation Solution

A method for lossless synchronization during software resets involves monitoring for reset conditions, saving relevant parameters in memory, performing software resets, and initializing components based on these parameters to ensure seamless reconnection without data loss, using a device controller and flash memory configuration.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If software reset is performed on the arrangement, then system stability and operability are improved, but contact with connected devices is lost requiring resynchronization which slows down computing operations

Engineering Contradiction:
Improvesystem stabilityVSAvoidcomputing operation speed
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent applies preliminary action by saving arrangement parameters in memory before the software reset occurs. This allows the system to restore synchronization state quickly after reset without requiring time-consuming resynchronization procedures, thus maintaining productivity while achieving reliability through necessary resets

Inventive Principle:
Principle #10Preliminary action

2Reliability

If resynchronization is performed after software reset, then device connectivity is restored, but computing operations are significantly slowed down

Engineering Contradiction:
Improvedevice connectivityVSAvoidresynchronization time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary action by storing arrangement parameters in memory before reset occurs. After reset, these pre-saved parameters are immediately restored, eliminating the need for time-consuming resynchronization procedures and reducing loss of time while maintaining device connectivity

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent uses copying by creating a backup copy of arrangement parameters in memory before reset. This copy is then restored after reset instead of performing time-consuming resynchronization, significantly reducing the time required to restore device connectivity

Inventive Principle:
Principle #26Copying

3Reliability

If traditional resynchronization procedure is used after software reset, then device and computer are resynchronized, but data loss may occur due to deadlock conditions

Engineering Contradiction:
Improvesynchronization stateVSAvoiddata loss
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The system performs preliminary action by saving arrangement parameters before reset. This ensures that the synchronization state is preserved and can be restored exactly as it was before reset, preventing data loss from deadlock conditions while maintaining reliable synchronization

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent uses copying to create a backup of arrangement parameters in memory before reset. This copy serves as a safe restoration point that prevents data loss by avoiding the deadlock conditions that can occur during traditional resynchronization procedures

Inventive Principle:
Principle #26Copying

Data Source

PatentUS10445181B2Lossless synchronization software reset
Publication Date: 2019.10.15 SANDISK TECHNOLOGIES LLC
  • US10445181B2 patent drawing
  • US10445181B2 patent drawing

AI summary

A method to perform a lossless synchronization software reset is disclosed including provisions for monitoring an arrangement for occurrence of a software reset condition; saving at least one arrangement parameter in a memory in the arrangement; performing at least one software reset on the arrangement; performing a device mount procedure; reading the at least one arrangement parameter in the memory and initializing at least one component according to the at least one arrangement parameter saved in the memory.