Method and system for ISP network performance monitoring and fault detection

Patent metadata

Field	Value
Publication number	US-9930098-B2
Application number	US-201514604461-A
Country	US
Kind code	B2
Filing date	Jan 23, 2015
Priority date	Jan 23, 2015
Publication date	Mar 27, 2018
Grant date	Mar 27, 2018

Abstract

A monitoring tool to facilitate real-time system performance monitoring, fault detection, fault isolation, and fault remediation verification, wherein the monitoring tool is connected to each of a plurality of gateways within a network, including a request reporter module configured to record results of URL access requests from one or more end users, a processing module configured to calculate a set of metrics based on success and failure rates for each of the URL access requests recorded by the request reporter and distinguish between failures related to the network and failures unrelated to the network, and a consolidator module configured to organize and present the set of metrics into a format useable for monitoring the network.

First claim

What is claimed is:

1. A monitoring tool connected to each of a plurality of gateways within a network, comprising:
one or more non-transitory computer-readable mediums having instructions stored thereon that, when executed by one or more processors cause the monitoring tool to:
record results of URL access requests from one or more end users;
calculate a set of metrics based on success and failure rates for each of the recorded results of the URL access requests;

distinguish between failures related to the network and failures unrelated to the network; and
consolidate and present the set of calculated metrics in a user-friendly format for monitoring network connections.

2. The monitoring tool of claim 1 , wherein the instructions, when executed by the one or more processors, further cause the monitoring tool to: distinguish between failures of one URL access request through one of the plurality of gateways and failures of the URL access request through the plurality of gateways.

3. The monitoring tool of claim 1 , wherein the instructions, when executed by the one or more processors, further cause the monitoring tool to: record which interconnect of a plurality of interconnects each of the plurality of gateways is connected to; and
distinguish between failures of one URL access request through one of the plurality of gateways connected to one of the plurality of interconnect carriers and failures of the URL access request through other gateways of the plurality of gateways connected to the same interconnect carrier.

4. The monitoring tool of claim 1 , wherein the instructions, when executed by the one or more processors, further cause the monitoring tool to: record which content distribution network (CDN) of a plurality of CDNs each of the plurality of gateways is connected to; and
distinguish between failures of one URL access request through one of the plurality of gateways served by a content distribution network (CDN) and failures of the URL access request through toe other gateways of the plurality of gateways served by the same CDN.

5. The monitoring tool of claim 1 , wherein the instructions, when executed by the one or more processors, further cause the monitoring tool to: record a software version of each of the plurality of gateways; and
distinguish between failures of one URL access request through one of the plurality of gateways with a first software version and failures of the URL access request through the plurality of gateways with a software version different from the first software version.

6. The monitoring tool of claim 1 , wherein the instructions, when executed by the one or more processors, further cause the monitoring tool to: record a software version of each of a plurality of user terminals; and
distinguish between failures of one URL access request through one of the plurality of user terminals with a first software version and failures of the URL access request through the plurality of user terminals with a software version different from the first software version.

7. The monitoring tool of claim 1 , wherein the instructions, when executed by the one or more processors, further cause the monitoring tool to: record a hostname for each URL access request and one or more IP addresses associated with the hostname; and
determine failures associated with each hostname through the plurality of gateways.

8. The monitoring tool of claim 1 , wherein the results of URL access requests includes a response time for each URL request from the one or more end users, wherein the response time is a time taken to complete retrieval for a URL request.

9. The monitoring tool of claim 8 , wherein the instructions, when executed by the one or more processors, further cause the monitoring tool to: calculate response time metrics for each URL request, wherein the response time metrics comprises one or more of the following:
average response time during a given time span;
maximum response time during a given time span;
minimum response time during a given time span;
median response time during a given time span;
response time standard deviation during a given time span;
response time variance during a given time span; and
response time distribution during a given time span.

10. The monitoring tool of claim 9 , wherein the instructions, when executed by the one or more processors, further cause the monitoring tool to: detect and trigger an alarm when one of the response time metrics for a URL request rises above or falls below a threshold value.

11. The monitoring tool of claim 10 , wherein the threshold value is derived from previous response time metrics.

12. The monitoring tool of claim 1 , wherein the instructions, when executed by the one or more processors, further cause the monitoring tool to: identify a set of most requested URLs.

13. The monitoring tool of claim 12 , wherein identifying the set of most requested URLs comprises determining results of prefetch operations performed by a web acceleration proxy, wherein the web acceleration proxy is included within each of the plurality of gateways or connected to each of the plurality of gateways.

14. The monitoring tool of claim 12 , wherein the instructions, when executed by the one or more processors, further cause the monitoring tool to: detect and trigger an alarm when a success rate for one URL of the set of most requested URLs rises above or falls below a threshold value.

15. The monitoring tool of claim 14 , wherein the instructions, when executed by the one or more processors, further cause the monitoring tool to: prioritize alarms such that alarms for URLs with a higher volume of requests are triggered first.

16. The monitoring tool of claim 14 , wherein the instructions, when executed by the one or more processors, further cause the monitoring tool to: prioritize alarms such that alarms for URLs with a higher frequency of requests are triggered first.

17. The monitoring tool of claim 12 , wherein the results of URL access requests includes a response time for each URL of the set of most requested URLs, wherein the response time is a time taken to complete retrieval for a URL request.

18. The monitoring tool of claim 17 , wherein the instructions, when executed by the one or more processors, further cause the monitoring tool to: calculate response time metrics for each URL of the set of most requested URLs, wherein the response time metrics comprises one or more of the following:
average response time during a given time span;
maximum response time during a given time span;
minimum response time during a given time span;
median response time during a given time span;
response time standard deviation during a given time span;
response time variance during a given time span; and
response time distribution during a given time span.

19. The monitoring tool of claim 18 , wherein the instructions, when executed by the one or more processors, further cause the monitoring tool to: detect and trigger an alarm when one of the response time metrics for a URL of the set of most requested URLs rises above or falls below a threshold value.

20. The monitoring tool of claim 19 , wherein the threshold value is derived from previous response time metrics.

Assignees

• Hughes Network Systems Llc

Inventors

• Choquette George
• Gupta Vivek
• Huang Hsiu-Chu

Classifications

• H04L43/0811 Primary

  by checking connectivity · CPC title

• H04L67/02 Primary

  based on web technology, e.g. hypertext transfer protocol [HTTP] · CPC title