Flash Memory Exception Handling via Reserved Response Bytes

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional methods for communicating exception events in memory systems consume additional signaling time and power, reducing efficiency on the memory system interface.

Innovation Solution

Incorporating exception event information into an existing response message transmitted by the memory system, utilizing reserved bytes in a response packet to encode the event, and acknowledging its receipt by the host controller to reduce overhead and improve efficiency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If additional signaling is used to communicate exception events from memory system to host controller, then exception event information can be transmitted, but bandwidth consumption increases and system efficiency decreases

Engineering Contradiction:
Improveexception event communicationVSAvoidpower consumption
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent combines exception event information with regular data packets by utilizing reserved bytes in the existing packet structure. Instead of creating separate signaling messages, the exception information is merged into the data path, thereby eliminating additional transmissions and reducing power consumption while maintaining reliable exception communication.

Inventive Principle:
Principle #5Merging (Combining)

2Reliability

If additional signaling is used to communicate exception events from memory system to host controller, then exception event information can be transmitted, but system performance decreases due to additional overhead

Engineering Contradiction:
Improveexception event communicationVSAvoidsystem performance
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

Exception event information is merged into existing data packets using reserved bytes, eliminating the need for separate signaling transactions. This reduces protocol overhead and allows exception information to be transmitted alongside regular data operations, thereby improving system performance while maintaining reliable exception communication.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The existing data packet structure is made multi-functional by incorporating exception event information alongside regular data transmission. The reserved bytes in the packet structure serve dual purposes: carrying data when no exception occurs and carrying exception information when needed, thereby improving overall system efficiency.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Reliability

If additional messaging is used to fetch exception event information, then exception events can be reported, but bandwidth consumption increases

Engineering Contradiction:
Improveexception event reportingVSAvoidbandwidth consumption
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent merges exception event reporting with regular data transmissions by embedding exception information in the data path. Reserved bytes in existing packets are utilized to carry exception information, eliminating the need for separate messaging transactions and thereby reducing bandwidth consumption while maintaining reliable exception reporting.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS12393479B1Exception event handling in flash memory system
Publication Date: 2025.08.19 QUALCOMM INC
  • US12393479B1 patent drawing
  • US12393479B1 patent drawing
  • US12393479B1 patent drawing

AI summary

This disclosure provides systems, methods, and devices for memory systems that support exception event handling and reporting. In a first aspect, a method of exception event handling in a flash memory system includes a host memory controller receiving a response from the memory system, the response comprising user data, an indication that an exception event was encountered by the memory system, and information regarding the exception event encountered by the memory system; and transmitting an acknowledgement of receiving the indication that the exception event was encountered by the memory system. Other aspects and features are also claimed and described.