# US 11,443,007 B2 · System and method for managing network traffic routing

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

- Number: US 11,443,007 B2
- Document ID: US11443007B2
- Status: Granted
- Kind: B2
- Application number: 16/992,900
- Filed: 2020-08-13
- Published: 2020-11-26
- Granted: 2022-09-13
- Earliest claimed: 2006-03-16
- Assignees: eBay Inc.
- Applicants: eBay Inc.
- Inventors: Daniel L Pritchett; Ian Flint; Connie W. Yang
- Web page: https://patentgrep.com/patent/US11443007B2

## CPC

- G06F 16/9566: {URL specific, e.g. using aliases, detecting broken or misspelled links}
- H04L 67/1001: for accessing one among a plurality of replicated servers
- H04L 67/1021: based on client or server locations
- H04L 67/52: specially adapted for the location of the user terminal
- H04L 67/63: Routing a service request depending on the request content or context
- H04W 4/02: Services making use of location information
- H04L 61/30: Managing network names, e.g. use of aliases or nicknames (name-to-address mapping H04L61/45)
- H04L 61/35: {involving non-standard use of addresses for implementing network functionalities, e.g. coding subscription information within the address or functional addressing, i.e. assigning an address to a function}
- 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

A method and system receives at a server a search request and processes the search request to determine a context of the search request, then determines, based on the context, a network route to an application server having the closest geographic proximity, with respect to the server, to the most relevant database associated with the context.

## Claims

### Claim 1

A method comprising:
receiving a request from a user device, the request being associated with a location of the user device;
forwarding the request to a proxy;
analyzing the request to determine a context of the request;
identifying an application server to service the request based on a combination of the context and a geographic proximity of the application server to the location of the user device; and
in response to identifying the application server based on the context and the geographic proximity of the application server to the location of the user device, routing the request to the application server.

### Claim 2 (depends on 1)

The method of claim 1, wherein the request comprises a uniform resource locator (URL).

### Claim 3 (depends on 2)

The method of claim 2, wherein the analyzing comprises parsing the URL and the context used in identifying the application server comprises URL context.

### Claim 4 (depends on 1)

The method of claim 1, wherein the routing is based in part on a host name.

### Claim 5 (depends on 1)

The method of claim 1, wherein the identifying is based on a configuration file that indicates a destination for serving the request based on the context.

### Claim 6 (depends on 5)

The method of claim 5, wherein the configuration file includes routing rules indicating where to route the request based on context.

### Claim 7 (depends on 5)

The method of claim 5, further comprising generating the configuration information.

### Claim 8 (depends on 1)

The method of claim 1, wherein the application server serves a specific geographic location.

### Claim 9

A system comprising:
one or more hardware processors; and
a storage device storing instructions that, when executed by the one or more hardware processors, cause the one or more hardware processors to perform operations comprising:
receiving a request from a user device, the request being associated with a location of the user device;
forwarding the request to a proxy;
analyzing the request to determine a context of the request;
identifying an application server to service the request based on a combination of the context and a geographic proximity of the application server to the location of the user device; and
in response to identifying the application server based on the context and the geographic proximity of the application server to the location of the user device, routing the request to the application server.

### Claim 10 (depends on 9)

The system of claim 9, wherein the request comprises a uniform resource locator (URL).

### Claim 11 (depends on 10)

The system of claim 10, wherein the analyzing comprises parsing the URL and the context used in identifying the application server comprises URL context.

### Claim 12 (depends on 9)

The system of claim 9, wherein the routing is based in part on a host name.

### Claim 13 (depends on 9)

The system of claim 9, wherein the identifying is based on a configuration file that indicates a destination for serving the request based on the context.

### Claim 14 (depends on 13)

The system of claim 13, wherein the configuration file includes routing rules indicating where to route the request based on context.

### Claim 15 (depends on 13)

The system of claim 13, wherein the operations further comprise generating the configuration information.

### Claim 16 (depends on 9)

The system of claim 9, wherein the application server serves a specific geographic location.

### Claim 17

A non-transitory machine-readable medium storing instructions that, when executed by one or more processors of a machine, cause the machine to perform operations comprising:
receiving a request from a user device, the request being associated with a location of the user device;
forwarding the request to a proxy;
analyzing the request to determine a context of the request;
identifying an application server to service the request based on a combination of the context and a geographic proximity of the application server to the location of the user device; and
in response to identifying the application server based on the context and the geographic proximity of the application server to the location of the user device, routing the request to the application server.

### Claim 18 (depends on 17)

The non-transitory machine-readable medium of claim 17, wherein:
the request comprises a uniform resource locator (URL);
the analyzing comprises parsing the URL; and
the context comprises URL context.

### Claim 19 (depends on 17)

The non-transitory machine-readable medium of claim 17, wherein the identifying is based on a configuration file that indicates a destination for serving the request based on the context.

### Claim 20 (depends on 17)

The non-transitory machine-readable medium of claim 17, wherein the application server serves a specific geographic location.
