Dave's PCF WIP: Paragraphs

Edit Paragraph

Application

Application Number

Matter Number

Paragraph Number

Content

In another embodiment, the write data pipeline 106 also includes an encryption module 314 that encrypts a data or metadata segment received from the input buffer 306, either directly or indirectly, prior sending the data segment to the packetizer 302, the data segment encrypted using an encryption key received in conjunction with the data segment. The encryption module 314 differs from the media encryption module 318 in that the encryption keys used by the encryption module 314 to encrypt data may not be common to all data stored within the solid-state storage device 102 but may vary on an object basis and received in conjunction with receiving data segments as described below. For example, an encryption key for a data segment to be encrypted by the encryption module 314 may be received with the data segment or may be received as part of a command to write an object to which the data segment belongs. The solid-sate storage device 102 may use and store a non-secret cryptographic nonce in each object packet that is used in conjunction with the encryption key. A different nonce may be stored with every packet. Data segments may be split between multiple packets with unique nonces for the purpose of improving protection by the encryption algorithm. In one embodiment, the nonce used by the media encryption module 318 is the same as that used by the encryption module 314.

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">In another embodiment, the write data pipeline </w:t></w:r><w:r><w:t>106</w:t></w:r><w:r><w:t xml:space="preserve"> also includes an encryption module </w:t></w:r><w:r><w:t>314</w:t></w:r><w:r><w:t xml:space="preserve"> that encrypts a data or metadata segment received from the input buffer </w:t></w:r><w:r><w:t>306</w:t></w:r><w:r><w:t xml:space="preserve">, either directly or indirectly, prior sending the data segment to the packetizer </w:t></w:r><w:r><w:t>302</w:t></w:r><w:r><w:t xml:space="preserve">, the data segment encrypted using an encryption key received in conjunction with the data segment. The encryption module </w:t></w:r><w:r><w:t>314</w:t></w:r><w:r><w:t xml:space="preserve"> differs from the media encryption module </w:t></w:r><w:r><w:t>318</w:t></w:r><w:r><w:t xml:space="preserve"> in that the encryption keys used by the encryption module </w:t></w:r><w:r><w:t>314</w:t></w:r><w:r><w:t xml:space="preserve"> to encrypt data may not be common to all data stored within the solid-state storage device </w:t></w:r><w:r><w:t>102</w:t></w:r><w:r><w:t xml:space="preserve"> but may vary on an object basis and received in conjunction with receiving data segments as described below. For example, an encryption key for a data segment to be encrypted by the encryption module </w:t></w:r><w:r><w:t>314</w:t></w:r><w:r><w:t xml:space="preserve"> may be received with the data segment or may be received as part of a command to write an object to which the data segment belongs. The solid-sate storage device </w:t></w:r><w:r><w:t>102</w:t></w:r><w:r><w:t xml:space="preserve"> may use and store a non-secret cryptographic nonce in each object packet that is used in conjunction with the encryption key. A different nonce may be stored with every packet. Data segments may be split between multiple packets with unique nonces for the purpose of improving protection by the encryption algorithm. In one embodiment, the nonce used by the media encryption module </w:t></w:r><w:r><w:t>318</w:t></w:r><w:r><w:t xml:space="preserve"> is the same as that used by the encryption module </w:t></w:r><w:r><w:t>314</w:t></w:r><w:r><w:t>.</w:t></w:r></w:p>