Memory Startup Checks for Incomplete Writes and Data Erasure

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing memory writing and startup methods lack security for sensitive data, fail to verify successful completion of write operations, and are vulnerable to power-down attacks that can expose unerased sensitive data.

Innovation Solution

Implement a method that verifies the last group of data written to memory, ensuring it contains only non-sensitive data, and if sensitive data is detected, performs an erasure operation followed by writing non-sensitive reference data, with metadata indicating sensitivity and validity.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the last group of data written to memory includes sensitive data, then security is improved by performing erasure operation, but the complexity of the startup process increases due to verification and conditional erasure steps

Engineering Contradiction:
ImprovesecurityVSAvoidstartup process complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent applies preliminary action by ensuring that the last group of data written to memory before power-down contains only non-sensitive data. This is achieved by implementing a write operation that checks data sensitivity and performs erasure or padding operations in advance, so that when the system restarts, no sensitive data remains in the memory buffer. The conditional erasure and padding operations are performed before the power-down event, preventing security vulnerabilities from arising during startup.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If verification of the last write operation is implemented during startup, then reliability is improved by detecting incomplete writes, but the startup time increases due to additional verification steps

Engineering Contradiction:
Improvewrite operation completion verificationVSAvoidstartup time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies feedback by implementing a verification mechanism during startup that checks whether the last write operation completed successfully. The system reads back the last written data group and verifies its integrity and completion status. Based on this feedback, the system determines whether to proceed with normal startup or to perform corrective actions such as erasure or padding operations. This feedback loop ensures data integrity while maintaining efficient startup performance.

Inventive Principle:
Principle #23Feedback

3Reliability

If sensitive data is detected in the last written group, then security is improved by performing erasure, but the productivity of the memory system decreases due to additional erasure and write operations

Engineering Contradiction:
Improvesensitive data protectionVSAvoidmemory write efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent applies the disposable principle by using non-sensitive reference data as a temporary placeholder to overwrite sensitive data in the last written group. Instead of performing complex erasure operations, the system writes non-sensitive reference data (such as zero values or predefined patterns) to the memory locations that previously contained sensitive data. This disposable approach effectively secures the sensitive data by overwriting it with inexpensive, non-sensitive data, eliminating the need for time-consuming erasure operations while maintaining security.

Inventive Principle:
Principle #27Cheap short-living objects (Disposable)

Data Source

PatentEP4614377A1Memory start-up
Publication Date: 2025.09.10 STMICROELECTRONICS INT NV
  • EP4614377A1 patent drawingFigure 1
  • EP4614377A1 patent drawingFigure 2~3
  • EP4614377A1 patent drawingFigure 4

AI summary

The present description relates to a method for verifying the writing of data in a memory comprising the following successive steps: - verifying (404) whether the last group of data written in the memory comprises at least one sensitive data item; - if said group comprises at least one sensitive data item, erasing (406) a first group of data of which at least one address is indicated in at least one first metadata item of data of said last group of data.