New Term
Terms List
| Id | Matter | Usage | Term | Definition | Doc No | Modified | Actions |
|---|---|---|---|---|---|---|---|
| 1294 | Placeholder App | Defined | scratch memory |
"Scratch memory" refers to a section of memory that temporarily stores data for use in subsequent operations.
"Scratch memory" refers to a section of memory that temporarily stores data for use in subsequent operations.
|
FSP1830 | 6/24/20, 9:17 PM | Add Term Edit Unassociate Delete |
| 1293 | Placeholder App | Defined | differentiator |
"Differentiator" refers to any hardware, software, firmware, circuit, component, module, logic, device, or apparatus configured, programmed, designed, arranged, or engineered to manage differential data and define a whole source storage block that includes fill data and a valid parity section associated with a fragmented source storage block.
"Differentiator" refers to any hardware, software, firmware, circuit, component, module, logic, device, or apparatus configured, programmed, designed, arranged, or engineered to manage differential data and define a whole source storage block that includes fill data and a valid parity section associated with a fragmented source storage block.
|
FSP1830 | 6/24/20, 9:17 PM | Add Term Edit Unassociate Delete |
| 1292 | Placeholder App | Defined | differential data |
"Differential data" refers to data used to convert an invalid parity section into a valid parity section. Based on the actions to be done to convert a fragmented source storage block into a whole source storage block, the differential data may include a number of different types of data. For example, in one embodiment, the differential data may include invalid data from a fragmented source storage block, an invalid parity section from the same fragmented source storage block, a valid parity section, and fill data that will be stored in a whole source storage block resulting from the fragmented source storage block.
"Differential data" refers to data used to convert an invalid parity section into a valid parity section. Based on the actions to be done to convert a fragmented source storage block into a whole source storage block, the differential data may include a number of different types of data. For example, in one embodiment, the differential data may include invalid data from a fragmented source storage block, an invalid parity section from the same fragmented source storage block, a valid parity section, and fill data that will be stored in a whole source storage block resulting from the fragmented source storage block.
|
FSP1830 | 6/24/20, 9:17 PM | Add Term Edit Unassociate Delete |
| 1291 | Placeholder App | Defined | circuit |
"Circuit" refers to a set of one or more electrical and/or electronic components providing one or more pathways for electrical current. In certain embodiments, a circuit may include a return pathway for electrical current, so that the circuit is a closed loop. In another embodiment, however, a set of components that does not include a return pathway for electrical current may be referred to as a circuit (e.g., an open loop). For example, an integrated circuit may be referred to as a circuit regardless of whether the integrated circuit is coupled to ground (as a return pathway for electrical current) or not. In various embodiments, a circuit may include a portion of an integrated circuit, an integrated circuit, a set of integrated circuits, a set of non-integrated electrical and/or electrical components with or without integrated circuit devices, or the like.In one embodiment, a circuit may include custom VLSI circuits, gate arrays, logic circuits, or other integrated circuits; off-the-shelf semiconductors such as logic chips, transistors, or other discrete devices; and/or other mechanical or electrical devices.A circuit may also be implemented as a synthesized circuit in a programmable hardware device such as field programmable gate array, programmable array logic, programmable logic device, or the like (e.g., as firmware, a netlist, or the like). A circuit may comprise one or more silicon integrated circuit devices (e.g., chips, die, die planes, packages) or other discrete electrical devices, in electrical communication with one or more other components through electrical lines of a printed circuit board (PCB) or the like. Each of the modules described herein, in certain embodiments, may be embodied by or implemented as a circuit.
"Circuit" refers to a set of one or more electrical and/or electronic components providing one or more pathways for electrical current. In certain embodiments, a circuit may include a return pathway for electrical current, so that the circuit is a closed loop. In another embodiment, however, a set of components that does not include a return pathway for electrical current may be referred to as a circuit (e.g., an open loop). For example, an integrated circuit may be referred to as a circuit regardless of whether the integrated circuit is coupled to ground (as a return pathway for electrical current) or not. In various embodiments, a circuit may include a portion of an integrated circuit, an integrated circuit, a set of integrated circuits, a set of non-integrated electrical and/or electrical components with or without integrated circuit devices, or the like.In one embodiment, a circuit may include custom VLSI circuits, gate arrays, logic circuits, or other integrated circuits; off-the-shelf semiconductors such as logic chips, transistors, or other discrete devices; and/or other mechanical or electrical devices.A circuit may also be implemented as a synthesized circuit in a programmable hardware device such as field programmable gate array, programmable array logic, programmable logic device, or the like (e.g., as firmware, a netlist, or the like). A circuit may comprise one or more silicon integrated circuit devices (e.g., chips, die, die planes, packages) or other discrete electrical devices, in electrical communication with one or more other components through electrical lines of a printed circuit board (PCB) or the like. Each of the modules described herein, in certain embodiments, may be embodied by or implemented as a circuit.
|
FSP1830 | 6/24/20, 9:17 PM | Add Term Edit Unassociate Delete |
| 1289 | Placeholder App | Defined | valid data |
"Valid data" refers to data of a data block that was stored by a host or other user of a storage device, and should be preserved and maintained until the host indicates that the data of the data block is no longer needed, and either can, or should be, deleted.
"Valid data" refers to data of a data block that was stored by a host or other user of a storage device, and should be preserved and maintained until the host indicates that the data of the data block is no longer needed, and either can, or should be, deleted.
|
FSP1830 | 6/24/20, 9:17 PM | Add Term Edit Unassociate Delete |
| 1285 | Placeholder App | Defined | combined XOR parity data |
"Combined XOR parity data" refers to an XOR parity data calculation that combines XOR parity data from two sets of data. In one example, data in one storage block of nonvolatile memory is combined using, for example, a bitwise exclusive or (e.g., XOR) operation, with data in a second storage block. The output of the bitwise XOR operation is combined XOR parity data. As needed, the output of the bitwise XOR operation can be combined with another set of data from a storage block to create a new set of combined XOR parity data. Based on a number of storage blocks for which XOR parity data is to be combined into combined XOR parity data, a process of successive bitwise XOR operations (termed accumulating XOR parity data) may be performed on the data of each storage block in order to generate combined XOR parity data.Thus, in one embodiment, XOR parity data from one open storage block of nonvolatile memory may be combined with XOR parity data from another, or each of a plurality of storage blocks, of nonvolatile memory to generate combined XOR parity data.
"Combined XOR parity data" refers to an XOR parity data calculation that combines XOR parity data from two sets of data. In one example, data in one storage block of nonvolatile memory is combined using, for example, a bitwise exclusive or (e.g., XOR) operation, with data in a second storage block. The output of the bitwise XOR operation is combined XOR parity data. As needed, the output of the bitwise XOR operation can be combined with another set of data from a storage block to create a new set of combined XOR parity data. Based on a number of storage blocks for which XOR parity data is to be combined into combined XOR parity data, a process of successive bitwise XOR operations (termed accumulating XOR parity data) may be performed on the data of each storage block in order to generate combined XOR parity data.Thus, in one embodiment, XOR parity data from one open storage block of nonvolatile memory may be combined with XOR parity data from another, or each of a plurality of storage blocks, of nonvolatile memory to generate combined XOR parity data.
|
FSP1830 | 6/24/20, 9:17 PM | Add Term Edit Unassociate Delete |
| 1280 | Placeholder App | Defined | data section |
"Data section" refers to one part of a storage block. A data section stores data blocks within the storage block. The data block may include XOR parity data in addition to any XOR parity data stored in a parity section associated with the data section. For example, the data block may store one or more codewords that include data and error correction code data (another form of XOR parity data) that protects the data of the codeword.The data section may be organized in a variety of ways in different embodiments. In certain embodiments, the data section includes a plurality of logical pages each made up of physical pages that span planes and memory die of a non-volatile memory array.
"Data section" refers to one part of a storage block. A data section stores data blocks within the storage block. The data block may include XOR parity data in addition to any XOR parity data stored in a parity section associated with the data section. For example, the data block may store one or more codewords that include data and error correction code data (another form of XOR parity data) that protects the data of the codeword.The data section may be organized in a variety of ways in different embodiments. In certain embodiments, the data section includes a plurality of logical pages each made up of physical pages that span planes and memory die of a non-volatile memory array.
|
FSP1830 | 6/24/20, 9:17 PM | Add Term Edit Unassociate Delete |
| 1269 | Placeholder App | Defined | fill data |
"Fill data" refers to one or more data blocks that comprise valid data and are used to replace invalid data within a storage block, such as a fragmented source storage block. Relocating fill data may include updating a physical block address associated with the logical block address for the data block that includes the fill data.
"Fill data" refers to one or more data blocks that comprise valid data and are used to replace invalid data within a storage block, such as a fragmented source storage block. Relocating fill data may include updating a physical block address associated with the logical block address for the data block that includes the fill data.
|
FSP1830 | 6/24/20, 9:17 PM | Add Term Edit Unassociate Delete |
| 1299 | Placeholder App | Defined | XOR module |
"XOR module" refers to any hardware, circuit, component, module, logic, device, or apparatus configured, programmed, designed, arranged, or engineered to compute, modify, adjust, or calculate XOR parity data. In certain embodiments, the XOR module applies a binary XOR function to two operands and produces a result which is the bitwise XOR of both operands.
"XOR module" refers to any hardware, circuit, component, module, logic, device, or apparatus configured, programmed, designed, arranged, or engineered to compute, modify, adjust, or calculate XOR parity data. In certain embodiments, the XOR module applies a binary XOR function to two operands and produces a result which is the bitwise XOR of both operands.
|
FSP1830 | 6/24/20, 9:17 PM | Add Term Edit Unassociate Delete |
| 1261 | Placeholder App | Defined | non-volatile storage media |
"Non-volatile storage media" refers to any hardware, device, component, element, or circuit configured to maintain an alterable physical characteristic (deleted) used to represent a binary value of zero or one after a primary power source is removed. Non-volatile storage media may be used interchangeably herein with the term non-volatile memory media.
"Non-volatile storage media" refers to any hardware, device, component, element, or circuit configured to maintain an alterable physical characteristic (deleted) used to represent a binary value of zero or one after a primary power source is removed. Non-volatile storage media may be used interchangeably herein with the term non-volatile memory media.
|
FSP1830 | 6/24/20, 9:17 PM | Add Term Edit Unassociate Delete |
| 1250 | Placeholder App | Defined | current mirror circuit |
"Current mirror circuit" refers to a circuit, sub-circuit, circuitry, electronic component, hardware, software, firmware, module, logic, device, or apparatus configured, programmed, designed, arranged, or engineered to mirror/copy a current through one active device by controlling the current in another active device of a circuit, keeping the output current constant regardless of loading. (search "current mirror" on Wikipedia.com March 6, 2020. Modified. Accessed May 1, 2020.)
"Current mirror circuit" refers to a circuit, sub-circuit, circuitry, electronic component, hardware, software, firmware, module, logic, device, or apparatus configured, programmed, designed, arranged, or engineered to mirror/copy a current through one active device by controlling the current in another active device of a circuit, keeping the output current constant regardless of loading. (search "current mirror" on Wikipedia.com March 6, 2020. Modified. Accessed May 1, 2020.)
|
FSP1822 | 6/24/20, 9:16 PM | Add Term Edit Unassociate Delete |
| 1247 | Placeholder App | Defined | leakage detection circuit |
"Leakage detection circuit" refers to a circuit, sub-circuit, circuitry, electronic component, hardware, software, firmware, module, logic, device, or apparatus configured, programmed, designed, arranged, or engineered to sense/detect/determine current leakage current within, or from, one or more target control lines that are tested or checked for leakage current. In one embodiment, the target control lines may comprise one or more of word lines, bit lines, NAND strings, memory cells, and the like.
"Leakage detection circuit" refers to a circuit, sub-circuit, circuitry, electronic component, hardware, software, firmware, module, logic, device, or apparatus configured, programmed, designed, arranged, or engineered to sense/detect/determine current leakage current within, or from, one or more target control lines that are tested or checked for leakage current. In one embodiment, the target control lines may comprise one or more of word lines, bit lines, NAND strings, memory cells, and the like.
|
FSP1822 | 6/24/20, 9:16 PM | Add Term Edit Unassociate Delete |
| 1245 | Placeholder App | Defined | driver circuit |
"Driver circuit" refers to a circuit, sub-circuit, circuitry, electronic component, hardware, software, firmware, module, logic, device, or apparatus configured, programmed, designed, arranged, or engineered to supply a voltage, either in analog or digital wave form, to another circuit, sub-circuit, electronic component, logic, device, or apparatus.
"Driver circuit" refers to a circuit, sub-circuit, circuitry, electronic component, hardware, software, firmware, module, logic, device, or apparatus configured, programmed, designed, arranged, or engineered to supply a voltage, either in analog or digital wave form, to another circuit, sub-circuit, electronic component, logic, device, or apparatus.
|
FSP1822 | 6/24/20, 9:16 PM | Add Term Edit Unassociate Delete |
| 1224 | Placeholder App | Defined | current control circuit |
"Current control circuit" refers to a circuit, sub-circuit, circuitry, electronic component, hardware, software, firmware, module, logic, device, or apparatus configured, programmed, designed, arranged, or engineered to supply a one or more currents from one or more current sources. In one embodiment, one or more of the one or more current sources controlled by the current control circuit may comprise variable/configurable current sources. In particular, in one embodiment, another controller, such as a storage controller, may define a current level for each of the one or more variable current sources by way of the current control circuit.
"Current control circuit" refers to a circuit, sub-circuit, circuitry, electronic component, hardware, software, firmware, module, logic, device, or apparatus configured, programmed, designed, arranged, or engineered to supply a one or more currents from one or more current sources. In one embodiment, one or more of the one or more current sources controlled by the current control circuit may comprise variable/configurable current sources. In particular, in one embodiment, another controller, such as a storage controller, may define a current level for each of the one or more variable current sources by way of the current control circuit.
|
FSP1822 | 6/24/20, 9:16 PM | Add Term Edit Unassociate Delete |
| 1213 | Placeholder App | Defined | latency data |
"Latency data" refers to data that identifies or may be used to determine a latency for an associated activity, event, or operation, such as a storage operation.
"Latency data" refers to data that identifies or may be used to determine a latency for an associated activity, event, or operation, such as a storage operation.
|
FSP1824 | 6/12/20, 2:24 PM | Add Term Edit Unassociate Delete |
| 1211 | Placeholder App | Defined | data bus |
"Data bus" refers to a communication bus used to exchange one or more of data bits between two electronic circuits, components, chips, die, and/or systems. A data bus may include one or more signal/control lines. A sender, such as a controller, may send data signals over one or more control lines of the data bus in parallel (operating as a parallel bus) or in series (operating as a serial bus). A data bus may include the hardware, control line(s), software, firmware, logic, and/or the communication protocol used to operate the data bus.Examples data buses may include 8-bit buses having 8 control lines, 16-bit buses having 16 control lines, 32-bit buses having 32 control lines, 64-bit buses having 64 control lines, and the like. Control lines may carry exclusively communication data, exclusively address data, exclusively control data, or any combination of these types of data.In one embodiment, a single data bus may be shared by a plurality of components, such as memory die. When multiple chips or memory die share a data bus, that data may be accessed or transferred by a single memory die or by all the memory die in parallel based on signals on a chip enable control line.A data bus may operate, and be configured, according to an industry standard or based on a proprietary protocol and design. Multiple control line of a data bus may be used in parallel and may latch data into latches of a destination component according to a clocking signal, data strobe signal ("DQS"), or clock, such as strobe signal. In certain embodiments, a control bus and a data bus together may form a communication bus between a sender and a receiver.
"Data bus" refers to a communication bus used to exchange one or more of data bits between two electronic circuits, components, chips, die, and/or systems. A data bus may include one or more signal/control lines. A sender, such as a controller, may send data signals over one or more control lines of the data bus in parallel (operating as a parallel bus) or in series (operating as a serial bus). A data bus may include the hardware, control line(s), software, firmware, logic, and/or the communication protocol used to operate the data bus.Examples data buses may include 8-bit buses having 8 control lines, 16-bit buses having 16 control lines, 32-bit buses having 32 control lines, 64-bit buses having 64 control lines, and the like. Control lines may carry exclusively communication data, exclusively address data, exclusively control data, or any combination of these types of data.In one embodiment, a single data bus may be shared by a plurality of components, such as memory die. When multiple chips or memory die share a data bus, that data may be accessed or transferred by a single memory die or by all the memory die in parallel based on signals on a chip enable control line.A data bus may operate, and be configured, according to an industry standard or based on a proprietary protocol and design. Multiple control line of a data bus may be used in parallel and may latch data into latches of a destination component according to a clocking signal, data strobe signal ("DQS"), or clock, such as strobe signal. In certain embodiments, a control bus and a data bus together may form a communication bus between a sender and a receiver.
|
FSP1824 | 6/12/20, 2:24 PM | Add Term Edit Unassociate Delete |
| 1166 | Placeholder App | Defined | circuitry |
"Circuitry" refers to electrical circuitry having at least one discrete electrical circuit, electrical circuitry having at least one integrated circuit, electrical circuitry having at least one application specific integrated circuit, circuitry forming a general purpose computing device configured by a computer program (e.g., a general purpose computer configured by a computer program which at least partially carries out processes or devices described herein, or a microprocessor configured by a computer program which at least partially carries out processes or devices described herein), circuitry forming a memory device (e.g., forms of random-access memory), or circuitry forming a communications device (e.g., a modem, communications switch, or optical-electrical equipment).
"Circuitry" refers to electrical circuitry having at least one discrete electrical circuit, electrical circuitry having at least one integrated circuit, electrical circuitry having at least one application specific integrated circuit, circuitry forming a general purpose computing device configured by a computer program (e.g., a general purpose computer configured by a computer program which at least partially carries out processes or devices described herein, or a microprocessor configured by a computer program which at least partially carries out processes or devices described herein), circuitry forming a memory device (e.g., forms of random-access memory), or circuitry forming a communications device (e.g., a modem, communications switch, or optical-electrical equipment).
|
FSP1824 | 6/12/20, 2:24 PM | Add Term Edit Unassociate Delete |
| 1111 | Placeholder App | Defined | correlation data structure |
"Correlation data structure" refers to a data structure configured to store one or more correlation factors and an index for identifying the correlation factor for a particular correlation between two items or things. In one embodiment, a correlation data structure may be a table, an array, a list, a linked list, portion of a memory, a database, or the like. An index for the correlation data structure for correlation factors between memory states may comprise a row identifier for a memory state of correlation data structure table and a correlated memory state may comprise a column of the correlation data structure table.
"Correlation data structure" refers to a data structure configured to store one or more correlation factors and an index for identifying the correlation factor for a particular correlation between two items or things. In one embodiment, a correlation data structure may be a table, an array, a list, a linked list, portion of a memory, a database, or the like. An index for the correlation data structure for correlation factors between memory states may comprise a row identifier for a memory state of correlation data structure table and a correlated memory state may comprise a column of the correlation data structure table.
|
5/21/20, 2:03 PM | Add Term Edit Unassociate Delete | |
| 21 | Placeholder App | Defined | Asymmetric storage media |
a storage media having different latencies for different storage operations. Many types of solid-state storage media (e.g., memory dies) are asymmetric; for example, a read operation may be much faster than a write/program operation, and a write/program operation may be much faster than an erase operation (e.g., reading the storage media may be hundreds of times faster than erasing, and tens of times faster than programming the storage media).
a storage media having different latencies for different storage operations. Many types of solid-state storage media (e.g., memory dies) are asymmetric; for example, a read operation may be much faster than a write/program operation, and a write/program operation may be much faster than an erase operation (e.g., reading the storage media may be hundreds of times faster than erasing, and tens of times faster than programming the storage media).
|
FSP1782 | 4/24/20, 7:36 AM | Add Term Edit Unassociate Delete |
| 365 | Placeholder App | Defined | Lowest temperature | FSP1796 | 4/24/20, 7:36 AM | Add Term Edit Unassociate Delete |