FORM 2
THE PATENTS ACT, 1970 (39 OF 1970) & THE PATENT RULES, 2003
COMPLETE SPECIFICATION
(See section 10 and rule 13)
“METHOD AND SYSTEM FOR VISUALIZATION OF ALARMS IN A NETWORK”
We, Jio Platforms Limited, an Indian National, of 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.

METHOD AND SYSTEM FOR VISUALIZATION OF ALARMS IN A
NETWORK
FIELD OF INVENTION
[0001] The present disclosure relates generally to the field of wireless communication networks such as fifth generation (5G), or sixth generation (6G) networks. More particularly, the present disclosure relates to methods and systems for implementation of visualization of alarm(s) for different scenarios in a wireless communication network.
BACKGROUND
[0002] The following description of related art is intended to provide background information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section be used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of prior art.
[0003] Wireless communication technology has rapidly evolved over the past few decades, with each generation bringing significant improvements and advancements. The first generation of wireless communication technology was based on analog technology and offered only voice services. However, with the advent of the second generation (2G) technology, digital communication and data services became possible, and text messaging was introduced. The third generation (3G) technology marked the introduction of high-speed internet access, mobile video calling, and location-based services. The fourth generation (4G) technology revolutionized wireless communication with faster data speeds, better network coverage, and improved security. Currently, the fifth generation (5G) technology is being deployed, promising even faster data speeds, low latency, and the ability to

connect multiple devices simultaneously. With each generation, wireless communication technology has become more advanced, sophisticated, and capable of delivering more services to its users.
[0004] Furthermore, the wireless communication technology has enabled the network service providers to cater millions of users simultaneously, but the need of providing efficient services to such users has also led to various challenges for the network service providers. For instance, to provide the users seamless services, the network service providers need to continuously monitor the functioning of the network nodes to detect abnormal functioning at such nodes.
[0005] Also, in telecommunication network systems, an Element Management System, referred as EMS is the vendor equipment which collects the data like Performance Data, Alert Messages like Alarms and Parameter related information, etc. from all network nodes parented to it. Every EMS has a defined capacity not only on the hardware front but also depends upon the capacity to handle the number of nodes on the software angle. Hence, for the large-scale network having millions of nodes there will be multitudes of EMS at National level installed across various geographies. In the absence of centralized platform of automation to monitor the alarms in the real time is humanly impossible and there may be a need to deploy huge manpower.
[0006] Further, over the period of time various solutions have been developed to improve the performance of the wireless communication networks and to monitor the alarms generated by various network nodes. However, there are certain challenges with existing solutions. For instance, in the existing systems there is an absence of a centralized platform of automation to monitor the alarms in a wireless communication network and the existing solutions also failed to provide an implementation of visualization of such alarms for different scenarios in the wireless communication network, wherein such limitation of the existing solutions the present disclosure aims to overcome.

OBJECTS OF THE DISCLOSURE
[0007] Some of the objects of the present disclosure, which at least one implementation disclosed herein satisfies are listed herein below.
[0008] It is an object of the present disclosure to provide a system and a method for implementation of visualization of alarms for different scenarios in a wireless communication network.
[0009] It is another object of the present disclosure to provide a solution that may be applicable to networks such as including but not limited to 5G/6G NR SA (New Radio- Standalone) associated with different network nodes that may be further associated with different vendors.
[0010] It is another object of the present disclosure to provide three different views for monitoring the Alarms in a wireless communication system at National level almost in a near real time i.e., Active Alarm Tabular View, Site View, and Live Alarm View.
[0011] It is yet another object of the present disclosure to provide a solution to provide to the operation team of a wireless communication network an option to view the ageing of the sites facing outage so as to prioritize and to rectify the same.
SUMMARY
[0012] This section is provided to introduce certain aspects of the present disclosure in a simplified form that are further described below in the detailed description. This summary is not intended to identify the key features or the scope of the claimed subject matter.

[0013] An aspect of the present disclosure relates to a method for visualization of one or more alarms in a network. The method comprises receiving, by a receiving unit via a North Bound Interface (NBI), one or more alarm messages from at least one Element Management System (EMS), wherein the one or more alarm messages are received in one or more formats. The method further comprises processing, by a processing unit, the one or more alarm messages to convert the one or more formats into a simplified message format. The method further comprises identifying, by an identification unit, a data associated with the one or more alarms based at least on the simplified message format. The method further comprises generating, by the processing unit, at least one visual format of at least the one or more alarms for displaying, based at least on the identified data.
[0014] According to an exemplary aspect of the present disclosure the method further comprises tagging, by the processing unit, at least one attribute to the one or more alarm messages.
[0015] According to another exemplary aspect of the present disclosure the at least one attribute comprises one of an outage alarm, and a performance degradation.
[0016] According to another exemplary aspect of the present disclosure the method further comprises displaying, by a display unit, the at least one visual format of at least the one or more alarms on at least one geographical region in one or more views, wherein the one or more views are configurable based at least on an input.
[0017] According to another exemplary aspect of the present disclosure the one or more views comprises at least one of an active alarm view, a site view, and a live alarm view.
[0018] According to another exemplary aspect of the present disclosure each of the one or more alarm messages are stored in a repository to create an alarm history.

[0019] According to another exemplary aspect of the present disclosure the one or more views provide an access for checking the alarm history.
[0020] According to another exemplary aspect of the present disclosure the data comprises at least one of one or more cell sites of occurrence of the one or more alarms, and an extent of impact on the one or more cell sites.
[0021] According to another exemplary aspect of the present disclosure the one or more formats comprises at least a Simple Network Management Protocol (SNMP) format.
[0022] According to another exemplary aspect of the present disclosure the method further comprises downloading, by the processing unit, an alarm report corresponding to the at least one visual format of at least the one or more alarms; and storing, by a storage unit, the downloaded alarm report.
[0023] Another aspect of the present disclosure relates to a system for visualization of one or more alarms in a network. The system comprises a receiver unit, a processing unit, and an identification unit, connected to each other. The receiving unit is configured to receive, via a North Bound Interface (NBI), one or more alarm messages from at least one Element Management System (EMS), wherein the one or more alarm messages are received in one or more formats. Further, the processing unit is configured to process, the one or more alarm messages to convert the one or more formats into a simplified message format. Further, the identification unit is configured to identify a data associated with the one or more alarms based at least on the simplified message format. Further, the processing unit is configured to generate at least one visual format of at least the one or more alarms for displaying, based at least on the identified data.
[0024] Another aspect of the present disclosure relates to a user equipment comprising a processor. The processor is configured to send a request to a system,

to display one or more alarms associated with a network in at least one visual format. The processor is further configured to receive from the system, the at least one visual format of the one or more alarms. The at least one visual format of the one or more alarms is generated by the system based on receiving, by the system via a North Bound Interface (NBI), one or more alarm messages from at least one Element management system (EMS), wherein the one or more alarm messages are received in one or more formats. Further, the generation of the visual format is further based on processing, by the system, the one or more alarm messages to convert the one or more formats into a simplified message format. The generation of the visual format is further based on identifying, by the system, a data associated with the one or more alarm messages based at least on the simplified message format. Further, the generation of the visual format is further based on generating, by the system, at least one visual format of at least the one or more alarms for displaying, based at least on the identified data.
[0025] Yet another aspect of the present disclosure relates to a non-transitory computer readable storage medium storing one or more instructions for visualization of one or more alarms in a network. The one or more instructions comprises executable code which, when executed by one or more units of a system, causes the system to perform certain functions. The one or more instructions when executed causes a receiving unit of the system to receive via a North Bound Interface (NBI), one or more alarm messages from at least one Element Management System (EMS), wherein the one or more alarm messages are received in one or more formats. The one or more instructions when executed further causes a processing unit of the system to process the one or more alarm messages to convert the one or more formats into a simplified message format. The one or more instructions when executed further causes an identification unit of the system to identify a data associated with the one or more alarms based at least on the simplified message format. The one or more instructions when executed further causes the processing unit of the system to generate at least one visual format of at least the one or more alarms for displaying, based at least on the identified data.

BRIEF DESCRIPTION OF DRAWINGS
[0026] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary implementations 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 electronic components or circuitry commonly used to implement such components.
[0027] FIG. 1A illustrates an exemplary block diagram of a system [100A] for implementation of visualization of one or more alarms in a network, in accordance with exemplary implementations of the present disclosure.
[0028] FIG. 1B illustrates an exemplary block diagram of a computing device upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure.
[0029] FIG. 2 illustrates an exemplary method flow diagram indicating the process [200] for implementation of visualization of one or more alarms in a network, in accordance with exemplary implementations of the present disclosure.
[0030] FIG. 3 illustrates an exemplary active alarm tabular view, in accordance with exemplary implementations of the present disclosure.

[0031] FIG. 4 illustrates an exemplary sequence diagram indicating the process of implementation of visualization of alarms for different scenarios i.e., visualization of alarms in a network, in accordance with exemplary implementations of the present disclosure. 5
[0032] FIG. 5 illustrates an exemplary sequence diagram for site view in the map layer, in accordance with exemplary implementations of the present disclosure.
[0033] FIG. 6 illustrates an exemplary map layer site view, in accordance with
10 exemplary implementations of the present disclosure.
[0034] FIG. 7 illustrates another exemplary map layer site view, in accordance with exemplary implementations of the present disclosure.
15 [0035] FIG. 8 illustrates an exemplary alarm view, in accordance with exemplary
implementations of the present disclosure.
[0036] FIG. 9 illustrates an exemplary live alarm view, in accordance with exemplary implementations of the present disclosure. 20
[0037] FIG. 10 illustrates another exemplary live alarm view, in accordance with exemplary implementations of the present disclosure.
[0038] FIG. 11 illustrates another exemplary active alarm age view, in accordance
25 with exemplary implementations of the present disclosure.
[0039] FIG. 12 illustrates another exemplary alarm-trends view, in accordance with exemplary implementations of the present disclosure.
30 [0040] FIG. 13 illustrates another exemplary alarm history view, in accordance
with exemplary implementations of the present disclosure.
9

[0041] The foregoing shall be more apparent from the following more detailed description of the disclosure.
5 DETAILED DESCRIPTION
[0042] In the following description, for the purposes of explanation, various specific details are set forth in order to provide a thorough understanding of implementations of the present disclosure. It will be apparent, however, that
10 implementations 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. An individual feature may not address any of the problems discussed above or might address only some of the problems discussed above. Some of the problems discussed above might not be
15 fully addressed by any of the features described herein. Example implementations
of the present disclosure are described below, as illustrated in various drawings in which like reference numerals refer to the same parts throughout the different drawings.
20 [0043] The ensuing description provides exemplary implementations only, and is
not intended to limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing description of the exemplary implementations will provide those skilled in the art with an enabling description for implementing an exemplary implementation. It should be understood that various changes may be made in the
25 function and arrangement of elements without departing from the spirit and scope
of the disclosure as set forth.
[0044] It should be noted that the terms "mobile device", "user equipment", "user
device", “communication device”, “device” and similar terms are used
30 interchangeably for the purpose of describing the disclosure. These terms are not
intended to limit the scope of the disclosure or imply any specific functionality or
10

limitations on the described implementations. The use of these terms is solely for
convenience and clarity of description. The disclosure is not limited to any
particular type of device or equipment, and it should be understood that other
equivalent terms or variations thereof may be used interchangeably without
5 departing from the scope of the disclosure as defined herein.
[0045] Specific details are given in the following description to provide a thorough understanding of the implementations. However, it will be understood by one of ordinary skill in the art that the implementations may be practiced without these
10 specific details. For example, circuits, systems, networks, processes, and other
components may be shown as components in block diagram form in order not to obscure the implementations in unnecessary detail. In other instances, well-known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail in order to avoid obscuring the implementations.
15
[0046] Also, it is noted that individual implementations may be described as a process which is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations can be performed in
20 parallel or concurrently. In addition, the order of the operations may be re-arranged.
A process is terminated when its operations are completed but could have additional steps not included in a figure.
[0047] The word “exemplary” and/or “demonstrative” is used herein to mean
25 serving as an example, instance, or illustration. For the avoidance of doubt, the
subject matter disclosed herein is not limited by such examples. In addition, any
aspect or design described herein as “exemplary” and/or “demonstrative” is not
necessarily to be construed as preferred or advantageous over other aspects or
designs, nor is it meant to preclude equivalent exemplary structures and techniques
30 known to those of ordinary skill in the art. Furthermore, to the extent that the terms
“includes,” “has,” “contains,” and other similar words are used in either the detailed
11

description or the claims, such terms are intended to be inclusive—in a manner similar to the term “comprising” as an open transition word—without precluding any additional or other elements.
5 [0048] As used herein, an “electronic device”, or “portable electronic device”, or
“user device” or “communication device” or “user equipment” or “device” refers to any electrical, electronic, electromechanical and computing device. The user device is capable of receiving and/or transmitting one or parameters, performing function/s, communicating with other user devices and transmitting data to the
10 other user devices. The user equipment may have a processor, a display, a memory,
a battery and an input-means such as a hard keypad and/or a soft keypad. The user equipment may be capable of operating on any radio access technology including but not limited to IP-enabled communication, Zig Bee, Bluetooth, Bluetooth Low Energy, Near Field Communication, Z-Wave, Wireless fidelity (Wi-Fi), Wi-Fi
15 direct, etc. For instance, the user equipment may include, but not limited to, a
mobile phone, smartphone, virtual reality (VR) devices, augmented reality (AR) devices, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, mainframe computer, or any other device as may be obvious to a person skilled in the art for implementation of the features of the present disclosure.
20
[0049] Further, the user device may also comprise a “processor” or “processing unit”, wherein processor refers to any logic circuitry for processing instructions. The processor may be a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor, a plurality of microprocessors,
25 one or more microprocessors in association with a digital signal processing (DSP)
core, a controller, a microcontroller, Application Specific Integrated Circuits, Field Programmable Gate Array circuits, any other type of integrated circuits, etc. The processor may perform signal coding data processing, input/output processing, and/or any other functionality that enables the working of the system according to
30 the present disclosure. More specifically, the processor is a hardware processor.
12

[0050] As portable electronic devices and wireless technologies continue to
improve and grow in popularity, the advancing wireless technologies for data
transfer are also expected to evolve and replace the older generations of
technologies. In the field of wireless data communications, the dynamic
5 advancement of various generations of cellular technology are also seen. The
development, in this respect, has been incremental in the order of second generation (2G), third generation (3G), fourth generation (4G), and now fifth generation (5G), and more such generations are expected to continue in the forthcoming time.
10 [0051] Radio Access Technology (RAT) refers to the technology used by mobile
devices/ user equipment (UE) to connect to a cellular network. It refers to the specific protocol and standards that govern the way devices communicate with base stations, which are responsible for providing the wireless connection. Further, each RAT has its own set of protocols and standards for communication, which define
15 the frequency bands, modulation techniques, and other parameters used for
transmitting and receiving data. Examples of RATs include GSM (Global System for Mobile Communications), CDMA (Code Division Multiple Access), UMTS (Universal Mobile Telecommunications System), LTE (Long-Term Evolution), and 5G. The choice of RAT depends on a variety of factors, including the network
20 infrastructure, the available spectrum, and the mobile device's/device's capabilities.
Mobile devices often support multiple RATs, allowing them to connect to different types of networks and provide optimal performance based on the available network resources.
25 [0052] As discussed in the background section, the current known solutions have
several shortcomings. The present disclosure aims to overcome the above-mentioned and other existing problems in this field of technology by providing methods and systems for implementation of visualization of alarms for different scenarios. Mainly, according to the present disclosure vendor EMSs (Element
30 Management Systems) are connected to Centralized Automation Platform via NBI
interface, i.e., North Bound Interface. The north bound interface refers to the
13

interface or connection between the element management system and a system as
disclosed in the present disclosure which enables transfer of the data between the
two. Alarms are raised by the network nodes as and when it encounters the abnormal
functioning in certain scenario and such alarms are collected in the form of
5 messages by the Element Management System to which the nodes are parented.
The Centralized Automation Platform collects all the alarm related messages which
are streamed from different EMS and further these alarms are processed in a near
real time and various attributes are added to these alarms like Outage Alarm,
Performance Degradation alarm for the quick visibility for both, Network
10 Operations Centre and Field Staff to take corrective action to resolve the issues,
thereby improving the Network uptime and hence the customer experience.
[0053] This feature also enables not only the field staff and network operation
center (NOC) operation team to have a quick visibility of the outage site but also
15 customer care agent for dealing with the customer complaints and update the
customer accordingly.
[0054] Furthermore, it is pertinent to note that the solution as disclosed in the
present disclosure is not limited to the Radio network, the implementation can be
20 adopted with zero development efforts to any technology 5G, 6G, etc, any Domain,
viz., Transport, Core, Backhaul IP equipment’s like Routers, FTTX (Fiber to Home/Curb/Building), etc and also vendor agnostic.
[0055] Hereinafter, exemplary implementations of the present disclosure will be
25 described with reference to the accompanying drawings.
[0056] Referring to FIG. 1A, an exemplary block diagram of a system [100A] for
implementation of visualization of one or more alarms in a network is shown, in
accordance with the exemplary implementations of the present disclosure. The
30 system [100A] comprises at least one of a receiving unit [102A], at least one
processing unit [104A], at least one identification unit [106A], at least one display
14

unit [108A], at least one repository [110A], and at least one storage unit [112A].
Also, all of the components/ units of the system [100A] are assumed to be connected
to each other unless otherwise indicated below. Also, in FIG. 1A only a few units
are shown, however, the system [100A] may comprise multiple such units or the
5 system [100A] may comprise any such numbers of said units, as required to
implement the features of the present disclosure. Further, in an implementation, the system [100A] may be present in a server device to implement the features of the present disclosure. The system [100A] may be a part of the server device / or may be independent of but in communication with the server device.
10
[0057] The system [100A] is configured for implementation of visualization of the one or more alarms in a network, with the help of the interconnection between the components/units of the system [100A]. The storage unit [112A] of the system [100A] is configured to store the data as required to implement the features of the
15 present disclosure. Also, the receiving unit [102A], the processing unit [104], and
the identification unit [106A] of the system [100A] are configured to enable three different scenarios, i.e., Active Alarm Tabular View (also interchangeably used with active alarm view), a Site View and a Live Alarm View for monitoring the one or more Alarms at National level almost in a near real time.
20
[0058] Particularly, in order for visualization of the one or more alarms in a network, the receiving unit [102A] of the system [100A] is configured to receive, via a North Bound Interface (NBI) [116A], one or more alarm messages from at least one Element management system (EMS) [114A], wherein the one or more
25 alarm messages are received in one or more formats. In an implementation of the
present disclosure, the one or more formats comprises at least a Simple Network Management Protocol (SNMP) format. The visualisation of alarms refers to displaying the information related to the different alarms and visualising the information through various ways such as by providing a user interface for
30 displaying the information. The network refers to the telecommunication network
for different generation of the network technologies. The receiving unit [102A] may
15

be a unit capable of receiving data and may also be connected to a processor capable
of receiving and/or processing data from certain other units. The north bound
interface [116A] refers to the interface or connection between the element
management system [114A] and the system [100A] which enables transfer of the
5 data between the two. Each alarm message from the one or more alarm messages
may be a message containing information associated with the alarm(s) such as type of alarm, reason of alarm, information related to one or more faults, identifier of alarm, geographical location, vendor name, alarm severity, an identifier associated with an enterprise resource planning software, an identifier associated with a site,
10 alarm name, number of occurrences, and some other allied information. The one or
more alarm messages may have different formats and may contain information in different formats. The EMS [114A] may be a system which is associated with management of certain faults, errors, and alarms. The EMS [114A] may also be a fault management system.
15
[0059] Further, the processing unit [104A] of the system [100A] is configured to process, the one or more alarm messages to convert the one or more formats into a simplified message format. The one or more alarm messages may also be processed via an Operation Support System (OSS). The processing unit [104A] may be a unit
20 capable of processing data and converting input into output by processing data, and
may also be a processor capable of implementing the features if the present disclosure. The OSS may be a system capable of handling different formats of messages and interpretation of associated information. The OSS can identify whether any problem in a network is a site related problem or randomly occurring
25 throughout the geography. The OSS can also initiate action in either case by sending
the field staff to the site or by taking it up with the SMEs/vendor for further analysis and resolution like tuning the parameter, software upgrade, etc. The simplified message format refers to the format which converts the complex messages comprising a lot of details into a simpler format which provides information in a
30 simpler way.
16

[0060] Further, the identification unit [106A] of the system [100A] is configured to identify data associated with the one or more alarms based at least on the simplified message format. The data associated with one or more alarms refers to the information related to the alarm. 5
[0061] In an implementation of the present disclosure, the data comprises at least
one of one or more cell sites of occurrence of the one or more alarms, and an extent
of impact on the one or more cell sites. The one or more cell sites of occurrence of
the one or more alarms may be the information related to the faults/issues which
10 are detected by the EMS [114A] specifically related to the location or identifier of
the cell/terminals/gNodeB at which the error/fault/issue has been occurred. The extent of the impact of the cell sites may refer to the impact which has occurred on the coverage due to such faults/errors/issues at the particular cell.
15 [0062] Further, the processing unit [104A] of the system [100A] is configured to
generate at least one visual format of at least the one or more alarms to display on at least one geographical region based at least on the identified data. The at least one visual format may be a format for displaying the information related to the alarms for a particular cell. The at least one geographical region may be the region
20 at which the alarm has been generated due to certain faults/issues.
[0063] In an implementation of the present disclosure, the processing unit [104A]
is further configured to tag at least one attribute to the one or more alarm messages.
The at least one attribute may in be an outage alarm or a performance degradation.
25 The outage alarm refers to the alarm where the cell has stopped working due to
certain issues such as power outage. The performance degradation refers to the attributes where the cell is not working at an optimum level and has been not able to function efficiently and effectively.
30 [0064] In an implementation of the present disclosure, the display unit [108A] of
the system [100A] is further configured to display the at least one visual format of
17

at least the one or more alarms on the at least one geographical region in one or
more views, wherein the one or more views are configurable based at least on an
input. Further, in an implementation of the present disclosure, the one or more views
comprises at least an active alarm view, a site view, and a live alarm view. In an
5 implementation, the active alarm view depicts the details of one or more active
alarms (i.e., unresolved issues), the site view depicts details of one or more issues at one or more cell sites / sites of a network entity, and the live alarm view depicts details of one or more issues that are occurring at a network entity in real time and/or in near real time.
10
[0065] In an implementation of the present disclosure, each of the one or more alarm messages are stored within a repository [110A] for creating an alarm history. The repository [110A] refers to a storage which stores the source codes and may also be a storage unit [112A] which is capable of storing information. The alarm
15 history refers to the history of previous alarms and contains the information related
to the previous alarms. Furthermore, the one or more views provides an access for checking the alarm history. The access for checking the alarm history may refer to the providing an option for accessing the alarm history in the one or more views.
20 [0066] In an implementation of the present disclosure, the processing unit [104A]
is configured to download an alarm report corresponding to the at least one visual format of at least the one or more alarms and then store the downloaded alarm report in the storage unit [112A]. The alarm report is made based on the at least one visual format which contains the information related to the one or more alarms.
25
[0067] FIG. 1B illustrates an exemplary block diagram of a computing device [1000] upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure. In an implementation, the computing device [1000] may also implement a method [200]
30 for visualization of one or more alarm in a network by utilising the system [100A].
In another implementation, the computing device [1000] itself implements the
18

method [200] for visualisation of one or more alarms in a network using one or more units configured within the computing device [1000], wherein said one or more units are capable of implementing the features as disclosed in the present disclosure. 5
[0068] The computing device [1000] may include a bus [1002] or other communication mechanism for communicating information, and a hardware processor [1004] coupled with bus [1002] for processing information. The hardware processor [1004] may be, for example, a general-purpose microprocessor. The
10 computing device [1000] may also include a main memory [1006], such as a
random-access memory (RAM), or other dynamic storage device, coupled to the bus [1002] for storing information and instructions to be executed by the processor [1004]. The main memory [1006] also may be used for storing temporary variables or other intermediate information during execution of the instructions to be
15 executed by the processor [1004]. Such instructions, when stored in non-transitory
storage media accessible to the processor [1004], render the computing device [1000] into a special-purpose machine that is customized to perform the operations specified in the instructions. The computing device [1000] further includes a read only memory (ROM) [1008] or other static storage device coupled to the bus [1002]
20 for storing static information and instructions for the processor [1004].
[0069] A storage device [1010], such as a magnetic disk, optical disk, or solid-state drive is provided and coupled to the bus [1002] for storing information and instructions. The computing device [1000] may be coupled via the bus [1002] to a
25 display [1012], such as a cathode ray tube (CRT), Liquid crystal Display (LCD),
Light Emitting Diode (LED) display, Organic LED (OLED) display, etc. for displaying information to a computer user. An input device [1014], including alphanumeric and other keys, touch screen input means, etc. may be coupled to the bus [1002] for communicating information and command selections to the
30 processor [1004]. Another type of user input device may be a cursor controller
[1016], such as a mouse, a trackball, or cursor direction keys, for communicating
19

direction information and command selections to the processor [1004], and for controlling cursor movement on the display [1012]. This input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allow the device to specify positions in a plane. 5
[0070] The computing device [1000] may implement the techniques described herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware and/or program logic which in combination with the computing device [1000] causes or programs the computing device [1000] to be a special-purpose machine.
10 According to one implementation, the techniques herein are performed by the
computing device [1000] in response to the processor [1004] executing one or more sequences of one or more instructions contained in the main memory [1006]. Such instructions may be read into the main memory [1006] from another storage medium, such as the storage device [1010]. Execution of the sequences of
15 instructions contained in the main memory [1006] causes the processor [1004] to
perform the process steps described herein. In alternative implementations of the present disclosure, hard-wired circuitry may be used in place of or in combination with software instructions.
20 [0071] The computing device [1000] also may include a communication interface
[1018] coupled to the bus [1002]. The communication interface [1018] provides a two-way data communication coupling to a network link [1020] that is connected to a local network [1022]. For example, the communication interface [1018] may be an integrated services digital network (ISDN) card, cable modem, satellite
25 modem, or a modem to provide a data communication connection to a
corresponding type of telephone line. As another example, the communication interface [1018] may be a local area network (LAN) card to provide a data communication connection to a compatible LAN. Wireless links may also be implemented. In any such implementation, the communication interface [1018]
30 sends and receives electrical, electromagnetic or optical signals that carry digital
data streams representing various types of information.
20

[0072] The computing device [1000] can send messages and receive data, including
program code, through the network(s), the network link [1020] and the
communication interface [1018]. In the Internet example, a server [1030] might
5 transmit a requested code for an application program through the Internet [1028],
the ISP [1026], the local network [1022], a host [1024] and the communication interface [1018]. The received code may be executed by the processor [1004] as it is received, and/or stored in the storage device [1010], or other non-volatile storage for later execution.
10
[0073] Referring to FIG. 2, an exemplary method flow diagram [200] for visualization of one or more alarms in a network, in accordance with exemplary implementations of the present disclosure is shown. In an implementation the method [200] is performed by the system [100A]. Further, in an implementation,
15 the system [100A] may be present in a server device to implement the features of
the present disclosure. Also, as shown in FIG. 2, the method [200] starts at step [202].
[0074] At step [204], the method [200] as disclosed by the present disclosure
20 comprises receiving, by a receiving unit [102A] via a North Bound Interface (NBI)
[116A], one or more alarm messages from at least one Element Management
System (EMS) [114A], wherein the one or more alarm messages are received in
one or more formats. In an implementation of the present disclosure, the one or
more formats comprises at least a Simple Network Management Protocol (SNMP)
25 format. The visualisation of alarms refers to displaying the information related to
the different alarms and visualising the information through various ways such as
by providing a user interface for displaying the information. The network refers to
the telecommunication network for different generation of the network
technologies. The receiving unit [102A] may be a unit capable of receiving data and
30 may also be connected to a processor capable of receiving and/or processing data
from certain other units. The north bound interface [116A] refers to the interface or
21

connection between the element management system [114A] and the system [100A]
which enables transfer of the data between the two systems. Each alarm from the
one or more alarm messages may be a message containing information associated
with the alarms such as type of alarm, reason of alarm, information related to one
5 or more faults, identifier of alarm, geographical location, vendor name, alarm
severity, an identifier associated with an enterprise resource planning software, an
identifier associated with a site, alarm name, number of occurrences, and some
other allied information. The one or more alarm messages may have different
formats and may contain information in different formats. The EMS [114A] may
10 be a system which is associated with management of certain faults, errors, and
alarms. The EMS [114A] may also be a fault management system.
[0075] At step [206], the method [200] as disclosed by the present disclosure comprises processing, by the processing unit [104A], the one or more alarm
15 messages to convert the one or more formats into a simplified message format. The
one or more alarm messages may also be processed via an Operation Support System (OSS). The processing unit [104A] may be a unit capable of processing data and converting input into output by processing data, and may also be a processor capable of implementing the features if the present disclosure. The OSS may be a
20 system capable of handling different formats of messages and interpretation of
associated information. The OSS can identify whether the problem in the network is a site related problem or randomly occurring throughout the geography. The OSS can also initiate action in either case by sending the field staff to the site or take up with the SMEs/vendor for further analysis and resolution like tuning the parameter,
25 software upgrade, etc. The simplified message format refers to the format which
converts the complex messages comprising a lot of details into a simpler format which provides information in a simpler way.
[0076] At step [208], the method [200] as disclosed by the present disclosure
30 comprises identifying, by an identification unit [106A], data associated with the one
22

or more alarms based at least on the simplified message format. The data associated with one or more alarms refers to the information related to the alarm.
[0077] In an implementation of the present disclosure, the data comprises at least
5 one of one or more cell sites of occurrence of the one or more alarms, and an extent
of impact on the cell sites. The one or more cell sites of occurrence of the one or
more alarms may be the information related to the faults/issues which are detected
by the EMS [114A] specifically related to the location or identifier of the
cell/terminals/gNodeB at which the error/fault/issue has been occurred. The extent
10 of the impact of the cell sites may refer to the impact which has occurred on the
coverage due to such faults/errors/issues at the particular cell.
[0078] At step [210], the method [200] as disclosed by the present disclosure comprises generating, by the processing unit [104A], at least one visual format of
15 at least the one or more alarms for displaying on at least one geographical region
based at least on the identified data. The at least one visual format may be a format for displaying the information related to the alarms for a particular cell. The at least one geographical region may be the region at which the alarm has been generated due to certain faults/issues.
20
[0079] In an implementation of the present disclosure, the processing unit [104A] tags at least one attribute to the one or more alarm messages. The at least one attribute may in another implementation be an outage alarm or a performance degradation. The outage alarm refers to the alarm where the cell has stopped
25 working due to certain issues such as power outage. The performance degradation
refers to the attributes where the cell is not working at an optimum level and has been not able to function efficiently and effectively.
[0080] In an implementation of the present disclosure, the method further
30 comprises displaying, by a display unit [108A] the at least one visual format of at
least the one or more alarms on at least one geographical region in one or more
23

views, wherein the one or more views are configurable based at least on an input.
Further, in another implementation of the present disclosure, the one or more views
comprises at least an active alarm view, a site view, and a live alarm view. In an
implementation, the active alarm view depicts the details of one or more active
5 alarms (i.e., unresolved issues), the site view depicts details of one or more issues
at one or more cell sites / sites of a network entity, and the live alarm view depicts details of one or more issues that are occurring at a network entity in real time and/or in near real time.
10 [0081] In an implementation of the present disclosure, each of the alarm messages
are stored within a repository [110A] for creating an alarm history. The repository [110A] refers to a storage which stores the source codes and may also be a storage unit [112A] which is capable of storing information. The alarm history refers to the history of previous alarms and contains the information related to the previous
15 alarms. The one or more views further provides an access for checking the alarm
history. The access for checking the alarm history may refer to the providing an option for accessing the alarm history in the one or more views.
[0082] In an implementation of the present disclosure, the method [200] further
20 comprises downloading, by the processing unit [104A] via the interface, an alarm
report corresponding to the at least one visual format of at least the one or more alarms and then storing, by the processing unit [104A], the downloaded alarm report in a storage unit [112A]. The alarm report is made based on the at least one visual format which contains the information related to the one or more alarms. 25
[0083] Thereafter, the method terminates at step (212).
[0084] Furthermore, according to exemplary implementations of the present
disclosure a fault management system may be provided that may have a fault
30 management architecture for providing implementation of visualization of one or
more alarms for different scenarios. The Architecture may include various stages of
24

alarm parsing right from the ingestion of streaming alarm data from Vendor Element Management System to the storage of the alarms in the database. This architecture is common for all the three scenarios i.e., Active Alarm Tabular View (also interchangeably used with active alarm view), Site View and Live Alarm View. 5
[0085] According to the present disclosure the alarm messages are streamed from
the vendor EMS [114A] to the North Bound Interface (NBI) interface [116A]. It is
to be noted that the messages are streamed from the vendor EMS [114A] adopting
different alarm message format. OSS System (Operation Support System) should
10 be robust and able to handle any format and interpret the alarms with all relevant
attributes. These alarms are further enriched with geographical and other allied information and stored in the active database and the cleared alarms are moved to the history database.
15 [0086] Further, various scenarios according to the present disclosure are provided
as below:
[0087] Scenario 1: Visualization of Active Alarms is provided as below:
20 [0088] The active alarms are processed in near real time and are visible in the
graphical user interface (GUI) to the operation team without any delay.
[0089] Referring to FIG. 3, an exemplary active alarm tabular view, in accordance with exemplary implementations of the present disclosure is provided. This feature
25 also provides the user the facility to view the alarms based on different filters. The
filters include visualisation of the alarms, vendor wise - for visualisation of the alarms based on different vendors. The filters further include visualisation of alarms, technology wise - for any geography starting from National level to the smallest entity of the business cluster. The filters further include visualisation of
30 alarms, node wise - for different types of network nodes ranging from Macro nodes
to small nodes. Also, operation engineer can view any site of his choice. The active
25

alarm report for any vendor at any geography can be downloaded for further
information and analysis. The active alarm tabular view comprises various
information in tabular format such as event time, circle, state (location), vendor
names and one or more identifiers. The active alarm tabular view may also comprise
5 information associated with type of alarm, reason of alarm, information related to
one or more faults, identifier of alarm, geographical location, vendor name, alarm severity, an identifier associated with an enterprise resource planning software, an identifier associated with a site, alarm name, number of occurrences, and some other allied information.
10
[0090] Referring to FIG. 4, an exemplary sequence diagram indicating the process of implementation of visualization of alarms for different scenarios is shown, in accordance with exemplary implementations of the present disclosure. As indicated in the FIG. 4 at step 1, a Web Server/User Interface (UI) sends an HTTP request to
15 a Fault Management MicroService (FM MicroService) which processes request and
then at step 2, sends a HTTP response to the web server/UI. The HTTP request and HTTP response respectively comprises information related to a request and response related to active alarms 5G data visualisation, active alarms 5G data count, download all 5G active alarm, and/or service affecting alarm data count etc. At step
20 3, The FM MicroService sends a REST API request to the rest layer. The REST
layer sends a request, at step 4, seeking active alarms as “Get Active Alarms” to a service layer. The service layer, at step 5, sends a query for alarm data to a database collection which returns a result at step 6, which is then sent to the rest layer which contains information associated with active alarms. The rest layer, at step 7, also
25 sends a request seeking active alarms count for which the service layer sends a
query, at step 8, for alarm count to the data collection, the data collection return a result, at step 9, to the service layer which sends the information related to the count of active alarms to the rest layer. At step 10, the rest layer also sends a request to the service layer for downloading alarms, the service layer, at step 11, sends a query
30 seeking alarm data to the database collection, which returns a result at step 12. The
returned result is sent to the service layer which further sends the result information
26

to the rest layer. The rest layer, at step 13, also sends a request to the service layer
for seeking a count for services affected alarm which sends a query at step 14,
seeking count for service affecting alarm to the database collection. The database
collection returns a result, at step 15 to the service layer, which sends the result to
5 the rest layer. The rest layer, at step 16, sends the received responses associated with
information related to the alarm in response to the Rest API Request.
[0091] Scenario 2: Visualization of Alarm for any site in the Map Layer is provided as below: 10
[0092] Map layer view of the site is a unique feature which provides multiple information like Alarms, KPI’s, Properties, Capacity and Configuration of the selected site.
15 [0093] The Properties option gives the wealth of information regarding the physical
properties which include not only Lat- Long, Azimuth but also equipment configuration like Band, etc along with the location of the site.
[0094] A site icon is dynamically updated on daily basis as per the configuration of
20 the Band and its azimuth available from the configuration dump.
[0095] Based on the site search on the map layer for different types of nodes, the active and history alarms are made available by selecting the alarm option in the site icon of the map layer.
25
[0096] Furthermore, Referring to FIG. 5, an exemplary sequence diagram for site view in the map layer is illustrated, in accordance with exemplary implementations of the present disclosure. As indicated in the FIG. 5 an App Server/UI sends a request, at step 501, seeking information related to spider view macro active alarm
30 listing to the rest layer for finding Macro Active Alarms, the REST layer, at step
502, request the service layer, which request, at step 503, a data access objects
27

(DAO) layer, then the DAO layer sends a request, at step 504, for data to an Alarm
Library which sends, at step 505, a query for data to a Database 1. The database 1
stores information related to active alarm, and executes the query and then provides
the result to the rest layer, at step 509, through the Alarm Library at step 506, DAO
5 layer at step 507, and Service layer at step 508. At step 510, the rest layer provides
the result to the App server/ UI. The App Server/ UI sends a request, at step 511, to the rest layer for spider view macro history alarm listing, and the rest layer sends a request, at step 512, to the service layer to get Macro Alarms history. The service layer sends a request, at step 513, for data through the DAO layer, to the Alarm
10 Library, at step 514, which sends, at step 515, a query to the Database 2. The
database 2 stores information related to alarm history and executes the query and provides the result for macro alarm history to the rest layer at step 519, through the Alarm Library at step 516, DAO layer at step 517, and Service layer at step 518. Then, at step 520, the rest layer provides the result to the App Server/UI. The App
15 Server/ UI sends a request, at step 521, for downloading all macro active alarm and
alarm history to the rest layer, the rest layer sends a request, at step 522, to the service layer for downloading the Macro alarms. The service layer sends a request, at step 523, for data and creating a report to the DAO layer. The DAO layer sends a request, at step 524, for data to the alarm library which sends a query for data to
20 the databases. The Alarm library sends the query to the database 1 at step 525, and
database 2 at step 526. The database 1 and 2 executes the query and sends the information to the rest layer, at step 531, through the Alarm Library at step 527, and step 528, DAO layer at step 529, and the Service layer at step 530. At step 532, the rest layer provides the result to the App Server/ UI.
25
[0097] In an exemplary implementation of the present disclosure, a map layer site view, an alarm view for map layer site, and a map layer site properties view are provided for visualization of alarm for any site in the Map Layer.
30 [0098] Referring to FIG. 6 and FIG. 7, an exemplary map layer site view is
illustrated, in accordance with exemplary implementations of the present
28

disclosure. The FIG. 6 shows a view of a map layer comprising various network
nodes at various locations which are illustrated on a geographical map. FIG. 7
shows the map layer site view which is visualised after clicking on a certain network
node as shown in FIG. 6. Further, FIG. 7 shows various options for selecting one or
5 more options such as the alarm, KPIs, properties, capacity, configurations, among
other options as well.
[0099] Also, FIG. 8 illustrates an exemplary alarm view, in accordance with exemplary implementations of the present disclosure. The alarm view is illustrated
10 as a part of the map layer visualisation, which may be visualised after selection of
the one or more options as the alarm as provided in the FIG. 7. The alarm view visualisation may illustrate information associated with an identifier type of alarm, reason of alarm, information related to one or more faults, identifier of alarm, geographical location, vendor name, alarm severity, an identifier associated with an
15 enterprise resource planning software, an identifier associated with a site, alarm
name, number of occurrences, and some other allied information.
[0100] Scenario 3: Visualization of live alarms is provided as below:
20 [0101] NOC team focuses majorly on Service Affecting alarms for prioritizing the
resolution.
[0102] Live Alarms provides near real time view of the alarm and the outage site count for a desired geography. 25
[0103] It also provides the ageing of the alarms along with report download functionality.
[0104] In addition, operation team can also visualize the Service Affecting Alarm
30 trend for any selected alarm and for any geography and drill down to the site level.
29

[0105] Visualization of Live Alarms will help the centralized NOC team to monitor the impacted area on map view and accordingly can drive the field team to take action and rectify the issue on priority.
5 [0106] Live alarm details are updated periodically in near real time via the
streaming alarm messages. Only service affecting alarms and unique outage site
count is considered in Live Alarms as these are the alarms which impacts the
services in an area. Operation team can navigate between the desired geographies
from National level view and drill down to Business Cluster view. In addition, by
10 selecting any Business cluster, it can be drill down to site level for further analysis
which is also downloadable. Operation team can also view the ageing of the outage sites so as to prioritize and to rectify the same.
[0107] Live Alarm view also provides the trend of each of the Service Affecting
15 alarm on a chosen geography. Operation team can select any of the Service
Affecting alarms for any geography and analyse the trend of the alarms to the tune of n days (e.g., 15 days) which can further be drilled down to the Site level along with the information of the number of occurrences of the alarm Site wise.
20 [0108] Further, Operation team can easily identify whether it is a Site related
problem or randomly occurring throughout the geography. Accordingly, Operation team can initiate action in either case by sending the Field staff to the site or take up with the SMEs/Vendor for further analysis and resolution like tuning the parameter, software upgrade, etc.
25
[0109] Live alarm gives a single pane view of the Network status which can be used effectively by Network Operation Centre engineers to prioritize the resolutions and also find out the root cause of the problems. By this feature, there is a signification reduction of analysis time taken by the Operations team as manual
30 computation is totally avoided.
30

[0110] Referring to FIG. 9 and FIG. 10, exemplary live alarm views are illustrated,
in accordance with exemplary implementations of the present disclosure. The
visualisations (both under FIG. 9 as well as FIG. 10) shows the number of on-Air
sites, and number of outage sites based on states or geographical locations of the
5 one or more alarms, where the one or more alarms are associated with outage sites.
Both of the figures illustrate different exemplary illustrations of the visualisation.
[0111] Referring to FIG. 11, another exemplary active alarm age view is illustrated,
in accordance with exemplary implementations of the present disclosure. The
10 visualisation illustrates a site count of standalone sites and non-standalone sites.
The visualisation illustrates active alarms associated with standalone sites and non-standalone sites on a time-period basis.
[0112] Referring to FIG. 12, another exemplary alarm-trends view is illustrated, in
15 accordance with exemplary implementations of the present disclosure. The
visualisation illustrates a count of alarms based on different types of alarms illustrating a trend of occurrence of alarms.
[0113] Referring to FIG. 13, another exemplary alarm history view is illustrated, in
20 accordance with exemplary implementations of the present disclosure. The
visualisation illustrates a history of the alarms for each type of alarm illustrating
another trend of occurrence of alarms. The visualisation shows day-wise occurrence
of alarms. The visualisation may comprise information such as type of alarm, reason
of alarm, information related to one or more faults, identifier of alarm, geographical
25 location, vendor name, alarm severity, an identifier associated with enterprise
resource planning software, an identifier associated with site, alarm name, number of occurrences, and some other allied information.
[0114] Therefore, the present disclosure discloses implementation of visualization
30 of alarms for different scenarios. According to present disclosure initially a plurality
of alarm messages is received. In an implementation the plurality of alarm messages
31

includes SNMP protocol-based alarm messages. Further, the plurality of alarm
messages is processed and are converted into a simpler format for example in text
format. Next, details related to the alarms are identified based on the text, for
example the details such as a cell location where the alarms happened, is the entire
5 cell site is affected or some of the cells on the cell site are affected etc. Next, the
implementation of visualization of alarms for different scenarios is provided based on the identified details related to the alarms.
[0115] Another aspect of the present disclosure may also relate to a user equipment
10 comprising a processor. The processor is configured to send a request to a system
[100A], to display one or more alarms associated with a network in at least one visual format. The processor is further configured to receive from the system [100A], the at least one visual format of the one or more alarms. The at least one visual format of the one or more alarms is generated by the system [100A] based
15 on receiving, by the system [100A] via a North Bound Interface (NBI) [116A], one
or more alarm messages from at least one Element management system (EMS) [114A], wherein the one or more alarm messages are received in one or more formats. Further, the generation of the visual format is further based on processing, by the system [100A], the one or more alarm messages to convert the one or more
20 formats into a simplified message format. The generation of the visual format is
further based on identifying, by the system [100A], a data associated with the one or more alarm messages based at least on the simplified message format. Further, the generation of the visual format is further based on generating, by the system [100A], at least one visual format of at least the one or more alarms for displaying,
25 based at least on the identified data.
[0116] Also, an aspect of the present disclosure may relate to a non-transitory
computer readable storage medium storing one or more instructions for
visualization of one or more alarms in a network. The one or more instructions
30 comprises executable code which, when executed by one or more units of a system
[100A], causes the one or more units of the system [100A] to perform certain
32

functions. The one or more instructions when executed causes a receiving unit
[102A] of the system [100A] to receive via a North Bound Interface (NBI) [116A],
one or more alarm messages from at least one Element management system (EMS)
[114A], wherein the one or more alarm messages are received in one or more
5 formats. The one or more instructions when executed further causes a processing
unit [104A] of the system [100A] to process the one or more alarm messages to
convert the one or more formats into a simplified message format. The one or more
instructions when executed further causes an identification unit [106A] of the
system [100A] to identify a data associated with the one or more alarms based at
10 least on the simplified message format. The one or more instructions when executed
further causes the processing unit [104A] to generate at least one visual format of at least the one or more alarms on at least one geographical region based at least on the identified data.
15 [0117] As is evident from the above, the present disclosure provides a technically
advanced solution of implementation of visualization of alarms for different scenarios. Mainly, the present disclosure provides three different scenarios for monitoring the Alarms at National level almost in a near real time i.e., Active Alarm Tabular View, Site View, and Live Alarm View. Also, to the operation team, an
20 option is provided to view the ageing of the outage sites so as to prioritize and to
rectify the same.
[0118] Moreover, based on the present disclosure NOC engineer can monitor the live alarm view for any vendor at any desired geography and can easily take action
25 to improve the network uptime and hence customer experience. This feature can be
used as a monitoring tool in case of any events or festivals or VIP sites wherein live monitoring is required to keep 100% uptime for customer experience. Further, the Map layer Site Alarm view feature enables the operation team for quick resolution of customer complaint by having the alarm information on the map layer for both,
30 serving cell and neighbour cell based on the customer location. This also helps the
Customer care agents to identify the Outage sites based on customer location and
33

accordingly service ticket can be issued to the field staff for early resolution and
inform the customer the expected time of resolution. Furthermore, NOC user can
visualize and monitor the outage sites and ageing of the alarms in near real time
through a graphical view and can be drilled down from National level to Business
5 Cluster/Site level.
[0119] While considerable emphasis has been placed herein on the disclosed
implementations, it will be appreciated that many implementations can be made and
that many changes can be made to the implementations without departing from the
10 principles of the present disclosure. These and other changes in the implementations
of the present disclosure will be apparent to those skilled in the art, whereby it is to be understood that the foregoing descriptive matter to be implemented is illustrative and non-limiting.
15 [0120] Further, in accordance with the present disclosure, it is to be acknowledged
that the functionality described for the various components/units can be implemented interchangeably. While specific embodiments may disclose a particular functionality of these units for clarity, it is recognized that various configurations and combinations thereof are within the scope of the disclosure. The
20 functionality of specific units as disclosed in the disclosure should not be construed
as limiting the scope of the present disclosure. Consequently, alternative arrangements and substitutions of units, provided they achieve the intended functionality described herein, are considered to be encompassed within the scope of the present disclosure.
34

We Claim:
1. A method for visualization of one or more alarms in a network, comprising:
- receiving, by a receiving unit [102A] via a North Bound Interface (NBI) [116A], one or more alarm messages from at least one Element management system (EMS) [114A], wherein the one or more alarm messages are received in one or more formats;
- processing, by a processing unit [104A] the one or more alarm messages to convert the one or more formats into a simplified message format;
- identifying, by an identification unit [106A], a data associated with the one or more alarms based at least on the simplified message format; and
- generating, by the processing unit [104A], at least one visual format of at least the one or more alarms for displaying, based at least on the identified data.

2. The method as claimed in claim 1, further comprises tagging, by the processing unit [104A], at least one attribute to the one or more alarm messages.
3. The method as claimed in claim 2, wherein the at least one attribute comprises one of an outage alarm, and a performance degradation.
4. The method as claimed in claim 1, further comprising:
- displaying, by a display unit [108A], the at least one visual format of at
least the one or more alarms on at least one geographical region in one
or more views, wherein the one or more views are configurable based at
least on an input.
5. The method as claimed in claim 4, wherein the one or more views comprises
at least one of an active alarm view, a site view, and a live alarm view.

6. The method as claimed in claim 4, wherein each of the one or more alarm messages are stored in a repository [110A] to create an alarm history.
7. The method as claimed in claim 6, wherein the one or more views provide an access for checking the alarm history.
8. The method as claimed in claim 1, wherein the data comprises at least one of one or more cell sites of occurrence of the one or more alarms, and an extent of impact on the one or more cell sites.
9. The method as claimed in claim 1, wherein the one or more formats comprises at least a Simple Network Management Protocol (SNMP) format.
10. The method as claimed in claim 1, further comprising:

- downloading, by the processing unit [104A], an alarm report corresponding to the at least one visual format of at least the one or more alarms; and
- storing, by a storage unit [112A], the downloaded alarm report.
11. A system [100A] for visualization of one or more alarms in a network, the
system [100A] comprising:
- a receiving unit [102A], configured to receive, via a North Bound Interface (NBI) [116A], one or more alarm messages from at least one Element management system (EMS) [114A], wherein the one or more alarm messages are received in one or more formats;
- a processing unit [104A] connected to at least the receiving unit [102A], the processing unit [104A] configured to process, the one or more alarm messages to convert the one or more formats into a simplified message format;
- an identification unit [106A] connected to at least the processing unit [104A], the identification unit [106A] configured to identify a data

associated with the one or more alarms based at least on the simplified message format; and - the processing unit [104A], configured to generate at least one visual format of at least the one or more alarms for displaying, based at least on the identified data.
12. The system [100A] as claimed in claim 11, wherein the processing unit [104A] is further configured to tag at least one attribute to the one or more alarm messages.
13. The system [100A] as claimed in claim 12, wherein the at least one attribute comprises one of an outage alarm, and a performance degradation.
14. The system [100A] as claimed in claim 11, further comprises a display unit [108A], configured to display the at least one visual format of at least the one or more alarms on at least one geographical region in one or more views, wherein the one or more views are configurable based at least on an input.
15. The system [100A] as claimed in claim 14, wherein the one or more views comprises at least one of an active alarm view, a site view, and a live alarm view.
16. The system [100A] as claimed in claim 14, further comprises a repository [110A] to store each of the one or more alarm messages to create an alarm history.
17. The system [100A] as claimed in claim 16, wherein the one or more views provide an access for checking the alarm history.

18. The system [100A] as claimed in claim 11, wherein the data comprises at least one of one or more cell sites of occurrence of the one or more alarms, and extent of impact on the one or more cell sites.
19. The system [100A] as claimed in claim 11, wherein the one or more formats comprises at least a Simple Network Management Protocol (SNMP) format.
20. The system [100A] as claimed in claim 11, wherein the processing unit [104A] is further configured to download an alarm report corresponding to the at least one visual format of at least the one or more alarms.
21. The system [100A] as claimed in claim 20, further comprises a storage unit [112A], configured to store the downloaded alarm report.
22. A user equipment comprising: - a processor configured to:
o send a request to a system [100A], to display one or more alarms associated with a network in at least one visual format; and
o receive from the system [100A], the at least one visual format of the one or more alarms,
wherein the at least one visual format of the one or more alarms is generated by the system [100A] based on:
receiving, by the system [100A] via a North Bound Interface (NBI) [116A], one or more alarm messages from at least one Element management system (EMS) [114A], wherein the one or more alarm messages are received in one or more formats, processing, by the system [100A], the one or more alarm messages to convert the one or more formats into a simplified message format,

identifying, by the system [100A], a data associated with the one or more alarm messages based at least on the simplified message format, and
generating, by the system [100A], at least one visual format of at least the one or more alarms for displaying, based at least on the identified data.