Encrypted file storage

US10574456B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-10574456-B2
Application numberUS-201816182554-A
CountryUS
Kind codeB2
Filing dateNov 6, 2018
Priority dateDec 30, 2014
Publication dateFeb 25, 2020
Grant dateFeb 25, 2020

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

Various systems facilitate encrypted file storage. A client device may generate an encrypted version of a file. The client device may obtain at least one reference to at least one storage location for the encrypted version of the file. The client device may cause the encrypted version of the file to be store at the at least one storage location using the at least one reference to the at least one storage location.

First claim

Opening claim text (preview).

Therefore, the following is claimed: 1. A method of storing files comprising: sending, to an index server from a client device, a request to store a first file on behalf of a user of the client device, the user associated with access credentials of a user account of a cloud data storage provider; receiving, by the client device from the index server, a first storage location and a second storage location associated with the user account for the first file at the cloud data storage provider, the first and second storage locations being different than the index server; partitioning, by a file management application at the client device, the first file into first and second portions; encrypting the first and second portions based on a first and second encryption keys; sending an encrypted version of the first portion to the first storage location at the cloud data storage provider, wherein the first encryption key is stored by the index server corresponding to the first storage location; and sending an encrypted version of the second portion to the second storage location at the cloud data storage provider, wherein the second encryption key is stored by the index server corresponding to the second storage location. 2. The method of claim 1 , further comprising: sending, to the index server, a request from the client device to access the first file; receiving, from the index server, the first and second locations for retrieving the first and second encrypted portions, respectively; and obtaining at least one of the first and second encrypted portions by transmitting access credentials to the cloud storage provider. 3. The method of claim 2 , further comprising: receiving multiple keys, including a first key, at the client device in response to the request to access the first file; and decrypting the first and second encrypted portions using the multiple keys. 4. The method of claim 1 , further comprising: transmitting a first key to the index server from the client device; requesting, by the client device, access to the file; and receiving a version of the first key for decrypting the first encrypted portion. 5. The method of claim 1 , further comprising: deleting, by the file management application, a first key from the client device after the encrypting the first portion using the first key. 6. The method of claim 1 , further comprising: sending, from the client device to the index server, a request to store a second file; receiving a third storage location unassociated with the cloud data storage provider, wherein the second storage location is at the index server; encrypting the second file based on a key associated with the third storage location; and sending, from the client device, the encrypted second file to the third storage location using access credentials associated with the third storage location. 7. The method of claim 1 , further comprising: requesting access to the first file; receiving, from the index server, the first and second storage locations; receiving, from the index server, a first key for decrypting the first portion and a second key for decrypting the second portion; and combining the first and second portions, by the file management application, to provide access to the first file. 8. A system for storing files, comprising: a non-transitory, computer-readable medium containing instructions; and a hardware processor that executes the instructions for a file management service at a client device to perform stages comprising: sending, to an index server from the client device, a request to store a first file on behalf of a user of the client device, the user associated with access credentials of a user account of a cloud data storage provider; receiving, by the client device from the index server, a first storage location and a second storage location associated with the user account for the first file at the cloud data storage provider, the first and second locations being different than the index server; partitioning, by the file management service at the client device, the first file into first and second portions; encrypting the first and second portions based on a first and second encryption keys; sending an encrypted version of the first portion to the first storage location at the cloud data storage provider, wherein the first encryption key is stored by the index server corresponding to the first storage location; and sending an encrypted version of the second portion to the second storage location at the cloud data storage provider, wherein the second encryption key is stored by the index server corresponding to the second storage location. 9. The system of claim 8 , the stages further comprising: sending, to the index server, a request from the client device to access the first file; receiving, from the index server, the first and second locations for retrieving the first and second encrypted portions, respectively; and obtaining at least one of the first and second encrypted portions by transmitting access credentials to the cloud storage provider. 10. The system of claim 9 , the stages further comprising: receiving multiple keys, including a first key, at the client device in response to the request to access the first file; and decrypting the first and second encrypted portions using the multiple keys. 11. The system of claim 8 , the stages further comprising: transmitting a first key to the index server from the client device; requesting, by the client device, access to the file; and receiving a version of the first key for decrypting the first encrypted portion. 12. The system of claim 8 , the stages further comprising: deleting, by the file management service, a first key from the client device after the encrypting the first portion using the first key. 13. The system of claim 8 , the stages further comprising: sending, from the client device to the index server, a request to store a second file; receiving a third storage location unassociated with the cloud data storage provider, wherein the second storage location is at the index server; encrypting the second file based on a key associated with the third storage location; and sending, from the client device, the encrypted second file to the third storage location using access credentials associated with the third storage location. 14. The system of claim 8 , the stages further comprising: requesting access to the first file; receiving, from the index server, the first and second storage locations; receiving, from the index server, a first key for decrypting the first portion and a second key for decrypting the second portion; and combining the first and second portions, by the file management service, to provide access to the first file. 15. A non-transitory, computer-readable medium containing instructions for a file management service of a client device, the instructions being executed by a hardware processor to perform stages comprising: sending, to an index server from a client device, a request to store a first file on behalf of a user of the client device, the user associated with access credentials of a user account of a cloud data storage provider; receiving, by the client device from the index server, a first storage location and a second storage location associated with the user account for the first file at the cloud data storage provider, the first and second storage locations being different than the index server; partitioning, by the file management service of the client device, the first file into first and second portions;

Assignees

Inventors

Classifications

  • Hierarchical storage management [HSM] systems, e.g. file migration or policies thereof (details of archiving G06F16/11) · CPC title

  • Distributed file systems · CPC title

  • using a plurality of keys or algorithms · CPC title

  • to a single file or object, e.g. in a secure envelope, encrypted and accessed using a key, or with access control rules appended to the object itself · CPC title

  • to a system of files or objects, e.g. local or distributed file system or database · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US10574456B2 cover?
Various systems facilitate encrypted file storage. A client device may generate an encrypted version of a file. The client device may obtain at least one reference to at least one storage location for the encrypted version of the file. The client device may cause the encrypted version of the file to be store at the at least one storage location using the at least one reference to the at least o…
Who is the assignee on this patent?
Vmware Inc
What technology area does this patent fall under?
Primary CPC classification H04L9/0894. Mapped technology areas include Electricity.
When was this patent published?
Publication date Tue Feb 25 2020 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 8 related publications on this page (citations in our corpus or others sharing the same primary CPC).