DESC:FORM 2
THE PATENTS ACT, 1970 (39 OF 1970)
&
THE PATENT RULES, 2003
COMPLETE SPECIFICATION
(See section 10 and rule 13)

SYSTEM AND METHODS FOR VISUALIZING LIVE ALARMS OF NODES IN COMMUNICATION NETWORKS

Jio Platforms Limited, an Indian company, having registered address at Office -101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India

The following specification particularly describes the invention and the manner in which it is to be performed.

TECHNICAL FIELD
[0001] The embodiments of the present disclosure generally relate to the field of wireless communication systems. More particularly, the present disclosure relates to a system and method for visualizing live alarms of nodes in a communication network.
BACKGROUND OF THE INVENTION
[0002] The subject matter disclosed in the background section should not be assumed or construed to be prior art merely because of its mention in the background section. Similarly, any problem statement mentioned in the background section or its association with the subject matter of the background section should not be assumed or construed to have been previously recognized in the prior art.
[0003] In the realm of wireless communication networks, efficient operation of a communication network is of utmost importance to ensure seamless communication and uninterrupted services to end users. To this end, Network Operations Centers (NOCs) play a crucial role by monitoring and visualizing performance of Network Elements (NEs) or nodes with the service-affecting events or alarms, through an NOC terminal and taking corrective actions if needed. The NOC refers to a centralized location where network administrators monitor and manage architecture and infrastructure of deployed communication networks. The monitoring of the performance of the NEs or the nodes using the NOC terminal provides individual site wise details of the NEs or the nodes to the network administrators.
[0004] However, it is difficult for the network administrators to assess an impact of the service-affecting events or the alarms on a particular geography as there may be multiple vendor Element Management Systems (EMSs), and NOC engineers or the network administrators have to login to multiple EMSs and monitor the performance of the NEs or the nodes where the service-affecting events or alarms are present.
[0005] Further, a service area of the communication network is divided into a number of geographies which again have been bifurcated into multiple maintenance clusters and business clusters for administrative purposes. To this end, various types of conventional systems are prevalent nowadays for visualizing performance of the NEs or the nodes, which offer only individual site-wise details of alarms and does not offer a holistic view of outage patterns across different geographies. Additionally, the conventional systems are not user-friendly and do not include options using which the network administrators can manage the broader geographical implications of incidents such as outages alarms, active alarm ageing, performance degradation, or failure of nodes, which impacts the performance of the communication network, thus, resulting in a degraded user experience.
[0006] The aforementioned limitations of the conventional systems for visualizing the performance of the NEs further hamper the ability of the network administrators to analyze data related to alarms, which is important for minimizing service disruptions and optimizing network performance. Additionally, the conventional systems for visualizing performance of the NEs do not provide any interactive mapping features which again limits the ability of the network administrators to visualize a spatial distribution of network alarms.
[0007] Therefore, there lies a need for an improved method and system that can overcome the above-mentioned shortcomings associated with the conventional systems for visualizing alarms in the communication network.
SUMMARY OF THE INEVNTION
[0008] The following embodiments present a simplified summary in order to provide a basic understanding of some aspects of the disclosed invention. This summary is not an extensive overview, and it is not intended to identify key/critical elements or to delineate the scope thereof. Its sole purpose is to present some concepts in a simplified form as a prelude to the more detailed description that is presented later.
[0009] In an embodiment, disclosed herein is a method for visualizing live alarms of a plurality of nodes in a communication network. The method comprises receiving, by a receiving module from a user device, an input for visualizing the live alarms of the plurality of nodes within a service area of the communication network, and fetching, by a data extraction module from a database, live alarm data associated with the plurality of nodes based on the input. Further, the method comprises determining, by a data processing module, for one or more geographical locations within the service area, a count of a set of outage nodes among the plurality of nodes and a count of a set of performance degraded nodes among the plurality of nodes based on the fetched live alarm data. The set of outage nodes includes outage alarms, and the set of performance degraded nodes includes performance degraded alarms. Furthermore, the method comprises generating, by the data processing module, at least one of a live alarm outage report or a live alarm ageing information report based on at least one of the determined count of the set of outage nodes or the determined count of the set of performance degraded nodes. The live alarm outage report comprises information indicating the determined count of the set of outage nodes for the one or more geographical locations, and the live alarm ageing information report comprises information indicating ageing of the outage alarms and the performance degraded alarms for the one or more geographical locations at a plurality of predefined time slots. Thereafter, the method comprises displaying, by a display module, the at least one of the live alarm outage report or the live alarm ageing information report on an interface of the user device.
[0010] In an aspect, the method further comprises displaying, by the display module on the interface of the user device, a plurality of selectable report generation options including a first selectable option for generating the live alarm outage report and a second selectable option for generating the live alarm ageing information report. The live alarm outage report is generated upon receiving the input via the first selectable option and the live alarm ageing information report is generated upon receiving the input via the second selectable option. The live alarm data comprises at least one of alarm identification information, node related information, alarm related details, real-time performance metrics, connectivity information, and alarm correlation data.
[0011] In one or more aspects, the live alarm outage report comprises information related to one or more of event timestamps associated with the outage alarms, one or more vendors, an Identifier (ID) of each of the set of outage nodes, a type of site corresponding to each outage node of the set of outage nodes, an alarm ID of each of the outage alarms, and a name of each of the outage alarms.
[0012] In an aspect, the method further comprises displaying, by the display module on the interface, the determined count of the set of outage nodes for the one or more geographical locations in a descending order.
[0013] In an aspect, the method further comprises determining, by the data processing module based on the fetched live alarm data, a count of the outage alarms in each maintenance cluster of a plurality of maintenance clusters within the service area, and generating, by the data processing module, the live alarm outage report based on the determined count the outage alarms in each maintenance cluster of the plurality of maintenance clusters.
[0014] In one or more aspects, the database corresponds to one of a relational database, a non-relational database, a time-series database, a distributed file system, a cloud-based database, an in-memory database, a file based storage system, an event-driven database, or a hybrid database.
[0015] In one or more aspects, the method comprises displaying, by the display module on the interface, a hierarchical navigation tab for visualizing the count of the set of outage nodes and the count of the set of performance degraded nodes across hierarchical geographical levels including the service area, maintenance clusters within the service area, and a node level. Thereafter, the method comprises navigating, by the display module based on a reception of an input via the displayed hierarchical navigation tab, between a display of the count of the set of outage nodes and the count of the set of performance degraded nodes across the hierarchical geographical levels.
[0016] In one or more aspects, the method comprises dynamically updating, by the data processing module, the live alarm ageing information report when an input indicating one of a selection of a geographical level from the hierarchical geographical levels is received via the displayed hierarchical navigation tab.
[0017] In another embodiment, disclosed herein is a system for visualizing live alarms of a plurality of nodes in a communication network. The system comprises a receiving module, a data extraction module, a data processing module, and a display module. The receiving module is configured to receive, from a user device, an input for visualizing the live alarms of the plurality of nodes within a service area of the communication network. The data extraction module is configured to fetch, from a database, live alarm data associated with the plurality of nodes based on the input. The data processing module is configured to determine, for one or more geographical locations within the service area, a count of a set of outage nodes among the plurality of nodes and a count of a set of performance degraded nodes among the plurality of nodes based on the fetched live alarm data. The set of outage nodes includes outage alarms, and the set of performance degraded nodes includes performance degraded alarms. The data processing module is further configured to generate at least one of a live alarm outage report or a live alarm ageing information report based on at least one of the determined count of the set of outage nodes or the determined count of the set of performance degraded nodes. The live alarm outage report comprises information indicating the determined count of the set of outage nodes for the one or more geographical locations, and the live alarm ageing information report comprises information indicating ageing of the outage alarms and the performance degraded alarms for the one or more geographical locations at a plurality of predefined time slots. The display module is configured to display the at least one of the live alarm outage report or the live alarm ageing information report on an interface of the user device.
[0018] In an aspect, the data processing module is further configured to control the display module to display, on the interface of the user device, a plurality of selectable report generation options including a first selectable option for generating the live alarm outage report and a second selectable option for generating the live alarm ageing information report.
[0019] In an aspect, the data processing module is further configured to control the display module to display, on the interface, the determined count of the set of outage nodes for the one or more geographical locations in a descending order.
[0020] In an aspect, the data processing module is further configured to determine, based on the fetched live alarm data, a count of the outage alarms in each maintenance cluster of a plurality of maintenance clusters within the service area, and generate the live alarm outage report based on the determined count the outage alarms in each maintenance cluster of the plurality of maintenance clusters.
[0021] In an aspect, the display module is further configured to display, on the interface of the user device, a hierarchical navigation tab for visualizing the count of the set of outage nodes and the count of the set of performance degraded nodes across hierarchical geographical levels including the service area, maintenance clusters within the service area, and a node level. Thereafter, the display module is configured to navigate, based on a reception of an input via the displayed hierarchical navigation tab, between a display of the count of the set of outage nodes and the count of the set of performance degraded nodes across the hierarchical geographical levels.
[0022] In an aspect, the data processing module is further configured to dynamically update the live alarm ageing information report when an input indicating one of a selection of a geographical level from the hierarchical geographical levels is received via the displayed hierarchical navigation tab.
BRIEF DESCRIPTION OF DRAWINGS
[0023] Various embodiments disclosed herein will become better understood from the following detailed description when read with the accompanying drawings. The accompanying drawings constitute a part of the present disclosure and illustrate certain non-limiting embodiments of inventive concepts disclosed herein. Further, components and elements shown in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. For consistency and ease of understanding, similar components and elements are annotated by reference numerals in the exemplary drawings. In the drawings:
[0024] FIG. 1 illustrates an exemplary communication network, in accordance with an example embodiment of the present disclosure.
[0025] FIG. 2 illustrates an exemplary block diagram depicting a system architecture of a server for visualizing live alarms of nodes in the communication network, in accordance with an embodiment of the present disclosure.
[0026] FIG. 3 illustrates a flowchart of a method for visualizing the live alarms of nodes in the communication network, in accordance with an embodiment of the present disclosure.
[0027] FIG. 4 illustrates a flowchart of a method for updating live alarm ageing information report, in accordance with an embodiment of the present disclosure.
[0028] FIG. 5 illustrates an example Graphics User Interface (GUI) for visualizing outage sites pattern across different geographies, in accordance with an embodiment of the present disclosure.
[0029] FIG. 6 illustrates another example GUI for visualizing ageing of alarms in the communication network, in accordance with an embodiment of the present disclosure.
[0030] FIG. 7 illustrates another example GUI for visualizing maintenance cluster wise count of the outage sites for one or more vendors, in accordance with an embodiment of the present disclosure.
[0031] FIG. 8 illustrates an example GUI depicting an example of the outage site report for a maintenance cluster selected by an end user, in accordance with an embodiment of the present disclosure.
[0032] FIG. 9 is a block diagram depicting an example computer system in which embodiments of the present disclosure may be implemented.
DETAILED DESCRIPTION OF THE INVENTION
[0033] Inventive concepts of the present disclosure will now be described more fully hereinafter with reference to the accompanying drawings, in which examples of one or more embodiments of inventive concepts are shown. Inventive concepts may, however, be embodied in different forms and should not be construed as limited to the embodiments set forth herein. Further, the one or more embodiments disclosed herein are provided to describe the inventive concept thoroughly and completely, and to fully convey the scope of each of the present inventive concepts to those skilled in the art. Furthermore, it should be noted that the embodiments disclosed herein are not mutually exclusive concepts. Accordingly, one or more components from one embodiment may be tacitly assumed to be present or used in any other embodiment.
[0034] The following description presents various embodiments of the present disclosure. The embodiments disclosed herein are presented as teaching examples and are not to be construed as limiting the scope of the present disclosure. The present disclosure should in no way be limited to the illustrative implementations, drawings, and techniques illustrated below, including the exemplary design and implementation illustrated and described herein, but may be modified, omitted, or expanded upon without departing from the scope of the present disclosure.
[0035] The following description contains specific information pertaining to embodiments in the present disclosure. The detailed description uses the phrases “in some embodiments” which may each refer to one or more or all of the same or different embodiments. The term “some” as used herein is defined as “one, or more than one, or all.” Accordingly, the terms “one,” “more than one,” “more than one, but not all” or “all” would all fall under the definition of “some.” In view of the same, the terms, for example, “in an embodiment” refers to one embodiment and the term, for example, “in one or more embodiments” refers to “at least one embodiment, or more than one embodiment, or all embodiments.”
[0036] The term “comprising,” when utilized, means “including, but not necessarily limited to;” it specifically indicates open-ended inclusion in the so-described one or more listed features, elements in a combination, unless otherwise stated with limiting language. Furthermore, to the extent that the terms “includes,” “has,” “have,” “contains,” and other similar words are used in either the detailed description, such terms are intended to be inclusive in a manner similar to the term “comprising.”
[0037] In the following description, for the purposes of explanation, various specific details are set forth in order to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific details. Several features described hereafter can each be used independently of one another or with any combination of other features.
[0038] The description provided herein discloses exemplary embodiments only and is not intended to limit the scope, applicability, or configuration of the present disclosure. Rather, the foregoing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing any of the exemplary embodiments. Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it may be understood by one of the ordinary skilled in the art that the embodiments disclosed herein may be practiced without these specific details.
[0039] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. As used herein the description, the singular forms "a", "an", and "the" include plural forms unless the context of the invention indicates otherwise.
[0040] The terminology and structure employed herein are for describing, teaching, and illuminating some embodiments and their specific features and elements and do not limit, restrict, or reduce the scope of the present disclosure. Accordingly, unless otherwise defined, all terms, and especially any technical and/or scientific terms, used herein may be taken to have the same meaning as commonly understood by one having ordinary skill in the art.
[0041] An object of the present disclosure is to provide a method and system that can provide a network operations team with a holistic view of a performance of a communication network using which the network operations team can visualize count of nodes having service affecting alarms for each of geographies in the communication network.
[0042] Another object of the present disclosure is to provide a system and method using which top management, a field engineer, or a network operations team can visualize and monitor outage sites and ageing of alarms in the communication network in near real time through a graphical view and can drill down from service area level view to maintenance/business cluster view to node level view.
[0043] Yet, another object of the present disclosure is to provide, for the network administrator or an end user, a Graphical User Interface (GUI) that includes options corresponding to a single glass pane view of the count of nodes that includes the service affecting alarms at any geographical level.
[0044] In the disclosure, various embodiments are described using terms used in some communication standards (e.g., 3rd Generation Partnership Project (3GPP), Extensible Radio Access Network (xRAN), and Open-Radio Access Network (O-RAN)), but these are merely examples for description. Various embodiments of the disclosure may also be easily modified and applied to other communication systems.
[0045] In order to facilitate an understanding of the disclosed invention, a number of terms are defined below.
[0046] A service area refers to a geographical region covered by a group of cells in the communication network. The service area may be determined using the radio coverage provided by base stations in a communication network. For example, the service area of a single cell in a network environment may be a few kilometers in radius.
[0047] A performance degraded alarm refers to an alarm generated by a network element or a network management system indicating a condition that performance of a network node or network resource has deteriorated beyond a predefined threshold level but not resulted in a complete failure. Such alarm server as early warning to network administrator or network engineer for enabling prompt attention in order to prevent one or more service disruptions.
[0048] An outage alarm signifies a total loss of service in a specific network area or cell. A cell outage refers to a total loss of radio services in a coverage area of a cell. The outage alarms are critical as they indicate complete service disruption at any node in the communication network, requiring immediate remediation.
[0049] An outage node refers to a node that includes one or more outage alarms, and a performance degraded nodes refers to a node that includes one or more performance degraded alarms.
[0050] A type of site refers to a classification of nodes based on their functionality, deployment characteristics, and coverage region. Examples of the type of site may include, but not limited to, a macrocell site, a microcell site, a small cell site, and a repeater site.
[0051] The EMS refers to an intermediary entity between network nodes and a Network Management System (NMS) within the communication network. The EMS is responsible for collecting and aggregating performance measurements and generated alarms/events from individual network elements such as base stations/nodes of a specific vendor, and transferring the collected data to the NMS. The NMS may refer to a system responsible for monitoring and optimizing operations of the network elements.
[0052] A vendor EMS cluster refers to a group of multiple vendor-specific EMSs, where each vendor-specific EMS is responsible for managing the network elements of a particular vendor. The vendor EMS cluster may provide a centralized control over the network elements from different vendors for performing vendor-specific management functionalities in the communication network.
[0053] The following description provides specific details of certain aspects of the disclosure illustrated in the drawings to provide a thorough understanding of those aspects. It should be recognized, however, that the present disclosure can be reflected in additional aspects and the disclosure may be practiced without some of the details in the following description.
[0054] Embodiments of the present disclosure will be described below in detail with reference to the accompanying drawings. FIG. 1 through FIG. 9, discussed below, and the one or more embodiments used to describe the principles of the present disclosure are by way of illustration only and should not be construed in any way to limit the scope of the present disclosure. Those skilled in the art will understand that the principles of the present disclosure may be implemented in any suitably arranged system or device.
[0055] FIG. 1 illustrates an exemplary communication network 100, in accordance with an embodiment of the present disclosure. The embodiment of the communication network 100 shown in FIG. 1 is for illustration only. Other embodiments of the communication network 100 may be used without departing from the scope of this disclosure.
[0056] As shown in FIG. 1, the communication network 100 includes a vendor EMS cluster 110 including a plurality of vendor EMSs 102' through 108', where each vendor EMS is managing one or more nodes (e.g., one or more base stations). For instance, nodes 102, 104, 106, and 108 are shown in FIG. 1 for exemplary purpose, without departing form the scope of the present disclosure. Depending on the network type, the term “nodes” may refer to any component (or collection of components) configured to provide wireless access to a network, such as Transmit Point (TP), Transmit-Receive point (TRP), an Evolved Base Station (eNodeB or eNB), a 5G/NR base station (gNB), a macrocell, a femtocell, a Wi-Fi Access Point (AP), or other wirelessly enabled devices. The nodes and vendor EMSs may communicate with each other via wireless communication protocols, e.g., 5G/NR 3GPP New Radio interface/access (NR), Long Term Evolution (LTE), LTE advanced (LTE-A), High Speed Packet Access (HSPA), Wi-Fi 802.11a/b/g/n/ac, etc. For the sake of convenience, the terms “base station” and “node” are used interchangeably in the present disclosure to refer to network infrastructure components that provide wireless access to remote terminals.
[0057] Each of the vendor EMSs 102’ through 108’ (hereinafter also referred to as ‘the EMS’) may be configured to monitor, manage, and control individual Network Elements (NEs) within the communication network 100. Each of the vendor EMSs 102’ through 108’ may be controlled by one or more EMS server(s).
[0058] The communication network 100 further includes a network 120, a load balancer 130, a server 140, a distributed file system 150, a user device 160, and a gateway 170. The server 140 is connected to the vendor EMS cluster 110 via the network 120 followed by the load balancer 130. The network 120 may correspond to one of an Internet, a proprietary Internet Protocol (IP) network, or other data network. The load balancer 130 is an intermediary between the network 120 and the server 140. The load balancer 130 is configured to distribute incoming alarm data from the vendor EMS cluster 110 to one or more parsers 225 (hereinafter also referred to as the “parser 225”) (shown in FIG. 2 described below) of the server 140 for efficient parallel processing.
[0059] The server 140 is configured to process the alarm data incoming from the vendor EMS cluster 110 in real time for generating live alarm outage report and live alarm ageing information report for a particular geography within the communication network 100.
[0060] The distributed file system 150 may correspond to an external file system or a file system integrated within the server 140 for storing the live alarm outage report and the live alarm ageing information report and other operational data. In a non-limiting example, the distributed file system 150 may be a cloud-based storage system, a Network File System (NFS), or a distributed database.
[0061] The user device 160 corresponds to a device used by a network operation team or an end user. Further, depending on the network type, the term “user device 160” may refer to any component such as “mobile station,” “subscriber station,” “remote terminal,” “wireless terminal,” or “receive point,”. The user device 160 includes a user interface 160-1 (hereinafter also referred to as “GUI 160-1) and a communication unit 160-2. In a non-limiting example, the user interface 160-1 may facilitate display of one of data related to the live alarm outage report including outage sites view depicting the geography wise ageing of the outage and the performance degrading alarms or data related to the live alarm ageing information report.
[0062] The communication unit 160-2 may include a plurality of antennas, a plurality of Radio Frequency (RF) transceivers, a transmit processing circuitry, and a receive processing circuitry. Additionally, the user device 160 may further include circuitry, programing, applications, or a combination thereof.
[0063] The gateway 170 between the user device 160 and the server 140 may be referred to as an interface unit, and may be located on the network 120. In other embodiments, a plurality of gateways may be deployed on the network 120. In other embodiments, the gateway 170 may be located at any point in the network or network communications path between the user device 160 and the server 140.
[0064] Although FIG. 1 illustrates one example of the communication network 100, various changes may be made to FIG. 1. For example, the communication network 100 may include any number of vendor EMS, nodes, communication gateways, servers, and user devices in any suitable arrangement. Further, various components in FIG. 1 may be combined, further subdivided, or omitted and additional components may be added according to particular needs.
[0065] FIG. 2 illustrates an exemplary block diagram depicting a system architecture of the server 140, in accordance with an example embodiment of the present disclosure. The embodiment of the server 140 as shown in FIG. 2 is for illustration only. However, the server 140 may come in a wide variety of configurations, and FIG. 2 does not limit the scope of the present disclosure to any particular implementation of the server 140.
[0066] As shown in FIG. 2, the server 140 includes one or more processors 210 (hereinafter also referred to as “processor 210”), a memory 215, a communication interface 220, one or more parsers 225 (hereinafter also referred to as the “parser 225”) an interface(s) 230, a processing unit(s)/modules(s) 260, and a database 270. These components may be in electronic communication via one or more buses (e.g., bus 280).
[0067] The processor 210 may include a plurality of processing engines i.e., information processing task executors for efficient parallel processing of the live alarm data of the nodes that includes the service affecting alarms. The one or more components of the server 140 are communicatively coupled with the processor 210 (described below) to process the live alarm data incoming from the EMSs efficiently and generate the live alarm visualization data. The processor 210 may further include various processing circuitry and configured to execute programs or computer readable instructions stored in the memory 215. The processor 210 may also include an intelligent hardware device including a general-purpose processor, such as, for example, and without limitation, a Central Processing Unit (CPU), an Application Processor (AP), a dedicated processor, or the like, a graphics-only processing unit such as a Graphics Processing Unit (GPU), a microcontroller, a Field-Programmable Gate Array (FPGA), a programmable logic device, a discrete hardware component, or any combination thereof. In some cases, the processor 210 may be configured to operate a memory array using a memory controller. In some cases, a memory controller may be integrated into the processor 210. The processor 210 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 215) to cause the server 140 to perform various functions (e.g., determining a count of outage nodes and performance degrading nodes among the nodes in the communication network 100, and generating a live alarm outage report or a live alarm ageing information report using which the field engineer or the network operations team can visualize and monitor outage sites and ageing of alarms in the communication network 100 efficiently).
[0068] The memory 215 is communicatively coupled to the processor 210. A part of the memory 215 may include a RAM, and another part of the memory 215 may include a flash memory or other ROM. The memory 215 is configured to store a set of instructions required by the processor 210 for controlling overall operations of the server 140. The memory 215 may include non-volatile storage elements. Examples of such non-volatile storage elements may include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories. In addition, the memory 215 may, in some examples, be considered a non-transitory storage medium. The "non-transitory" storage medium is not embodied in a carrier wave or a propagated signal. However, the term "non-transitory" should not be interpreted that the memory 215 is non-movable. In some examples, the memory 215 can be configured to store larger amounts of information. In certain examples, a non-transitory storage medium may store data that can, over time, change (e.g., in Random Access Memory (RAM) or cache). The memory 215 can be an internal storage unit or it can be an external storage unit of the server 140, cloud storage, or any other type of external storage.
[0069] More specifically, the memory 215 may store computer-readable instructions 215A including instructions that, when executed by a processor (e.g., the processor 210) cause the server 140 to perform various functions described herein. In some cases, the memory 215 may contain, among other things, a BIOS which may control basic hardware or software operation such as the interaction with peripheral components or devices.
[0070] The communication interface 220 includes an electronic circuit specific to a standard that enables wired or wireless communication. The communication interface 220 is configured to communicate internally between internal hardware components and with external devices via one or more networks. The communication interface 220 may be configured to enable the nodes to communicate with various entities of the communication network 100 (such as UEs, nodes, and databases and in some scenarios external user device) via the network 120. Examples of the communication interface 220 may include, but are not limited to, a modem, a network interface such as an Ethernet card, a communication port, and/or a Personal Computer Memory Card International Association (PCMCIA) slot and card, an antenna, a radio frequency (RF) transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a coder-decoder (CODEC) chipset, a subscriber identity module (SIM) card, and a local buffer circuit. It will be apparent to a person of ordinary skill in the art that the communication interface 220 may include any device and/or apparatus capable of providing wireless or wired communications between the server 140 and various other entities of the communication network 100.
[0071] The parser 225 is configured to parse and extract information from the incoming alarm data, decode a format of the alarm data, and transform raw live alarm data into structured records for further processing.
[0072] The interface 230 may include suitable logic, circuitry, a variety of interfaces, and/or codes that may be configured to receive input(s) and present (or display) output(s) on a display interface or a Graphical User Interface (GUI). The variety of interfaces may include interfaces for data input and output devices, referred to as I/O devices, storage devices, and the like. For example, the I/O interface may have an input interface and an output interface. The interface 230 may facilitate communication of the server 140 with various devices connected to it. The interface 230 may also provide a communication pathway for one or more components of the server 140. Examples of such components include, but are not limited to, the parser 225, the processing module(s) 260, and the database 270.
[0073] In one or more embodiments, the processing module(s) 260 may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the server 140. In non-limiting examples, described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processing modules(s) 260 may be processor-executable instructions stored on a non-transitory machine-readable storage medium and the hardware for the processor 210 may comprise a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the machine-readable storage medium may store instructions that, when executed by the processing resource, implement the processing module(s) 260. In such examples, the server 140 may also comprise the machine-readable storage medium storing the instructions and the processing resource to execute the instructions, or the machine-readable storage medium may be separate but accessible to the server 140 and the processing resource. In other examples, the processing module(s) 260 may be implemented using an electronic circuitry.
[0074] In one or more embodiments, the processing module(s) 260 may include one or more units/modules selected from any of a receiving module 242, a transmitting module 244, a data extraction module 246, a data processing module 248, a display module 250, and other units/modules 252 (not shown). The other units/modules 252 may include, but are not limited to, a scheduler, a monitoring module, a data analytics module, and the like.
[0075] In an aspect, the processor 210, using the receiving module 242, is configured to receive live alarm data associated with all the nodes (i.e., nodes 102 through 108) from the EMS cluster 110. The alarms at the nodes may be monitored by the one or more EMSs of the vendor EMS cluster 110, and the live alarm data collected as a result of the monitoring process may be stored as the live alarm data in the database 270. Further, the processor 210, using the receiving module 242, may also store the live alarm data received from the EMS cluster 110 in the database 270. The live alarm data comprises one or more of alarm identification information, node related information, alarm related details, real-time performance metrics, connectivity information, and alarm correlation data associated with the nodes within the communication network 100.
[0076] In an embodiment, the processor 210, using the receiving module 242, is configured to receive, via the UI 160-1 of the user device 160, an input for visualizing the live alarms of the nodes (i.e., nodes 102 through 108) within a service area of the communication network 100. Further, the processor 210 using the data extraction module 246, fetch live alarm data associated with each of the nodes in the communication network 110 from the database 270 based on the input. Further, the processor 210 may also utilize the scheduler to fetch the live alarm data from the database 270 at periodic time intervals, for example, after every 15 minutes, 30 minutes, or 1 hour.
[0077] Further, the processor 210, using the data processing module 248, is configured to determine a count of a set of outage nodes/sites and a count of performance degraded nodes among the nodes (for example, nodes 102 may be determined as an outage node and nodes (104, 106) may be determined as the performance degraded nodes among the nodes 102 through 108) based on the live alarm data fetched from the database 270. The set of outage nodes refers to the nodes that include outage alarms, and the set of performance degraded nodes refers to the nodes that includes performance degraded alarms. It is to be noted that the terms “outage nodes” and “outage sites” are used interchangeably throughout the disclosure and have same meaning. Unless otherwise specified, these terms should be understood to encompass any variations or equivalents within the scope of the present disclosure.
[0078] Furthermore, the processor 210, using the data processing module 248, is configured to generate the live alarm outage report or the live alarm ageing information report based on the determined count of the set of outage nodes or the determined count of the set of performance degraded nodes. The live alarm outage report comprises information indicating the determined count of the set of outage nodes for the one or more geographical locations within the service area selected by the end user. The live alarm outage report may further comprise, but not limited to, information related to one or more of event timestamps associated with the outage alarms, one or more vendors, an Identifier (ID) of each of the set of outage nodes, a type of site corresponding to each outage node of the set of outage nodes, an alarm ID of each of the outage alarms, a name of each of the outage alarms. The live alarm ageing information report comprises information indicating ageing of the outage alarms and the performance degraded alarms for the one or more geographical locations at predefined time slots (described below with reference to FIG. 6).
[0079] The live alarm ageing of the outage alarms and the performance degraded alarms refers to real-time tracking of alarms duration during which the alarms remains active at the outage nodes or the performance degraded nodes, and the live alarm ageing information report may provide time-stamped details on time of initiation of the outage alarms or the performance degradation alarms, total duration in which the outage alarms or the performance degraded alarms have been active, and the time-based categorization of the outage alarms or the performance degraded alarms into pre-defined time slots (for example, alarms active for 0-2 hours, 2-6 hours, 6-12 hours, or more than 24 hours). Such real-time tracking can help the network operation team to prioritize responses to ensure that long-duration outages can be received immediate attention to minimize the service disruption.
[0080] Furthermore, the processor 210, using the display module 250, is configured to display the live alarm outage report or the live alarm ageing information report on the UI 160-1 of the user device 160. To render the visual representation of the live alarm outage report or the live alarm ageing information report, the processor 210 may control the display module 250 to display, on the UI 160-1 of the user device 160, a hierarchical navigation tab for visualizing the count of the set of outage nodes and the count of the set of performance degraded nodes across hierarchical geographical levels for example, at a service area level, at maintenance cluster level within the service area, and at a node level. When an input from the end user is received from the user device 160 via the displayed hierarchical navigation tab, the processor 210 may further control the display module 250 to navigate between a display of the count of the set of outage nodes and the count of the set of performance degraded nodes across the hierarchical geographical levels.
[0081] In an embodiment, the processor 210, using the data processing module 248, is configured to dynamically update the live alarm ageing information report when the input indicating a selection of a geographical level from the hierarchical geographical levels is received by the receiving module 242 from the user device 160 via the displayed hierarchical navigation tab.
[0082] In an embodiment, the processor 210, using the transmitting module 244, may send the generated live alarm outage report or live alarm ageing information report to the user device 160 when a downloading request is received by the receiving module 242 from the user device 160.
[0083] In an embodiment, the processor 210 using the data processing module 248 may control the display module 250 to display the determined count of the set of outage nodes for the one or more geographical locations in a descending order, on the UI 160-1 of the user device 160.
[0084] In an embodiment, the processor 210 using the data processing module 248 may determine, based on the fetched live alarm data, a count of the outage alarms in each maintenance cluster of maintenance clusters within the service area selected by the end user, and may further generate the live alarm outage report based on the determined count the outage alarms in each maintenance cluster.
[0085] The database 270 may correspond to a centralized database system configured to store and manage real-time alarm data. The database 270 is configured to maintain a comprehensive record of data corresponding to the outage alarms or active alarm ageing data, geography wise live alarm ageing data, data corresponding to geography wise and maintenance cluster wise count of the outage nodes/sites, and associated metadata. In a non-limiting example, the database 270 may correspond, but not limited to, a relational database, a non-relational database, a time-series database, a distributed file system, a cloud-based database, an in-memory database, a file based storage system, an event-driven database, or a hybrid database.
[0086] Although FIG. 2 illustrates one example of the server 140, various changes may be made to FIG. 2. Further, the server 140 may include any number of components in addition to those shown in FIG. 2, without deviating from the scope of the present disclosure. For example, the server 140 may include a console host to control devices that communicates with the server 140 via a wired or a wireless medium or the server 140 may be coupled to an external database that provides data storage space to the server 140. Further, various components in FIG. 2 may be combined, further subdivided, or omitted, and additional components may be added according to particular needs.
[0087] FIG. 3 illustrates a flowchart of a method 300 for visualizing the live alarms of nodes (for example, nodes 102 through 108) in the communication network 100, in accordance with an embodiment of the present disclosure. The method 300 comprises a series of operation steps indicated by blocks 302 through 310. The method 300 starts at block 302.
[0088] At block 302, the receiving module 242 receives, via the UI 160-1 of the user device 160, the input for visualizing the live alarms of the nodes (i.e., nodes 102 through 108) within a specific service area of the communication network 100. The specific service area may be selected by the end user via the UI 160-1 of the user device 160.
[0089] At block 304, the data extraction module 246 fetches the live alarm data and geographical location information for all the nodes within the specific service area from the database 270 based on the input received at the receiving module 242 for visualizing the live alarms of the nodes within the specific service area.
[0090] At block 306, the data processing module 248 determines the count of the outage nodes/sites and the count of the performance degraded nodes among the nodes present in the specific service area based on the live alarm data fetched from the database 270. In a non-limiting example, let say nodes 102 is counted as an outage node and nodes (104, 106) is counted as the performance degraded nodes among the nodes 102 through 108 based on the live alarm data fetched from the database 270. Here, the outage nodes/sites refers to those network nodes that are completely inoperable due to critical failures such as, but not limited to, power outages, hardware malfunctions, or disconnections. The performance degraded nodes refers to those network nodes that remain operational but experiences performance issues, such as but not limited to, high packet loss, increased latency, or a degraded throughput.
[0091] At block 308, the data processing module 248 generates the live alarm outage report or the live alarm ageing information report based on the determined count of the outage nodes or the determined count of the performance degraded nodes among the nodes present in the specific service area.
[0092] At block 310, the display module 250 displays the generated live alarm outage report or the live alarm ageing information report on the UI 160-1 of the user device 160. In particular, the processor 210, using the display module 250, controls the user device 160 to display the generated live alarm outage report or the live alarm ageing information report on the UI 160-1 of the user device 160. A non-limiting example of the live alarm outage report and the live alarm ageing information report is shown in FIG. 5 and FIG. 6, respectively to make an easy understanding of the present invention.
[0093] Referring now to FIG. 4, illustrates a flowchart of a method 400 for updating the live alarm ageing information report, in accordance with an embodiment of the present disclosure. The method 400 comprises a series of operation steps indicated by blocks 402 through 408. The method 400 starts at block 402.
[0094] At block 402, the processor 210, using the display module 250, controls the user device 160 to display the hierarchical navigation tab on the UI 160-1 of the user device 160, for visualizing the count of the outage nodes and the count the performance degraded nodes across hierarchical geographical levels in the specific service area. The hierarchical navigation tab may correspond to a GUI component for enabling the network operations team or the end user to visualize the live alarm outage report and the live alarm ageing information report at different levels of granularity. The hierarchical navigation tab facilitates seamless navigation across multiple hierarchical levels such as at a service area level, a maintenance cluster level, or at a node level.
[0095] At block 404, the receiving module 242 receives the input from the end user via the UI 160-1 of the user device 160 based on a selection operation performed by the end user on the displayed hierarchical navigation tab.
[0096] At block 406, the data processing module 248 dynamically updates the live alarm ageing information report when the selection of the geographical level from the hierarchical geographical levels is received by the receiving module 242 from the user device 160 via the displayed hierarchical navigation tab.
[0097] At block 408, the processor 210 controls the display module 250 to navigate between the display of the count of the outage nodes and the display of the count of the performance degraded nodes across the hierarchical geographical levels.
[0098] FIG. 5 illustrates an example Graphics User Interface (GUI) 500 for visualizing outage sites pattern across different geographies, in accordance with an embodiment of the present disclosure. As shown in FIG. 5, the GUI 500 provides a selectable report generation option 502 to the end user for generation of the live alarm outage report to visualize outage sites pattern across different geographies.
[0099] Once the end user selects the option 502 for the outage site data generation, the processor 210 may control the display module 250 to display the count of the outage sites for the one or more geographical locations on the GUI 500 using which the end user can visualize and monitor the outage sites on a specific geographical level. In a non-limiting example, the displayed data may also include information indicating a service area, a technology area, one or more vendors, node-type, a count of overall on-Air sites, a count of overall outage sites, and the like. Further, as shown in FIG. 5 by reference 504, the determined count of the outage nodes for the one or more geographical locations may be displayed in the descending order.
[0100] FIG. 6 illustrates another example GUI 600 for visualizing ageing of alarms in the communication network 100, in accordance with an embodiment of the present disclosure. The GUI 600 as shown in FIG. 6 provides a selectable option 602 to the end user and the network administrator for generating the live alarm ageing information report to visualize the ageing of alarms on the nodes within the service area of the communication network 100 selected by the end user. When the end user or the network administrator selects the displayed option 602 for generating the live alarm ageing information report, the processor 210, using the data processing module 258, generates the live alarm ageing information report corresponding to the one or more vendors, and controls the display module 160 to display the generated live alarm ageing information report on the UI 160-1. In FIG. 6, the generated live alarm ageing information report is indicated by the reference 604. As can be seen from the reference 604, the generated live alarm ageing information report includes data related to ageing of the live alarm and the performance degrading alarms for any geographical location in different time slots in . In a non-limiting example, the time slots may include a plurality of slots such as 0-4 hours, 4-8 hours, 8-12 hours, 12-24 hours and more than 24 hours. The display of the live alarm ageing information report may help the end user or the network administrator in visualizing the ageing of the outage alarms and the performance degrading alarms in the communication network 100. Such visualization may serve as the early warning to network administrator or network engineer for enabling prompt attention in order to prevent one or more service disruptions and for providing immediate remediation.
[0101] FIG. 7 illustrates another example GUI 700 for visualizing maintenance cluster wise count of the outage sites (i.e. outage nodes) for one or more vendors, in accordance with an embodiment of the present disclosure. The GUI 700 as shown in FIG. 7 provide an option using which the end user can visualize maintenance cluster wise count of the outage sites in the communication network 100. Once the end user or the network administrator selects the option for displaying the count of the outage sites for each of the maintenance cluster, the processor 210 may control the display module 250 to display, on the UI 160-1, the generated live alarm outage report (also referred to as “outage site report” in the GUI 700) including the determined count of the outage sites for the one or more maintenance clusters in the descending order. Further, the processor 210 may be configured to control the display module 250 to display the hierarchical navigation tab to help the end user or the network administrator to drill down from maintenance cluster view to a node level view and vice-versa in order to visualize the determined count of the outage sites across hierarchical geographical levels.
[0102] FIG. 8 illustrates an example GUI 800 depicting an example of the outage site report for a maintenance cluster selected by the end user, in accordance with an embodiment of the present disclosure. The outage site report as shown in FIG. 8 on the GUI 800 includes detailed alarm events and the live alarm data. As shown in FIG. 8, the outage site report includes one or more of event timestamps associated with corresponding outage alarm and corresponding vendors, a Service Access Point Identifier (SAP ID) of each of the outage nodes, a type of the site, an alarm ID of each of the outage alarms, a name of each of the outage alarms, and the like. The SAP ID of the outage nodes is an identifier that helps in uniquely identifying each network node experiencing an outage within the communication network 100. The SAP ID is generally assigned to each individual node for facilitating precise tracking, monitoring, and troubleshooting of alarms generated at the individual node. The display of the such detailed outage site report may help the end user or the network administrator to easily navigate to any spatial level while visualizing outage sites pattern across different geographies.
[0103] FIG. 9 is a block diagram depicting an example computer system 900 in which embodiments of the present disclosure may be implemented. The computer system 900 can be any commercially available and well-known computer capable of performing the functions described herein. The computer system 900 may be any type of computer, including a server, a web server, a cloud server, etc.
[0104] The computer system 900 includes one or more processors (also called central processing units, or CPUs), such as a processor 904. The processor 904 is connected to a communication infrastructure 902, such as a communication bus. In some embodiments, the processor 904 can simultaneously operate multiple computing threads.
[0105] The computer system 900 also includes a primary or main memory 906, such as random access memory (RAM). The main memory 906 has stored therein control logic 924 (computer software), and data.
[0106] The computer system 900 also includes one or more secondary storage devices 908. The secondary storage devices 908 include, for example, a hard disk drive 910 and/or a removable storage device or drive 912, as well as other types of storage devices, such as memory cards and memory sticks. For instance, the computer system 900 may include an industry standard interface, such a universal serial bus (USB) interface for interfacing with devices such as a memory stick. The removable storage drive 912 represents a floppy disk drive, a magnetic tape drive, a compact disk drive, an optical storage device, tape backup, etc.
[0107] The removable storage drive 912 interacts with a removable storage unit 914. The removable storage unit 914 includes a computer useable or readable storage medium 920 having stored therein computer software 922 (control logic) and/or data. The removable storage unit 914 represents a floppy disk, magnetic tape, compact disk, DVD, optical storage disk, or any other computer data storage device. The removable storage drive 912 reads from and/or writes to removable storage unit 914 in a well-known manner.
[0108] The computer system 900 may also include input interface/output interface/display devices 918, such as monitors, keyboards, pointing devices, etc.
[0109] The computer system 900 further includes a communication interface or a network interface 916. The communication interface 916 enables the computer system 900 to communicate with remote systems and devices. For example, communication interface 916 allows the computer system 900 to communicate over communication networks or mediums 928, such as LANs, WANs, the Internet, etc. The network interface 916 may interface with remote sites or networks via wired or wireless connections.
[0110] Control logic 926 may be transmitted to and from the computer system 900 via the communication medium 928. More particularly, the computer system 900 may receive and transmit carrier waves (electromagnetic signals) modulated with control logic 926 via the communication medium 928.
[0111] Embodiments of the present technology may be described herein with reference to flowchart illustrations of methods and systems according to embodiments of the technology, and/or procedures, algorithms, steps, operations, formulae, or other computational depictions, which may also be implemented as computer program products. In this regard, each block or step of the flowchart, and combinations of blocks (and/or steps) in the flowchart, as well as any procedure, algorithm, step, operation, formula, or computational depiction can be implemented by various means, such as hardware, firmware, and/or software including one or more computer program instructions embodied in computer-readable program code. As will be appreciated, any such computer program instructions may be executed by one or more computer processors, including without limitation a general-purpose computer or special purpose computer, or other programmable processing apparatus to perform a group of operations comprising the operations or blocks described in connection with the disclosed methods.
[0112] Further, these computer program instructions, such as embodied in computer-readable program code, may also be stored in one or more computer-readable memory or memory devices (for example, the memory 215) that can direct a computer processor or other programmable processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory or memory devices produce an article of manufacture including instruction means which implement the function specified in the block(s) of the flowchart(s).
[0113] It will further be appreciated that the term “computer program instructions” as used herein refer to one or more instructions that can be executed by the one or more processors (for example, the processor 210) to perform one or more functions as described herein. The instructions may also be stored remotely such as on a server, or all or a portion of the instructions can be stored locally and remotely.
[0114] Now, referring to the technical abilities and advantageous effect of the present disclosure, operational advantages that may be provided by one or more embodiments may include enabling the network operations team to view performance of the communication network holistically in a single glass pane view by providing a user-friendly and intuitive interface to visualize the count of nodes that includes the outage alarms or the performance degrading alarms for corresponding geographies in the communication network.
[0115] Further, the one or more embodiments described herein may help the network operations team or the network administrator in monitoring the performance of the communication network during any events or festivals or at locations, where live monitoring of the performance of the communication network is crucial and required to be updated in real time for enriching end users experience.
[0116] Furthermore, the method and system disclosed herein can help the network operations team in visualizing and monitoring the outage sites and the ageing of the outage alarms and the performance degrading alarms in the communication network, in near real time by providing navigational options on the GUI for drilling down from service area level view to maintenance cluster view to node level view. This feature facilitate the network operations team to prioritize the rectification of the long duration outage alarms, thereby improving the end users experience.
[0117] In other words, the method and system disclosed herein helps in performing an automated alarm analysis associated with the nodes in the communication network by performing real-time alarm data processing to detect and categorize network issues, thereby reducing a need for manual intervention. Further, the live alarm ageing information report generated by the system as disclosed herein can assist in predictive maintenance by identifying recurring faults, helping the network operations team to preemptively address node failures. Furthermore, by providing the hierarchical navigation tab and time-stamped alarm ageing data, the system disclosed herein can enhance troubleshooting efficiency for clearing active/live alarms raised at the network nodes across different levels of the service area.
[0118] Those skilled in the art will appreciate that the methodology described herein in the present disclosure may be carried out in other specific ways than those set forth herein in the above disclosed embodiments without departing from essential characteristics and features of the present invention. The above-described embodiments are therefore to be construed in all aspects as illustrative and not restrictive.
[0119] The drawings and the forgoing description give examples of embodiments. Those skilled in the art will appreciate that one or more of the described elements may well be combined into a single functional element. Alternatively, certain elements may be split into multiple functional elements. Elements from one embodiment may be added to another embodiment. For example, orders of processes described herein may be changed and are not limited to the manner described herein. Any combination of the above features and functionalities may be used in accordance with one or more embodiments.
[0120] In the present disclosure, each of the embodiments has been described with reference to numerous specific details which may vary from embodiment to embodiment. The foregoing description of the specific embodiments disclosed herein may reveal the general nature of the embodiments herein that others may, by applying current knowledge, readily modify and/or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications are intended to be comprehended within the meaning of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and is not limited in scope.
LIST OF REFERENCE NUMERALS
[0121] The following list is provided for convenience and in support of the drawing figures and as part of the text of the specification, which describe innovations by reference to multiple items. Items not listed here may nonetheless be part of a given embodiment. For better legibility of the text, a given reference number is recited near some, but not all, recitations of the referenced item in the text. The same reference number may be used with reference to different examples or different instances of a given item. The list of reference numerals is:
100 - Communication network
102-108 - GNodeB (gNB)
110 - Element Management System (EMS) cluster
102'-108' - Vendor EMSs
120 - Network
130 - Load balancer
140 - Server
150 - Distributed file system
160 - User device
160-1 - User Interface (UI)
160-2 - Communication unit
170 - Gateway
210 - Processor
215 - Memory
215A - Instructions
220 - Communication Interface
225 - Parser(s)
230 - Interface(s)
260 - Processing unit(s)/modules(s)
242 - Receiving module
244 - Transmitting module
246 - Data extraction module
248 - Data processing module
250 - Display module
252 - Other units/modules
270 - Database
280 - Communication bus
300 - Method for visualizing the live alarms of nodes (102-108) in the communication network 100
400 - Method for updating live alarm ageing information report
500 - Graphics User Interface (GUI) for visualizing outage sites pattern across different geographies
600 - GUI for visualizing ageing of alarms in the communication network 100
700 - GUI for visualizing maintenance cluster wise count of the outage sites for one or more vendors
800 - Example of the outage site report for a maintenance cluster selected by end user
900 - Computer system
902 - Communication infrastructure
904 – Processor of computer system
906 - Memory
908 - Secondary storage devices
910 - Hard disk drive
912 - Removable storage device
914 - Removable storage unit
916 – Communication/Network interface
918 - Input interface/output interface/display devices
920 - Readable storage medium
922 - Software
924 - Removable storage unit
926 - Control logic
928 - Communication networks or mediums
,CLAIMS:1. A method (300) for visualizing live alarms of a plurality of nodes (102-108) in a communication network (100), the method comprising:
receiving, by a receiving module (242) from a user device (160), an input for visualizing the live alarms of the plurality of nodes (102-108) within a service area of the communication network (100);
fetching, by a data extraction module (246) from a database (270), live alarm data associated with the plurality of nodes (102-108) based on the input;
determining, by a data processing module (248), for one or more geographical locations within the service area, a count of a set of outage nodes among the plurality of nodes and a count of a set of performance degraded nodes among the plurality of nodes based on the fetched live alarm data, wherein the set of outage nodes includes outage alarms, and the set of performance degraded nodes includes performance degraded alarms;
generating, by the data processing module (248), at least one of a live alarm outage report or a live alarm ageing information report based on at least one of the determined count of the set of outage nodes or the determined count of the set of performance degraded nodes, wherein
the live alarm outage report comprises information indicating the determined count of the set of outage nodes for the one or more geographical locations, and
the live alarm ageing information report comprises information indicating ageing of the outage alarms and the performance degraded alarms for the one or more geographical locations at a plurality of predefined time slots; and
displaying, by a display module (250), the at least one of the live alarm outage report or the live alarm ageing information report on an interface (160-1) of the user device (160).

2. The method (300) as claimed in claim 1, further comprising displaying, by the display module (250) on the interface (160-1) of the user device (160), a plurality of selectable report generation options including a first selectable option for generating the live alarm outage report and a second selectable option for generating the live alarm ageing information report, wherein
the live alarm outage report is generated upon receiving the input via the first selectable option and the live alarm ageing information report is generated upon receiving the input via the second selectable option, and
the live alarm data comprises at least one of alarm identification information, node related information, alarm related details, real-time performance metrics, connectivity information, and alarm correlation data.

3. The method (300) as claimed in claim 1, wherein the live alarm outage report comprises information related to one or more of event timestamps associated with the outage alarms, one or more vendors, an Identifier (ID) of each of the set of outage nodes, a type of site corresponding to each outage node of the set of outage nodes, an alarm ID of each of the outage alarms, and a name of each of the outage alarms.

4. The method (300) as claimed in claim 1, further comprising displaying, by the display module (250) on the interface (160-1), the determined count of the set of outage nodes for the one or more geographical locations in a descending order.

5. The method (300) as claimed in claim 1, further comprising:

determining, by the data processing module (248) based on the fetched live alarm data, a count of the outage alarms in each maintenance cluster of a plurality of maintenance clusters within the service area; and
generating, by the data processing module (248), the live alarm outage report based on the determined count the outage alarms in each maintenance cluster of the plurality of maintenance clusters.

6. The method (300) as claimed in claim 1, wherein the database (270) corresponds to one of a relational database, a non-relational database, a time-series database, a distributed file system, a cloud-based database, an in-memory database, a file based storage system, an event-driven database, or a hybrid database.

7. The method (300) as claimed in claim 1, further comprising:
displaying, by the display module (250) on the interface (160-1), a hierarchical navigation tab for visualizing the count of the set of outage nodes and the count of the set of performance degraded nodes across hierarchical geographical levels including the service area, maintenance clusters within the service area, and a node level; and
navigating, by the display module (250) based on a reception of an input via the displayed hierarchical navigation tab, between a display of the count of the set of outage nodes and the count of the set of performance degraded nodes across the hierarchical geographical levels.

8. The method (300) as claimed in claim 7, further comprising dynamically updating, by the data processing module (248), the live alarm ageing information report when an input indicating one of a selection of a geographical level from the hierarchical geographical levels is received via the displayed hierarchical navigation tab.

9. A system (140) for visualizing live alarms of a plurality of nodes (102-108) in a communication network (100), the system (140) comprising:
a receiving module (242) configured to receive, from a user device (160), an input for visualizing the live alarms of the plurality of nodes (102-108) within a service area of the communication network (100);
a data extraction module (246) configured to fetch, from a database (270), live alarm data associated with the plurality of nodes (102-108) based on the input;
a data processing module (248) configured to:
determine, for one or more geographical locations within the service area, a count of a set of outage nodes among the plurality of nodes and a count of a set of performance degraded nodes among the plurality of nodes based on the fetched live alarm data, wherein the set of outage nodes includes outage alarms, and the set of performance degraded nodes includes performance degraded alarms; and
generate at least one of a live alarm outage report or a live alarm ageing information report based on at least one of the determined count of the set of outage nodes or the determined count of the set of performance degraded nodes, wherein
the live alarm outage report comprises information indicating the determined count of the set of outage nodes for the one or more geographical locations, and
the live alarm ageing information report comprises information indicating ageing of the outage alarms and the performance degraded alarms for the one or more geographical locations at a plurality of predefined time slots; and
a display module (250) configured to display the at least one of the live alarm outage report or the live alarm ageing information report on an interface (160-1) of the user device (160).

10. The system (140) as claimed in claim 9, wherein the data processing module (248) is further configured to control the display module (250) to display, on the interface (160-1) of the user device (160), a plurality of selectable report generation options including a first selectable option for generating the live alarm outage report and a second selectable option for generating the live alarm ageing information report, wherein
the live alarm outage report is generated upon receiving the input via the first selectable option and the live alarm ageing information report is generated upon receiving the input via the second selectable option, and
the live alarm data comprises at least one of alarm identification information, node related information, alarm related details, real-time performance metrics, connectivity information, and alarm correlation data.

11. The system (140) as claimed in claim 9, wherein the live alarm outage report comprises information related to one or more of event timestamps associated with the outage alarms, one or more vendors, an Identifier (ID) of each of the set of outage nodes, a type of site corresponding to each outage node of the set of outage nodes, an alarm ID of each of the outage alarms, a name of each of the outage alarms.

12. The system (140) as claimed in claim 9, wherein the data processing module (248) is further configured to control the display module (250) to display, on the interface (160-1), the determined count of the set of outage nodes for the one or more geographical locations in a descending order.

13. The system (140) as claimed in claim 9, wherein the data processing module (248) is further configured to:
determine, based on the fetched live alarm data, a count of the outage alarms in each maintenance cluster of a plurality of maintenance clusters within the service area; and
generate the live alarm outage report based on the determined count the outage alarms in each maintenance cluster of the plurality of maintenance clusters.

14. The system (140) as claimed in claim 9, wherein the database (270) corresponds to a relational database, a non-relational database, a time-series database, a distributed file system, a cloud-based database, an in-memory database, a file based storage system, an event-driven database, or a hybrid database.

15. The system (140) as claimed in claim 9, wherein the display module (250) is further configured to:
display, on the interface (160-1) of the user device (160), a hierarchical navigation tab for visualizing the count of the set of outage nodes and the count of the set of performance degraded nodes across hierarchical geographical levels including the service area, maintenance clusters within the service area, and a node level; and
navigate, based on a reception of an input via the displayed hierarchical navigation tab, between a display of the count of the set of outage nodes and the count of the set of performance degraded nodes across the hierarchical geographical levels.

16. The system (140) as claimed in claim 15, wherein the data processing module (248) is further configured to dynamically update the live alarm ageing information report when an input indicating one of a selection of a geographical level from the hierarchical geographical levels is received via the displayed hierarchical navigation tab.