FORM 2
THE PATENTS ACT, 1970 (39 OF 1970) & THE PATENT RULES, 2003
COMPLETE SPECIFICATION
(See section 10 and rule 13)
“METHOD AND SYSTEM FOR COMPUTING NETWORK AVAILABILITY AT SCALE”
We, Jio Platforms Limited, an Indian National, of Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India.
The following specification particularly describes the invention and the manner in which it is to be performed.

METHOD AND SYSTEM FOR COMPUTING NETWORK AVAILABILITY AT SCALE
FIELD OF THE DISCLOSURE
[0001] The present disclosure relates to the derivation of network quality of a wireless communication network. More particularly, the present disclosure relates to methods and systems for computing network availability at scale.
BACKGROUND
[0002] The following description of related art is intended to provide background information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section be used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of prior art.
[0003] Wireless communication technology has rapidly evolved over the past few decades, with each generation bringing significant improvements and advancements. The first generation of wireless communication technology was based on analog technology and offered only voice services. However, with the advent of the second-generation (2G) technology, digital communication and data services became possible, and text messaging was introduced. Third generation (3G) technology marked the introduction of high-speed internet access, mobile video calling, and location-based services. The fourth-generation (4G) technology revolutionized wireless communication with faster data speeds, better network coverage, and improved security. Currently, the fifth-generation (5G) technology is being deployed, promising even faster data speeds, low latency, and the ability to connect multiple devices simultaneously. With each generation, wireless

communication technology has become more advanced, sophisticated, and capable of delivering more services to its users.
[0004] Network uptime is a very important metric which shows the quality of service rendered to the customer and it is directly proportional to the revenue. The revenue is impacted if the network is down and hence there is a need to monitor the availability of network at higher geographies.
[0005] Further, over the period of time various solutions have been developed to compute network availability at scale. However, there are certain challenges with the existing solutions. The currently known solutions fail to monitor the network availability at all levels, viz., State, Business Cluster, Maintenance Cluster and to the Site level when the network consists of millions of nodes.
[0006] Thus, there exists an imperative need in the art to compute network availability at scale, which the present disclosure aims to address.
SUMMARY
[0007] This section is provided to introduce certain aspects of the present disclosure in a simplified form that are further described below in the detailed description. This summary is not intended to identify the key features or the scope of the claimed subject matter.
[0008] An aspect of the present disclosure may relate to a method for computing network availability at scale. The method includes identifying, by an identification unit, one or more service affecting alarms raised for at least one cell for a period of time. Next, the method includes computing, by a processing unit, a duration of outage for each cell based on the identification of the one or more service affecting alarms. Next, the method includes removing, by the processing unit, a planned

outage duration from the duration of outage for each cell. Thereafter, the method includes generating, by the processing unit, outage statistics based at least on the computing and removing step, wherein the outage statistics are generated for one or more geographical regions.
[0009] In an exemplary aspect of the present disclosure, the method further comprises receiving, by a receiving unit via an interface, a user input comprising selection of a geographical region and an attribute level.
[0010] In an exemplary aspect of the present disclosure, the method further comprises removing, by the processing unit, an overlapping duration from the duration of outage for each cell.
[0011] In an exemplary aspect of the present disclosure, upon receiving the user input, the method further comprises generating, by the processing unit at an application server, a report configuration based at least on the received user input; and storing, by the processing unit, the report configuration in a database based at least on a RESTful Application Programming Interface (API).
[0012] In an exemplary aspect of the present disclosure, the method further comprises retrieving, by the processing unit via a Fault Management (FM) microservice, the stored report configuration from the database; generating, by the processing unit, at least a network availability report by using at least the stored report configuration from the database and the generated outage statistics; and enabling, by the processing unit via the interface, downloading of at least the network availability report.
[0013] In an exemplary aspect of the present disclosure, the attribute level comprises at least one of a state level, a business level, a cell level, a band level, and a site level.

[0014] Another aspect of the present disclosure may relate to a system for computing network availability at scale. The system comprising: an identification unit, configured to identify one or more service affecting alarms raised for at least one cell for a period of time; a processing unit connected at least to the identification unit, the processing unit, configured to: compute a duration of outage for each cell based on the identification of the one or more service affecting alarms, remove a planned outage duration from the duration of outage for each cell, and generate outage statistics based at least on the computation of outage for each cell and after removing the planned outage duration, wherein the outage statistics are generated for one or more geographical regions.
[0015] Yet another aspect of the present disclosure may relate to a non-transitory computer readable storage medium storing instructions for computing network availability at scale, the instructions include executable code which, when executed by one or more units of a system, causes: an identification unit, configured to identify one or more service affecting alarms raised for at least one cell for a period of time; a processing unit of the system to: compute a duration of outage for each cell based on the identification of the one or more service affecting alarms, remove a planned outage duration from the duration of outage for each cell, and generate outage statistics based at least on the computation of outage for each cell and after removing the planned outage duration, wherein the outage statistics are generated for one or more geographical regions.
OBJECTS OF THE INVENTION
[0016] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.

[0017] It is an object of the present disclosure to provide a system and a method for computing network availability at scale.
[0018] It is another object of the present disclosure to provide a solution that monitors the network availability at all levels, viz., state, business cluster, maintenance cluster and to the site level.
[0019] It is yet another object of the present disclosure to provide a solution that helps in decision making to improve the network uptime.
[0020] It is yet another object of the present disclosure to provide a solution that calculates the outage duration for each cell ensuring to remove overlapping duration to keep the integrity of the data.
BRIEF DESCRIPTION OF DRAWINGS
[0021] 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 electronic components or circuitry commonly used to implement such components.
[0022] FIG. 1 illustrates an exemplary block diagram of a computing device upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure.

[0023] FIG. 2 illustrates an exemplary block diagram of a system for computing network availability at scale, in accordance with exemplary embodiments of the present disclosure.
[0024] FIG. 3 illustrates an exemplary method flow diagram indicating the process for computing network availability at scale, in accordance with exemplary embodiments of the present disclosure.
[0025] FIG. 4 illustrates an exemplary diagram of a user equipment in connection with a sever via a network, for computing network availability at scale, in accordance with exemplary embodiments of the present disclosure.
[0026] FIG. 5 illustrates an exemplary process flow diagram indicating the process for fetching the network availability report, in accordance with exemplary embodiments of the present disclosure.
[0027] FIGs. 6a-6e illustrate tables representing statistics report at the cell level, in accordance with exemplary embodiments of the present disclosure.
[0028] FIG. 7 illustrates tables representing statistic report at state level, in accordance with exemplary embodiments of the present disclosure.
[0029] FIG 8. illustrates tables representing statistic report at maintenance level, in accordance with exemplary embodiments of the present disclosure.
[0030] FIG. 9. illustrates tables representing statistic report at business level, in accordance with exemplary embodiments of the present disclosure.
[0031] The foregoing shall be more apparent from the following more detailed description of the disclosure.

DETAILED DESCRIPTION
[0032] In the following description, for the purposes of explanation, various
5 specific details are set forth in order to provide a thorough understanding of
embodiments of the present disclosure. It will be apparent, however, that
embodiments of the present disclosure may be practiced without these specific
details. Several features described hereafter may each be used independently of one
another or with any combination of other features. An individual feature may not
10 address any of the problems discussed above or might address only some of the
problems discussed above.
[0033] The ensuing description provides exemplary embodiments only, and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather,
15 the ensuing description of the exemplary embodiments will provide those skilled in
the art with an enabling description for implementing an exemplary embodiment. It should be understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope of the disclosure as set forth.
20
[0034] Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it will be understood by one of ordinary skill in the art that the embodiments may be practiced without these specific details. For example, circuits, systems, processes, and other components
25 may be shown as components in block diagram form in order not to obscure the
embodiments in unnecessary detail.
[0035] Also, it is noted that individual embodiments may be described as a process
which is depicted as a flowchart, a flow diagram, a data flow diagram, a structure
30 diagram, or a block diagram. Although a flowchart may describe the operations as
8

a sequential process, many of the operations may be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed but could have additional steps not included in a figure. 5
[0036] The word “exemplary” and/or “demonstrative” is used herein to mean serving as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples. In addition, any aspect or design described herein as “exemplary” and/or “demonstrative” is not
10 necessarily to be construed as preferred or advantageous over other aspects or
designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar words are used in either the detailed description or the claims, such terms are intended to be inclusive—in a manner
15 similar to the term “comprising” as an open transition word—without precluding
any additional or other elements.
[0037] As used herein, a “processing unit” or “processor” or “operating processor” includes one or more processors, wherein processor refers to any logic circuitry for
20 processing instructions. A processor may be a general-purpose processor, a special
purpose processor, a conventional processor, a digital signal processor, a plurality of microprocessors, one or more microprocessors in association with a (Digital Signal Processing) DSP core, a controller, a microcontroller, Application Specific Integrated Circuits, Field Programmable Gate Array circuits, any other type of
25 integrated circuits, etc. The processor may perform signal coding data processing,
input/output processing, and/or any other functionality that enables the working of the system according to the present disclosure. More specifically, the processor or processing unit is a hardware processor.
9

[0038] As used herein, “a user equipment”, “a user device”, “a smart-user-device”,
“a smart-device”, “an electronic device”, “a mobile device”, “a handheld device”,
“a wireless communication device”, “a mobile communication device”, “a
communication device” may be any electrical, electronic and/or computing device
5 or equipment, capable of implementing the features of the present disclosure. The
user equipment/device may include, but is not limited to, a mobile phone, smart
phone, laptop, a general-purpose computer, desktop, personal digital assistant,
tablet computer, wearable device or any other computing device which is capable
of implementing the features of the present disclosure. Also, the user device may
10 contain at least one input means configured to receive an input from at least one of
a transceiver unit, a processing unit, a storage unit and any other such unit(s) which are required to implement the features of the present disclosure.
[0039] As used herein, “storage unit” or “memory unit” refers to a machine or
15 computer-readable medium including any mechanism for storing information in a
form readable by a computer or similar machine. For example, a computer-readable
medium includes read-only memory (“ROM”), random access memory (“RAM”),
magnetic disk storage media, optical storage media, flash memory devices or other
types of machine-accessible storage media. The storage unit stores at least the data
20 that may be required by one or more units of the system to perform their respective
functions.
[0040] As used herein “interface” or “user interface” refers to a shared boundary
across which two or more separate components of a system exchange information
25 or data. The interface may also be referred to a set of rules or protocols that define
communication or interaction of one or more modules or one or more units with each other, which also includes the methods, functions, or procedures that may be called.
10

[0041] All modules, units, components used herein, unless explicitly excluded
herein, may be software modules or hardware processors, the processors being a
general-purpose processor, a special purpose processor, a conventional processor,
a digital signal processor (DSP), a plurality of microprocessors, one or more
5 microprocessors in association with a DSP core, a controller, a microcontroller,
Application Specific Integrated Circuits (ASIC), Field Programmable Gate Array circuits (FPGA), any other type of integrated circuits, etc.
[0042] As used herein the transceiver unit include at least one receiver and at least
10 one transmitter configured respectively for receiving and transmitting data, signals,
information, or a combination thereof between units/components within the system and/or connected with the system.
[0043] As discussed in the background section, the current known solutions for
15 computing network availability at scale have several shortcomings such as the
currently known solutions fail to monitor the network availability at all levels, viz., state, business cluster, maintenance cluster and to the site level when the network consists of millions of nodes.
20 [0044] The present disclosure aims to overcome the above-mentioned and other
existing problems in this field of technology by automating the complex calculation of cell availability for a day which helps the network engineer to monitor the uptime of the cell, site etc. Also, the present disclosure provides visibility to managerial team to have a view of overall network availability from national level to a business
25 or maintenance centre enabling them to focus on the poor performing areas. The
present disclosure provides network service provider a holistic view which in turn helps in decision making to improve the network uptime. In addition, the present disclosure provides optimized and ease monitoring of plurality of nodes based on the network availability at all levels, viz., state, business cluster, maintenance
30 cluster and to the site level.
11

[0045] Also, as used in the present disclosure “Fault management” is the
component of network management that detects, isolates, and fixes problems. When
properly implemented, network fault management can keep connectivity,
5 applications and services running at an optimal level, provide fault tolerance and
minimize downtime. Fault management systems are platforms or tools designed specifically for this purpose. Faults result from malfunctions or events that interfere with, degrade, or obstruct service delivery.
10 [0046] An application programming interface (API) is a set of protocols, rules, and
tools that specifies how software components should interact and communicate with each other. APIs are used in all kinds of digital environments such as Web APIs, for example, HTTP APIs or REST APIs; Operating System APIs define how different software applications interact with the operating system. For example, if
15 a software program needs to display a window on a display screen, it uses an API
provided by the operating system to do so; and database APIs enable communication between an application and a database. For example, if an application needs to retrieve some data from a database, it uses a database API to send a query to the database and receive the results.
20
[0047] Hereinafter, exemplary embodiments of the present disclosure will be described with reference to the accompanying drawings.
[0048] FIG. 1 illustrates an exemplary block diagram of a computing device [100]
25 (also referred to herein as a computer system) upon which the features of the present
disclosure may be implemented in accordance with exemplary implementation of
the present disclosure. In an implementation, the computing device [100] may also
implement a method for computing network availability at scale utilising the system
[200]. In another implementation, the computing device [100] itself implements the
30 method for computing network availability at scale using one or more units
12

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

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

[0053] The computing device [100] can send messages and receive data, including
program code, through the network(s), the network link [120] and the
communication interface [118]. In the Internet example, a server [130] might
5 transmit a requested code for an application program through the Internet [128], the
ISP [126], the local network [122], host [124] and the communication interface [118]. The received code may be executed by the processor [104] as it is received, and/or stored in the storage device [110], or other non-volatile storage for later execution.
10
[0054] The computing device [100] encompasses a wide range of electronic devices capable of processing data and performing computations. Examples of computing device [100] include, but are not limited only to, personal computers, laptops, tablets, smartphones, servers, and embedded systems. The devices may
15 operate independently or as part of a network and can perform a variety of tasks
such as data storage, retrieval, and analysis. Additionally, computing device [100] may include peripheral devices, such as monitors, keyboards, and printers, as well as integrated components within larger electronic systems, showcasing their versatility in various technological applications.
20
[0055] Referring to FIG. 2, an exemplary block diagram of a system [200] for computing network availability at scale, is shown, in accordance with the exemplary implementations of the present disclosure. The system [200] comprises at least one identification unit [202], at least one processing unit [204], at least one
25 receiving unit [206], at least one database [208], at least one application server [210]
and at least one fault management (FM) microservice [212]. Also, all of the components/ units of the system [200] are assumed to be connected to each other unless otherwise indicated below. As shown in the figures all units shown within the system should also be assumed to be connected to each other. Also, in FIG. 2
30 only a few units are shown, however, the system [200] may comprise multiple such
15

units or the system [200] may comprise any such numbers of said units, as required
to implement the features of the present disclosure. Further, in an implementation,
the system [200] may be present in a user device to implement the features of the
present disclosure. The system [200] may be a part of the user device connected to
5 a server or network / or the system [200] may be independent of but in
communication with such user device (may also referred herein as a UE). In another implementation, the system [200] may reside in a server or a network entity. In yet another implementation, the system [200] may reside partly in the server/ network entity and partly in the user device. 10
[0056] The system [200] is configured for computing network availability at scale, with the help of the interconnection between the components/units of the system [200].
15 [0057] The system [200] comprises at least one identification unit [202], configured
to identify one or more service affecting alarms raised for at least one of cell for a period of time. As used herein, sites also referred to as telecom sites (such as cell towers), are structures that house electrical communications equipment and antennae, enabling the surrounding region to use wireless communication devices
20 such as mobile phones and radios. Further, as used herein, cell is a geographic area
that is covered by one or more base stations in a cellular network. Therefore, the identification unit [202] identifies one or more service affecting alarms raised for at least one the cell for the period of time. The present disclosure encompasses that a user or a network administrator may define the period of time, such as, but not
25 limited to, number of day(s), week, hours, and on demand basis. The identification
unit [202] identifies one or more services, such as, including but not limited to, customer service type, subscription-based service type, band availability, and quality of service (QoS), and service affecting alarm(s) i.e., the alarm(s) that are raised for the one or more services at the defined site and/or the cell for the defined
30 period of time. The identification unit [202] stores an information of the service
16

affecting alarms (or a service affecting alarms information) with service ID, timestamp, cell information, and/or site information in the at least one or more database [208]. The identification unit [202] transmits the service affecting alarms information to the processing unit [204] for further processing. 5
[0058] The disclosure encompasses that, the user or the network administrator may pre-define a network coverage into such as, but not limited to, plurality of service areas, site levels, zone levels, cells levels, business cluster level, maintenance cluster level, band availability and the like.
10
[0059] The disclosure encompasses, the user or the network administrator may define different alarms or service affecting alarms with threshold values or ranges, duration of time for triggering alarms for different degradation events or service types such as quality of service (QoS), subscription services, band availability and
15 the like. In an implementation, the user may define the severity (i.e., impact) levels
of alarms such as, high, medium, low, ignore and corresponding types of actions (e.g., immediate response, wait for pre-defined duration after pre-defined number of degradation events) during outage monitoring of network availability.
20 [0060] The processing unit [204] is then configured to compute a duration of outage
for each cell based on the identification of the one or more service affecting alarms. The processing unit [204] computes the duration of outage for at least each cell, site, band type based on the identification of the one or more service affecting alarms and/or the information received from the identification unit [202]. The
25 disclosure encompasses, in an implementation, the processing unit [204] computes
the duration of outage by subtracting the start time of service degradation event (i.e., raised service affecting alarm time) from the end time (time of resolution of service degradation event or clear service affecting alarm time). In operation, the processing unit [204] is configured to remove an overlapping duration from the
30 duration of outage of each cell. The processing unit [204] calculates the outage
17

duration for each cell ensuring to remove overlapping duration to keep the integrity
of the data. Further, the overlapping duration corresponds to time when multiple
alarms are triggered simultaneously, or the same issue affects multiple cells,
detected using identifiers related to cells or alarms. By removing such durations,
5 the system [200] ensures that each outage period is counted accurately and without
redundancy.
[0061] Therefore, the processing unit [204] is configured to remove a planned
outage duration from the duration of outage for each cell. The processing unit [204]
10 excludes the planned outages from the duration of outage for each cell to give a real
picture of the availability of the cell. In an implementation, the planned outage may be pre-defined for the user defined zone, site, maintenance cluster level and the like.
[0062] Furthermore, the processing unit [204] is configured to generate outage
15 statistics based at least on the computation of outage for each cell and after
removing the planned outage duration, wherein the outage statistics are generated
for one or more geographical regions. In operation, the processing unit [204] may
generate outage statistics based at least on the computation of outage for each cell
after removing the planned outage duration. In an implementation, the outage
20 statistics may comprise site details, cell details, cell outage duration, number of
outage cell, user defined maintenance zone, outage summary band wise, outage summary network node(s) wise, an availability of cells, and/or the like.
[0063] Also, the system [200] comprises an application server [210], which is
25 configured to generate report configurations for outage statistics for each cell. The
processing unit [204] may communicate with the application server [210] for
creating the report configurations and generate outage statistics based on the created
report configurations. The processing unit [204] may store created report
configurations details and/or the generated outage statistics into the database [208].
30 In an implementation, the processing unit [204], the application server [210],
18

database [208] and other units/components of the system may communicate over RESTful Application Programming Interface (API).
[0064] The receiving unit [206] of the system [200] is configured to receive, via an
5 interface, a user input comprising selection of a geographical region and an attribute
level. The attribute level comprises at least one of a state level, a business level, a
cell level, a band level, and a site level. In an implementation, the user or the
network administrator may provide input from the user devices such as, computing
device, mobile device, human machine interface, network device and the like. The
10 user may select any input such as geographical region, zone, cell, site and the like
for network, service type availability reporting.
[0065] In an implementation, upon receipt of the user input, the processing unit
[204] is further configured to generate, at the application server [210], a report
15 configuration based at least on the received user input; and store the report
configuration in the database [208] based at least on the RESTful Application Programming Interface (API).
[0066] Further, the user or the network administrator may fetch the outage statistics
20 network availability report from the user input device.
[0067] Also, in an operation, the processing unit [204] is configured to retrieve, via
the Fault Management (FM) microservice [212], the stored report configuration
from the database [208]. Further, the processing unit [204] generates at least a
25 network availability report by using at least the stored report configuration from the
database [208] and the generated outage statistics. Thereafter, the processing unit [204] enables, via the interface, downloading of at least the network availability report, to the user or the network administrator.
19

[0068] In an implementation, the Fault Management (FM) microservice [212], application server [210] and database [208] may communicate over RESTful interface for fetching report configuration, accessing generated outage statistics, and downloading network availability report. 5
[0069] In a preferred implementation, the system [200] identifies all the service
affecting alarms for both cell and site level for day one and calculates the outage
duration for each cell ensuring to remove overlapping duration to keep the integrity
of the data. Also, planned outages are excluded from the outage calculation to give
10 a real picture of the availability of the cell. Now, the single aggregated figures are
made available for any geography spanning from a larger area (say country level area) to any smaller entity. This report can be fetched from the front-end report generation wizard.
15 [0070] Referring to FIG. 3 an exemplary method flow diagram [300], for
computing network availability at scale, in accordance with exemplary embodiments of the present invention is shown. In an implementation the method [300] is performed by the system [200]. Further, in an implementation, the system [200] may be present in a server device to implement the features of the present
20 disclosure. Also, as shown in FIG. 3, the method [300] starts at step [302].
[0071] At step [304], the method [300] as disclosed by the present disclosure comprises identifying, by an identification unit [202], one or more service affecting alarms raised for at least one of a cell, for a period of time. Therefore, the
25 identification unit [202] identifies one or more service affecting alarms raised for
at least one of the cell for a period of time. The present disclosure encompasses that, a user or a network administrator may define the period of time, such as, but not limited to, number of day(s), week, hours, and on demand basis. The identification unit [202] identifies one or more services, such as, including but not limited to,
30 customer service type, subscription-based service type, band availability, and
20

quality of service (QoS), and service affecting alarms i.e., the alarms that are raised
for the one or more services at the defined site and/or the cell for the defined period
of time. The identification unit [202] stores an information of the service affecting
alarms with service ID, timestamp, cell information, and/or site information in at
5 least one or more database [208]. The identification unit [202] transmits the service
affecting alarms information to a processing unit [204] for further processing.
[0072] The disclosure encompasses that, the user or the network administrator may
pre-define a network coverage into such as, but not limited to, plurality of service
10 areas, site levels, zone levels, cells levels, business cluster level, maintenance
cluster level, band availability and the like.
[0073] The disclosure encompasses, the user or the network administrator may define different alarms or service affecting alarms with threshold values or ranges,
15 duration of time for triggering alarms for different degradation events or service
types such as quality of service (QoS), subscription services, band availability and the like. In an implementation, the user may define the levels of alarms such as, high, medium, low, ignore and corresponding types of actions (e.g., immediate response, wait for pre-defined duration after pre-defined number of degradation
20 events) during outage monitoring of network availability.
[0074] Next, at step [306], the method [300] as disclosed by the present disclosure comprises computing, by the processing unit [204], a duration of outage for each cell based on the identification of the one or more service affecting alarms. The
25 method [300] implemented by system [200] comprises the processing unit [204],
which is configured to compute the duration of outage for at least each cell, site, band type based on the identification of the one or more service affecting alarms and/or the information received from the identification unit [202]. The processing unit [204] computes the duration of outage by subtracting the start time of service
30 degradation event (service affecting alarms) from the end time (time of resolution
21

of service degradation event). In an operation, the method [300] further comprising
removing, by the processing unit [204], an overlapping duration from the duration
of outage of each cell. The processing unit [204] calculates the outage duration for
each cell ensuring to remove overlapping duration to keep the integrity of the data.
5 Further, the overlapping duration corresponds to time when multiple alarms are
triggered simultaneously, or the same issue affects multiple cells. By removing such durations, via the processing unit [204], the system [200] ensures that each outage period is counted accurately and without redundancy.
10 [0075] At step [308], the method [300] as disclosed by the present disclosure
comprises removing, by the processing unit [204], a planned outage duration from the duration of outage for each cell. Further, the processing unit [204] excludes the planned outages from the outage calculation to give a real picture of the availability of the cell. In an implementation, the planned outage may be pre-defined for the
15 user defined zone, site, maintenance cluster level and the like.
[0076] Next, at step [310], the method [300] as disclosed by the present disclosure
comprises generating, by the processing unit [204], outage statistics based at least
on the computing and removing step, wherein the outage statistics are generated for
20 one or more geographical regions. In an implementation, the outage statistics may
comprise site details, cell details, cell outage duration, number of outage cell, user defined maintenance zone, outage summary band wise, outage summary network node(s) wise, an availability of cells, and/or the like.
25 [0077] In an operation, the method [300] implemented by the system [200]
comprises an application server [210], which generates report configurations for outage statistics for each cell. The processing unit [204] may communicate with the application server [210] for creating the report configurations and generate outage statistics based on the created report configurations. The processing unit [204] may
30 store created report configurations details and/or the generated outage statistics into
22

the database [208]. In an implementation, the processing unit [204], the application server [210], database [208] and other units/components of the system may communicate over RESTful Application Programming Interface (API).
5 [0078] In an operation, the method [300] comprising receiving, by a receiving unit
[206] of the system [200] via an interface, a user input comprising selection of a
geographical region and an attribute level. In an exemplary aspect, the attribute
level comprises at least one of a state level, a business level, a cell level, a band
level, and a site level. In an implementation, the user or the network administrator
10 may provide input from the user devices such as, computing device, mobile device,
human machine interface, network device and the like. The user may select any input such as geographical region, zone, cell, site and the like for network, service type availability reporting.
15 [0079] In an operation, the method [300], upon receiving the user input, further
comprising generating, by the processing unit [204] at the application server [210], a report configuration based at least on the received user input; and storing, by the processing unit [204], the report configuration in the database [208] based at least on the RESTful Application Programming Interface (API). Further, the user or
20 network administrator may fetch the outage statistics network availability report
from the user input device.
[0080] The present disclosure also encompasses, the method [300] further comprises retrieving, by the processing unit [204] via a Fault Management (FM)
25 microservice [212] of the system [200], the stored report configuration from the
database [208]; generating, by the processing unit [204], at least a network availability report by using at least the stored report configuration from the database [208] and the generated outage statistics; and enabling, by the processing unit [204] via the interface, downloading of at least the network availability report.
30
23

[0081] In an implementation, the FM microservice [212] is the component of
network management that detects, isolates, and fixes problems. During operation,
network fault management can keep connectivity, applications and services running
at an optimal level, provide fault tolerance and minimize downtime. Fault
5 management systems are platforms or tools designed specifically for this purpose.
Faults result from malfunctions or events that interfere with, degrade, or obstruct
service delivery. Examples of faults include hardware failure, connectivity loss or
port status change. Once the fault management platform detects a fault, it notifies
the network administrator and any additional authorized or designated parties via
10 an alarm or alert.
[0082] Thereafter, the method terminates at step [312].
[0083] FIG. 4 illustrates an exemplary block diagram [400] of a user equipment
15 [402] in connection with a server [410] via a network [408], for computing network
availability at scale, in accordance with exemplary embodiments of the present disclosure.
[0084] As shown in FIG. 4, exemplary block diagram [400] comprises a user
20 equipment [402] having a processor [404] and memory [406], wherein the user
equipment [402] is connected with the server [410] over the network [408]. In an
operation, the user equipment (UE) [402] comprising the processor [404] is
configured to send, to a system [200], a user input comprising selection of a
geographical region and an attribute level; and receive, from the system [200], a
25 network availability report generated based on at least a stored report configuration,
wherein the stored report configuration is generated by the system [200] using the
user input, wherein the network availability report is generated based on
identifying, by the system [200], one or more service affecting alarms raised for at
least one cell, for a period of time. The processor [404] is further configured to
30 computing, by the system [200], a duration of outage for each cell based on the one
24

or more service affecting alarms. The processor [404] is further configured to
removing, by the system [200], a planned outage duration from the duration of
outage for each cell. The processor [404] is furthermore configured to generating,
by the system [200], outage statistics based at least on the computation of outage
5 for each cell and after removing the planned outage duration, wherein the outage
statistics are generated for one or more geographical regions. The memory [406] stores computation data of the processor [404].
[0085] FIG. 5 illustrates an exemplary process flow diagram [500] indicating the
10 process for fetching the network availability report, in accordance with exemplary
embodiments of the present disclosure. As shown in FIG. 5, the disclosure
encompasses at step S1, an App Server [502] creates a report configuration using
Rest API to create Report configuration with Rest Service 1 [504]. In an
implementation, the user may select through the graphical user interface (GUI) of
15 user device, the geography configuration to fetch the network availability report.
[0086] Next at step S2, the Rest Service 1 [504] stores the report configuration on database [506].
20 [0087] Next at step S3, the FM microservice [508] retrieves the saved report
configuration from the database [506] and at step S4, fetches network availability data from database [506] and generates Network Availability report via Rest Service 2 [510].
25 [0088] Next at step S5, the Rest Service 2 [510] downloads generated network
availability report to App Server [502], which is downloadable from the front end via user input device.
[0089] FIG. 6a – 6e illustrates tables [600] representing statistics report at the cell
30 level. The cell level comprises sites details, integration details, outage summary of
25

GNB/band wise details, outage details of cells (seconds), availability, outage details of cells.
[0090] FIG. 6a illustrates a table showing site details comprising various states,
5 names of different clusters such as but not limited to maintenance clusters, business
clusters, and identifiers such as network element identifier (NE ID)
[0091] FIG. 6b illustrates a table showing integration details comprising details related to integration state, and various bands such as band 1 and band 2.
10
[0092] FIG. 6c, illustrates a table showing outage summary of GNB/band wise details. The table includes cell count of band 1, cell count of band 2 and corresponding outages such as outages seconds of band 1 and outage seconds of band 2. Further, the table includes Total Cell Count and Total Outage Seconds.
15
[0093] FIG. 6d, illustrates a table showing band 1 availability and band 2 and site availability.
[0094] FIG. 6e, illustrates a table showing outage details (in seconds) of cells such
20 as but not limited to outage of cell no. 1, cell no. 2, cell no. 3, cell no. 4, cell no. 5,
cell no. 6, cell no. 7, cell no 8 and cell no 9.
[0095] FIG. 7 illustrates a table representing statistic report at state level. The state
level report comprises reports of various zones represented as zone E, W, N etc.,
25 total number of cells in those zones, overall cell availability (in percentage), and
availability of band 1 and band 2 (in percentage). The overall cell availability is calculated by taking average of cell availability of band 1 and band 2.
26

[0096] FIG. 8 illustrates a table representing statistic report at maintenance level as
referred to herein as maintenance cluster. The maintenance cluster comprises
various zones represented as zone N, W etc. The table further include maintenance
cluster names, total cells, overall cell availability (in percentage) based on band 1
5 availability and band 2 availability. The overall cell availability is calculated by
taking average of cell availability of band 1 and band 2.
[0097] FIG. 9 illustrates a table representing statistic report at business level also
represented herein as business cluster. The business cluster comprises details
10 related to business cluster’s identity (ID), business clusters names, total cells,
overall cell availability, band 1 availability and band 2 availability. The overall cell availability is calculated by taking average of cell availability of band 1 and band 2.
15 [0098] The present disclosure further discloses a non-transitory computer readable
storage medium storing instructions for computing network availability at scale, the instructions include executable code which, when executed by one or more units of a system, causes: an identification unit [202], to identify one or more service affecting alarms raised for at least one of a cell level for a period of time; a
20 processing unit [204] of the system to compute a duration of outage for each cell
based on the identification of the one or more service affecting alarms, remove a planned outage duration from the duration of outage for each cell, and generate outage statistics based at least on the computation of outage for each cell and after removing the planned outage duration, wherein the outage statistics are generated
25 for one or more geographical regions.
[0099] As is evident from the above, the present disclosure provides a technically
advanced solution for computing network availability at scale. The present
disclosure provides a solution that helps in decision making to improve the network
30 uptime. Further, the present disclosure automates the complex calculation of cell
27

availability for a day which helps the network engineer to monitor the uptime of the
cell, site etc. Furthermore, the present disclosure enables the Network and Business
team to take collective action on the impacted geographies and helps in improving
the network uptime and hence the customer experience. The present disclosure also
5 provides single glass pane view of the quality of the network which in turn gives
the measure of customer experience. This feature is useful right from network
operation engineer to the apex team as this captures all the relevant data individually
at cell level and also at hierarchical aggregated level. As this feature is an automated
form, the accuracy of the uptime indicated is almost cent percent taking into account
10 the planned activity duration for maintenance work is excluded from the
computation.
[0100] Further, in accordance with the present disclosure, it is to be acknowledged that the functionality described for the various the components/units can be implemented interchangeably. While specific embodiments may disclose a
15 particular functionality of these units for clarity, it is recognized that various
configurations and combinations thereof are within the scope of the disclosure. The functionality of specific units as disclosed in the disclosure should not be construed as limiting the scope of the present disclosure. Consequently, alternative arrangements and substitutions of units, provided they achieve the intended
20 functionality described herein, are considered to be encompassed within the scope
of the present disclosure.
[0101] While considerable emphasis has been placed herein on the
disclosed embodiments, it will be appreciated that many embodiments can be made
25 and that many changes can be made to the embodiments without departing from the
principles of the present disclosure. These and other changes in the embodiments of the present disclosure will be apparent to those skilled in the art, whereby it is to be understood that the foregoing descriptive matter to be implemented is illustrative and non-limiting.
30
28

We Claim
1. A method for computing network availability at scale, comprising:
- identifying, by an identification unit [202], one or more service affecting alarms raised for at least one cell, for a period of time;
- computing, by a processing unit [204], a duration of outage for each cell based on the identification of the one or more service affecting alarms;
- removing, by the processing unit [204], a planned outage duration from the duration of outage for each cell; and
- generating, by the processing unit [204], outage statistics based at least on the computing and removing step, wherein the outage statistics are generated for one or more geographical regions.

2. The method as claimed in claim 1, further comprising receiving, by a receiving unit [206] via an interface, a user input comprising selection of a geographical region and an attribute level.
3. The method as claimed in claim 1, further comprising removing, by the processing unit [204], an overlapping duration from the duration of outage for each cell.
4. The method as claimed in claim 2, wherein upon receiving the user input, the method further comprising:

- generating, by the processing unit [204] at an application server [210], a report configuration based at least on the received user input; and
- storing, by the processing unit [204], the report configuration in a database [208] based at least on a RESTful Application Programming Interface (API).
5. The method as claimed in claim 4, further comprising:

- retrieving, by the processing unit [204] via a Fault Management (FM) microservice [212], the stored report configuration from the database [208];
- generating, by the processing unit [204], at least a network availability report by using at least the stored report configuration from the database [208] and the generated outage statistics; and
- enabling, by the processing unit [204] via the interface, downloading of at least the network availability report.

6. The method as claimed in claim 2, wherein the attribute level comprises at least one of a state level, a business level, a cell level, a band level, and a site level.
7. A system for computing network availability at scale, comprising:

- an identification unit [202], configured to identify one or more service affecting alarms raised for at least one cell, for a period of time;
- a processing unit [204] connected at least to the identification unit [202], the processing unit [204] configured to:
compute a duration of outage for each cell based on the identification of the one or more service affecting alarms;
remove a planned outage duration from the duration of outage for each cell; and
generate outage statistics based at least on the computation of outage for each cell and after removing the planned outage duration, wherein the outage statistics are generated for one or more geographical regions.
8. The system as claimed in claim 7, wherein a receiving unit [206] is
configured to receive, via an interface, a user input comprising selection of
a geographical region and an attribute level.

9. The system as claimed in claim 7, wherein the processing unit [204] is further configured to remove an overlapping duration from the duration of outage for each cell.
10. The system as claimed in claim 8, wherein upon receipt of the user input, the processing unit [204] is further configured to:

- generate, at an application server [210], a report configuration based at least on the received user input; and
- store the report configuration in a database [208] based at least on a RESTful Application Programming Interface (API).
11. The system as claimed in claim 10, wherein the processing unit [204] is
further configured to:
- retrieve, via a Fault Management (FM) microservice [212], the stored report configuration from the database [208];
- generate at least a network availability report by using at least the stored report configuration from the database [208] and the generated outage statistics; and
- enable, via the interface, downloading of at least the network availability report.

12. The system as claimed in claim 8, wherein the attribute level comprises at least one of a state level, a business level, a cell level, a band level, and a site level.
13. A user equipment (UE) comprising:
a processor [404], the processor [404] configured to:
send, to a system [200], a user input comprising selection of a geographical region and an attribute level; and

receive, from the system [200], a network availability report generated based on at least a stored report configuration, wherein the stored report configuration is generated by the system [200] using the user input, wherein the network availability report is generated based on
identify, by the system [200], one or more service affecting alarms raised for at least one of a site and a cell, for a period of time,
compute, by the system [200], a duration of outage for each cell based on the one or more service affecting alarms,
remove, by the system [200], a planned outage duration from the duration of outage for each cell; and
generate, by the system [200], outage statistics based at least on the computation of outage for each cell and after removing the planned outage duration, wherein the outage statistics are generated for one or more geographical regions.