# US 2008/0189225 A1 · Method and System for Predicting Causes of Network Service Outages Using Time Domain Correlation

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

- Number: US 2008/0189225 A1
- Document ID: US20080189225A1
- Status: Published application
- Kind: A1
- Application number: 12/054,132
- Filed: 2008-03-24
- Published: 2008-08-07
- Earliest claimed: 2000-11-28
- Inventors: David Herring; John Carrol; Rehan O'Grady; Neil Coleman; Felix Marks
- Web page: https://patentgrep.com/patent/US20080189225A1

## CPC

- G06Q 30/0283: Price estimation or determination
- H04L 41/064: {involving time analysis}
- H04L 41/5025: by proactively reacting to service quality change, e.g. by reconfiguration after service quality degradation or upgrade
- H04L 43/00: Arrangements for monitoring or testing data switching networks
- H04L 43/10: Active monitoring, e.g. heartbeat, ping or trace-route
- H04L 41/20: {Network management software packages}
- H04L 41/5003: Managing SLA; Interaction between SLA and QoS
- H04L 43/0817: by checking functioning
- H04L 43/106: using time related information in packets, e.g. by adding timestamps
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Methods and systems are described for predicting the likely causes of service outages using only time information, and for predicting and the likely costs of service outages. The likely causes are found by defining a narrow likely cause window around an outage based on service quality and/or service usage data, and correlating service events to the likely cause window in the time domain to find a probability distribution for the events. The likely costs are found by measuring usage loss and duration for a given point during an outage and using cost component functions of the time and usage to extrapolate over the outage. These cause and cost predictions supply service administrators with tools for making more informed decisions about allocation of resources in preventing and correcting service outages.

## Claims

### Claim 1

A method for quantifying the effect of an outage in a service over a first period of time, the method comprising:
measuring usage of the service over time;
defining a cost of outage time window comprising the first time period and a second time period following the first time period; and
computing a cost of outage as the difference between the measured service usage during the cost of outage time window with service usage measured during a comparison window, the comparison window being substantially equal in time to that of the cost of outage time window and reflecting a similar period of service activity as that of the cost of outage time window without having a service outage.

### Claim 2 (depends on 1)

The method of claim 1, comprising determining the second period of time to be a time in which the measured service usage returns to within a given percentage of a normal service usage.

### Claim 3 (depends on 1)

The method of claim 1, comprising determining the second period of time to be the shorter of (1) a time in which the measured service usage returns to within a given percentage of a normal service usage and (2) a maximum time period.

### Claim 4 (depends on 1)

The method of claim 1, wherein computing the cost of outage comprises computing the difference in units of service usage.

### Claim 5 (depends on 4)

The method of claim 4, wherein the service is a communication service conveying a plurality of messages, the method comprising computing the cost of outage in numbers of messages conveyed.

### Claim 6 (depends on 4)

The method of claim 4, wherein the service is a network server providing data items in response to requests therefor, the method comprising computing the cost of outage in numbers of requests received or data items provided by a server on the network.

### Claim 7 (depends on 4)

The method of claim 4, comprising converting the computed units of cost of service outage to a monetary value.

### Claim 8 (depends on 7)

The method of claim 7, wherein converting the computed units of cost of service outage comprises multiplying the units of cost of service outage by a first monetary value per unit of usage.

### Claim 9 (depends on 1)

The method of claim 1, comprising comparing the cost of outage to a second cost of outage value for a different service and prioritizing the outages based on the compared costs.

### Claim 10 (depends on 1)

The method of claim 1, comprising computing the difference between the monitored service usage following the cost of outage time window and a normal service usage level to thereby measure a long term effect of the service outage.

### Claim 11

A method for quantifying the effect of an outage in a service, the method comprising:
measuring usage amounts of the service during a period of the service outage and a second period following the service outage;
comparing the measured usage amounts to normal usage amounts measured under similar service conditions for a similar period of time where no service outage occurs; and
determining a level of loss of service due to the service outage based on the comparison.

### Claim 12 (depends on 11)

The method of claim 11, comprising defining the second period as the shorter of a time period in which measured service usage amounts return to within a given range of normal usage amounts and a predefined maximum time period.

### Claim 13 (depends on 11)

The method of claim 11, wherein measuring service usage amounts comprises measuring service usage amounts in terms of units of service usage.

### Claim 14 (depends on 13)

The method of claim 13, wherein the service is a communication service conveying a plurality of messages, comprising measuring service usage amounts in terms of number of messages conveyed by the system.

### Claim 15 (depends on 13)

The method of claim 13, wherein the service is a network server providing data items in response to requests therefor, comprising measuring service usage amounts in terms of numbers of requests received or data items provided by a server on the network.

### Claim 16 (depends on 11)

The method of claim 11, wherein determining the level of service loss comprises determining that substantially no loss of service occurred due to the outage based on the measured service usage amounts and normal service usage amounts being substantially equal.

### Claim 17 (depends on 11)

The method of claim 11, comprising:
measuring service usage amounts during a third period following the second period;
comparing the measured third period service usage amounts to normal usage amounts measured under similar service conditions for a similar period of time; and
determining a long term effect on the service due to the service outage based on the comparison.

### Claim 18

A computer readable medium storing program code which, when executed, causes a computer to perform a method for quantifying the effect of an outage in a service over a first period of time, the method comprising:
measuring service usage over time;
defining a cost of outage time window comprising the first time period and a second time period; and
computing a cost of outage as the difference between the measured level of service usage during the cost of outage time window with a level of usage in a comparison window, the comparison window being substantially equal in time to the cost of outage time window and reflecting a similar period of service activity as the cost of outage time window without having a service outage.

### Claim 19

A method for predicting a cost of an outage of a service, the method comprising:
measuring time duration for and service usage during the outage;
comparing the measured usage amounts to normal usage amounts measured under similar service conditions for a similar period of time where no service outage occurs, to thereby determine a usage loss amount; and
computing a predicted cost of the outage based at least upon a cost component, the cost component comprising a function of the measured time of the outage and measured usage loss amount.

### Claim 20 (depends on 19)

The method of claim 19, comprising measuring service usage on an ongoing basis and detecting the onset of the service outage using the measured service usage.

### Claim 21 (depends on 20)

The method of claim 20, wherein detecting the onset of the service outage comprises detecting a step change in service usage.

### Claim 22 (depends on 19)

The method of claim 19, comprising monitoring quality of the service and detecting the onset of a service outage based upon the service quality.

### Claim 23 (depends on 22)

The method of claim 22, wherein monitoring service quality comprises monitoring service quality through periodic polling of the service quality, and wherein detecting the onset of a service outage comprises detecting the outage onset as bounded by a polled point of a first, working state and a polled point of a second, non-working state.

### Claim 24 (depends on 19)

The method of claim 19, wherein computing the predicted cost of the outage comprises using a service demand cost component representing an affect on service usage based upon the duration of an outage.

### Claim 25 (depends on 24)

The method of claim 24, wherein using the service demand cost component comprises multiplying the measured usage loss by a usage loss curve which is a function of time duration of an outage and represents a predicted percentage usage due to an outage based on time duration of the outage.

### Claim 26 (depends on 25)

The method of claim 25, comprising generating the usage loss curve using historical data derived from prior service outages.

### Claim 27 (depends on 19)

The method of claim 19, wherein computing the predicted cost of the outage comprises using a customer retention cost component representing a number or percentage of customers lost due to the outage.

### Claim 28 (depends on 19)

The method of claim 19, wherein computing the predicted cost of the outage comprises using an agreement penalty component representing penalties arising under one or more service agreements due to a service outage.

### Claim 29 (depends on 19)

The method of claim 19, wherein computing the predicted cost of the outage comprises computing the cost in units of service usage.

### Claim 30 (depends on 29)

The method of claim 29, comprising converting the computed units of predicted cost to a monetary value by multiplying the units of predicted cost by a first monetary value per unit of usage.

### Claim 31 (depends on 19)

The method of claim 19, comprising comparing the predicted cost of service outage to a second predicted cost of outage value for a different service and prioritizing the outages based on the compared costs.

### Claim 32

A network monitoring system comprising:
a usage meter for measuring usage of a service on the network;
an event detector for detecting network events and times at which the network events occur;
a probable cause engine, coupled to receive data from the usage meter and the event detector, for determining which of the network events detected by the event detector is the most likely cause of a service outage based at least in part of the relations of the detected network event times to a service change time window, the service change time window encompassing at least part of an occurrence of the service outage in the network; and
a costing engine, coupled to receive data from the usage meter, for predicting the cost of the service outage.

### Claim 33

Computer readable media comprising program code that, when executed by a programmable microprocessor, causes the programmable microprocessor to execute a method for quantifying the effect of an outage in a service, the method comprising:
measuring usage amount of the service during a period of the service outage and a second period following the service outage;
comparing the measured usage amounts to normal usage amounts measured under similar service conditions for a similar period of time where no service outage occurs; and
determining a level of loss of service due to the service outage based on the comparison.

### Claim 34 (depends on 33)

The computer readable media of claim 33 comprising program code that, when executed by a programmable microprocessor, causes the programmable microprocessor to execute a method for quantifying the effect of an outage in a service, the method comprising defining the second period as the shorter of a time period in which measured service usage amounts return to within a given range of normal usage amounts and a predefined maximum time period.

### Claim 35 (depends on 33)

The computer readable media of claim 33 comprising program code that, when executed by a programmable microprocessor, causes the programmable microprocessor to execute a method for quantifying the effect of an outage in a service, wherein measuring service usage amounts comprises measuring service usage amounts in terms of units of service usage.

### Claim 36 (depends on 35)

The computer readable media of claim 35 comprising program code that, when executed by a programmable microprocessor, causes the programmable microprocessor to execute a method for quantifying the effect of an outage in a service, wherein the service is a communications service conveying a plurality of messages, comprising measuring service usage amounts in terms of number of messages conveyed by the system.

### Claim 37 (depends on 35)

The computer readable media of claim 35 comprising program code that, when executed by a programmable microprocessor, causes the programmable microprocessor to execute a method for quantifying the effect of an outage in a service, wherein the service is a network server providing data items in response to requests therefore, comprising measuring service usage amounts in terms of number of requests received or data items provided by a server on the network.

### Claim 38 (depends on 33)

The computer readable media of claim 33 comprising program code that, when executed by a programmable microprocessor, causes the programmable microprocessor to execute a method for quantifying the effect of an outage in a service, wherein determining the level of service loss comprises determining that substantially no loss of service occurred due to the outage based on the measured service usage amounts and normal service usage amounts being substantially equal.

### Claim 39 (depends on 33)

The computer readable media of claim 33 comprising program code that, when executed by a programmable microprocessor, causes the programmable microprocessor to execute a method for quantifying the effect of an outage in a service, the method comprising:
measuring service usage amounts during a third period following the second period;
comparing the measured third period service usage amounts to normal usage amounts measured under similar conditions for a similar period of time; and
determining a long term effect on the service due to the service outage based on the comparison.

### Claim 40

Computer readable media comprising program code that, when executed by a programmable microprocessor, causes the programmable microprocessor to execute a method for predicting a cost of an outage of a service, the method comprising:
measuring time duration for and service usage during the outage;
comparing the measured usage amounts to normal usage amounts measured under similar service conditions for s similar period of time where no service outage occurs, to thereby determine a usage loss amount; and
computing a predicted cost of the outage based at least upon a cost component. the cost component comprising a function of the measured time of the outage and measured usage loss amount.
