Network latency measurement and analysis system

• US 10,735,307 B1
• Filed: 01/10/2019
• Issued: 08/04/2020
• Est. Priority Date: 01/10/2019
• Status: Active Grant

• Current Assignee: eBay Inc.
• Original Assignee: eBay Inc.
• Inventors: Srinivasa Murthy, Ashok, Gurnani, Sunny Rameshkumar
• Primary Examiner(s): Butt, Walli Z
• Application Number:
  US16/244,363
• Publication Number:
  US 20200228437A1
• Time in Patent Office: 572 Days
• CPC Class Codes: H04L 41/0246 Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols
• CPC Class Codes: H04L 41/22 comprising specially adapted graphical user interfaces [GUI]
• CPC Class Codes: H04L 43/067 using time frame reporting
• CPC Class Codes: H04L 43/0852 Delays
• CPC Class Codes: H04L 45/121 by minimising delays
• CPC Class Codes: H04L 45/14 Routing performance; Theoretical aspects
• CPC Class Codes: H04L 45/22 Alternate routing
• CPC Class Codes: H04L 45/302 Route determination based on requested QoS

Abstract

Deploying a point of presence (PoP) changes traffic flow to a cloud service provider. To determine if the PoP improves the performance of a cloud service to a client, actual network latencies between the client and the cloud service are measured. In more complex scenarios, multiple PoPs are used. The client sends multiple requests for the same content to the cloud provider. The requests are sent via different routes. The cloud provider serves the requests and collates the latency information. Based on the latency information, a route for a future request is selected, resources are allocated, or a user interface is presented. The process of determining the latency for content delivered by different routes may be repeated for content of different sizes. A future request is routed along the network path that provides the lowest latency for the data being requested.

Claims

1. A method comprising:

sending, at a first time and by a client, a first request to a server via a first route over a network, the first request comprising a first identifier;

sending, at a second time and by the client, a second request to the server via a second route over the network, the second request comprising the first identifier;

receiving, at a third time and by the client, a first response to the first request, the first response comprising the first identifier;

receiving, at a fourth time and by the client, a second response to the second request, the second response comprising the first identifier;

based on the first identifier being in the first request and the first response, determining a first transit duration of the first route over the network using the third time and the first time;

based on the first identifier being in the second request and the second response, determining a second transit duration of the second route over the network using the fourth time and the second time; and

based on the first transit duration and the second transit duration, sending, by the client, a third request to the server via the first route over the network.

2. The method of claim 1, wherein:

the first request and the second request are for first data of a first type;

the third request is for second data of the first type;

the method further comprises;

sending, at a fifth time by the client, a fourth request for second data of a second type to the server via the first route over the network, the fourth request comprising a second identifier, the second type of data being different from the first type of data;

sending, at a sixth time by the client, a fifth request for the second data of the second type to the server via the second route over the network, the fifth request comprising the second identifier;

receiving, at a seventh time and by the client, a fourth response to the fourth request, the fourth response comprising the second identifier;

receiving, at an eighth time and by the client, a fifth response to the fifth request, the fifth response comprising the second identifier;

based on the second identifier being in the fourth request and the fourth response, determining a third transit duration of the first route over the network using the seventh time and the fifth time; and

based on the second identifier being in the fifth request and the fifth response, determining a fourth transit duration of the second route over the network using the eighth time and the sixth time; and

based on the third request being for the first type of data different from the second type of data, the sending of the third request via the first route is not based on the third transit duration and the fourth transit duration.

3. The method of claim 2, wherein the fourth transit duration is less than the first transit duration.

4. The method of claim 2, wherein the second data is at least twice as large as the first data.

5. The method of claim 2, further comprising:

sending, at a ninth time by the client, a sixth request for third data of a third type to the server via the first route over the network, the sixth request comprising a third identifier, the third type of data being different from the first type of data and the second type of data;

sending, at a tenth time by the client, a seventh request for the third data of the third type to the server via the second route over the network, the seventh request comprising the third identifier;

receiving, at an eleventh time by the client, a sixth response to the sixth request, the sixth response comprising the third identifier;

receiving, at a twelfth time by the client, a seventh response to the seventh request, the seventh response comprising the third identifier;

based on the third identifier being in the sixth request and the sixth response, determining a fifth transit duration of the first route over the network using the ninth time and the eleventh time; and

based on the third identifier being in the seventh request and the seventh response, determining a sixth transit duration of the second route over the network using the tenth time and the twelfth time;

wherein;

based on the third request being for the first type of data different from the third type of data, the sending of the third request via the first route is not based on the fifth transit duration and the sixth transit duration.

6. The method of claim 1, wherein sending the third request to the server via the first route comprises addressing the third request to a second server.

7. The method of claim 1, further comprising:

sending, at a fifth time by the client, a fourth request to the server via a third route over the network, the fourth request comprising a third identifier;

receiving, at a sixth time by the client, a fourth response to the fourth request, the fourth response comprising the third identifier; and

based on the third identifier being in the fourth request and the fourth response, determining a third transit duration of the third route over the network using the fifth time and the sixth time;

wherein;

the sending of the third request to the server via the first route over the network is further based on the third transit duration.

8. A method comprising:

sending a web page, the web page including a first page item with an identifier and a first network path and a second page item with the identifier and a second network path, wherein the web page includes an executable script, the executable script configured to calculate first performance data associated with the first page item and second performance data associated with the second page item;

receiving the first performance data associated with the first page item, the first performance data including a first time for delivery of the first page item via the first network path;

receiving the second performance data associated with the second page item, the second performance data including a second time for delivery of the second page item via the second network path; and

merging the first performance data and the second performance data into a merged record.

9. The method of claim 8, further comprising:

generating a user interface page to display the merged record; and

sending the user interface page.

10. The method of claim 9, wherein the user interface page identifies the first network path, the second network path, the first performance data, and the second performance data.

11. The method of claim 8, further comprising:

based on the merged record, causing a client device to access a third page item via the first network path.

12. The method of claim 8, wherein the first page item is the same size as the second page item.

13. The method of claim 8, wherein:

the web page further includes a third page item with a second identifier and the first network path and a fourth page item with the second identifier and the second network path;

the executable script is further configured to calculate third performance data associated with the third page item and fourth performance data associated with the fourth page item; and

the method further comprises;

receiving the third performance data associated with the third page item, the third performance data including a third time for delivery of the third page item via the first network path;

receiving the fourth performance data associated with the fourth page item, the fourth performance data including a fourth time for delivery of the fourth page item via the second network path; and

merging the third performance data and the fourth performance data into the merged record.

14. The method of claim 11, wherein the third page item and the first page item are different sizes.

15. A system comprising:

a memory that stores instructions; and

one or more processors configured by the instructions to perform operations comprising;

sending a web page, the web page including a first page item with an identifier and a first network path and a second page item with the identifier and a second network path, wherein the web page includes an executable script, the executable script configured to calculate first performance data associated with the first page item and second performance data associated with the second page item;

receiving the first performance data associated with the first page item, the first performance data including a first time for delivery of the first page item via the first network path;

receiving the second performance data associated with the second page item, the second performance data including a second time for delivery of the second page item via the second network path; and

merging the first performance data and the second performance data into a merged record.

16. The system of claim 15, wherein the operations further comprise:

generating a user interface page to display the merged record; and

sending the user interface page.

17. The system of claim 16, wherein the user interface page identifies the first network path, the second network path, the first performance data, and the second performance data.

18. The system of claim 15, wherein the operations further comprise:

based on the merged record, causing a client device to access a third page item via the first network path.

19. The system of claim 15, wherein the first page item is the same size as the second page item.

20. The system of claim 15, wherein:

the web page further includes a third page item with a second identifier and the first network path and a fourth page item with the second identifier and the second network path;

the executable script is further configured to calculate third performance data associated with the third page item and fourth performance data associated with the fourth page item; and

the operations further comprise;

receiving the third performance data associated with the third page item, the third performance data including a third time for delivery of the third page item via the first network path;

receiving the fourth performance data associated with the fourth page item, the fourth performance data including a fourth time for delivery of the fourth page item via the second network path; and

merging the third performance data and the fourth performance data into the merged record.