Dave's PCF WIP: Paragraphs

Paragraph #3,079

Edit Paragraph

View List Paragraphs Delete

Application

Matter Number

Paragraph Number

Application Number

Reference Case 1

Reference Case 2

Content

In another embodiment, the read data pipeline 108 includes a decryption module 334 that decrypts a data segment formatted by the depacketizer 324 prior to sending the data segment to the output buffer 330. The data segment decrypted using an encryption key received in conjunction with the read request that initiates retrieval of the requested packet received by the read synchronization buffer 328. The decryption module 334 may decrypt a first packet with an encryption key received in conjunction with the read request for the first packet and then may decrypt a second packet with a different encryption key or may pass the second packet on to the next stage of the read data pipeline 108 without decryption. Typically, the decryption module 334 uses a different encryption key to decrypt a data segment than the media decryption module 332 uses to decrypt requested packets. When the packet was stored with a non-secret cryptographic nonce, the nonce is used in conjunction with an encryption key to decrypt the data packet. The encryption key may be received from a client 114, a computer 112, key manager, or other device that manages the encryption key to be used by the solid-state storage controller 104.

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 read data pipeline </w:t></w:r><w:r><w:t>108</w:t></w:r><w:r><w:t xml:space="preserve"> includes a decryption module </w:t></w:r><w:r><w:t>334</w:t></w:r><w:r><w:t xml:space="preserve"> that decrypts a data segment formatted by the depacketizer </w:t></w:r><w:r><w:t>324</w:t></w:r><w:r><w:t xml:space="preserve"> prior to sending the data segment to the output buffer </w:t></w:r><w:r><w:t>330</w:t></w:r><w:r><w:t xml:space="preserve">. The data segment decrypted using an encryption key received in conjunction with the read request that initiates retrieval of the requested packet received by the read synchronization buffer </w:t></w:r><w:r><w:t>328</w:t></w:r><w:r><w:t xml:space="preserve">. The decryption module </w:t></w:r><w:r><w:t>334</w:t></w:r><w:r><w:t xml:space="preserve"> may decrypt a first packet with an encryption key received in conjunction with the read request for the first packet and then may decrypt a second packet with a different encryption key or may pass the second packet on to the next stage of the read data pipeline </w:t></w:r><w:r><w:t>108</w:t></w:r><w:r><w:t xml:space="preserve"> without decryption. Typically, the decryption module </w:t></w:r><w:r><w:t>334</w:t></w:r><w:r><w:t xml:space="preserve"> uses a different encryption key to decrypt a data segment than the media decryption module </w:t></w:r><w:r><w:t>332</w:t></w:r><w:r><w:t xml:space="preserve"> uses to decrypt requested packets. When the packet was stored with a non-secret cryptographic nonce, the nonce is used in conjunction with an encryption key to decrypt the data packet. The encryption key may be received from a client </w:t></w:r><w:r><w:t>114</w:t></w:r><w:r><w:t xml:space="preserve">, a computer </w:t></w:r><w:r><w:t>112</w:t></w:r><w:r><w:t xml:space="preserve">, key manager, or other device that manages the encryption key to be used by the solid-state storage controller </w:t></w:r><w:r><w:t>104</w:t></w:r><w:r><w:t>.</w:t></w:r></w:p>