# Patent application title: RESOLVING TRAPPING SETS

##
Inventors:
Chandra C. Varanasi (Broomfield, CO, US)
Chandra C. Varanasi (Broomfield, CO, US)

Assignees:
MICRON TECHNOLOGY, INC.

IPC8 Class: AH03M1311FI

USPC Class:
714758

Class name: Digital data error correction forward correction by block code error correcting code with additional error detection code (e.g., cyclic redundancy character, parity)

Publication date: 2014-01-16

Patent application number: 20140019824

Sign up to receive free email alerts when patent applications with chosen keywords are published SIGN UP

## Abstract:

Apparatuses and methods for resolving trapping sets are provided. One
example method can include attempting to decode a codeword using initial
values for confidence levels associated with digits of the codeword. For
a trapping set, the confidence levels associated with the digits
corresponding to a failed parity check are adjusted. The method further
includes attempting to decode a codeword using the adjusted value for the
confidence levels of the digits corresponding to the failed parity check.## Claims:

**1.**A method for resolving trapping sets, comprising: attempting to decode a codeword using initial values for confidence levels associated with digits of the codeword; adjusting, for a trapping set, the confidence levels associated with digits corresponding to a failed parity check to a no confidence value; and attempting to decode the codeword using the unchanged digits of the codeword corresponding to the failed parity check and the adjusted values for the confidence levels of the digits corresponding to the failed parity check, wherein the no confidence value is midway between full confidence values.

**2.**The method of claim 1, wherein attempting to decode a codeword using initial values for confidence levels associated with digits includes processing the digits in a low-density parity-check (LDPC) decoder for a first plurality of iterations that each result in at least one failed parity check.

**3.**The method of claim 1, further comprising determining initial values for confidence levels associated with respective digits of a codeword.

**4.**The method of claim 3, wherein determining initial values for confidence levels associated with digits of a codeword includes determining initial values based on values of the digits.

**5.**The method of claim 3, wherein determining the initial values based on values of the digits includes setting the initial value for the confidence level to +1 for a digit sensed as a first data state, and setting the initial value for the confidence level to -1 for a digit sensed as a second data state.

**6.**The method of claim 3, wherein determining the initial values based on values of the digits includes setting the initial value for the confidence level to a first value for a digit sensed as a first data state, and setting the initial value for the confidence level to a second value for a digit sensed as a second data state.

**7.**The method of claim 6, wherein determining the initial value for the confidence level includes sending the initial value for the confidence level to +1 for a digit sensed as a zero data state, sending the initial value for the confidence level to -1 for a digit sensed as a one data state, and wherein adjusting the confidence levels includes adjusting the confidence levels associated with digits corresponding to the failed parity check to zero.

**8.**The method of claim 6, wherein adjusting the confidence levels associated with the digits corresponding to a failed parity check includes setting the confidence level associated with each of the digits corresponding to the failed parity check to a value midway between the first and second values.

**9.**The method of claim 8, wherein adjusting the confidence levels associated with the digits corresponding to a failed parity check includes setting the confidence levels associated with the digits corresponding to the failed parity check to zero.

**10.**The method of claim 3, wherein determining initial values for confidence levels includes computing a log-likelihood ratio (LLR) as LLR = log ( P ( 0 ) P ( 1 ) ) , ##EQU00015## where P(0) is a probability that a particular digit is a zero data state, and P(1) is a probability that the particular digit is a one data state.

**11.**The method of claim 10, further comprising sensing the digits from a memory, wherein determining initial values for confidence levels includes setting P(0)=1 and P(1)=0 for a digit sensed having a zero data state, and setting P(0)=0 and P(1)=1 for a digit sensed having a one data state.

**12.**The method of claim 1, wherein adjusting the confidence levels includes adjusting the confidence levels associated with digits corresponding to the failed parity check to a zero value.

**13.**The method of claim 1, wherein attempting to decode the codeword using initial values includes attempting to decode the codeword for up to a particular number of iterations using the initial values.

**14.**The method of claim 1, wherein adjusting the confidence levels includes adjusting the confidence levels associated with the digits corresponding to the failed parity check after attempting to decode the codeword a particular number of iterations using the initial values.

**15.**The method of claim 1, wherein adjusting the confidence levels associated with the digits corresponding to a failed parity check includes adjusting the confidence levels associated with the digits corresponding to the failed parity check for a trapping set corresponding to a Tanner graph having a quantity of failed c-nodes that is less than a quantity of failed v-nodes.

**16.**A method for resolving trapping sets, comprising: initializing a low-density parity-check (LDPC) decoder with initial values of confidence levels for digits of a codeword; evaluating a number of parity checks based on the digits of a codeword; attempting to correct errors in digits of the codeword associated with a failed parity check using the initial values of confidence levels; adjusting, after a particular number of iterations and for a trapping set, confidence levels associated with the digits corresponding to the failed parity check to a no confidence value; and attempting to decode the codeword using the unchanged digits of the codeword corresponding to the failed parity check and the adjusted confidence levels for the digits corresponding to the failed parity check, wherein the no confidence value is midway between full confidence values.

**17.**The method of claim 16, wherein evaluating parity checks includes determining, for each digit, if a present value of the vector corresponding to the digit is less than zero, then setting a decision indication to -1, or if the present value of the vector corresponding to the digit is not less than zero, then setting the decision indication to

**1.**

**18.**The method of claim 17, wherein evaluating parity checks includes checking whether all parity checks result in even parity based on the determined decision indications, where a quantity of parity checks equals a quantity of parity digits in the codeword in excess of n.

**19.**The method of claim 18, wherein evaluating parity checks includes verifying, for each of the parity checks, even parity by multiplying the determined decision indications column numbers that have a 1 in a parity check matrix in the row that corresponds to the particular parity check.

**20.**A non-transitory computer-readable medium including instructions executable on a processor to: attempt to decode a codeword using initial values for log-likelihood ratio (LLR) associated with digits of the codeword; adjust, for a trapping set, the LLRs associated with digits corresponding to a failed parity check to a no confidence value; and attempt to decode the codeword using the unchanged digits of the codeword corresponding to the failed parity check and the adjusted values for the LLRs of the digits corresponding to the failed parity check, wherein the no confidence value is midway between full confidence values.

**21.**The non-transitory computer-readable medium of claim 20, further including instructions executable on a processor to compute the LLR as LLR = log ( P ( 1 stSDataState ) P ( 2 ndDataState ) ) , ##EQU00016## where P(1stDataState) is a probability that a particular digit has a value corresponding to a first data state, and P(2ndDataState) is a probability that the particular digit has a value corresponding to a second data state.

**22.**The non-transitory computer-readable medium of claim 21, further including instructions executable on a processor to set the LLR associated with each of the digits corresponding to a failed parity check to a value midway between a full-confidence value and a no-confidence value.

**23.**The non-transitory computer-readable medium of claim 21, further including instructions executable on a processor to set P(1stDataState)=1 and P(2ndDataState)=0 for a digit sensed as having the first data state, and set P(1stDataState)=0 and P(2ndDataState)=1 for a digit sensed as having the second data state.

**24.**The non-transitory computer-readable medium of claim 21, further including instructions executable on a processor to set the LLR associated with each of the digits corresponding to a failed parity check to zero.

**25.**An apparatus for resolving trapping sets, comprising: a memory; and a low-density parity-check (LDPC) decoder communicatively coupled to the memory and configured to: for a particular number of iterations, attempt to decode a codeword using initial values for confidence levels associated with initial digits of the codeword; and after the particular number of iterations, attempt to decode the codeword using the unchanged initial digits of the codeword and a no confidence value for the confidence levels associated with at least some of the initial digits of the codeword, wherein the no confidence value is midway between full confidence values.

**26.**The apparatus of claim 25, wherein the no confidence value comprises a zero value.

**27.**The system of claim 25, further comprising a controller, the controller including the LDPC decoder.

**28.**The system of claim 25, further comprising a controller communicatively coupled to the memory through the LDPC decoder.

## Description:

**TECHNICAL FIELD**

**[0001]**The present disclosure relates generally to error correction, and more particularly, to apparatuses and methods for resolving trapping sets.

**BACKGROUND**

**[0002]**Memory devices are typically provided as internal, semiconductor, integrated circuits in computers or other electronic devices. There are many different types of memory including volatile and non-volatile memory. Volatile memory can require power to maintain its data and includes random-access memory (RAM), dynamic random access memory (DRAM), and synchronous dynamic random access memory (SDRAM), among others. Non-volatile memory can provide persistent data by retaining stored data when not powered and can include NAND flash memory, NOR flash memory, read only memory (ROM), Electrically Erasable Programmable ROM (EEPROM), Erasable Programmable ROM (EPROM), and resistance variable memory such as phase change random access memory (PCRAM), resistive random access memory (RRAM), and magnetoresistive random access memory (MRAM), among others.

**[0003]**Memory devices can be combined together to form a storage volume of a memory system such as a solid state drive (SSD). A solid state drive can include non-volatile memory (e.g., NAND flash memory and NOR flash memory), and/or can include volatile memory (e.g., DRAM and SRAM), among various other types of non-volatile and volatile memory.

**[0004]**An SSD can be used to replace hard disk drives as the main storage volume for a computer, as the solid state drive can have advantages over hard drives in terms of performance, size, weight, ruggedness, operating temperature range, and power consumption. For example, SSDs can have superior performance when compared to magnetic disk drives due to their lack of moving parts, which may avoid seek time, latency, and other electro-mechanical delays associated with magnetic disk drives.

**[0005]**Memory is utilized as volatile and non-volatile data storage for a wide range of electronic applications. Non-volatile memory may be used in, for example, personal computers, portable memory sticks, digital cameras, cellular telephones, portable music players such as MP3 players, movie players, and other electronic devices. Memory cells can be arranged into arrays, with the arrays being used in memory devices.

**[0006]**When data is transmitted from one location to another there is the possibility that an error may occur. Errors can also occur over time while data is stored in a memory. There are a number of techniques that can be used to encode data so that an error can be detected and/or corrected. Since data is routinely transmitted to and from memory, and stored therein, memory can employ error correction techniques to attempt to correct data associated with the memory.

**[0007]**One type of error correction involves a low-density parity-check (LDPC) technique. Unencoded, e.g., "raw" data can be encoded into codewords for transmission and/or storage. The codewords can subsequently be decoded to recover the data. However, depending on the nature and extent of errors that occur to the encoded codeword during transit and/or storage, a decoder may not be successful in properly decoding the codeword.

**BRIEF DESCRIPTION OF THE DRAWINGS**

**[0008]**FIG. 1 is a functional block diagram of an apparatus in the form of a computing system including at least one memory system, in accordance with a number of embodiments of the present disclosure.

**[0009]**FIG. 2 is a Tanner graph representation for the matrix H, in accordance with a number of embodiments of the present disclosure.

**[0010]**FIG. 3 is a possible trapping set in the Tanner graph representation of FIG. 2, in accordance with a number of embodiments of the present disclosure.

**[0011]**FIG. 4 is a flow chart of a method for resolving trapping sets in accordance with a number of embodiments of the present disclosure.

**DETAILED DESCRIPTION**

**[0012]**Apparatuses and methods for resolving trapping sets are provided. One example method can include attempting to decode a codeword using initial values for confidence levels associated with digits of the codeword. For a trapping set, the confidence levels associated with digits corresponding to a failed parity check are adjusted. The method further includes attempting to decode a codeword using the adjusted value for the confidence levels of the digits corresponding to the failed parity check.

**[0013]**Communication channel noise, increases in communication speed, and increases in storage density can each provide opportunities for the introduction of errors to the data being transmitted and/or stored. With particular respect to storage of data in a memory, it has been observed that charge storage memory cells can have a finite endurance. The quantity of data states per memory cell, as well as the quantity of program and erase cycles, can affect the reliability of the data stored therein. For example, the greater the quantity of data states per memory cell and/or the greater the quantity of program/erase cycles to which a memory cell is subjected, the lower reliability of accurately determining the data that was stored by the cell. Programming a memory cell repeatedly and/or repeatedly at relatively higher voltage levels can cause physical degradation of the memory cell resulting in increased likelihood of error introduction.

**[0014]**Increases in errors and/or decreases in reliability can lead to use of stronger error-correction techniques to detect, and/or timely correct, errors, for instance. Algebraic error-correction codes such as Bose, Chaudhuri, and Hocquenghem (BCH) codes can be used to correct a fixed number of errors in data, e.g., data stored in Flash memory devices. Soft data processing error correcting codes, such as low-density parity-check (LDPC) codes, can out-perform BCH codes.

**[0015]**Data can be expressed in a sequence of digits, e.g., bits. Data can further be encoded, for instance, into codewords. The codewords can comprise multiple digits. The digits of a codeword are sometimes referred to herein as code digits, e.g., code bits, so as to distinguish from the digits of the original data.

**[0016]**In attempting to recover correct data from a low-density parity-check (LDPC) encoded codeword, an LDPC decoder may encounter a number of sets that prevent the decoder from properly decoding the encoded codeword. "Sets" refer to groups of digits, such as the digits of a codeword, being evaluated by the decoder. Sets that prevent the decoder from properly decoding the encoded codeword are referred to as a trapping set. For example, the decoder may not being able to converge to a solution that satisfies decoding criteria for a trapping set.

**[0017]**For example, if errors happen at certain locations in the LDPC encoded codeword, the decoder can become "trapped" and may be unable to properly correct the errors. Errors happening at locations in the LDPC encoded codeword refer to errors associated with the respective column numbers of the parity check matrix H of the code.

**[0018]**According to a number of embodiments of the present disclosure, LDPC decoding can initially proceed based on full-confidence sensing of the data state of bits of a codeword. Associating a confidence level to a sensed data state can more completely reflect the uncertainty that may be included in the sensed data state. For example, initial values for confidence levels associated with digits of a codeword, which reflect confidence about a decision regarding a digit value received in a transmission and/or retrieved from a memory, can be set to reflect full confidence in the digit value. This is explained further below with respect to log-likelihood-ratios (LLR). When trapping sets are encountered, the values of confidence levels associated with those digits of a codeword corresponding to a failed parity check can be adjusted to a no confidence value, such as a value midway between the confidence values of the two possible data states

**[0019]**For example, if the full confidence value for a codeword digit sensed as a "0" is +1, and the full confidence value for a codeword digit sensed as a "1" is -1, then the no confidence value can be midway between +1 and -1, which is equal to zero (0).

**[0020]**A confidence level set to a no confidence value does not mean an absence of a confidence value, but rather that the confidence value is set to reflect a quantity that does not prefer any particular digit value to another, i.e., a value that does not reflect confidence in the sensed digit being any particular digit value. Thus, the no confidence value can be midway between the full confidence values of respective possible data states. The term "erasure" is sometimes used to mean a 50% probability that the digit is one data state, e.g., "0," and a 50% probability that the digit is a different data state, e.g., "1." Accordingly, the confidence level can be set to a no confidence value associated with erasure.

**[0021]**Full-confidence sensing assumes the sensed data state is accurate. Full-confidence sensing is faster since a probability associated with a sensed data state (such as may be associated with a charge distribution associated with a particular data state) is not considered. Full-confidence sensing is discussed further below. However, the confidence levels associated with digits corresponding to a failed parity checks, e.g., that fail after a number of iterations, are adjusted and decoding proceeds.

**[0022]**In the following detailed description of the present disclosure, reference is made to the accompanying drawings that form a part hereof, and in which is shown by way of illustration how a number of embodiments of the disclosure may be practiced. These embodiments are described in sufficient detail to enable those of ordinary skill in the art to practice the embodiments of this disclosure, and it is to be understood that other embodiments may be utilized and that process, electrical, and/or structural changes may be made without departing from the scope of the present disclosure. As used herein, the designator "N" indicates that a number of the particular feature so designated can be included with a number of embodiments of the present disclosure.

**[0023]**As used herein, "a number of" something can refer to one or more of such things. For example, a number of memory devices can refer to one or more of memory devices. Additionally, designators such as "N", as used herein, particularly with respect to reference numerals in the drawings, indicates that a number of the particular feature so designated can be included with a number of embodiments of the present disclosure.

**[0024]**The figures herein follow a numbering convention in which the first digit or digits correspond to the drawing figure number and the remaining digits identify an element or component in the drawing. Similar elements or components between different figures may be identified by the use of similar digits. As will be appreciated, elements shown in the various embodiments herein can be added, exchanged, and/or eliminated so as to provide a number of additional embodiments of the present disclosure. In addition, the proportion and the relative scale of the elements provided in the figures are intended to illustrate various embodiments of the present disclosure and are not to be used in a limiting sense.

**[0025]**FIG. 1 is a functional block diagram of an apparatus in the form of a computing system 100 including at least one memory system 104, in accordance with a number of embodiments of the present disclosure. Although the apparatus and methods of the present disclosure are illustrated with respect to a computing system, and more particularly with respect to decoding data read from memory, embodiments of the present disclosure are not so limited and can be implemented in other manners, such as in receiving data transmitted through a communication channel, etc.

**[0026]**As illustrated in FIG. 1, a host 102 can be communicatively coupled to a memory system 104, such as by an interface 106, e.g., a communication channel. As used herein, a memory system 104, a controller 115, or a memory device 130 might also be separately considered an "apparatus." The memory system 104 can be used as a mass data storage memory system in the computing system 100, e.g., an enterprise solid state storage appliance. Alternatively, the memory system 104 can be used as an external, or portable, memory system for computing system 100, e.g., a portable solid state drive (SSD) with plug-in connectivity such as a thumb drive, etc.

**[0027]**The memory system 104 can include a host interface 108, a controller 115 (e.g., a processor and/or other control circuitry), and a memory 130), which provides a storage volume for the memory system 104. The memory 130 can be comprised of a number of memory devices (not individually shown for simplicity), e.g., solid state memory devices such as NAND flash devices. In a number of embodiments, the controller 115, the memory device 130, and/or the host interface 108 can be physically located on a single die or within a single package, e.g., a managed NAND application. Also, in a number of embodiments, a memory can include a single memory device.

**[0028]**Interface 106 can be a cable or bus, such as a serial advanced technology attachment (SATA), peripheral component interconnect express (PCIe), or a universal serial bus (USB), or other interface.

**[0029]**The memory system 104 can include a controller 115 communicatively coupled to memory 130. The controller 115 can be communicatively coupled to a host interface 108, which can be communicatively coupled to the host 102. The host interface 108 can be connected to the interface 106, and include, for example, a compatible connector and/or other receptor for the interface 106. For a number of embodiments, the host interface 108 can be in the form of a standardized interface, such as those listed above, or can be compatible with other connectors and/or interfaces. The host interface 1108 is used to communicate data between the memory 130 and the host 102. For example, the host interface 108 can provide an interface for passing control, address, user data, and other signals between the memory 130 and the host 102.

**[0030]**Host 102 and/or host interface 108 can include a memory access device, e.g., a processor, and/or other computing components. One of ordinary skill in the art will appreciate that "a processor" can intend a number of processors, such as a parallel processing system, a number of coprocessors, etc. Examples of host 102 include a desktop computer, a mobile telephone, a server, a laptop computer, a personal computer, a digital camera, a digital recording and playback device, a personal digital assistant (PDA), a memory card reader, an interface hub, etc.

**[0031]**Memory 130 can be a non-transitory media, and include a number of arrays of memory cells, e.g., non-volatile memory cells. The arrays can be Flash arrays with a NAND architecture, for example. However, embodiments of the present disclosure are not limited to a particular type of memory array or array architecture. The methods and apparatuses of the present disclosure can also be used or implemented with other memory cells, such as memory cells typically used in, for example, DRAM, PCRAM, and/or RRAM memories. The memory 130 can include a number of storage nodes, e.g., groups of memory cells (detail not shown in FIG. 1).

**[0032]**The controller 115 can include logic (including high speed memory) configured for a number of functions such as error correction coding (ECC), performing physical to logical mapping, "in-flight" data buffering, block management, e.g., wear leveling, and communications interfaces with the memory 130. The controller 115 can translate commands received from the host 102 into appropriate commands to accomplish an intended memory operation, and thereby provide a translation layer between the host 102 and the memory 130. Controller 115 can also process host command sequences and associated data, and other data, to the appropriate memory command sequences in order to store and retrieve data, for example.

**[0033]**The controller 115 can communicate with the memory 130 to operate, e.g., read, write, move, program, sense, erase, the memory cells. Thus, controller 115 can manage communications with, and the data stored in, the memory 130. The controller 115 can have circuitry utilizing a number of integrated circuits, as well as other discrete components. In a number of embodiments, the controller 115 can be an application specific integrated circuit (ASIC) coupled to a printed circuit board including the host interface 108, and/or the memory device 130.

**[0034]**The memory system 104, memory 130, and/or controller 115 can include additional circuitry that is not illustrated so as not to obscure embodiments of the present disclosure. For example, although not specifically illustrated, in some embodiments, the memory can include a plurality of components each coupled to the controller 115 by a respective channel. The controller 115 can include a discrete memory channel controller for each channel. The controller 115 can include, for example, a number of components in the form of hardware and/or firmware (e.g., a number of integrated circuits) and/or software for controlling access to the memory 130. As used herein, the memory system 104, the controller 115, or the memory 130 might also be implemented separately and/or considered an "apparatus."

**[0035]**The controller 115 can also include logic configured for encoding and decoding data being transmitted to and/or received from the memory 130. As illustrated in FIG. 1, the controller 115 can include a number of error coding/decoding components, e.g., encoder/decoder implementing an error correction code (ECC) engine. The error coding components can be configured to encode data, e.g., user data, received from the host 102 to be stored in the memory 130.

**[0036]**According to a number of embodiments, the controller 115 can include an encoding portion and/or a decoding portion. For example, the controller 115 can include a low-density parity check (LDPC) encoder 118, an LDPC decoder 120, a BCH (Bose, Chaudhuri, and Hocquenghem) encoder 116, and/or a BCH decoder 122. User data can be encoded using a linear error correcting code such as an LDPC code.

**[0037]**Encoding and/or decoding of the data can be accomplished in hardware and/or software, such as in the controller 115 and/or at the host 102 before communication to the controller 115. Encoders 116/118 receive unencoded data at an input and provided encoded data at an output. Encoders 116/118 can receive, e.g., from a host 102, k digits of data at an input, e.g., a k-digit codeword, and generate n digits of data, e.g., an n-digit encoded codeword at an output. As used herein, a "digit" refers to a digit of data, such as a binary digit, e.g., bit, a hexadecimal digit, etc.

**[0038]**As used herein, a "codeword" refers to a combination of digits of data, such as input data, e.g., user data. A codeword can include a particular amount of data which may correspond to a data transfer size of the memory 130 and/or host 102, for example. A codeword can include additional digits as a result of encoding, such as parity digits, for example. The n-digit encoded codeword can uniquely correspond to the k-digit codeword. The n-digit encoded codeword can be stored in the memory 130 in place of the k-digit codeword.

**[0039]**Decoders 120/122 receive encoded data at an input and provide the original data at an output. Decoders 120/122 can receive, e.g., from memory 130, n digits of data, e.g., an n-digit encoded codeword, at an input, and generate k digits of data, e.g., an k-digit codeword, at an output. The encoding and decoding process can be such that errors in the encoded codeword can be detected and/or corrected during the decoding process.

**[0040]**Although illustrated as components within the controller 115 in FIG. 1, each of the error coding components can be external to the controller 115, or a number of components can be located within the controller 115 and a number of components can be located external to the controller 115.

**[0041]**FIG. 2 is a Tanner graph representation for the matrix H, in accordance with a number of embodiments of the present disclosure. Errors that happen at certain locations in a LDPC codeword, such as locations determined by the parity check matrix, H, of the code, can cause the decoder to be trapped. For example, the decoder may not be capable of correcting the errors at all. A technique is discussed below that helps the decoder efficiently recover from such trapping sets.

**[0042]**To protect against errors, a binary data pattern of k bits can be coded into a codeword of n bits, where n>k. The (n-k) redundant bits in the codeword are called parity checks, e.g., parity bits.

**[0043]**A code can be characterized by two matrices, a generator matrix, G, and the parity check matrix, H, of the code.

**[0044]**The (n, k) code can be defined by a unique matrix H of size (n-k)×n, known as its parity check matrix. The entries in matrix H are 1s and 0s. If the count of 1 is relative to 0s is low in H, the code is referred to as a low density parity check (LDPC) code. An example of a parity check matrix H for an n-bit codeword (where n=7 as indicated by the quantity of columns in matrix H) and based on 3 parity bits (as indicated by the quantity of rows in matrix H) is shown below:

**H**= [ 1 0 1 0 1 0 0 0 1 0 1 0 1 0 1 0 0 1 0 0 1 ] ##EQU00001##

**[0045]**In this example, the codeword is 7 bits long, e.g., n=7, and with 3 parity bits, e.g., (n-k)=3, so the H matrix is a 3×7 matrix, i.e., 3 rows and 7 columns. The data pattern being coded is 4 bits in length, since here the codeword length, n, is 7, and the quantity of parity bits, (n-k), is 3.

**[0046]**The (n, k) code can also be defined by a generator matrix, G, of size k×n. A codeword can be generated from the data pattern being coded using the generator matrix, G. For this example, the generator matrix, G, is a 4×7 matrix, i.e., 4 rows and 7 columns. The generator matrix, G, can be generated from the parity-check matrix, H, or the parity-check matrix H can be generated from the generator matrix, G. The generator matrix, G, for this example is shown below:

**G**= [ 0 1 1 1 0 0 0 1 0 1 0 1 0 0 1 1 0 0 0 1 0 1 1 1 0 0 0 1 ] ##EQU00002##

**[0047]**A data pattern can be chopped-up into 4-bit words, and the words encoded to a codeword using the G matrix. For example [1 0 1 0] can be matrix multiplied with the matrix G to determine the corresponding 7-bit codeword. In this example, the codeword x=[1 0 1 1 0 1 0] results. The codeword can be transmitted and/or stored, e.g., in a memory).

**[0048]**Upon receipt and/or retrieval from memory, the codeword, e.g., [1 0 1 1 0 1 0] for this example, can be checked for validity and used to recover the 4-bit word. One way the codeword can be checked for validity is by matrix multiplication with the transpose matrix of H, i.e., H'. The matrix H' is referred to as H transpose, and is obtained by interchanging the rows and columns of H. The H' matrix for this example is the 7×3 matrix shown below:

**H**' = [ 1 0 0 0 1 0 0 0 1 0 1 1 1 0 1 1 1 0 1 1 1 ] ##EQU00003##

**[0049]**The matrix multiplication of a valid n-bit codeword, x, with H' should result in an all-zero vector. For this example, matrix multiplication of the 1×7 matrix x with the 7×3 matrix H' results in the 1×3 all-zero vector [0 0 0], which proves that x, e.g., [1 0 1 1 0 1 0], is a valid codeword for this H matrix. The additions in the matrix multiplications discussed herein are modulo 2 additions, also referred to as exclusive-or additions, such that adding 1 plus 1 equals 0 (not 2).

**[0050]**If the matrix multiplication of x and H' does not result in an all-zero vector, such a result indicates the presence of errors in the codeword, i.e., a failed parity check. Errors in a codeword refer to digits of the codeword in certain locations where the digits have been changed, e.g., 0s changed to 1s and 1s to 0s.

**[0051]**Upon failure of a parity check, attempt(s) can be made to decode the codeword using initial values for confidence levels associated with digits of the codeword. If a solution does not converge, resulting in a trapping set, the confidence levels associated with digits corresponding to the failed parity check can be adjusted to a no confidence value, and further attempt(s) can be made to decode the codeword using the adjusted values for the confidence levels of the digits corresponding to the failed parity check. Attempt(s) to decode the codeword refer to a process to correct the error(s) of digit values in the codeword.

**[0052]**The valid codeword above, [1 0 1 1 0 1 0], may be transmitted and/or stored in a memory. However, if digit(s) change during transmission, while stored in memory, and/or upon sensing from memory, the codeword may change, for example, to [1 0 1 0 0 1 0], in which the fourth digit is changed from a "1" to a "0." The codeword [1 0 1 0 0 1 0] matrix multiplied by H' results in the vector [0 1 1], which is not an all-zero vector indicative of a valid codeword. Thus, the codeword [1 0 1 0 0 1 0] is not valid, and error correction measures can be used to decode the codeword, to the valid codeword to which the errors occurred. Illustration of a codeword having errors that result in a trapping set during subsequent iterative error correction measures is not possible for this simple example. However, the ability to correct errors in a codeword can depend on the location and quantity of the erroneous digits in a codeword, which can have more digits than used in this simple example. The locations of digit errors within a codeword that result in a trapping set are referred to as being at trapping set locations.

**[0053]**The matrix H for an n-bit codeword can also be represented graphically by a structure known as the Tanner graph, consisting of n circles and (n-k) squares. In a Tanner graph, each circle represents a column in matrix H (each column corresponding to a bit of the codeword), and each square represents a row in matrix H (each row corresponding to a parity bit). A line is drawn between a square and a circle if there is a 1 in the row that corresponds to that square at the column position denoted by that circle. The Tanner graph representation for the example matrix H provided above is shown in FIG. 2.

**[0054]**The squares are referred to as check nodes 234 (c-nodes) and the circles are referred to as vertices 232 (v-nodes). The v-nodes 232 can also be referred to as code bits, as indicated parenthetically for the v-nodes 232 in FIG. 3. The number of lines exiting a c-node 234 is the degree of that c-node 234. In this example, the degree of each c-node 234 equals three. A c-node 234 is said to be adjacent to a v-node 232 if it is attached to that v-node 232, as indicated in FIG. 2 by a connection 233 therebetween. For example, in FIG. 2, c-node 1 is adjacent v-nodes 1, 3, and 5.

**[0055]**A c-node 234 is said to be satisfied if the modulo-2 sum, i.e., exclusive-or (XOR) addition of two bits, of the bits in the v-node 232 locations that the c-node 234 is connected to in the Tanner graph equals 0. Exclusive-or addition results in a "1" output sum if one, and only one, of the input digits is a "1," and results in a "0" output sum if both of the input digits are "0" or if both of the input digits are "1."

**[0056]**For example, FIG. 2 shows the v-node values for the valid codeword example above. The v-node values are the digits of the codeword, so v-node 1 has a value of 1, v-node 2 has a value of 0, and so on as shown for the valid codeword [1 0 1 1 0 1 0]. The corresponding c-node values for the valid codeword example are also shown on FIG. 2. The value of c-node 1 is computed as the modulo-2 sum of the v-node values connected to c-node 1, e.g., the value of v-node 1+the value of v-node 3+the value of v-node 5. Using the v-node values, the modulo-2 sum is 1+1+0=0. The value for c-node 2 is equal to 0+1+1=0, and the value for c-node 3 is equal to 1+1+0=0. The computed c-node values are the same as the all-zero vector computed above by matrix multiplication of the valid codeword and H'.

**[0057]**FIG. 2 also shows the v-node values for the invalid codeword example above. The v-node values are the digits of the invalid codeword example previously discussed, so v-node 1 has a value of 1, v-node 2 has a value of 0, and so on as shown for the invalid codeword [1 0 1 0 0 1 0], i.e., with the fourth digit flipped from 1 to 0. The corresponding c-node values for the invalid codeword example are also shown on FIG. 2. The value of c-node 1 (for the invalid codeword) is computed as the modulo-2 sum of the v-node values connected to c-node 1, e.g., the value of v-node 1+the value of v-node 3+the value of v-node 5. Using the v-node values for the invalid codeword, the modulo-2 sum is 1+1+0=0. The value for c-node 2 is equal to 0+0+1=1, and the value for c-node 3 is equal to 1+0+0=1. Again, the computed c-node values are the same as the not-all-zero vector computed above by matrix multiplication of the invalid codeword and H'.

**[0058]**An unsatisfied c-node 234 is said to have failed. If a first quantity (b) of digits in a codeword are erroneously received, and if that results in a second quantity (a) of c-nodes 234 failing, that pair (a, b) is said to be an (a, b) trapping set (assuming it causes the decoder to fail to converge to a solution). For the example above, quantity b is 1 (the quantity of erroneous digits in the codeword) and quantity (a) is 2 (the quantity of failed c-nodes). An example of a possible trapping set is discussed below with respect to FIG. 3.

**[0059]**FIG. 3 is a possible trapping set in the Tanner graph representation of FIG. 2, in accordance with a number of embodiments of the present disclosure. The term possible trapping set is used here to denote that single digit error in the invalid codeword may, or may not, cause the decoder to fail to converge to a solution. For this possible trapping set example, bits of the 7-bit codeword (represented by the v-nodes 232 in FIG. 2) in location 4 is in error. The Tanner graph of FIG. 3 is constructed by extracting the erroneous code bit 4, which is indicated in FIG. 3 by the solid circle 340. The connections of c-nodes 338 that are adjacent to those this v-node 336, e.g., 4, are also included in the Tanner graph of FIG. 3. For this example, c-nodes 2 and 3 are adjacent v-node 4, as indicated by the lines connecting c-nodes 2 and 3 to v-node 4 in FIG. 2. Therefore, c-nodes 2 and 3 are shown in the Tanner graph of FIG. 3 as solid boxes, and the connections between c-nodes 2 and 3 and v-node 4 are shown as solid lines.

**[0060]**The Tanner graph of FIG. 3 also includes the other v-nodes connected to the c-nodes 2 and 3. As shown in FIG. 3, c-node 2 is also adjacent to v-nodes 2 and 6, so v-nodes 2 and 6 are shown being attached to c-node 2 by the dotted connections 344. Likewise, c-node 3 is also adjacent to v-nodes 1 and 7, shown by a dotted connection 344 in FIG. 3. The Tanner graph of FIG. 3 shows the failed parity checks (corresponding to the failed c-nodes) and all of the digits of the codeword associated with the failed parity checks. In practice, the computation shown in FIG. 2 can determine which parity checks have failed, from which the digits associated with those failed parity checks that possibly caused the parity check failures can be identified, as shown in FIG. 3.

**[0061]**The erroneous v-nodes 340 are shown in FIG. 3 by solid circles and the correct v-nodes 342 are shown by dotted circles. Both c-nodes 2 and 3 will fail on account of the error in the fourth digit of the codeword, e.g., to code bit 4, even when digits 1, 2, 6, and 7 are correct. Therefore, the Tanner graph of FIG. 3 indicates a (2, 1) possible trapping set for this example, where 2 is the quantity of failing c-nodes 338 (as indicated by the quantity of boxes in the possible trapping set illustrated FIG. 3) and 1 is the quantity of erroneous bits 340 in the codeword (as indicated by the quantity of solid circles in the possible trapping set illustrated in FIG. 3).

**[0062]**Referring again to FIG. 1, data can be encoded by the LDPC encoder 118, which uses an LDPC code. Accordingly, memory 130 can be programmed using coded data. As such, memory 130 can be sensed, e.g., read, based on coded bits, which are processed by the LDPC decoder 120. According to various embodiments, the LPDC decoder 120 can consider confidence levels associated with sensed digits. That is, a confidence value associated with a sensed digit value can be used in decoding.

**[0063]**Confidence about a decision regarding a digit value can be expressed as log-likelihood-ratio (LLR), which is calculated as

**LLR**= log ( P ( 0 ) P ( 1 ) ) , ##EQU00004##

**where P**(0) is a probability that a code bit is a first value, e.g., zero, and P(1) is a probability that a code bit is a second value, e.g., one. As such, when full confidence is assigned to a sensed decision, the above formula results in positive infinity when a `0` is sensed since

**LLR**= log ( 1 0 ) = log ( ∞ ) = ∞ , ##EQU00005##

**and negative infinity when a**"1" is sensed since

**LLR**= log ( 0 1 ) = log ( 0 ) = - ∞ . ##EQU00006##

**The measure of confidence can be truncated to one bit**, sending +1 in place of positive infinity and sending -1 in place of negative infinity to the LDPC decoder 120.

**[0064]**Such full-confidence sensing is referred to as `hard` sensing. That is, the value sensed from the memory 130 is assumed to be the value that was stored in the memory 130. That is, for full-confidence sensing, a code bit that is sensed, e.g., read from memory, as a "0" will have a corresponding LLR of +1, and a code bit that is sensed, e.g., read from memory, as a "1" will have a corresponding LLR of -1. In contrast, "soft" sensing is where a certain measure of doubt about the sensed decision is considered along with the sensed value. Along with sensing the code bits, a probability that a particular sensed code bit is a zero and a probability that the particular sensed code bit is a one is used to compute an LLR associated with the sensed code bit. For example, a code bit may have a 75% probability of actually being in a zero data state and a 25% probability of actually being in a one data state. Therefore, the associated LLR can be calculated to be:

**LLR**= log ( .75 .25 ) = 0.4771 ##EQU00007##

**Hard sensing is a preferred mode of sensing memory**130 for throughput reasons since it avoids the computational load and delay to consider probabilities for each state and compute an associated LLR for each sensed bit.

**[0065]**The LLRs of the bits in the trapping set can have the same magnitude as those in the non-erroneous locations even when "soft" sensing is done. After a certain number of iterations, if the LDPC decoder 120 can arrive at a state where the LLRs in trapping set locations have roughly the same magnitude as in the non-erroneous locations, the LDPC decoder 120 will not converge.

**[0066]**Particularly problematic are (a, b) trapping sets, where a<b, that is, the quantity of failed c-nodes is less than the quantity of erroneously-received digits in the codeword. The example discussed above that resulted in a (2,1) possible trapping set is not an (a, b) trapping sets, where a<b. However, in referring back to FIG. 2 one can appreciate that if digits 2 and 6, or 3 and 5, of a codeword were flipped, in each case only one c-node would fail, e.g., c-node 2 and c-node 1 respectively. Each of these scenarios reflects a (1,2) possible trapping set, which are (a, b) trapping sets, where a<b. The examples discussed above are relatively simple in order to illustrate the principles being utilized, which can be applied to more complex scenarios of error correction that can increase as the quantity of digits in a codeword increases.

**[0067]**Some previous approaches for resolving trapping sets relied on first recognizing a trapping set, for example, by comparing a set with an enumeration of all the trapping sets of a code. The greater the quantity of digits in a codeword, the more difficult and time consuming the process becomes for comparing a set being decoded with all possible trapping sets. Furthermore, such previous approaches used memory to maintain a table of such trapping sets so that when the decoder fails, the particular trapping set at which the decoder is stuck and the remedy, e.g., LLR change(s) to apply, can be looked-up. The amount of memory used for maintaining a table for codes is greater as the size of codewords increase, and is increasingly burdensome as the list of trapping sets increases. Use of a table can have drawbacks, such as consuming a significant portion of memory 130, thus reducing the quantity of data that can be stored in memory 130, and/or other drawbacks.

**[0068]**According to a number of embodiments of the present disclosure, the LDPC decoder 120 can implement an iterative decoding process of an n-bit codeword to resolve those trapping sets where the number of failed c-nodes is less than the number of failed v-nodes. According to the embodiments, prior enumeration and/or storing of trapping sets for the LDPC code is not necessary since the method of the present disclosure does not rely on trapping set look-up and/or application of skew to LLRs of a particular trapping set.

**[0069]**If errors happen at trapping set locations, the minimum sum (min-sum) process will not converge. For example, decoding will not succeed, no matter how many iterations are performed. This situation can arise when the LLRs of the bits in the trapping set have the same magnitude as those in the non-erroneous locations. This can occur when "hard" sensing is done of the memory 130, e.g., where sensed 0s have a corresponding LLR of +1 and sensed 1s have a corresponding LLR of -1.

**[0070]**FIG. 4 is a flow chart of a method for resolving trapping sets in accordance with a number of embodiments of the present disclosure. In a number of embodiments, an LDPC decoder, e.g., 120 in FIG. 1, utilizes an iterative minimum-sum process decoding technique. The flow chart shown in FIG. 4 is discussed using pseudo-code for the iterative decoding process of an n-bit codeword that is given below. MaxIterations is the maximum number of iterations allowed for the LDPC decoder 120 when processing for convergence using initial LLRs. For example, the maximum number of iterations allowed for the LDPC decoder 120 when processing for convergence using initial LLRs can be 10-12 iterations. However, embodiments are not limited to this range and the method of the present disclosure can be implemented using a maximum number of iterations using initial LLRs above, or below, the example range. A maximum number of iterations using initial LLRs can be up to 50, for instance.

**[0071]**The process is initiated at 450. To begin a decoding process, the LDPC decoder is initialized at 452. The LDPC decoder 120 is initialized by receiving, e.g., sensing, the n-bit codeword from memory 130. For example, the codeword n can be an array where CB1 indicates the value of the first sensed code bit as follows:

**n**=[CB1 CB2 CB3 CB4 CB5 CB6 CB7]

**Initialization continues by**:

**[0072]**1. Determining the associated LLRs for each of the n code bits. The LLRs may be stored, e.g., in an array, for the whole n-bit codeword. For example, the array storing the LLRs associated with each code bit, where LLR1 indicates the value of the initial LLR associated with the first sensed code bit, can be as follows:

**ILLR**=[LLR1 LLR2 LLR3 LLR4 LLR5 LLR6 LLR7]

**[0073]**2. Initializing a matrix Lq, which is of the same size as matrix H using the received LLRs (for the whole n-bit codeword) as follows:

**[0074]**for i=1: Number of Rows in Lq; and for j=1: n,

**[0075]**if H (i, j)=1, set Lq(i, j)=LLR of the jth sensed code bit. For example, for full-confidence sensing the elements of Lq will initially be +1 if a "0" code bit is sensed (and H (i, j)=1) or -1 if a "1" code bit is sensed (and H (i, j)=1) or 0 if H (i, j)=0. For the H matrix discussed previously:

**[0075]**Lq = [ LLR 1 0 LLR 3 0 LLR 5 0 0 0 LLR 2 0 LLR 4 0 LLR 6 0 LLR 1 0 0 LLR 4 0 0 LLR 7 ] , ##EQU00008##

**[0076]**where the initial LLR values are +/-1, and where LLR1 indicates the LLR for code bit 1, etc. As an example, for the valid codeword example [1 0 1 1 0 1 0] discussed with respect to FIG. 2, and where the measure of confidence is truncated to one bit, sending +1 in place of positive infinity when a `0` is sensed and sending -1 in place of negative infinity when a `1` is sensed, the example initial Lq matrix is as follows:

**Lq**= [ - 1 0 - 1 0 + 1 0 0 0 + 1 0 - 1 0 - 1 0 - 1 0 0 - 1 0 0 + 1 ] ##EQU00009##

**[0077]**3. Initializing a matrix Lr with all zeros (0), where matrix Lr is also of the same size as matrix H.

**Lr**= [ 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 ] ##EQU00010##

**[0078]**4. Initializing variables, e.g., flags, to zero for tracking whether the decoding is successful (DecodeSucceded) and the number of iterations (numIterations) of the decoding process. That is, set DecodeSucceded=0 and numIterations=0.

**[0079]**Processing

**[0080]**After initialization is complete, the iterative decoding process can be performed as follows:

**[0081]**While (DecodeSucceded=0 and numIterations<MaxIterations){

**[0082]**1) Initialize the vector app_llr of length n with the initially determined LLRs, e.g., based on the code bits sensed from memory 130. As an example, for the valid codeword example [1 0 1 1 0 1 0] discussed with respect to FIG. 2, and where the LLR is truncated to one bit, sending +1 in place of positive infinity when a `0` is sensed and sending -1 in place of negative infinity when a `1` is sensed, the example initial app_llr vector is as follows:

**[0082]**app_llr=[-1+1 -1 -1 +1 -1 +1]

**[0083]**Minimum Generation

**[0084]**As shown in FIG. 4 at 454, minimum values can be generated as follows:

**[0085]**2) Compute the two smallest magnitudes m1 and m2 of all the numbers in each row of matrix Lq; m1 is the smallest and m2 is the next smallest. For the example Lq matrix shown above, m1 and m2 are each -1 (as -1 appears twice in each row).

**[0086]**3) Get the product of the signs S of all the numbers in each row of matrix Lq. For the example Lq matrix shown above, the sign of each row is positive (zero values are taken as having a positive sign). The first row sign, for example, is determined as -x+x-x+x+x+x+=+, which has a positive sign.

**[0087]**4) for i=1: Number of Rows in matrix Lq, and for j=1: n,

**[0088]**set Lr (i, j)=sign (Lq (i, j))*S*m1;

**[0089]**or, set Lr (i, j)=sign (Lq (i, j))*S*m2 (if that (i, j) location generated m1). From the example Lq matrix shown above, where S is +, and the values for m1 and m2 are each -1, Lr (1, 1)=-*+*-1=+1, Lr (1, 2)=+*+*-1=-1, . . . Lr (1, 5)=+*+*-1=-1, etc. The resulting Lr matrix becomes:

**[0089]**Lr = [ + 1 - 1 + 1 - 1 - 1 - 1 - 1 - 1 - 1 - 1 + 1 - 1 + 1 - 1 + 1 - 1 - 1 + 1 - 1 - 1 - 1 ] ##EQU00011##

**[0090]**Sum Operation

**[0091]**As shown in FIG. 4 at 456, the LLRs associated with respective code bits can be adjusted by addition of a scale factor multiplied by a value based on the generated minimum as follows:

**[0092]**5) For the jth code bit, do the following: (there are n code bits, so 1≦j≦n)

**[0093]**For i=1: number of rows in matrix Lq, compute app_llr (j)=app_llr (j)+scale_factor*Lr (i, j). The scale factor can be a constant that can be determined by instrumentation, for example, in various embodiments the scale factor can be in the range of 0-1. From the Lr matrix immediately above, and a scale factor of 0.5, for example, app_llr (1)=-1+(0.5)(+1)+(0.5)(-1)+(0.5)(+1)=-0.5, app_llr (2)=+1+(0.5)(-1)+(0.5)(-1)+(0.5)(-1)=+0.5, etc. The app_llr vector becomes:

**[0093]**app_llr=[-0.5 +0.5 -1.5 -0.5 -0.5 -1.5 -0.5]

**[0094]**Decision Making

**[0095]**As shown in FIG. 4 at 458, parity checks can be evaluated for the sensed code bits as follows:

**[0096]**6) For each code bit, use the decision rule: If app_llr (code bit)<0, decision=-1 else, decision=1. For the example app_llr vector above, the decisions are:

**[0097]**1

^{st}code bit: decision=-1

**[0098]**2

^{nd}code bit: decision=+1

**[0099]**3

^{rd}code bit: decision=-1

**[0100]**4

^{th}code bit: decision=-1

**[0101]**5

^{th}code bit: decision=-1

**[0102]**6

^{th}code bit: decision=-1

**[0103]**7

^{th}code bit: decision=-1

**[0104]**As shown in FIG. 4 at 460, a determination is made whether the decoder has converged to a solution for all parity checks as follows:

**[0105]**7) Check if all the (n-k) parity checks result in even parity with the decisions made above. Note that the encoded codeword has n bits and the unencoded codeword has k bits, so (n-k) is the quantity of parity bits, which is 3 for matrix H for this example. For each of the (n-k) parity checks, verify even parity by multiplying the decisions made above for column numbers with 1s in matrix H in the row that corresponds to the particular parity check. The example H matrix is:

**[0105]**H = [ 1 0 1 0 1 0 0 0 1 0 1 0 1 0 1 0 0 1 0 0 1 ] ##EQU00012##

**[0106]**Here, the first row corresponds to the first parity check, the second row to the second parity check, and the third row to the third parity check. The fourth code bit corresponds to the fourth column in the H matrix. The fourth column in the H matrix includes 1's in the second and third rows corresponding to parity checks 2 and 3 (as shown in FIG. 2). For example, for parity check 2, the decisions for the second, fourth and sixth code bits are multiplied together: +1×-1×-1=+1.

**[0107]**That product should result in a value of 1 for that row, as was computed for the second row in the example above. If a value of 1 for all the (n-k) rows is determined, the process is done, so set DecodingSucceded=1 and exit the while loop, as shown in FIG. 4 at 462. That is, the LDPC decoder 120 is run for the allocated maximum number of iterations (MaxIterations) using the initial LLR values, e.g., the +/-1 values based on the sensed value of each code bit. If the LDPC decoder 120 converges within the allocated maximum number of iterations using the initial LLR values, the iterative routine is exited at 462.

**[0108]**If a value of 1 for all the (n-k) rows is not determined, and if numIterations<MaxIterations, i.e., the maximum iterations using initial LLRs, as indicated at 464, then the process proceeds to the preparation of the next iteration 472 (using initial LLR values) detailed below.

**[0109]**Preparation for the Next Iteration

**[0110]**As shown in FIG. 4 at 472, another round of iteration can be prepared for in this way:

**[0111]**8) Update matrix Lq as follows:

**[0112]**for j=1: number of code bits,

**[0113]**for i=1: Number of rows in matrix Lq,

**[0114]**update Lq(i, j)=app_llr(j)-Lr(i, j)

**[0115]**For example, based on the app_llr vector and Lr matrix as shown below:

**[0115]**app_llr=[-0.5 +0.5 -1.5 -0.5 -0.5 -1.5 -0.5]

**Lr**= [ + 1 - 1 + 1 - 1 - 1 - 1 - 1 - 1 - 1 - 1 + 1 - 1 + 1 - 1 + 1 - 1 - 1 + 1 - 1 - 1 - 1 ] ##EQU00013##

**[0116]**the updated Lq matrix becomes:

**[0116]**Lq = [ - 1.5 + 1.5 - 2.5 + 0.5 + 0.5 - 0.5 + 0.5 + 0.5 + 1.5 - 0.5 - 1.5 + 0.5 - 2.5 + 0.5 - 1.5 1.5 - 0.5 - 1.5 + 0.5 - 0.5 + 0.5 ] ##EQU00014##

**[0117]**The next iteration proceeds based on the updated Lq matrix.

**[0118]**9) Update numIterations=numIterations+1.

**[0119]**} // End of while loop. The decoding process then proceeds as before by repeating all the steps in Processing section.

**[0120]**Branch if Max Iterations

**[0121]**If the maximum number of iterations has been reached then as shown in FIG. 4 at 470 the confidence values, e.g., LLRs, for code bits associated with the failed parity checks are adjusted to a no confidence level, as follows:

**[0122]**A) Determine the failed parity checks by: from matrix H, determine code bits to which each failed parity check is attached as being the column numbers in matrix H with 1s in the row that corresponds to that parity check. Determination of a failed parity check and of the code bits associated with the failed parity checks were discussed with respect to FIGS. 2 and 3. Referring to FIG. 3, the confidence value associated with the fourth code bit can be adjusted to a no confidence level, e.g., 0, before another iteration is executed.

**[0123]**B) For all subsequent iterations, after preparation for the next iteration (shown in FIG. 4 at 472), at the beginning of the iteration, in step 1) of Processing above, the app_llr values are initialized to the adjusted confidence level, e.g., zero which is half way between the two full-confidence levels of +1 and -1, for all those code bits (v-nodes) that were attached to checks (c-nodes) that failed in the previous iteration. For example, app_llr (4

^{th}code bit)=0.

**[0124]**The method described above was evaluated experimentally. A particular (18600, 17112) code, i.e., having 18600 codebits or v-nodes and (18600-17112)=1488 c-nodes was taken and 350,000 (6,7) trapping sets were first isolated and tabulated for the code. Note that the number of failed c-nodes is less than the number of failed v-nodes. An all-zero codeword was taken, and in the trapping set locations those zeros were changed to is. The LDPC decoder 120 was tested assuming hard sensing of the memory 130. That is, LLRs of +1 were assigned to 0s in the codeword, and LLRs of -1 were assigned to is in the codeword. The LDPC decoder 120 failed to converge even after 100 iterations. The procedure described above was invoked with scale-factor of 0.25. The LDPC decoder 120 converged in three iterations or less. The procedure succeeded on all 350,000 trapping sets.

**[0125]**Advantages of the present disclosure include providing the ability to resolve trapping sets that otherwise might not be resolvable without use of a look-up of stored trapping sets and application of skew to LLRs. With more efficient resolution of trapping sets, data can be stored in memory without use of an outer BCH code. Elimination of the outer BCH code can eliminate the need for a BCH encoder 116 and a BCH decoder 122 on the controller 115. That is, according to a number of embodiments, the controller 115 does not include the BCH encoder 116 and/or the BCH decoder 122. Elimination of the outer BCH code can also improve code rate attainable for ECC and thus increases the amount of data stored on a memory device (including through elimination of stored trapping sets for look-up).

**[0126]**Although specific embodiments have been illustrated and described herein, those of ordinary skill in the art will appreciate that an arrangement calculated to achieve the same results can be substituted for the specific embodiments shown. This disclosure is intended to cover adaptations or variations of various embodiments of the present disclosure. It is to be understood that the above description has been made in an illustrative fashion, and not a restrictive one. Combination of the above embodiments, and other embodiments not specifically described herein will be apparent to those of skill in the art upon reviewing the above description. The scope of the various embodiments of the present disclosure includes other applications in which the above structures and methods are used. Therefore, the scope of various embodiments of the present disclosure should be determined with reference to the appended claims, along with the full range of equivalents to which such claims are entitled.

**[0127]**In the foregoing Detailed Description, various features are grouped together in a single embodiment for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the disclosed embodiments of the present disclosure have to use more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed embodiment. Thus, the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separate embodiment.

User Contributions:

Comment about this patent or add new information about this topic: