Low-latency media sharing

• US 10,019,591 B1
• Filed: 12/23/2014
• Issued: 07/10/2018
• Est. Priority Date: 12/23/2014
• Status: Active Grant

• Current Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Original Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Inventors: Beguin, Julien George
• Primary Examiner(s): Abedin, Shanto M
• Application Number:
  US14/580,267
• Time in Patent Office: 1,295 Days
• Field of Search: 713165, 713168, 713171, 726 4, 726 26- 27, 380277, 709223, 709225, 709231, 709206
• CPC Class Codes: G06F 21/62 Protecting access to data via a platform, e.g. using keys or access control rules
• CPC Class Codes: G06F 21/6245 Protecting personal data, e.g. for financial or medical purposes
• CPC Class Codes: H04L 63/0428 wherein the data content is protected, e.g. by encrypting or encapsulating the payload
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/108 when the policy decisions are valid for a limited amount of time
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 67/288 Distributed intermediate devices, i.e. intermediate devices for interaction with other intermediate devices on the same level
• CPC Class Codes: H04L 67/5681 Pre-fetching or pre-delivering data based on network characteristics
• CPC Class Codes: H04L 67/5682 Policies or rules for updating, deleting or replacing the stored data

Abstract

Devices, systems and methods are disclosed that receive encrypted media files from a remote device during pre-caching. The encrypted media files may be transferred from the remote devices prior to a user issuing a request to share the particular media file. The remote device may maintain cryptographic keys associated with the sent encrypted media files and only share a cryptographic key associated with a media file the user wishes to share. Without the cryptographic keys, the local device cannot access the contents of the pre-shared encrypted media files in a cache. Upon the user sharing the media file and the local device receiving the cryptographic key, the local device may use the cryptographic key to decrypt the encrypted media file and display the media file at a significantly reduced latency than if the media file were sent only upon the sharing request.

Claims

1. A computer-implemented method comprising:

receiving, by a first device at a first time, a first encrypted image from a second device, the second device within communicable range of the first device, the first encrypted image associated with a first identifier, wherein there is relationship data associated with at least one of the first device and the second device, the relationship data representing at least one previous interaction involving the first device and the second device;

receiving, by the first device, a second encrypted image from the second device, the second encrypted image associated with a second identifier;

storing, by the first device, the first encrypted image in a cache;

storing, by the first device, the second encrypted image in the cache;

receiving, by the first device at a second time, a first cryptographic key from the second device, wherein the second time is after the first time and the first cryptographic key is associated with the first identifier;

identifying, based on the first identifier, the first encrypted image in the cache, wherein the first encrypted data is associated with the first cryptographic key;

generating a first image by decrypting the first encrypted image using the first cryptographic key; and

displaying the first image.

2. The computer-implemented method of claim 1, further comprising:

identifying, by the second device at a third time before the first time, the first image on the second device as a candidate for sharing, the first image selected on the second device;

assigning, by the second device, the first identifier to the first image;

encrypting, by the second device, the first image to generate the first encrypted image, the encrypting using the first cryptographic key, the first cryptographic key stored on the second device, the first cryptographic key exclusively used to encrypt the first image and decrypt the first encrypted image;

inserting, by the second device, the first identifier in a header associated with the first encrypted image, the header being supplemental data placed at a beginning of the first encrypted image;

sending, by the second device at a fourth time after the third time and before the first time, the first encrypted image from the second device to the first device;

receiving, by the second device at a fifth time after the fourth time and before the second time, a share request instructing the second device to share the first image with the first device;

identifying, by the second device, the first identifier associated with the first image;

identifying, by the second device, the first cryptographic key using the first identifier;

sending, by the second device, the first cryptographic key from the table computer to the first device; and

sending, by the second device, the first identifier from the table computer to the first device.

3. The computer-implemented method of claim 1, further comprising:

receiving, by the first device at a third time before the second time, a third encrypted image from the second device, the third encrypted image comprising a compressed version of the first encrypted image;

identifying the third encrypted image as associated with the first cryptographic key;

decrypting the third encrypted image using the first cryptographic key; and

displaying a third image in response to decrypting the third encrypted image.

4. The computer-implemented method of claim 1, further comprising:

determining, by the first device, that the second encrypted image is past an expiration time threshold, the expiration time threshold being a determined time period after a timestamp, the timestamp stored in a header of the second encrypted image; and

deleting the second encrypted image from the cache.

5. A computer-implemented method, the method comprising:

receiving, by a first device at a first time, first encrypted data from a second device, the second device in physical proximity to the first device, the first encrypted data associated with a first identifier, wherein there is relationship data associated with at least one of the first device and the second device, the relationship data representing at least one previous interaction involving the first device and the second device;

receiving, by the first device, second encrypted data from the second device, the second encrypted data associated with a second identifier;

storing, by the first device, the first encrypted data in a cache;

storing, by the first device, the second encrypted data in the cache;

receiving, at a second time, a first cryptographic key from the second device, wherein the second time is after the first time and the first cryptographic key is associated with the first identifier;

identifying, based on the first identifier, the first encrypted data in the cache, wherein the first encrypted data is associated with the first cryptographic key;

generating first data by decrypting the first encrypted data using the first cryptographic key; and

displaying the first data.

6. The computer-implemented method of claim 5, further comprising:

identifying, by the second device at a third time, the first data on the second device as a candidate for sharing, the third time before the first time;

generating, by the second device, the first encrypted data based at least in part on the first data;

sending, by the second device at a fourth time, the first encrypted data to the first device, wherein the fourth time is after the third time and before the first time;

after sending the first encrypted data to the first device, receiving, by the second device, a share request instructing the second device to share the first data with the first device; and

sending, by the second device, the first cryptographic key to the first device.

7. The computer-implemented method of claim 5, further comprising:

receiving, by the first device at a third time, third encrypted data from the second device, the third time before the second time, the third encrypted data associated with the first encrypted data;

identifying the third encrypted data as associated with the first cryptographic key;

decrypting the third encrypted data using the first cryptographic key; and

displaying, by the first device, third data in response to decrypting the third encrypted data.

8. The computer-implemented method of claim 5, further comprising:

determining, by the first device, that the second encrypted data is past an expiration time threshold, the expiration time threshold being a determined time period after a timestamp, the timestamp stored in a header of the second encrypted data; and

removing the second encrypted data from the cache.

9. The computer-implemented method of claim 5, further comprising:

receiving a delete signal including the second identifier;

locating the second identifier in a first header in the cache;

determining that the second encrypted data is associated with the first header; and

removing the second encrypted data from the cache.

10. The computer-implemented method of claim 5, further comprising:

determining, by the first device, that the second device has disconnected from the first device;

determining that the second encrypted data is associated with the second device; and

removing the second encrypted data from the cache.

11. The computer-implemented method of claim 5, further comprising:

sending, by the first device, a share request to the second device instructing the second device to share the first data with the first device.

12. The computer-implemented method of claim 5, further comprising:

sending, by a third device, a share request to the second device instructing the second device to share the first data with the first device.

13. The computer-implemented method of claim 5, wherein the identifying further comprises:

receiving the first from the second device;

locating the first identifier in a first header in the cache; and

determining that the first encrypted data is associated with the first header.

14. The computer-implemented method of claim 5, wherein, prior to the first time, there is an established relationship between the first device and the second device, the established relationship including current and previous interactions between the first device and the second device.

15. The computer-implemented method of claim 5, wherein the first cryptographic key is exclusively used to encrypt the first data and decrypt the first encrypted data.

16. The computer-implemented method of claim 5, wherein the at least one previous interaction corresponds to at least one of:

a previous communication between the first device and the second device,

a previous communication between the first device and a user profile associated with the second device, or

a previous communication between the first device and an account associated with the second device.

17. A computing system, comprising:

a first device, the first device including,

at least one processor;

a memory device including instructions operable to be executed by the at least one processor to cause the first device to;

receive, at a first time, first encrypted data from a second device, the second device in physical proximity to the first device, the first encrypted data associated with a first identifier, wherein there is relationship data associated with at least one of the first device and the second device, the relationship data representing at least one previous interaction involving the first device and the second device;

receive second encrypted data from the second device, the second encrypted data associated with a second identifier;

store the first encrypted data in a cache;

store the second encrypted data in the cache;

receive, at a second time, a first cryptographic key from the second device, wherein the second time is after the first time and the first cryptographic key is associated with the first identifier;

identify, based on the first identifier, the first encrypted data in the cache, wherein the first encrypted data is associated with the first cryptographic key;

generate first data by decrypting the first encrypted data using the first cryptographic key; and

display the first data.

18. The system of claim 17, further comprising:

a second device, the second device including,

at least one processor;

a memory device including instructions operable to be executed by the at least one processor to cause the second device to;

identify, at a third time, the first data on the second device as a candidate for sharing, the third time before the first time;

generate the first encrypted data based at least in part on the first data;

send, at a fourth time, the first encrypted data to the first device, wherein the fourth time is after the third time and before the first time;

after sending the first encrypted data to the first device, receive a share request instructing the second device to share the first data with the first device; and

send the first cryptographic key to the first device.

19. The system of claim 17, wherein the instructions further configure the first device to:

receive, at a third time, third encrypted data from the second device, the third time before the second time, the third encrypted data associated with the first encrypted data;

identify the third encrypted data as associated with the first cryptographic key;

decrypt the third encrypted data using the first cryptographic key; and

display third data in response to decrypting the third encrypted data.

20. The system of claim 17, wherein the instructions further configure the first device to:

determine that the second encrypted data is past an expiration time threshold, the expiration time threshold being a determined time period after a timestamp, the timestamp stored in a header of the second encrypted data; and

remove the second encrypted data from the cache.

21. The system of claim 17, wherein the instructions further configure the first device to:

receive a delete signal including the second identifier;

locate the second identifier in a first header in the cache;

determine that the second encrypted data is associated with the first header; and

remove the second encrypted data from the cache.

22. The system of claim 17, wherein the instructions further configure the first device to:

determine that the second device has disconnected from the first device;

determine that the second encrypted data is associated with the second device; and

remove the second encrypted data from the cache.

23. The system of claim 17, wherein the instructions further configure the first device to:

send a share request to the second device instructing the second device to share the first data with the first device.

24. The system of claim 17, further comprising:

a third device, the third device including,

at least one processor;

a memory device including instructions operable to be executed by the at least one processor to cause the third device to;

send a share request to the second device instructing the second device to share the first data with the first device.