Alarm prioritization in a 5G Telco network
Examples herein describe systems and methods for alarm prioritization in a Telco network. A prioritization engine can receive root cause problems and impacted network components from a network analysis module. The prioritization engine can define a mapping matrix that weights the problems according to network component type and service level. Using the problem weights, the prioritization engine can construct a problem-impact matrix that includes impact weights. The impact weights can be summed for each problem, as can the problem weights. The problems with the highest summed weights can then be prioritized first. The summed weights can also be based on predicted failure costs, such that the most expensive problems are prioritized first. The prioritization engine can send prioritized alerts for the problems for display on a graphical user interface (“GUI”).
1. A method for alarm prioritization in a Telco network, comprising:
constructing a mapping matrix that maps network resource types to problem weights, wherein the problem weights correlate to how impactful a network resource type is to operation of the Telco network;
receiving, at a prioritization engine, problem notifications that indicate impacted network resources, the impacted network resources having corresponding network resource types;
creating a problem-impact (“PI”) matrix based on the received problem notifications, wherein creating the PI matrix includes:
correlating problems to corresponding impacted network resources based on the problem notifications; and
assigning impact weights to the impacted network resources based on the problem weights of the mapping matrix, wherein the problem weights are identified in the mapping matrix based on the respective network types of the network resources;
summing the impact weights for each problem notification to produce PI weights; and
prioritizing alerts on a graphical user interface (“GUI”) based on the PI weights of the problem notifications.
2. The method of claim 1 , wherein the mapping matrix further includes different classes of service that act as multipliers against weights for the network resource types, and wherein different tenants are assigned different classes of service.
3. The method of claim 1 , wherein the problem weights are updated based on which problems an administrator resolves before other problems.
4. The method of claim 1 , wherein assigning impact weights includes determining an edge weight value in a graph.
5. The method of claim 1 , wherein creating the PI matrix includes:
creating a table having a first dimension for problems and a second dimension for impacted network components; and
populating the table with the impact weights for impacted resources based on the symptoms identified in the problem notifications.
6. The method of claim 5 , wherein a first symptom corresponding to a first network resource is used to determine a first tenant is impacted by the problem, and wherein the corresponding impact weight is populated from the mapping matrix based on identifying the first tenant and the resource type of the first network resource.
7. The method of claim 1 , wherein prioritizing the alerts includes ranking problems based on failure costs, and wherein the failure costs are obtained based on multiplying an estimated downtime against a PI weight.
8. A non-transitory, computer-readable medium comprising instructions that, when executed by a processor, perform stages for alarm prioritization in a Telco network, the stages comprising:
constructing a mapping matrix that maps network resource types to problem weights, wherein the problem weights correlate to how impactful a network resource type is to operation of the Telco network;
receiving, at a prioritization engine, problem notifications that indicate impacted network resources, the impacted network resources having corresponding network resource types;
creating a problem-impact (“PI”) matrix based on the received problem notifications, wherein creating the PI matrix includes:
correlating problems to corresponding impacted network resources based on the problem notifications; and
assigning impact weights to the impacted network resources based on the problem weights of the mapping matrix, wherein the problem weights are identified in the mapping matrix based on the respective network types of the network resources;
summing the impact weights for each problem notification to produce PI weights; and
prioritizing alerts on a graphical user interface (“GUI”) based on the PI weights of the problem notifications problems.
9. The non-transitory, computer-readable medium of claim 8 , wherein the mapping matrix further includes different classes of service that act as multipliers against weights for the network resource types, and wherein different tenants are assigned different classes of service.
10. The non-transitory, computer-readable medium of claim 8 , wherein the problem weights are updated based on which problems an administrator resolves before other problems.
11. The non-transitory, computer-readable medium of claim 8 , wherein assigning impact weights includes determining an edge weight value in a graph.
12. The non-transitory, computer-readable medium of claim 8 , wherein creating the PI matrix includes:
creating a table having a first dimension for problems and a second dimension for impacted network components; and
populating the table with the impact weights for impacted resources based on the symptoms identified in the problem notifications.
13. The non-transitory, computer-readable medium of claim 12 , wherein a first symptom corresponding to a first network resource is used to determine a first tenant is impacted by the problem, and wherein the corresponding impact weight is populated from the mapping matrix based on identifying the first tenant and the resource type of the first network resource.
14. The non-transitory, computer-readable medium of claim 8 , wherein prioritizing the alerts includes ranking problems based on failure costs, and wherein the failure costs are obtained based on multiplying an estimated downtime against a PI weight.
15. A system for alarm prioritization in a Telco network, comprising:
a non-transitory, computer-readable medium containing instructions; and
a processor that executes the instructions perform stages comprising:
constructing a mapping matrix that maps network resource types to problem weights, wherein the problem weights correlate to how impactful a network resource type is to operation of the Telco network;
receiving, at a prioritization engine, problem notifications that indicate impacted network resources, the impacted network resources having corresponding network resource types;
creating a problem-impact (“PI”) matrix based on the received problem notifications, wherein creating the PI matrix includes:
correlating problems to corresponding impacted network resources based on the problem notifications; and
assigning impact weights to the impacted network resources based on the problem weights of the mapping matrix, wherein the problem weights are identified in the mapping matrix based on the respective network types of the network resources;
summing the impact weights for each problem notification to produce PI weights; and
prioritizing alerts on a graphical user interface (“GUI”) based on the PI weights of the problem notifications.
16. The system of claim 15 , wherein the mapping matrix further includes different classes of service that act as multipliers against weights for the network resource types, and wherein different tenants are assigned different classes of service.
17. The system of claim 15 , wherein the problem weights are updated based on which problems an administrator resolves before other problems.
18. The system of claim 15 , wherein assigning impact weights includes determining an edge weight value in a graph.
19. The system of claim 15 , wherein creating the PI matrix includes:
creating a table having a first dimension for problems and a second dimension for impacted network components; and
populating the table with the impact weights for impacted resources based on the symptoms identified in the problem notifications.
20. The system of claim 15 , wherein prioritizing the alerts includes ranking problems based on failure costs, and wherein the failure costs are obtained based on multiplying an estimated downtime against a PI weight.