The present invention relates generally to computer memory and more particularly to flash memory.
The state of the art is believed to be represented by the following documents:
Wikipedia states that “In coding theory, puncturing is the process of removing some of the parity bits after encoding with an error-correction code. This has the same effect as encoding with an error-correction code with a higher rate, or less redundancy. However, with puncturing the same decoder can be used regardless of how many bits have been punctured, thus puncturing considerably increases the flexibility of the system without significantly increasing its complexity. In some cases, a pre-defined pattern of puncturing is used in an encoder. Then, the inverse operation, known as depuncturing, is implemented by the decoder.” The disclosures of all publications and patent documents mentioned in the specification, and of the publications and patent documents cited therein directly or indirectly, are hereby incorporated by reference.
The following terms may be construed either in accordance with any definition thereof appearing in the prior art literature or in accordance with the specification, or as follows:
Bit error rate: a parameter that a flash memory device manufacturer commits to vis a vis its customers, expressing the maximum proportion of wrongly read bits (wrongly read bits/total number of bits) that users of the flash memory device need to expect during the stipulated lifetime of the flash memory device e.g. 10 years.
Block: a set of flash memory device cells which must, due to physical limitations of the flash memory device, be erased together. Also termed erase sector, erase block.
Cell: A component of flash memory that stores one bit of information (in single-level cell devices) or n bits of information (in a multi-level device having 2 exp n levels). Typically, each cell comprises a floating-gate transistor. n may or may not be an integer.
Charge level: the measured voltage of a cell which reflects its electric charge.
Cycling: Repeatedly writing new data into flash memory cells and repeatedly erasing the cells between each two writing operations.
Decision regions: Regions extending between adjacent decision levels
Demapping: basic cell-level reading function in which a digital n-tuple originally received from an outside application is derived from a physical value representing a physical state in the cell having a predetermined correspondence to the digital n-tuple.
Digital value or “logical value”: n-tuple of bits represented by a cell in flash memory capable of generating 2 exp n distinguishable levels of a typically continuous physical value such as charge, where n may or may not be an integer
Erase cycle: The relatively slow process of erasing a block of cells (erase sector), each block typically comprising more than one page, or, in certain non-flash memory devices, of erasing a single cell or the duration of so doing. An advantage of erasing cells collectively in blocks as in flash memory, rather than individually, is enhanced programming speed: Many cells and typically even many pages of cells are erased in a single erase cycle.
Erase-write cycle: The process of erasing a block of cells (erase sector), each block typically comprising a plurality of pages, and subsequently writing new data into at least some of them. The terms “program” and “write” are used herein generally interchangeably.
Flash memory: Non-volatile computer memory including cells that are erased block by block, each block typically comprising more than one page, but are written into and read from, page by page. Includes NOR-type flash memory, NAND-type flash memory, and PRAM, e.g. Samsung PRAM, inter alia, and flash memory devices with any suitable number of levels per cell, such as but not limited to 2, 4, or 8.
Mapping: basic cell-level writing function in which incoming digital n-tuple is mapped to a program level by inducing a program level in the cell, having a predetermined correspondence to the incoming digital value.
Page: A portion, typically 512 or 2048 or 4096 bytes in size, of a NAND flash memory device. Writing can be performed page by page, as opposed to erasing which can be performed only erase sector by erase sector. A few bytes, typically 16-32 for every 512 data bytes are associated with each page (typically 16, 64 or 128 per page), for storage of error correction information. A typical block may include 32 512-byte pages or 64 2048-byte pages.
Puncturing: generating a new code by removing parity bits from an original code. The new code is decoded by using a reduced set of parity questions, or as for the original code but with less parity questions. The reduced set of parity bits characterizing the new code is known to the decoder and is typically predetermined in the design stage.
Precise read, soft read: Cell threshold voltages are read at a precision (number of bits) greater than the number of Mapping levels (2^n). The terms precise read or soft read are interchangeable. In contrast, in “hard read”, cell threshold voltages are read at a precision (number of bits) smaller than the number of Mapping levels (2^n).
Present level, Charge level: The amount of charge in the cell. The Amount of charge currently existing in a cell, at the present time, as opposed to “program level”, the amount of charge originally induced in the cell (i.e. at the end of programming)
Program: same as “write”.
Program level (programmed level, programming level): amount of charge originally induced in a cell to represent a given digital value, as opposed to “present level”.
Reprogrammability (Np): An aspect of flash memory quality. This is typically operationalized by a reprogram ability parameter, also termed herein “Np”, denoting the number of times that a flash memory can be re-programmed (number of erase-write cycles that the device can withstand) before the level of errors is so high as to make an unacceptably high proportion of those errors irrecoverable given a predetermined amount of memory devoted to redundancy. Typically recoverability is investigated following a conventional aging simulation process which simulates or approximates the data degradation effect that a predetermined time period e.g. a 10 year period has on the flash memory device, in an attempt to accommodate for a period of up to 10 years between writing of data in flash memory and reading of the data therefrom.
Retention: of original physical levels induced in the cells; retention is typically below 100% resulting in deterioration of original physical levels into present levels.
Retention time: the time which elapses between programming of a page and reading of the same page, typically without voltage supply and without data refresh.
Significance level: of a bit, “most” for a most significant bit, “least” for a least significant bit, and intermediate for an intermediate level bit. If the symbols has 3 bits (bit1, bit2, bit3), bit1 is the MSB.
Symbol: Digital value Threshold level: the voltage (e.g.) against which the charge level of a cell is measured.
Puncturing: reducing the number of redundancy bits generated during an error correction encoding procedure typically by erasing some of these bits using a predetermined “puncture rule” or “puncture pattern” such as “delete every fourth bit”.
In this specification, the terms “decision levels” and “threshold levels” are used interchangeably. “Reliably storing” and “reliable” are used to indicate that certain information is stored with high reliability in the sense that statistically, it can be expected to be read without error throughout the guaranteed lifetime of the flash memory device.
The following terms are used herein generally synonymously: amount of redundancy. level of redundancy (e.g. per page). length of redundancy, redundancy length. A Flash page is typically divided into two sections: section 1 for the data (payload) and section 2 for redundancy. In the second, redundancy section the system typically stores the code's parity bits (or bytes) and some management information.
Certain embodiments of the present invention seek to provide apparatus and methods for encoding and decoding for purposes of error correction in data stored in flash memory devices, including determining a BER which is specific to less than all pages in the flash memory device, and using code rates and numbers of redundancy cells which are adapted to the specific BER values.
Certain embodiments of the present invention seek to provide a method for writing in a flash memory cell comprising writing on a plurality of pages with a plurality of levels of error including encoding data intended for each of the plurality of pages using a level of redundancy for each page which corresponds to the level of error.
Certain embodiments of the present invention seek to provide use of different numbers of redundancy cells per each page 1, . . . N in any of many groups of N pages each having one of N different probabilities of errors respectively.
Certain embodiments of the present invention seek to provide use of multiple codes per each page 1, . . . N in any of many groups of N pages each having one of N different probabilities of errors respectively.
Certain embodiments of the present invention seek to provide use of a different level of puncturing from a single code to generate code per each page 1, . . . N in any of many groups of N pages each having one of N different probabilities of errors respectively.
Certain embodiments of the present invention seek to provide use of a combination of an inner variable rate code (e.g. convolution) and outer fixed rate code (e.g. algebraic).
Certain embodiments of the present invention seek to provide rearranging unequal coded groups of pages into equal coded pages that fit the mapping to multi levels.
Certain embodiments of the present invention seek to provide a flash memory device having a file system which knows that each of N pages has a non-equal number of redundancy bits housed in one of the N pages. This file system could be implemented in the flash memory device, e.g. in the device's microcontroller, and/or in an external controller.
Certain embodiments of the present invention provide a method for writing into flash memory which includes some or all of the following steps, suitably ordered e.g. as follows:
a. Receive logical pages from host. Place N logical pages into a temporary memory, such as an SRAM internal to a microcontroller internal to or external to the flash memory device.
b. Treat the N logical pages as a group and code the first, second, . . . . Nth logical page in the group using for each logical page a page-specific ECC (error correction code) code rate typically computed during set-up or during the design process of the flash memory device to match that page's probability of error, thereby to generate encoded logical pages of different lengths, which typically are also stored in temporary memory.
c. Even up (e.g. equalize) the lengths of the encoded logical pages (so that no space will be wasted in subsequent interleaved storage of N different length logical pages in the same physical page) by moving redundancy bits pertaining to at least one encoded logical page suffering from a high probability of error to at least one encoded logical page enjoying a low probability of error, either separately from step b or integrally with step b.
d. Interleave the N evened encoded logical pages into a physical page in flash memory, e.g. by grouping the bits in each individual position within all of the N evened encoded logical pages together into an N-bit symbol, and mapping each such symbol into a threshold voltage value to be stored in a cell within a physical page. Always use the bit contributed by the first evened encoded logical page as the MSB of the symbol and the bit contributed by the last evened encoded logical page as the LSB of the symbol, and similarly for the intermediate pages.
Certain embodiments of the present invention provide a method for reading from flash memory which includes some or all of the following steps, suitably ordered e.g. as follows:
e. Responsive to a read command pertaining to an individual logical page, retrieve a physical page storing a group of N interleaved evened logical pages from flash memory including the individual logical page, by de-mapping and consolidating each interleaved logical page back into a consecutive logical page.
f. Restore original uneven-length logical pages by moving redundancy bits pertaining to encoded logical pages suffering from high probability of error which are stored in another encoded logical page enjoying a low probability of error, back to where they belong (back to the high error probability pages).
g. Perform error correction decoding on the restored original uneven-length logical pages and return decoded logical pages to host.
Any suitable processor, display and input means may be used to process, display, store and accept information, including computer programs, in accordance with some or all of the teachings of the present invention, such as but not limited to a conventional personal computer processor, workstation or other programmable device or computer or electronic computing device, either general-purpose or specifically constructed, for processing; a display screen and/or printer and/or speaker for displaying; machine-readable memory such as optical disks, CDROMs, magnetic-optical discs or other discs; RAMs, ROMs, EPROMs, EEPROMs, magnetic or optical or other cards, for storing, and keyboard or mouse for accepting. The term “process” as used above is intended to include any type of computation or manipulation or transformation of data represented as physical, e.g. electronic, phenomena which may occur or reside e.g. within registers and/or memories of a computer.
The above devices may communicate via any conventional wired or wireless digital communication means, e.g. via a wired or cellular telephone network or a computer network such as the Internet.
The apparatus of the present invention may include, according to certain embodiments of the invention, machine readable memory containing or otherwise storing a program of instructions which, when executed by the machine, implements some or all of the apparatus, methods, features and functionalities of the invention shown and described herein. Alternatively or in addition, the apparatus of the present invention may include, according to certain embodiments of the invention, a program as above which may be written in any conventional programming language, and optionally a machine for executing the program such as but not limited to a general purpose computer which may optionally be configured or activated in accordance with the teachings of the present invention.
Any trademark occurring in the text or drawings is the property of its owner and occurs herein merely to explain or illustrate one example of how an embodiment of the invention may be implemented.
Unless specifically stated otherwise, as apparent from the following discussions, it is appreciated that throughout the specification discussions, utilizing terms such as, “processing”, “computing”, “estimating”, “selecting”, “ranking”, “grading”, “calculating”, “determining”, “generating”, “reassessing”, “classifying”, “generating”, “producing”, “stereo-matching”, “registering”, “detecting”, “associating”, “superimposing”, “obtaining” or the like, refer to the action and/or processes of a computer or computing system, or processor or similar electronic computing device, that manipulate and/or transform data represented as physical, such as electronic, quantities within the computing system's registers and/or memories, into other data similarly represented as physical quantities within the computing system's memories, registers or other such information storage, transmission or display devices.
Certain embodiments of the present invention are illustrated in the following drawings:
Today's flash memory devices store information with high density on Flash memory cells with ever smaller dimensions. In addition, Multi-Layer Cells (MLC) store several bits per cell by setting the amount of charge in the cell. The amount of charge is then measured by a detector, as measured by a threshold voltage of the transistor gate. Due to inaccuracies during the programming procedure and/or charge loss due to retention (pass of time) and temperature, the measured levels during a Read operation typically suffer from detection errors. The small dimensions of the Flash memory cells result in cells that can store very small amounts of charge, enhancing the effects of inaccuracies due to programming and charge loss. Thus, modern single level cells (SLC) and MLC devices have significantly increased bit error rate (BER), decreasing the reliability of the device.
Flash memory devices are organized into (physical) pages. Each page contains a section allocated for data (ranging from 512 bytes-4 Kbytes) and a small number of bytes (ranging from 16-32 bytes for every 512 data bytes) containing redundancy and back pointers. The redundancy bytes are used to store error correcting information, for correcting errors which may have occurred during or after a writing step. Each Read and Program operation is typically performed on an entire page. A number of pages are grouped together to form an Erase Block (EB). A page typically cannot be erased unless the entire EB which contains it is erased.
An important measure of a Flash memory device quality is the number of times (Np) it may be reprogrammed before irrecoverable errors occur: the higher the number of program-erase cycles, the higher the BER. Thus, today's MLC devices can perform around Np=1000 cycles or less before the allocation of 16-32 bytes of redundancy per 512 bytes of data bytes becomes insufficient to correct errors. SLC devices usually perform better but provide a much lower density and hence their prices are much higher. Note that following Np program-erase cycles the device is still operational but the BER is higher. Furthermore, in many devices (e.g. NROM Flash memory devices), this behavior is predictable and it can be shown that the number of redundancy bytes required to correct these errors does not jump rapidly.
Conventional flash memory devices use a fixed amount of redundancy to store code information and use a single coding schema for all pages.
Reference is now made to
Typically, the flash memory device is used to store logical pages including multiple bits of information, e.g. 8192 information bits per logical page, provided by the host 100. The bits arriving from the host are grouped, e.g. by the microcontroller 110, into N-bit symbols (where N may be a suitable integer such as, for example, 2, 3 or 4), thereby to form a sequence of symbols to be stored in the flash memory device. For example, if N is 3, the bits may be grouped into symbols such as the 8 symbols appearing in the “symbol” column of the table of
Certain embodiments of the invention shown and described herein are particularly suited to applications in which the microcontroller groups bits arriving from the host into N-bit symbols, such that each symbol includes one bit each from N different logical pages, and such that adjacent bits from each N logical pages grouped together by the microcontroller, are grouped into adjacently positioned symbols in the sequence of symbols (for example: the 1st bits from each of 3 logical pages L1, L2 and L3 may be grouped into a 3-bit symbol forming the 1st symbol in the sequence, the 2nd bits from each of the same 3 logical pages may be grouped into a 3-bit symbol forming the 2nd symbol in the sequence, and so on, until all bits in the 3 logical pages have been grouped into symbols in the sequence at which point the microcontroller begins to group the bits of 3 other logical pages, perhaps L4, L5 and L6.
Certain embodiments of the invention are also particularly suited to applications in which bits supplied by each logical page are always stored in the same significant level of each symbol (e.g. most significant bit (MSB), least significant bit (LSB) or other intermediate bit significance level if any). For example, in each (three bit) symbol storing data from logical pages L1, L2 and L3, the MSB might always represent a bit taken from logical page L1, the intermediate bit might always represent a bit from logical page L2, and the LSB of each symbol might always represent a bit taken from logical page L3.
Other embodiments may employ alternative schemes for sorting the bits of logical pages into the various significant levels. For example, consider an application in which three bit symbols are used and each symbol represents bits from three logical pages. For each three logical pages L1, L2 and L3 containing bits of information, the first half of page L1's bits (say) may be stored in the MSB of the symbol, the second half of page L1's bits (say) may be stored in the LSB of the symbol, all of page L2's bits (say) may be stored in the intermediate significant bit of each symbol, the first half of page L3's bits (say) may be stored in the LSB of the symbol and the second half of page L3's bits (say) may be stored in the MSB of the symbol.
Certain embodiments of the invention shown and described herein are further particular suited to applications in which the sequence of symbols is stored in a corresponding sequence of cells within the flash memory, each cell being capable of storing M=2^N possible voltage values, such as those shown in the “threshold voltage” column of
It is appreciated that adjacent threshold voltage levels can be confused with one another when read, as shown in the “possible error” columns of the tables of
According to certain embodiments of the present invention, the number of redundancy cells added to each logical page and/or the code rate used for each logical page does not assume that the probability of error in the bits representing each logical page is the same. Instead, it is assumed that the probability of error in the bits representing each logical page varies over each N logical page, e.g. doubling between each pair of successive logical pages.
Example: Referring to the table of
3 logical pages are provided each having 1024 bytes (8192 bits). Each page is coded and the result is 3 coded logical pages in which coded logical page 1 has 1024+50=1074 Bytes, coded logical page 2 has 1024+75=1099 Bytes, and coded logical page 3 has 1024+100=1124 Bytes. These are to be rearranged in 3 equal size pages e.g. according to
Page 1a, page 2a and page 3a all have 1099 bytes (=(1074+1099+1124)/3). Those equal size pages are converted to symbols by grouping 3 bits per symbol. The 1099 symbols are programmed into a single physical page with 1099 cells. This physical page has 1024 cells for the data and 75 cells for the code redundancy.
A method for programming symbols into voltages (P0, P1, . . . P7) is presented in
The present invention need not be limited to cases where the flash is manufactured specifically for performing the method of this invention. Flash memory systems may be transformed e.g. by software configuration to perform the method of the present invention. Coding is typically not performed by the flash device but rather by the controller.
Reference is now made to
The method of
Step 210: establish a line for manufacturing flash memory devices.
Step 220: estimate page-specific bit error rates for individual logical pages in flash memory (e.g. per page position 1, 2, . . . N in a characteristically repeating group of N logical pages such as N physical pages used to store successive sets of N bits in one or more logical pages, wherein the N bits in each set are typically stored respectively and successively in the N physical pages). Step 220 is described in further detail below with reference to
Step 230: determine physical page size by determining number of data cells per page and then computing the number of redundancy bytes to be allocated to each page (e.g. per page position 1, 2, . . . N in a characteristically repeating group of N pages) as a function of its page-specific bit error rate. A method for performing step 230 is described below in detail with reference to the graph of
Step 240: Configure file system of microcontroller 110 to accommodate for allocation of redundancy bytes per logical page (e.g. per page position 1, 2, . . . N in a characteristically repeating group of N pages) according to step 230. Optionally, file system is configured to accommodate similar-sized or identically sized pages each with an average number of redundancy cells (average taken over each group of pages) wherein redundancy cells for each page are allocated to that page or to another page such that pages having a low page-specific bit error rate contribute some redundancy cells to pages having a high page-specific bit error rate and hence insufficient redundancy cells.
According to certain embodiments of the present invention, each three (say) logical pages are represented (contribute a bit to) each symbol, each physical page contains bits from three (say) logical pages, and each three (say) physical pages contain encoded data and redundancy from three (say) logical pages.
According to certain variations on the embodiment of
Step 250: compute page-specific code rate for each individual logical page based on page-specific BER computed in step 220, e.g. using the formula:
Code rate=data bytes/(redundancy bytes+data bytes),
Step 260: Select suitable error correction code according to step 250, e.g. a code whose code rate equals or exceeds maximum logical page-specific code rate over all pages and which can be punctured down to the page-specific code rate of each logical page and generate appropriate error correction encoding/decoding circuits accordingly in the microcontroller 110 and/or I-F controller of host 100.
Puncturing is only one option to generate multi rate code. It is relevant to soft decoders. One possible programming method includes some or all of the following steps, suitably ordered e.g. as shown:
One possible reading method includes some or all of the following steps, suitably ordered e.g. as shown:
A particular advantage of the “puncturing” embodiment is that generally the same encoding/decoding circuits can be used for all pages, use of these circuits for different pages differing only in the puncturing rule employed.
Certain differences between the embodiment of
Modern Flash memory devices use, say, M=4, 8 or 16 voltage levels per cell to store, say, N=2, 3, 4 bits per cell (M=2^N). The Flash memory micro-controller 110 can map N bits from N successive pages into a single level, m. A multi level Flash memory error probability is not even for all bits. The MSB in general has lower error probability from the LSB. An interleaving schema may be used that maps the first page in each of many groups of N pages to the MSB and the last page in each of the groups to the LSB, and similarly for the intermediate bits. The result is groups of N pages with variable error performance per each page in the group. Or, we can use N bits from a page as a group with variable error rate per each bit in the group.
In
The error probability for the first logical page may be the probability of mistakenly recognizing one of the 4 lower levels as one of the 4 upper levels. The error probability may decrease rapidly if voltage levels are used which have absolute values greater than the distance between adjacent levels. As a result page number 1 may have a lower error probability from page number 2. Page number 2 may have a lower error probability than page number 3.
Conventionally, a single ECC (error correction code) is used to encode each logical page and the flash memory manufacturer designs the redundancy to accommodate the worst case condition e.g., in the illustrated example, to accommodate the most error-prone logical page namely logical page 3. The result is poor cost effectiveness because more cells are allocated for redundancy than needed. If in the example logical page 1 has a BER of P_error_1=Px than the BER of page 2 is approximately 2Px and Page 3's BER is approximately 4Px. The redundancy is proportional to the error probability. Thus logical page 1 can manage with only one quarter of the redundancy cells required by logical page 3 and logical page 2 can manage with only half the number of redundancy cells required by logical page 3.
The logical page probability can be extended to any combination of the above. Generating the first by combining ⅓ of the first page with ⅔ of the third page results in P_error=3 Px. And the complimentary third page is combining ⅔ of the first page with ⅓ of the last page will resulted in 2Px. This example will yield P_error_1=3Px, P_error_2=2Px, P_error_3=2Px, e.g. as shown in
Generally, therefore, each logical page need not be represented by only a single significance level. Instead, several significance levels may be used to represent several respective portions of a single page. For example, assume that the total redundancy of each, say, three pages is limited by the hardware to 335 cells and assigning a single significance level to each of the three pages results in redundancy lengths (number of redundancy cells) of 75-100-160 for the 3 pages respectively. If for some reason it is desired to provide redundancy lengths of, say, 50-125-160, this may only be achievable by using different significant levels for different portions within a single page.
Prior art systems, e.g. as shown in
Since variable redundancy is used per page in each group, N codes are typically used, differing in their code rates—one code per each of the N pages in each group. One possibility is to puncture a single code down to N different code rates, typically using an increased number of puncturing per each page in the group.
It is appreciated that according to some embodiments one code is used which is adjusted to three different bit error rates using puncturing. Alternatively, three different codes may be used together to accommodate the 3 different bit error rates e.g. as shown in
Certain embodiments of the present invention are suitable, inter alia, for any application in which a physical page of M-level memory cells, e.g. flash memory cells (M>=2), are used to store N logical pages of data such that each M-level cell stores a bit from each of the N logical pages. In these applications, each of the N logical pages may be regarded as having a unique bit significance rank extending, say, from 1 to N, such that bits of the logical page having a bit significance rank of 1 are stored in the LSBs of each cell, whereas the bits of the logical page having a bit significance rank of N are stored in the MSBs of each cell, and the bits of the logical pages having intermediate bit significance ranks (2 to (N−1)) are stored in bits of ascending significance respectively within the various flash memory cells. According to certain embodiments, for at least one, and optionally all, pairs of logical pages ‘A’ and ‘B’ having a corresponding pair of bit significance ranks r_A>r_B respectively (A and B may for example be the logical pages stored in the MSBs and LSBs respectively), the error correction code for logical page ‘A’ is designed to have less redundancy bits (parity bits) than the error correction code for logical page ‘B’. Typically, the redundancy for each logical page is limited to that required to overcome the particular probability of error characterizing that logical page.
The encoding rate and amount of redundancy added may be varied according to the number of bits per cell. For example, in 2 bit per cell applications, there may be only two code rates whereas in 4 bit per cell applications there may be four code rates. When a program (write) operation is initiated by the host, the processing of the data may be as described below with reference to
Reference is now made to
Step 400. The “Host” 100 (
Step 410. A “Variable Rate Encoder/Decoder functionality residing e.g. in microcontroller 110 encodes the logical pages and adds redundancy. The amount of redundancy added per page depends on the rate indication of the page which in turn corresponds to the page's index in the group. In an example, perhaps the page 1 redundancy is 5%, the page 2 redundancy is 10% and the page 3 redundancy is 15% (as shown in
The output of step 410, for each group of N logical pages, is N coded logical pages each with a different redundancy length, depending on the rate indication of the page which in turn corresponds to the page's index in the group. Typically, different percentages of the original page lengths are added to each page.
Step 420: Compute the average coded page length for each group of N pages. This computation need not be effected each time writing is performed. Instead, computation may be carried out in advance, analogously to prior art flash devices where the bit error rate of the encoder/decoder is determined in advance. However, in accordance with certain embodiments of the present invention, more than one bit error rate, such as 3 bit error rates, are determined in advance.
Step 430: Allocate redundancy bits from longer coded pages to shorter coded pages until all coded pages are of the same length, typically the average length computed in step 420 (it is appreciated that the redundancy bits are not physically moved from one coded page to another, the above explanation being intuitive rather than technical). If N is odd, one possible allocation scheme is that redundancy bits which cause coded page N, which is the longest, to exceed the average length can be moved to coded page 1, which is the shortest; redundancy bits which cause coded page N−1 to exceed the average length can be moved to coded page 2, and generally, redundancy bits can be moved from all overly long coded page N-k to coded page k+1, because for all relevant k, coded page k+1 lacks exactly the number of bits by which coded page N-k exceeds the average page length. Alternatively, the allocation scheme need not relate to oddness/even-ness of N.
Step 440: Page mapping: map each group of N bits to one of the M voltage levels. Mapping typically uses g
ray coding. The physical page supplying the most significant bit is termed the first physical page. The physical page supplying the least significant bit is termed the last physical page.
Step 450: The generated voltage level (one of the M voltage levels) is programmed into a cell.
Step 460: Steps 440 and 450 are repeated until the last group of N bits generated from the N physical pages has been programmed into a last cell.
The above steps, 400 et al, need not be performed each time memory is read; the same is the case for various of the steps of
Each time the host 100 of
Step 500: The host 100's I/F controller or microcontroller 110 issues a read command to read a cell's voltage value and de-maps it into bits until it generates N bit sets representing the encoded N pages, each bit set with equal length. These bit sets may be stored in temporary memory (SRAM).
Step 510: The host 100's I/F controller or microcontroller 110 decomposes the equal length bit sets into N unequal bit sets by reversing step 430. To follow the example presented above in step 430, redundancy bits within the first page which actually belong to the last page are restored to the last page, redundancy bits within the second page which actually belong to the second-to-last page are restored to the second-to-last page, and so forth.
Step 520: The N unequal bit sets are fed into N decoding circuits respectively having code rates determined in accordance with step 250 of
Step 530: The N logical pages output by the N decoding circuits respectively are transferred to the host 100.
Referring again to
Step 220 of
Reference is now made to
Step 600: Perform a multiplicity of erase and program cycles on one or more example flash memory devices according to a specification, e.g. 1000 cycles or 10,000 cycles.
Step 610: Bake the device to simulate several years of retention, such as 1 or 10 years of retention.
Step 620: Group the, say, 4 Gb bits in the reference block into symbols (example: ‘00’, ‘01’, ‘11’, ‘10’) thereby to assign a significance level to each bit (each bit is either the most significant bit of a particular symbol, or a least significant bit thereof, or an intermediately significant bit thereof). Map the M symbols into M voltage levels and program the device to store the 4 Gb bits using the mapping. An example of a suitable mapping is: ‘00’->−1 volt, ‘01’->1 volt, ‘11’->3 volt, ‘10’->5 volt as shown in the table of
Step 630: Generate a symbol-physical address table listing, for each of the 2^N symbols (assuming an N-bit-per-cell device), all of the physical addresses within the reference block at which that symbol was found, as shown in
Step 635: Plot the device's symbol histograms. Typically, in an N bit-per-cell device there are 2^N−1 such histograms corresponding to the 2^N−1 Gaussian probability density functions of the 2^N−1 non-zero symbols respectively. For example, in an N=3 bit-per-cell device the histogram includes 2^N−1=7 Gaussian probability density functions. These histograms are described, for example, in:
To do this, for each symbol (column) read the threshold voltage from each cell address in the corresponding column of the above table and store, e.g. as in the table of
Step 640: For each of the 2^N−1 Gaussian probability density functions (for each of the histograms) compute the mean and variance, for which the following notation (taking the example of N=3) is now used: (m1,Var1), (m2,Var2), . . . (m7,Var7) for the means and variances of the 7 histograms respectively. Compute the average, Var, of the 7 variances.
Step 650: Compute distances d1, . . . d6 between each two adjacent histogram means: d1=m2−m1, d2=m3−m2, . . . , d6=m7−m6. Compute the average d of the 6 distances.
Step 660: Compute the error probability for the page (termed herein Page 1) which stores the MSB. The decision is between half of the upper half PDF group to lower half PDF group. From all the couples, numbers #3 to #4 generate most of the errors; the rest may be neglected. For example, assuming 3 bits per cell, the decision is between symbols #3 and #4 so the error probability for page 1 is (see
where erfc is the conventional complementary error function:
For real input, ERFC may be computed using rational functions, as described in “Rational Chebyshev approximations for the error function,” W. J. Cody, Math. Comp., 1969, pp. 631-638.
Step 670: Compute the error probability for the page (termed herein Page 2) which stores the second most significant bit. The decisions are between quarters of the PDF group e.g. as per
Step 680: Compute the error probability for the page (termed herein Page N) which stores the least significant bit. The decisions are between sub groups of PDF each with 0.125 of the PDF group e.g. as per
It is appreciated that the above per-page error probability computation can be modified suitably if N is not 3 or if gray coding is not used. For example, referring to
since the decision is between half of the upper half PDF group to the lower half PDF group. Similarly, LSB-page error probability computation step 670 is replaced by the following:
Another example is that if each cell stores 2 bits rather than 3 bits, then, assuming gray coding is used, step 650 (computation of the probability of error for the first page which stores the MSB) becomes:
because the decision is between half of the upper half PDF group to lower half PDF group, so for 2 bits per cell the decision is between symbols #1 and #2; step 660 is omitted, and step 670 (computation of the probability of error for the last page, which stores the LSB) becomes:
because the decisions are between quarters of the PDF group. With reference to
Referring again to
The graph of
p=BER (bit error rate)
n=block length (in bits, block=data plus redundancy bits)
L=number of error bits corrected by the BCH code in the block
P_block=Target block error rate
Ferr(n,L,p)=Block error rate as given by the following equation:
The minimum number of redundancy bits which may be employed given the above parameters is the solution of the following optimization problem:
An example of the operation of the method of
The steps to convert the graph into the table of
If three logical pages (LP1, LP2 and LP3), each 1024 bits long, are sent from the host to the flash for writing, then disregarding redundancy needs, 1024×3 bits may be required for storage. 1024 flash memory cells may be used, each representing one bit from each of the logical pages. The flash memory may decide to store LP1 in the MSB of the 1024 cells, LP2 in the next level and LP3 in the LSB. Appropriate BER and encoder code is then selected for each logical page.
It is appreciated that each logical page may be assigned only one significance level, as in certain embodiments shown and described herein in which, say, LP1 is assigned to MSB, LP2 to ISB and LP3 to LSB. However, this is not intended to be limiting. For example, in the alternative, the following method may be employed for each 3 logical pages received by a flash memory device:
a. Assign the first half of the bits of LP1 to significance level MSB.
b. Assign the first half of the bits of LP2 to significance level ISB.
c. Assign the first half of the bits of LP3 to significance level LSB.
d. Assign the second half of the bits of LP1 to significance level LSB.
e. Assign the second half of the bits of LP2 to significance level ISB.
f. Assign the second half of the bits of LP3 to significance level MSB.
Typically, the redundancy rate is a property of different logical pages whereas different physical pages are all manufactured with the same ratio of data:redundancy bits. However, this difference between logical pages is typically not an inherent characteristic of a logical page; when the host delivers a logical page to the flash device for writing, it need not know anything about the redundancy rate that is to characterize this particular logical page within the flash device. Only once the logical page is received in the flash device, the flash controller may decide to write it to a specific significance level, thereby to determine a redundancy rate of this logical page.
It is appreciated that different levels of significance may be used within one page). A mixture of logical pages may be used to achieve a desired BER (bit error rate), e.g. as shown in
Certain operations are described herein as occurring in the microcontroller internal to a flash memory device. Such description is intended to include operations which may be performed by hardware which may be associated with the microcontroller such as peripheral hardware on a chip on which the microcontroller may reside. It is also appreciated that some or all of these operations, in any embodiment, may alternatively be performed by the external, host-flash memory device interface controller including operations which may be performed by hardware which may be associated with the interface controller such as peripheral hardware on a chip on which the interface controller may reside. Finally it is appreciated that the internal and external controllers may each physically reside on a single hardware device, or alternatively on several operatively associated hardware devices.
Any data described as being stored at a specific location in memory may alternatively be stored elsewhere, in conjunction with an indication of the location in memory with which the data is associated. For example, instead of storing page- or erase-sector-specific information within a specific page or erase sector, the same may be stored within the flash memory device's internal microcontroller or within a microcontroller interfacing between the flash memory device and the host, and an indication may be stored of the specific page or erase sector associated with the cells.
It is appreciated that the teachings of the present invention can, for example, be implemented by suitably modifying, or interfacing externally with, flash controlling apparatus. The flash controlling apparatus controls a flash memory array and may comprise either a controller external to the flash array or a microcontroller on-board the flash array or otherwise incorporated therewithin. Examples of flash memory arrays include Samsung's K9XXG08UXM series, Hynix' HY27UK08BGFM Series, Micron's MT29F64G08TAAWP or other arrays such as but not limited to NOR or phase change memory. Examples of controllers which are external to the flash array they control include STMicroelectrocincs's ST7265x microcontroller family, STMicroelectrocincs's ST72681 microcontroller, and SMSC's USB97C242, Traspan Technologies' TS-4811, Chipsbank CBM2090/CBM1190. Example of commercial IP software for Flash file systems are: Denali's Spectra™ NAND Flash File System, Aarsan's NAND Flash Controller IP Core and Arasan's NAND Flash File System. It is appreciated that the flash controller apparatus need not be NAND-type and can alternatively, for example, be NOR-type or phase change memory-type.
Flash controlling apparatus, whether external or internal to the controlled flash array, typically includes the following components: a Memory Management/File system, a NAND interface (or other flash memory array interface), a Host Interface (USB, SD or other), error correction circuitry (ECC) typically comprising an Encoder and matching decoder, and a control system managing all of the above.
The present invention may for example interface with or modify, as per any of the embodiments described herein, one, some or all of the above components and particularly the ECC and memory management components. The ECC component, or a functional unit interacting therewith, is, according to certain embodiments of the present invention, operative to obtain an address which indicates which layer is being coded.
Included in the scope of the present invention, inter alia, are electromagnetic signals carrying computer-readable instructions for performing any or all of the steps of any of the methods shown and described herein, in any suitable order; machine-readable instructions for performing any or all of the steps of any of the methods shown and described herein, in any suitable order; program storage devices readable by machine, tangibly embodying a program of instructions executable by the machine to perform any or all of the steps of any of the methods shown and described herein, in any suitable order; a computer program product comprising a computer useable medium having computer readable program code having embodied therein, and/or including computer readable program code for performing, any or all of the steps of any of the methods shown and described herein, in any suitable order; any technical effects brought about by any or all of the steps of any of the methods shown and described herein, when performed in any suitable order; any suitable apparatus or device or combination of such, programmed to perform, alone or in combination, any or all of the steps of any of the methods shown and described herein, in any suitable order; information storage devices or physical records, such as disks or hard drives, causing a computer or other device to be configured so as to carry out any or all of the steps of any of the methods shown and described herein, in any suitable order; a program pre-stored e.g. in memory or on an information network such as the Internet, before or after being downloaded, which embodies any or all of the steps of any of the methods shown and described herein, in any suitable order, and the method of uploading or downloading such, and a system including server/s and/or client/s for using such; and hardware which performs any or all of the steps of any of the methods shown and described herein, in any suitable order, either alone or in conjunction with software.
It is appreciated that software components of the present invention, if any, including programs and data may, if desired, be implemented in ROM (read only memory) form including CD-ROMs, EPROMs and EEPROMs, or may be stored in any other suitable computer-readable medium such as but not limited to disks of various kinds, cards of various kinds and RAMs. Components described herein as software may, alternatively, be implemented wholly or partly in hardware, if desired, using conventional techniques.
Features of the present invention which are described in the context of separate embodiments may also be provided in combination in a single embodiment. Conversely, features of the invention, including method steps, which are described for brevity in the context of a single embodiment or in a certain order may be provided separately or in any suitable subcombination or in a different order. “e.g.” is used herein in the sense of a specific example which is not intended to be limiting.
This application is a National Phase Application of PCT International Application No. PCT/IL2008/001243, entitled “APPARATUS FOR CODING AT A PLURALITY OF RATES IN MULTI-LEVEL FLASH MEMORY SYSTEMS, AND METHODS USEFUL IN CONJUNCTION THEREWITH”, International Filing Date Sep. 17, 2008, published on Jun. 25, 2009 as International Publication No. WO 2009/078006, which in turn claims priority from U.S. Provisional Application No. 61/006,078, filed Dec. 18, 2007 and entitled “Systems and Methods for Multi Rate Coding in Multi Level Flash Devices” and U.S. Provisional Application No. 61/064,923, filed Apr. 3, 2008 and entitled “Apparatus For Coding At A Plurality Of Rates In Multi-Level Flash Memory Systems, And Methods Useful In Conjunction Therewith”, all of which are incorporated herein by reference in their entirety. Priority is claimed from the following co-pending applications: U.S. Provisional Application No. 61/006,078, filed Dec. 18, 2007 and entitled “Systems and Methods for Multi Rate Coding in Multi Level Flash Devices” and U.S. Provisional Application No. 61/064,923, filed Apr. 30, 2008 and entitled “Apparatus For Coding At A Plurality Of Rates In Multi-Level Flash Memory Systems, And Methods Useful In Conjunction Therewith”. Other co-pending applications include: U.S. Provisional Application No. 60/960,207, filed Sep. 20, 2007 and entitled “Systems and Methods for Coupling Detection in Flash Memory”, U.S. Provisional Application No. 61/071,467, filed Apr. 30, 2008 and entitled “Improved Systems and Methods for Determining Logical Values of Coupled Flash Memory Cells”, U.S. Provisional Application No. 60/960,943, filed Oct. 22, 2007 and entitled “Systems and methods to reduce errors in Solid State Disks and Large Flash Devices” and U.S. Provisional Application No. 61/071,469, filed Apr. 30, 2008 and entitled “Systems and Methods for Averaging Error Rates in Non-Volatile Devices and Storage Systems”, U.S. Provisional Application No. 60/996,027, filed Oct. 25, 2007 and entitled “Systems and Methods for Coping with Variable Bit Error Rates in Flash Devices”, U.S. Provisional Application No. 61/071,466, filed Apr. 30, 2008 and entitled “Systems and Methods for Multiple Coding Rates in Flash Devices”, U.S. Provisional Application No. 61/006,120, filed Dec. 19, 2007 and entitled “Systems and Methods for Coping with Multi Stage Decoding in Flash Devices”, U.S. Provisional Application No. 61/071,464, filed Apr. 30, 2008 and entitled “A Decoder Operative to Effect A Plurality of Decoding Stages Upon Flash Memory Data and Methods Useful in Conjunction Therewith”, U.S. Provisional Application No. 61/006,385, filed Jan. 10, 2008 and entitled “A System for Error Correction Encoder and Decoder Using the Lee Metric and Adapted to Work on Multi-Level Physical Media”, U.S. Provisional Application No. 61/064,995, filed Apr. 8, 2008 and entitled “Systems and Methods for Error Correction and Decoding on Multi-Level Physical Media”, U.S. Provisional Application No. 60/996,948, filed Dec. 12, 2007 and entitled “Low Power BCH/RS Decoding: a Low Power Chien-Search Implementation”, U.S. Provisional Application No. 61/071,487, filed May 1, 2008 and entitled “Chien-Search System Employing a Clock-Gating Scheme to Save Power for Error Correction Decoder and other Applications”, U.S. Provisional Application No. 61/071,468, filed Apr. 30, 2008 and entitled “A Low Power Chien-Search Based BCH/RS Recoding System for Flash Memory, Mobile Communications Devices and Other Applications”, U.S. Provisional Application No. 60/996,782, filed Dec. 5, 2007 and entitled “Systems and Methods for Using a Training Sequence in Flash Memory”, U.S. Provisional Application No. 61/064,853, filed Mar. 31, 2008 and entitled “Flash Memory Device with Physical Cell Value Deterioration Accommodation and Methods Useful in Conjunction Therewith”, U.S. Provisional Application No. 61/129,608, filed Jul. 8, 2008 and entitled “A Method for Acquiring and Tracking Detection Thresholds in Flash Devices”, U.S. Provisional Application No. 61/006,806, filed Jan. 31, 2008 and entitled “Systems and Methods for using a Erasure Coding in Flash memory”, U.S. Provisional Application No. 61/071,486, filed May 1, 2008 and entitled “Systems and Methods for Handling Immediate Data Errors in Flash Memory”, U.S. Provisional Application No. 61/006,805, filed Jan. 31, 2008 and entitled “A Method for Extending the Life of Flash Devices”, U.S. Provisional Application No. 61/071,465, filed Apr. 30, 2008 and entitled “Systems and Methods for Temporarily Retiring Memory Portions”, U.S. Provisional Application No. 61/064,760, filed Mar. 25, 2008 and entitled “Hardware efficient implementation of rounding in fixed-point arithmetic”, U.S. Provisional Application No. 61/071,404, filed Apr. 28, 2008 and entitled “Apparatus and Methods for Hardware-Efficient Unbiased Rounding”, U.S. Provisional Application No. 61/136,234, filed Aug. 20, 2008 and entitled “A Method Of Reprogramming A Non-Volatile Memory Device Without Performing An Erase Operation”, U.S. Provisional Application No. 61/129,414, filed Jun. 25, 2008 and entitled “Improved Programming Speed in Flash Devices Using Adaptive Programming”, and several other co-pending patent applications being filed concurrently (same day).
Filing Document | Filing Date | Country | Kind | 371c Date |
---|---|---|---|---|
PCT/IL2008/001243 | 9/17/2008 | WO | 00 | 10/19/2009 |
Publishing Document | Publishing Date | Country | Kind |
---|---|---|---|
WO2009/078006 | 6/25/2009 | WO | A |
Number | Name | Date | Kind |
---|---|---|---|
4463375 | Macovski | Jul 1984 | A |
4584686 | Fritze | Apr 1986 | A |
4589084 | Fling et al. | May 1986 | A |
4866716 | Weng | Sep 1989 | A |
5077737 | Leger et al. | Dec 1991 | A |
5297153 | Baggen et al. | Mar 1994 | A |
5657332 | Auclair et al. | Aug 1997 | A |
5729490 | Calligaro et al. | Mar 1998 | A |
5793774 | Usui et al. | Aug 1998 | A |
5926409 | Engh et al. | Jul 1999 | A |
5956268 | Lee | Sep 1999 | A |
5982659 | Irrinki et al. | Nov 1999 | A |
6038634 | Ji et al. | Mar 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 |
6278633 | Wong et al. | Aug 2001 | B1 |
6279133 | Vafai et al. | Aug 2001 | B1 |
6301151 | Engh et al. | Oct 2001 | B1 |
6370061 | Yachareni et al. | Apr 2002 | B1 |
6374383 | Weng | Apr 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 |
6637002 | Weng et al. | Oct 2003 | B1 |
6639865 | Kwon | Oct 2003 | B2 |
6674665 | Mann et al. | Jan 2004 | B1 |
6704902 | Shinbashi et al. | Mar 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 |
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 |
7149950 | Spencer et al. | Dec 2006 | B2 |
7177977 | Chen et al. | Feb 2007 | B2 |
7191379 | Adelmann et al. | Mar 2007 | B2 |
7196946 | Chen et al. | Mar 2007 | B2 |
7203874 | Roohparvar | Apr 2007 | B2 |
7290203 | Emma et al. | Oct 2007 | B2 |
7292365 | Knox | Nov 2007 | B2 |
7301928 | Nakabayashi et al. | Nov 2007 | B2 |
7441067 | Gorobets et al. | Oct 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 |
7697326 | Sommer et al. | Apr 2010 | B2 |
7706182 | Shalvi et al. | Apr 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 |
7961797 | Yang et al. | Jun 2011 | B1 |
8020060 | Murin | Sep 2011 | B2 |
8020073 | Emma et al. | Sep 2011 | B2 |
8122328 | Liu et al. | Feb 2012 | B2 |
20020063774 | Hillis et al. | May 2002 | A1 |
20020085419 | Kwon et al. | Jul 2002 | A1 |
20020154769 | Petersen et al. | Oct 2002 | A1 |
20030065876 | Lasser | Apr 2003 | A1 |
20030101404 | Zhao et al. | May 2003 | A1 |
20030105620 | Bowen | Jun 2003 | A1 |
20030192007 | Miller et al. | Oct 2003 | A1 |
20040015771 | Lasser et al. | Jan 2004 | A1 |
20040030971 | Tanaka et al. | Feb 2004 | A1 |
20040153722 | Lee | Aug 2004 | A1 |
20040153817 | Norman et al. | Aug 2004 | A1 |
20040181735 | Xin | Sep 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 |
20060059406 | Micheloni et al. | Mar 2006 | A1 |
20060059409 | Lee | Mar 2006 | A1 |
20060064537 | Oshima et al. | Mar 2006 | A1 |
20060101193 | Murin | May 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 |
20060294312 | Walmsley | Dec 2006 | A1 |
20070025157 | Wan et al. | Feb 2007 | A1 |
20070063180 | Asano et al. | Mar 2007 | A1 |
20070086239 | Litsyn et al. | Apr 2007 | A1 |
20070097744 | Li et al. | 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 |
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 |
20080010581 | Alrod et al. | Jan 2008 | A1 |
20080028014 | Hilt et al. | Jan 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 |
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 |
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 |
20080219050 | Shalvi et al. | Sep 2008 | A1 |
20080225599 | Chae | Sep 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 |
20090043951 | Shalvi et al. | 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 et al. | May 2009 | A1 |
20090144600 | Perlmutter et al. | 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 |
20100005270 | Jiang | Jan 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 |
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 |
20100251066 | Radke | Sep 2010 | A1 |
20100253555 | Weingarten et al. | Oct 2010 | A1 |
20100257309 | Barsky et al. | Oct 2010 | A1 |
20100293321 | Weingarten | Nov 2010 | A1 |
20110051521 | Levy et al. | Mar 2011 | A1 |
20110055461 | Steiner et al. | Mar 2011 | A1 |
20110096612 | Steiner et al. | Apr 2011 | A1 |
20110119562 | Steiner et al. | May 2011 | A1 |
20110153919 | Sabbag | Jun 2011 | A1 |
20110161775 | Weingarten | Jun 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 |
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 |
Number | Date | Country | |
---|---|---|---|
20100131806 A1 | May 2010 | US |
Number | Date | Country | |
---|---|---|---|
61006078 | Dec 2007 | US | |
61064923 | Apr 2008 | US |