Memory Device History Table Segmentation for Pre-Pulse Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Non-volatile memory devices face challenges in managing initial and subsequent core operations effectively, leading to potential degradation due to differing charge potential differences during pre-pulse periods, which affects reliability and data processing speed.
Innovation Solution
A memory device with a history table that determines the type of core operation based on whether a memory block is untouched or touched, applying distinct pre-pulse periods to manage initial and subsequent operations separately, thereby optimizing voltage levels and preventing hot carrier injection.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If a uniform pre-pulse period is applied to all memory block operations, then device complexity is reduced, but reliability deteriorates due to hot carrier injection in initial operations
Solution Approach 1:
The patent segments memory operations into two distinct types: initial operations for untouched memory blocks and subsequent operations for touched memory blocks. A history table tracks the operation status of each memory block, enabling the system to apply different pre-pulse periods appropriate to each operation type, thereby preventing hot carrier injection while maintaining manageable complexity through systematic categorization.
Solution Approach 2:
The patent implements preliminary action by checking the history table before executing core operations to determine whether a memory block requires initial operation treatment. This advance detection allows the system to apply appropriate pre-pulse periods before the actual data operations, preventing reliability issues before they occur.
2Reliability
If different pre-pulse periods are applied to initial and subsequent operations, then reliability is improved, but device complexity increases due to history table management
Solution Approach 1:
The history table implements self-service by automatically tracking the operation status of memory blocks and providing this information to the control logic. The system updates the history table itself during operations, eliminating the need for external tracking mechanisms and reducing overall system complexity despite the enhanced operational control.
3Ease of operation
If initial operations are performed without distinction, then ease of operation is maintained, but degradation occurs due to hot carrier injection
Solution Approach 1:
The history table serves as an intermediary between the control logic and memory blocks, mediating the determination of operation types. This intermediary component enables the system to distinguish between initial and subsequent operations without complicating the overall operation flow, as the history table automatically provides the necessary classification information.
4Productivity
If data processing speed is prioritized over reliability, then productivity is improved, but degradation increases due to insufficient pre-pulse period management
Solution Approach 1:
The patent applies parameter changes by adjusting the pre-pulse period duration based on the operation type determined from the history table. Initial operations receive extended pre-pulse periods to prevent hot carrier injection, while subsequent operations use standard pre-pulse periods, thereby optimizing both reliability and data processing speed through dynamic parameter adjustment.
Data Source
AI summary
Disclosed is a memory device which includes a history table and communicates with a storage controller. A method of operating the memory device includes receiving a first request indicating a first core operation of a first memory block from the storage controller, determining whether history data of the first memory block have a first value or a second value, with reference to the history table, in response to the first request, when it is determined that the history data of the first memory block have the first value, performing the first core operation corresponding to a first type on the first memory block, and after performing the first core operation corresponding to the first type on the first memory block, updating the history data of the first memory block in the history table from the first value to the second value.