NETWORK SERVICE FUNCTIONALITY MONITOR AND CONTROLLER

• US 20130339515A1
• Filed: 06/13/2012
• Published: 12/19/2013
• Est. Priority Date: 06/13/2012
• Status: Abandoned Application

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Radhakrishnan, Rajesh
• Application Number:
  US13/495,640
• Publication Number:
  US 20130339515A1
• Time in Patent Office: Days
• US Class Current: 709/224
• CPC Class Codes: H04L 41/064 involving time analysis
• CPC Class Codes: H04L 41/0816 the condition being an adaptation, e.g. in response to network events
• CPC Class Codes: H04L 41/142 using statistical or mathematical methods
• CPC Class Codes: H04L 41/147 for predicting network behaviour
• CPC Class Codes: H04L 41/149 for prediction of maintenance

Abstract

A system and method is disclosed for controlling functionality of a computer network to avoid occurrence of resource or service incidents that degrade or disrupt operation of the network. The metrics monitored are formulated into control charts. Nelson like rules analyze the control charts to identify abnormal service events and abnormal resource events. The identified abnormal service events and abnormal resource events are analyzed using various analytic modes to identify potential resource incidents and potential service incidents. The analytic modes include covariate analysis, multivariate analysis, time series analysis and similar analytic techniques. Information on the abnormal service and abnormal resource events and the information on the potential service incidents/potential resource incidents are forwarded to a control or decision center to guide actions by an autonomic system or human operator to prevent the identified potential resource incidents and potential service incidents from degrading or disrupting operation of the network.

Claims

1. A method for controlling service functionality in a distributed network comprising:

monitoring metrics of a plurality of network factors;

formulating a control chart for each metric monitored of the network factors;

detecting abnormal events by applying Nelson Rules to the control charts;

predicting if an abnormal event indicates a potential incident by analyzing the abnormal events with a predetermined analytic mode; and

controlling service functionality of the distributed network based on the information regarding detected abnormal events and potential incidents.

2. The method of claim 1 wherein the step of detecting an abnormal event comprises the further step of determining if it is an abnormal resource event or an abnormal service event and the step of predicting if an abnormal event indicates a potential incident comprises the further step of determining if it is a potential resource incident or a potential service incident.

3. The method of claim 1 wherein the step of analyzing with a predetermined analytic mode includes analyzing by one or more of the following analytic modes:

correlation analysis, multivariate analysis, and time series analysis.

4. The method of claim 2 comprising the further step of using at least one detected abnormal resource event as an independent variable and using at least one abnormal service level event as a dependent variable in a multivariate analysis to identify a potential resource incident or a potential service incident.

5. The method of claim 2 comprising the further step of using at least one potential resource incident as an independent variable and using the at least one potential service incident as a dependent variable in a multivariate analysis of historical data on incidents to identify additional potential resource incidents or potential service incidents.

6. The method of claim 1 wherein the step of controlling service functionality includes taking one or more of the following actions with respect to the network:

scaling, reconfiguring, load balancing, managing traffic, and fault management.

7. The method of claim 1 wherein the step of analyzing with an analytic mode comprises:

a. determining if an identified abnormal event is an abnormal resource event or an abnormal service event;

b. selecting one of the following analytic modes to identify potential incidents;

i) correlation analysis, ii) multivariate analysis, or iii) time series analysis;

c. selecting independent and dependent variables to conduct the analysis with the selected analytic mode;

d. selecting criteria for identifying potential incidents;

e. applying the selected analytic mode based on the selected variables and the selected criteria to identify potential incidents; and

f. determining if an identified potential incident is a potential resource incident or a potential service incident.

8. A computer program product for controlling service functionality of a distributed network, said computer product comprising:

a computer readable storage medium;

first program instructions for monitoring metrics of a plurality of distributed network factors;

second program instructions for formulating control charts based on the metrics monitored;

third program instructions for detecting abnormal events by applying Nelson Rules to said control charts;

fourth program instructions for predicting if any abnormal event indicates a potential incident by analyzing said abnormal events with a predetermined analytic mode;

fifth program instructions for controlling service functionality of the network based on information regarding said detected events and said potential incidents; and

wherein said first, second, third, fourth and fifth program instructions are stored on said computer readable storage medium.

9. The computer program product of claim 8 wherein the program instructions to detect an abnormal event includes the instructions to determine if it is an abnormal resource event or an abnormal service event, and wherein the program instructions to predict abnormal event is an incident include instructions to determine if it is an abnormal resource incident or an abnormal service incident.

10. The computer program product of claim 8 wherein the step of analyzing with a predetermined analytic mode includes analyzing by one or more of the following analytic modes:

correlation analysis, multivariate analysis, and time series analysis of control chart data.

11. The computer program of claim 9 comprising the further instruction of using at least one detected abnormal resource event as an independent variable and using the at least one abnormal service level event as a dependent variable in a multivariate analysis to identify potential resource incidents or potential service incidents.

12. The computer program product of claim 9 comprising the further step of using at least one potential resource incident as an independent variable and using the at least one potential service incident as a dependent variable in a multivariate analysis of historical data on incidents to identify additional potential resource incidents or potential service incidents.

13. The computer program product of claim 8 wherein the step of controlling service functionality includes taking one or more of the following actions with respect to the network:

scaling, reconfiguring, load balancing, managing traffic, and fault management.

14. The computer program product of claim 8 wherein the program instructions of analyzing with a predetermined analytic mode includes:

sixth program instructions for determining if an identified abnormal event is an abnormal resource event or an abnormal service event;

seventh program instructions for selecting one of the following analytic modes to identify potential incidents;

i) correlation analysis, ii) multivariate analysis, or iii) time series analysis;

eight program instructions for selecting independent and dependent variables to conduct the analysis with the selected analytic mode;

ninth program instructions for selecting criteria for identifying potential incidents;

tenth program instructions for applying the selected analytic mode based on the selected variables and the selected criteria to identify potential incidents;

eleventh program instructions for determining if an identified potential incident is a potential resource incident or a potential service incident; and

wherein said fifth, sixth, seventh, eighth, ninth, tenth and eleventh program instructions are also stored on said computer readable storage medium.

15. An engine for control of service functionality of a distributed network, comprising:

a computer readable storage medium;

a processor operatively coupled to said computer readable storage medium and also operatively coupled to a plurality of external factor monitors, a plurality of service factor monitors, and a plurality of resource factor monitors in the distributed network;

an intelligent analytics engine operatively connected to said processor and said computer readable storage medium, said intelligent analytic engine having program instructions for formulating into control charts, metrics gathered from said plurality of external factor monitors, said plurality of service factor monitors, and said plurality of resource factor monitors;

said intelligent analytics engine having program instructions for detecting abnormal service events and abnormal resource events by applying Nelson style rules to said control charts;

said intelligent analytics engine having program instructions for identifying potential resource incidents and potential service incidents by analyzing said detected abnormal resource events and said detected abnormal service events with a predetermined analytic mode;

said intelligent analytics engine having program instructions for sending information on said detected service events, said detected resource events, said identified potential resource incidents, and said identified potential service incidents to a network control center to thereby aid in controlling resource and service functionality of the distributed network; and

wherein all of said program instructions are stored on said computer readable storage medium.

16. The engine of claim 15 wherein analyzing with a predetermined analytic mode includes analyzing by one or more of the following analytic modes:

correlation analysis, multivariate analysis, and time series analysis of control chart data.

17. The engine of claim 15 comprising the further instructions of using said detected abnormal resource events as an independent variables and using said detected abnormal service level events as a dependent variables in a multivariate analysis to identify a potential resource incident or a potential service incident.

18. The engine of claim 15 comprising the further step of using said potential resource incidents as an independent variables and using said potential service incidents as a dependent variables in a multivariate analysis of historical data on incidents to identify additional potential resource incidents or potential service incidents.

19. The engine of claim 15 wherein controlling service functionality at a network control center includes taking one or more of the following actions with respect to the network:

scaling, reconfiguring, load balancing, managing traffic, and fault management.

20. The engine of claim 15 wherein the program instructions of analyzing with a predetermined analytic mode includes:

program instructions for selecting one of the following analytic modes to identify potential incidents;

i) correlation analysis, ii) multivariate analysis, or iii) time series analysis;

program instructions for selecting independent and dependent variables to conduct the analysis with the selected analytic mode;

program instructions for selecting criteria for identifying potential incidents;

program instructions for applying the selected analytic mode based on the selected variables and the selected criteria to identify potential incidents;

program instructions for determining if an identified potential incident is a potential resource incident or a potential service incident; and

wherein all said program instructions are also stored on said computer readable storage medium.