# US 2022/0286495 A1 · Domain Name Query Method and Related Device

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

- Number: US 2022/0286495 A1
- Document ID: US20220286495A1
- Status: Published application
- Kind: A1
- Application number: 17/827,264
- Filed: 2022-05-27
- Published: 2022-09-08
- Earliest claimed: 2019-11-28
- Assignees: Huawei Cloud Computing Technologies Co., Ltd.
- Applicants: Huawei Cloud Computing Technologies Co., Ltd.
- Inventors: Jiankang Su
- Web page: https://patentgrep.com/patent/US20220286495A1

## CPC

- H04L 61/4511: using domain name system [DNS]
- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L 67/52: specially adapted for the location of the user terminal
- H04L 67/568: Storing data temporarily at an intermediate stage, e.g. caching
- H04L 67/62: Establishing a time schedule for servicing the requests
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A domain name query method and a related device. The method includes: An HTTPDNS server receives an HTTP request packet sent by a terminal device; the HTTPDNS server constructs a DNS query packet based on the HTTP request packet, and sends the DNS query packet to an authoritative DNS server; receives a DNS reply packet sent by the authoritative domain name server; and constructs an HTTP reply packet based on the DNS reply packet, and sends the HTTP reply packet to the terminal device, where the HTTP reply packet carries the IP address of the to-be-accessed site.

## Claims

### Claim 1

A domain name query method, comprising:
receiving, by a hypertext transfer protocol domain name system (HTTPDNS) server, a hypertext transfer protocol (HTTP) request packet sent by a terminal device, wherein the HTTP request packet carries a to-be-accessed domain name and scheduling information of the terminal device;
constructing, by the HTTPDNS server, a domain name system DNS query packet based on the HTTP request packet, and sending the DNS query packet to an authoritative domain name server, wherein the DNS query packet carries the to-be-accessed domain name and the scheduling information;
receiving, by the HTTPDNS server, a DNS reply packet sent by the authoritative domain name server, wherein the DNS reply packet carries an IP address of a to-be-accessed site, and the to-be-accessed site is an edge cache node that is selected by the authoritative domain name server from a plurality of sites of the to-be-accessed domain name and that corresponds to the scheduling information; and
constructing, by the HTTPDNS server, an HTTP reply packet based on the DNS reply packet, and sending the HTTP reply packet to the terminal device, wherein the HTTP reply packet carries the IP address of the to-be-accessed site.

### Claim 2 (depends on 1)

The method according to claim 1, wherein the constructing, by the HTTPDNS server, a DNS query packet based on the HTTP request packet comprises:
setting, by the HTTPDNS server, the scheduling information in a resource data field of the DNS query packet.

### Claim 3 (depends on 1)

The method according to claim 1, wherein the scheduling information of the HTTP request packet and the DNS query packet comprises a geographical location of the terminal device, and the to-be-accessed site is an edge cache node that is selected by the authoritative domain name server from the plurality of edge cache nodes of the to-be-accessed domain name and that corresponds to the geographical location of the terminal device.

### Claim 4 (depends on 3)

The method according to claim 3, wherein the scheduling information of the HTTP request packet and the DNS query packet further comprises information about an operator to which the terminal device belongs, and the to-be-accessed site is an edge cache node that is selected by the authoritative domain name server from the plurality of edge cache nodes of the to-be-accessed domain name and that is nearest to the geographical location among sites provided by the operator.

### Claim 5

A domain name query method, comprising:
receiving, by an authoritative domain name server, a DNS query packet sent by an HTTPDNS server, wherein the DNS query packet carries a to-be-accessed domain name and scheduling information;
selecting, by the authoritative domain name server based on the scheduling information, an edge cache node corresponding to the scheduling information from a plurality of edge cache nodes of the to-be-accessed domain name as a to-be-accessed site; and
sending, by the authoritative domain name server, a DNS reply packet to the HTTPDNS server, wherein the DNS replay packet carries an IP address of the to-be-accessed site.

### Claim 6 (depends on 5)

The method according to claim 5, wherein the scheduling information is set in a resource data field of the DNS query packet.

### Claim 7 (depends on 5)

The method according to claim 5, wherein the scheduling information comprises a geographical location of a terminal device; and
the authoritative domain name server selects an edge cache node nearest to the geographical location from the plurality of edge cache nodes of the to-be-accessed domain name as the to-be-accessed site based on the geographical location.

### Claim 8 (depends on 7)

The method according to claim 7, wherein the scheduling information further comprises information about an operator to which the terminal device belongs; and
the authoritative domain name server selects an edge cache node, nearest to the geographical location among edge cache nodes provided by the operator, from the plurality of edge cache nodes of the to-be-accessed domain name as the to-be-accessed site based on the geographical location and the information about the operator.

### Claim 9

An HTTPDNS server, comprising a processor, a memory, wherein the memory is configured to store an instruction, and the processor is configured to invoke the instruction in the memory to:
receive an HTTP request packet sent by a terminal device, wherein the HTTP request packet carries a to-be-accessed domain name and scheduling information of the terminal device;
construct a DNS query packet based on the HTTP request packet;
send the DNS query packet to an authoritative domain name server, wherein the DNS query packet carries the to-be-accessed domain name and the scheduling information;
receive a DNS reply packet sent by the authoritative domain name server, wherein the DNS reply packet carries an IP address of a to-be-accessed site, and the to-be-accessed site is an edge cache node that is selected by the authoritative domain name server from a plurality of edge cache nodes of the to-be-accessed domain name and that corresponds to the scheduling information;
construct an HTTP reply packet based on the DNS reply packet; and
send the HTTP reply packet to the terminal device, wherein the HTTP reply packet carries the IP address of the to-be-accessed site.

### Claim 10 (depends on 9)

The server according to claim 9, wherein the processor is configured to invoke the instruction in the memory to: set the scheduling information in a resource data field of the DNS query packet.

### Claim 11 (depends on 9)

The server according to claim 9, wherein the scheduling information of the HTTP request packet and the DNS query packet comprises a geographical location of the terminal device, and the to-be-accessed site is an edge cache node that is selected by the authoritative domain name server from the plurality of edge cache nodes of the to-be-accessed domain name and that corresponds to the geographical location of the terminal device.

### Claim 12 (depends on 11)

The server according to claim 11, wherein the scheduling information of the HTTP request packet and the DNS query packet further comprises information about an operator to which the terminal device belongs, and the to-be-accessed site is an edge cache node that is selected by the authoritative domain name server from the plurality of edge cache nodes of the to-be-accessed domain name and that is nearest to the geographical location among sites provided by the operator.

### Claim 13

An authoritative domain name server, comprising a processor, a memory, wherein the memory is configured to store an instruction, and the processor is configured to invoke the instruction in the memory to:
receive a DNS query packet sent by an HTTPDNS server, wherein the DNS query packet carries a to-be-accessed domain name and scheduling information;
select, based on the scheduling information, an edge cache node corresponding to the scheduling information from a plurality of edge cache nodes of the to-be-accessed domain name as a to-be-accessed site; and
send a DNS reply packet to the HTTPDNS server, wherein the DNS reply packet carries an IP address of the to-be-accessed site.

### Claim 14 (depends on 13)

The server according to claim 13, wherein the scheduling information is set in a resource data field of the DNS query packet.

### Claim 15 (depends on 13)

The server according to claim 13, wherein the scheduling information comprises a geographical location of a terminal device; and wherein the processor is configured to invoke the instruction in the memory to:
select an edge cache node nearest to the geographical location from the plurality of edge cache nodes of the to-be-accessed domain name as the to-be-accessed site based on the geographical location.

### Claim 16 (depends on 15)

The server according to claim 15, wherein the scheduling information further comprises information about an operator to which the terminal device belongs; and wherein the processor is configured to invoke the instruction in the memory to:
select an edge cache node, nearest to the geographical location among edge cache nodes provided by the operator, from the plurality of edge cache nodes of the to-be-accessed domain name as the to-be-accessed site based on the geographical location and the information about the operator.
