DESC:
FORM 2
THE PATENTS ACT, 1970
(39 of 1970)
&
THE PATENTS RULES, 2003

COMPLETE SPECIFICATION
(See section 10 and rule 13)
1. TITLE OF THE INVENTION
METHOD AND SYSTEM FOR MANAGING LOAD OF ALARMS IN A NETWORK MANAGEMENT SYSTEM
2. APPLICANT(S)
NAME NATIONALITY ADDRESS
JIO PLATFORMS LIMITED INDIAN OFFICE-101, SAFFRON, NR. CENTRE POINT, PANCHWATI 5 RASTA, AMBAWADI, AHMEDABAD 380006, GUJARAT, INDIA
3.PREAMBLE TO THE DESCRIPTION

THE FOLLOWING SPECIFICATION PARTICULARLY DESCRIBES THE NATURE OF THIS INVENTION AND THE MANNER IN WHICH IT IS TO BE PERFORMED.

FIELD OF THE INVENTION
[0001] The present invention generally relates to wireless communication networks, and more particularly relates to a method and system for managing load of alarms in the networks.
BACKGROUND OF THE INVENTION
[0002] Network Management Systems (NMS) are software applications or platforms designed to monitor, control, and manage computer networks. NMS solutions play a crucial role in maintaining network performance, reliability, and security. NMS provides a centralized interface for network administrators to efficiently manage and troubleshoot network devices, services, and resources.
[0003] NMS tools monitor network devices and services for fault conditions and generate alarms or notifications when issues are detected. Alarms can include events such as device failures, connectivity problems, threshold violations, security breaches, or performance degradation.
[0004] By effectively managing network traffic and alarms, NMS tools help network administrators monitor network health, troubleshoot issues, and maintain a stable and reliable network infrastructure. These functionalities contribute to efficient network operations and better end-user experiences.
[0005] In the Network Management System, there are several possible events of sudden and significant increase in the number of alarms or events being generated within a short period, that is known as burst case. It could be due to various factors such as network failures, equipment malfunctions, security incidents, or sudden spikes in network traffic. During a burst case, the NMS experiences a surge in the volume of alarms, which can potentially overwhelm the system and its components responsible for processing and managing those alarms.
[0006] The existing burst mechanism may not have been designed to handle sudden and significant increases in alarm volumes. As a result, the NMS may struggle to scale up its processing capabilities to accommodate the burst, leading to performance degradation or unresponsiveness.
[0007] Additionally, if the existing burst mechanism heavily relies on manual intervention for managing the burst, it can introduce delays and increase the risk of errors. Manual processes may not be able to keep up with the rapid influx of alarms, potentially leading to extended resolution times and suboptimal handling of the burst situation.
[0008] Therefore, there is a need for an advancement of a system and method that can overcome at least one of the above shortcomings, particularly for managing load of alarms in the network management system.
BRIEF SUMMARY OF THE INVENTION
[0009] One or more embodiments of the present disclosure provide a method and system for managing load of alarms in a Network Management Systems (NMS).
[0010] In one aspect of the present invention, a method for managing load of alarms in a Network Management Systems (NMS) is disclosed. The method includes the step of fetching, by one or more processors, data pertaining to a total count of alarms stored in a database. The method includes the step of comparing, by the one or more processors, the total count of alarms with a first predefined threshold and a second predefined threshold, respectively. The method includes the step of performing, by the one or more processors, one or more tasks to manage the load of alarms in the NMS based on comparison of the total count of alarms with the first predefined threshold and the second predefined threshold, respectively.
[0011] In one embodiment, the one or more tasks performed by the one or more processors, includes at least one of disabling, consumption of subsequent one or more alarms until a pre-defined time period is completed, in response to detecting, the total count of alarms being greater than the first predefined threshold. The one or more tasks includes enabling, consumption of subsequent one or more alarms until the pre-defined time period is completed, in response to detecting, the total count of alarms being lower than the second predefined threshold. The one or more tasks includes enabling, consumption of subsequent one or more alarms until the pre-defined time period is completed, in response to detecting, the total count of alarms being lower than the first predefined threshold and greater than the second predefined threshold, and the total count of the alarms increases until the total count of alarms reaches the first pre-defined threshold. The one or more tasks includes disabling, consumption of subsequent one or more alarms until the pre-defined time period is completed, in response to detecting, the total count of alarms being lower than the first predefined threshold and greater than the second predefined threshold, and the total count of the alarms at least one of, remains constant and decreases.
[0012] In another embodiment, the one or more processors fetches details of the alarm by retrieving an alarm identifier from a message stream. The one or more processors fetches details of the alarm by fetching, a relevant alarm from the database using the retrieved alarm identifier.
[0013] In yet another embodiment, the alarms are generated by the one or more network elements and stored in the database with the alarm identifier.
[0014] In yet another embodiment, the one or more processors communicates with the database to facilitate in maintaining a timestamp array for each alarm, thereby enabling accurate tracking of alarm occurrences.
[0015] In yet another embodiment, the first predefined threshold and the second predefined threshold are configured by a user.
[0016] In yet another embodiment, the method further includes the step of transmitting, by the one or more processors, at least one of, a burst critical alert via Short Message Service (SMS) or email to the user when the total count of alarms is greater than the first predefined threshold for a pre-defined number of consecutive time intervals.
[0017] In yet another embodiment, the method further includes the step of subsequent to the total count of alarms in the database is greater than the first predefined threshold, the one or more processors, delays in consumption of the one or more alarms in the NMS to manage the load of alarms, wherein the delay is at least one of, a pre-defined and dynamic.
[0018] In yet another embodiment, the method further includes the step of managing the load of the alarms in the NMS by introducing a first counter that stores count of consumed alarm records from the message stream and a second counter that stores the count of alarm records inserted to the database.
[0019] In yet another embodiment, the method further includes the step of comparing, by the one or more processors, an absolute difference between the second counter and the first counter with the first predefined threshold. The method further includes the step of in response to the comparison, enabling, by the one or more processors, a flag to indicate a threshold breach of the database when the absolute difference between the second counter and the first counter is greater than the first predefined threshold. The method further includes the step of disabling, by the one or more processors, the flag when the absolute difference between the second counter and the first counter is less than the first predefined threshold.
[0020] In yet another embodiment, the method further includes the step of retrieving, by the one or more processors, load of the alarms from the message stream. The method further includes the step of communicating, by the one or more processors, with the database pertaining to the load of the alarms. The method further includes the step of segregating, by the one or more processors, the load as at least one of, a Raise, a Clear, a Retry and a Call-back.
[0021] In another aspect of the present invention, a system for managing load of alarms in a Network Management Systems (NMS) is disclosed. The system includes a fetching unit configured to fetch, data pertaining to a total count of alarms stored in a database. The system includes a comparator configured to compare the total count of alarms with a first predefined threshold and a second predefined threshold, respectively. The system includes a load manager configured to perform one or more tasks to manage the load of alarms in the NMS based on comparison of the total count of alarms with the first predefined threshold and the second predefined threshold, respectively.
[0022] Other features and aspects of this invention will be apparent from the following description and the accompanying drawings. The features and advantages described in this summary and in the following detailed description are not all-inclusive, and particularly, many additional features and advantages will be apparent to one of ordinary skill in the relevant art, in view of the drawings, specification, and claims hereof. Moreover, it should be noted that the language used in the specification has been principally selected for readability and instructional purposes and may not have been selected to delineate or circumscribe the inventive subject matter, resort to the claims being necessary to determine such inventive subject matter.
BRIEF DESCRIPTION OF THE DRAWINGS
[0023] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in which like reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Some drawings may indicate the components using block diagrams and may not represent the internal circuitry of each component. It will be appreciated by those skilled in the art that disclosure of such drawings includes disclosure of electrical components, electronic components or circuitry commonly used to implement such components.
[0024] FIG. 1 is an exemplary block diagram of an environment for managing load of alarms in a Network Management System (NMS), according to one or more embodiments of the present disclosure;
[0025] FIG. 2 is an exemplary block diagram of a system for managing the load of alarms in the NMS, according to one or more embodiments of the present disclosure;
[0026] FIG. 3 is a schematic representation of the present system of FIG. 1 workflow, according to one or more embodiments of the present disclosure;
[0027] FIG. 4 is a sequence flow diagram illustrating a method for managing the load of alarms in the NMS, according to one or more embodiments of the present disclosure;
[0028] FIG.5 is a schematic representation of an architecture of the system of FIG. 2, according to one or more embodiments of the present disclosure; and
[0029] FIG. 6 is a flow diagram illustrating a method for managing load of alarms in the NMS, according to one or more embodiments of the present disclosure.
[0030] The foregoing shall be more apparent from the following detailed description of the invention.
DETAILED DESCRIPTION OF THE INVENTION
[0031] Some embodiments of the present disclosure, illustrating all its features, will now be discussed in detail. It must also be noted that as used herein and in the appended claims, the singular forms "a", "an" and "the" include plural references unless the context clearly dictates otherwise.
[0032] Various modifications to the embodiment will be readily apparent to those skilled in the art and the generic principles herein may be applied to other embodiments. However, one of ordinary skill in the art will readily recognize that the present disclosure including the definitions listed here below are not intended to be limited to the embodiments illustrated but is to be accorded the widest scope consistent with the principles and features described herein.
[0033] A person of ordinary skill in the art will readily ascertain that the illustrated steps detailed in the figures and here below are set out to explain the exemplary embodiments shown, and it should be anticipated that ongoing technological development will change the manner in which particular functions are performed. These examples are presented herein for purposes of illustration, and not limitation. Further, the boundaries of the functional building blocks have been arbitrarily defined herein for the convenience of the description. Alternative boundaries can be defined so long as the specified functions and relationships thereof are appropriately performed. Alternatives (including equivalents, extensions, variations, deviations, etc., of those described herein) will be apparent to persons skilled in the relevant art(s) based on the teachings contained herein. Such alternatives fall within the scope and spirit of the disclosed embodiments.
[0034] The present invention relates to a method and a system for managing load of alarms in a Network Management Systems (NMS). Conventional alarm systems face challenges in managing the burst cases, which can introduce delays and increase the risk of errors. The disclosed invention addresses these challenges by introducing a high Transaction Per Second (TPS) and implementing the hold and process of the load of alarms to handle the peak TPS of alarms flow towards the processor.
[0035] The present invention handles the load of alarms on the processor which may leave the processor in an unresponsive state. The load of alarms is referred to as Burst cases and the mechanism is known as burst control mechanism. The present invention prevents the processor from getting the memory full issue, which in turn keeps the processor in responsive state, with high availability even when the TPS is very high.
[0036] FIG. 1 illustrates an exemplary block diagram of an environment 100 for managing load of alarms in a Network Management System (NMS) 120, according to one or more embodiments of the present disclosure. The environment 100 includes a network 105, a User Equipment (UE) 110, a server 115, the NMS 120, and a system 125. The UE 110 aids a user to interact with the system 125 to receive at least one of, a burst critical alert via Short Message Service (SMS) or email, when a total count of alarms is greater than a first predefined threshold for a pre-defined number of consecutive time intervals. The burst critical alert typically refers to an alarm or notification triggered when an unexpected increase in activity or data occurs within the system 125 at any time.
[0037] For the purpose of description and explanation, the description will be explained with respect to one or more UEs 110, or to be more specific will be explained with respect to a first UE 110a, a second UE 110b, and a third UE 110c, and should nowhere be construed as limiting the scope of the present disclosure. Each of the UE 110 from the first UE 110a, the second UE 110b, and the third UE 110c is configured to connect to the server 115 via the network 105.
[0038] In an embodiment, the first UE 110a includes, but not limited to, a network element. The first UE 110a is one of, but is not limited to, hubs, switches, routers, bridges, gateways, modems, repeaters, and access points.
[0039] In an embodiment, each of the second UE 110b, and the third UE 110c is one of, but not limited to, any electrical, electronic, electro-mechanical or an equipment and a combination of one or more of the above devices such as virtual reality (VR) devices, augmented reality (AR) devices, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, mainframe computer, or any other computing device.
[0040] In accordance with one aspect of the present invention, each of the second UE 110b, and the third UE 110c is configured to facilitate receiving an alert message via the network 105 for the purpose of availing a plurality of services. The scope of the plurality of services includes, but is not limited to, engaging with the server 115 for the purpose of submitting a request thereto, and receiving the at least one of, the burst critical alert via SMS or email, all aforementioned activities being conducted over the network 105 The plurality of services enables a streamlined and efficient interaction between the UE 110 and the network resources, thereby enhancing the utility and performance of the network 105 in providing said services.
[0041] The network 105 includes, by way of example but not limitation, one or more of a wireless network, a wired network, an internet, an intranet, a public network, a private network, a packet-switched network, a circuit-switched network, an ad hoc network, an infrastructure network, a Public-Switched Telephone Network (PSTN), a cable network, a cellular network, a satellite network, a fiber optic network, or some combination thereof. The network 105 may include, but is not limited to, a Third Generation (3G), a Fourth Generation (4G), a Fifth Generation (5G), a Sixth Generation (6G), a New Radio (NR), a Narrow Band Internet of Things (NB-IoT), an Open Radio Access Network (O-RAN), and the like.
[0042] The network 105 may also include, by way of example but not limitation, at least a portion of one or more networks having one or more nodes that transmit, receive, forward, generate, buffer, store, route, switch, process, or a combination thereof, etc. one or more messages, packets, signals, waves, voltage or current levels, some combination thereof, or so forth. The network 105 may also include, by way of example but not limitation, one or more of a wireless network, a wired network, an internet, an intranet, a public network, a private network, a packet-switched network, a circuit-switched network, an ad hoc network, an infrastructure network, a Public-Switched Telephone Network (PSTN), a cable network, a cellular network, a satellite network, a fiber optic network, a VOIP or some combination thereof.
[0043] The environment 100 includes the server 115 accessible via the network 105. The server 115 may include by way of example but not limitation, one or more of a standalone server, a server blade, a server rack, a bank of servers, a server farm, hardware supporting a part of a cloud service or system, a home server, hardware running a virtualized server, one or more processors executing code to function as a server, one or more machines performing server-side functionality as described herein, at least a portion of any of the above, some combination thereof. In an embodiment, the entity may include, but is not limited to, a vendor, a network operator, a company, an organization, a university, a lab facility, a business enterprise side, a defence facility side, or any other facility that provides service.
[0044] The environment 100 further includes the NMS 120. The NMS 120 is a set of tools, protocols, and software applications designed to monitor, manage, and optimize computer networks. The NMS 120 typically includes features such as network monitoring, performance management, fault detection and isolation, configuration management, security management, and reporting. The NMS 120 solutions play a crucial role in maintaining network performance, reliability, and security. The NMS 120 provides a centralized interface for network administrators to efficiently manage and troubleshoot network devices, services, and resources. The NMS 120 is configured for managing the load of alarms and storing a total count of alarms in a database 130.
[0045] The database 130 is configured to store data pertaining to the total count of alarms. Further, the database 130 provides structured storage, support for complex queries, and enables efficient data retrieval and analysis. The database 130 is one of, but is not limited to, one of a centralized database, a cloud-based database, a commercial database, an open-source database, a distributed database, an end-user database, a graphical database, a No-Structured Query Language (NoSQL) database, an object-oriented database, a personal database, an in-memory database, a document-based database, a time series database, a wide column database, a key value database, a search database, a Input/ Output (I/O) cache databases, and so forth. The foregoing examples of database types are non-limiting and may not be mutually exclusive e.g., a database can be both commercial and cloud-based, or both relational and open-source, etc.
[0046] In an embodiment, the I/O cache is a memory layer that temporarily stores the data pertaining to the total count of alarms that is being transferred between the first UE 110a and a Central Processing Unit (CPU). The primary purpose of the I/O cache is to speed up data access times and improve the overall efficiency of data processing. The I/O cache performs faster TPS processing, which reduces latency, increases throughput, and optimizes utilization of resources, thus improving system performance, reduces load, and enhances user experience.
[0047] The environment 100 further includes the system 125 communicably coupled to the server 115 and each of the first UE 110a, the second UE 110b, and the third UE 110c via the network 105. The system 125 is adapted to be embedded within the server 115 or is embedded as the individual entity. However, for the purpose of description, the system 125 is described as an integral part of the server 115, without deviating from the scope of the present disclosure.
[0048] The environment 100 includes the NMS 120 communicably coupled to the system 125 via the network 105. As per the illustrated embodiment, the NMS 120 is adapted to be embedded as an individual entity. In an alternate embodiment, the NMS 120 is adapted to be embedded within the system 125.
[0049] The system 125 is further configured to employ Transmission Control Protocol (TCP) connection to identify any connection loss in the network 105 and thereby improving overall efficiency. The TCP connection is a communication standard enabling applications and the system 125 to exchange information over the network 105.
[0050] Operational and construction features of the system 125 will be explained in detail with respect to the following figures.
[0051] FIG. 2 illustrates an exemplary block diagram of the system 125 for managing load of alarms in the NMS 120, according to one or more embodiments of the present disclosure. The system 125 includes one or more processors 205, a memory 210, and an interface unit 215. The one or more processors 205, hereinafter referred to as the processor 205 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, single board computers, and/or any devices that manipulate signals based on operational instructions. As per the illustrated embodiment, the system 125 includes one processor 205. However, it is to be noted that the system 125 may include multiple processors as per the requirement and without deviating from the scope of the present disclosure.
[0052] The information related to the request pertaining to managing the load of alarms is provided or stored in the memory 210. Among other capabilities, the processor 205 is configured to fetch and execute computer-readable instructions stored in the memory 210. The memory 210 may be configured to store one or more computer-readable instructions or routines in a non-transitory computer-readable storage medium, which may be fetched and executed to create or share data packets over a network service. The memory 210 may include any non-transitory storage device including, for example, volatile memory such as RAM, or non-volatile memory such as EPROMs, FLASH memory, unalterable memory, and the like.
[0053] The information related to the request pertaining to managing the load of alarms is rendered on the interface unit 215. The interface unit 215 includes a variety of interfaces, for example, interfaces for a Graphical User Interface (GUI), a web user interface, a Command Line Interface (CLI), and the like. The interface unit 215 facilitates communication of the system 125. In one embodiment, the interface unit 215 provides a communication pathway for one or more components of the system 125. Examples of the one or more components include, but are not limited to, the UE 110 and the database 130.
[0054] Further, the processor 205, in an embodiment, may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processor 205. In the examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processor 205 may be processor-executable instructions stored on a non-transitory machine-readable storage medium and the hardware for processor 205 may comprise a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the memory 210 may store instructions that, when executed by the processing resource, implement the processor 205. In such examples, the system 125 may comprise the memory 210 storing the instructions and the processing resource to execute the instructions, or the memory 210 may be separate but accessible to the system 125 and the processing resource. In other examples, the processor 205 may be implemented by electronic circuitry.
[0055] In order for the system 125 to manage load of alarms in the NMS 120, the processor 205 includes a fetching unit 220, a comparator 225, and a load manager 230 communicably coupled to each other for managing the load of alarms in the NMS 120. The load manager 230 includes a first counter 235, and a second counter 240.
[0056] The fetching unit 220, the comparator 225, and the load manager 230 in an embodiment, may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processor 205. In the examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processor 205 may be processor-executable instructions stored on a non-transitory machine-readable storage medium and the hardware for the processor may comprise a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the memory 210 may store instructions that, when executed by the processing resource, implement the processor. In such examples, the system 125 may comprise the memory 210 storing the instructions and the processing resource to execute the instructions, or the memory 210 may be separate but accessible to the system 125 and the processing resource. In other examples, the processor 205 may be implemented by electronic circuitry.
[0057] The fetching unit 220 is configured to fetch data pertaining to a total count of alarms stored in the database 130. The NMS 120 includes the database 130. The one or more alarms include, but not limited to, performance alarms, connection alarms, QoS alarms, and environmental alarms. In an example, the performance alarms indicate alerts on high network traffic when the network traffic exceeds a predefined threshold, delays in data transmission, which can impact network performance, notifies packet loss when a significant number of packets are lost during transmission. In an embodiment, the alarms can be of different types such as, but not limited to, a raise alarm, a clear alarm, a retry alarm, and a count are fetched by the fetching unit 220. The one or more alarms are generated by the one or more network elements and stored in the database 130 with an alarm identifier. The alarm identifier refers to a unique code or label assigned to each alarm event that occurs within the system 125. The alarm identifier is used to uniquely identify and track individual alarms, making it easier for administrators and automated systems to manage and respond to network issues efficiently.
[0058] In an embodiment, the one or more network elements is at least one of, routers, switches, links, the server 115, and the NMS 120. The alarms are held within a continuous stream, managed to ensure that all consumed alarms are processed efficiently and without any loss, based on the availability of resources. The fetching unit 220 fetches details of the alarm by retrieving the alarm identifier from a message stream. The message stream refers to a continuous flow of data messages that are transmitted or received in a sequential order. The message stream typically consists of discrete units of data, each representing a specific piece of information or event. In an embodiment, the details of the alarm include, but not limited to, network traffics, delays, packet losses, and the like. The fetching unit 220 fetches details of the alarm by fetching a relevant alarm from the database 130 using the retrieved alarm identifier.
[0059] Upon retrieving the alarm identifier from the message stream, the load manager 230 is further configured to retrieve load of the alarms from the message stream. The load manager 230 is further configured to communicate, with the database 130 pertaining to the load of the alarms. The load manager 230 is further configured to segregate the load as at least one of different types of alarms such as, but not limited to, a Raise, a Clear, a Retry and a Call-back.
[0060] The load manager 230 is configured to segregate the load as the raise, the load manager 230 accepts the one or more alarms and inserts the data related to raise alarms into a persistence storage with pre-processing and forwards the data further for post-processing after insertion. The load manager 230 is configured to segregate the load as the clear, the load manager 230 accepts the one or more alarms and performs clearance operation and forwards the one or more alarms further for termination, and also produces the data to the Retry for unidentified clear alarms. The load manager 230 is configured to segregate the load as the retry, the load manager 230 accepts the unidentified clear alarms and tries to associate with raise events with configured number of retries. The load manager 230 is configured to segregate the load as the call-back, the load manager 230 accepts the one or more alarms and updates physical/ logical enrichment and forwards the data further for correlation and Trouble Ticket (TT) creation.
[0061] In addition to the fetching unit 220, on fetching details of the alarm in the database 130 using the retrieved alarm identifier, the comparator 225 is configured to compare the total count of alarms with a first predefined threshold and a second predefined threshold, respectively. In an embodiment, the first predefined threshold and the second predefined threshold are configured by a user. The user includes network administrators.
[0062] On comparing the total count of alarms with the first predefined threshold and the second predefined threshold, respectively, the load manager 230 is configured to perform one or more tasks to manage the load of alarms in the NMS 120. In an embodiment, the one or more tasks includes disabling consumption of subsequent one or more alarms which is transmitted to the UE 110 until a pre-defined time period is completed, in response to detecting, the total count of alarms being greater than the first predefined threshold. In an embodiment, the pre-defined time period is defined by the network administrators. The load manager 230 is further configured to check whether the total count of alarms is greater than the first predefined threshold. The load manager 230 is further configured to transmit at least one of, a burst critical alert via Short Message Service (SMS) or email to the user when the total count of alarms is greater than the first predefined threshold for the pre-defined number of consecutive time intervals. The burst case alert typically refers to an alarm or notification triggered when an unexpected increase in activity or data occurs within the system 125 at any time.
[0063] In another embodiment, in response to detecting, the total count of alarms being lower than the second predefined threshold, the one or more tasks includes enabling consumption of subsequent one or more alarms until the pre-defined time period is completed. Additionally, in response to detecting, the total count of alarms being lower than the first predefined threshold and greater than the second predefined threshold, the one or more tasks includes enabling consumption of subsequent one or more alarms until the pre-defined time period is completed. The total count of the alarms increases until the total count of alarms reaches the first pre-defined threshold. If the total count of alarms reaches the first pre-defined threshold, the burst case alert is transmitted to the UE 110.
[0064] In yet another embodiment, in response to detecting, the total count of alarms being greater than the first predefined threshold, the one or more tasks includes disabling, consumption of subsequent one or more alarms until the pre-defined time period is completed, and the total count of the alarms includes, at least one of, remains constant and decreases.
[0065] In addition to managing the load of alarms, the load manager 230 is further configured to communicate with the database 130 to facilitate in maintaining a timestamp array for each alarm. Doing so, the load manager aids in enabling accurate tracking of alarm occurrences. The timestamp array is a data structure that stores a sequence of timestamp values in a specific order. The timestamp arrays are typically used to record date and time when events occur in the system 125.
[0066] In addition to managing the load of alarms, the load manager 230 is further configured to receive delay in consumption of the one or more alarms in the NMS 120 if the total count of alarms in the database 130 is greater than the first predefined threshold. The delay is at least one of, a pre-defined and dynamic. The predefined delay refers to a set period of time that has been predetermined or preconfigured for receiving one or more alarms within the system 125. The predefined delay is typically established in advance based on the requirements or specifications of the system 125. The dynamic delay refers to the delay caused due to processes or mechanisms that adapt, change, or update automatically based on the current network conditions or configurations.
[0067] In addition to managing the load of alarms, the load manager 230 is configured to manage the load of the alarms in the NMS 120 by introducing a first counter 235 and a second counter 240. The first counter 235 stores a count of consumed alarm records from the message stream. In an embodiment, the consumed alarm records are referred to as the total count of alarms received from the message stream. The second counter 240 stores the total count of alarms processed and inserted to the database 130. The load manager 230 is further configured to compare an absolute difference between the second counter 240 and the first counter 235 with the first predefined threshold. In an embodiment, the absolute difference includes, but is not limited to the total count of the alarms which are received and the total count of the alarms which are processed.
[0068] The load manager 230 is further configured to enable a flag to indicate a threshold breach of the database 130 in response to the comparison when the absolute difference between the second counter 240 and the first counter 235 is greater than the first predefined threshold. In an example, the first predefined threshold is 100, the absolute difference between the second counter 240 and the first counter 235 reaches 101, the load manager 230 enables the flag for indicating the threshold breach of the database 130.
[0069] The load manager 230 is further configured to disable the flag when the absolute difference between the second counter 240 and the first counter 235 is lesser than the first predefined threshold. In an example, the first predefined threshold is 100, the absolute difference between the second counter 240 and the first counter 235 reaches 81, the load manager 230 disables the flag. Upon disabling the flag, the database 130 receives the one or more alarms until the database 130 reaches the first predefined threshold. By doing so, the system 125 reduces requirement of the memory space, which in turn keeps the processor 205 in responsive state, with high availability even when the Transaction Per Second (TPS) is very high. The one or more alarms are held in database 130 and consumed the availability of resources such as the processor 205 to ensure all the consumed alarms are being processed properly without any loss.
[0070] FIG. 3 is a schematic representation of the system 125 in which various entities operations are explained, according to one or more embodiments of the present disclosure. Referring to FIG. 3, describes the system 125 for managing load of alarms in the NMS 120. It is to be noted that the embodiment with respect to FIG. 3 will be explained with respect to the first UE 110a for the purpose of description and illustration and should nowhere be construed as limited to the scope of the present disclosure.
[0071] As mentioned earlier in FIG.1, In an embodiment, the first UE 110a may encompass electronic apparatuses. These devices are illustrative of, but not restricted to, personal computers, laptops, tablets, smartphones (including phones), or other devices enabled for web connectivity. The scope of the first UE 110a explicitly extends to a broad spectrum of electronic devices capable of executing computing operations and accessing networked resources, thereby providing users with a versatile range of functionalities for both personal and professional applications. This embodiment acknowledges the evolving nature of electronic devices and their integral role in facilitating access to digital services and platforms. In an embodiment, the first UE 110a can be associated with multiple users. Each UE 110 is communicatively coupled with the processor 205 via the network 105.
[0072] The first UE 110a includes one or more primary processors 305 communicably coupled to the one or more processors 205 of the system 125. The one or more primary processors 305 are coupled with a memory unit 310 storing instructions which are executed by the one or more primary processors 305. Execution of the stored instructions by the one or more primary processors 305 enables the first UE 110a to receive, at least one of, the burst critical alert via the SMS or the email, when the total count of alarms is greater than the first predefined threshold for the pre-defined time.
[0073] Furthermore, the one or more primary processors 305 within the UE 110 are uniquely configured to execute a series of steps as described herein. This configuration underscores the processor 205 capability to manage the load of alarms in the NMS 120. The operational synergy between the one or more primary processors 305 and the additional processors, guided by the executable instructions stored in the memory unit 310, facilitates a seamless managing of the load of alarms in the NMS 120.
[0074] As mentioned earlier in FIG.2, the one or more processors 205 of the system 125 is configured to fetch data pertaining to the total count of alarms stored in the database 130, compare the total count of alarms with the first predefined threshold and the second predefined threshold, respectively, and perform, the one or more tasks to manage the load of alarms in the NMS 120 based on comparison of the total count of alarms with the first predefined threshold and the second predefined threshold, respectively.
[0075] As per the illustrated embodiment, the system 125 includes the one or more processors 205, the memory 210, and the interface unit 215. The operations and functions of the one or more processors 205, the memory 210, and the interface unit 215 are already explained in FIG. 2. For the sake of brevity, a similar description related to the working and operation of the system 125 as illustrated in FIG. 2 has been omitted to avoid repetition.
[0076] Further, the processor 205 includes the fetching unit 220, the comparator 225, the load manager 230, the first counter 235, and the second counter 240. The operations and functions of the fetching unit 220, the comparator 225, the load manager 230, the first counter 235, and the second counter 240 are already explained in FIG. 2. Hence, for the sake of brevity, a similar description related to the working and operation of the system 125 as illustrated in FIG. 2 has been omitted to avoid repetition. The limited description provided for the system 125 in FIG. 3, should be read with the description provided for the system 125 in the FIG. 2 above, and should not be construed as limiting the scope of the present disclosure.
[0077] FIG. 4 illustrates an exemplary block diagram of the load manager to perform enabling and disabling function of the load of alarms, according to one or more embodiments of the present disclosure.
[0078] At step 402, the fetching unit 220 is configured to fetch data pertaining to the total count of alarms stored in the database 130. The alarms are generated by the one or more network elements and stored in the database 130 with the alarm identifier. The fetching unit 220 fetches details of the alarm by retrieving the alarm identifier from the message stream. The fetching unit 220 fetches the details of the alarm by fetching the relevant alarm from the database 130 using the retrieved alarm identifier.
[0079] At step 404, on fetching details of the alarm in the database 130 using the retrieved alarm identifier, the comparator 225 is configured to compare the total count of alarms with the first predefined threshold and the second predefined threshold, respectively.
[0080] At step 406, the load manager 230 is configured to perform the one or more tasks to manage the load of alarms in the NMS 120 based on comparison of the total count of alarms with the first predefined threshold and the second predefined threshold, respectively. In an example, the first predefined threshold is 1000 and the second predefined threshold is 500.
[0081] At step 408, in response to detecting, the total count of alarms being greater than the first predefined threshold, the one or more tasks includes disabling consumption of subsequent one or more alarms until the pre-defined time period is completed. Let us consider for example, the first predefined threshold is 1000, the pre-defined time period is 10 seconds. When the total count of alarms reaches 1001, the consumption of subsequent one or more alarms is disabled until the pre-defined time period is completed. The load manager 230 is further configured to transmit at least one of, the burst critical alert via the SMS or email to the user when the total count of alarms is greater than the first predefined threshold for the pre-defined number of consecutive time intervals.
[0082] In another embodiment, in response to detecting, 1001 total count of alarms being greater than the first predefined threshold 1000the one or more tasks includes disabling, consumption of subsequent one or more alarms until the pre-defined time period is completed. The total count of the alarms including, at least one of, remains constant and decreases.
[0083] At step 410, accordingly, as per the above embodiment, in response to detecting, the total count of alarms being lower than the second predefined threshold, the one or more tasks includes enabling consumption of subsequent one or more alarms until the pre-defined time period is completed. Let us consider for example, the second predefined threshold is 500, the pre-defined time period is 5 seconds. When the total count of alarms reaches 480, the consumption of subsequent one or more alarms is enabled until the pre-defined time period is completed.
[0084] In yet another embodiment, in response to detecting, the 600 total count of alarms being lower than the first predefined threshold 1000 and greater than the second predefined threshold 500, the one or more tasks includes enabling consumption of subsequent one or more alarms until the pre-defined time period is completed. The total count of the alarms increases until the total count of alarms reaches the first pre-defined threshold. If the total count of alarms reaches the first pre-defined threshold, the burst case alert is transmitted to the UE 110.
[0085] In addition to managing the load of alarms, the load manager 230 is further configured to receive delay in consumption of the one or more alarms in the NMS 120 if the total count of alarms in the database 130 is greater than the first predefined threshold. The delay is at least one of, a pre-defined and dynamic.
[0086] In addition to managing the load of alarms, the load manager 230 is configured to manage the load of the alarms in the NMS 120 by introducing the first counter 235 and the second counter 240. The first counter 235 stores the count of consumed alarm records from the message stream. In an embodiment, the consumed alarm records are referred to as the total count of alarms received from the message stream. The second counter 240 stores the count of alarms processed and inserted to the database 130. The load manager 230 is further configured to compare the absolute difference between the second counter 240 and the first counter 235 with the first predefined threshold.
[0087] The load manager 230 is further configured to enable the flag to indicate the threshold breach of the database 130 in response to the comparison when the absolute difference between the second counter 240 and the first counter 235 is greater than the first predefined threshold. In an example, the first predefined threshold is 100, the absolute difference between the second counter 240 and the first counter 235 reaches 101, the load manager 230 enables the flag for indicating the threshold breach of the database 130.
[0088] The load manager 230 is further configured to disable the flag when the absolute difference between the second counter 240 and the first counter 235 is less than the first predefined threshold. In an example, the first predefined threshold is 100, the absolute difference between the second counter 240 and the first counter 235 reaches 81, the load manager 230 disables the flag. Upon disabling the flag, the database 130 receives the one or more alarms until the database 130 reaches the first predefined threshold.
[0089] At step 412, the UE 110 is configured to receive the at least one of, the burst critical alert via the SMS or the email, when the total count of alarms (for e.g., 1001) is greater than the first predefined threshold (for e.g., 1000) for the pre-defined time (for e.g., 10 seconds). The one or more alarms are being held in stream and consumed the availability of resources to ensure all the consumed alarms are being processed properly without any loss.
[0090] FIG. 5 is a schematic representation of an architecture 500 of the system 125 for managing the load of alarms in the NMS 120, according to one or more embodiments of the present disclosure.
[0091] The architecture 500 of the system 125 includes the FP master 505, the FP raise 510, the FP clear 515, the FP retry 520, and the FP callback 525. The FP master 505 is configured to accept the traffic from message stream and communicate with IO Cache for and further segregating the traffic as the raise / clear / retry / call-back.
[0092] The FP raise 510 is configured to accept the traffic and insert into the persistence storage with pre-processing. Further, the FP raise 510 is configured to forward the data further for post-processing after insertion.
[0093] The FP clear 515 is configured to accept the traffic and perform clearance operation and forward the traffic further for termination. The FP clear 515 is configured to produce data to the FP retry 520 for unidentified clearance alarms.
[0094] The FP retry 520 is configured to accept the unidentified clear alarms and try to associate it with raise events with configured number of retries.
[0095] The FP callback 525 is configured to accept the traffic from the processor 205 and update physical/logical enrichment and forward the data further for correlation and TT creation.
[0096] FIG. 6 is a flow diagram illustrating a method 600 for managing the load of alarms in the NMS 120, according to one or more embodiments of the present disclosure.
[0097] At step 605, the method 600 includes the step of fetching the data pertaining to the total count of alarms stored in the database 130 by the fetching unit 220. The alarms are generated by the one or more network elements and stored in the database 130 with the alarm identifier. The fetching unit 220 fetches details of the alarm by retrieving the alarm identifier from the message stream. The fetching unit 220 fetches details of the alarm by fetching the relevant alarm from the database 130 using the retrieved alarm identifier.
[0098] Further, the method 600 includes the step of retrieving the load of the alarms from the message stream by the load manager 230. The load manager 230 is further configured to communicate, with the database 130 pertaining to the load of the alarms. The load manager 230 is further configured to segregate the load as at least one of, a Raise, a Clear, a Retry and a Call-back.
[0099] At step 610, the method 600 includes the step of comparing the total count of alarms with the first predefined threshold and the second predefined threshold, respectively by the comparator 225 upon fetching details of the alarm in the database 130 using the retrieved alarm identifier. In an embodiment, the first predefined threshold and the second predefined threshold are configured by the user.
[00100] At step 615, the method 600 includes the step of performing the one or more tasks to manage the load of alarms in the NMS 120 based on comparison of the total count of alarms with the first predefined threshold and the second predefined threshold, respectively. In an embodiment, in response to detecting, the total count of alarms being greater than the first predefined threshold, the one or more tasks includes disabling consumption of subsequent one or more alarms until a pre-defined time period is completed. The load manager 230 is further configured to transmit at least one of, a burst critical alert via Short Message Service (SMS) or email to the user when the total count of alarms is greater than the first predefined threshold for the pre-defined number of consecutive time intervals.
[00101] Accordingly, as per the above embodiment, in response to detecting, the total count of alarms being lower than the second predefined threshold, the one or more tasks includes enabling consumption of subsequent one or more alarms until the pre-defined time period is completed. In response to detecting, the total count of alarms being lower than the first predefined threshold and greater than the second predefined threshold, the one or more tasks includes enabling, consumption of subsequent one or more alarms until the pre-defined time period is completed. The total count of the alarms increases until the total count of alarms reaches the first pre-defined threshold.
[00102] The method 600 further includes managing the load of alarms in the NMS 120 by introducing a first counter 235 and a second counter 240. The first counter 235 stores a count of consumed alarm records from the message stream. The second counter 240 stores the total count of alarms processed and inserted to the database 130. The load manager 230 is further configured to compare an absolute difference between the second counter 240 and the first counter 235 with the first predefined threshold. In an embodiment, the absolute difference includes, but is not limited to the total count of the alarms which are received and the total count of the alarms which are processed.
[00103] The method 600 further includes enabling a flag to indicate a threshold breach of the database 130 in response to the comparison when the absolute difference between the second counter 240 and the first counter 235 is greater than the first predefined threshold. In an example, the first predefined threshold is 100, the absolute difference between the second counter 240 and the first counter 235 reaches 101, the load manager 230 enables the flag for indicating the threshold breach of the database 130.
[00104] The method 600 further includes enabling disabling the flag when the absolute difference between the second counter 240 and the first counter 235 is lesser than the first predefined threshold. In an example, the first predefined threshold is 100, the absolute difference between the second counter 240 and the first counter 235 reaches 81, the load manager 230 disables the flag. Upon disabling the flag, the database 130 receives the one or more alarms until the database 130 reaches the first predefined threshold. By doing so, the method 500 reduces requirement of the memory space, which in turn keeps the processor 205 in responsive state, with high availability even when the Transaction Per Second (TPS) is very high. The one or more alarms are held in database 130 and consumed the availability of resources such as the processor 205 to ensure all the consumed alarms are being processed properly without any loss.
[00105] The present invention discloses a non-transitory computer-readable medium having stored thereon computer-readable instructions. The computer-readable instructions are executed by a processor 205. The processor 205 is configured to fetch data pertaining to a total count of alarms stored in a database 130. The processor 205 is configured to compare the total count of alarms with a first predefined threshold and a second predefined threshold, respectively. The processor 205 is configured to perform one or more tasks to manage the load of alarms in the NMS 120 based on comparison of the total count of alarms with the first predefined threshold and the second predefined threshold, respectively.
[00106] A person of ordinary skill in the art will readily ascertain that the illustrated embodiments and steps in description and drawings (FIG.1-6) are set out to explain the exemplary embodiments shown, and it should be anticipated that ongoing technological development will change the manner in which particular functions are performed. These examples are presented herein for purposes of illustration, and not limitation. Further, the boundaries of the functional building blocks have been arbitrarily defined herein for the convenience of the description. Alternative boundaries can be defined so long as the specified functions and relationships thereof are appropriately performed. Alternatives (including equivalents, extensions, variations, deviations, etc., of those described herein) will be apparent to persons skilled in the relevant art(s) based on the teachings contained herein. Such alternatives fall within the scope and spirit of the disclosed embodiments.
[00107] The present disclosure incorporates technical advancement of managing the load of alarms in the NMS. The present disclosure perform one or more tasks to manage the load of alarms in the NMS based on comparison of the total count of alarms with the first predefined threshold and the second predefined threshold, respectively. By doing so, the system and method reduces requirement of the memory space, which in turn maintains the processor in responsive state, with high availability even when the Transaction Per Second (TPS) is very high. The one or more alarms are being held in stream and consumed the availability of resources to ensure all the consumed alarms are being processed properly without any loss.
[00108] The present invention offers multiple advantages over the prior art and the above listed are a few examples to emphasize on some of the advantageous features. The listed advantages are to be read in a non-limiting manner.

REFERENCE NUMERALS
[00109] Environment - 100
[00110] Network - 105
[00111] User Equipment - 110
[00112] Server - 115
[00113] NMS - 120
[00114] System - 125
[00115] Database - 130
[00116] One or more processor -205
[00117] Memory – 210
[00118] Interface unit – 215
[00119] Fetching unit- 220
[00120] Comparator- 225
[00121] Load manager- 230
[00122] First counter- 235
[00123] Second counter- 240
[00124] One or more primary processors – 305
[00125] Memory of user equipment – 310
[00126] FP master - 505
[00127] FP raise - 510
[00128] FP clear - 515
[00129] FP retry - 520
[00130] FP call-back- 525
,CLAIMS:
CLAIMS
We Claim:
1. A method (600) for managing load of alarms in a Network Management System (NMS) (120), the method (600) comprises the steps of:
fetching (605), by one or more processors (205), data pertaining to a total count of alarms stored in a database (130);
comparing (610), by the one or more processors (205), the total count of alarms with a first predefined threshold and a second predefined threshold, respectively; and
performing (615), by the one or more processors (205), one or more tasks to manage the load of alarms in the NMS (120) based on comparison of the total count of alarms with the first predefined threshold and the second predefined threshold, respectively.

2. The method (600) as claimed in claim 1, wherein the one or more tasks performed by the one or more processors (205), includes at least one of:
disabling, consumption of subsequent one or more alarms until a pre-defined time period is completed, in response to detecting, the total count of alarms being greater than the first predefined threshold;
enabling, consumption of subsequent one or more alarms until the pre-defined time period is completed, in response to detecting, the total count of alarms being lower than the second predefined threshold;
enabling, consumption of subsequent one or more alarms until the pre-defined time period is completed, in response to detecting, the total count of alarms being lower than the first predefined threshold and greater than the second predefined threshold, and the total count of the alarms increases until the total count of alarms reaches the first pre-defined threshold; and
disabling, consumption of subsequent one or more alarms until the pre-defined time period is completed, in response to detecting, the total count of alarms being greater than the first predefined threshold, and the total count of the alarms at least one of, remains constant and decreases.

3. The method (600) as claimed in claim1, wherein the one or more processors (205) fetches details of the alarm by:
retrieving, an alarm identifier from a message stream; and
fetching, a relevant alarm from the database (130) using the retrieved alarm identifier.

4. The method (600) as claimed in claim 1, wherein the alarms are generated by the one or more network elements and stored in the database (130) with the alarm identifier.

5. The method (600) as claimed in claim 1, wherein the one or more processors (205) communicates with the database (130) to facilitate in maintaining a timestamp array for each alarm, thereby enabling accurate tracking of alarm occurrences.

6. The method (600) as claimed in claim 1, wherein the first predefined threshold and the second predefined threshold are configured by a user.

7. The method (600) as claimed in claim 1, wherein the method (600) further comprises the step of:
transmitting, by the one or more processors (205), at least one of, a burst critical alert via Short Message Service (SMS) or email to the user when the total count of alarms is greater than the first predefined threshold for a pre-defined number of consecutive time intervals.

8. The method (600) as claimed in claim 1, wherein subsequent to the total count of alarms in the database (130) is greater than the first predefined threshold, the one or more processors, delays in consumption of the one or more alarms in the NMS (120) to manage the load of alarms, wherein the delay is at least one of, a pre-defined and dynamic.

9. The method (600) as claimed in claim 1, wherein the method (600) further comprises the step of:
managing the load of the alarms in the NMS (120) by introducing a first counter (235) that stores count of consumed alarm records from the message stream and a second counter (240) that stores the count of alarm records inserted to the database (130).

10. The method (600) as claimed in claim 9, wherein the method (600) further comprises the step of:
comparing, by the one or more processors (205), an absolute difference between the second counter (240) and the first counter (235) with the first predefined threshold;
in response to the comparison, enabling, by the one or more processors (205), a flag to indicate a threshold breach of the database (130) when the absolute difference between the second counter (240) and the first counter (235) is greater than the first predefined threshold; and
disabling, by the one or more processors (205), the flag when the absolute difference between the second counter (240) and the first counter (235) is less than the first predefined threshold.

11. The method (600) as claimed in claim 1, wherein the method (600) further comprises the steps of:
retrieving, by the one or more processors (205), load of the alarms from the message stream;
communicating, by the one or more processors (205), with the database (130) pertaining to the load of the alarms; and
segregating, by the one or more processors (205), the load as at least one of, a Raise, a Clear, a Retry and a Call-back.

12. A system (125) for managing load of alarms in a Network Management System (NMS) (120), the system (125) comprising:
a fetching unit (220) configured to fetch, data pertaining to a total count of alarms stored in a database (130);
a comparator (225) configured to compare, the total count of alarms with a first predefined threshold and a second predefined threshold, respectively; and
a load manager (230) configured to perform, one or more tasks to manage the load of alarms in the NMS (120) based on comparison of the total count of alarms with the first predefined threshold and the second predefined threshold, respectively.

13. The system (125) as claimed in claim 12, wherein the one or more tasks performed by the load manager (230), includes at least one of:
disabling, consumption of subsequent one or more alarms until a pre-defined time period is completed, in response to detecting, the total count of alarms being greater than the first predefined threshold;
enabling, consumption of subsequent one or more alarms until the pre-defined time period is completed, in response to detecting, the total count of alarms being lower than the second predefined threshold;
enabling, consumption of subsequent one or more alarms until the pre-defined time period is completed, in response to detecting, the total count of alarms being lower than the first predefined threshold and greater than the second predefined threshold, and the total count of the alarms increases until the total count of alarms reaches the first pre-defined threshold; and
disabling, consumption of subsequent one or more alarms until the pre-defined time period is completed, in response to detecting, the total count of alarms being greater than the first predefined threshold, and the total count of the alarms at least one of, remains constant and decreases.

14. The system (125) as claimed in claim 12, wherein the fetching unit (220) fetches details of the alarm by:
retrieving, an alarm identifier from a message stream; and
fetching, a relevant alarm from the database (130) using the retrieved alarm identifier.

15. The system (125) as claimed in claim 12, wherein the alarms are generated by the one or more network elements and stored in the database (130) with an alarm identifier.

16. The system (125) as claimed in claim 12, wherein the load manager (230) communicates with the database (130) to facilitate in maintaining a timestamp array for each alarm, thereby enabling accurate tracking of alarm occurrences.

17. The system (125) as claimed in claim 12, wherein the first predefined threshold and the second predefined threshold are configured by a user.

18. The system (125) as claimed in claim 12, wherein the load manager (230) is further configured to:
transmit, at least one of, a burst critical alert via Short Message Service (SMS) or email to the user when the total count of alarms is greater than the first predefined threshold for a pre-defined number of consecutive time intervals.

19. The system (125) as claimed in claim 12, wherein subsequent to the total count of alarms in the database (130) is greater than the first predefined threshold, the load manager (230), delays in consumption of the one or more alarms in the NMS (120) to manage the load of alarms, wherein the delay is at least one of, a pre-defined and dynamic.

20. The system (125) as claimed in claim 12, wherein the load manager (230) is further configured to:
manage load of the alarms in the NMS (120) by introducing a first counter (235) that stores count of consumed alarm records from the message stream and a second counter (240) that stores the count of alarm records inserted to the database.

21. The system (125) as claimed in claim 20, wherein the load manager (230) is further configured to:
compare, an absolute difference between the second counter (240) and the first counter (235) with the first predefined threshold;
in response to the comparison, enables, a flag to indicate a threshold breach of the database (130) when the absolute difference between the second counter (240) and the first counter (235) is greater than the first predefined threshold; and
disables, the flag when the absolute difference between the second counter (240) and the first counter (235) is less than the first predefined threshold.

22. The system (125) as claimed in claim 12, wherein the load manager (230) is further configured to:
retrieve, load of the alarms from the message stream;
communicate, with the database (130) pertaining to the load of the alarms; and
segregate, the load as at least one of, a Raise, a Clear, a Retry and a Call-back.

23. A User Equipment (UE) (110), comprising:
one or more primary processors (305) communicatively coupled to the one or more processors (205), the one or more primary processors (305) coupled with a memory unit (310), wherein said memory unit (310) stores instructions which when executed by the one or more primary processors (305) causes the UE (110) to:
receive, at least one of, a burst critical alert via Short Message Service (SMS) or email, when a total count of alarms is greater than a first predefined threshold for a pre-defined time;
wherein the one or more processors (205) is configured to perform the steps as claimed in claim 1.