# US 2021/0176301 A1 · Method and apparatus for multi-vendor gtm fabric

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

- Number: US 2021/0176301 A1
- Document ID: US20210176301A1
- Status: Published application
- Kind: A1
- Application number: 16/709,820
- Filed: 2019-12-10
- Published: 2021-06-10
- Earliest claimed: 2019-12-10
- Assignees: Oracle International Corporation
- Applicants: Oracle International Corporation
- Inventors: Rishi Mutnuru
- Web page: https://patentgrep.com/patent/US20210176301A1

## CPC

- H04L 67/101: based on network conditions
- H04L 43/0852: Delays
- H04L 43/0864: Round trip delays
- H04L 43/10: Active monitoring, e.g. heartbeat, ping or trace-route
- H04L 61/4511: using domain name system [DNS]
- H04L 61/4552: Lookup mechanisms between a plurality of directories; Synchronisation of directories, e.g. metadirectories
- H04L 2101/69: using geographic information, e.g. room number
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

An example method facilitates Global Traffic Management (GTM) and associated selective distribution of computing loads and/or network traffic among different geographically distributed data centers of a particular domain by allocating the servicing of request messages from Local Domain Name Servers (LDNSs) to data centers that are estimated to provide the quickest response times to the LDNSs. Estimates of path latencies or Round Trip Times (RTTs) between the LDNSs and the different distributed data centers are estimated using DNS reflection methodologies and are maintained in a database that may be accessed and collectively managed via the data centers, e.g., via use of a web service that fronts the database. Locations of the LDNSs approximate locations of client devices seeking access to the domain.

## Claims

### Claim 1

A non-transitory medium processor-readable medium including instructions executable by one or more processors, and when executed operable for:
estimating a first Round Trip Time (RTT) between a first data center and a Local Domain Name Server (LDNS) and a second Round Trip Time (RTT) between a second data center and the LDNS using a message-reflection method, resulting in a first RTT value and a second RTT value, respectively;
storing the first RTT value and the second RTT value in a database that is accessible to the first data center and the second data center, resulting in stored latency information;
receiving a first request message from the LDNS at the first data center or the second data center;
determining, based on the stored latency information, whether the first RTT or the second RTT is smaller; and
selecting the first data center or the second data center to process the first request message based on whether or not the first RTT or the second RTT is smaller, respectively.

### Claim 2 (depends on 1)

The non-transitory medium processor-readable medium of claim 1, further including using a web service or Application Programming Interface (API) to facilitate providing access to the database by the first data center and the second data center.

### Claim 3 (depends on 1)

The non-transitory medium processor-readable medium of claim 1, wherein the first request message specifies a CNAME (Canonical Name) of a domain name, wherein the domain name is specified by a client device in communication with the LDNS, and wherein the LDNS sends the first request message to the first data center or the second data center after a query specifying the domain name from the client device is received by the LDNS and after retrieval of the CNAME by the LDNS.

### Claim 4 (depends on 3)

The non-transitory medium processor-readable medium of claim 3, wherein retrieval of the CNAME by the LDNS includes first accessing a root DNS server to identify a Top-level DNS server (TDNS), and then using the TDNS to obtain the CNAME for use in constructing the first request message.

### Claim 5 (depends on 1)

The non-transitory medium processor-readable medium of claim 1, wherein estimating further includes:
determining whether or not one or more of the first RTT value or the second RTT value, as measured using the message-reflection method, preexists in the database; and
initializing the database with one or more first RTT estimates obtained using a passive method when the database has not yet been populated with the first RTT value or the second RTT value and when the database has not yet been populated with second RTT estimates obtained using an active method.

### Claim 6 (depends on 5)

The non-transitory medium processor-readable medium of claim 5, wherein the passive method includes providing the one or more first RTT estimates based on location information pertaining to the first data center, the second data center, and the LDNS.

### Claim 7 (depends on 5)

The non-transitory medium processor-readable medium of claim 5, wherein the active method includes selectively probing the LDNS using one or more pings or queries to obtain the second RTT estimates.

### Claim 8 (depends on 7)

The non-transitory medium processor-readable medium of claim 7, wherein the first RTT value and the second RTT value represent third RTT estimates obtained using the message-reflection method.

### Claim 9 (depends on 1)

The non-transitory medium processor-readable medium of claim 1, wherein the first data center includes a first Application Delivery Controller (ADC); wherein the second data center includes a second ADC; wherein the first ADC communicates with a first reflector Domain Name System (DNS) server and a first collector DNS server; wherein the second ADC communicates with a second reflector DNS server and a second collector DNS server; and wherein the first request message includes a DNS request message.

### Claim 10 (depends on 9)

The non-transitory medium processor-readable medium of claim 9, wherein the message-reflection method includes determining the first RTT value by:
receiving, at the first reflector DNS server at the first data center, the first request message;
augmenting the first request message with a first time stamp and an Internet Protocol (IP) address of the first collector DNS server, resulting in an adjusted first message;
sending the adjusted first message to the LDNS, whereby the adjusted first message represents a first reflected request message;
receiving at the first collector DNS server a first return message from the LDNS in response to receiving the first reflected request message;
comparing the first time stamp with a time at which the first collector DNS server receives the first return message; and
estimating the first RTT based on the comparing.

### Claim 11

A method for facilitating Global Traffic Management (GTM), the method comprising:
estimating a first Round Trip Time (RTT) between a first data center and a Local Domain Name Server (LDNS) and a second Round Trip Time (RTT) between a second data center and the LDNS using a message-reflection method, resulting in a first RTT value and a second RTT value, respectively;
storing the first RTT value and the second RTT value in a database that is accessible to the first data center and the second data center, resulting in stored latency information;
receiving a first request message from the LDNS at the first data center or the second data center;
determining, based on the stored latency information, whether the first RTT or the second RTT is smaller; and
selecting the first data center or the second data center to process the first request message based on whether or not the first RTT or the second RTT is smaller, respectively.

### Claim 12 (depends on 11)

The method of claim 11, further including using a web service or Application Programming Interface (API) to facilitate providing access to the database by the first data center and the second data center.

### Claim 13 (depends on 11)

The method of claim 11, wherein the first request message specifies a CNAME (Canonical Name) of a domain name, wherein the domain name is specified by a client device in communication with the LDNS, and wherein the LDNS sends the first request message to the first data center or the second data center after a query specifying the domain name from the client device is received by the LDNS and after retrieval of the CNAME by the LDNS.

### Claim 14 (depends on 13)

The method of claim 13, wherein retrieval of the CNAME by the LDNS includes first accessing a root DNS server to identify a Top-level DNS server (TDNS), and then using the TDNS to obtain the CNAME for use in constructing the first request message.

### Claim 15 (depends on 11)

The method of claim 11, wherein estimating further includes:
determining whether or not one or more of the first RTT value or the second RTT value, as measured using the message-reflection method, preexists in the database; and
initializing the database with one or more first RTT estimates obtained using a passive method when the database has not yet been populated with the first RTT value or the second RTT value and when the database has not yet been populated with second RTT estimates obtained using an active method.

### Claim 16 (depends on 15)

The method of claim 15, wherein the passive method includes providing the one or more first RTT estimates based on location information pertaining to the first data center, the second data center, and the LDNS.

### Claim 17 (depends on 15)

The method of claim 15, wherein the active method includes selectively probing the LDNS using one or more pings or queries to obtain the second RTT estimates.

### Claim 18 (depends on 17)

The method of claim 17, wherein the first RTT value and the second RTT value represent third RTT estimates obtained using the message-reflection method.

### Claim 19 (depends on 11)

The method of claim 11, wherein the first data center includes a first Application Delivery Controller (ADC); wherein the second data center includes a second ADC; wherein the first ADC communicates with a first reflector Domain Name System (DNS) server and a first collector DNS server; wherein the second ADC communicates with a second reflector DNS server and a second collector DNS server; and wherein the first request message includes a DNS request message, wherein the message-reflection method includes determining the first RTT value by:
receiving, at the first reflector DNS server at the first data center, the first request message;
augmenting the first request message with a first time stamp and an Internet Protocol (IP) address of the first collector DNS server, resulting in an adjusted first message;
sending the adjusted first message to the LDNS, whereby the adjusted first message represents a first reflected request message;
receiving at the first collector DNS server a first return message from the LDNS in response to receiving the first reflected request message;
comparing the first time stamp with a time at which the first collector DNS server receives the first return message; and
estimating the first RTT based on the comparing.

### Claim 20

An apparatus comprising:
one or more processors; and
logic encoded in one or more tangible media for execution by the one or more processors and when executed operable for:
estimating a first Round Trip Time (RTT) between a first data center and a Local Domain Name Server (LDNS) and a second Round Trip Time (RTT) between a second data center and the LDNS using a message-reflection method, resulting in a first RTT value and a second RTT value, respectively;
storing the first RTT value and the second RTT value in a database that is accessible to the first data center and the second data center, resulting in stored latency information;
receiving a first request message from the LDNS at the first data center or the second data center;
determining, based on the stored latency information, whether the first RTT or the second RTT is smaller; and
selecting the first data center or the second data center to process the first request message based on whether or not the first RTT or the second RTT is smaller, respectively.
