IP Library Granted Patent US 9,813,241
Granted Patent B2
US 9,813,241 · App. 15/439,375 · Granted Nov 7, 2017

Encrypted file storage

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 9,813,241
App. No.
15/439,375
Granted
Nov 7, 2017
Kind
B2
Abstract

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.

Claims (61)

1. A method of storing files that are associated with a user account in at least one cloud data storage provider, comprising:

receiving, by an index server, a request to store a first file on behalf of a user associated with access credentials of the user account, the request being received from a client device executing a file management application that communicates with the index server;

identifying, by the index server, a first storage location of the first file associated with a cloud data storage provider that is different from the index server; and

providing, by the index server, the first storage location to the file management application, the first storage location specifying where to send an encrypted version of the first file, the encryption being based on a first key associated with the first storage location of the first file, the first key being different than the access credentials for the cloud data storage provider.

2. The method of claim 1 , further comprising:

receiving, at the index server, a request from the client device to access the file;

determining the client device is authorized to access the file; and

providing the first storage location to the client device for retrieving the encrypted file for decryption by the file management application using the first key.

3. The method of claim 1 , further comprising:

receiving the first key from the client device;

receiving a request from the client device to access the file; and

sending, to the client device, a version of the first key for decrypting the encrypted first file.

4. The method of claim 1 , further comprising:

sending a management component to the client device for installation, wherein the management component causes the first key to be deleted from the client device after the encrypting.

5. The method of claim 1 , further comprising:

receiving, by the index server, a request to store a second file;

identifying, by the index server, a second storage location unassociated with the cloud data storage provider; and

providing the second storage location to the file management application, wherein the file management application encrypts the second file based on a second key associated with the second storage location and sends the encrypted second file to second storage location using access credentials associated with the second storage location.

6. The method of claim 5 , wherein the second storage location is at the index server.

7. The method of claim 1 , wherein the wherein the file management application requests the first key for decrypting the encrypted file.

8. A system of storing files that are associated with a user account in at least one cloud data storage provider, comprising:

a non-transitory, computer-readable medium containing instructions; and

a processor device for an index server that executes the instructions to perform stages comprising:

receiving, by the index server, a request to store a first file on behalf of a user associated with access credentials of the user account, the request being received from a client device executing a file management application that communicates with the index server;

identifying a first storage location of the first file associated with a cloud data storage provider that is different from the index server; and

providing, by the index server, the first storage location to the file management application, the first storage location specifying where to send an encrypted version of the first file, the encryption being based on a first key associated with the first storage location of the first file, the first key being different than the access credentials for the cloud data storage provider.

9. The system of claim 8 , the stages further comprising:

receiving, at the index server, a request from the client device to access the file;

determining the client device is authorized to access the file; and

providing the first storage location to the client device for retrieving the encrypted file for decryption by the file management application using the first key.

10. The system of claim 8 , the stages further comprising:

receiving the first key from the client device;

receiving a request from the client device to access the file; and

sending, to the client device, a version of the first key for decrypting the encrypted first file.

11. The system of claim 8 , the stages further comprising:

sending a management component to the client device for installation, wherein the management component causes the first key to be deleted from the client device after the encrypting.

12. The system of claim 8 , the stages further comprising:

receiving, by the index server, a request to store a second file;

identifying, by the index server, a second storage location unassociated with the cloud data storage provider; and

providing the second storage location to the file management application, wherein the file management application encrypts the second file based on a second key associated with the second storage location and sends the encrypted second file to second storage location using access credentials associated with the second storage location.

13. The system of claim 12 , wherein the second storage location is at the index server.

14. The system of claim 8 , wherein the wherein the file management application requests the first key for decrypting the encrypted file.

15. A non-transitory, computer-readable medium containing instructions for storing files that are associated with a user account in at least one cloud data storage provider, the instructions being executed by a processor device to perform stages comprising:

receiving, by the index server, a request to store a first file on behalf of a user associated with access credentials of the user account, the request being received from a client device executing a file management application that communicates with the index server;

identifying a first storage location of the first file associated with a cloud data storage provider that is different from the index server; and

providing, by the index server, the first storage location to the file management application, the first storage location specifying where to send an encrypted version of the first file, the encryption being based on a first key associated with the first storage location of the first file, the first key being different than the access credentials for the cloud data storage provider.

16. The non-transitory, computer-readable medium of claim 15 , the stages further comprising:

receiving, at the index server, a request from the client device to access the file;

determining the client device is authorized to access the file; and

providing the first storage location to the client device for retrieving the encrypted file for decryption by the file management application using the first key.

17. The non-transitory, computer-readable medium of claim 15 , the stages further comprising:

receiving the first key from the client device;

receiving a request from the client device to access the file; and

sending, to the client device, a version of the first key for decrypting the encrypted first file.

18. The non-transitory, computer-readable medium of claim 15 , the stages further comprising:

sending a management component to the client device for installation, wherein the management component causes the first key to be deleted from the client device after the encrypting.

19. The non-transitory, computer-readable medium of claim 15 , the stages further comprising:

receiving, by the index server, a request to store a second file;

identifying, by the index server, a second storage location unassociated with the cloud data storage provider; and

providing the second storage location to the file management application, wherein the file management application encrypts the second file based on a second key associated with the second storage location and sends the encrypted second file to second storage location using access credentials associated with the second storage location.

20. The non-transitory, computer-readable medium of claim 19 , wherein the second storage location is at the index server.

Assignments (5)
PATENT ASSIGNMENT Recorded Aug 5, 2024
From: VMWARE LLC
To: OMNISSA, LLC
Reel/Frame 068327/0365 →
SECURITY INTEREST Recorded Jul 3, 2024
From: OMNISSA, LLC
To: UBS AG, STAMFORD BRANCH
Reel/Frame 068118/0004 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 30, 2024
From: AIRWATCH LLC
To: VMWARE, INC.
Reel/Frame 067879/0157 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 30, 2024
From: STUNTEBECK, ERICH; PANCHAPAKESAN, RAMANI; LAXMINARAYAN, AKSHAY; ASHISH, KUMAR
To: AIRWATCH LLC
Reel/Frame 068063/0493 →
CHANGE OF NAME Recorded Apr 15, 2024
From: VMWARE, INC.
To: VMWARE LLC
Reel/Frame 067102/0314 →