Method and system for isp network performance monitoring and fault detection

Patent metadata

Field	Value
Publication number	US-2016218942-A1
Application number	US-201514604461-A
Country	US
Kind code	A1
Filing date	Jan 23, 2015
Priority date	Jan 23, 2015
Publication date	Jul 28, 2016
Grant date	—

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:
a request reporter module communicatively coupled to each of the plurality of gateways and configured to record results of URL access requests from one or more end users; a processing module communicatively coupled to the request reporter module and 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 communicatively coupled to the processing module and configured to consolidate and present the set of metrics outputted by the processing module in a user-friendly format for monitoring network connections.

2 . The monitoring tool of claim 1 , wherein the processing module is further configured 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 request reporter module is further configured to record which interconnect of a plurality of interconnects each of the plurality of gateways is connected to; and
the processing module is further configured to 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 the other gateways of the plurality of gateways connected to the same interconnect carrier.

4 . The monitoring tool of claim 1 , wherein the request reporter module is further configured to record which content distribution network (CDN) of a plurality of CDNs each of the plurality of gateways is connected to; and
the processing module is further configured to 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 the other gateways of the plurality of gateways served by the same CDN.

5 . The monitoring tool of claim 1 , wherein the request reporter module is further configured to record a software version of each of the plurality of gateways; and
the processing module is further configured to 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 request reporter module is further configured to record a software version of each of the plurality of user terminals; and
the processing module is further configured to 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 request reporter module is further configured to record a hostname for each URL access request and one or more IP addresses associated with the hostname; and
the processing module is further configured to 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 the time taken to complete retrieval for a URL request.

9 . The monitoring tool of claim 8 , wherein the processing module is further configured 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; response time distribution during a given time span.

10 . The monitoring tool of claim 9 , wherein the processing module is further configured 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 processing module is further configured to identify a set of most requested URLs.

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

14 . The monitoring tool of claim 12 , wherein the processing module is further configured to detect and trigger an alarm when the 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 processing module is configured 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 processing module is configured 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 the time taken to complete retrieval for a URL request.

18 . The monitoring tool of claim 17 , wherein the processing module is further configured 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; response time distribution during a given time span.

19 . The monitoring tool of claim 18 , wherein the processing module is further configured 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.

21 . A method for real-time network performance monitoring, comprising:
recording information related to a plurality of URL access requests from a plurality of end users; determining a status of each URL request of the plurality of URL requests, wherein the status is either that a request was successful or failed; recording the status of each URL request of the plurality of URL requests; calculating a success rate and a failure rate of for each URL request of the plurality of URL requests; and i

Assignees

• Hughes Network Systems Llc

Inventors

• Choquette George
• Gupta Vivek
• Huang Hsiu-Chu

Classifications

• H04L67/02 Primary

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

• H04L43/0811 Primary

  by checking connectivity · CPC title

• H04L43/0823

  Errors, e.g. transmission errors · CPC title

• H04L43/062 Primary

  related to network traffic · CPC title