Cognitive Radio System And Cognitive Radio Carrier Device

• US 20140094140A1
• Filed: 12/05/2013
• Published: 04/03/2014
• 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: David Cohen, Saswat Misra
• Inventors: Lang, Andrew K., MISRA, Saswat, CHARKOW, Jason, COHEN, David
• Granted Patent: US 9,401,850 B2
• Time in Patent Office: Days
• US Class Current: 455/407
• 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 receiving data on a mobile device includes accessing information identifying a number of collaborator devices and receiving respective portions of the data from each of the number of collaborator devices. The respective portions depend on at least one of (a) throughputs between the mobile device and the number of collaborator devices and (b) potential debits charged by the number of collaborator devices. The receiving occurs via mobile-to-mobile connections between the mobile device and the number of collaborator devices. The received respective portions of data are stored at the mobile device. Content is generated on a display of the mobile device based on the stored respective portions of the data.

Claims

1. A method for receiving data on a mobile device, the method comprising:

accessing information;

identifying a number of collaborator devices;

receiving respective portions of the data from each of the number of collaborator devices, wherein the respective portions depend on at least one of (a) throughputs between the mobile device and the number of collaborator devices and (b) potential debits charged by the number of collaborator devices, wherein the receiving occurs via mobile-to-mobile connections between the mobile device and the number of collaborator devices;

storing, at the mobile device, the received respective portions of data; and

generating content on a display of the mobile device based on the stored respective portions of the data.

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

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

4. The method of claim 1, wherein the content is streamed to the display of the mobile device and wherein data sizes of the respective portions depend on at least one latency requirement of the streamed content.

5. The method of claim 1, wherein the respective portions of the data received from 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.

6. The method of claim 1, wherein one of the number of collaborator devices receives its respective portions of the data from another collaborator device via a first mobile-to-mobile connection and forwards its respective portions of the data to the mobile device via a second mobile-to-mobile connection.

7. The method of claim 1, wherein the mobile-to-mobile connections comprise an LTE-Direct based connection.

8. The method of claim 1, wherein the accessing information identifying the number of collaborator devices comprises:

transmitting a first message from the mobile device to a server remote to the mobile device, the first message requesting collaborator information; and

in response to the transmission, receiving a second message from the server, wherein the second message identifies the number of collaborator devices.

9. The method of claim 1, wherein the accessing information identifying the number of collaborator devices comprises:

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

in response to the transmission, receiving a number of response messages from at least some of the potential collaborator devices, the number of response messages collectively identifying the number of collaborator devices.

10. The method of claim 1, wherein the accessing information identifying the number of collaborator devices comprises:

receiving a respective broadcast message from each of the collaborator devices indicating an identity of that collaborator device.

11. The method of claim 1, further comprising generating, on the 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 device.

12. The method of claim 11, further comprising:

sequentially receiving user selection of each of the number of collaborator devices from the listing potential collaborator devices, wherein each selection of a collaborator device from the listing generates instructions to update a displayed estimated transfer time associated with the data file on the display of the mobile device.

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

14. The method of claim 1, further comprising receiving a request to download the data and an associated time constraint for downloading the data.

15. The method of claim 14, further comprising:

determining a current effective throughput of the mobile device; and

in response to determination that the current effective throughput of the mobile device is not sufficient to download the data within the time constraint, performing the accessing of information identifying the number of collaborator devices.

16. The method of claim 1, wherein the mobile-to-mobile connections between the mobile device and the number of collaborator devices comprise:

a first connection receiving data from a first collaborator device operating according to a WiFi protocol; and

simultaneously with the first connection, a second connection receiving data from a second collaborator device operating according to a communications protocol other than a WiFi protocol.

17. A mobile application comprising computer executable instructions stored on a non-transitory computer-readable storage medium, which when executed by a processor of a mobile device, cause the processor to perform a method comprising:

accessing information identifying a number of collaborator devices;

receiving respective portions of data from each of the number of collaborator devices, wherein the respective portions depend on at least one of (a) throughputs between the mobile device and the number of collaborator devices and (b) potential debits charged by the number of collaborator devices, wherein the receiving occurs via mobile-to-mobile connections between the mobile device and the number of collaborator devices;

providing instructions to store, at the mobile device, the received respective portions of data; and

providing instructions to generate content on a display of the mobile device based on the stored respective portions of data.

18. The mobile application of claim 17, wherein each of the number of collaborator devices is a mobile device.

19. The mobile application of claim 18, wherein the number of collaborator devices comprises a tablet computing device.

20. The mobile application of claim 17, wherein the content is streamed to the display of the mobile device and wherein data sizes of the respective portions depend on at least one latency requirement of the streamed content.

21. The mobile application of claim 17, wherein the respective portions of the data received from 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.

22. The mobile application of claim 17, wherein one of the number of collaborator devices receives its respective portions of the data from another collaborator device via a first mobile-to-mobile connection and forwards its respective portions of the data to the mobile device via a second mobile-to-mobile connection.

23. The mobile application of claim 17, wherein the mobile-to-mobile connections comprise an LTE-Direct based connection.

24. The mobile application of claim 17, wherein the accessing information identifying the number of collaborator devices comprises:

causing transmission of a first message from the mobile device to a server remote to the mobile device, the first message requesting collaborator information; and

in response to the transmission, receiving a second message from the server, wherein the second message identifies the number of collaborator devices.

25. The mobile application of claim 17, wherein the accessing information 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 a number of response messages from at least some of the potential collaborator devices, the number of response messages collectively identifying the number of collaborator devices.

26. The mobile application of claim 17, wherein the accessing information identifying the number of collaborator devices comprises:

receiving a respective broadcast message from each of the collaborator devices indicating an identity of that collaborator device.

27. The mobile application of claim 17, the method further comprising providing instructions to generate, on the 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 device.

28. The mobile application of claim 27, the method further comprising:

sequentially receiving user selection of each of the number of collaborator devices from the listing potential collaborator devices, wherein each selection of a collaborator device from the listing generates instructions to update a displayed estimated transfer time associated with the data file on the display of the mobile device.

29. The mobile application of claim 17, wherein the debits are assessed as Bitcoins.

30. The mobile application of claim 17, further comprising receiving a request to download the data and an associated time constraint for downloading the data.

31. The mobile application of claim 30, the method further comprising:

determining a current effective throughput of the mobile device; and

in response to determination that the current effective throughput of the mobile device is not sufficient to download the data within the time constraint, performing the accessing of information identifying the number of collaborator devices.

32. The mobile application of claim 17, wherein the mobile-to-mobile connections between the mobile device and the number of collaborator devices comprise:

a first connection receiving data from a first collaborator device operating according to a WiFi protocol; and

simultaneously with the first connection, a second connection receiving data from a second collaborator device operating according to a communications protocol other than a WiFi protocol.