Dave's PCF WIP: Paragraphs

Edit Paragraph

Application

Application Number

Matter Number

Paragraph Number

Content

The secondary ECC module 304, in one embodiment, is configured to determine whether at least one ECC chunk encoded with a secondary error correcting code is correctable using the secondary error correcting code. In certain embodiments, the secondary error correcting code may be different from the primary error correcting code described above with regard to the primary ECC module 302. As described above, the primary ECC module 302 and the secondary ECC module 302 may operate on different data (e.g., the primary ECC module 302 may encode and/or decode user data, workload data, client data or the like and the secondary ECC module 304 may encode and/or decode access data), or, in certain embodiments, the primary ECC module 302 and the secondary ECC module 304 may operate on at least a portion of the same data in a nested manner (e.g., the primary ECC module 302 may encode and/or decode each ECC chunk and the secondary ECC module 304 may encode and/or decode a subset of ECC chunks, such as access data, using multiple levels or layers of error correcting codes).

Reference Case 1

Reference Case 2

Notes

Raw Data

<w:p><w:pPr><w:pStyle w:val="TPSBody1"/></w:pPr><w:r><w:t xml:space="preserve">The secondary ECC module </w:t></w:r><w:r><w:t>304</w:t></w:r><w:r><w:t xml:space="preserve">, in one embodiment, is configured to determine whether at least one ECC chunk encoded with a secondary error correcting code is correctable using the secondary error correcting code. In certain embodiments, the secondary error correcting code may be different from the primary error correcting code described above with regard to the primary ECC module </w:t></w:r><w:r><w:t>302</w:t></w:r><w:r><w:t xml:space="preserve">. As described above, the primary ECC module </w:t></w:r><w:r><w:t>302</w:t></w:r><w:r><w:t xml:space="preserve"> and the secondary ECC module </w:t></w:r><w:r><w:t>302</w:t></w:r><w:r><w:t xml:space="preserve"> may operate on different data (e.g., the primary ECC module </w:t></w:r><w:r><w:t>302</w:t></w:r><w:r><w:t xml:space="preserve"> may encode and/or decode user data, workload data, client data or the like and the secondary ECC module </w:t></w:r><w:r><w:t>304</w:t></w:r><w:r><w:t xml:space="preserve"> may encode and/or decode access data), or, in certain embodiments, the primary ECC module </w:t></w:r><w:r><w:t>302</w:t></w:r><w:r><w:t xml:space="preserve"> and the secondary ECC module </w:t></w:r><w:r><w:t>304</w:t></w:r><w:r><w:t xml:space="preserve"> may operate on at least a portion of the same data in a nested manner (e.g., the primary ECC module </w:t></w:r><w:r><w:t>302</w:t></w:r><w:r><w:t xml:space="preserve"> may encode and/or decode each ECC chunk and the secondary ECC module </w:t></w:r><w:r><w:t>304</w:t></w:r><w:r><w:t xml:space="preserve"> may encode and/or decode a subset of ECC chunks, such as access data, using multiple levels or layers of error correcting codes).</w:t></w:r></w:p>