Cognitive radio system and cognitive radio carrier device

• US 9,294,365 B2
• Filed: 12/05/2013
• Issued: 03/22/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: XpresSpa Group, Inc. (f/k/a FORM Holdings Corp.)
• Inventors: Misra, Saswat, Lang, Andrew K., CHARKOW, Jason, Cohen, David
• Primary Examiner(s): Ho, Duc C
• Application Number:
  US14/098,390
• Publication Number:
  US 20140098766A1
• Time in Patent Office: 838 Days
• Field of Search: None
• 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 identifying a data file;

retrieving the data file from a remote storage device in response to receiving the request, wherein the remote storage device is operated by a party other than a party that operates the server;

identifying a number of collaborator devices, wherein each of the number of collaborator devices is capable of establishing a mobile-to-mobile communications link with the mobile device;

allocating respective portions of the data file 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; and

transmitting of respective portions of the data file to each of the number of collaborator devices according to the allocation.

2. The method of claim 1, wherein the request is identified as having been generated by a mobile application executing on the mobile device.

3. The method of claim 1, wherein retrieving the data file from the remote 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.

4. The method of claim 1, wherein identifying the number of collaborator devices comprises

accessing a database of potential collaborator devices and corresponding geographic locations of those potential collaborator devices.

5. The method of claim 4, wherein identifying the number of collaborator devices comprises:

broadcasting of a message to potential collaborator devices; and

receiving position information associated with each potential collaborator device in response to the broadcasting.

6. The method of claim 5, wherein identifying the number of collaborator devices comprises determining whether to include a potential collaborator device in the number of collaborator devices based on the position information associated with that collaborator device.

7. The method of claim 1, wherein allocating the respective portions of the data file to each of the number of collaborator devices comprises receiving allocation instructions from the mobile device.

8. The method of claim 1, wherein identifying a number of collaborator devices comprises receiving identification of the number of collaborator devices from the mobile device.

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

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

11. The method of claim 10, wherein the number of collaborator devices comprises a tablet computing device.

12. The method of claim 1, wherein data sizes of the respective portions of the data file depend on at least one latency requirement indicated by the request identifying the data file.

13. The method of claim 1, wherein the respective portions of the data file allocated to one of the number of collaborator devices comprises a first portion of a data file and a second portion of the data file separated by a third portion of the data file.

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

15. The method of claim 1, wherein identifying the number of collaborator devices 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 number of collaborator devices.

16. 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 (a) throughput or (b) potential debits associated with that potential collaborator device.

17. The method of claim 1, wherein the debits are assessed as Bitcoins.

18. The method of claim 1, further comprising:

determining a current effective throughput of the mobile device in response to receiving the remote 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 number of collaborator devices.

19. A non-transitory computer-readable storage medium storing computer executable instructions, which when executed by a processor, cause the computing device to perform a method comprising:

receiving a request from a mobile device identifying a data file;

causing retrieval of the data file from a remote storage device in response to receiving the request, wherein the remote storage device is operated by a party other than a party that operates the computing device;

identifying a number of collaborator devices, wherein each of the number of collaborator devices is capable of establishing a mobile-to-mobile communications link with the mobile device;

allocating respective portions of the data file 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; and

causing transmission of respective portions of the data file to each of the number of collaborator devices according to the allocation.

20. The computing device of claim 19, wherein the request is identified as having been generated by a mobile application executing on the mobile device.

21. The computing device of claim 19, wherein causing retrieval of the data file from the storage device comprises causing sending of a request to the server, the request to the server identifying the computing device but not identifying the mobile device.

22. The computing device of claim 19, wherein identifying the number of collaborator devices comprises accessing a database of potential collaborator devices and corresponding geographic locations of those potential collaborator devices.

23. The computing device of claim 22, wherein identifying the number of collaborator devices comprises:

causing a broadcasting of a message to potential collaborator devices; and

receiving position information associated with each potential collaborator device in response to the broadcasting.

24. The computing device of claim 23, wherein identifying the number of collaborator devices comprises determining whether to include a potential collaborator device in the number of collaborator devices based on the position information associated with that collaborator device.

25. The computing device of claim 19, wherein allocating the respective portions of the data file to each of the number of collaborator devices comprises receiving allocation instructions from the mobile device.

26. The computing device of claim 19, wherein identifying a number of collaborator devices comprises receiving identification of the number of collaborator devices from the mobile device.

27. The computing device of claim 19, wherein identifying a number of collaborator devices comprises selecting the number of collaborator devices from a number of potential collaborator devices at the computing device.

28. The computing device of claim 19, wherein each of the number of collaborator devices is a mobile device.

29. The computing device of claim 28, wherein the number of collaborator devices comprises a tablet computing device.

30. The computing device of claim 19, wherein data sizes of the respective portions of the data file depend on at least one latency requirement indicated by the request identifying the data file.

31. The computing device of claim 19, wherein the respective portions of the data file allocated to one of the number of collaborator devices comprises a first portion of a data file and a second portion of the data file separated by a third portion of the data file.

32. The computing device of claim 19, wherein one of the number of collaborator devices is capable of an LTE-Direct based mobile-to-mobile communications link with the mobile device.

33. The computing device of claim 19, wherein identifying the number of collaborator devices comprises:

causing transmission of 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 number of collaborator devices.

34. The computing device of claim 19, further comprising causing transmission of 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 (a) throughput or (b) potential debits associated with that potential collaborator device.

35. The computing device of claim 19, wherein the debits are assessed as Bitcoins.

36. The computing device of claim 19, further comprising:

determining a current effective throughput of the mobile device in response to receiving the remote 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 number of collaborator devices.