Interleaved encoding

Information

  • Patent Grant
  • 9584159
  • Patent Number
    9,584,159
  • Date Filed
    Thursday, July 3, 2014
    11 years ago
  • Date Issued
    Tuesday, February 28, 2017
    8 years ago
Abstract
A method for interleaved multi-dimensional encoding, the method may include receiving or generating a first version of a group of bits and a second version of the group of bits, wherein the first and second versions differ from each other by an arrangement of bits of the group of bits; and encoding the first and second versions of the groups of bits in an interleaved manner; wherein the encoding comprises calculating at least one codeword component of the first version by encoding a set of bits of the first version and at least a portion of a redundancy of at least one data entity of the second version and calculating at least one codeword component of the second version by encoding a set of bits of the second version and at least a portion of a redundancy of at least one data entity of the first version.
Description
BACKGROUND OF THE INVENTION

Multi-dimensional codes are widely used due to their potential efficiency. In NAND flash memory systems the reliability requirement dictates operation in extremely low output bit error rate (BER), for example, this can be output BER that is below ten by the power of minus fifteen.


For achieving such goal, the encoding system should have a very low error-floor. There are various methods of designing codes and decoder for low error floor. Novel methods for encoding and decoding for obtaining low-error-floor codes are suggested in this application.


SUMMARY

According to an embodiment of the invention there may be provided a method for interleaved multi-dimensional encoding, the method may include receiving or generating a first version of a group of bits and a second version of the group of bits, wherein the first and second versions differ from each other by an arrangement of bits of the group of bits; and encoding, by an encoder, the first and second versions of the groups of bits in an interleaved manner; wherein the encoding may include calculating at least one codeword component of the first version by encoding a set of bits of the first version and at least a portion of a redundancy of at least one data entity of the second version and calculating at least one codeword component of the second version by encoding a set of bits of the second version and at least a portion of a redundancy of at least one data entity of the first version.


The encoding may include calculating a minority of codeword components of the first version in response to at least portions of data entities of the second version and calculating a majority of codeword components of the first version regardless of the at least portions of data entities of the second version.


The encoding may include calculating a majority of codeword components of the first version in response to at least portions of data entities of the second version and calculating a minority of codeword components of the first version regardless of the at least portions of data entities of the second version.


The at least a portion of a redundancy of a certain data entity of the second version may affect a calculation of only a single codeword component of the first version.


The method may include calculating a certain codeword component of a version of the first and second versions without taking into account a redundancy of another codeword of another version of the first and second versions.


The at least a portion of a redundancy of a certain data entity of the second version may affect a calculation of multiple codeword components of the first version.


The one or more codeword components of the first version may differ by length from one or more codeword components of the second version.


The two or more codeword components of a same version out of the first and second versions may differ by length from each other.


The encoding may include calculating a first codeword component by encoding a first data entity that belongs to of the first version; calculating a second codeword component by encoding, before a completion of an encoding of the first version, a second data entity that belongs to the second version and at least a portion of the first codeword component; calculating a third codeword component by encoding a third data entity that belongs to the first version and at least a portion of the second codeword component; calculating a fourth codeword component by encoding a fourth data entity that belongs to the second version and at least a portion of the third codeword component.


The at least portion of the second codeword component may include one or more second codeword component redundancy bits.


The encoding may include calculating a first codeword component by encoding a first data entity that belongs to of the first version; calculating a second codeword component by encoding a second data entity that belongs to of the second version; calculating a third codeword component by encoding, before a completion of an encoding of the first version, a third data entity that belongs to the first version and at least a portion of the second codeword component; calculating a fourth codeword component by encoding a fourth data entity that belong to the second version and at least a portion of the first codeword component.


The multi-dimensional encoding may include encoding multiple (K) versions of the group of bits that correspond to K dimensions; wherein the method further may include jointly encoding portions of redundancies of a K'th dimension and portions of redundancies of a lower than K dimension to provide joint redundancy.


The joint redundancy may include multiple joint redundancy units, wherein at least one joint redundancy unit is generated by encoding at least a portion of a K'th dimension redundancy unit and at least a portion of a (K−q)'th redundancy portion, q being a positive integer that ranges between 1 and (K−1).


According to an embodiment of the invention there may be provided a method for multi-dimensional encoding, the method may include encoding, by an encoder, multiple versions of a group of bits that correspond to multiple dimensions; and jointly encoding portions of redundancies of a last dimension of the multiple dimensions and portions of redundancies of a not-last dimension to provide joint redundancy.


The joint redundancy may include multiple joint redundancy units, wherein at least one joint redundancy unit is generated by encoding at least a portion of a last dimension redundancy unit and at least a portion of the non-last redundancy portion.


According to an embodiment of the invention there may be provided a method for decoding an interleaved multi-dimensional codeword, the method may include receiving a multi-dimensional codeword that was encoded in an interleaved manner; and decoding, by a decoder, the multi-dimensional codeword; wherein the multi-dimensional codeword was calculated by receiving or generating a first version of a group of bits and a second version of the group of bits, wherein the first and second versions differ from each other by an arrangement of bits of the group of bits; an encoding the first and second versions of the groups of bits in the interleaved manner; wherein the encoding may include calculating at least one codeword component of the first version by encoding a set of bits of the first version and at least a portion of a redundancy of at least one data entity of the second version and calculating at least one codeword component of the second version by encoding a set of bits of the second version and at least a portion of a redundancy of at least one data entity of the first version.


According to an embodiment of the invention there may be provided a non-transitory computer readable medium that stores instructions that once executed by a computer cause the computer to perform the stages of receiving or generating a first version of a group of bits and a second version of the group of bits, wherein the first and second versions differ from each other by an arrangement of bits of the group of bits; and encoding the first and second versions of the groups of bits in an interleaved manner; wherein the encoding may include calculating at least one codeword component of the first version by encoding a set of bits of the first version and at least a portion of a redundancy of at least one data entity of the second version and calculating at least one codeword component of the second version by encoding a set of bits of the second version and at least a portion of a redundancy of at least one data entity of the first version.


According to an embodiment of the invention there may be provided a non-transitory computer readable medium that stores instructions that once executed by a computer cause the computer to perform the stages of encoding multiple versions of a group of bits that correspond to multiple dimensions; and jointly encoding portions of redundancies of a last dimension of the multiple dimensions and portions of redundancies of a not-last dimension to provide joint redundancy


According to an embodiment of the invention there may be provided a non-transitory computer readable medium that stores instructions that once executed by a computer cause the computer to perform the stages of receiving a multi-dimensional codeword that was encoded in an interleaved manner; and decoding the multi-dimensional codeword; wherein the multi-dimensional codeword was calculated by receiving or generating a first version of a group of bits and a second version of the group of bits, wherein the first and second versions differ from each other by an arrangement of bits of the group of bits; an encoding the first and second versions of the groups of bits in the interleaved manner; wherein the encoding may include calculating at least one codeword component of the first version by encoding a set of bits of the first version and at least a portion of a redundancy of at least one data entity of the second version and calculating at least one codeword component of the second version by encoding a set of bits of the second version and at least a portion of a redundancy of at least one data entity of the first version.


According to an embodiment of the invention there may be provided a system that may include an encoder; wherein the system is arranged to receive or generate a first version of a group of bits and a second version of the group of bits, wherein the first and second versions differ from each other by an arrangement of bits of the group of bits; and wherein the encoder is arranged to encode the first and second versions of the groups of bits in an interleaved manner; wherein the encoding may include calculating at least one codeword component of the first version by encoding a set of bits of the first version and at least a portion of a redundancy of at least one data entity of the second version and calculating at least one codeword component of the second version by encoding a set of bits of the second version and at least a portion of a redundancy of at least one data entity of the first version.


According to an embodiment of the invention there may be provided a system that may include an encoder; wherein the encoder is arranged to encode, multiple versions of a group of bits that correspond to multiple dimensions; and jointly encoding portions of redundancies of a last dimension of the multiple dimensions and portions of redundancies of a not-last dimension to provide joint redundancy


According to an embodiment of the invention there may be provided a system that may include an decoder; wherein the system is arranged to receive a multi-dimensional codeword that was encoded in an interleaved manner; wherein the decoder is arranged to decode, the multi-dimensional codeword; wherein the multi-dimensional codeword was calculated by receiving or generating a first version of a group of bits and a second version of the group of bits, wherein the first and second versions differ from each other by an arrangement of bits of the group of bits; an encoding the first and second versions of the groups of bits in the interleaved manner; wherein the encoding may include calculating at least one codeword component of the first version by encoding a set of bits of the first version and at least a portion of a redundancy of at least one data entity of the second version and calculating at least one codeword component of the second version by encoding a set of bits of the second version and at least a portion of a redundancy of at least one data entity of the first version.





BRIEF DESCRIPTION OF THE DRAWINGS

The subject matter regarded as the invention is particularly pointed out and distinctly claimed in the concluding portion of the specification. The invention, however, both as to organization and method of operation, together with objects, features, and advantages thereof, may best be understood by reference to the following detailed description when read with the accompanying drawings in which:



FIG. 1 illustrates a method according to an embodiment of the invention;



FIGS. 2-5 illustrate codewords according to various embodiments of the invention;



FIG. 6 illustrates a system that includes two dimensional encoder with folded redundancy encoding according to an embodiment of the invention;



FIG. 7 illustrates a method according to an embodiment of the invention;



FIGS. 8-10 illustrate a two dimensional codeword according to various embodiments of the invention; and



FIG. 11 illustrates a flow chart according to an embodiment of the invention.





DETAILED DESCRIPTION OF THE DRAWINGS

In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the invention. However, it will be understood by those skilled in the art that the present invention may be practiced without these specific details. In other instances, well-known methods, procedures, and components have not been described in detail so as not to obscure the present invention.


The subject matter regarded as the invention is particularly pointed out and distinctly claimed in the concluding portion of the specification. The invention, however, both as to organization and method of operation, together with objects, features, and advantages thereof, may best be understood by reference to the following detailed description when read with the accompanying drawings.


It will be appreciated that for simplicity and clarity of illustration, elements shown in the figures have not necessarily been drawn to scale. For example, the dimensions of some of the elements may be exaggerated relative to other elements for clarity. Further, where considered appropriate, reference numerals may be repeated among the figures to indicate corresponding or analogous elements.


Because the illustrated embodiments of the present invention may for the most part, be implemented using electronic components and circuits known to those skilled in the art, details will not be explained in any greater extent than that considered necessary as illustrated above, for the understanding and appreciation of the underlying concepts of the present invention and in order not to obfuscate or distract from the teachings of the present invention.


Any reference in the specification to a method should be applied mutatis mutandis to a system capable of executing the method and should be applied mutatis mutandis to a non-transitory computer readable medium that stores instructions that once executed by a computer result in the execution of the method.


Any reference in the specification to a system should be applied mutatis mutandis to a method that may be executed by the system and should be applied mutatis mutandis to a non-transitory computer readable medium that stores instructions that may be executed by the system.


Any reference in the specification to a non-transitory computer readable medium should be applied mutatis mutandis to a system capable of executing the instructions stored in the non-transitory computer readable medium and should be applied mutatis mutandis to method that may be executed by a computer that reads the instructions stored in the non-transitory computer readable medium.


Multi-dimensional encoding invoices receiving or generating multiple versions of a group of bits. The different versions differ from each other by the arrangement of bits. Different versions are associated with different dimensions. For example—assuming that that there are two dimensions and that the bits of the group of bits are arranged in a virtual (rectangular) matrix. According to a first arrangement of the bits, (first dimension) payloads are formed by the rows of the matrix. According to a second arrangement of the bits (second dimension) payloads are formed by the columns of the matrix. In a non-folded arrangement each payload occupies a single row or column. In a folded arrangement a single payload (of a single codeword component) can occupy more than a single row or column.


Various examples of multi-dimensional encoding are provided in U.S. Pat. Nos. 8,700,970, 8,341,502, 8,621,321, 8,510,639, 8,468,431, and US patent application 20130132793, all being incorporated herein by reference.


Prior art multi-dimensional encoding included serial concatenation, where a dimension is encoded only after the other dimension was entirely encoded. This way, the redundancy of one dimension is protected by the other dimension. However, the last dimension may be unprotected. Another prior art (3D application) the each dimension encoding generates a redundancy for codeword components of its dimension, the resulting overall redundancy may then be encoded with another encoder. This type of encoding is not too efficient as the redundancy is protected due to an additional code, and does not take part in the encoding process (like suggested in this invention).


According to an embodiment of the invention there is provided an interleaved multi-dimensional encoding scheme in which one or more encoding results of a first dimension affect one or more encoding results of a second dimension and one or more encoding results of the second dimension affect one or more encoding results of the first dimension. The interleaving can be applied on one, some, part or all group of bits of either one of the first and second dimensions. The interleaving may require that the encoding of a dimension out of the first and second dimensions is not completed before starting the encoding of the other dimension.


In the following examples it is assumed that there are two dimensions and that the bits are arranged in a two dimensional matrix. These are only non-limiting assumptions. There may be K dimensions and K may exceed 2. The bits may be arranged in different manners and the matrix is merely provided to simplify the explanation.



FIG. 1 illustrates method 300 according to an embodiment of the invention.


Method 300 may start by stage 310 of receiving or generating a first version of a group of bits and a second version of the group of bits, wherein the first and second versions differ from each other by an arrangement of bits of the group of bits.


One (or none) of the first and second versions may be the data unit. One or both first and second versions may differ from the data unit. One or both of the first and second versions of the data unit may be generated by interleaving.


The first and second versions are associated with first and second dimensions of the multi-dimensional encoding. Thus, encoding the first version may be referred to as first dimension encoding and encoding the second version may be referred to as second dimension encoding.


Stage 310 may be followed by stage 320 of encoding the first and second versions of the groups of bits in an interleaved manner.


Stage 320 may include stages 311, 322 and 324.


Stage 311 may include calculating a certain codeword component of a version (of the first and second versions) without taking into account a redundancy of another codeword of another version (of the first and second versions). For example—the first encoding of the first codeword component of the first or second version can be performed on a payload that may include only data.


Stage 322 may include calculating at least one codeword component of the first version by encoding a set of bits of the first version and at least a portion of a redundancy of at least one data entity of the second version.


Stage 324 may include calculating at least one codeword component of the second version by encoding a set of bits of the second version and at least a portion of a redundancy of at least one data entity of the first version.


Stages 322 and 324 may be executed for encoding a minority, a half, a majority of codeword components of the first version while the remaining (if such exist) codeword components can be calculated regardless of the at least portions of data entities of the second version.



FIGS. 2-4 illustrate a two-dimensional codeword 10 (and 200) that includes row payloads P11-P1811-18, each extending over more than a single row. First row payload P1111 includes only bits of a first version of a data unit. Other row payloads P12-P18 include bits of a first version of the data unit as well as redundancy bits of column codeword components. For example, row payloads P12 and P13 include bits of redundancy R21121. Every codeword component can be for example a short BCH (Bose-Chaudhuri-Hocquenghem) code, or a Hamming code, or any other short block code.


The two-dimensional codeword 10 includes column payloads P21-P2921-29, each extending over more than a single column. First column payload P2121 includes only bits of a second version of the data unit. Other column payloads P22-P29 include bits of a second version of the data unit as well as redundancy bits of row codeword components. For example, row payloads P22 and P23 include bits of redundancy R11111.


Because of the interleaved encoding, the redundancy bits (and the codeword components) are calculated in a serial manner. At any point of time, the redundancy of a codeword component can be calculated if all bits of the payload are available. When some bits are still unknown (for example—are redundancy bits that are not calculated yet) the calculation of the codeword component should be postponed.


This serial nature of the interleaving process is illustrated in FIG. 4. In this figure, gaps are left for redundancy bits that are not calculated yet.


The top part of FIG. 4 illustrates two calculated redundancies R11111 and R21121 while other redundancy bits are not calculated yet and there are gaps 150 at the locations of such redundancies.


The lower part of FIG. 4 illustrates four calculated redundancies R11111, R21121, R12112, and R22122 while other redundancy bits are not calculated yet and there are gaps 150 at the locations of such redundancies. R12112 and R22122 can be calculated only after R11111 and R21121 are calculated. The arrows demonstrate what part of the payload is used for generating R11111 and R21121 in the upper part of the figure, and then R12112 and R22122 on the lower part of FIG. 4.


It is noted that the number of row codeword components that can be affected by a redundancy of a single column component code can be one or more. The number of column codeword components that can be affected by a redundancy of a single row component code can be one or more. The payload length for every codeword component may also be different per codeword. A first example of a relationship between row and column component codes are illustrated in FIGS. 2-4. Another example is illustrated in FIG. 5.


It is noted that the interleaved encoding can include jumping between versions after encoding a single payload or after encoding multiple payloads. FIGS. 2-4 illustrated an encoding of a single payload per each version—before jumping to the calculation of the next two codewords. In this case the execution of stage 320 may include:

    • a. Calculating a first codeword component by encoding a first data entity that belongs to of the first version. For example—calculating R11111.
    • b. Calculating a second codeword component by encoding a second data entity that belongs to of the second version. For example—calculating R21121.
    • c. Calculating a third codeword component by encoding, before a completion of an encoding of the first version, a third data entity that belongs to the first version and at least a portion of the second codeword component. For example—calculating R12121.
    • d. Calculating a fourth codeword component by encoding a fourth data entity that belongs to the second version and at least a portion of the first codeword component. For example—calculating R22122.


Yet for another example—these stages may include calculating a first codeword component by encoding a first data entity that belongs to the first version; calculating a second codeword component by encoding, before a completion of an encoding of the first version, a second data entity that belongs to the second version and at least a portion of the first codeword component; calculating a third codeword component by encoding a third data entity that belongs to the first version and at least a portion of the second codeword component and calculating a fourth codeword component by encoding a fourth data entity that belongs to the second version and at least a portion of the third codeword component.


According to an embodiment of the invention, the interleaved encoding may be applied to protect redundancies.


In this case, stage 320 may be used for encoding multiple (K) versions of the group of bits that correspond to K dimensions.


Stage 320 may be followed by stage 330 of jointly encoding portions of redundancies of a K'th dimension and portions of redundancies of a lower than K dimension to provide joint redundancy.


The joint redundancy includes multiple joint redundancy units. At least one joint redundancy unit is generated by encoding at least a portion of a K'th dimension redundancy unit and at least a portion of a (K−q)'th redundancy portion, q being a positive integer that ranges between 1 and (K−1).



FIG. 6 illustrates a system that includes a two dimensional encoder 8 with folded redundancy encoding according to an embodiment of the invention.


The two dimensional encoder 8 may be included in a memory controller 9 that is coupled to a memory module 9′ such as a flash memory module. Memory controller 9 may also include an encoder 8′. FIG. 6 illustrates an encoder 8 that outputs a codeword. It may output one or more codeword component of the codeword.


Once a codeword component encoding is completely encoded (encoded codeword is ready, i.e. its redundancy is fully computed), its redundancy is passed to the encoders of the other dimension, and it is taken as additional input data to encoders of the other dimension. Consider for example, K-input bits, which pass through interleaver D01 on the first dimension, and through interleaver D12 of the other dimension. D0 has multiple encoders (D0 encoders 3) (which in a special case may be identical); each encoder receives a different portion of the D0-interleaved input bits.


D0 encoders 3 begin by encoding packets, which do not need D1-redundancy bits for encoding completion (the minimum is a single packet). Then each time D0 encoders 3 completed the encoding of a packet, it passes the associated redundancy bits through its D0-Redundancy-interleaver 5 to D1 encoders (D1 encoders 4), which use this input for jointly encoding the input data and the input redundancy, at the same time. The same applies to the D1 encoders 4-D1 encoders 4 begins by encoding packets which do not need D0-redundancy bits for encoding completion (the minimum is a single packet). Then each time D1 encoders 4 completed the encoding of a packet, it passes the encoded redundancy bits through its D1-Redundancy-interleaver 6 to D0 encoders (D0 encoders 3), which use this input for jointly encoding the input data and the input redundancy, at the same time.


That is, both D0 and D1 encoders 3 and 4 may operate in parallel (or in a serial manner) in order to provide intermittent results and enable protecting most of the redundancy bits generated by code components with codes on other dimensions. Naturally, the last code component on each dimension will not have an encoded redundancy, since it encodes the last portion of the input bits to the encoder. Therefore, the last few component codes may (optionally) have an additional D2-encoder, which encodes the less protected parity bits. Thus, the systematic codeword consists of K-input bits, D0-Redundancy, D1-Redundancy, and D2-Redundancy.


According to an embodiment of this invention, every codeword component can be of a different code rate. This creates an irregular folded BCH code, and may be used instead of having the D2-encoder. Methods for obtaining different code component strengths include for example, using varying length per component encoder, while using the same BCH parameters (field size—Q, and number of errors—t).



FIG. 7 illustrates a method 400 for multi-dimensional encoding, according to an embodiment of the invention.


Method 400 may start by stage 410 of encoding multiple versions of a group of bits that correspond to multiple dimensions. Stage 410 may include any stage of method 300. Other encoding schemes may be used.


Stage 410 may be followed by stage 420 of jointly encoding portions of redundancies of a last dimension of the multiple dimensions and portions of redundancies of a not-last dimension to provide joint redundancy.


The joint redundancy may include multiple joint redundancy units, wherein at least one joint redundancy unit is generated by encoding at least a portion of a last dimension redundancy unit and at least a portion of the non-last redundancy portion.



FIGS. 8-10 illustrates two dimensional codeword 200 according to various embodiments of the invention. It includes row payloads D1,1-D1,12210(1,1)-210(1,12) that occupy one row each and include only data bits. It also includes column payloads D2,1-D2,12220(1,1)-220(1,12) that occupy one row each and include only data bits.


The row payloads (first dimension, first version) were encoded to provide row redundancies R1,1-R1,12230(1,1)-230(1,12).


The column payloads (second dimension, second version) were encoded to provide column redundancies R2,1-R2,12240(2,1)-240(2,12).



FIG. 8 illustrates a first joint redundancy R3250 that includes first joint redundancy units, each is calculated by encoding a single row redundancy and multiple bits from multiple column redundancies. For example first joint redundancy unit 251 is calculated by encoding R1,3230(1,3) and multiple bits (241) from multiple column redundancies.



FIG. 9 illustrates a second joint redundancy R4260 that includes first joint redundancy units, each is calculated by encoding a single column redundancy and multiple bits from multiple row redundancies. For example second joint redundancy unit 261 is calculated by encoding R2,7240(2,7) and multiple bits (231) from multiple row redundancies.



FIG. 10 illustrates a first joint redundancy R3250 that includes first joint redundancy units, each is calculated by encoding a multiple bits from multiple column redundancies and multiple bits from multiple column redundancies. For example second joint redundancy unit 252 is calculated by encoding multiple bits (231) from row redundancies and multiple bits (241) from multiple column redundancies. For simplicity of explanation, the arrows connecting the multiple bits (241, 231) to second joint redundancy unit 252 were omitted. FIG. 10 also includes second joint redundancy 260.


It is noted that only one of the first and second joint redundancies can be provided, that the encoding can be applied to more than two dimensions, and that the encoding may be responsive to the data bits and not just to the redundancies.


It is noted that the decoding process may be done in various manners. The decoding can also be iterative decoding. Non-limiting examples of decoding include:

    • a. Iterative irregular multi-dimensional decoding (using codeword components of different size and/or different rate).
    • b. Using soft decoding with list decoding.
    • c. Applying hard and/or soft decoding with false correction elimination (FCE) methods.
    • d. Performing hard decoding with intersections decoding.


The invention may also be implemented in a computer program for running on a computer system, at least including code portions for performing steps of a method according to the invention when run on a programmable apparatus, such as a computer system or enabling a programmable apparatus to perform functions of a device or system according to the invention. The computer program may cause the storage system to allocate disk drives to disk drive groups.


A computer program is a list of instructions such as a particular application program and/or an operating system. The computer program may for instance include one or more of a subroutine, a function, a procedure, an object method, an object implementation, an executable application, an applet, a servlet, a source code, an object code, a shared library/dynamic load library, and/or other sequence of instructions designed for execution on a computer system.


The computer program may be stored internally on a non-transitory computer readable medium. All or some of the computer program may be provided on computer readable media permanently, removably or remotely coupled to an information processing system. The computer readable media may include, for example and without limitation, any number of the following magnetic storage media including disk and tape storage media; optical storage media such as compact disk media (e.g., CD-ROM, CD-R, etc.) and digital video disk storage media; nonvolatile memory storage media including semiconductor-based memory units such as FLASH memory, EEPROM, EPROM, ROM; ferromagnetic digital memories; MRAM; volatile storage media including registers, buffers or caches, main memory, RAM, etc.


A computer process typically includes an executing (running) program or portion of a program, current program values and state information, and the resources used by the operating system to manage the execution of the process. An operating system (OS) is the software that manages the sharing of the resources of a computer and provides programmers with an interface used to access those resources. An operating system processes system data and user input, and responds by allocating and managing tasks and internal system resources as a service to users and programs of the system.


The computer system may for instance include at least one processing unit, associated memory and a number of input/output (I/O) devices. When executing the computer program, the computer system processes information according to the computer program and produces resultant output information via I/O devices.


In the foregoing specification, the invention has been described with reference to specific examples of embodiments of the invention. It will, however, be evident that various modifications and changes may be made therein without departing from the broader spirit and scope of the invention as set forth in the appended claims.


Moreover, the terms “front,” “back,” “top,” “bottom,” “over,” “under” and the like in the description and in the claims, if any, are used for descriptive purposes and not necessarily for describing permanent relative positions. It is understood that the terms so used are interchangeable under appropriate circumstances such that the embodiments of the invention described herein are, for example, capable of operation in other orientations than those illustrated or otherwise described herein.


The connections as discussed herein may be any type of connection suitable to transfer signals from or to the respective nodes, units or devices, for example via intermediate devices. Accordingly, unless implied or stated otherwise, the connections may for example be direct connections or indirect connections. The connections may be illustrated or described in reference to being a single connection, a plurality of connections, unidirectional connections, or bidirectional connections. However, different embodiments may vary the implementation of the connections. For example, separate unidirectional connections may be used rather than bidirectional connections and vice versa. In addition, plurality of connections may be replaced with a single connection that transfers multiple signals serially or in a time multiplexed manner. Likewise, single connections carrying multiple signals may be separated out into various different connections carrying subsets of these signals. Therefore, many options exist for transferring signals.


Although specific conductivity types or polarity of potentials have been described in the examples, it will be appreciated that conductivity types and polarities of potentials may be reversed.


Each signal described herein may be designed as positive or negative logic. In the case of a negative logic signal, the signal is active low where the logically true state corresponds to a logic level zero. In the case of a positive logic signal, the signal is active high where the logically true state corresponds to a logic level one. Note that any of the signals described herein may be designed as either negative or positive logic signals. Therefore, in alternate embodiments, those signals described as positive logic signals may be implemented as negative logic signals, and those signals described as negative logic signals may be implemented as positive logic signals.


Furthermore, the terms “assert” or “set” and “negate” (or “deassert” or “clear”) are used herein when referring to the rendering of a signal, status bit, or similar apparatus into its logically true or logically false state, respectively. If the logically true state is a logic level one, the logically false state is a logic level zero. Moreover, if the logically true state is a logic level zero, the logically false state is a logic level one.


Those skilled in the art will recognize that the boundaries between logic blocks are merely illustrative and that alternative embodiments may merge logic blocks or circuit elements or impose an alternate decomposition of functionality upon various logic blocks or circuit elements. Thus, it is to be understood that the architectures depicted herein are merely exemplary, and that in fact many other architectures may be implemented which achieve the same functionality.


Any arrangement of components to achieve the same functionality is effectively “associated” such that the desired functionality is achieved. Hence, any two components herein combined to achieve a particular functionality may be seen as “associated with” each other such that the desired functionality is achieved, irrespective of architectures or intermedial components. Likewise, any two components so associated can also be viewed as being “operably connected,” or “operably coupled,” to each other to achieve the desired functionality.


Furthermore, those skilled in the art will recognize that boundaries between the above described operations merely illustrative. The multiple operations may be combined into a single operation, a single operation may be distributed in additional operations and operations may be executed at least partially overlapping in time. Moreover, alternative embodiments may include multiple instances of a particular operation, and the order of operations may be altered in various other embodiments.


Also for example, in one embodiment, the illustrated examples may be implemented as circuitry located on a single integrated circuit or within a same device. Alternatively, the examples may be implemented as any number of separate integrated circuits or separate devices interconnected with each other in a suitable manner.


Also for example, the examples, or portions thereof, may implemented as soft or code representations of physical circuitry or of logical representations convertible into physical circuitry, such as in a hardware description language of any appropriate type.


Also, the invention is not limited to physical devices or units implemented in non-programmable hardware but can also be applied in programmable devices or units able to perform the desired device functions by operating in accordance with suitable program code, such as mainframes, minicomputers, servers, workstations, personal computers, notepads, personal digital assistants, electronic games, automotive and other embedded systems, cell phones and various other wireless devices, commonly denoted in this application as ‘computer systems’.


However, other modifications, variations and alternatives are also possible. The specifications and drawings are, accordingly, to be regarded in an illustrative rather than in a restrictive sense.


In the claims, any reference signs placed between parentheses shall not be construed as limiting the claim. The word ‘comprising’ does not exclude the presence of other elements or steps then those listed in a claim. Furthermore, the terms “a” or “an,” as used herein, are defined as one or more than one. Also, the use of introductory phrases such as “at least one” and “one or more” in the claims should not be construed to imply that the introduction of another claim element by the indefinite articles “a” or “an” limits any particular claim containing such introduced claim element to inventions containing only one such element, even when the same claim includes the introductory phrases “one or more” or “at least one” and indefinite articles such as “a” or “an.” The same holds true for the use of definite articles. Unless stated otherwise, terms such as “first” and “second” are used to arbitrarily distinguish between the elements such terms describe. Thus, these terms are not necessarily intended to indicate temporal or other prioritization of such elements. The mere fact that certain measures are recited in mutually different claims does not indicate that a combination of these measures cannot be used to advantage.


While certain features of the invention have been illustrated and described herein, many modifications, substitutions, changes, and equivalents will now occur to those of ordinary skill in the art. It is, therefore, to be understood that the appended claims are intended to cover all such modifications and changes as fall within the true spirit of the invention.

Claims
  • 1. A method for interleaved multi-dimensional encoding, comprising: receiving or generating a first version of a group of bits and a second version of the group of bits, wherein the first and second versions differ from each other by an arrangement of bits of the group of bits; andencoding, by an encoder, the first and second versions of the groups of bits in an interleaved manner; wherein the encoding comprises: calculating at least one codeword component of the first version by encoding a set of bits of the first version and at least a portion of a redundancy of at least one data entity of the second version andcalculating at least one codeword component of the second version by encoding a set of bits of the second version and at least a portion of a redundancy of at least one data entity of the first version.
  • 2. The method according to claim 1 wherein the encoding comprises calculating a minority of codeword components of the first version in response to at least portions of data entities of the second version and calculating a majority of codeword components of the first version regardless of the at least portions of data entities of the second version.
  • 3. The method according to claim 1 wherein the encoding comprises calculating a majority of codeword components of the first version in response to at least portions of data entities of the second version and calculating a minority of codeword components of the first version regardless of the at least portions of data entities of the second version.
  • 4. The method according to claim 1 wherein at least a portion of a redundancy of a certain data entity of the second version affects a calculation of only a single codeword component of the first version.
  • 5. The method according to claim 1 comprising calculating a certain codeword component of a version of the first and second versions without taking into account a redundancy of another codeword of another version of the first and second versions.
  • 6. The method according to claim 1 wherein at least a portion of a redundancy of a certain data entity of the second version affects a calculation of multiple codeword components of the first version.
  • 7. The method according to claim 1 wherein one or more codeword components of the first version differ by length from one or more codeword components of the second version.
  • 8. The method according to claim 1 wherein two or more codeword components of a same version out of the first and second versions differ by length from each other.
  • 9. The method according to claim 1 wherein the encoding comprises: calculating a first codeword component by encoding a first data entity that belongs to the first version;calculating a second codeword component by encoding, before a completion of an encoding of the first version, a second data entity that belongs to the second version and at least a portion of the first codeword component;calculating a third codeword component by encoding a third data entity that belongs to the first version and at least a portion of the second codeword component;calculating a fourth codeword component by encoding a fourth data entity that belongs to the second version and at least a portion of the third codeword component.
  • 10. The method according to claim 8 wherein the at least portion of the second codeword component comprises one or more second codeword component redundancy bits.
  • 11. The method according to claim 1 wherein the encoding comprises: calculating a first codeword component by encoding a first data entity that belongs to the first version;calculating a second codeword component by encoding a second data entity that belongs to of the second version;calculating a third codeword component by encoding, before a completion of an encoding of the first version, a third data entity that belongs to the first version and at least a portion of the second codeword component;calculating a fourth codeword component by encoding a fourth data entity that belongs to the second version and at least a portion of the first codeword component.
  • 12. The method according to claim 1 wherein the multi-dimensional encoding comprises encoding multiple (K) versions of the group of bits that correspond to K dimensions; wherein the method further comprises jointly encoding portions of redundancies of a K'th dimension and portions of redundancies of a lower than K dimension to provide joint redundancy.
  • 13. The method according to claim 12 wherein the joint redundancy comprises multiple joint redundancy units, wherein at least one joint redundancy unit is generated by encoding at least a portion of a K'th dimension redundancy unit and at least a portion of a (K−q)'th redundancy portion, q being a positive integer that ranges between 1 and (K−1).
  • 14. A method for multi-dimensional encoding, the method comprises: encoding, by an encoder, multiple versions of a group of bits that correspond to multiple dimensions; andjointly encoding portions of redundancies of a last dimension of the multiple dimensions and portions of redundancies of a not-last dimension to provide joint redundancy.
  • 15. The method according to claim 13 wherein the joint redundancy comprises multiple joint redundancy units, wherein at least one joint redundancy unit is generated by encoding at least a portion of a last dimension redundancy unit and at least a portion of the non-last redundancy portion.
  • 16. A method for decoding an interleaved multi-dimensional codeword, the method comprises: receiving a multi-dimensional codeword that was encoded in an interleaved manner; anddecoding, by a decoder, the multi-dimensional codeword;wherein the multi-dimensional codeword that was encoded in an interleaved manner; anddecoding, by a decoder, the multi-dimensional codeword;wherein the multi-dimensional codeword was calculated by receiving or generating a first version of a group of bits and a second version of the group of bits, wherein the first and second versions differ from each other by an arrangement of bits of the group of bits; an encoding the first and second versions of the groups of bits in the interleaved manner; wherein the encoding comprises: calculating at least one codeword component of the first version by encoding a set of bits of the first version and at least a portion of a redundancy of at least one data entity of the second version and calculating at least one codeword component of the second version by encoding a set of bits of the second version and at least a portion of a redundancy of at least one data entity of the first version.
  • 17. A non-transitory computer readable medium that stores instructions that once executed by a computer cause the computer to perform the stages of: receiving or generating a first version of a group of bits and a second version of the group of bits, wherein the encoding comprises: calculating at least one codeword component of the first version by encoding a set of bits of the first version and at least a portion of a redundancy of at least one data entity of the second version andcalculating at least one codeword component of the first version by encoding a set of bits of the first version and at least a portion of a redundancy of at least one data entity of the second version andcalculating at least one codeword component of the second version by encoding a set of bits of the second version and at least a portion of a redundancy of at least one data entity of the first version.
  • 18. A memory controller comprising an encoder; wherein the memory controller is arranged to receive or generate a first version of a group of bits and a second version of the group of bits, wherein the first and second versions differ from each other by an arrangement of bits of the group of bits; andwherein the encoder is arranged to encode the first and second versions of the groups of bits in an interleaved manner; wherein the encoding comprises: calculating at least one codeword component of the first version by encoding a set of bits of the first version and at least a portion of a redundancy of at least one data entity of the second version andcalculating at least one codeword component of the second version by encoding a set of bits of the second version and at least a portion of a redundancy of at least one data entity of the first version.
US Referenced Citations (339)
Number Name Date Kind
4430701 Christian et al. Feb 1984 A
4463375 Macovski Jul 1984 A
4584686 Fritze Apr 1986 A
4589084 Fling et al. May 1986 A
4777589 Boettner et al. Oct 1988 A
4866716 Weng Sep 1989 A
5003597 Merkle Mar 1991 A
5077737 Leger et al. Dec 1991 A
5297153 Baggen et al. Mar 1994 A
5305276 Uenoyama Apr 1994 A
5592641 Doyle et al. Jan 1997 A
5623620 Alexis et al. Apr 1997 A
5640529 Hasbun Jun 1997 A
5657332 Auclair et al. Aug 1997 A
5663901 Harari et al. Sep 1997 A
5724538 Morris et al. Mar 1998 A
5729490 Calligaro et al. Mar 1998 A
5740395 Wells et al. Apr 1998 A
5745418 Hu et al. Apr 1998 A
5778430 Ish et al. Jul 1998 A
5793774 Usui et al. Aug 1998 A
5805228 Proctor et al. Sep 1998 A
5920578 Zook et al. Jul 1999 A
5926409 Engh et al. Jul 1999 A
5933368 Hu et al. Aug 1999 A
5956268 Lee Sep 1999 A
5956473 Hu et al. Sep 1999 A
5968198 Balachandran Oct 1999 A
5982659 Irrinki et al. Nov 1999 A
6011741 Harari et al. Jan 2000 A
6016275 Han Jan 2000 A
6023783 Divsalar et al. Feb 2000 A
6038634 Ji et al. Mar 2000 A
6081878 Estakhri et al. Jun 2000 A
6094465 Stein et al. Jul 2000 A
6119245 Hiratsuka Sep 2000 A
6182261 Haller et al. Jan 2001 B1
6192497 Yang et al. Feb 2001 B1
6195287 Hirano Feb 2001 B1
6199188 Shen et al. Mar 2001 B1
6209114 Wolf et al. Mar 2001 B1
6259627 Wong Jul 2001 B1
6272052 Miyauchi Aug 2001 B1
6278633 Wong et al. Aug 2001 B1
6279133 Vafai et al. Aug 2001 B1
6301151 Engh et al. Oct 2001 B1
6304985 Sindhushayana et al. Oct 2001 B1
6370061 Yachareni et al. Apr 2002 B1
6374383 Weng Apr 2002 B1
6405341 Maru Jun 2002 B1
6504891 Chevallier Jan 2003 B1
6532169 Mann et al. Mar 2003 B1
6532556 Wong et al. Mar 2003 B1
6553533 Demura et al. Apr 2003 B2
6560747 Weng May 2003 B1
6563877 Abbaszadeh May 2003 B1
6637002 Weng et al. Oct 2003 B1
6639865 Kwon Oct 2003 B2
6643331 Farrell et al. Nov 2003 B1
6674665 Mann et al. Jan 2004 B1
6675281 Oh et al. Jan 2004 B1
6704902 Shinbashi et al. Mar 2004 B1
6735734 Liebetreu et al. May 2004 B1
6751766 Guterman et al. Jun 2004 B2
6772274 Estakhri Aug 2004 B1
6781910 Smith Aug 2004 B2
6792569 Cox et al. Sep 2004 B2
6873543 Smith et al. Mar 2005 B2
6891768 Smith et al. May 2005 B2
6914809 Hilton et al. Jul 2005 B2
6915477 Gollamudi et al. Jul 2005 B2
6952365 Gonzalez et al. Oct 2005 B2
6961890 Smith Nov 2005 B2
6968421 Conley Nov 2005 B2
6990012 Smith et al. Jan 2006 B2
6996004 Fastow et al. Feb 2006 B1
6999854 Roth Feb 2006 B2
7010739 Feng et al. Mar 2006 B1
7012835 Gonzalez et al. Mar 2006 B2
7038950 Hamilton et al. May 2006 B1
7068539 Guterman et al. Jun 2006 B2
7079436 Perner et al. Jul 2006 B2
7143336 Moon Nov 2006 B1
7149950 Spencer et al. Dec 2006 B2
7173978 Zhang et al. Feb 2007 B2
7177977 Chen et al. Feb 2007 B2
7188228 Chang et al. Mar 2007 B1
7191379 Adelmann et al. Mar 2007 B2
7196946 Chen et al. Mar 2007 B2
7203874 Roohparvar Apr 2007 B2
7212426 Park et al May 2007 B2
7290203 Emma et al. Oct 2007 B2
7292365 Knox Nov 2007 B2
7301928 Nakabayashi et al. Nov 2007 B2
7315916 Bennett et al. Jan 2008 B2
7388781 Litsyn et al. Jun 2008 B2
7395404 Gorobets et al. Jul 2008 B2
7441067 Gorobets et al. Oct 2008 B2
7443729 Li Oct 2008 B2
7450425 Aritome Nov 2008 B2
7454670 Kim et al. Nov 2008 B2
7466575 Shalvi et al. Dec 2008 B2
7533328 Alrod et al. May 2009 B2
7558109 Brandman et al. Jul 2009 B2
7593263 Sokolov et al. Sep 2009 B2
7610433 Randell et al. Oct 2009 B2
7613043 Cornwell et al. Nov 2009 B2
7619922 Li et al. Nov 2009 B2
7681105 Sim-Tang et al. Mar 2010 B1
7697326 Sommer et al. Apr 2010 B2
7706182 Shalvi et al. Apr 2010 B2
7716538 Gonzalez et al. May 2010 B2
7804718 Kim Sep 2010 B2
7805663 Brandman et al. Sep 2010 B2
7805664 Yang et al. Sep 2010 B1
7844877 Litsyn et al. Nov 2010 B2
7911848 Eun et al. Mar 2011 B2
7961797 Yang et al. Jun 2011 B1
7975192 Sommer et al. Jul 2011 B2
8020073 Emma et al. Sep 2011 B2
8108590 Chow et al. Jan 2012 B2
8122328 Liu et al. Feb 2012 B2
8159881 Yang Apr 2012 B2
8190961 Yang et al. May 2012 B1
8250324 Haas et al. Aug 2012 B2
8300823 Bojinov et al. Oct 2012 B2
8305812 Levy et al. Nov 2012 B2
8327246 Weingarten et al. Dec 2012 B2
8341502 Steiner Dec 2012 B2
8407560 Ordentlich et al. Mar 2013 B2
8417893 Khmelnitsky et al. Apr 2013 B2
8468431 Steiner Jun 2013 B2
8510639 Steiner Aug 2013 B2
8700970 Steiner Apr 2014 B2
8949700 Azadet Feb 2015 B2
20010034815 Dugan et al. Oct 2001 A1
20020049947 Sridharan et al. Apr 2002 A1
20020063774 Hillis et al. May 2002 A1
20020085419 Kwon et al. Jul 2002 A1
20020154769 Petersen et al. Oct 2002 A1
20020156988 Toyama et al. Oct 2002 A1
20020174156 Birru et al. Nov 2002 A1
20030014582 Nakanishi Jan 2003 A1
20030065876 Lasser Apr 2003 A1
20030101404 Zhao et al. May 2003 A1
20030105620 Bowen Jun 2003 A1
20030177300 Lee et al. Sep 2003 A1
20030192007 Miller et al. Oct 2003 A1
20040015771 Lasser et al. Jan 2004 A1
20040030971 Tanaka et al. Feb 2004 A1
20040059768 Denk et al. Mar 2004 A1
20040080985 Chang et al. Apr 2004 A1
20040153722 Lee Aug 2004 A1
20040153817 Norman et al. Aug 2004 A1
20040181735 Xin Sep 2004 A1
20040203591 Lee Oct 2004 A1
20040210706 In et al. Oct 2004 A1
20050013165 Ban Jan 2005 A1
20050018482 Cemea et al. Jan 2005 A1
20050083735 Chen et al. Apr 2005 A1
20050117401 Chen et al. Jun 2005 A1
20050120265 Pline et al. Jun 2005 A1
20050128811 Kato et al. Jun 2005 A1
20050138533 Le-Bars et al. Jun 2005 A1
20050144213 Simkins et al. Jun 2005 A1
20050144368 Chung et al. Jun 2005 A1
20050169057 Shibata et al. Aug 2005 A1
20050172179 Brandenberger et al. Aug 2005 A1
20050213393 Lasser Sep 2005 A1
20050243626 Ronen Nov 2005 A1
20060059406 Micheloni et al. Mar 2006 A1
20060059409 Lee Mar 2006 A1
20060064537 Oshima Mar 2006 A1
20060101193 Murin May 2006 A1
20060104372 Coene May 2006 A1
20060195651 Estakhri et al. Aug 2006 A1
20060203587 Li et al. Sep 2006 A1
20060221692 Chen Oct 2006 A1
20060248434 Radke et al. Nov 2006 A1
20060268608 Noguchi et al. Nov 2006 A1
20060282411 Fagin et al. Dec 2006 A1
20060284244 Forbes et al. Dec 2006 A1
20060294312 Walmsley Dec 2006 A1
20070025157 Wan et al. Feb 2007 A1
20070063180 Asano et al. Mar 2007 A1
20070081388 Joo Apr 2007 A1
20070098069 Gordon May 2007 A1
20070103992 Sakui et al. May 2007 A1
20070104004 So et al. May 2007 A1
20070109858 Conley et al. May 2007 A1
20070124652 Litsyn et al. May 2007 A1
20070140006 Chen et al. Jun 2007 A1
20070143561 Gorobets Jun 2007 A1
20070150694 Chang et al. Jun 2007 A1
20070168625 Cornwell et al. Jul 2007 A1
20070171714 Wu et al. Jul 2007 A1
20070171730 Ramamoorthy et al. Jul 2007 A1
20070180346 Murin Aug 2007 A1
20070223277 Tanaka et al. Sep 2007 A1
20070226582 Tang et al. Sep 2007 A1
20070226592 Radke Sep 2007 A1
20070228449 Takano et al. Oct 2007 A1
20070253249 Kang et al. Nov 2007 A1
20070253250 Shibata et al. Nov 2007 A1
20070263439 Cornwell et al. Nov 2007 A1
20070266291 Toda et al. Nov 2007 A1
20070271494 Gorobets Nov 2007 A1
20070297226 Mokhlesi Dec 2007 A1
20080010581 Alrod et al. Jan 2008 A1
20080028014 Hilt et al. Jan 2008 A1
20080049497 Mo Feb 2008 A1
20080055989 Lee et al. Mar 2008 A1
20080082897 Brandman et al. Apr 2008 A1
20080092026 Brandman et al. Apr 2008 A1
20080104309 Cheon et al. May 2008 A1
20080112238 Kim et al. May 2008 A1
20080116509 Harari et al. May 2008 A1
20080126686 Sokolov et al. May 2008 A1
20080127104 Li et al. May 2008 A1
20080128790 Jung Jun 2008 A1
20080130341 Shalvi et al. Jun 2008 A1
20080137413 Kong et al. Jun 2008 A1
20080137414 Park et al. Jun 2008 A1
20080141043 Flynn et al. Jun 2008 A1
20080148115 Sokolov et al. Jun 2008 A1
20080158958 Shalvi et al. Jul 2008 A1
20080159059 Moyer Jul 2008 A1
20080162079 Astigarraga et al. Jul 2008 A1
20080168216 Lee Jul 2008 A1
20080168320 Cassuto et al. Jul 2008 A1
20080181001 Shalvi Jul 2008 A1
20080198650 Shalvi et al. Aug 2008 A1
20080198652 Shalvi et al. Aug 2008 A1
20080201620 Gollub Aug 2008 A1
20080209114 Chow et al. Aug 2008 A1
20080219050 Shalvi et al. Sep 2008 A1
20080225599 Chae Sep 2008 A1
20080250195 Chow et al. Oct 2008 A1
20080263262 Sokolov et al. Oct 2008 A1
20080282106 Shalvi et al. Nov 2008 A1
20080285351 Shlick et al. Nov 2008 A1
20080301532 Uchikawa et al. Dec 2008 A1
20090024905 Shalvi et al. Jan 2009 A1
20090027961 Park et al. Jan 2009 A1
20090043951 Shalvi et al. Feb 2009 A1
20090046507 Aritome Feb 2009 A1
20090072303 Prall et al. Mar 2009 A9
20090091979 Shalvi Apr 2009 A1
20090103358 Sommer et al. Apr 2009 A1
20090106485 Anholt Apr 2009 A1
20090113275 Chen et al. Apr 2009 A1
20090125671 Flynn May 2009 A1
20090132755 Radke May 2009 A1
20090144598 Yoon et al. Jun 2009 A1
20090144600 Perlmutter et al. Jun 2009 A1
20090150599 Bennett Jun 2009 A1
20090150748 Egner et al. Jun 2009 A1
20090157964 Kasorla et al. Jun 2009 A1
20090158126 Perlmutter et al. Jun 2009 A1
20090168524 Golov et al. Jul 2009 A1
20090187803 Anholt et al. Jul 2009 A1
20090199074 Sommer Aug 2009 A1
20090213653 Perlmutter et al. Aug 2009 A1
20090213654 Perlmutter et al. Aug 2009 A1
20090228761 Perlmutter et al. Sep 2009 A1
20090240872 Perlmutter et al. Sep 2009 A1
20090282185 Van Cauwenbergh Nov 2009 A1
20090282186 Mokhlesi et al. Nov 2009 A1
20090287930 Nagaraja Nov 2009 A1
20090300269 Radke et al. Dec 2009 A1
20090323942 Sharon et al. Dec 2009 A1
20100005270 Jiang Jan 2010 A1
20100025811 Bronner et al. Feb 2010 A1
20100030944 Hinz Feb 2010 A1
20100058146 Weingarten et al. Mar 2010 A1
20100064096 Weingarten et al. Mar 2010 A1
20100088557 Weingarten et al. Apr 2010 A1
20100091535 Sommer et al. Apr 2010 A1
20100095186 Weingarten Apr 2010 A1
20100110787 Shalvi et al. May 2010 A1
20100115376 Shalvi et al. May 2010 A1
20100122113 Weingarten et al. May 2010 A1
20100124088 Shalvi et al. May 2010 A1
20100131580 Kanter et al. May 2010 A1
20100131806 Weingarten et al. May 2010 A1
20100131809 Katz May 2010 A1
20100131826 Shalvi et al. May 2010 A1
20100131827 Sokolov et al. May 2010 A1
20100131831 Weingarten et al. May 2010 A1
20100146191 Katz Jun 2010 A1
20100146192 Weingarten et al. Jun 2010 A1
20100149881 Lee et al. Jun 2010 A1
20100172179 Gorobets et al. Jul 2010 A1
20100174853 Lee et al. Jul 2010 A1
20100180073 Weingarten et al. Jul 2010 A1
20100199149 Weingarten et al. Aug 2010 A1
20100211724 Weingarten Aug 2010 A1
20100211833 Weingarten Aug 2010 A1
20100211856 Weingarten Aug 2010 A1
20100241793 Sugimoto et al. Sep 2010 A1
20100246265 Moschiano et al. Sep 2010 A1
20100251066 Radke Sep 2010 A1
20100253555 Weingarten et al. Oct 2010 A1
20100257309 Barsky et al. Oct 2010 A1
20100269008 Leggette et al. Oct 2010 A1
20100293321 Weingarten Nov 2010 A1
20100318724 Yeh Dec 2010 A1
20110051521 Levy et al. Mar 2011 A1
20110055461 Steiner et al. Mar 2011 A1
20110093650 Kwon et al. Apr 2011 A1
20110096612 Steiner et al. Apr 2011 A1
20110099460 Dusija et al. Apr 2011 A1
20110119562 Steiner et al. May 2011 A1
20110153919 Sabbag Jun 2011 A1
20110161775 Weingarten Jun 2011 A1
20110194353 Hwang et al. Aug 2011 A1
20110209028 Post et al. Aug 2011 A1
20110214029 Steiner et al. Sep 2011 A1
20110214039 Steiner et al. Sep 2011 A1
20110246792 Weingarten Oct 2011 A1
20110246852 Sabbag Oct 2011 A1
20110252187 Segal et al. Oct 2011 A1
20110252188 Weingarten Oct 2011 A1
20110271043 Segal et al. Nov 2011 A1
20110302428 Weingarten Dec 2011 A1
20120001778 Steiner et al. Jan 2012 A1
20120005554 Steiner et al. Jan 2012 A1
20120005558 Steiner et al. Jan 2012 A1
20120005560 Steiner et al. Jan 2012 A1
20120008401 Katz et al. Jan 2012 A1
20120008414 Katz et al. Jan 2012 A1
20120017136 Ordentlich et al. Jan 2012 A1
20120051144 Weingarten et al. Mar 2012 A1
20120063227 Weingarten et al. Mar 2012 A1
20120066441 Weingarten Mar 2012 A1
20120110250 Sabbag et al. May 2012 A1
20120124273 Goss et al. May 2012 A1
20120246391 Meir et al. Sep 2012 A1
20130132793 Ha May 2013 A1
Foreign Referenced Citations (1)
Number Date Country
WO2009053963 Apr 2009 WO
Non-Patent Literature Citations (37)
Entry
Search Report of PCT Patent Application WO 2009/118720 A3, Mar. 4, 2010.
Search Report of PCT Patent Application WO 2009/095902 A3, Mar. 4, 2010.
Search Report of PCT Patent Application WO 2009/078006 A3, Mar. 4, 2010.
Search Report of PCT Patent Application WO 2009/074979 A3, Mar. 4, 2010.
Search Report of PCT Patent Application WO 2009/074978 A3, Mar. 4, 2010.
Search Report of PCT Patent Application WO 2009/072105 A3, Mar. 4, 2010.
Search Report of PCT Patent Application WO 2009/072104 A3, Mar. 4, 2010.
Search Report of PCT Patent Application WO 2009/072103 A3, Mar. 4, 2010.
Search Report of PCT Patent Application WO 2009/072102 A3, Mar. 4, 2010.
Search Report of PCT Patent Application WO 2009/072101 A3, Mar. 4, 2010.
Search Report of PCT Patent Application WO 2009/072100 A3, Mar. 4, 2010.
Search Report of PCT Patent Application WO 2009/053963 A3, Mar. 4, 2010.
Search Report of PCT Patent Application WO 2009/053962 A3, Mar. 4, 2010.
Search Report of PCT Patent Application WO 2009/053961 A3, Mar. 4, 2010.
Search Report of PCT Patent Application WO 2009/037697 A3, Mar. 4, 2010.
Yani Chen, Kcshab K. Parhi, “Small Area Parallel Chien Search Architectures for Long BCH Codes”, Ieee Transactions On Very Large Scale Integration(VLSI) Systems, vol. 12, No. 5, May 2004.
Yuejian Wu, “Low Power Decoding of BCH Codes”, Nortel Networks, Ottawa, Ont., Canada, in Circuits and systems, 2004. ISOAS '04, Proceeding of the 2004 International Symposium on Circuits and Systems, published May 23-26, 2004, vol. 2, pp. II-369-72 vol. 2.
Michael Purser, “introduction To Error Correcting Codes”, Artech House Inc., 1995.
Ron M. Roth, “Introduction to Coding Theory”, Cambridge University Press, 2006.
Akash Kumar, Sergei Sawitzki, “High-Throughput and Low Power Architectures for Reed Solomon Decoder”, (a.kumar at tue.nl, Eindhoven University of Technology and sergei.sawitzki at philips.com), Oct. 2005.
Todd K.Moon, “Error Correction Coding Mathematical Methods and Algorithms”, A John Wiley & Sons, Inc., 2005.
Richard E. Blahut, “Algebraic Codes for Data Transmission”, Cambridge University Press, 2003.
David Esseni, Bruno Ricco, “Trading-Off Programming Speed and Current Absorption in Flash Memories with the Ramped-Gate Programming Technique”, Ieee Transactions On Electron Devices, vol. 47, No. 4, Apr. 2000.
Giovanni Campardo, Rino Micheloni, David Novosel, “VLSI-Design of Non-Volatile Memories”, Springer Berlin Heidelberg New York, 2005.
John G. Proakis, “Digital Communications”, 3rd ed., New York: McGraw-Hill, 1995.
J.M. Portal, H. Aziza, D. Nee, “EEPROM Memory: Threshold Voltage Built In Self Diagnosis”, ITC International Test Conference, Paper 2.1, Feb. 2005.
J.M. Portal, H. Aziza, D. Nee, “EEPROM Diagnosis Based on Threshold Voltage Embedded Measurement”, Journal of Electronic Testing: Theory and Applications 21, 33-42, 2005.
G. Tao, A. Scarpa, J. Dijkstra, W. Stidl, F. Kuper, “Data retention prediction for modern floating gate non-volatile memories”, Microelectronics Reliability 40 (2000), 1561-1566.
T. Hirncno, N. Matsukawa, H. Hazama, K. Sakui, M. Oshikiri, K. Masuda, K. Kanda, Y. Itoh, J. Miyamoto, “A New Technique for Measuring Threshold Voltage Distribution in Flash EEPROM Devices”, Proc. IEEE 1995 Int. Conference on Microelectronics Test Structures, vol. 8, Mar. 1995.
Boaz Eitan, Guy Cohen, Assaf Shappir, Eli Lusky, Amichai Givant, Meir Janai, Ilan Bloom, Yan Polansky, Oleg Dadashev, Avi Lavan, Ran Sahar, Eduardo Maayan, “4-bit per Cell NROM Reliability”, Appears on the website of Saifun.com, 2005.
Paulo Cappelletti, Clara Golla, Piero Olivo, Enrico Zanoni, “Flash Memories”, Kluwer Academic Publishers, 1999.
JEDEC Standard, “Stress-Test-Driven Qualification of Integrated Circuits”, JEDEC Solid State Technology Association. JEDEC Standard No. 47F pp. 1-26, Dec. 2007.
Dempster, et al., “Maximum Likelihood from Incomplete Data via the EM Algorithm”, Journal of the Royal Statistical Society. Series B (Methodological), vol. 39, No. 1 (1997), pp. 1-38.
Mielke, et al., “Flash EEPROM Threshold Instabilities due to Charge Trapping During Program/Erase Cycling”, IEEE Transactions on Device and Materials Reliabiiity, vol. 4, No. 3, Sep. 2004, pp. 335-344.
Daneshbeh, “Bit Serial Systolic Architectures for Multiplicative Inversion and Division over GF (2)”, A thesis presented to the University of Waterloo, Ontario, Canada, 2005, pp. 1-118.
Chen, Formulas for the solutions of Quadratic Equations over GF (2), IEEE Trans. Inform. Theory, vol. IT-28, No. 5, Sep. 1982, pp. 792-794.
Berlekamp et al., “On the Solution of Algebraic Equations over Finite Fields”, Inform. Cont. 10, Oct. 1967, pp. 553-564.