IP Library Granted Patent US 8,676,964
Granted Patent B2
US 8,676,964 · App. 12/266,105 · Granted Mar 18, 2014

Detecting outliers in network traffic time series

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 8,676,964
App. No.
12/266,105
Granted
Mar 18, 2014
Kind
B2
Abstract

According to an aspect of the invention, a system and method is configured to detect time series outliers in network traffic.

Claims (61)

1. A computer program product residing on a non-transitory computer readable medium for intrusion detection, the computer program product comprising instructions for causing a processor to:

for each of a plurality of multiple different network traffic metrics,

generate a forecast of network traffic using a model, the forecast being based on previously observed network traffic;

generate a prediction interval that extends above and below the forecast of the network traffic, the prediction interval being based on previously observed deviations from predicted network traffic;

compare observed network traffic to the prediction interval;

identify an outlier for the metric if the observed network traffic is outside of the prediction interval during a time period;

compute a count of outliers for the metric that are identified during the time period; and

identify an anomaly in network traffic for the metric only when the computed count of outliers identified for the metric during the time period is greater than or equal to two and the computed count of outliers identified for the metric during the time period exceeds an anomaly threshold for the metric that is greater than or equal to one; and

merge anomalies for each of the multiple different network traffic metrics to identify a single event.

2. The computer program product of claim 1 , wherein the computer program product further comprises instructions for causing the processor to provide information about the network traffic at the time of the event to a user.

3. The computer program product of claim 1 , wherein the computer program product further comprises instructions for causing the processor to:

generate the forecast using a model that includes at least a first and a second seasonality, the forecast being based on previously observed network traffic at first and second time periods associated with the first and the second seasonality.

4. The computer program product of claim 3 , wherein the computer program product further comprises instructions for causing the processor to generate the forecast using a Holt-Winters model having daily and weekly seasonality.

5. The computer program product of claim 3 , wherein:

the first seasonality comprises a weekly seasonality;

the first time period comprises a time period one week prior to the time of the observed network traffic;

the second seasonality comprises a daily seasonality; and

the second time period comprises a time period one day prior to the time of the observed network traffic.

6. The computer program product of claim 4 , wherein the computer program product further comprises instructions for causing the processor to:

initialize the model used to generate the forecast based on at least two weeks of network traffic data; and

initialize errors used to generate the prediction interval using at least one week of network traffic data.

7. The computer program product of claim 4 , wherein the instructions for causing the processor to generate the prediction interval comprise instructions for causing the processor to define a distribution identifying the variance of errors and use the variance to determine the expected variance about a the forecast of network traffic.

8. The computer program product of claim 7 , wherein the forecast and the prediction interval are based on network data associated with a sliding window of prior network data.

9. An anomaly detection system, comprising:

a computing device configured to:

for each of a plurality of multiple different network traffic metrics,

generate a forecast of network traffic using a model, the forecast being based on previously observed network traffic;

generate a prediction interval that extends above and below the forecast of the network traffic, the prediction interval being based on previously observed deviations from predicted network traffic;

compare observed network traffic to the prediction interval;

identify an outlier for the metric if the observed network traffic is outside of the prediction interval during a time period;

compute a count of outliers for the metric that are identified during the time period; and

identify an anomaly in network traffic for the metric only when the computed count of outliers identified for the metric during the time period is greater than or equal to two and the computed count of outliers identified for the metric during the time period exceeds an anomaly threshold for the metric that is greater than or equal to one; and

merge identified anomalies for each of the multiple different network traffic metrics to identify a single event.

10. The anomaly detection system of claim 9 , wherein the computer device is further configured to:

generate the forecast using a model that includes at least a first and a second seasonality, the forecast being based on previously observed network traffic at first and second time periods associated with the first and the second seasonality.

11. The anomaly detection system of claim 10 , wherein the computing device is further configured to generate the forecast using a Holt-Winters model having daily and weekly seasonality.

12. The anomaly detection system of claim 10 , wherein:

the first seasonality comprises a weekly seasonality;

the first time period comprises a time period one week prior to the time of the observed network traffic;

the second seasonality comprises a daily seasonality; and

the second time period comprises a time period one day prior to the time of the observed network traffic.

13. The anomaly detection system of claim 11 , wherein the computing device is further configured to:

initialize the model used to generate the forecast based on at least two weeks of network traffic data; and

initialize errors used to generate the prediction interval using at least one week of network traffic data.

14. The anomaly detection system of claim 11 , wherein the computing device is further configured to define a distribution identifying the variance of errors and use the variance to determine the expected variance about a the forecast of network traffic.

15. A computer implemented method comprising:

for each of a plurality of multiple different network traffic metrics,

generating a forecast of network traffic using a model, the forecast being based on previously observed network traffic;

generating a prediction interval that extends above and below the forecast of the network traffic, the prediction interval being based on previously observed deviations from predicted network traffic;

comparing observed network traffic to the prediction interval;

identifying, by computer, an outlier for the metric if the observed network traffic is outside of the prediction interval during a time period;

computing a count of outliers for the metric that are identified during the time period; and

identifying an anomaly for the metric in network traffic only when the computed count of outliers for the metric identified during the time period is greater than or equal to two and the computed count of outliers identified for the metric during the time period exceeds an anomaly threshold for the metric that is greater than or equal to one; and

merging identified anomalies for each of the multiple different network traffic metrics to identify a single event.

16. The computer implemented method of claim 15 , the method further comprising:

generating the forecast using a model that includes at least a first and a second seasonality, the forecast being based on previously observed network traffic at first and second time periods associated with the first and the second seasonality.

17. The computer implemented method of claim 16 , further comprising generating the forecast using a Holt-Winters model having daily and weekly seasonality.

18. The computer implemented method of claim 17 , further comprising

initializing the model used to generate the forecast based on at least two weeks of network traffic data; and

initializing errors used to generate the prediction interval using at least one week of network traffic data.

19. The computer implemented method of claim 17 , further comprising defining a distribution identifying the variance of errors and use the variance to determine the expected variance about the forecast of network traffic.

Assignments (18)
RELEASE OF SECURITY INTEREST Recorded Aug 11, 2023
From: ALTER DOMUS (US) LLC, AS COLLATERAL AGENT
To: RIVERBED TECHNOLOGY, INC.; ATERNITY LLC; RIVERBED HOLDINGS, INC.
Reel/Frame 064673/0739 →
CHANGE OF NAME Recorded Feb 18, 2022
From: RIVERBED TECHNOLOGY, INC.
To: RIVERBED TECHNOLOGY LLC
Reel/Frame 059232/0551 →
TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS Recorded Dec 27, 2021
From: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS U.S. COLLATERAL AGENT
To: RIVERBED TECHNOLOGY, INC.; ATERNITY LLC
Reel/Frame 058593/0169 →
TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS Recorded Dec 27, 2021
From: MORGAN STANLEY SENIOR FUNDING, INC., AS COLLATERAL AGENT
To: RIVERBED TECHNOLOGY, INC.; ATERNITY LLC
Reel/Frame 058593/0046 →
TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS Recorded Dec 27, 2021
From: ALTER DOMUS (US) LLC, AS COLLATERAL AGENT
To: RIVERBED TECHNOLOGY, INC.; ATERNITY LLC
Reel/Frame 058593/0108 →
SECURITY INTEREST Recorded Dec 10, 2021
From: RIVERBED TECHNOLOGY LLC (FORMERLY RIVERBED TECHNOLOGY, INC.); ATERNITY LLC
To: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS U.S. COLLATERAL AGENT
Reel/Frame 058486/0216 →
PATENT SECURITY AGREEMENT Recorded Oct 27, 2021
From: RIVERBED TECHNOLOGY, INC.; ATERNITY LLC
To: WILMINGTON TRUST, NATIONAL ASSOCIATION
Reel/Frame 057943/0386 →
PATENT SECURITY AGREEMENT SUPPLEMENT - FIRST LIEN Recorded Oct 14, 2021
From: RIVERBED HOLDINGS, INC.; RIVERBED TECHNOLOGY, INC.; ATERNITY LLC
To: MORGAN STANLEY SENIOR FUNDING, INC., AS COLLATERAL AGENT
Reel/Frame 057810/0502 →
PATENT SECURITY AGREEMENT SUPPLEMENT - SECOND LIEN Recorded Oct 14, 2021
From: RIVERBED HOLDINGS, INC.; RIVERBED TECHNOLOGY, INC.; ATERNITY LLC
To: ALTER DOMUS (US) LLC, AS COLLATERAL AGENT
Reel/Frame 057810/0559 →
RELEASE OF SECURITY INTEREST IN PATENTS RECORED AT REEL 056397, FRAME 0750 Recorded Oct 13, 2021
From: MACQUARIE CAPITAL FUNDING LLC
To: RIVERBED HOLDINGS, INC.; RIVERBED TECHNOLOGY, INC.; ATERNITY LLC
Reel/Frame 057983/0356 →
SECURITY INTEREST Recorded May 26, 2021
From: RIVERBED HOLDINGS, INC.; RIVERBED TECHNOLOGY, INC.; ATERNITY LLC
To: MACQUARIE CAPITAL FUNDING LLC
Reel/Frame 056397/0750 →
PATENT SECURITY AGREEMENT Recorded Mar 5, 2021
From: RIVERBED TECHNOLOGY, INC.
To: ALTER DOMUS (US) LLC, AS COLLATERAL AGENT
Reel/Frame 055514/0249 →
CORRECTIVE ASSIGNMENT TO CORRECT THE CONVEYING PARTY NAME PREVIOUSLY RECORDED ON REEL 035521 FRAME 0069. ASSIGNOR(S) HEREBY CONFIRMS THE RELEASE OF SECURITY INTEREST IN PATENTS. Recorded Jun 2, 2015
From: JPMORGAN CHASE BANK, N.A.
To: RIVERBED TECHNOLOGY, INC.
Reel/Frame 035807/0680 →
SECURITY INTEREST Recorded May 1, 2015
From: RIVERBED TECHNOLOGY, INC.
To: MORGAN STANLEY SENIOR FUNDING, INC., AS COLLATERAL AGENT
Reel/Frame 035561/0363 →
RELEASE OF SECURITY INTEREST IN PATENTS Recorded Apr 28, 2015
From: BARCLAYS BANK PLC
To: RIVERBED TECHNOLOGY, INC.
Reel/Frame 035521/0069 →
PATENT SECURITY AGREEMENT Recorded Dec 27, 2013
From: RIVERBED TECHNOLOGY, INC.
To: JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 032421/0162 →
RELEASE OF PATENT SECURITY INTEREST Recorded Dec 26, 2013
From: MORGAN STANLEY & CO. LLC, AS COLLATERAL AGENT
To: RIVERBED TECHNOLOGY, INC.
Reel/Frame 032113/0425 →
SECURITY AGREEMENT Recorded Dec 20, 2012
From: RIVERBED TECHNOLOGY, INC.; OPNET TECHNOLOGIES, INC.
To: MORGAN STANLEY & CO. LLC
Reel/Frame 029646/0060 →