Technical Field
This disclosure relates in part to data storage systems for computer systems. More particularly, the disclosure relates in part to a non-binary decoder using binary subgroup processing.
Description of the Related Art
Non-volatile memory arrays often have limited endurance. The endurance of the memory array is typically contingent on usage pattern and wear. In addition, the endurance depends on a type of the non-volatile memory array used. For example, memory arrays with multi-level cell (MLC) NAND media typically have a lower endurance than memory arrays with single-level cell (SLC) NAND media. To protect user data stored to memory arrays from corruption, which may be caused by a diminished endurance, user data can be encoded, for example, by generating parity data that can be stored along with user data to facilitate error detection and correction. However, decoding of encoded data can be time consuming and resource intensive. Accordingly, it is desirable to provide more efficient mechanisms for decoding data.
Systems and methods disclosed herein will now be described with reference to the following drawings, in which:
While certain embodiments are described, these embodiments are presented by way of example only, and are not intended to limit the scope of protection. Indeed, the novel methods and systems described herein may be embodied in a variety of other forms. Furthermore, various omissions, substitutions, and changes in the form of the methods and systems described herein may be made without departing from the scope of protection.
Overview
Data storage systems, such as solid state drives, typically include one or more controllers coupled with one or more non-volatile memory arrays. Depending on the type of non-volatile memory array used, stored data may be subject to corruption as a result of, for example, read/write disturbs, loss of data retention, and/or loss of endurance. Data storage systems can utilize one or more error correction or error coding mechanisms to detect and/or correct errors in the stored data. One such mechanism can determine parity data when writing user data. Parity data can be stored, for example, in a memory array. When stored user data is retrieved, parity data can be utilized as part of a decoding process to determine the integrity of the retrieved user data. If one or more errors are detected, such errors may be corrected.
One type of error correct on or error coding mechanism that can be used by data storage systems to code data is low-density parity-check (LDPC)codes. To manage LDPC coding, the data storage systems can include decoder and encoder modules that utilize the LDPC codes for decoding and generating parity data, respectively. The LDPC codes can be decoded using a decoding matrix H and generated using a corresponding generating matrix G. The decoding process performed by the decoder modules, in particular, can involve an iterative decoding process where values (for example, probabilities or likelihoods of belief) are passed between variable nodes and check nodes to decode data.
Data storage systems can implement LDPC coding to enable processing of binary and/or non-binary LDPC codes. In some embodiments, whether the data storage systems may decode or encode data using a binary LDPC code or non-binary LDPC code can, for example, depend on a number of memory states for a storage medium in which the data storage systems can store and retrieve data, whether multiple memory cells are grouped into a memory element, etc. For example, a data storage system can use binary LDPC codes for storing or retrieving data from one or more storage mediums including memory elements that store single bits of information, such as SLC NAND media which may store in a memory cell one of “0” and “1” values, and use non-binary LDPC codes for storing or retrieving data from one or more storage mediums including memory elements that store multiple bits of information, such as MLC NAND media or SLC NAND media in which two or more memory cells are grouped into a single memory element. For instance, two-level or two-bit MLC NAND can store in a memory cell one of “00,” “01,” “10,” and “11” values.
Embodiments of the present disclosure are directed in part to a LDPC decoder module that can decompose a non-binary decoding process into binary decoding processes. In one embodiment, the decomposition of the non-binary decoding processes into the binary decoding processes can enable the LDPC decoder module to arrive at the same decoding results as if the LDPC decoder module directly performed the decoding using the non-binary decoding process. In another embodiment, the decomposition of the non-binary decoding processes into the binary decoding processes can enable the LDPC decoder module to utilize simplifications or approximations to increase the speed at which the LDPC decoder module reaches decoding results. In yet another embodiment, the LDPC decoder module can utilize simplifications or approximations in the decoding process to remove logarithmic or exponential operations, reducing memory usage and implementation complexity for the LDPC decoder module. Advantageously, in certain embodiments, the decomposition of the non-binary decoding processes into the binary decoding processes can enable the LDPC decoder module perform the decoding process without evaluating numerous combinations of values to determine minimum values as may be done in some non-binary decoding processes, like in particular extended minimum-sum algorithms.
System Overview
The controller 130 can be configured to receive data and/or storage access commands from a storage interface module 112 (e.g., a device driver) of the host system 110. Storage access commands communicated by the storage interface module 112 can include write data and read data commands issued by the host system 110. Read and write commands can specify a logical address (e.g., logical block addresses or LBAs) used to access the data storage system 120. The controller 130 can execute the received commands in the storage medium 140.
Data storage system 120 can store data communicated by the host system 110. In other words, the data storage system 120 can act as memory storage for the host system 110. To facilitate this function, the controller 130 can implement a logical interface. The logical interface can present to the host system 110 data storage system memory as a set of logical addresses e.g., contiguous address) where user data can be stored. Internally, the controller 130 can map logical addresses to various physical locations or addresses in the storage medium 140 and/or other storage modules.
The controller 130 includes a decoder module 132 and an encoder module 134 configured to decode and encode data, respectively, stored in and retrieved from the storage medium 140. The encoder module 134 can encode stored data so as to, for example, protect the data from potential errors encountered during retrieval of stored data. The decoder module 132 can further perform error detection to determine the integrity of data retrieved from the storage medium 140 and perform, if necessary, error correction of retrieved data. In some embodiments, when the storage medium 140 comprises NAND memory that may be early in the lifecycle and thus have relatively higher retention and/or endurance, the controller 130 can direct the encoder module 134 to encode data using a relatively higher coding rate so that less parity data is used. As the storage medium 140 wears out over time, the controller 130 can direct the encoder module 134 to switch to lower encoding rates such that more parity data is generated to protect stored user data from errors. The controller 130 can store the coding rates for encoded data in the storage medium 140 or another storage module (not shown) so that the decoder module 132 can later access the information to decode the encoded data. In some embodiments, the decoder module 132 and the encoder module 134 can respectively decode LDPC coded data and encode data using LDPC codes.
LDPC Decoder
In some embodiments, the decoder module 132 can decode data that may have been encoded using anon-binary LDPC coding. The decoder module 132 can read retrieved data from the storage medium 140 and calculate log likelihood ratio (LLR) values (for example, vectors of LLR values) for one or more read channels based on the data. The decoder module 132 can then iteratively transfer LLR values between variable nodes and check nodes using one or more LDPC coding techniques to decode the data. The decoding process can iterate on average from 3 to 4 iterations and may complete after a predetermined maximum number of iterations, such as 20 iterations.
The example of flow diagram 200 demonstrates the decomposition of non-binary values for a Galois field of size four (i.e., GF(4)) at the variable nodes 210A, 210B, 210C. This example, however, is intended to be illustrative and approaches disclosed herein can further extend to a Galois field having any other size less than or greater than four (for example, a Galois field of size eight or sixteen
At state transition 1, the variable nodes 210A, 210B, 210C can each output a vector including four values to a respective one of permutation nodes 220A, 220B, 220C. The permutation nodes 220A, 220B, 220C can permute the received vectors including the four LLR values using a corresponding element of a decoding matrix At state transition 2, the permutation nodes 220A, 220B, 220C can output the permuted vectors to a respective one of the conversion nodes 230A, 230B, 230C. The permuted vectors can have the form of [LLR00(p
The conversion nodes 230A, 230B, 230C can convert the permuted vectors in accordance with a decomposition algorithm to form binary inputs for the binary check nodes 240A, 240B, 240C. For example, each of the conversion nodes 230A, 230B, 230C can convert the permuted vectors according to Equations (1), (2), and (3).
L01(p
L10(p
L11(p
where max*(a,b)=max(a,b)+log(1+e−|a−b|); L01(p
In some embodiments, the computation for max*(a,b) can be performed using one or more simplifications or approximations. For instance, the computation can be performed using a lookup table or an approximation max*(a, b)≈γ·max(a, b) in place of performing the logarithmic or exponential operations that may otherwise be performed. The value for γ can be selected based on a code rate for the encoded data and set at manufacture of the data storage system 120. The value for γ can be a real number such as 0.75 in one implementation, or more or less in other implementations (for example, such as 0.65, 0.80, 1.00). In certain embodiments, the value for γ may not be based on noise detected on one or more read channels at run-time.
At state transition 3, the conversion nodes 230A, 230B, 230C can each output three binary values for processing by the binary check nodes 240A, 240B, 240C. The binary check nodes 240A, 240B, 240C can then perform a binary check node algorithm to determine a value for output to the inverse conversion node 250. In one example, each of the binary check nodes 240A, 240B, 240C can perform the binary check node algorithm of Equation (4).
where i can correspond to the subgroup for a given binary check node (such as 01, 10, and 11); Li(c
In another example, each of the binary check nodes 240A, 240B, 240C can perform the binary check node algorithm of Equation (8), which can reduce the memory usage and calculation complexity for performing the binary check node algorithm and enable faster processing and parallelization of performance of some processing by one or more of the conversion nodes 230A, 230B, 230C and the permutation nodes 220A, 220B, 220C.
where i can correspond to the subgroup for a given binary check nodes (such as 01, 10, and 11); a can correspond to a configurable constant such as 0.75, or more or less depending on the implementation (for example, 0,65, 0.80, 1.00); sign(Li(p
At state transition 4, the binary check nodes 240A, 240B, 240C can output the determined values of L01(c
where S01, S10, and S11 can correspond to intermediate values used to determine the values for the vector [LLR00(p), LLR01(p), LLR10(p), LLR11(p)] output from the inverse conversion node 250.
In another example, the determined values of L01(c
[LLR00(p), LLR01(p), LLR10(p), LLR11(p)]=[−|L01(c
At state transition 5, the inverse conversion node 250 can output the determined vector [LLR00(p), LLR01(p), LLR10(p)] to the inverse permutation node 260. The inverse permutation node 260 can inversely permute the determined vector [LLR00(p), LLR01(p), LLR10(p), LLR11(p)] using a corresponding element of the decoding matrix H before outputting the results of the inverse permutation to the variable nodes 210A, 210B, 210C at state transition 6. The variable nodes 210A, 210B, 210C can perform a summation of the received LLR values of the inversely permuted vectors and make a decision.
In a second decoder implementation of algorithms and data transfers in the decoding process illustrated in the flow diagram 200, the decoder can implement the decoding process of the flow diagram 300, with the exception of using the approximation algorithms of Equations (9), (10), and (11)to respectively perform the check node updates at the binary check nodes 240A, 240B, 240C.
In a third decoder implementation of algorithms and data transfers in the LDPC decoding process illustrated in the flow diagram 200, the decoder can implement the decoding process of the flow diagram 300, with the exception of: (i) using the approximation algorithms of Equations (9), (10), and (11) to respectively perform the check node updates at the binary check nodes 240A, 240B, 240C, (ii) using the approximation algorithm of max*(a, b)≈γ·max(a, b) to solve for max*(a, b) at the conversion nodes 230A, 230B, 230C, and (iii) using an approximation sort algorithm, such as illustrated with respect to Equation (16), to solve for the values of the vector [LLR00(p), LLR01(p), LLR10(p), LLR11(p)] at the inverse conversion node 250.
Table 2 below provides a legend for relating the graph labels in the graph 500 and the corresponding decoder implementations described herein.
As can be seen from the graphs 400 and 500, the performance of the first decoder implementation can match the performance of the traditional non-binary LDPC decoder. In addition, the performance loss from using the second or third decoder implementations can be relatively small compared to using the traditional non-binary LDPC decoder and first decoder implementation, especially for relatively higher signal-to-noise ratios.
At block 602, the conversion nodes 230A, 230B, 230C can convert input non-binary values to input binary values in accordance with a decomposition algorithm. The input non-binary values can be permuted vectors including LLR values determined based on an LDPC encoded data unit or from a previous decoding iteration. In one example, each of the conversion nodes 230A, 230B, 230C can convert the permuted vectors according to Equations (1), (2), and (3).
At block 604, the binary check nodes 240A, 240B, 240C can perform a binary check node algorithm to determine output binary values from the input binary values. For instance, the binary check nodes 240A, 240B, 240C can respectively perform the binary check node algorithms of Equations (5), (6), and (7).
At block 606, the inverse conversion node 250 can convert the output binary values to output non-binary values in accordance with an inverse decomposition algorithm. The inverse decomposition algorithm can be an inverse algorithm from the decomposition algorithm of block 602. For example, the inverse conversion node 250 can convert the output binary values according to Equations (12), (13), (14), and (15).
Other Variations
Although some embodiments of this disclosure may have been described using data storage systems or controllers for non-volatile storage media as examples, the disclosure can further apply to other environments and applications where data coding may be utilized. For example, the disclosure can apply to technologies where a non-binary LDPC signal can be read from a channel or data source (for example, the data communication channel 154) and then decoded using one or more binary decoders (for example, the decoder 156). In one such example, the disclosure can be used for decoding one or more communication channels in a telecommunications system, for instance, such as a mobile communications system or wireless communications system. Moreover, in some embodiments, statistical or probability metrics can be used in addition to or instead of log likelihood ratios.
The actual steps taken in the disclosed processes, such as the process 600 illustrated in
Although the flow diagrams and approaches herein may be described in terms of outputting and receiving reliability values, for example, it should be understood that the output and received reliability values may actually be reliability information representing the reliability values output or received. For instance, reliability information itself can include one or more “0” or “1” values that may have no specific meaning when standing alone. However, when understood in a particular context, the one or more “0” or “1” values of the reliability information can represent a particular binary or non-binary value, for example, that may be output or received.
While certain embodiments have been described, these embodiments have been presented by way of example only, and are not intended to limit the scope of the protection. Indeed, the novel methods and systems described herein may be embodied in a variety of other forms. Furthermore, various omissions, substitutions and changes in the form of the methods and systems described herein may be made without departing from the spirit of the protection. For example, the various components illustrated in the figures may be implemented as software and/or firmware on a processor, ASIC/FPGA, or dedicated hardware. Hardware components, such as processors, ASICs, FPGAs, and the like, can include logic circuitry. Also, the features and attributes of the specific embodiments disclosed above may be combined in different ways to form additional embodiments, all of which fall within the scope of the present disclosure. Although the present disclosure provides certain preferred embodiments and applications, other embodiments that are apparent to those of ordinary skill in the art, including embodiments which do not provide all of the features and advantages set forth herein, are also within the scope of this disclosure.
The present application claims the benefit of priority under 35 U.S.C. §120 as a continuation of U.S. patent application Ser. No. 14/231,511 entitled “Non-Binary LDPC Decoder using Binary Subgroup Processing,” filed on Mar. 31, 2014, which claims the benefit of priority under 35 U.S.C. §119 as a nonprovisional of U.S. Provisional Patent Application No. 61/933,147 entitled “Non-Binary LDPC Decoder using Binary Subgroup Processing,” filed Jan. 29, 2014, the disclosures of which are hereby incorporated by reference in their entirety for all purposes.
Number | Name | Date | Kind |
---|---|---|---|
6856556 | Hajeck | Feb 2005 | B1 |
7126857 | Hajeck | Oct 2006 | B2 |
7190681 | Wu | Mar 2007 | B1 |
7430136 | Merry, Jr. et al. | Sep 2008 | B2 |
7447807 | Merry et al. | Nov 2008 | B1 |
7502256 | Merry, Jr. et al. | Mar 2009 | B2 |
7509441 | Merry et al. | Mar 2009 | B1 |
7596643 | Merry, Jr. et al. | Sep 2009 | B2 |
7653778 | Merry, Jr. et al. | Jan 2010 | B2 |
7685337 | Merry, Jr. et al. | Mar 2010 | B2 |
7685338 | Merry, Jr. et al. | Mar 2010 | B2 |
7685374 | Diggs et al. | Mar 2010 | B2 |
7733712 | Walston et al. | Jun 2010 | B1 |
7765373 | Merry et al. | Jul 2010 | B1 |
7898855 | Merry, Jr. et al. | Mar 2011 | B2 |
7912991 | Merry et al. | Mar 2011 | B1 |
7936603 | Merry, Jr. et al. | May 2011 | B2 |
7962792 | Diggs et al. | Jun 2011 | B2 |
8078918 | Diggs et al. | Dec 2011 | B2 |
8090899 | Syu | Jan 2012 | B1 |
8095851 | Diggs et al. | Jan 2012 | B2 |
8108692 | Merry et al. | Jan 2012 | B1 |
8122185 | Merry, Jr. et al. | Feb 2012 | B2 |
8127048 | Merry et al. | Feb 2012 | B1 |
8135903 | Kan | Mar 2012 | B1 |
8151020 | Merry, Jr. et al. | Apr 2012 | B2 |
8161227 | Diggs et al. | Apr 2012 | B1 |
8166245 | Diggs et al. | Apr 2012 | B2 |
8243525 | Kan | Aug 2012 | B1 |
8254172 | Kan | Aug 2012 | B1 |
8261012 | Kan | Sep 2012 | B2 |
8296625 | Diggs et al. | Oct 2012 | B2 |
8312207 | Merry, Jr. et al. | Nov 2012 | B2 |
8316176 | Phan et al. | Nov 2012 | B1 |
8341339 | Boyle et al. | Dec 2012 | B1 |
8375151 | Kan | Feb 2013 | B1 |
8392635 | Booth et al. | Mar 2013 | B2 |
8397107 | Syu et al. | Mar 2013 | B1 |
8407449 | Colon et al. | Mar 2013 | B1 |
8423722 | Deforest et al. | Apr 2013 | B1 |
8433858 | Diggs et al. | Apr 2013 | B1 |
8443167 | Fallone et al. | May 2013 | B1 |
8447920 | Syu | May 2013 | B1 |
8458435 | Rainey, III et al. | Jun 2013 | B1 |
8458556 | Planjery et al. | Jun 2013 | B2 |
8478930 | Syu | Jul 2013 | B1 |
8489854 | Colon et al. | Jul 2013 | B1 |
8503237 | Horn | Aug 2013 | B1 |
8521972 | Boyle et al. | Aug 2013 | B1 |
8549236 | Diggs et al. | Oct 2013 | B2 |
8559540 | Sun et al. | Oct 2013 | B2 |
8583835 | Kan | Nov 2013 | B1 |
8601311 | Horn | Dec 2013 | B2 |
8601313 | Horn | Dec 2013 | B1 |
8612669 | Syu et al. | Dec 2013 | B1 |
8612804 | Kang et al. | Dec 2013 | B1 |
8615681 | Horn | Dec 2013 | B2 |
8638602 | Horn | Jan 2014 | B1 |
8639872 | Boyle et al. | Jan 2014 | B1 |
8683113 | Abasto et al. | Mar 2014 | B2 |
8700834 | Horn et al. | Apr 2014 | B2 |
8700950 | Syu | Apr 2014 | B1 |
8700951 | Call et al. | Apr 2014 | B1 |
8706985 | Boyle et al. | Apr 2014 | B1 |
8707104 | Jean | Apr 2014 | B1 |
8707123 | Liu | Apr 2014 | B2 |
8713066 | Lo et al. | Apr 2014 | B1 |
8713357 | Jean et al. | Apr 2014 | B1 |
8719531 | Strange et al. | May 2014 | B2 |
8724422 | Agness et al. | May 2014 | B1 |
8725931 | Kang | May 2014 | B1 |
8745277 | Kan | Jun 2014 | B2 |
8751728 | Syu et al. | Jun 2014 | B1 |
8769190 | Syu et al. | Jul 2014 | B1 |
8769232 | Suryabudi et al. | Jul 2014 | B2 |
8775720 | Meyer et al. | Jul 2014 | B1 |
8782327 | Kang et al. | Jul 2014 | B1 |
8788778 | Boyle | Jul 2014 | B1 |
8788779 | Horn | Jul 2014 | B1 |
8788880 | Gosla et al. | Jul 2014 | B1 |
8792594 | Vojcic | Jul 2014 | B2 |
8793429 | Call et al. | Jul 2014 | B1 |
8935598 | Norrie | Jan 2015 | B1 |
8984365 | Norrie | Mar 2015 | B1 |
8990661 | Micheloni et al. | Mar 2015 | B1 |
9191256 | Vojcic | Nov 2015 | B2 |
9250994 | Vakilinia et al. | Feb 2016 | B1 |
9337864 | Vakilinia | May 2016 | B1 |
20100174849 | Walston et al. | Jul 2010 | A1 |
20100250793 | Syu | Sep 2010 | A1 |
20110087946 | Planjery et al. | Apr 2011 | A1 |
20110099323 | Syu | Apr 2011 | A1 |
20110283049 | Kang et al. | Nov 2011 | A1 |
20120260020 | Suryabudi et al. | Oct 2012 | A1 |
20120278531 | Horn | Nov 2012 | A1 |
20120284460 | Guda | Nov 2012 | A1 |
20120324191 | Strange et al. | Dec 2012 | A1 |
20130132638 | Horn et al. | May 2013 | A1 |
20130145106 | Kan | Jun 2013 | A1 |
20130290793 | Booth et al. | Oct 2013 | A1 |
20140059405 | Syu et al. | Feb 2014 | A1 |
20140101369 | Tomlin et al. | Apr 2014 | A1 |
20140115427 | Lu | Apr 2014 | A1 |
20140133220 | Danilak et al. | May 2014 | A1 |
20140136753 | Tomlin et al. | May 2014 | A1 |
20140149826 | Lu et al. | May 2014 | A1 |
20140157078 | Danilak et al. | Jun 2014 | A1 |
20140181432 | Horn | Jun 2014 | A1 |
20140223255 | Lu et al. | Aug 2014 | A1 |
Entry |
---|
DeClercq, et al., “Decoding Algorithms for Nonbinary LDPC Codes Over GF(q),” Communications, IEEE Transactions on, vol. 55, No. 4, pp. 633,643, Apr. 2007. |
DeClercq, et al., “Extended minSum algorithm for decoding LDPC codes over GF(q)”, IEEE Int. Symp. Inf. Theory, 2005. |
Song; et al., “Reduced-complexity decoding of Q-ary LDPC codes for magnetic recording,” Magnetics, IEEE Transactions on , vol. 39, No. 2, pp. 1081,1087, Mar. 2003. |
Savin, “Min-max decoding for non binary LDPC codes”, IEEE Int. Symp. Inf. Theory, 2008. |
Voicila, et al., “Low-complexity decoding for non-binary LDPC codes in high order fields,” Communications, IEEE Transactions on , vol. 58, No. 5, pp. 1365,1375, May 2010. |
Voicila, et al., “Low-Complexity, Low-Memory EMS Algorithm for Non-Binary LDPC Codes,” Communications, 2007. ICC '07. IEEE International Conference on , vol., No., pp. 671,676, Jun. 24-28, 2007. |
Wymeersch,et al., “Log-domain decoding of LDPC codes over GF(q)” , Proc. IEEE Int. Conf. Commun., pp. 772-776 2004. |
Number | Date | Country | |
---|---|---|---|
20160329910 A1 | Nov 2016 | US |
Number | Date | Country | |
---|---|---|---|
61933147 | Jan 2014 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 14231511 | Mar 2014 | US |
Child | 15150340 | US |