Device-to-device based content delivery for time-constrained communications

• US 9,374,280 B2
• Filed: 09/18/2014
• Issued: 06/21/2016
• Est. Priority Date: 05/08/2013
• Status: Active Grant

• Current Assignee: Vringo Infrastructure, Inc. (XpresSpa Group, Inc. (f/k/a FORM Holdings Corp.))
• Original Assignee: Vringo Infrastructure, Inc. (XpresSpa Group, Inc. (f/k/a FORM Holdings Corp.))
• Inventors: Misra, Saswat, Lang, Andrew K.
• Primary Examiner(s): HO, DUC CHI
• Application Number:
  US14/490,506
• Publication Number:
  US 20150006739A1
• Time in Patent Office: 642 Days
• Field of Search: 709/224
• 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 mobile device comprising:

a processor; and

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

receive a first request to download a data file;

determine a time constraint associated with the download of the data file;

in response to a determination that a bandwidth of the mobile device is insufficient for the download of the data file within the time constraint, transmit a second request to one or more potential collaborator devices;

assign a respective portion of the data file to a number of collaborator devices selected from the one or more potential collaborator devices;

receive the assigned respective portions of the data file from the number of collaborator devices; and

store the assigned portions of the data file in the memory.

2. The mobile device of claim 1, wherein the number of collaborator devices comprises at least one stationary hotspot device.

3. The mobile device of claim 1, wherein the first request comprises a request for an identity and a bandwidth availability of a potential collaborator device.

4. The mobile device of claim 3, wherein the computer executable instructions, when executed by the processor, cause the mobile device to select the number of collaborator devices from the one or more potential collaborator devices based on respective bandwidth availabilities advertised by the one or more potential collaborator devices.

5. The mobile device of claim 1, wherein the first request is received automatically, without any further user input, based on a predefined schedule.

6. The mobile device of claim 1, wherein the computer executable instructions, when executed by the processor, cause the mobile device to determine the time constraint based on accessing calendar information stored on the mobile device.

7. The mobile device of claim 1, wherein the computer executable instructions, when executed by the processor, cause the mobile device to determine the time constraint based on accessing travel schedule information stored on the mobile device.

8. The mobile device of claim 1, wherein the computer executable instructions, when executed by the processor, cause the mobile device to determine the time constraint based on a predicted time at which a network connection of the mobile device will become unavailable.

9. The mobile device of claim 1, wherein the computer executable instructions, when executed by the processor, cause the mobile device to:

monitor an actual bandwidth provided by a respective collaborator device in the number of collaborator devices; and

remove the collaborator device from the number of collaborator devices in response to a determination that the actual bandwidth of the collaborator device is less than a bandwidth previously advertised by the collaborator device.

10. The mobile device of claim 1, wherein the computer executable instructions, when executed by the processor, cause the mobile device to:

monitor an actual bandwidth provided by each of the number of collaborator devices; and

add an additional collaborator device to the number of collaborator devices based on a determination that mobile device is not on pace to download the data file within the time constraint according to the monitored actual bandwidth provided by each of the number of collaborator devices.

11. A method for retrieving a data file using a collaborator device, the method comprising:

receiving a first request to download the data file;

determining a time constraint associated with the download of the data file;

in response to a determination that a bandwidth of a mobile device is insufficient for the download of the data file within the time constraint, transmitting a second request to one or more potential collaborator devices;

assigning a respective portion of the data file to a number of collaborator devices selected from the one or more potential collaborator devices;

receiving the assigned respective portions of the data file from the number of collaborator devices; and

storing the assigned portions of the data file in the memory.

12. The method of claim 11, wherein the number of collaborator devices comprises at least one stationary hotspot device.

13. The method of claim 11, wherein the first request comprises a request for an identity and a bandwidth availability of a potential collaborator device.

14. The method of claim 13, comprising selecting the number of collaborator devices from the one or more potential collaborator devices based on respective bandwidth availabilities advertised by the one or more potential collaborator devices.

15. The method of claim 11, wherein the first request is received automatically, without any further user input, based on a predefined schedule.

16. The method of claim 11, comprising determining the time constraint based on accessing calendar information stored on the mobile device.

17. The method of claim 11, comprising determining the time constraint based on accessing travel schedule information stored on the mobile device.

18. The method of claim 11, comprising determining the time constraint based on a predicted time at which a network connection of the mobile device will become unavailable.

19. The method of claim 11, comprising:

monitoring an actual bandwidth provided by a respective collaborator device in the number of collaborator devices; and

removing the collaborator device from the number of collaborator devices in response to a determination that the actual bandwidth of the collaborator device is less than a bandwidth previously advertised by the collaborator device.

20. The method of claim 11, comprising monitoring an actual bandwidth provided by each of the number of collaborator devices;

and

adding an additional collaborator device to the number of collaborator devices based on a determination that mobile device is not on pace to download the data file within the time constraint according to the monitored actual bandwidth provided by each of the number of collaborator devices.