Term #1,161
storage controller (long)
Claim Term
storage controller (long)
Origin matter
—
Reference Case 1
FSP1824
Date Added
—
Created
6/12/20, 2:24 PM
Modified
9/11/25, 10:56 PM
Full Desc
"Storage controller" refers to any hardware, device, component, element, or circuit configured to manage data operations and/or storage operations on non-volatile memory media, and may comprise one or more processors, programmable processors (e.g., FPGAs), ASICs, micro-controllers, or the like.) A storage controller may take the form of processing circuitry, a microprocessor or processor, and a computer-readable medium that stores computer-readable program code (e.g., software or firmware) executable by the (micro)processor, logic gates, switches, an application specific integrated circuit (ASIC), a programmable logic controller, and an embedded microcontroller, or the like.In some embodiments, the storage controller is configured to store data on and/or read data from non-volatile memory media, to transfer data to/from the non-volatile memory device(s), and so on. A storage controller can have various functionality in addition to the specific functionality described herein. For example, the storage controller can format the non-volatile memory media to ensure the memory is operating properly, map out bad memory cells, and allocate spare cells to be substituted for future failed cells. Some part of memory cells may be used to hold firmware to operate the storage controller and implement other features. One example of the firmware, or modules within firmware, is a flash translation manager. In operation, when a host device needs to read data from, or write data to, the non-volatile memory media, the host device may provide a logical block address to which data is to be read/written, the storage controller, uses the flash translation manager to convert the logical block address to a physical block address in the non-volatile memory media. The storage controller can also perform various memory management functions, such as, but not limited to, wear leveling (distributing writes to avoid wearing out specific storage blocks of memory that would otherwise be repeatedly written to) and garbage collection (after a storage block is full, moving only the valid pages of data to another storage block, so the full storage block can be erased and reused).