Server function for device-to-device based content delivery

• US 9,300,724 B2
• Filed: 09/18/2014
• Issued: 03/29/2016
• Est. Priority Date: 05/08/2013
• Status: Active Grant

• Current Assignee: XpresSpa Group, Inc. (f/k/a FORM Holdings Corp.)
• Original Assignee: XpresSpa Group, Inc. (f/k/a FORM Holdings Corp.)
• Inventors: Lang, Andrew K., Misra, Saswat
• Primary Examiner(s): HO, DUC CHI
• Application Number:
  US14/490,494
• Publication Number:
  US 20150046570A1
• Time in Patent Office: 558 Days
• Field of Search: 709/224, 455/414.2
• US Class Current: 1/1
• CPC Class Codes: G06Q 20/065 using e-cash
• CPC Class Codes: G06Q 20/123 Shopping for digital content
• CPC Class Codes: G06Q 20/223 based on the use of peer-to-peer networks
• CPC Class Codes: H04L 41/50 Network service management, e.g. ensuring proper service fulfilment according to agreements
• CPC Class Codes: H04L 43/0805 by checking availability
• CPC Class Codes: H04L 47/70 Admission control; Resource allocation
• CPC Class Codes: H04L 5/0037 Inter-user or inter-terminal allocation
• CPC Class Codes: H04L 63/0853 using an additional device, e.g. smartcard, SIM or a different communication terminal cryptographic mechanisms or cryptographic arrangements for entity authentication involving additional secure or trusted devices H04L9/3234
• CPC Class Codes: H04L 65/61 for supporting one-way streaming services, e.g. Internet radio
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 67/104 Peer-to-peer [P2P] networks
• CPC Class Codes: H04L 67/1063 Discovery through centralising entities
• CPC Class Codes: H04L 67/1068 Discovery involving direct consultation or announcement among potential requesting and potential source peers
• CPC Class Codes: H04L 67/1074 for supporting data block transmission mechanisms file transfer H04L67/06
• CPC Class Codes: H04L 67/108 characterised by resources being split in blocks or fragments
• CPC Class Codes: H04L 67/52 specially adapted for the location of the user terminal
• CPC Class Codes: H04L 67/53 using third party service providers
• CPC Class Codes: H04M 15/07 Split billing, i.e. both A-party and B-party charged for the communication
• CPC Class Codes: H04M 15/31 Distributed metering or calculation of charges
• CPC Class Codes: H04M 15/46 Real-time negotiation between users and providers or operators
• CPC Class Codes: H04M 15/93 : using near field or similar technologies
• CPC Class Codes: H04W 12/06 : Authentication
• CPC Class Codes: H04W 4/24 : Accounting or billing
• CPC Class Codes: H04W 76/14 : Direct-mode setup
• CPC Class Codes: H04W 76/15 : Setup of multiple wireless link connections
• CPC Class Codes: H04W 84/12 : WLAN [Wireless Local Area Networks]
• CPC Class Codes: H04W 88/04 : adapted for relaying to or from another terminal or user

Abstract

A method for operating a server includes receiving, at the server, a request from a mobile device identifying a data file and retrieving the data file from a remote storage device in response to receiving the request. A party other than a party that operates the server operates the remote storage device. A number of collaborator devices are identified. Each of the number of collaborator devices is capable of establishing a mobile-to-mobile communications link with the mobile device. Respective portions of the data file are allocated to each of the number of collaborator devices based on at least one of (a) throughputs associated with the number of collaborator devices and (b) potential debits charged by the number of collaborator devices. Respective portions of the data file are transmitted to each of the number of collaborator devices according to the allocation.

Claims

1. A method for operating a server comprising:

receiving, at the server, a request from a mobile device comprising (a) identification of a data file and (b) an indication that either a streaming mode or a download mode is associated with the request;

retrieving the data file from a storage device in response to receiving the request, wherein the storage device is located remotely from the server and the mobile device;

identifying a collaborator device and a percentage of the data file to be assigned to the collaborator device, wherein the collaborator device is capable of establishing a mobile-to-mobile communications link with the mobile device;

assigning the percentage of the data file to the collaborator device as a single contiguous portion of the data file or as a plurality of non-contiguous portions of the data file based on whether the streaming mode or the download mode is associated with the data file; and

transmitting the portion of the data file corresponding to the assigned percentage to the collaborator device.

2. The method of claim 1, wherein the percentage of the data file assigned to the collaborator device is based on a throughput associated with the collaborator device and a potential debit charged by the collaborator device.

3. The method of claim 1, further comprising identifying the request as having been generated by a mobile application executing on the mobile device.

4. The method of claim 1, wherein retrieving the data file from the storage device comprises sending a request to the storage device, the request to the storage device identifying the server but not identifying the mobile device.

5. The method of claim 1, wherein identifying the collaborator device comprises accessing a database of potential collaborator devices and corresponding geographic locations of the potential collaborator devices.

6. The method of claim 5, wherein identifying the collaborator device comprises broadcasting of a message to potential collaborator devices;

and receiving position information associated with each of the potential collaborator devices in response to the broadcasting.

7. The method of claim 1, wherein assigning the percentage of the data file to the collaborator device comprises receiving allocation instructions from the mobile device.

8. The method of claim 1, wherein identifying the collaborator device comprises receiving information identifying the collaborator device from the mobile device.

9. The method of claim 1, wherein identifying the collaborator device comprises selecting, at the server, the collaborator device from a number of potential collaborator devices.

10. The method of claim 1, wherein the collaborator device is a mobile device.

11. The method of claim 10, wherein the collaborator device is a tablet computing device.

12. The method of claim 1, wherein the request comprises information indicative of at least one latency requirement, and wherein the percentage of the data file depends on the at least one latency requirement.

13. The method of claim 1, wherein the collaborator device is capable of an LTE-Direct based mobile-to-mobile communications link with the mobile device.

14. The method of claim 1, wherein identifying the collaborator device comprises:

transmitting a message from the mobile device to potential collaborator devices located in the vicinity of the mobile device; and

in response to the transmission, receiving at least one response message identifying the collaborator device.

15. The method of claim 1, further comprising transmitting instructions to generate, on a display of the mobile device, a listing of potential collaborator devices, wherein the listing for each potential collaborator device includes an indication of throughput or potential debits associated with that potential collaborator device.

16. The method of claim 1, wherein the debits are represented as Bitcoins.

17. The method of claim 1, further comprising:

determining a current effective throughput of the mobile device in response to receiving the request; and

in response to determination that the current effective throughput of the mobile device is not sufficient to download the data file within a specified time constraint, performing the identification of the collaborator device.

18. A server system comprising:

a processor; and

a memory storing computer executable instructions, which, when executed by the processor, cause the server system to;

receive a request from a mobile device comprising (a) identification of a data file and (b) an indication that either a streaming mode or a download mode is associated with the request;

retrieve the data file from a storage device in response to receiving the request, wherein the storage device is located remotely from the server and the mobile device;

identify a collaborator device and a percentage of the data file to be assigned to the collaborator device, wherein the collaborator device is capable of establishing a mobile-to-mobile communications link with the mobile device;

assign the percentage of the data file to the collaborator device as a single contiguous portion of the data file or as a plurality of non-contiguous portions of the data file based on whether the streaming mode or the download mode is associated with the data file; and

transmit the portion of the data file corresponding to the assigned percentage to the collaborator device.

19. The server system of claim 18, wherein the computer executable instructions, when executed by the processor, cause the server system to assign the percentage of the data file based on a throughput associated with the collaborator device and a potential debit charged by the collaborator device.

20. The server system of claim 18, wherein the computer executable instructions, when executed by the processor, cause the server system to retrieve the data file from the storage device by, at least in part, sending a request to the storage device, the request to the storage device identifying the server but not identifying the mobile device.

21. The server system of claim 18, wherein the computer executable instructions, when executed by the processor, cause the server system to identify the collaborator device by, at least in part, accessing a database of potential collaborator devices and corresponding geographic locations of the potential collaborator devices.

22. The server system of claim 21, wherein the computer executable instructions, when executed by the processor, cause the server system to identify the collaborator device by, at least in part, broadcasting a message to potential collaborator devices and receiving position information associated with each of the potential collaborator devices in response to the broadcasting.

23. The server system of claim 18, wherein the computer executable instructions, when executed by the processor, cause the server system to assign the percentage of the data file to the collaborator device based on, at least in part, allocation instructions received from the mobile device.

24. The server system of claim 18, wherein the computer executable instructions, when executed by the processor, cause the server system to identify the collaborator device based on information received from the mobile device identifying the collaborator device.

25. The server system of claim 18, wherein the computer executable instructions, when executed by the processor, cause the server system to identify the collaborator device by, at least in part, selecting the collaborator device from a number of potential collaborator devices.

26. The server system of claim 18, wherein the collaborator device is a mobile device.

27. The server system of claim 18, wherein the request comprises information indicative of at least one latency requirement, and wherein the percentage of the data file depends on the at least one latency requirement.

28. The server system of claim 18, wherein the collaborator device is capable of an LTE-Direct based mobile-to-mobile communications link with the mobile device.

29. The server system of claim 18, wherein the computer executable instructions, when executed by the processor, cause the server system to identify the collaborator device by, at least in part, transmitting a message from the mobile device to potential collaborator devices located in the vicinity of the mobile device;

and in response to the transmission, receiving at least one response message identifying the collaborator device.

30. The server system of claim 18, wherein the computer executable instructions, when executed by the processor, cause the server system to transmit instructions to generate, on a display of the mobile device, a listing of potential collaborator devices, wherein the listing for each potential collaborator device includes an indication of throughput or potential debits associated with that potential collaborator device.

31. The server system of claim 18, wherein the debits are represented as Bitcoins.

32. The server system of claim 18, wherein the computer executable instructions, when executed by the processor, cause the server system to determine a current effective throughput of the mobile device in response to receiving the request;

and in response to determination that the current effective throughput of the mobile device is not sufficient to download the data file within a specified time constraint, perform the identification of the collaborator device.