# US 11,310,305 B1 · Systems and methods for locating microserver nodes in proximity to edge devices using georouting > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 11,310,305 B1 - Document ID: US11310305B1 - Status: Granted - Kind: B1 - Application number: 17/394,932 - Filed: 2021-08-05 - Granted: 2022-04-19 - Earliest claimed: 2019-11-04 - Assignees: Edjx, Inc. - Applicants: EDJX, Inc. - Inventors: James A. Thomason - Web page: https://patentgrep.com/patent/US11310305B1 ## CPC - G06F 9/547: {Remote procedure calls [RPC]; Web services} - H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP] - G06F 21/6218: {to a system of files or objects, e.g. local or distributed file system or database} - H04L 9/0643: {Hash functions, e.g. MD5, SHA, HMAC or f9 MAC} - H04L 45/12: Shortest path evaluation - H04L 61/4511: using domain name system [DNS] - H04L 67/1021: based on client or server locations - H04L 67/1038: Load balancing arrangements to avoid a single path through a load balancer - H04L 67/104: Peer-to-peer [P2P] networks - H04W 40/20: based on geographic position or location - G06F 2221/2111: Location-sensitive, e.g. geographical location, GPS - H04L 9/50: {using hash chains, e.g. blockchains or hash trees} - H04L 63/126: {the source of the received data} - H04L 2209/56: Financial cryptography, e.g. electronic payment or e-cash - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) ## Abstract Systems and methods for locating microserver nodes in proximity to edge devices using georouting are disclosed. Microservers automatically form a global peer-to-peer network to serve edge functions and content to edge devices. Edge devices use HyperText Transfer Protocol (HTTP) to execute serverless functions or otherwise retrieve data from edge nodes and/or microservers located in proximity to the HTTP client. The cloud platform locates the nearest edge node and/or microserver. Edge devices georoute HTTP requests to the nearest edge node and/or microserver. Serverless functions are implemented in secure, isolated environments using a blockchain. ## Claims ### Claim 1 A system for locating microserver nodes in proximity to edge devices using georouting, comprising: at least one cloud platform including a cloud platform domain name service (DNS), an edge platform DNS, at least one edge platform application programming interface (API), and at least one node database containing at least one edge platform router; at least one microserver node containing a current internet protocol (IP) address, an edge platform executor, and at least one hypertext transfer protocol (HTTP) server program; at least one edge device, wherein the at least one edge device contains an HTTP client; wherein the at least one edge device is in network communication with the at least one cloud platform and the at least one microserver node; wherein the at least one edge device is operable to transmit an initial HTTP request to the at least one cloud platform, wherein the initial HTTP request includes location information of the at least one edge device; wherein the at least one edge device is operable to receive an HTTP response from the at least one cloud platform; and wherein the at least one edge device is operable to transmit at least one additional HTTP request to a nearest microserver node based on the HTTP response from the at least one cloud platform. ### Claim 2 (depends on 1) The system of claim 1, wherein the location information is real-time location information or near real-time location information. ### Claim 3 (depends on 1) The system of claim 1, further comprising at least one edge platform ledger, wherein the at least one edge platform ledger is operable to validate and store a plurality of HTTP requests and interact with at least one edge platform smart contract. ### Claim 4 (depends on 3) The system of claim 3, wherein the at least one edge platform ledger is stored on a blockchain. ### Claim 5 (depends on 1) The system of claim 1, wherein the at least one cloud platform is private. ### Claim 6 (depends on 1) The system of claim 1, wherein the at least one edge device is operable to convert the location information to a geohash. ### Claim 7 (depends on 6) The system of claim 6, wherein the initial HTTP request includes a query for a geohashed hostname, and wherein the geohashed hostname includes the geohash. ### Claim 8 (depends on 1) The system of claim 1, wherein the at least one cloud platform forwards the initial HTTP request to the edge platform DNS. ### Claim 9 (depends on 1) The system of claim 1, wherein the nearest microserver node is determined using at least one shortest path algorithm. ### Claim 10 (depends on 1) The system of claim 1, wherein the location information is determined using a global positioning system (GPS), an edge device identifier (ID), a cell ID, a wireless local area network (WLAN), inertial sensors, a barometer, radio-frequency identification (RFID), near field communications (NFC), a personal area network (PAN), a wireless personal area network (WPAN), terrestrial transmitters, and/or Hyper Text Markup Language 5 (HTML5). ### Claim 11 (depends on 1) The system of claim 1, wherein the nearest microserver node is determined using machine learning. ### Claim 12 (depends on 1) The system of claim 1, wherein the HTTP response includes an address of the nearest microserver node with a pre-determined Time-to-Live (TTL). ### Claim 13 (depends on 1) The system of claim 1, wherein the at least one microserver node is operable to execute serverless functions. ### Claim 14 A system for locating microserver nodes in proximity to edge devices using georouting, comprising: at least one cloud platform including a cloud platform domain name service (DNS), an edge platform DNS, at least one edge platform application programming interface (API), and at least one node database containing at least one edge platform router; at least one microserver node containing a current internet protocol (IP) address, an edge platform executor, and at least one hypertext transfer protocol (HTTP) server program; at least one edge device, wherein the at least one edge device contains an HTTP client; wherein the at least one edge device is in network communication with the at least one cloud platform and the at least one microserver node; wherein the at least one edge device is operable to transmit an initial HTTP request to the at least one cloud platform, wherein the initial HTTP request includes location information of the at least one edge device; wherein the at least one edge platform API is operable to solve for a nearest microserver node; wherein the at least one edge device is operable to receive an HTTP response from the at least one cloud platform, wherein the HTTP response is an HTTP redirect; and wherein the at least one edge device is operable to transmit at least one additional HTTP request to the nearest microserver node based on the HTTP response from the at least one cloud platform. ### Claim 15 (depends on 14) The system of claim 14, wherein the HTTP redirect is to a microserver node hostname, and wherein the microserver node hostname includes a microserver node ID (nodeID) and an application ID (appID). ### Claim 16 (depends on 15) The system of claim 15, wherein the edge platform DNS is operable to resolve the microserver node hostname to the current IP address. ### Claim 17 A method for locating microserver nodes in proximity to edge devices using georouting, comprising: providing at least one cloud platform including a cloud platform domain name service (DNS), an edge platform DNS, at least one edge platform application programming interface (API), and at least one node database containing at least one edge platform router; providing at least one microserver node containing a current internet protocol (IP) address, an edge platform executor, and at least one hypertext transfer protocol (HTTP) server program; providing at least one edge device, wherein the at least one edge device contains an HTTP client, and wherein the at least one edge device is in network communication with the at least one cloud platform and the at least one microserver node; the at least one edge device transmitting an initial HTTP request to the at least one cloud platform, wherein the initial HTTP request includes location information of the at least one edge device; the at least one edge device receiving an HTTP response from the at least one cloud platform; and the at least one edge device transmitting at least one additional HTTP request to a nearest microserver node based on the HTTP response from the at least one cloud platform. ### Claim 18 (depends on 17) The method of claim 17, further comprising determining the nearest microserver node using at least one shortest path algorithm. ### Claim 19 (depends on 17) The method of claim 17, further comprising determining the nearest microserver node using machine learning. ### Claim 20 (depends on 17) The method of claim 17, wherein the HTTP response is an HTTP redirect.