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 PERIODIC ALARM-BASED NETWORK AVAILABILITY REPORT GENERATION
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 systems, more particularly relates to a method and system for periodic alarm-based network availability report generation.
BACKGROUND OF THE INVENTION
[0002] In the Network Management System (NMS), there are several possible alarms for indicating whether the node is up or down. The period in which the node is down is called the node outage, whereas the period in which the node is up is called node availability. During the outage time, the node remains disconnected in the network. It is necessary to monitor the network availability to understand and analyze the system. Generally, as part of monitoring, the alarms which indicate the node outage are fetched from daily dumps and the outages are calculated manually for each day. However, manually performed calculations are high on human resource consumption and prone to human errors.
[0003] Whenever a node is down, an alarm is generated. If a node is creating a high number of alarms, then taking a dump of all those alarms in a day can be challenging. Conventionally, durations or intervals are calculated manually. Further, reports for the alarms are also created manually.
[0004] It is, therefore, desirable to provide an automation solution for a user who is accessing the UI and monitoring a list of nodes, for monitoring alarms and creating the report for the alarms.
SUMMARY OF THE INVENTION
[0005] One or more embodiments of the present disclosure provide a method and a system for periodic alarm-based network availability report generation.
[0006] In one aspect of the present invention, the system for periodic alarm-based network availability report generation is disclosed. The system includes a fetching unit configured to fetch from a database, a plurality of active Network Availability (NWA) profiles corresponding to a plurality of alarms raised by a plurality of network nodes. The system further includes a determination unit configured to determine a node outage time interval pertaining to each node of the plurality of network nodes based on the fetched plurality of active NWA profiles. The system further a generation unit configured to generate a periodic alarm-based network availability report pertaining to each node of the plurality network nodes based on one or more parameters.
[0007] In an embodiment, the determination unit determines a node outage time interval pertaining to each node of the plurality of network nodes, by fetching from the database, the plurality of alarms raised by the plurality of network nodes. Further, the determination unit determines a node outage time interval pertaining to each node of the plurality of network nodes, by applying, one or more time-based filters to the plurality of alarms raised by the plurality of network nodes and determines, the node outage time interval pertaining to each of the plurality of network nodes by computing a time difference between an alarm raising time and an alarm clearing time of each of the plurality of network nodes.
[0008] In an embodiment, the determination unit, determines the node outage time interval pertaining to each node of the plurality of network nodes for at least one of, each hour of the day, total outage for the day, total availability of the plurality of network nodes for the day and a percentage availability of the plurality of network nodes for the day.
[0009] In an embodiment, the system is further configured to store the calculated node outage time intervals for each of the plurality of network nodes in the database.
[0010] In an embodiment, the system further comprises a merging unit, configured to, merge, the node outage time interval of a specific node of the plurality of network nodes with the node outage time interval of one or more network nodes of the plurality of network nodes, when the node outage time interval pertaining to the specific node overlaps with the node outage time interval of the one or more nodes of the plurality of network nodes.
[0011] In an embodiment, the merging unit, is further configured to store a list of the merged node outage time intervals pertaining to each node of the plurality network nodes in the database against a unique identifier of each node of the plurality network nodes.
[0012] In an embodiment, the unique identifier includes at least one of, a Service Access Point (SAP) ID.
[0013] In an embodiment, a fetching job is created by the fetching unit to fetch the NWA profiles corresponding to the plurality of alarms raised by plurality of network nodes from the database.
[0014] In an embodiment, the periodic alarm-based network availability report pertaining to each node of the plurality network nodes are displayed on the UI or shared with the user via at least one of, emails.
[0015] In an embodiment, the periodic alarm-based network availability report includes data of at least one of, determined node outage time intervals and a list of merged node outage time intervals.
[0016] In an embodiment, the periodic alarm-based network availability report generated pertaining to each node of the plurality network nodes is transmitted to a user by a transceiver of the system.
[0017] In an embodiment, the one or more parameters for generating, the periodic alarm-based network availability report pertaining to each node of the plurality network nodes includes at least one of, the determined node outage time intervals and a list of merged node outage time intervals.
[0018] In another aspect of the present invention, the method for periodic alarm-based network availability report generation is disclosed. The method includes the step of fetching, by one or more processors, from a database, a plurality of active Network Availability (NWA) profiles corresponding to a plurality of alarms raised by a plurality of network nodes. The method further includes the step of determining a node outage time interval pertaining to each node of the plurality of network nodes based on the fetched plurality of active NWA profiles. The method further includes the step of generating a periodic alarm-based network availability report pertaining to each node of the plurality network nodes based on one or more parameters.
[0019] 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 fetch, from a database, a plurality of active Network Availability (NWA) profiles corresponding to a plurality of alarms raised by a plurality of network nodes. The processor is further configured to determine a node outage time interval pertaining to each node of the plurality of network nodes based on the fetched plurality of active NWA profiles. The processor is further configured to generate a periodic alarm-based network availability report pertaining to each node of the plurality network nodes based on one or more parameters.
[0020] In another aspect of invention, User Equipment (UE) is disclosed. The UE 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 is configured to receive the periodic alarm-based network availability report pertaining to each node of the plurality network nodes from the one or more processors.
[0021] 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
[0022] 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.
[0023] FIG. 1 is an exemplary block diagram of an environment for periodic alarm-based network availability report generation, according to one or more embodiments of the present invention;
[0024] FIG. 2 an exemplary block diagram of a system for periodic alarm-based network availability report generation, according to one or more embodiments of the present invention;
[0025] 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;
[0026] FIG. 4 is an exemplary architecture implemented in the system of the FIG. 2, according to one or more embodiments of the present invention;
[0027] FIG. 5 is a signal flow diagram for periodic alarm-based network availability report generation, according to one or more embodiments of the present invention;
[0028] FIG. 6 is a schematic representation of a method for periodic alarm-based network availability report generation, according to one or more embodiments of the present invention; and
[0029] FIG.7 is an exemplary schematic representation of the method for periodic alarm-based network availability report generation.
[0030] The foregoing shall be more apparent from the following detailed description of the invention.
DETAILED DESCRIPTION OF THE INVENTION
[0031] Some embodiments of the present disclosure, illustrating all its features, will now be discussed in detail. It must also be noted that as used herein and in the appended claims, the singular forms "a", "an" and "the" include plural references unless the context clearly dictates otherwise.
[0032] Various modifications to the embodiment will be readily apparent to those skilled in the art and the generic principles herein may be applied to other embodiments. However, one of ordinary skill in the art will readily recognize that the present disclosure including the definitions listed here below are not intended to be limited to the embodiments illustrated but is to be accorded the widest scope consistent with the principles and features described herein.
[0033] A person of ordinary skill in the art will readily ascertain that the illustrated steps detailed in the figures and here below are set out to explain the exemplary embodiments shown, and it should be anticipated that ongoing technological development will change the manner in which particular functions are performed. These examples are presented herein for purposes of illustration, and not limitation. Further, the boundaries of the functional building blocks have been arbitrarily defined herein for the convenience of the description. Alternative boundaries can be defined so long as the specified functions and relationships thereof are appropriately performed. Alternatives (including equivalents, extensions, variations, deviations, etc., of those described herein) will be apparent to persons skilled in the relevant art(s) based on the teachings contained herein. Such alternatives fall within the scope and spirit of the disclosed embodiments.
[0034] The present disclosure relates to a method and a system for periodic alarm-based network availability report generation. A report may be generated for the network availability of the nodes. The network availability may indicate that a node is communicable in the cluster. The report may include which nodes are available and which all nodes went down.
[0035] FIG. 1 illustrates an exemplary block diagram of an environment 100 for periodic alarm-based network availability report generation, according to one or more embodiments of the present disclosure. In this regard, the environment 100 includes a User Equipment (UE) 102, a server 104, a network 106 and a system 108 communicably coupled to each other for periodic alarm-based network 106 availability report generation.
[0036] As per the illustrated embodiment and for the purpose of description and illustration, the UE 102 includes, but not limited to, a first UE 102a, a second UE 102b, and a third UE 102c, and should nowhere be construed as limiting the scope of the present disclosure. In alternate embodiments, the UE 102 may include a plurality of UEs as per the requirement. For ease of reference, each of the first UE 102a, the second UE 102b, and the third UE 102c, will hereinafter be collectively and individually referred to as the “User Equipment (UE) 102”.
[0037] In an embodiment, the UE 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.
[0038] 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.
[0039] 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.
[0040] 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.
[0041] The environment 100 further includes the system 108 communicably coupled to the server 104 and the UE 102 via the network 106. The system 108 is configured to generate the report based on the availability of the periodic alarm-based network. As per one or more embodiments, the system 108 is adapted to be embedded within the server 104 or embedded as an individual entity.
[0042] Operational and construction features of the system 108 will be explained in detail with respect to the following figures.
[0043] FIG. 2 is an exemplary block diagram of the system 108 for periodic alarm-based network 106 availability report generation, according to one or more embodiments of the present invention.
[0044] 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.
[0045] 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.
[0046] 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 UE 102 and the database 208.
[0047] 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.
[0048] In order for the system 108 for periodic alarm-based network 106 availability report generation, the processor 202 includes one or more modules. In one embodiment, the one or more modules includes, but not limited to, a fetching unit 210, a determination unit 212, a merging unit 214, a generation unit 216, a transceiver 218 communicably coupled to each other for periodic alarm-based network 106 availability report generation.
[0049] In one embodiment, the one or more modules includes, but not limited to, the fetching unit 210, the determination unit 212, the merging unit 214, the generation unit 216, the transceiver 218 can be used in combination or interchangeably for periodic alarm-based network 106 availability report generation.
[0050] The fetching unit 210, the determination unit 212, the merging unit 214 the generation unit 216, the transceiver 218 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.
[0051] In one embodiment, in a Network Management System (NMS), there are several possible alarms for indicating whether the node is up or down. The period in which the node is down, is called the node outage whereas the period in which the node is up, is called the node availability. The NMS refers to a collection of applications that enable network 106 components to be monitored and controlled. In NMS cluster, each node may go down and come up once or more or never on each day. The NMS can understand the node status based on the alarms which indicate the node down or up. The necessity to monitor the aggregation of node’s availability or unavailability is calculable based their respective indicative alarms. To achieve the requirement, profiles can be created for multiple node types. Each node type’s sub profile configuration contains the unique ids of the node instances, circles and the alarm names. A list of email ids of addressee or copy recipients can also be added for each profile in addition to the global addressee list to receive the final reports on a daily basis. The profiles can be kept deactivated also if their monitoring is temporarily undesired.
[0052] In an embodiment, the fetching unit 210 is configured to fetch a plurality of active Network availability (NWA) profiles corresponding to a plurality of alarms raised by a plurality of network nodes from the database 208. In an embodiment, a fetching job is created by the fetching unit to fetch the NWA profiles corresponding to the plurality of alarms raised by plurality of network nodes from the database 208.
[0053] The NWA refers to the operational status of the network 106 and its ability to quickly make connections, process traffic, and respond to user requests. The active NWA profiles refer to dynamic sets of parameters, rules, and configurations that are actively used to manage and monitor the real-time availability and performance of the network 106.The active NWA profiles include, but not limited to, real-time performance metrics, alert thresholds, redundancy and failover configurations, dynamic resource allocation, fault detection and recovery procedures, security measures, maintenance protocols, Service Level Agreements (SLAs) compliance, historical data analysis, user and application prioritization. The active NWA profiles enable network administrators to maintain a high level of network availability and performance by providing a framework for real-time monitoring, dynamic management, and raid response to any issues.
[0054] The plurality of alarms refers to multiple distinct alerts or notifications that are generated by different network nodes indicating various issues or irregularities in network performance or availability. The network nodes are fundamental components of network infrastructure, enabling data communication and connectivity across the network 106. The network nodes include, but not limited to computers and servers, routers, switches, hubs, access points, printers, IoT devices. Further, the NWA profiles corresponding to the plurality of alarms raised by plurality of network nodes are configurable in real time via a User Interface (UI).
[0055] Upon fetching the plurality of active NWA profiles corresponding to the plurality of alarms raised by the plurality of network nodes, the determination unit 212 is configured to determine a node outage time interval pertaining to each node of the plurality of network nodes. The node outage time interval refers to the specific period during which the network node is not operational or unable to provide its intended services. The determination unit 212 determines the node outage time interval pertaining to each node of the plurality of network nodes for at least one of, each hour of the day, total outage for the day, total availability of the plurality of network nodes for the day and a percentage availability of the plurality of network nodes for the day.
[0056] Further, the determination unit 212 determines the node outage time interval pertaining to each of the plurality of network nodes by fetching the plurality of alarms raised by the plurality of network nodes from the database 208. Upon fetching the plurality of alarms raised by the plurality of network nodes, one or more time-based filters are applied to the plurality of alarms raised by the plurality of network nodes. The one or more time-based filter includes, but not limited to, time-based filter for fetching only those alarms which can determine the outage for Nth day, time-based filter excluding the active alarms which are raised after Nth day, time-based filter excluding the cleared alarms which are cleared before Nth day.
[0057] Thereafter, the node outage time interval pertaining to each of the plurality of network nodes are determined by computing a time difference between an alarm raising time and an alarm clearing time of each of the plurality of network nodes.
[0058] The computing the time difference between the alarm raising time and the alarm clearing time of each of the plurality of network nodes is as follows. In an instance of active alarms, if suppose the alarm is raised before the Nth date, then it will calculate the outage for 24 hours (N:00:00:00 to N:23:59:59). If the alarm is raised after the Nth date, then it will not be eligible for outage calculation. If the alarm is raised on the same Nth date then it will take the outage from the raise time to the end of the day (N:xx:xx:xx to N:23:59:59). In case of archived alarms, if the alarm is cleared before the Nth date, then it will not be eligible for outage calculation. If the alarm clearance and raise has happened after the Nth date, then it will not come into consideration for outage calculation. If the alarm clearance and raise is happened before the Nth date then it will take the outage from the raise time to the end of the day (N:xx:xx:xx to N:23:59:59). If the alarm clearance comes after the Nth date and but the alarm is raised on the same date i.e., Nth date then it will take the outage from the raise time to end of the day. If the alarm clearance date and raise date is same on the Nth date i.e., Nth date then it will take the outage from the raise time to the end of the day (N:xx:xx:xx to N:yy:yy:yy).
[0059] The archived alarms are fetched and checked whether they were cleared on Nth date. If yes, the alarm is checked whether the alarm is raised on the Nth date. If it is raised on Nth date, then both true conditions will point to interval between raise time and clear time.
[0060] In another instance, if the alarm is not cleared on the Nth date (e.g. it might be cleared on the next day) and got raised before the Nth date, then the interval will be from the first second of the day to the clearance time. In a scenario, when the alarm is not cleared on the Nth date (i.e. cleared on the next day), the alarm will be treated as active alarm. In such cases, the interval will be between raise time and last second of the day. In another case, if it alarm is not raised on the Nth day (i.e. raised on N-1 day) and cleared on N+1 day, then the interval is between first second of the day and last second of the day. In other words, the interval will be total 24 hours of outage.
[0061] Upon computing the time difference between the alarm raising time and the alarm clearing time of each of the plurality of network nodes, the calculated node outage time intervals for each of the plurality of network nodes are stored in the database 208.
[0062] Thereafter, when the node outage time interval pertaining to the specific node overlaps with the node outage time interval of the one or more nodes of the plurality of network nodes, the node outage time interval of a specific node of the plurality of network nodes is merged with the node outage time interval of one or more network nodes of the plurality of network nodes by the merging unit 214.
[0063] Upon merging the node outage time interval of a specific node of the plurality of network nodes with the node outage time interval of one or more network nodes of the plurality of network nodes, a list of the merged node outage time intervals pertaining to each node of the plurality network nodes are stored in the database 208. The merged node outage time intervals pertaining to each node of the plurality network nodes are stored in the database 208 against a unique identifier of each node of the plurality network nodes. The unique identifier includes at least one of, a Service Access Point (SAP) ID.
[0064] Upon storing the merged node outage time intervals at the database, the generation unit 216 is configured to generate a periodic alarm-based network availability report pertaining to each node of the plurality network nodes based in one or more parameters. The one or more parameters for generating the periodic alarm-based network availability report pertaining to each node of the plurality network nodes includes at least one of, the determined node outage time intervals and the list of merged node outage time intervals.
[0065] The periodic alarm-based network availability report includes data of at least one of, determined node outage time intervals and the list of merged node outage time intervals. Further, the periodic alarm-based network availability report generated pertaining to each node of the plurality network nodes is transmitted to a user by the transceiver 218 of the system 108. Furthermore, the periodic alarm-based network availability report pertaining to each node of the plurality network nodes are displayed on the UI or shared with the user via at least one of, emails. Therefore, the system 108 provides customized automation in calculation and storage in database 208 and prevents from possibility of errors due to manual calculation.
[0066] 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 UE 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.
[0067] As mentioned earlier in FIG. 1, each of the first UE 102a the second UE 102b, and the third UE 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 UE 102a without deviating from the scope of the present disclosure and the limiting the scope of the present disclosure. The first UE 102a includes one or more primary processors 302 communicably coupled to the one or more processors 202 of the system 108.
[0068] 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 UE 102a to receive the periodic alarm-based network availability report pertaining to each node of the plurality network nodes from the one or more processors 202.
[0069] As mentioned earlier in FIG. 2, the one or more processors 202 of the system 108 is configured for periodic alarm-based network availability report generation. 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.
[0070] Further, the processor 202 includes the fetching unit 210, the determination unit 212, the merging unit 214, the generation unit 216. The operations and functions of the fetching unit 210, the determination unit 212, the merging unit 214, the generation unit 216, and the transceiver 218 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.
[0071] FIG. 4 is an exemplary architecture 400 implemented in the system 108 for periodic alarm-based network 106 availability report generation, according to one or more embodiments of the present invention.
[0072] The architecture 400 includes an NWA profile management from UI 408 stores the NWA profiles in the database 208. The plurality of active NWA profiles corresponding to the plurality of alarms are fetched from the database 208.
[0073] Upon fetching the active NWA profiles corresponding to the plurality of alarms 402, the active NWA profiles are transmitted to a scheduler-based NWA processor 404 and an algorithm-based NWA calculator 406. The scheduler-based NWA processor and the algorithm-based NWA calculator 406 perform the calculations and store the calculations in the database 208.
[0074] Upon performing the calculations and storing the calculations in the database 208, the NWA reports are generated and stored in the database 208. The generated reports of each NWA profiles are shared to profile specific addressee, for example, over email.
[0075] Further, the generated reports stored in the database 208 may be accessed from the UI. Furthermore, the accessed generated reports are either visualized on UI or downloaded from the UI. The reports can be downloaded for the selected date, with the various combinations of filters for profiles, node types, circles and instance unique SAP IDs.
[0076] FIG. 5 is a signal flow diagram for failure management in the network 106 according to one or more embodiments of the present invention.
[0077] At step 502, the plurality of active NWA profiles corresponding to the plurality of alarms raised by the plurality of network nodes are fetched by the fetching unit 210 from the database 208. The fetching job is created by the fetching unit 210 to fetch the NWA profiles corresponding to the plurality of alarms raised by plurality of network nodes from the database 208. The NWA profiles corresponding to the plurality of alarms raised by plurality of network nodes are configurable in real time via the UI.
[0078] At step 504, upon fetching the plurality of active NWA profiles from the database 208, the node outage time interval pertaining to each node of the plurality of network nodes based on the fetched plurality of active NWA profiles are determined by the determination unit 212. The determination unit 212 determines the node outage time interval pertaining to each node of the plurality of network nodes for at least one of, each hour of the day, total outage for the day, total availability of the plurality of network nodes for the day and a percentage availability of the plurality of network nodes for the day.
[0079] Further, the determination unit 212 determines the node outage time interval pertaining to each of the plurality of network nodes by fetching the plurality of alarms raised by the plurality of network nodes from the database 208.
[0080] Upon fetching the plurality of alarms raised by the plurality of network nodes, one or more time-based filters are applied to the plurality of alarms raised by the plurality of network nodes.
[0081] Thereafter, the node outage time interval pertaining to each of the plurality of network nodes are determined by computing the time difference between an alarm raising time and an alarm clearing time of each of the plurality of network nodes.
[0082] Upon computing the time difference between the alarm raising time and the alarm clearing time of each of the plurality of network nodes, the calculated node outage time intervals for each of the plurality of network nodes are stored in the database 208.
[0083] At step 506, subsequently, when the node outage time interval pertaining to the specific node overlaps with the node outage time interval of the one or more nodes of the plurality of network nodes, the node outage time interval of a specific node of the plurality of network nodes is merged with the node outage time interval of one or more network nodes of the plurality of network nodes by the merging unit 214.
[0084] The merged node outage time intervals pertaining to each node of the plurality network nodes are stored in the database 208 against a unique identifier of each node of the plurality network nodes. The unique identifier includes at least one of, a Service Access Point (SAP) ID.
[0085] At step 508, upon storing the merged node outage time intervals at the database, the generation unit 216 is configured to generate a periodic alarm-based network availability report pertaining to each node of the plurality network nodes based in one or more parameters. The one or more parameters for generating the periodic alarm-based network availability report pertaining to each node of the plurality network nodes includes at least one of, the determined node outage time intervals and the list of merged node outage time intervals. The periodic alarm-based network availability report includes data of at least one of, determined node outage time intervals and the list of merged node outage time intervals. The periodic alarm-based network availability reports are stored at the database 208.
[0086] At step 510, further, the periodic alarm-based network availability report generated pertaining to each node of the plurality network nodes is transmitted to the user by the transceiver 218 of the system 108. Furthermore, the periodic alarm-based network availability report pertaining to each node of the plurality network nodes are displayed on the UI or shared with the user via at least one of, emails.
[0087] FIG. 6 is a flow diagram of a method 600 for periodic alarm-based network 106 availability report generation, 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.
[0088] At step 602, the method 600 includes the step of fetching the plurality of active NWA profiles corresponding to the plurality of alarms raised by the plurality of network nodes from the database by the fetching unit 210. The fetching job is created to fetch the NWA profiles corresponding to the plurality of alarms raised by plurality of network nodes from the database 208. The NWA profiles corresponding to the plurality of alarms raised by plurality of network nodes are configurable in real time via the UI.
[0089] At step 604, the method 600 includes the step of determining the node outage time interval pertaining to each node of the plurality of network nodes based on the fetched plurality of active NWA profiles by the determination unit 212. The determination unit 212 determines the node outage time interval pertaining to each node of the plurality of network nodes for at least one of, each hour of the day, total outage for the day, total availability of the plurality of network nodes for the day and a percentage availability of the plurality of network nodes for the day.
[0090] Further, the determination unit 212 determines the node outage time interval pertaining to each of the plurality of network nodes by fetching the plurality of alarms raised by the plurality of network nodes from the database 208. Upon fetching the plurality of alarms raised by the plurality of network nodes, one or more time-based filters are applied to the plurality of alarms raised by the plurality of network nodes. Thereafter, the node outage time interval pertaining to each of the plurality of network nodes are determined by computing the time difference between an alarm raising time and an alarm clearing time of each of the plurality of network nodes. Upon computing the time difference between the alarm raising time and the alarm clearing time of each of the plurality of network nodes, the calculated node outage time intervals for each of the plurality of network nodes are stored in the database 208.
[0091] Subsequently, when the node outage time interval pertaining to the specific node overlaps with the node outage time interval of the one or more nodes of the plurality of network nodes, the node outage time interval of a specific node of the plurality of network nodes is merged with the node outage time interval of one or more network nodes of the plurality of network nodes by the merging unit 214. The merged node outage time intervals pertaining to each node of the plurality network nodes are stored in the database 208 against a unique identifier of each node of the plurality network nodes. The unique identifier includes at least one of, a Service Access Point (SAP) ID.
[0092] At step 606, the method 600 includes the step of generating the periodic alarm-based network availability report pertaining to each node of the plurality network nodes based on one or more parameters by the generation unit 216. The one or more parameters for generating the periodic alarm-based network availability report pertaining to each node of the plurality network nodes includes at least one of, the determined node outage time intervals and the list of merged node outage time intervals. The periodic alarm-based network availability report includes data of at least one of, determined node outage time intervals and the list of merged node outage time intervals. The periodic alarm-based network availability reports are stored at the database 208. Further, the periodic alarm-based network availability report generated pertaining to each node of the plurality network nodes is transmitted to the user by the transceiver 218 of the system 108. Furthermore, the periodic alarm-based network availability report pertaining to each node of the plurality network nodes are displayed on the UI or shared with the user via at least one of, emails.
[0093] FIG. 7 is an exemplary flow diagram of the method 700 for periodic alarm-based network 106 availability report generation, according to one or more embodiments of the present invention.
[0094] According to exemplary flow diagram illustrated in the FIG. 7, at step 702, a cronjob is scheduled. The cronjob refers to providing expressions to a scheduler for point of starting and frequency of running a job. For instance, if generation of reports is required once in a day, the job is scheduled that runs once in a day to fetch the reports of the previous day. At step 704, once the job has been created, the job will fetch all active network availability (NWA) profiles.
[0095] At step 706, upon fetching the active NWA profiles, the query is formed based on profile data and excluding the alarms raised after Nth data and cleared before Nth date. At step 708 and 710 all the NWA profiles satisfying the query are fetched and the fetched alarms are iterated.
[0096] At step 712, let’s consider a scenario of active alarms, if suppose the alarm is raised before the Nth date, then it will calculate the outage for 24 hours (N:00:00:00 to N:23:59:59). If the alarm is raised after the Nth date, then it will not be eligible for outage calculation. If the alarm is raised on the same Nth date then it will take the outage from the raise time to completion the day ((N:00:00:00 to N:23:59:59)).
[0097] In the case of history alarms, if the alarm is cleared before the Nth date, then it will not be eligible for outage calculation. If the alarm clearance and raise has happened after the Nth date then it will not come into consideration for outage calculation.
[0098] If the alarm clearance and raise is happened before the Nth date then it will take the outage from the raise time to completion of the day ((N:00:00:00 to N:23:59:59)). If the alarm clearance comes after the Nth date and but the alarm is raised on the same date i.e., Nth Date then it will take the outage from the raise time to completion if the day. If the alarm clearance date and raise date is same on the Nth date i.e., Nth Date then it will take the outage from the raise Time to completion the day ((N:xx:xx:xx to N:yy:yy:yy)).
[0099] The history alarms are fetched and checked for whether they were cleared on the Nth date. If yes, the alarm is checked whether the alarm is raised on the Nth date. If it is raised on Nth date, then both true conditions will point to interval between raise time and clear time.
[00100] In the other cases, if the alarm is not cleared on in the Nth date (e.g. it might be cleared on the next day) and got raised before the Nth date, then the interval will be from the first second of the day to the clearance time. In a scenario, when the alarm is not cleared on the Nth date (i.e. cleared on the next day), the alarm will be treated as active alarm. In such cases, the interval will be between raise time and last second of the day. In another case, if it alarm is not raised on the Nth day (i.e. raised on N-1 day) and cleared on N+1 day, then the interval is between first second of the day and last second of the day. In other words, the interval will be a total of 24 hours of outage.
[00101] More specifically, if the alarm is an active alarm and if the alarm is raised on Nth day, then the outage interval is N xx:xx:xx to N+1 00:00:00. If the alarm is an active alarm and if the alarm is raised before Nth day, then the the outage interval is N 00:00:00 to N+1 00:00:00. h.
[00102] Further, if the alarm is an archived alarm and,
i. if the alarm is cleared on Nth day and raised on Nth day, then the interval is N xx:xx:xx to N yy:yy:yy,
ii. if the alarm is cleared on Nth day and raised before Nth day, then the interval is N 00:00:00 to N yy:yy:yy,
iii. if the alarm is cleared after Nth day and raised before Nth day, then the interval is N 00:00:00 to N+1 00:00:00, and
iv. if the alarm is cleared after Nth day and raised on Nth day, then the interval is N xx:xx:xx to N+1 00:00:00.
[00103] At step 714, the list of intervals of each instance is segregated and stored in a map against the key to unique id of each instance. At step 716, iterate over the map and merge the intervals if any of them are overlapping. At step 718, for each instance, calculate the outage for each hour based on the merged intervals of an instance and store the hourly outages in a map for each hour. Later, calculate the consolidation like total outage for the day, total availability for the day and percentage availability for the day. At step 720, store the entire data along with calculated figures in the database 208 in the records specific to each instance of Nth day. Upon storing in the database 208, the reports of each profile-to-profile specific addressees and copy receipts along with global receipts over email. The reports stored in the database 208 can be accessed and visualized on UI or downloaded from the UI. The report can be downloaded for the selected data with various combination of filters for profiles, node types, circles and instance unique ids.
[00104] 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 fetch from the database 208, the plurality of active NWA profiles corresponding to a plurality of alarms raised by the plurality of network nodes. The processor 202 is further configured to determine the node outage time interval pertaining to each node of the plurality of network nodes based on the fetched plurality of active NWA profiles. The processor 202 is further configured to generate the periodic alarm-based network availability report pertaining to each node of the plurality network nodes based on one or more parameters.
[00105] 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.
[00106] The present disclosure incorporates technical advancement of providing customized automation in calculation and storage in database and solving issues of human resource consumption. Further, the present disclosure minimizes the possibility of errors due to manual calculation and ensures system’s efficient utilization. Further, the reports that are calculated are downloaded and stored, therefore the reports are accessible as and when needed.
[00107] 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
[00108] Environment- 100
[00109] User Equipment (UE)- 102
[00110] Server- 104
[00111] Network- 106
[00112] System -108
[00113] Processor- 202
[00114] Memory- 204
[00115] User Interface- 206
[00116] Database- 208
[00117] Fetching Unit- 210
[00118] Determination Unit- 212
[00119] Merging Unit- 214
[00120] Generation Unit- 216
[00121] Transceiver- 218
[00122] Primary processor- 302
[00123] Memory- 304
[00124] Alarms- 402
[00125] Scheduler based NWA processor- 404
[00126] Algorithm based NWA calculator- 406
[00127] NWA profile management from UI- 408
,CLAIMS:CLAIMS:
We Claim:
1. A method (600) for periodic alarm-based network availability report generation, the method (600) comprises the steps of:
fetching, by one or more processors (202), from a database (208), a plurality of active Network Availability (NWA) profiles corresponding to a plurality of alarms raised by a plurality of network nodes;
determining, by the one or more processors (202), a node outage time interval pertaining to each node of the plurality of network nodes based on the fetched plurality of active NWA profiles; and
generating, by the one or more processors (202), a periodic alarm-based network availability report pertaining to each node of the plurality network nodes based on one or more parameters.

2. The method (600) as claimed in claim 1, wherein the step of determining, a node outage time interval pertaining to each node of the plurality of network nodes, includes the steps of:
fetching, by the one or more processors (202), from the database (208), the plurality of alarms raised by the plurality of network nodes;
applying, by the one or more processors (202), one or more time-based filters to the plurality of alarms raised by the plurality of network nodes; and
determining, by the one or more processors (202), the node outage time interval pertaining to each of the plurality of network nodes by computing a time difference between an alarm raising time and an alarm clearing time of each of the plurality of network nodes.

3. The method (600) as claimed in claim 1, wherein the one or more processors (202), determines the node outage time interval pertaining to each node of the plurality of network nodes for at least one of, each hour of the day, total outage for the day, total availability of the plurality of network nodes for the day and a percentage availability of the plurality of network nodes for the day.

4. The method (600) as claimed in claim 3, wherein the one or more processors (202), is further configured to, store, the calculated node outage time intervals for each of the plurality of network nodes in the database (208).

5. The method (600) as claimed in claim 1, wherein the method (600) further comprises the step of:
merging, by the one or more processors (202), the node outage time interval of a specific node of the plurality of network nodes with the node outage time interval of one or more network nodes of the plurality of network nodes, when the node outage time interval pertaining to the specific node overlaps with the node outage time interval of the one or more nodes of the plurality of network nodes.

6. The method (600) as claimed in claim 5, wherein the step of, merging, the node outage time interval of a specific node of the plurality of network nodes with one or more network nodes of the plurality of network nodes, when the node outage time interval pertaining to the specific node overlaps with the node outage time interval of the one or more nodes of the plurality of network nodes further includes the step of:
storing, by the one or more processors (202), a list of the merged node outage time intervals pertaining to each node of the plurality network nodes in the database against a unique identifier of each node of the plurality network nodes.

7. The method (600) as claimed in claim 6, wherein the unique identifier includes at least one of, a Service Access Point (SAP) ID.

8. The method (600) as claimed in claim 1, wherein the NWA profiles corresponding to the plurality of alarms raised by plurality of network nodes are configurable in real time via a User Interface (UI).

9. The method (600) as claimed in claim 1, wherein a fetching job is created by the one or more processors (202) to fetch the NWA profiles corresponding to the plurality of alarms raised by plurality of network nodes from the database (208).

10. The method (600) as claimed in claim 1, wherein the periodic alarm-based network availability report pertaining to each node of the plurality network nodes are displayed on the UI or shared with the user via at least one of, emails.

11. The method (600) as claimed in claim 1, wherein the periodic alarm-based network availability report includes data of at least one of, determined node outage time intervals and a list of merged node outage time intervals.

12. The method (600) as claimed in claim 1, wherein the periodic alarm-based network availability report generated pertaining to each node of the plurality network nodes is transmitted to a user by the one or more processors (202).

13. The method (600) as claimed in claim 1, wherein the one or more parameters for generating, the periodic alarm-based network availability report pertaining to each node of the plurality network nodes includes at least one of, the determined node outage time intervals and a list of merged node outage time intervals.

14. A system (108) for periodic alarm-based network availability report generation, the system (108) comprising:
a fetching unit (210), configured to, fetch, from a database (208), a plurality of active Network Availability (NWA) profiles corresponding to a plurality of alarms raised by a plurality of network nodes;
a determination unit (212), configured to, determine, a node outage time interval pertaining to each node of the plurality of network nodes based on the fetched plurality of active NWA profiles; and
a generation unit (216), configured to, generate, a periodic alarm-based network availability report pertaining to each node of the plurality network nodes based on one or more parameters.

15. The system (108) as claimed in claim 14, wherein the determination unit (212), determines, a node outage time interval pertaining to each node of the plurality of network nodes, by:
fetching, from the database (208), the plurality of alarms raised by the plurality of network nodes;
applying, one or more time-based filters to the plurality of alarms raised by the plurality of network nodes; and
determining, the node outage time interval pertaining to each of the plurality of network nodes by computing a time difference between an alarm raising time and an alarm clearing time of each of the plurality of network nodes.

16. The system (108) as claimed in claim 14, wherein the determination unit (212), determines the node outage time interval pertaining to each node of the plurality of network nodes for at least one of, each hour of the day, total outage for the day, total availability of the plurality of network nodes for the day and a percentage availability of the plurality of network nodes for the day.

17. The system (108) as claimed in claim 16, wherein the system (108), is further configured to, store, the calculated node outage time intervals for each of the plurality of network nodes in the database (208).

18. The system (108) as claimed in claim 14, wherein the system (108) further comprises:
a merging unit (214), configured to, merge, the node outage time interval of a specific node of the plurality of network nodes with the node outage time interval of one or more network nodes of the plurality of network nodes, when the node outage time interval pertaining to the specific node overlaps with the node outage time interval of the one or more nodes of the plurality of network nodes.

19. The system (108) as claimed in claim 18, wherein the merging unit (214), is further configured to:
store, a list of the merged node outage time intervals pertaining to each node of the plurality network nodes in the database against a unique identifier of each node of the plurality network nodes.

20. The system (108) as claimed in claim 19, wherein the unique identifier includes at least one of, a Service Access Point (SAP) ID.

21. The system (108) as claimed in claim 14, wherein the NWA profiles corresponding to the plurality of alarms raised by plurality of network nodes are configurable in real time via a User Interface (UI).

22. The system (108) as claimed in claim 14, wherein a fetching job is created by the fetching unit (210) to fetch the NWA profiles corresponding to the plurality of alarms raised by plurality of network nodes from the database (208).

23. The system (108) as claimed in claim 14, wherein the periodic alarm-based network availability report pertaining to each node of the plurality network nodes are displayed on the UI or shared with the user via at least one of, emails.

24. The system (108) as claimed in claim 14, wherein the periodic alarm-based network availability report includes data of at least one of, determined node outage time intervals and a list of merged node outage time intervals.

25. The system (108) as claimed in claim 14, wherein the periodic alarm-based network availability report generated pertaining to each node of the plurality network nodes is transmitted to a user by a transceiver (218) of the system.

26. The system (108) as claimed in claim 14, wherein the one or more parameters for generating, the periodic alarm-based network availability report pertaining to each node of the plurality network nodes includes at least one of, the determined node outage time intervals and a list of merged node outage time intervals.

27. A User Equipment (UE) (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 UE (102) to:
receive, the periodic alarm-based network (106) availability report pertaining to each node of the plurality network nodes from the one or more processors (202); and
wherein the one or more processors (202) is configured to perform the steps as claimed in claim 1.