Distributed handoff-related processing for wireless networks

1. A tangible, non-transitory, machine-readable medium storing instructions that when executed by one or more processors effectuate operations comprising:

calling, with one or more processors, a distributed application protocol interface (API) of a distributed application with a request, wherein:

the distributed application executes on one or more peer nodes of a peer-to-peer network of computing devices;

the request causes the distributed application to provision a computing resource from at least one of the computing devices; and

the computing resource is accessible from at least one of the peer nodes of the peer-to-peer network;

storing a computing resource record corresponding to the computing resource in a distributed hash table, wherein the computing resource record indicates at least one of the computing devices used by the computing resource;

executing a program on data offloaded onto one or more data centers used by the computing resource, wherein an output of the program is a program state;

transferring the program state to a plurality of the peer nodes of the peer-to-peer network based on the computing resource record stored in the distributed hash table; and

ceasing to use the computing resource.

2. The medium of claim 1 , wherein the distributed application is a distributed handoff application, and wherein the operations further comprise:

receiving a signal from a mobile computing device at a plurality of base stations, wherein the plurality of base stations comprises a first base station and a second base station;

receiving, at the plurality of base stations, a set of signal strength measurements for the plurality of base stations perceived by the mobile computing device; and

committing to a handoff decision between the first base station and the second base station based on the set of signal strength measurements and one or more criteria encoded in a smart contract.

3. The medium of claim 1 , wherein an entry in the distributed hash table is linked to a key value in the distributed hash table corresponding to an address of the distributed application.

4. The medium of claim 1 , wherein:

the operations to provision the computing resource comprises instantiating a computational entity;

the computational entity comprises at least one of a virtual machine, container, or unikernel; and

the computing resource comprises the one or more data centers.

5. The medium of claim 1 , wherein the operations further comprise:

receiving the data at a first base station during a wireless data session;

transmitting the data at a bandwidth greater than one gigabyte per second to the one or more data centers;

effectuating a handoff of the wireless data session from the first base station to a second base station;

executing a neural network computation on the one or more the data centers, wherein the neural network is configured to detect features within images; and

conveying results of the neural network computation from the second base station to a mobile computing device within 200 milliseconds of receiving the data at the first base station.

6. The medium of claim 1 , wherein the operations further comprise concurrently sending data to a first data center corresponding to a first peer node of the peer-to-peer network and a second data center corresponding to a second peer node of the peer-to-peer network.

7. The medium of claim 1 , wherein:

the operations further comprise constructing a computing cluster that moves with a mobile computing device onto different data centers associated with base stations designated to communicate with the mobile computing device; and

the data is from a plurality of sensors of the mobile computing device that is streamed to the cluster, at least in part, via a first base station of a set of base stations; and

wherein transferring the program state comprises transferring the program state based on the data for the computing cluster.

8. The medium of claim 1 , wherein:

each peer node of the peer-to-peer network is assigned a node identifier;

the node identifier is a unique key determined by a cryptographic hash function and is organized on an identifier ring; and

the order of the peer nodes represented by the identifier ring is based on an ordering of the node identifiers.

9. The medium of claim 8 , wherein the operations further comprise labeling a file with a resource identifier, wherein the file is stored on a first peer compute node in the peer-to-peer network, and wherein the resource identifier is closest to an identifier of the first peer compute node in an address space of the identifier ring.

10. The medium of claim 1 , wherein the operations to provision the computing resource comprise instantiating a serverless function that operates on a first data center of the one or more data centers in response to a mobile computing device moving through a geographic area served by the first data center.

11. The medium of claim 1 , wherein the operations further comprise registering a persistent name of a mobile computing device with a base station of a set of base stations, wherein the persistent name is associated with the mobile computing device across the set of base stations.

12. The medium of claim 11 , wherein the operations further comprise:

resolving the persistent name at a first layer of a protocol stack to determine a network address; and

resolving the persistent name at a second layer of a protocol stack to determine a route to a wireless computing device.

13. The medium of claim 11 , wherein the operations further comprise:

receiving a cryptographic signature from the mobile computing device associated with the persistent name;

determining whether the cryptographic signature is valid; and

registering the persistent name in a memory of the base station in response to a determination that the cryptographic signature is valid.

14. The medium of claim 11 , wherein the base station is a first base station, and wherein registering the persistent name comprises:

updating a record in a memory of a second base station with an association between the persistent name with a wireless channel access configuration assigned to the mobile computing device; and

updating records as a means for performing a distributed name lookup.

15. The medium of claim 11 , wherein the base station is a first base station, and wherein registering the persistent name comprises:

designating the mobile computing device as having severed connection with the first base station in a routing table of the first base station; and

adding a pointer to a second base station to a record in a memory of the first base station that associates the pointer with the persistent name.

16. The medium of claim 1 , wherein the distributed application is a distributed handoff application, and wherein the operations further comprise:

obtaining a distributed-application address of the distributed handoff application, wherein:

the distributed-application address is a cryptographic hash value that uniquely identifies the distributed handoff application among a plurality of distributed applications executable on the peer nodes;

the distributed handoff application is accessible via one or more of the peer nodes identified by entries, wherein each entry is linked to a key value corresponding to the distributed-application address; and

the distributed handoff application comprises a distributed-handoff API by which handoff from a first base station to a second base station is coordinated at least in part by at least some of the peer nodes of the peer-to-peer network;

calling the distributed-handoff API with a second request to perform a handoff of a wireless data session between the first base station and a mobile computing device to the second base station, wherein the second request causes one or more parameters of the handoff of the wireless data session to be sent to both the mobile computing device and the second base station; and

receiving a result of the second request and, in response, at least partially effectuating the handoff of the wireless data session from the first base station to the second base station.

17. The medium of claim 16 , wherein:

the operations comprise obtaining a geolocation of the mobile computing device determined by a location sensor of the mobile computing device based on wireless beacons received from a plurality of satellites;

a plurality of candidate base stations are selected based on the obtained geolocation;

a public Internet Protocol address of the mobile computing device persists across the handoff, wherein the mobile computing device is reachable via the public Internet Protocol address before and after the handoff;

the public Internet Protocol address is associated with the first base station by the distributed hash table before the handoff; and

the public Internet Protocol address is associated with the second base station by the distributed hash table after the handoff.

18. The medium of claim 16 , wherein the operations further comprise:

receiving a set of bids, wherein each bid is a value that corresponds with one of a plurality of candidate base stations;

determine a set of scores based on the set of bids using a smart contract, wherein each of the set of scores correspond to one of the set of bids based on their respective bid parameters; and

select the second base station from the plurality of candidate base stations based on the set of scores.

19. The medium of claim 16 , wherein the operations further comprise selecting the second base station from among a plurality of candidate base stations based on respective coverage areas of the plurality of candidate base stations and a mobile computing device route.

20. A method comprising:

calling, with one or more processors, a distributed application protocol interface (API) of a distributed application with a request, wherein:

the distributed application executes on one or more peer nodes of a peer-to-peer network of computing devices;

the request causes the distributed application to provision a computing resource from at least one of the computing devices; and

the computing resource is accessible from at least one of the peer nodes of the peer-to-peer network;

storing a computing resource record corresponding to the computing resource in a distributed hash table, wherein the computing resource record indicates at least one of the computing devices used by the computing resource;

executing a program on data offloaded onto one or more data centers used by the computing resource, wherein an output of the program is a program state;

transferring the program state to a plurality of the peer nodes of the peer-to-peer network based on the computing resource record; and

ceasing to use the computing resource.