Peer-to-peer distribution of radio protocol data for software defined radio (SDR) updates
Updated radio protocol data may be propagated in a peer-to-peer (P2P) distribution scheme so that peer devices that are incompatible with a particular radio protocol may be dynamically re-configured to communicate with other devices using the particular radio protocol. A remote server(s) may push updated radio protocol data to a hub device, which thereafter disseminates the radio protocol data to other peer devices. These peer devices can forward the data to downstream peer devices, and so on, without further intervention by the remote server(s) that initiated the distribution. The transfer of radio protocol data over P2P connections may occur using a broadcasting technique where, prior to the transfer, a device in possession of the radio protocol data broadcasts an indication to nearby peer devices, which can receive the broadcast and indicate to the broadcaster whether they are ready to receive the radio protocol data.
1. A hub device, comprising:
a processor; and
memory storing computer-executable instructions that, when executed by the processor, cause the hub device to:
receive, from a remote server, (i) updated radio protocol data that corresponds to an update to a particular radio protocol and (ii) an instruction to disseminate, without further intervention by the remote server, the updated radio protocol data from the hub device to peer devices;
broadcast, within a local environment where the hub device is located, an indication that the hub device is in possession of the updated radio protocol data;
receive, via the hub device and from a peer device that is incompatible with the particular radio protocol, an indication that the peer device is ready to receive the updated radio protocol data from the hub device; and
send, over a peer-to-peer connection with the peer device, the updated radio protocol data to the peer device, the hub device routing the updated radio protocol data based on the hub device being incompatible with the particular radio protocol, the peer device being reconfigured by the updated radio protocol data and operable to establish a connection, and communicate, with other devices utilizing the particular radio protocol, the peer device communicating with at least one of the other devices without the hub device being reconfigured by the updated radio protocol data.
2. The hub device of claim 1 , wherein the computer-executable instructions, when executed by the processor, further cause the hub device to:
reconfigure, based on the updated radio protocol data, one or more components of a software defined radio (SDR) of the hub device to convert the SDR of the hub device to a reconfigured SDR that is operable to establish a connection, and communicate, with the other devices using the particular radio protocol; and
maintain, in the memory, an original version of the SDR of the hub device.
3. The hub device of claim 2 , wherein the computer-executable instructions, when executed by the processor, further cause the hub device to:
determine that the updated radio protocol data is signed by a trusted entity,
wherein reconfiguring the one or more components of the SDR of the hub device is conditioned on the updated radio protocol being signed by the trusted entity.
4. The hub device of claim 1 , wherein the computer-executable instructions, when executed by the processor, further cause the hub device to:
determine that there is an issue with the updated radio protocol data after sending the updated radio protocol data to the peer device over the peer-to-peer connection with the peer device; and
send, in response to determining that there is the issue with the updated radio protocol data, an instruction to the peer device to revoke the updated radio protocol data and revert to an original version of a software defined radio (SDR) of the peer device.
5. The hub device of claim 1 , wherein the computer-executable instructions, when executed by the processor, further cause the hub device to, after sending the updated radio protocol data:
receive, from the peer device, propagation data that includes:
a list of peer devices, including the peer device, that received the updated radio protocol data; and
timestamp data indicating times when the updated radio protocol data was received at each peer device in the list; and
forward the propagation data to the remote server.
6. The hub device of claim 5 , wherein the propagation data further includes at least one of:
geographic locations where each peer device in the list was located when the updated radio protocol data was received at each peer device; or
information about whether each peer device in the list (i) implemented the updated radio protocol data or (ii) forwarded the updated radio protocol data to another peer device without implementing the updated radio protocol data.
7. A method, comprising:
broadcasting, via a hub device, an indication that the hub device is in possession of updated radio protocol data that corresponds to an update to a particular radio protocol;
receiving, via the hub device and from a peer device that is incompatible with the particular radio protocol, an indication that the peer device is ready to receive the updated radio protocol data from the hub device; and
sending, via the hub device and over a peer-to-peer connection, the updated radio protocol data to the peer device, the hub device routing the updated radio protocol data based on the hub device being incompatible with the particular radio protocol, the peer device communicating with at least one other device without the hub device being reconfigured by the updated radio protocol data.
8. The method of claim 7 , further comprising:
receiving, from a remote server, the updated radio protocol data.
9. The method of claim 7 , further comprising:
receiving, from a remote server an instruction to disseminate the updated radio protocol data from the hub device to one or more peer devices including the peer device.
10. The method of claim 7 , further comprising:
reconfiguring, based at least in part on the updated radio protocol data, one or more components of a software defined radio (SDR) of the hub device to convert the SDR of the hub device to a reconfigured SDR that is operable to establish a connection with other devices using the particular radio protocol.
11. The method of claim 10 , further comprising:
determining that the updated radio protocol data is signed by a trusted entity,
wherein reconfiguring the one or more components of the SDR of the hub device is conditioned on the updated radio protocol being signed by the trusted entity.
12. The method of claim 7 , further comprising:
determining that there is an issue with the updated radio protocol data; and
sending, in response to determining that there is the issue with the updated radio protocol data, an instruction to the peer device to revoke the updated radio protocol data and revert to an original version of a software defined radio (SDR) of the peer device.
13. The method of claim 7 , further comprising:
receiving, from the peer device, propagation data that includes a list of peer devices, including the peer device, that received the updated radio protocol data; and
forwarding the propagation data to a remote server.
14. A system, comprising:
a processor; and
memory storing instructions that, when executed by the processor, cause the system to:
broadcast an indication that a hub device is in possession of updated radio protocol data that corresponds to an update to a particular radio protocol;
receive, via the hub device and from a peer device that is incompatible with the particular radio protocol, an indication that the peer device is ready to receive the updated radio protocol data from the hub device; and
send, over a peer-to-peer connection, the updated radio protocol data to the peer device, the hub device routing the updated radio protocol data based on the hub device being incompatible with the particular radio protocol, the peer device communicating with at least one other device without the hub device being reconfigured by the updated radio protocol data.
15. The system of claim 14 , wherein the instructions, when executed by the processor, further cause the system to:
receive, from a remote server, the updated radio protocol data.
16. The system of claim 14 wherein the instructions, when executed by the processor, further cause the system to:
receive, from a remote server an instruction to disseminate the updated radio protocol data from the hub device to one or more peer devices including the peer device.
17. The system of claim 14 , wherein the instructions, when executed by the processor, further cause the system to:
reconfigure, based at least in part on the updated radio protocol data, one or more components of a software defined radio (SDR) of the hub device to convert the SDR of the hub device to a reconfigured SDR that is operable to establish a connection with other devices using the particular radio protocol.
18. The system of claim 17 , wherein the instructions, when executed by the processor, further cause the system to:
determine that the updated radio protocol data is signed by a trusted entity,
wherein the system reconfigures the one or more components of the SDR of the hub device on a condition that the updated radio protocol is signed by the trusted entity.
19. The system of claim 14 , wherein the instructions, when executed by the processor, further cause the system to:
determine that there is an issue with the updated radio protocol data; and
send an instruction to the peer device to revoke the updated radio protocol data and revert to an original version of a software defined radio (SDR) of the peer device.
20. The system of claim 14 , wherein the instructions, when executed by the processor, further cause the system to:
receive, from the peer device, propagation data that includes a list of peer devices, including the peer device, that received the updated radio protocol data; and
forward the propagation data to the remote server.