Dave's PCF WIP: Paragraphs

Edit Paragraph

Application

Application Number

Matter Number

Paragraph Number

Content

If erase block 1 of a storage element SSS0.0 216a is damaged, experiencing errors due to wear, etc., or cannot be used for some reason, the remapping module 430 could change the logical-to-physical mapping for the logical address that pointed to erase block 1 of virtual erase block 1. If a spare erase block (call it erase block 221) of storage element SSS 0.0 216a is available and currently not mapped, the remapping module 430 could change the mapping of virtual erase block 1 to point to erase block 221 of storage element SSS 0.0 216a, while continuing to point to erase block 1 of storage element SSS 1.0 216b, erase block 1 of storage element SSS 2.0 (not shown) . . . , and to storage element M.0 216m. The mapping module 424 or remapping module 430 could map erase blocks in a prescribed order (virtual erase block 1 to erase block 1 of the storage elements, virtual erase block 2 to erase block 2 of the storage elements, etc.) or may map erase blocks of the storage elements 216, 218, 220 in another order based on some other criteria.

Reference Case 1

Reference Case 2

Notes

Raw Data

<w:p><w:pPr><w:pStyle w:val="TPSBody100"/></w:pPr><w:r><w:t xml:space="preserve">If erase block 1 of a storage element SSS0.0 </w:t></w:r><w:r><w:t>216</w:t></w:r><w:r><w:t xml:space="preserve">a </w:t></w:r><w:r><w:t xml:space="preserve">is damaged, experiencing errors due to wear, etc., or cannot be used for some reason, the remapping module </w:t></w:r><w:r><w:t>430</w:t></w:r><w:r><w:t xml:space="preserve"> could change the logical-to-physical mapping for the logical address that pointed to erase block 1 of virtual erase block 1. If a spare erase block (call it erase block </w:t></w:r><w:r><w:t>221</w:t></w:r><w:r><w:t xml:space="preserve">) of storage element SSS 0.0 </w:t></w:r><w:r><w:t>216</w:t></w:r><w:r><w:t xml:space="preserve">a </w:t></w:r><w:r><w:t xml:space="preserve">is available and currently not mapped, the remapping module </w:t></w:r><w:r><w:t>430</w:t></w:r><w:r><w:t xml:space="preserve"> could change the mapping of virtual erase block 1 to point to erase block </w:t></w:r><w:r><w:t>221</w:t></w:r><w:r><w:t xml:space="preserve"> of storage element SSS 0.0 </w:t></w:r><w:r><w:t>216</w:t></w:r><w:r><w:t>a</w:t></w:r><w:r><w:t xml:space="preserve">, while continuing to point to erase block 1 of storage element SSS 1.0 </w:t></w:r><w:r><w:t>216</w:t></w:r><w:r><w:t>b</w:t></w:r><w:r><w:t xml:space="preserve">, erase block 1 of storage element SSS 2.0 (not shown) . . . , and to storage element M.0 </w:t></w:r><w:r><w:t>216</w:t></w:r><w:r><w:t>m</w:t></w:r><w:r><w:t xml:space="preserve">. The mapping module </w:t></w:r><w:r><w:t>424</w:t></w:r><w:r><w:t xml:space="preserve"> or remapping module </w:t></w:r><w:r><w:t>430</w:t></w:r><w:r><w:t xml:space="preserve"> could map erase blocks in a prescribed order (virtual erase block 1 to erase block 1 of the storage elements, virtual erase block 2 to erase block 2 of the storage elements, etc.) or may map erase blocks of the storage elements </w:t></w:r><w:r><w:t>216</w:t></w:r><w:r><w:t xml:space="preserve">, </w:t></w:r><w:r><w:t>218</w:t></w:r><w:r><w:t xml:space="preserve">, </w:t></w:r><w:r><w:t>220</w:t></w:r><w:r><w:t xml:space="preserve"> in another order based on some other criteria.</w:t></w:r></w:p>