Search

EP-4740383-A1 - SYSTEM AND METHOD FOR AUTOMATED INTER INTRA NODE DOMAIN ALARM CORRELATION

EP4740383A1EP 4740383 A1EP4740383 A1EP 4740383A1EP-4740383-A1

Abstract

A system and a method of handling alarms in a network is described The method includes classifying a plurality of alarms into parent alarms or child alarms associated with one or more of the parent alarms, based on a policy configured for the network. The method further includes scheduling a task with a specified time interval for handling the child alarms post identification of the parent alarms. The method further includes correlating common attributes between the parent alarms and the child alarms. The method further includes generating a trouble ticket with identities of the parent alarms and identities of the child alarms associated with one or more of the parent alarms.

Inventors

  • BHATNAGAR, AAYUSH
  • E, Elanchezhiyan
  • TIWARI, SUMIT
  • BISHT, SANDEEP
  • MISHRA, RAHUL
  • Chillapalli, Jyothi Durga Prasad
  • MISHRA, SOMYA
  • KUMAR, VIPUL
  • MAGU, Sameer
  • MANIDEEP, Gunda
  • SHARMA, Smridhi

Assignees

  • Jio Platforms Limited

Dates

Publication Date
20260513
Application Date
20240703

Claims (20)

  1. 1. A method of handling alarms in a network, the method comprising the steps of: classifying, by a correlation engine (228), a plurality of alarms into parent alarms or child alarms associated with one or more of the parent alarms, based on a policy configured for the network; scheduling, by the correlation engine (228), a task with a specified time interval for handling the child alarms post identification of the parent alarms; correlating, by the correlation engine (228), common attributes between the parent alarms and the child alarms; and generating, by a trouble ticket processor (230), a trouble ticket with identities of the parent alarms and identities of the child alarms associated with one or more of the parent alarms.
  2. 2. The method as claimed in claim 1, comprising enriching, by an enrichment engine (235), the plurality of alarms prior to classification by the correlation engine (228).
  3. 3. The method as claimed in claim 1, comprising classifying, by the correlation engine (228), the plurality of alarms as the child alarms when corresponding parent alarms are not identified within the specified time interval.
  4. 4. The method as claimed in claim 1, comprising modifying, by the correlation engine (228), existing alarms stored in a database (220) with the attributes for associating the existing alarms as the child alarms with one or more of the parent alarms.
  5. 5. The method as claimed in claim 1, comprising classifying, by the correlation engine (228), the plurality of alarms as the child alarms when corresponding parent alarms are already present within the specified time interval.
  6. 6. The method as claimed in claim 1, comprising grouping, by the correlation engine (228), the plurality of alarms based on the common attributes when the plurality of alarms is not classified as the parent alarms and the child alarms.
  7. 7. The method as claimed in claim 1, comprising promoting, by the correlation engine (228), the child alarms in the order of preference of their respective trigger times when the parent alarms are terminated.
  8. 8. The method as claimed in claim 4, comprising, identifying one of a type of correlation applied, relationship status, and newly populated information corresponding to the modifications made for creating the identification.
  9. 9. The method as claimed in claim 1, comprising identifying, by the correlation engine (228), association between the parent alarms and the child alarms based on a point of interaction (POI) relationship.
  10. 10. The method as claimed in claim 1, comprising identifying, by the correlation engine (228), association between the parent alarms and the child alarms based on intra, inter, cross domain relationships between the plurality of alarms.
  11. 11. A system (125) for handling alarms in a network, the system (125) comprising: a correlation engine (228) configured to classify a plurality of alarms into parent alarms or child alarms associated with one or more of the parent alarms, based on a policy configured for the network, wherein the correlation engine (228) schedules a task with a specified time interval for handling the child alarms upon identifying the parent alarms, and wherein the correlation engine (228) correlates common attributes between the parent alarms and the child alarms; and a trouble ticket processor (230) configured to generate a trouble ticket with identities of the parent alarms and the identities of the child alarms associated with one or more of the parent alarms.
  12. 12. The system as claimed in claim 11, comprises an enrichment engine (235) for enriching the plurality of alarms prior classification by the correlation engine (228).
  13. 13. The system as claimed in claim 11, wherein the correlation engine (228) modifies existing alarms stored in a database (220) with the attributes for associating the existing alarms as the child alarms with one or more of the parent alarms.
  14. 14. The system as claimed in claim 11, wherein the correlation engine (228) classifies the plurality of alarms as the child alarms when corresponding parent alarms are not identified in the specified time interval.
  15. 15. The system as claimed in claim 11, wherein the correlation engine (228) groups the plurality of alarms based on the common attributes when the plurality of alarms is not classified as the parent alarms and the child alarms.
  16. 16. The system as claimed in claim 11 , wherein the correlation engine (228) groups the plurality of alarms as the child alarms when corresponding parent alarms are already present within the specified time interval.
  17. 17. The system as claimed in claim 11, wherein the correlation engine (228) promotes the child alarms in the order of preference of their respective trigger times when the parent alarms are terminated.
  18. 18. The system as claimed in claim 13, wherein the identification is created based on one of a type of correlation applied, relationship status, and newly populated information corresponding to the modifications made.
  19. 19. The system as claimed in claim 11, wherein the correlation engine (228) identifies association between the parent alarms and the child alarms based on a point of interaction (POI) relationship.
  20. 20. The system as claimed in claim 11, wherein the correlation engine (228) identifies association between the parent alarms and the child alarms based on intra, inter, cross domain relationships between the plurality of alarms.

Description

SYSTEM AND METHOD FOR AUTOMATED INTER INTRA NODE DOMAIN ALARM CORRELATION FIELD OF THE INVENTION [0001] The present invention generally relates to node domain alarm correlation, more particularly relates to a system and method for automated inter/intra node domain alarm correlation. BACKGROUND OF THE INVENTION [0002] Efficient network management is vital for telecom operators to ensure continuous service delivery and maintain operational continuity. This is a critical piece in the overall telecommunication network management solution which enables visualization and management of use cases. It is the sole mediator for moderating and managing the Fault Configuration Administration Performance Security (FCAPS) data of the network elements and provides a single pane of glass for the Network Operations Centre. [0003] The visualization and monitoring of use cases is performed by a Network Management System (NMS) which is a common platform that can integrate with all network function elements / nodes, it supports different types of protocols by integrating with the devices (hardware & software). Once integration is done all configuration data of the node is extracted, if a node is running successfully and there is a fault in the node, the node generates an alarm which is sent to NMS. [0004] Typically, in case of a fault in one part of the system, the main node having a fault as well as neighboring nodes raise alarms. Therefore, due to one fault, multiple modules may not work resulting in multiple alarms due to a single fault, issuing multiple trouble tickets. The trouble tickets are equivalent to complaints with associated alarm information condensed together. The information carried in these alarms are restricted to who raised said alarm and minimum information about the issue, information on neighboring domain etc. are not offered. This makes it difficult to pinpoint the faulty equipment thereby increases the work to be performed by the rectifying team as they need to go through all the trouble tickets raised not just by the main/faulty node but also all the neighboring nodes. This can be time consuming. [0005] Therefore, currently the alarms are raised not just by the actual node having fault but multiple others (neighboring) for a single fault due to the existence of many to one connection between elements within a system, resulting in many more alarms than the actual quantum of fault. Further, these alarms offer insufficient information about the fault, resulting in multiple alarms with information insufficient to instantly lead the rectification process to the source, making it difficult to pinpoint the faulty equipment and the failure recovery process time consuming. [0006] Thus, there is a need for a solution which addresses the above mentioned shortcomings. SUMMARY OF THE INVENTION [0007] One or more embodiments of the present disclosure provide a system and method of handling alarms in a network. [0008] In one aspect of the present invention, a system for handling alarms in a network is disclosed. The system includes a correlation engine configured to classify a plurality of alarms into parent alarms or child alarms associated with one or more of the parent alarms, based on a policy configured for the network. The correlation engine schedules a task with a specified time interval for handling the child alarms upon identifying the parent alarms. The correlation engine correlates common attributes between the parent alarms and the child alarms. The system further includes a trouble ticket processor configured to generate a trouble ticket with identities of the parent alarms and the identities of the child alarms associated with one or more of the parent alarms. [0009] In one aspect, the system further comprises an enrichment engine for enriching the plurality of alarms prior classification by the correlation engine. The correlation engine modifies existing alarms stored in a database with the attributes for associating the existing alarms as the child alarms with one or more of the parent alarms. The correlation engine classifies the plurality of alarms as the child alarms when corresponding parent alarms are not identified in the specified time interval. The correlation engine groups the plurality of alarms based on the common attributes when the plurality of alarms is not classified as the parent alarms and the child alarms. The correlation engine groups the plurality of alarms as the child alarms when corresponding parent alarms are already present within the specified time interval. The correlation engine promotes the child alarms in the order of preference of their respective trigger times when the parent alarms are terminated. The identification is created based on one of a type of correlation applied, relationship status, and newly populated information corresponding to the modifications made. The correlation engine identifies association between the parent alarms and the child alarms based on a