Peer to peer enterprise file sharing

• US 10,084,790 B2
• Filed: 12/14/2017
• Issued: 09/25/2018
• Est. Priority Date: 12/27/2014
• Status: Active Grant

• Current Assignee: Omnissa, LLC
• Original Assignee: AirWatch LLC (Broadcom, Inc.)
• Inventors: Panchapakesan, Ramani
• Primary Examiner(s): Potratz, Daniel B
• Application Number:
  US15/842,326
• Publication Number:
  US 20180109530A1
• Time in Patent Office: 285 Days
• 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/0823 using certificates cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263
• CPC Class Codes: H04L 63/083 using passwords cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources
• CPC Class Codes: H04L 63/12 Applying verification of the received information cryptographic mechanisms or cryptographic arrangements for data integrity or data verification H04L9/32
• CPC Class Codes: H04L 63/205 involving negotiation or determination of the one or more network security mechanisms to be used, e.g. by negotiation between the client and the server or between peers or by selection according to the capabilities of the entities involved negotiation of communication capabilities H04L69/24
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 67/1008 based on parameters of servers, e.g. available memory or workload monitoring of computer activity G06F11/30
• CPC Class Codes: H04L 67/101 based on network conditions
• CPC Class Codes: H04L 67/1021 based on client or server locations
• CPC Class Codes: H04L 67/104 Peer-to-peer [P2P] networks
• CPC Class Codes: H04L 67/1068 Discovery involving direct consultation or announcement among potential requesting and potential source peers
• CPC Class Codes: H04L 67/141 Setup of application sessions admission control or resource allocation in data switching networks H04L47/70

Abstract

Disclosed are various embodiments for facilitating the distribution of files from a file repository. Files from a file repository can be distributed via peer to peer transmissions where the peer devices can perform authentication functions. The authentication can be performed based upon metadata associated with the files as well as based upon authentication requests submitted to an authentication server.

Claims

1. A non-transitory computer-readable medium embodying a program executable in a client device, the program, when executed by the client device, being configured to cause the client device to at least:

broadcast a request to obtain a plurality of status parameters associated with a second client device accessible through a network to which the client device is connected, the second client device storing a copy of a file in addition to a secondary copy of the file stored in a file repository;

obtain at least one interrogator response to the request to obtain a plurality of status parameters associated with the second client device, the at least one interrogator response comprising at least the plurality of status parameters associated with the second client device, wherein the at least one interrogator response comprises at least one of an operating system associated with the second client device and a manufacturer associated with the second client device; and

select a sender client device based at least in part upon the at least one interrogator response to the request to obtain the plurality of status parameters associated with the second client device, wherein the sender client device is selected based on at least one of whether the operating system associated with the second client device matches an operating system of the client device and whether the manufacturer associated with the second client device matches a manufacturer associated with the client device, respectively.

2. The non-transitory computer-readable medium of claim 1, wherein the program causes the client device to at least:

authenticate the sender client device; and

establish a file transfer session with the sender client device in response to the authentication of the sender client device.

3. The non-transitory computer-readable medium of claim 1, wherein the at least one interrogator response further comprises a battery life parameter associated with the second client device, and wherein the program is further configured to select the sender client device based at least in part upon the battery life parameter.

4. The non-transitory computer-readable medium of claim 1, wherein the at least one interrogator response comprises at least one supported file transfer protocol of the second client device, and wherein the program is configured to select the sender client device based at least in part upon whether the client device supports the at least one supported file transfer protocol.

5. The non-transitory computer-readable medium of claim 1, wherein the sender client device is authenticated based at least in part upon metadata associated with the file, and wherein the program is configured to obtain the metadata associated with the file from at least one of an authentication server or the file repository.

6. The non-transitory computer-readable medium of claim 5, wherein the sender client device is authenticated based at least part upon a one-time password generated from a file hash associated with the file, and wherein the client device authenticates the one-time password by generating the file hash from the metadata associated with the file.

7. The non-transitory computer-readable medium of claim 5, wherein the at least one sender client device is authenticated based at least in part upon an authentication token provided to the client device, and wherein the program is configured to generate a request to authenticate the authentication token that is transmitted to the authentication server.

8. A method, comprising:

broadcasting a request to obtain a plurality of status parameters associated with a second client device accessible through a network to which the client device is connected, the second client device storing a copy of a file in addition to a secondary copy of the file stored in a file repository;

obtaining at least one interrogator response to the request to obtain a plurality of status parameters associated with the second client device, the at least one interrogator response comprising at least the plurality of status parameters associated with the second client device, wherein the at least one interrogator response comprises at least one of an operating system associated with the second client device and a manufacturer associated with the second client device; and

selecting a sender client device based at least in part upon the at least one interrogator response to the request to obtain the plurality of status parameters associated with the second client device, wherein the sender client device is selected based on at least one of whether the operating system associated with the second client device matches an operating system of the client device and whether the manufacturer associated with the second client device matches a manufacturer associated with the client device, respectively.

9. The method of claim 8, further comprising:

authenticating the sender client device; and

establishing a file transfer session with the sender client device in response to the authentication of the sender client device.

10. The method of claim 8, wherein the at least one interrogator response further comprises a battery life parameter associated with the second client device, and wherein the method further comprises selecting the sender client device based at least in part upon the battery life parameter.

11. The method of claim 8, wherein the at least one interrogator response comprises at least one supported file transfer protocol of the second client device, and wherein the method further comprises selecting the sender client device based at least in part upon whether the client device supports the at least one supported file transfer protocol.

12. The method of claim 8, further comprising authenticating the sender client device based at least in part upon metadata associated with the file and obtaining the metadata associated with the file from at least one of an authentication server or the file repository.

13. The method of claim 12, wherein the sender client device is authenticated based at least part upon a one-time password generated from a file hash associated with the file, and wherein the client device authenticates the one-time password by generating the file hash from the metadata associated with the file.

14. The method of claim 12, wherein the sender client device is authenticated based at least in part upon an authentication token provided to the client device, and wherein the method further comprises generating a request to authenticate the authentication token that is transmitted to the authentication server.

15. A system for peer to peer file sharing, comprising:

a memory storage including a non-transitory, computer-readable medium comprising instructions; and

a client device including a processor that executes the instructions to carry out stages comprising;

broadcasting a request to obtain a plurality of status parameters associated with a second client device accessible through a network to which the client device is connected, the second client device storing a copy of a file in addition to a secondary copy of the file stored in a file repository;

obtaining at least one interrogator response to the request to obtain a plurality of status parameters associated with the second client device, the at least one interrogator response comprising at least the plurality of status parameters associated with the second client device, wherein the at least one interrogator response comprises at least one of an operating system associated with the second client device and a manufacturer associated with the second client device; and

selecting a sender client device based at least in part upon the at least one interrogator response to the request to obtain the plurality of status parameters associated with the second client device, wherein the sender client device is selected based on at least one of whether the operating system associated with the second client device matches an operating system of the client device and whether the manufacturer associated with the second client device matches a manufacturer associated with the client device, respectively.

16. The system of claim 15, the stages further comprising:

authenticating the sender client device; and

establishing a file transfer session with the sender client device in response to the authentication of the sender client device.

17. The system of claim 15, wherein the at least one interrogator response further comprises a battery life parameter associated with the second client device, and wherein the client device is configured to select the sender client device based at least in part upon the battery life parameter.

18. The system of claim 15, wherein the at least one interrogator response comprises at least one supported file transfer protocol of the second client device, and wherein the client device is configured to select the sender client device based at least in part upon whether the client device supports the at least one supported file transfer protocol.

19. The system of claim 15, wherein the sender client device is authenticated based at least part upon a one-time password generated from a file hash associated with the file, and wherein the client device authenticates the one-time password by generating the file hash from metadata associated with the file.

20. The system of claim 15, wherein the at least one sender client device is authenticated based at least in part upon an authentication token provided to the client device, and wherein the client device generates a request to authenticate the authentication token that is transmitted to an authentication server.