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

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

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

FIELD OF THE INVENTION
[0001] The present invention relates to wireless communication system, more particularly relates to method and system for monitoring one or more alarms in a network.
BACKGROUND OF THE INVENTION
[0002] With the rapid growth in telecom technology, Network Management System (NMS) monitoring plays a vital role in a network’s performance. In NMS, an alarm is raised whenever an issue occurs and then when it is addressed. As such, this happens recursively. An operation team logs into a user interface (UI) and manually fetches the alarm data by clicking on filter options available on the UI. For example, when they want to monitor for two nodes (e.g. node A, node B), they click on a filter option and select the node A and node B. Then, a request is sent to the backend, and in response, alarm data of node A and node B is obtained. Since there can be lakhs of alarms, every time the operations team has to manually fetch the data and monitor.
[0003] It is, therefore, desirable to provide an efficient solution for live monitoring of alarms via a secure, highly available, responsive, and user-friendly interface. Further, it is desirable to provide various filters and reporting options for efficient monitoring.
SUMMARY OF THE INVENTION
[0004] One or more embodiments of the present disclosure provide a method and a system for monitoring one or more alarms in a network.
[0005] In one aspect of the present invention, the system for monitoring the one or more alarms in the network is disclosed. The system includes a retrieving unit configured to retrieve information pertaining to a user from a database in response to registration of the user via a network equipment. The system further includes a receiving unit configured to receive a request from the network equipment to retrieve one or more alarms assigned to one or more network elements and operation contexts. The system further includes a transmittal unit configured to transmit notifications pertaining to the one or more alarms assigned to the one or more network elements and operation contexts and the one or more alarms related to the one or more network elements and the operation contexts to the network equipment of the user.
[0006] In an embodiment, the transmittal unit is configured to transmit a plurality of alarms assigned to the one or more network elements and the operation contexts to the user interface, on receiving the request from the user interface.
[0007] In an embodiment, the information includes an identifier pertaining to the user, a communication protocol address, and identifier pertaining to one or more network elements and operation contexts. In an embodiment, the user is one of a network operator and a customer.
[0008] In an embodiment, a service provider assigns the one or more alarms corresponding to the one or more network elements and operation contexts to be monitored by the user.
[0009] In an embodiment, an assigning unit configured to assign each of the one or more alarms to the user.
[0010] In an embodiment, an establishment unit configured to establish a web socket connection with a load balancer in response to registration of the user via the network equipment with a network manager unit.
[0011] In an embodiment, the system comprises a managing unit configured to transmit the request towards the network manager unit to process the request. The management unit is further configured to retrieve the one or more alarms assigned to the one or more network elements and operation contexts upon processing the request at the network manager. The management unit is further configured to store on retrieving, data of the one or more alarms assigned to the one or more assigned network elements and the operational context in a database.
[0012] In an embodiment, a validation unit configured to validate the one or more assigned network elements and operation contexts on receipt of the request.
[0013] In another aspect of the present invention, the method of monitoring the one or more alarms in the network is disclosed. The method includes the step of retrieving information pertaining to a user from a database in response to registration of the user via a network equipment with the one or more processors. The method further includes the step of receiving a request from the user to retrieve the one or more alarms assigned to one or more network elements and operation contexts. The method further includes the step of transmitting notifications pertaining to the one or more alarms assigned to the one or more network elements and operation contexts and the one or more alarms related to the one or more network elements and the operation contexts to the network equipment of the user.
[0014] In another aspect of the invention, a non-transitory computer-readable medium having stored thereon computer-readable instructions is disclosed. The computer-readable instructions are executed by a processor. The processor is configured to retrieve information pertaining to a user from a database in response to registration of the user via a network equipment. The processor is further configured to receive a request from the network equipment to retrieve the one or more alarms assigned to one or more network elements and operation contexts. The processor is further configured to transmit notifications pertaining to the one or more alarms assigned to the one or more network elements and operation contexts to the network equipment of the user.
[0015] In another aspect of invention, network equipment is disclosed. The network equipment includes one or more primary processors communicatively coupled to one or more processors, the one or more primary processors coupled with a memory. The processor causes the network equipment to register a user with the one or more processors.
[0016] Other features and aspects of this invention will be apparent from the following description and the accompanying drawings. The features and advantages described in this summary and in the following detailed description are not all-inclusive, and particularly, many additional features and advantages will be apparent to one of ordinary skill in the relevant art, in view of the drawings, specification, and claims hereof. Moreover, it should be noted that the language used in the specification has been principally selected for readability and instructional purposes and may not have been selected to delineate or circumscribe the inventive subject matter, resort to the claims being necessary to determine such inventive subject matter.
BRIEF DESCRIPTION OF THE DRAWINGS
[0017] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in which like reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Some drawings may indicate the components using block diagrams and may not represent the internal circuitry of each component. It will be appreciated by those skilled in the art that disclosure of such drawings includes disclosure of electrical components, electronic components or circuitry commonly used to implement such components.
[0018] FIG. 1 is an exemplary block diagram of an environment for monitoring one or more alarms in a network, according to one or more embodiments of the present invention;
[0019] FIG. 2 an exemplary block diagram of a system for monitoring the one or more alarms in the network, according to one or more embodiments of the present invention;
[0020] FIG. 3 is a schematic representation of a workflow of the system of FIG. 1, according to the one or more embodiments of the present invention;
[0021] FIG. 4 is an exemplary block diagram of an architecture implemented in the system of the FIG. 2, according to one or more embodiments of the present invention;
[0022] FIG. 5 is a signal flow diagram for monitoring the one or more alarms in the network, according to one or more embodiments of the present invention; and
[0023] FIG. 6 is a schematic representation of a method of monitoring the one or more alarms in the network, according to one or more embodiments of the present invention.
[0024] The foregoing shall be more apparent from the following detailed description of the invention.
DETAILED DESCRIPTION OF THE INVENTION
[0025] Some embodiments of the present disclosure, illustrating all its features, will now be discussed in detail. It must also be noted that as used herein and in the appended claims, the singular forms "a", "an" and "the" include plural references unless the context clearly dictates otherwise.
[0026] Various modifications to the embodiment will be readily apparent to those skilled in the art and the generic principles herein may be applied to other embodiments. However, one of ordinary skill in the art will readily recognize that the present disclosure including the definitions listed here below are not intended to be limited to the embodiments illustrated but is to be accorded the widest scope consistent with the principles and features described herein.
[0027] A person of ordinary skill in the art will readily ascertain that the illustrated steps detailed in the figures and here below are set out to explain the exemplary embodiments shown, and it should be anticipated that ongoing technological development will change the manner in which particular functions are performed. These examples are presented herein for purposes of illustration, and not limitation. Further, the boundaries of the functional building blocks have been arbitrarily defined herein for the convenience of the description. Alternative boundaries can be defined so long as the specified functions and relationships thereof are appropriately performed. Alternatives (including equivalents, extensions, variations, deviations, etc., of those described herein) will be apparent to persons skilled in the relevant art(s) based on the teachings contained herein. Such alternatives fall within the scope and spirit of the disclosed embodiments.
[0028] The present invention provides a system and method of monitoring one or more alarms in a network. Whenever a user logs in, a web-socket is enabled. An alarm will flow into a load balancer and then according to the traffic, it will go to a particular call processor where all the lifecycle processes are performed. Before inserting into an input/output (IO) cache, some extra attributes are added from a fault processor. This process is called enrichment. Thereafter, the response is sent back to the UI through the web-socket. Therefore, the alarm data is visible on the UI. Whenever the alarm is raised, the operation team can see the alarm.
[0029] FIG. 1 illustrates an exemplary block diagram of an environment 100 for monitoring one or more alarms in a network, according to one or more embodiments of the present disclosure. In this regard, the environment 100 includes a network equipment 102, a server 104, a network 106 and a system 108 communicably coupled to each other for monitoring the one or more alarms in the network 106. The network equipment 102 aids a user to register with one or more processors.
[0030] As per the illustrated embodiment and for the purpose of description and illustration, the network equipment 102 includes, but not limited to, a first network equipment 102a, a second network equipment 102b, and a third network equipment 102c, and should nowhere be construed as limiting the scope of the present disclosure. In alternate embodiments, the network equipment 102 may include a plurality of network equipment’s as per the requirement. For ease of reference, each of the first network equipment 102a, the second network equipment 102b, and the third network equipment 102c, will hereinafter be collectively and individually referred to as the “network equipment 102”.
[0031] In an embodiment, the network equipment 102 is one of, but not limited to, any electrical, electronic, electro-mechanical or an equipment and a combination of one or more of the above devices such as virtual reality (VR) devices, augmented reality (AR) devices, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, mainframe computer, or any other computing device.
[0032] The environment 100 includes the server 104 accessible via the network 106. The server 104 may include, by way of example but not limitation, one or more of a standalone server, a server blade, a server rack, a bank of servers, a server farm, hardware supporting a part of a cloud service or system, a home server, hardware running a virtualized server, one or more processors executing code to function as a server, one or more machines performing server-side functionality as described herein, at least a portion of any of the above, some combination thereof. In an embodiment, the entity may include, but is not limited to, a vendor, a network operator, a company, an organization, a university, a lab facility, a business enterprise side, a defense facility side, or any other facility that provides service.
[0033] The network 106 includes, by way of example but not limitation, one or more of a wireless network, a wired network, an internet, an intranet, a public network, a private network, a packet-switched network, a circuit-switched network, an ad hoc network, an infrastructure network, a Public-Switched Telephone Network (PSTN), a cable network, a cellular network, a satellite network, a fiber optic network, or some combination thereof. The network 106 may include, but is not limited to, a Third Generation (3G), a Fourth Generation (4G), a Fifth Generation (5G), a Sixth Generation (6G), a New Radio (NR), a Narrow Band Internet of Things (NB-IoT), an Open Radio Access Network (O-RAN), and the like.
[0034] The network 106 may also include, by way of example but not limitation, at least a portion of one or more networks having one or more nodes that transmit, receive, forward, generate, buffer, store, route, switch, process, or a combination thereof, etc. one or more messages, packets, signals, waves, voltage or current levels, some combination thereof, or so forth. The network 106 may also include, by way of example but not limitation, one or more of a wireless network, a wired network, an internet, an intranet, a public network, a private network, a packet-switched network, a circuit-switched network, an ad hoc network, an infrastructure network, a Public-Switched Telephone Network (PSTN), a cable network, a cellular network, a satellite network, a fiber optic network, a VOIP or some combination thereof.
[0035] The environment 100 further includes the system 108 communicably coupled to the server 104 and the network equipment 102 via the network 106. The system 108 is configured to monitor the one or more alarms in the network 106. As per one or more embodiments, the system 108 is adapted to be embedded within the server 104 or embedded as an individual entity.
[0036] Operational and construction features of the system 108 will be explained in detail with respect to the following figures.
[0037] FIG. 2 is an exemplary block diagram of the system 108 for monitoring the one or more alarms in the network 106, according to one or more embodiments of the present invention.
[0038] As per the illustrated embodiment, the system 108 includes one or more processors 202, a memory 204, a user interface 206, and a database 208. For the purpose of description and explanation, the description will be explained with respect to one processor 202 and should nowhere be construed as limiting the scope of the present disclosure. In alternate embodiments, the system 108 may include more than one processors 202 as per the requirement of the network 106. The one or more processors 202, hereinafter referred to as the processor 202 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, single board computers, and/or any devices that manipulate signals based on operational instructions.
[0039] As per the illustrated embodiment, the processor 202 is configured to fetch and execute computer-readable instructions stored in the memory 204. The memory 204 may be configured to store one or more computer-readable instructions or routines in a non-transitory computer-readable storage medium, which may be fetched and executed to create or share data packets over a network service. The memory 204 may include any non-transitory storage device including, for example, volatile memory such as RAM, or non-volatile memory such as disk memory, EPROMs, FLASH memory, unalterable memory, and the like.
[0040] In an embodiment, the user interface 206 includes a variety of interfaces, for example, interfaces for a graphical user interface, a web user interface, a Command Line Interface (CLI), and the like. The user interface 206 facilitates communication of the system 108. In one embodiment, the user interface 206 provides a communication pathway for one or more components of the system 108. Examples of such components include, but are not limited to, the network equipment 102 and the database 208.
[0041] The database 208 is one of, but not limited to, a centralized database, a cloud-based database, a commercial database, an open-source database, a distributed database, an end-user database, a graphical database, a No-Structured Query Language (NoSQL) database, an object-oriented database, a personal database, an in-memory database, a document-based database, a time series database, a wide column database, a key value database, a search database, a cache databases, and so forth. The foregoing examples of database 208 types are non-limiting and may not be mutually exclusive e.g., a database can be both commercial and cloud-based, or both relational and open-source, etc.
[0042] In order for the system 108 for monitoring the one or more alarms in the network 106, the processor 202 includes one or more modules. In one embodiment, the one or more modules includes, but not limited to, a retrieving unit 210, an establishment unit 212, an assigning unit 214, a receiving unit 216, a validation unit 218, a managing unit 220, and a transmittal unit 222 communicably coupled to each other for monitoring the one or more alarms in the network 106.
[0043] In one embodiment, the one or more modules includes, but not limited to, the retrieving unit 210, the establishment unit 212, the assigning unit 214, the receiving unit 216, the validation unit 218, the managing unit 220, and the transmittal unit 222 can be used in combination or interchangeably for monitoring the one or more alarms in the network 106.
[0044] The retrieving unit 210, the establishment unit 212, the assigning unit 214, the receiving unit 216, the validation unit 218, the managing unit 220, and the transmittal unit 222 in an embodiment, may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processor 202. In the examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processor 202 may be processor-executable instructions stored on a non-transitory machine-readable storage medium and the hardware for the processor may comprise a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the memory 204 may store instructions that, when executed by the processing resource, implement the processor. In such examples, the system 108 may comprise the memory 204 storing the instructions and the processing resource to execute the instructions, or the memory 204 may be separate but accessible to the system 108 and the processing resource. In other examples, the processor 202 may be implemented by electronic circuitry.
[0045] In one embodiment, when the user registers via the network equipment 102, the retrieving unit 210 is configured to retrieve the information pertaining to a user from the database 208. The information includes an identifier pertaining to the user, a communication protocol address, and identifier pertaining to one or more network elements and operation contexts. The identifier pertaining to the user includes, but not limited to, username or user identifier (ID), email address, phone number, account number, authentication token, social security number or national ID. The communication protocol address includes, but not limited to, Internet Protocol address (IP address), Media Access Control Address (MAC address), port number, Uniform Resource Locator (URL), Uniform Resource Identifier (URI). The identifier pertaining to one or more network elements and operation contexts includes, but not limited to, network element identifier, operational context identifier, alarm ID, configuration profile ID. The user is one of a network operator and a customer.
[0046] In response to registration of the user via the network equipment 102 with a network manger unit, the establishment unit 212 is configured to establish a web socket connection with a load balancer.
[0047] In an embodiment, the assigning unit 214 is configured to assign each of one or more alarms to the user. The one or more alarms include, but not limited to performance alarms, fault alarms, security alarms, configuration alarms, environmental alarms, operational alarms. In an embodiment, a service provider assigns the one or more alarms corresponding to the one or more network elements and operation contexts to be monitored by the user. The network elements include, but are not limited to, routers, switches, firewalls, servers, load balancers, access points, modems, network storage devices, controllers, VoIP devices. The operation contexts refer to the various environments, conditions, and scenarios under which the network 106 operates. The operation contexts include, but are not limited to service types, geographical locations, time-based operations, user and device types, security, network segments, application-specific- contexts, compliance and Service Level Agreements (SLA).
[0048] Upon assigning the one or more alarms corresponding to the one or more network elements and operation contexts, the receiving unit 216 is configured to receive a request from the network equipment 102 to retrieve one or more alarms assigned to one or more network elements and operation contexts. The request includes, but not limited to, identifier information, alarm specification, network elements and contexts, authentication and authorization details.
[0049] On receipt of the request from the network equipment 102, the validation unit 218 is configured to validate the one or more assigned network elements and operation contexts. The validation of the one or more assigned network elements and operation contexts involves verifying the validity, accuracy and authorization of the network elements and their associated operational contexts that are included in the request. The validation of the one or more assigned network elements and operation contexts includes, but not limited to, checking user credentials, verifying network elements, checking operation contexts, cross-reference with the database 208. On successful validation, the notifications pertaining to the one or more alarms assigned to the one or more network elements and operation contexts are transmitted to the network equipment 102 of the user. Alternatively, on unsuccessful validation the error response such as unauthorized access, non-existent network elements, incorrect operational contexts are transmitted to the network equipment 102 of the user.
[0050] In an embodiment, the managing unit 220 is configured to transmit the request towards the network manager unit to process the request. Upon processing the request at the network manager unit, the one or more alarms assigned to the one or more network elements and operation contexts are retrieved. On retrieving the data of the one or more alarms assigned to the one or more assigned network elements and operational contexts are stored in the database 208. Thereafter, the transmittal unit 222 is configured to transmit notifications pertaining to the one or more alarms assigned to the one or more network elements and operation contexts to the network equipment 102 of the user.
[0051] In an embodiment, the request from the network equipment 102 involves one or more alarms assigned to one or more network elements and operation contexts with filters. The one or more alarms assigned to one or more network elements and operation contexts are filtered based on multiple attributes with logical AND/OR conditions. The attributes support range filter, contains, not-contains, equal and not equal filters. Thereafter, the transmittal unit 222 is configured to transmit notifications pertaining to the one or more alarms related to the one or more network elements and the operation contexts to the network equipment 102 of the user.
[0052] In an embodiment, on receiving the request from the user interface 206, the transmittal unit 222 is configured to transmit a plurality of alarms assigned to the one or more network elements and the operation contexts to the user interface 206.
[0053] Therefore, the system 108 is configured to provide easy live monitoring of alarms in the network 106. Further, the system 108 provides user-based segregation of network monitoring and various customizable filters for monitoring of required alarms.
[0054] FIG. 3 describes a preferred embodiment of the system 108 of FIG. 2, according to various embodiments of the present invention. It is to be noted that the embodiment with respect to FIG. 3 will be explained with respect to the first network equipment 102a and the system 108 for the purpose of description and illustration and should nowhere be construed as limited to the scope of the present disclosure.
[0055] As mentioned earlier in FIG. 1, each of the first network equipment 102a the second network equipment 102b, and the third network equipment 102c may include an external storage device, a bus, a main memory, a read-only memory, a mass storage device, communication port(s), and a processor. The exemplary embodiment as illustrated in FIG. 3 will be explained with respect to the first network equipment 102a without deviating from the scope of the present disclosure and the limiting the scope of the present disclosure. The first network equipment 102a includes one or more primary processors 302 communicably coupled to the one or more processors 202 of the system 108.
[0056] The one or more primary processors 302 are coupled with a memory 304 storing instructions which are executed by the one or more primary processors 302. Execution of the stored instructions by the one or more primary processors 302 enables the first network equipment 102a to register a user with one or more processers.
[0057] As mentioned earlier in FIG. 2, the one or more processors 202 of the system 108 is configured for monitoring the one or more alarms in the network 106. As per the illustrated embodiment, the system 108 includes the one or more processors 202, the memory 204, the user interface 206, and the database 208. The operations and functions of the one or more processors 202, the memory 204, the user interface 206, and the database 208 are already explained in FIG. 2. For the sake of brevity, a similar description related to the working and operation of the system 108 as illustrated in FIG. 2 has been omitted to avoid repetition.
[0058] Further, the processor 202 includes the retrieving unit 210, the establishment unit 212, the assigning unit 214, the receiving unit 216, the validation unit 218, the managing unit 220, and the transmittal unit 222. The operations and functions of the retrieving unit 210, the establishment unit 212, the assigning unit 214, the receiving unit 216, the validation unit 218, the managing unit 220, and the transmittal unit 222 are already explained in FIG. 2. Hence, for the sake of brevity, a similar description related to the working and operation of the system 108 as illustrated in FIG. 2 has been omitted to avoid repetition. The limited description provided for the system 108 in FIG. 3, should be read with the description as provided for the system 108 in the FIG. 2 above, and should not be construed as limiting the scope of the present disclosure.
[0059] FIG. 4 is an exemplary block diagram of an architecture 400 implemented in the system 108 for monitoring the one or more alarms in the network 106, according to one or more embodiments of the present invention.
[0060] The architecture 400 includes user and session management 402, Network Management System User Interface (NMS UI) 404, load balancer 406, and network Management System cluster (NMS cluster) 408 are communicably coupled to each other for monitoring the one or more alarms in the network 106. The NMS cluster 408 includes one or more NMS clusters such as NMS cluster 1, NMS cluster 2, NMS cluster 3.
[0061] In an embodiment, when a user logged into the NMS UI 404, the user and session management 402 check whether it is a user or an Admin. Accordingly, a request is transmitted to the load-balancer 406. Further the load balancer 406 distributes the incoming request among load balance cluster 1, load balance cluster 2, load balance cluster 3. The load balance cluster 1, load balance cluster 2, load balance cluster 3 further distributes the incoming request to the NMS cluster 408 (NMS cluster 1, NMS cluster 2, NMS cluster 3).
[0062] The NMS cluster 408 is configured to perform live alarm monitoring at node level, pan-India level and particular instance level. Thereafter, the NMS cluster 408 responds back to the load-balancer 406 and transmits to the NMS UI 404.
[0063] More specifically, for live monitoring of alarms, a web-socket protocol is used. The users are notified via the web-socket for only those alarms which they are monitoring instead of sending all the alarms. In an embodiment, the users are assigned with the one or more network elements and operation contexts alarm to monitor. When a user logs in, a web-socket connection is created with the load balancer 406 and the assigned one or more network elements and operation contexts are fetched from the NMS cluster and accordingly the request for alarms is transmitted to the user via the NMS UI 404. The web-socket address along with assigned one or more network elements and operation contexts are stored in the database 208. Fault service may use the web-socket addresses to send live alarms to corresponding users instead of all users.
[0064] In an embodiment, while sending on-demand requests by the user, assigned one or more network elements and operation contexts along with filters are sent in each alarm requests. The assigned one or more network elements and operation contexts are validated at NMS cluster 408, a query is executed, and accordingly response is generated and sent back to the NMS UI 404. For example, if a user wants to see alarms between June 1 to July 15, they are provided with search options to filter out greater than June 1 and lesser than July 15. Once the filter is applied, the user will be able to see the alarm between June 1 and July 15. Further, for example, if the user wants to search for the particular alarm ID, they can (if the user knows the particular alarm ID) go to the free text search, then they can click on alarm ID and enter the particular alarm ID which has to be searched.
[0065] In an embodiment, for communicating with the NMS cluster 408, Representational State Transfer (REST) Application Programming Interface (API) may be used.
[0066] FIG. 5 is a signal flow diagram for monitoring the one or more alarms in the network, according to one or more embodiments of the present invention.
[0067] At step 502, a user is registered via the network equipment 102. The user is one of network operator and a customer.
[0068] At step 504, in response to registration of the user via the network equipment 102, the information pertaining to the user is retrieved from the database 208. The information includes an identifier pertaining to the user, a communication protocol address, and identifier pertaining to one or more network elements and operation contexts.
[0069] At step 506, in response to registration of the user via the network equipment 102 with the network manger unit, the web socket connection with the load balancer 406 is established.
[0070] At step 508, a request is received from the user via the network equipment 102 to retrieve the one or more alarms assigned to the one or more network elements and operation contexts. Further, each of the one or more alarms is assigned to the user. In particular, the service provider assigns the one or more alarms corresponding to the one or more network elements and operation contexts to be monitored by the user.
[0071] At step 510, on receipt of the request received from the user via the network equipment 102, the one or more assigned network elements and operation contexts are validated.
[0072] At step 512, upon validating the request, the request is transmitted to the network manager unit to process the request.
[0073] At step 514, upon processing the request at the network manager unit, the one or more alarms assigned to the one or more network elements and operation contexts are retrieved.
[0074] At step 516, on retrieving, the data of the one or more alarms assigned to the one or more assigned network elements and the operational context is stored in the database 208.
[0075] At step 518, subsequently, notifications pertaining to the one or more alarms assigned to the one or more elements and operation contexts and the one or more alarms related to the one or more network elements and the operation contexts to the network equipment 102 of the user.
[0076] FIG. 6 is a flow diagram of a method 600 for monitoring the one or more alarms in the network 106, according to one or more embodiments of the present invention. For the purpose of description, the method 600 is described with the embodiments as illustrated in FIG. 2 and should nowhere be construed as limiting the scope of the present disclosure.
[0077] At step 602, the method 600 includes the step of retrieving the information pertaining to the user from the database by the retrieving unit 210, in response to registration of the user via the network equipment 102. The information includes an identifier pertaining to the user, a communication protocol address, and identifier pertaining to one or more network elements and operation contexts. The user is one of a network operator and a customer.
[0078] In response to registration of the user via the network equipment 102, the web socket connection is established with a load balancer by the establishment unit 212. In one embodiment, the each of the one or more alarms are assigned to the user by the assigning unit 214. The service provider assigns the one or more alarms corresponding to the one or more network elements and operation contexts to be monitored by the user.
[0079] At step 604, the method 600 includes the step of receiving the request from the user to retrieve the one or more alarms assigned to one or more network elements and operation contexts by the receiving unit 216. On receipt of the request, the one or more assigned network elements and operation contexts are validated by the validation unit 218.
[0080] In an embodiment, the managing unit 220 is configured to transmit the request towards the manger unit to process the request. Upon processing the request at the network manger unit, the one or more alarms assigned to the one or more network elements and operation contexts. On retrieving, the data of the one or more alarms assigned to the one or more assigned network elements and the operational context is stored in the database 208.
[0081] At step 606, the method 600 includes the step of transmitting notifications pertaining to the one or more alarms assigned to the one or more network elements and operation contexts and the one or more alarms related to the one or more network elements and the operation contexts to the network equipment of the user by the transmittal unit 222.
[0082] In an embodiment, on receiving the request from the user interface 206, the transmittal unit 222 is configured to transmit the plurality of alarms assigned to the one or more network elements and the operation contexts to the user interface 206.
[0083] The present invention further discloses a non-transitory computer-readable medium having stored thereon computer-readable instructions. The computer-readable instructions are executed by the processor 202. The processor 202 is configured to retrieve information pertaining to the user from the database 208 in response to registration of the user via the network equipment 102. The processor 202 is further configured to receive the request from the network equipment 102 to retrieve the one or more alarms assigned to one or more network elements and operation contexts. The processor 202 is further configured to transmit notifications pertaining to the one or more alarms assigned to the one or more network elements and operation contexts to the network equipment of the user.
[0084] A person of ordinary skill in the art will readily ascertain that the illustrated embodiments and steps in description and drawings (FIG.1-6) are set out to explain the exemplary embodiments shown, and it should be anticipated that ongoing technological development will change the manner in which particular functions are performed. These examples are presented herein for purposes of illustration, and not limitation. Further, the boundaries of the functional building blocks have been arbitrarily defined herein for the convenience of the description. Alternative boundaries can be defined so long as the specified functions and relationships thereof are appropriately performed. Alternatives (including equivalents, extensions, variations, deviations, etc., of those described herein) will be apparent to persons skilled in the relevant art(s) based on the teachings contained herein. Such alternatives fall within the scope and spirit of the disclosed embodiments.
[0085] The present disclosure incorporates technical advancement of ease in live monitoring of alarms in the network. The present disclosure provides secure user management and user-based segregation of network monitoring. Further provide various customizable filters for monitoring of required alarm. A central UI/UX is provided for monitoring multiple NMS clusters. Furthermore, the present disclosure provides customizable tables showing alarm to monitor necessary columns on the screen. Further provides reporting options available for the analysis of network alarms. Furthermore, various alarm management options are provided that include create, correlate, associate, create TT, Terminate etc. Furthermore, provides alarm via various modes not limited to short-message, or e-mail, based on user selection and alarm severity.
[0086] The present invention offers multiple advantages over the prior art and the above listed are a few examples to emphasize on some of the advantageous features. The listed advantages are to be read in a non-limiting manner.
REFERENCE NUMERALS

[0087] Environment- 100
[0088] Network Equipment - 102
[0089] Server- 104
[0090] Network- 106
[0091] System -108
[0092] Processor- 202
[0093] Memory- 204
[0094] User Interface- 206
[0095] Database- 208
[0096] Retrieving Unit- 210
[0097] Establishing Unit- 212
[0098] Assigning Unit- 214
[0099] Receiving Unit- 216
[00100] Validation Unit- 218
[00101] Managing Unit- 220
[00102] Transmittal Unit- 222
[00103] Primary processor- 302
[00104] Memory- 304
[00105] User and session management- 402
[00106] NMS UI- 404
[00107] Load balancer- 406
[00108] NMS cluster- 408
,CLAIMS:CLAIMS:

We Claim:
1. A method (600) of monitoring one or more alarms in a network (106), the method (600) comprising the steps of:
retrieving, by one or more processors (202), information pertaining to a user from a database (208) in response to registration of the user via a network equipment (102) with the one or more processors (202);
receiving, by the one or more processor (202), a request from the user to retrieve the one or more alarms assigned to one or more network elements and operation contexts; and
transmitting, by the one or more processors (202), notifications pertaining to the one or more alarms assigned to the one or more network elements and operation contexts and the one or more alarms related to the one or more network elements and the operation contexts to the network equipment (102) of the user.

2. The method (600) as claimed in claim 1, wherein on receiving the request from a user interface (206), the method comprises the step of transmitting, by the one or more processors (202), a plurality of alarms assigned to the one or more network elements and the operation contexts.

3. The method (600) as claimed in claim 1, wherein the information includes an identifier pertaining to the user, a communication protocol address, and identifier pertaining to one or more network elements and operation contexts.

4. The method (600) as claimed in claim 1, wherein the user is one of a network operator and a customer.

5. The method (600) as claimed in claim 1, wherein a service provider assigns the one or more alarms corresponding to the one or more network elements and operation contexts to be monitored by the user.

6. The method (600) as claimed in claim 1, wherein the one or more processors (202) is configured to assign each of the one or more alarms to the user.

7. The method (600) as claimed in claim 1, wherein the method (600) comprises the step of establishing, by the one or more processors (202), a web socket connection with a load balancer (406) in response to registration of the user via the network equipment with the one or more processers.

8. The method (600) as claimed in claim 1, wherein on receipt of the request, the method (600) comprises the steps of:
transmitting, by the one or more processors (202), the request towards a network manager unit to process the request;
retrieving, by the one or more processors (202), the one or more alarms assigned to the one or more network elements and operation contexts upon processing the request at the network manager; and
storing, by the one or more processors (202), on retrieving data of the one or more alarms assigned to the one or more assigned network elements and the operational context in the database.

9. The method (600) as claimed in claim 1, wherein the method (600) comprises the step of, validating, by the one or more processors (202), the one or more assigned network elements and operation contexts on receipt of the request.

10. A system (108) for monitoring one or more alarms in a network, the system (108) comprising:
a retrieving unit (210) configured to retrieve, information pertaining to a user from a database (208) in response to registration of the user via a network equipment (102);
a receiving unit (216) configured to receive, a request from the network equipment (102) to retrieve one or more alarms assigned to one or more network elements and operation contexts; and
a transmittal unit (222) configured to transmit, notifications pertaining to the one or more alarms assigned to the one or more network elements and operation contexts and the one or more alarms related to the one or more network elements and the operation contexts to the network equipment of the user.

11. The system (108) as claimed in claim 10, wherein the transmittal unit (222) is configured to transmit a plurality of alarms assigned to the one or more network elements and the operation contexts to a user interface (206), on receiving the request from the user interface (206).

12. The system (108) as claimed in claim 10, wherein the information includes an identifier pertaining to the user, a communication protocol address, and identifier pertaining to one or more network elements and operation contexts.

13. The system (108) as claimed in claim 10, wherein the user is one of a network operator and a customer.

14. The system (108) as claimed in claim 10, wherein a service provider assigns the one or more alarms corresponding to the one or more network elements and operation contexts to be monitored by the user.

15. The system (108) as claimed in claim 10, comprising an assigning unit (214) configured to assign each of the one or more alarms to the user.

16. The system (108) as claimed in claim 10, comprising an establishment unit (212) configured to establish, a web socket connection with a load balancer (406) in response to registration of the user via the network equipment with a network manager unit.

17. The system (108) as claimed in claim 10, wherein the system (108) comprises a managing unit (220) configured to:
transmit, the request towards the network manager unit to process the request;
retrieve, the one or more alarms assigned to the one or more network elements and operation contexts upon processing the request at the network manager unit; and
store, on retrieving, data of the one or more alarms assigned to the one or more assigned network elements and the operational context in a database (208).

18. The system (108) as claimed in claim 10, comprising a validation unit (218) configured to validate, the one or more assigned network elements and operation contexts on receipt of the request.

19. A network equipment (102), comprising:
one or more primary processors (302) communicatively coupled to one or more processors (202), the one or more primary processors (302) coupled with a memory (304), wherein said memory (304) stores instructions which when executed by the one or more primary processors (302) causes the network equipment (102) to:
register a user with the one or more processors (202);
wherein upon registration the one or more processors (202) is configured to perform the steps as claimed in claim 1.