FORM 2
THE PATENTS ACT, 1970
THE PATENTS RULE 0) 003
COMPLETE SPECIFICATION
NETWORK
APPLICANT
380006, Gujarat, India; Nationality: India
The following specification particularly describes
the invention and the manner in which
it is to be performed

RESERVATION OF RIGHTS
[001] A portion of the disclosure of this patent document contains
material, which is subject to intellectual property rights such as, but are not limited to, copyright, design, trademark, integrated circuit (IC) layout design, and/or trade dress protection, belonging to Jio Platforms Limited (JPL) or its affiliates (herein after referred as owner). The owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all rights whatsoever. All rights to such intellectual property are fully reserved by the owner.
TECHNICAL FIELD
[002] The present disclosure relates to a field of a network function, and
specifically to a system and a method for managing conditional alarms in a wireless network.
DEFINITION
[003] As used in the present disclosure, the following terms are generally
intended to have the meaning as set forth below, except to the extent that the context in which they are used to indicate otherwise.
[004] The term ‘network function’ as used herein, refers to a software-
based entity within a wireless network that performs specific network operations, such as handling call flows, managing network resources, and maintaining communication protocols. The network function may be deployed at various locations such as edge compute sites, central sites, public cloud, or private cloud environments, and can originate from different vendors.
[005] The term ‘Event Management System (EMS)’ as used herein,
refers to a centralized system responsible for monitoring, managing, and triggering events across a wireless network, including the resetting of network counters, system alerts, and fault detection.

[006] The term ‘call flow counters’ as used herein, refer to numerical
values maintained by the network function that track the number and status of
ongoing call flows and events within the network. These counters are crucial for
assessing network performance and identifying abnormal conditions.
[007] The term ‘non-zero counters’ as used herein, refer to call flow
counters that indicate active or unresolved call flows or events. These counters are critical in determining ongoing network conditions and are not reset during EMS-triggered resets.
BACKGROUND
[008] 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.
[009] In modern wireless networks, maintaining robust and efficient
network performance is critical. Network operators constantly monitor various
system parameters to ensure network smooth operation and to quickly address any
issues that may arise. One important aspect of network management is the ability
to detect abnormal conditions and failure scenarios early on, allowing for timely
intervention and mitigation measures.
[0010] Conditional alarms play a critical role at a network function level in
order to identify abnormal conditions in a system. The unusual conditions may be,
for example, memory overload, congestion risk, and the like. There are different
categories defined for the conditional alarms like warning, major, and critical as
per a pre-configured threshold value. The network function (NF) maintains call
flow counters for all different error scenarios. The NF may raise different
categories of the conditional alarms based on these counter values and threshold
defined for each error condition.
[0011] However, a significant challenge in the current approach for

managing conditional alarms is a handling of counter resets triggered by the Event Management System (EMS). Periodically, the EMS sends reset requests to the NFs to reset various counters, which helps in maintaining accurate and up-to-date monitoring data. Unfortunately, this may interfere with the conditional alarm mechanism. Specifically, if critical counters are reset while ongoing call flows or unresolved events are still being monitored, it may lead to a failure in generating necessary alarms, thereby compromising the network ability to detect and respond to abnormal conditions effectively.
[0012] There is, therefore, a need in the art to improve state of managing
conditional alarm call flow by overcoming the deficiencies of the prior arts.
SUMMARY
[0013] In an exemplary embodiment, a method for managing conditional
alarms in a wireless network is described. The method includes maintaining, by a network function (NF) module, a plurality of call flow counters defined for one or more conditional alarms. The one or more conditional alarms identify a plurality of abnormal conditions. The method includes monitoring, by the NF module, the plurality of call flow counters for the one or more conditional alarm. Each of the one or more conditional alarms is configured with a predefined threshold value. The method include detecting, by the NF module, a reset request from an event management system (EMS). The method includes upon detecting the reset request from the EMS, checking, by the NF module, for non-zero counters from the plurality of call flow counters. The non-zero counters indicate one of ongoing call flow or unresolved events. The method further includes storing, by the NF module, the non-zero counters that are relevant for the one or more conditional alarms to prevent the non-zero counters from being reset and resetting, by the NF module, remaining counters other than the non-zero counters. The method comprises raising, by the NF, the one or more conditional alarms when the stored non-zero counters reach predefined threshold.
[0014] In some embodiments, the plurality of abnormal conditions
includes a system overload, a memory overload, a congestion risk, a system

failure, a network failure, and an endpoint unreachability.
[0015] In some embodiments, the one or more conditional alarms are
categorized into a plurality of categories based on the predefined threshold value.
[0016] In some embodiments, the plurality of categories for the one or
more of conditional alarms comprises warning, major, and critical.
[0017] In some embodiments, the method includes preventing the reset of
non-zero counters corresponding to the ongoing call flows upon receiving a reset request from the EMS.
[0018] In another exemplary embodiment, a system for managing
conditional alarms in a wireless network is described. The system comprises a
server, a network function (NF) module, a memory, and one or more processor(s)
communicatively coupled with the memory. The one or more processor(s) is
configured to maintain a plurality of call flow counters defined for one or more
conditional alarms. The one or more conditional alarms is used to identify a
plurality of abnormal conditions. The one or more processor(s) is configured to
monitor the plurality of call flow counters for the one or more conditional alarms.
Each of the one or more conditional alarms is configured with a predefined
threshold value. The one or more processor(s) is configured to detect a reset
request from an event management system (EMS). On detecting the reset request
from the EMS, the one or more processor(s) is configured to check for non-zero
counters from the plurality of call flow counters. The non-zero counters indicate
ongoing call flows or unresolved events. The one or more processor(s) is
configured to store the non-zero counters that are relevant for the one or more
conditional alarms to prevent the non-zero counters from being reset and reset
remaining counters other than the non-zero counters. The one or more
processor(s) is further configured to raise the one or more conditional alarms
when the stored non-zero counters reach the predefined threshold.
[0019] In some embodiments, the plurality of abnormal conditions
includes a system overload, a memory overload, a congestion risk, a system
failure, a network failure, and an endpoint unreachability.
[0020] In some embodiments, the one or more conditional alarms are

categorized into a plurality of categories based on the predefined threshold value.
[0021] In some embodiments, the plurality of categories for the one or
more of conditional alarms comprises warning, major, and critical.
[0022] In some embodiments, the one or more processor(s) is configured
to prevent the reset of non-zero counters corresponding to the ongoing call flows
upon receiving a reset request from the EMS.
[0023] In yet another exemplary embodiment, a network function (NF)
module for managing conditional alarms in a wireless network is described. The
NF module is configured to maintain a plurality of call flow counters defined for
one or more conditional alarms. The one or more conditional alarms is used to
identify a plurality of abnormal conditions. The NF module is configured to
monitor the plurality of call flow counters for the one or more conditional alarms.
Each of the one or more conditional alarms is configured with a predefined
threshold value. The NF module is configured to detect a reset request from an
event management system (EMS). On detecting the reset request from the EMS,
the NF module is configured to check for non-zero counters from the plurality of
call flow counters. The non-zero counters indicate ongoing call flows or
unresolved events. The NF module is configured to store the non-zero counters
that are relevant for the one or more conditional alarms to prevent the non-zero
counters from being reset and reset remaining counters other than the non-zero
counters. The NF module is further configured to raise the one or more
conditional alarms when the stored non-zero counters reach the predefined
threshold.
[0024] In some embodiments, the plurality of abnormal conditions
includes a system overload, a memory overload, a congestion risk, a system
failure, a network failure, and an endpoint unreachability.
[0025] In some embodiments, the one or more conditional alarms are
categorized into a plurality of categories based on the predefined threshold value.
[0026] In some embodiments, the plurality of categories for the one or
more of conditional alarms include warning, major, and critical.
[0027] In some embodiments, the NF module is configured to prevent the

reset of non-zero counters corresponding to the ongoing call flows upon receiving a reset request from the EMS.
[0028] The foregoing general description of the illustrative embodiments
and the following detailed description thereof are merely exemplary aspects of the teachings of this disclosure and are not restrictive.
OBJECTS OF THE PRESENT DISCLOSURE
[0029] An object of the present disclosure is to provide a system and a
method to manage conditional alarms in a network function.
[0030] An object of the present disclosure is to store counters which are
used for raising conditional alarms, and reset other counters, thereby ensuring that
the conditional alarms are raised at a proper threshold value in order to prevent
system failure.
[0031] An object of the present disclosure is to describe failure conditions
in the system which helps in recovering possible failure scenario from the system
end.
[0032] An object of the present disclosure is to monitor a plurality of call
flow counters for the one or more conditional alarms.
BRIEF DESCRIPTION OF THE DRAWINGS
[0033] In the figures, similar components and/or features may have the
same reference label. Further, various components of the same type may be
distinguished by following the reference label with a second label that
distinguishes among the similar components. If only the first reference label is
used in the specification, the description is applicable to any one of the similar
components having the same first reference label irrespective of the second
reference label.
[0034] The diagrams are for illustration only, which thus is not a limitation
of the present disclosure, and wherein:
[0035] FIG. 1 illustrates an exemplary network architecture in which or
with which embodiments of the present disclosure may be implemented.

[0036] FIG. 2 illustrates an exemplary block diagram of a conditional
alarm managing system, in accordance with an embodiment of the present
disclosure.
[0037] FIG. 3 illustrates an exemplary process flow for managing
conditional alarms in a wireless network depicted via a flow chart, in accordance
with an embodiment of the present disclosure.
[0038] FIG. 4 illustrates a flow diagram of a method for managing
conditional alarms in a wireless network, in accordance with an embodiment of
the present disclosure
[0039] FIG. 5 illustrates an exemplary computer system in which or with
which embodiments of the present disclosure may be implemented.
[0040] The foregoing shall be more apparent from the following more
detailed description of the disclosure.
LIST OF REFERENCE NUMERALS
100 – Network architecture
102-1, 102-2…102-N - Users
104-1, 104-2…104-N - User Equipment (UE)
106 – Network
108 – System
110 – Server
200 – Block Diagram
202 – One or more processor(s)
204 – Memory
206 – One or more interface(s)
208 – Network Function (NF) module
210 – Counters monitoring module

212 – Reset handling module
214 – Threshold monitoring module
216 – Alarm generation module
218 – Database
500 – A computer system
510 – External storage device
520 – Bus
530 – Main memory
540 – Read only memory
550 – Mass storage device
560 – Communication port(s)
570 – Processor
DETAILED DESCRIPTION OF DISCLOSURE
[0041] The following is a detailed description of embodiments of the
disclosure depicted in the accompanying drawings. The embodiments are in such detail as to clearly communicate the disclosure. However, the amount of detail offered is not intended to limit the anticipated variations of embodiments; on the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the present disclosure as defined by the appended claims.
[0042] The present disclosure monitors counters maintained in a network
function (NF). The counters are useful for raising conditional alarms irrespective of a trigger from Element Management System (EMS). The NF stores required counters which are useful in case of conditional alarms, and these conditional alarms are used to detect failure scenario e.g., if endpoint is not reachable, or the network function reached overload condition. The conditional alarms provides early warning to the system so that some measures may be taken within time to avoid complete failover.

[0043] The various embodiments of the present disclosure will be
explained in detail with reference to FIGs. 1 to 5.
[0044] FIG. 1 illustrates an exemplary network architecture (100) in which
or with which embodiments of the present disclosure may be implemented.
5 [0045] Referring to FIG. 1, the network architecture (100) may include
one or more computing devices or one or more user equipments (UEs) (104-1,
104-2…104-N) associated with one or more users (102-1, 102-2…102-N) in an
environment. A person of ordinary skill in the art will understand that one or more
users (102-1, 102-2…102-N) may be individually referred to as the user (102) and
10 collectively referred to as the users (102). Similarly, a person of ordinary skill in
the art will understand that one or more UE (104-1, 104-2…104-N) may be
collectively referred to as the UE (104). A person of ordinary skill in the art will
appreciate that the terms “computing device(s)” and “user equipment” may be
used interchangeably throughout the disclosure. Although only three user UE
15 (104) are depicted in FIG. 1, however any number of the UEs (104) may be
included without departing from the scope of the ongoing description.
[0046] In an embodiment, the UE (104) may include smart devices
operating in a smart environment, for example, an Internet of Things (IoT) system. In such an embodiment, the UE (104) may include, but not limited to, 20 smart phones, smart watches, smart sensors (e.g., mechanical, thermal, electrical, magnetic, etc.), networked appliances, networked peripheral devices, networked lighting system, communication devices, networked vehicle accessories, networked vehicular devices, smart accessories, tablets, smart television (TV), computers, smart security system, smart home system, other devices for 25 monitoring or interacting with or for the users (102) and/or entities, or any combination thereof. A person of ordinary skill in the art will appreciate that the UE (104) may include, but not limited to, intelligent, multi-sensing, network-connected devices, that may integrate seamlessly with each other and/or with a central server or a cloud-computing system or any other device that is network-30 connected.
[0047] Additionally, in some embodiments, the UE (104) may include, but
10

not limited to, a handheld wireless communication device (e.g., a mobile phone, a smart phone, a phablet device, and so on), a wearable computer device(e.g., a head-mounted display computer device, a head-mounted camera device, a wristwatch computer device, and so on), a Global Positioning System (GPS) 5 device, a laptop computer, a tablet computer, or another type of portable computer, a media playing device, a portable gaming system, and/or any other type of computer device with wireless communication capabilities, and the like. In an embodiment, the user equipment (104) may include, but is not limited to, any electrical, electronic, electro-mechanical, or an equipment, or a combination of
10 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, wherein the UE (104) may include one or more in-built or externally coupled accessories including, but not limited to, a visual aid device such as a
15 camera, an audio aid, a microphone, a keyboard, and input devices for receiving input from the user (102) or the entity such as touch pad, touch enabled screen, electronic pen, and the like. A person of ordinary skill in the art will appreciate that the UE (104) may not be restricted to the mentioned devices and various other devices may be used.
20 [0048] Referring to FIG. 1, the UE (104) may communicate with a system
(108), for example, a conditional alarm managing system (108), through a network (106) for sending or receiving various data. In order to establish communication, initially, the network (106) is configured to receive a connection request from the UE (104). In response to receiving the connection request, the
25 network (106) is configured to send an acknowledgment of the connection request
to the UE (104). Further, a plurality of signals is transmitted in response to the
connection request. Based on the connection request, the conditional alarms may
be managed in a wireless network (e.g., the network (106)).
[0049] The conditional alarm managing system (108) may include a server
30 (110). The server (110) may include various modules that may be work together to manage conditional alarms in the wireless network. The various modules are
11

explained in detail in conjunction with FIG. 2. The server (110) may be a
centralized server configured to store counters (for example, non-zero counters)
for raising conditional alarms. Thereby, ensuring that the conditional alarms are
raised at a predefined threshold value in order to prevent system failure. These
5 conditional alarms may describe failure conditions in the system which helps in
recovering the possible failure scenario from the system end.
[0050] In an embodiment, the network (106) may include at least one of a
Fifth Generation (5G) network, 6G network, or the like. The network (106) may enable the UE (104) to communicate with other devices in the network
10 architecture (100) and/or with the conditional alarm managing system (108). The network (106) may include a wireless card or some other transceiver connection to facilitate this communication. In another embodiment, the network (106) may be implemented as, or include any of a variety of different communication technologies such as a wide area network (WAN), a local area network (LAN), a
15 wireless network, a mobile network, a Virtual Private Network (VPN), the
Internet, the Public Switched Telephone Network (PSTN), or the like.
[0051] Although FIG. 1 shows exemplary components of the network
architecture (100), in other embodiments, the network architecture (100) may include fewer components, different components, differently arranged
20 components, or additional functional components than depicted in FIG. 1.
Additionally, or alternatively, one or more components of the network
architecture (100) may perform functions described as being performed by one or
more other components of the network architecture (100).
[0052] FIG. 2 illustrates an exemplary block diagram (200) of the
25 conditional alarm managing system (108) configured to manage conditional alarms in the wireless network, in accordance with an embodiment of the present disclosure.
[0053] In an embodiment, the conditional alarm managing system (108)
may include one or more processor(s) (202), a memory (204), one or more
30 interface(s) (206), and the server (110). The one or more processor(s) (202) may be implemented as one or more microprocessors, microcomputers,
12

microcontrollers, edge or fog microcontrollers, digital signal processors, central processing units, logic circuitries, and/or any devices that process data based on operational instructions. Among other capabilities, the one or more processor(s) (202) may be configured to fetch and execute computer-readable instructions 5 stored in the memory (204) of the conditional alarm managing system (108). 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 comprise any non-transitory storage device
10 including, for example, volatile memory such as Random-Access Memory (RAM), or non-volatile memory such as Erasable Programmable Read-Only Memory (EPROM), flash memory, and the like.
[0054] Further. the interface(s) (206) may include a variety of interfaces,
for example, interfaces for data input and output devices, referred to as I/O
15 devices, storage devices, and the like. The interface(s) (206) may facilitate communication of the conditional alarm managing system (108). The interface(s) (206) may also provide a communication pathway for one or more components or modules of the conditional alarm managing system (108). Examples of such modules may include, but not limited to, an NF module (208) and a database
20 (218).
[0055] The server (110) may include the NF module (208) that may be
implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the server (110). In examples described herein, such combinations of hardware and
25 programming may be implemented in several different ways. For example, the programming for the NF module (208) may be processor-executable instructions stored on a non-transitory machine-readable storage medium and the hardware for the NF module (208) may comprise a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the
30 machine-readable storage medium may store instructions that, when executed by the processing resource, implement the NF module (208). In such examples, the
13

conditional alarm managing system (108) may comprise the machine-readable storage medium storing the instructions and the processing resource to execute the instructions, or the machine-readable storage medium may be separate but accessible to the conditional alarm managing system (108) and the processing 5 resource. In other examples, the NF module (208) may be implemented by an electronic circuitry.
[0056] The NF module (208) may include various modules that work
together to manage the conditional alarms in the wireless network. These various modules may include a counters monitoring module (210), a reset handling
10 module (212), a threshold monitoring module (214), and an alarm generation module (216).
[0057] In order to manage the conditional alarms, initially, the counters
monitoring module (210) may be configured to maintain a plurality of call flow counters defined for one or more conditional alarms within the NF module (208).
15 The one or more conditional alarms identify a plurality of abnormal conditions. The plurality of abnormal conditions includes a system overload, a memory overload, a congestion risk, a system failure, a network failure, and an endpoint unreachability The plurality of call flow counters may include, but may not be limited to, call initiation counters, call duration counters, resource utilization
20 counters, error and failure counters, traffic, and load counters, congestion counters, and endpoint counters.
[0058] The call initiation counters may include a total number of call
attempts, successful call setups, and failed call setups. The call initiation counters may help in understanding a demand on the network and efficiency of call
25 processing. For example, a high number of failed call setups may indicate issues with network resource allocation or signal quality. The call duration counters, on the other hand, track an average and total duration of calls. This may help in identifying patterns such as unusually long or short calls, which may signify problems in call handling or user behavior anomalies.
30 [0059] The resource utilization counters are crucial for monitoring the
usage of network resources such as memory, CPU, and bandwidth. Memory usage
14

counters measure the amount of memory being consumed by the NF module 208, that may help to detect conditions of memory overload that may lead to system instability. Similarly, CPU usage counters track a processing power being utilized, allowing the network to identify overload conditions that may degrade 5 performance. Bandwidth utilization counters measure the amount of data being transmitted and received, providing information of congestion levels and network load.
[0060] The error and failure counters are vital for identifying specific
issues related to network reliability and quality. The number of dropped calls,
10 failed handovers, and error rates provide information about network performance problems.
[0061] The traffic and load counters may help in understanding overall
usage and demand on the network. Peak load times and traffic volume provide critical information for capacity planning and network optimization. Peak load
15 time counters identify periods when network usage is at its highest, enabling
operators to anticipate and manage congestion. Traffic volume counters measure a
total amount of data being handled by the network, indicating the overall demand
and helping in identifying trends and patterns in network usage.
[0062] The congestion counters are specifically designed to detect
20 conditions of network congestion. The endpoint counters, such as the number of unreachable endpoints and active endpoints, provide information about the network interaction with user devices.
[0063] Further, the counters monitoring module (210) may monitor the
plurality of call flow counters for the one or more conditional alarms. Each of the
25 one or more conditional alarms is configured with a predefined threshold value.
[0064] Further, the reset handling module (212) may detect a reset request
from the EMS. Upon detecting the reset request from the EMS, the reset handling module (212) further checks for non-zero counters from the plurality of call flow counters. The non-zero counters are those call flow counters that have values
30 greater than zero at a time the reset request is received from the EMS. The non-zero counters indicate active or ongoing network activities or unresolved events
15

that are critical for maintaining accurate monitoring and timely issue detection.
The reset handling module (212) may store the non-zero counters in the database
218 that are relevant for the one or more conditional alarms to prevent the non¬
zero counters from being reset.
5 [0065] Further, the reset handling module (212) may reset remaining
counters other than the non-zero counters. In some embodiments, the reset
handling module (212) may prevent the reset of non-zero counters corresponding
to the ongoing call flows upon receiving the reset request from the EMS.
[0066] The threshold monitoring module (214) may monitor a predefined
10 threshold value of the call flow counters. The predefined threshold value is critical parameters set for various call flow counters that determine when a conditional alarm needs to be triggered. The predefined threshold value for each of the one or more conditional alarms are carefully defined based on network operational requirements, historical data, and expected performance standards. The purpose of
15 the predefined threshold value is to provide an early warning that may alert
network operators for issues before escalating into severe problems.
[0067] By way of an example, if the number of active call flows exceeds
80% of the network’s total capacity, the conditional alarm may be triggered to indicate a risk of system overload. By way of another example, if memory usage
20 exceeds 90% of the available memory resources, the conditional alarm may be
raised to warn of potential memory exhaustion and system instability.
[0068] The alarm generation module (216) may raise the one or more
conditional alarms during abnormal conditions when the stored non-zero counters reach the predefined threshold. The alarm generation module (216) may compare
25 current values of the non-zero counters against the predefined threshold value to determine if an alarm should be raised. There may be different categories defined for conditional alarms like warning, major, and critical as per the predefined threshold value. The one or more conditional alarms categorize as warning may indicate an issue
30 that may be monitored but does not require immediate action. Further, the one or more conditional alarms categorize as major may signify a more serious condition
16

that may impact network performance and requires timely intervention.
Additionally, the one or more conditional alarms categorize as critical may
represent a severe condition that may lead to significant network disruption or
failure, necessitating immediate action.
5 [0069] In an embodiment, the database (218) may comprise data that may
be either stored or generated as a result of functionalities implemented by any of
the components of the processor(s) (202) or the NF module (208) or the
conditional alarm managing system (108).
[0070] Although FIG. 2 shows an exemplary block diagram (200) of the
10 conditional alarm managing system (108), in other embodiments, the conditional alarm managing system (108) may include fewer components, different components, differently arranged components, or additional functional components than depicted in FIG. 2. Additionally, or alternatively, one or more components of the conditional alarm managing system (108) may perform
15 functions described as being performed by one or more other components of the conditional alarm managing system (108).
[0071] Referring to FIG. 3, is an exemplary process flow for managing the
conditional alarms depicted via a flow chart (300), in accordance with an embodiment of the present disclosure. It should be noted that the process may be
20 implemented by the NF module (208) of the system (108).
[0072] At step 302 of the flow chart (300), the NF module (208) may start
conditional alarm managing process.
[0073] At step 304 of the flow chart (300), the NF module (208) may
define a plurality of call flow counters for one or more conditional alarms. The
25 one or more conditional alarms is used to identify a plurality of abnormal
conditions. The plurality of abnormal conditions includes a system overload, a
memory overload, a congestion risk, a system failure, a network failure, and an
endpoint unreachability.
[0074] At step 306 of the flow chart (300), the NF module (208) may
30 continuously monitor the plurality of call flow counters for the one or more conditional alarms. Each of the one or more conditional alarms is configured with
17

a predefined threshold value.
[0075] At step 308 of the flow chart (300), the NF module (208) may
detect if a reset request is received from an event management system (EMS).
[0076] At step 310 of the flow chart (300), on detecting that the reset
5 request is received from the EMS, the NF module (208) may check for non-zero counters from the plurality of call flow counters. The non-zero counters indicate ongoing call flow.
[0077] At step 312 of the flow chart (300), the NF module (208) may store
the non-zero counters from the plurality of call flow counters.
10 [0078] At step 314 of the flow chart (300), the NF module (208) may reset
remaining counters other than the non-zero counters from the plurality of call flow counters.
[0079] At step 316 of the flow chart (300), the NF module (208) may raise
conditional alarm when the predefined threshold is reached for the one or more
15 conditional alarms.
[0080] In an aspect, a plurality of categories is defined for the one or more
conditional alarms based on the predefined threshold value. The plurality of categories for the plurality of conditional alarms include warning, major, and critical.
20 [0081] Referring to FIG. 4, a flow diagram of a method (400) for
managing conditional alarms in the wireless network is illustrated, in accordance with an embodiment of the present disclosure. The method (400), at step 402 includes maintaining a plurality of call flow counters defined for one or more conditional alarms. The one or more conditional alarms identify a plurality of
25 abnormal conditions. The plurality of abnormal conditions include a system overload, a memory overload, a congestion risk, a system failure, a network failure, and an endpoint unreachability.
[0082] The method (400), at step 404 includes monitoring the plurality of
call flow counters for the one or more conditional alarms. Each of the one or more
30 conditional alarms is configured with a predefined threshold value.
[0083] The method (400), at step 406 includes detecting a reset request
18

from an event management system (EMS). Upon detecting the reset request from
the EMS, the method (400), at step 408 includes checking for non-zero counters
from the plurality of call flow counters. The non-zero counters indicate one of
ongoing call flows or unresolved events.
5 [0084] The method (400), at step 410 includes storing the non-zero
counters that are relevant for the one or more conditional alarms to prevent the non-zero counters from being reset.
[0085] The method (400), at step 412 includes resetting remaining
counters other than the non-zero counters. In some embodiments, the method
10 (400) includes preventing the reset of non-zero counters corresponding to the
ongoing call flows upon receiving the reset request from the EMS.
[0086] The method (400), at step 414 includes raising the one or more
conditional alarms when the stored non-zero counters reach the predefined threshold value. In some embodiments, the one or more conditional alarms are
15 categorized into a plurality of categories based on the predefined threshold value. The plurality of categories for the one or more conditional alarms includes warning, major, and critical.
[0087] FIG. 5 illustrates an exemplary computer system (500) in which or
with which embodiments of the present disclosure may be implemented.
20 [0088] As shown in FIG. 5, the computer system (500) may include an
external storage device (510), a bus (520), a main memory (530), a read only memory (540), a mass storage device (550), a communication port (560), and a processor (570). A person skilled in the art will appreciate that the computer system (500) may include more than one processor (570) and communication
25 ports (560). Processor (570) may include various modules associated with embodiments of the present disclosure.
[0089] In an embodiment, the communication port (560) may be any of an
RS-232 port for use with a modem-based dialup connection, a 10/100 Ethernet port, a Gigabit or 10 Gigabit port using copper or fiber, a serial port, a parallel
30 port, or other existing or future ports. The communication port (560) may be chosen depending on a network, such a Local Area Network (LAN), Wide Area
19

Network (WAN), or any network to which the computer system (500) connects.
[0090] In an embodiment, the memory (530) may be Random Access
Memory (RAM), or any other dynamic storage device commonly known in the art. Read-only memory (540) may be any static storage device(s) e.g., but not 5 limited to, a Programmable Read Only Memory (PROM) chips for storing static information e.g., start-up or Basic Input/Output System (BIOS) instructions for the processor (570).
[0091] In an embodiment, the mass storage (550) may be any current or
future mass storage solution, which may be used to store information and/or
10 instructions. Exemplary mass storage solutions include, but are not limited to, Parallel Advanced Technology Attachment (PATA) or Serial Advanced Technology Attachment (SATA) hard disk drives or solid-state drives (internal or external, e.g., having Universal Serial Bus (USB) and/or Firewire interfaces), one or more optical discs, Redundant Array of Independent Disks (RAID) storage,
15 e.g., an array of disks (e.g., SATA arrays).
[0092] In an embodiment, the bus (520) communicatively couples the
processor(s) (570) with the other memory, storage and communication blocks. The bus (520) may be, e.g., a Peripheral Component Interconnect (PCI)/PCI Extended (PCI-X) bus, Small Computer System Interface (SCSI), Universal Serial
20 Bus (USB) or the like, for connecting expansion cards, drives and other subsystems as well as other buses, such a front side bus (FSB), which connects the processor (470) to the computer system (500).
[0093] Optionally, operator and administrative interfaces, e.g., a display,
keyboard, joystick, and a cursor control device, may also be coupled to the bus
25 (520) to support direct operator interaction with the computer system (500). Other operator and administrative interfaces may be provided through network connections connected through the communication port (560). Components described above are meant only to exemplify various possibilities. In no way should the aforementioned exemplary computer system (500) limit the scope of
30 the present disclosure.
[0094] The present disclosure provides technical advancement related to
20

managing conditional alarm in the wireless network. This advancement addresses the limitations of existing solutions by ensuring the consistency and reliability of conditional alarms despite external reset triggers from the EMS. The disclosure involves maintaining and monitoring call flow counters, detecting EMS reset requests, storing relevant non-zero counters, and raising conditional alarms based on predefined threshold values, which offer significant improvements in data consistency and early failure detection. By implementing an enhanced mechanism to retain critical counters for conditional alarms, the present disclosure enhances the monitoring and alerting functions of the network function, resulting in improved system reliability, early detection of potential failures, and timely intervention to prevent severe network issues.
[0095] While the foregoing describes various embodiments of the present
disclosure, other and further embodiments of the present disclosure may be devised without departing from the basic scope thereof. The scope of the present disclosure is determined by the claims that follow. The present disclosure is not limited to the described embodiments, versions or examples, which are included to enable a person having ordinary skill in the art to make and use the present disclosure when combined with information and knowledge available to the person having ordinary skill in the art.
ADVANTAGES OF THE PRESENT DISCLOSURE
[0096] The present disclosure provides a system and a method to manage
conditional alarms in the wireless network.
[0097] The present disclosure monitors counters for the conditional
alarms.
[0098] The present disclosure stores counters which are used for raising
conditional alarms, and reset other counters, thereby ensuring that the conditional
alarms are raised at a proper threshold value in order to prevent system failure.
[0099] The present disclosure describes failure conditions in the system
which helps in recovering possible failure scenario from the system end.
[00100] The present disclosure ensures data consistency by enabling the NF

to continuously monitor counters useful for raising conditional alarms irrespective
of triggers from the EMS.
[00101] The present disclosure provides prior recovery from failover by
storing required counters that are useful for conditional alarms. These conditional
alarms detect failure scenarios, such as endpoint unreachability or system
overload conditions, providing early warnings to the system. This allows timely
measures to be taken to avoid complete failover.
[00102] The present disclosure improves the system reliability by
maintaining and monitoring critical counters even during EMS-triggered resets.
This approach ensures reliable alarm generation and helps in maintaining the
overall system performance.

We Claim:
1. A method (400) for managing conditional alarms in a wireless network,
the method (400) comprising:
maintaining (402), by a network function (NF) module (208), a plurality of call flow counters defined for one or more conditional alarms, wherein the one or more conditional alarms identify a plurality of abnormal conditions;
monitoring (404), by the NF module (208), the plurality of call flow counters for the one or more conditional alarms, wherein each of the one or more conditional alarms is configured with a predefined threshold value;
detecting (406), by the NF module (208), a reset request from an event management system (EMS);
upon detecting the reset request from the EMS, checking (408), by the NF module (208), for non-zero counters from the plurality of call flow counters, wherein the non-zero counters indicate one of ongoing call flows or unresolved events;
storing (410), by the NF module (208), the non-zero counters that are relevant for the one or more conditional alarms to prevent the non-zero counters from being reset;
resetting (412), by the NF module (208), remaining counters other than the non-zero counters; and
raising (414), by the NF module (208), the one or more conditional alarms when the stored non-zero counters reach the predefined threshold value.
2. The method (400) as claimed in claim 1, wherein the plurality of abnormal
conditions comprises a system overload, a memory overload, a congestion
risk, a system failure, a network failure, and an endpoint unreachability.

3. The method (400) as claimed in claim 1, wherein the one or more conditional alarms are categorized into a plurality of categories based on the predefined threshold value.
4. The method (400) as claimed in claim 3, wherein the plurality of categories for the one or more conditional alarms comprises warning, major, and critical.
5. The method (400) as claimed in claim 1, further comprising preventing the reset of non-zero counters corresponding to the ongoing call flows upon receiving the reset request from the EMS.
6. A system (108) for managing conditional alarms in a wireless network, the system (108) comprising:
a server (110);
a network function (NF) module (208) within the server (110); a memory (204); and
one or more processor(s) (202) communicatively coupled with the memory (202), configured to:
maintain a plurality of call flow counters defined for one or more conditional alarms, wherein the one or more conditional alarms identify a plurality of abnormal conditions;
monitor the plurality of call flow counters for the one or more conditional alarms, wherein each of the one or more conditional alarms is configured with a predefined threshold value;
detect a reset request from an event management system (EMS);
upon detection of the reset request from the EMS, check for non-zero counters from the plurality of call flow counters, wherein the non-zero counters indicate one of ongoing call flows or unresolved events;

store the non-zero counters that are relevant for the one or more conditional alarms to prevent the non-zero counters from being reset;
reset remaining counters other than the non-zero counters; and
raise the one or more conditional alarms when the stored non-zero counters reach the predefined threshold value.
7. The system (108) as claimed in claim 6, wherein the plurality of abnormal conditions comprises a system overload, a memory overload, a congestion risk, a system failure, a network failure, and an endpoint unreachability.
8. The system (108) as claimed in claim 6, wherein the one or more conditional alarms are categorized into a plurality of categories based on the predefined threshold value.
9. The system (108) as claimed in claim 8, wherein the plurality of categories for the one or more conditional alarms comprises warning, major, and critical.
10. The system (108) as claimed in claim 6, wherein the one or more processor(s) (202) is configured to prevent the reset of non-zero counters corresponding to the ongoing call flows upon receiving the reset request from the EMS.
11. A network function (NF) module (208) for managing conditional alarms in a wireless network, the NF module (208) is configured to:
maintain a plurality of call flow counters defined for one or more conditional alarms, wherein the one or more conditional alarms identify a plurality of abnormal conditions;

monitor the plurality of call flow counters for the one or more conditional alarms, wherein each of the one or more conditional alarms is configured with a predefined threshold value;
detect a reset request from an event management system (EMS);
upon detection of the reset request from the EMS, check for non¬zero counters from the plurality of call flow counters, wherein the non¬zero counters indicate one of ongoing call flows or unresolved events;
store the non-zero counters that are relevant for the one or more conditional alarms to prevent the non-zero counters from being reset;
reset remaining counters other than the non-zero counters; and
raise the one or more conditional alarms when the stored non-zero counters reach the predefined threshold value.
12. The NF module (208) as claimed in claim 11, wherein the plurality of abnormal conditions comprises a system overload, a memory overload, a congestion risk, a system failure, a network failure, and an endpoint unreachability.
13. The NF module (208) as claimed in claim 11, wherein the one or more conditional alarms are categorized into a plurality of categories based on the predefined threshold value.
14. The NF module (208) as claimed in claim 13, wherein the plurality of categories for the one or more conditional alarms comprises warning, major, and critical.
15. The NF module (208) as claimed in claim 13, is further configured to prevent the reset of non-zero counters corresponding to the ongoing call flows upon receiving the reset request from the EMS.

16. A user equipment (104) communicatively coupled with a network (106), the coupling comprises steps of:
receiving, by the network (106), a connection request;
sending an acknowledgment of the connection request to the UE (104); and
transmitting a plurality of signals in response to the connection request, wherein the network (106) comprising a network function (NF) module (208) performing a method for managing conditional alarms in a wireless network as claimed in claim 1.