# US 11,122,131 B1 · Edge cloud resource location using enhanced DNS service

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 11,122,131 B1
- Document ID: US11122131B1
- Status: Granted
- Kind: B1
- Application number: 16/951,313
- Filed: 2020-11-18
- Granted: 2021-09-14
- Earliest claimed: 2020-11-18
- Assignees: AT&T Intellectual Property I, L.P.
- Applicants: AT&T Intellectual Property I, L.P.
- Inventors: Aleksandr Zelezniak; Abhigyan; Kaustubh Joshi; Oliver Spatscheck
- Web page: https://patentgrep.com/patent/US11122131B1

## CPC

- H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46)
- H04L 45/745: Address table lookup; Address filtering
- H04L 61/4511: using domain name system [DNS]
- H04L 67/101: based on network conditions
- H04L 67/1014: based on the content of a request
- H04L 67/51: Discovery or management thereof, e.g. service location protocol [SLP] or web services
- H04L 67/52: specially adapted for the location of the user terminal
- H04L 67/56: Provisioning of proxy services (store-and-forward switching systems in data switching networks H04L12/54)
- H04L 67/61: taking into account QoS or priority requirements
- H04L 69/22: Parsing or analysis of headers
- H04W 4/08: User group management
- H04L 61/4541: Directories for service discovery
- 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

Methods, systems, and apparatuses, among other things, may direct client requests to an Edge Cloud location satisfying application requirements associated with the request. Moreover, a domain name service (DNS) query may be received, one or more requests associated with DNS query may be determined, a server may be identified based on the one or more requests, and the DNS query may be redirected to the identified server.

## Claims

### Claim 1

A network device comprising:
a processor; and
a memory coupled with the processor, the memory comprising executable instructions that when executed by the processor cause the processor to effectuate operations comprising:
receiving a request comprising domain name service (DNS) query from a client device and one or more thresholds;
based on the DNS query, determining a plurality of DNS records pointing to a plurality of internet protocol (IP) addresses associated with a respective server of a plurality of servers, wherein the IP addresses are different, and wherein the plurality of servers are different;
identifying a location of the client device;
identifying respective latency for each path between the client device and each of the plurality of servers;
determining a first path to a first server of the plurality of servers meets the one or more thresholds; and
based on determining that the first server meets the one or more thresholds, responding to the request with a first IP address that corresponds to the first server identified in the DNS records.

### Claim 2 (depends on 1)

The network device of claim 1, wherein the request includes balancing a load of a network.

### Claim 3 (depends on 1)

The network device of claim 1, wherein the one or more thresholds include a minimum latency threshold.

### Claim 4 (depends on 1)

The network device of claim 1, the operations further comprising identifying a slice of a network based on the one or more thresholds, wherein the server is identified based on the slice of the network.

### Claim 5 (depends on 1)

The network device of claim 1, the operations further comprising identifying a user equipment (UE) group associated with the device.

### Claim 6 (depends on 5)

The network device of claim 5, the operations further comprising identifying access network metadata associated with the DNS query, wherein the UE group is identified based on the access network metadata.

### Claim 7 (depends on 1)

The network device of claim 1, the operations further comprising:
identifying packet headers associated with the DNS query; and
identifying a UE group based on the packet headers.

### Claim 8 (depends on 1)

The network device of claim 1, the operations further comprising identifying a service group associated with the DNS query, wherein the request is based on the identified service group.

### Claim 9 (depends on 1)

The network device of claim 1, the operations further comprising determining one or more constraints associated with the DNS query, wherein the one or more thresholds are based on the determined one or more constraints.

### Claim 10

A system comprising:
one or more processors; and
memory including instructions that, when executed by the one or more processors, cause the system to:
receive a request comprising domain name service (DNS) query from a client device and one or more thresholds;
based on the DNS query, determine a plurality of DNS records pointing to a plurality of internet protocol (IP) addresses associated with a respective server of a plurality of servers, wherein the IP addresses are different, and wherein the plurality of servers are different;
identify a location of the client device;
identify respective latency for each path between the client device and each of the plurality of servers;
determine a first path to a first server of the plurality of servers meets the one or more thresholds; and
based on determining that the first server meets the one or more thresholds, respond to the request with a first IP address that corresponds to the first server identified in the DNS records.

### Claim 11 (depends on 10)

The system of claim 10, wherein the one or more thresholds include a minimum latency threshold.

### Claim 12 (depends on 10)

The system of claim 10, wherein the instructions are further configured to cause the system to identify a slice of a network based on the one or more thresholds, wherein the server is identified based on the slice of the network.

### Claim 13 (depends on 10)

The system of claim 10, wherein the instructions are further configured to cause the system to identify a user equipment (UE) group associated with the device.

### Claim 14 (depends on 13)

The system of claim 13, wherein the instructions are further configured to cause the system to identify packet headers associated with the DNS query, wherein the UE group is identified based on the packet headers.

### Claim 15 (depends on 13)

The system of claim 13, wherein the instructions are further configured to cause the system to identify access network metadata associated with the DNS query, wherein the UE group is identified based on the access network metadata.

### Claim 16 (depends on 10)

The system of claim 10, wherein the instructions are further configured to cause the system to identify a service group associated with the DNS query, wherein the request is based on the identified service group.

### Claim 17 (depends on 10)

The system of claim 10, wherein the instructions are further configured to cause the system to determine one or more constraints associated with the DNS query, wherein the one or more thresholds are based on the determined one or more constraints.

### Claim 18

A computer program product comprising:
a computer-readable storage medium; and
instructions stored on the computer-readable storage medium that, when executed by a processor, causes the processor to:
receive a request comprising domain name service (DNS) query from a client device and one or more thresholds;
based on the DNS query, determine a plurality of DNS records pointing to a plurality of internet protocol (IP) addresses associated with a respective server of a plurality of servers, wherein the IP addresses are different, and wherein the plurality of servers are different;
identify a location of the client device;
identify respective latency for each path between the client device and each of the plurality of servers;
determine a first path to a first server of the plurality of servers meets the one or more thresholds; and
based on determining that the first server meets the one or more thresholds, respond to the request with a first IP address that corresponds to the first server identified in the DNS records.

### Claim 19 (depends on 18)

The computer program product of claim 18, wherein the one or more thresholds include a minimum latency threshold.