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 MANAGING TRAPS IN A COMMUNICATION NETWORK”
We, Jio Platforms Limited, an Indian National, of Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India.
The following specification particularly describes the invention and the manner in which it is to be performed.

METHOD AND SYSTEM FOR MANAGING TRAPS IN A COMMUNICATION NETWORK
FIELD OF INVENTION
[0001] Embodiments of the present disclosure generally relate to wireless communication systems. More particularly, embodiments of the present disclosure relate to method and system for managing traps in a communication network.
BACKGROUND OF THE DISCLOSURE
[0002] The following description of the 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 is used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of the prior art.
[0003] Wireless communication technology has rapidly evolved over the past few decades, with each generation bringing significant improvements and advancements. The first generation of wireless communication technology was based on analog technology and offered only voice services. However, with the advent of the second generation (2G) technology, digital communication and data services became possible, and text messaging was introduced. The third generation (3G) technology marked the introduction of high-speed internet access, mobile video calling, and location-based services. The fourth generation (4G) technology revolutionized wireless communication with faster data speeds, better network coverage, and improved security. Currently, the fifth generation (5G) technology is being deployed, promising even faster data speeds, low latency, and the ability to connect multiple devices simultaneously. With each generation, wireless

communication technology has become more advanced, sophisticated, and capable of delivering more services to its users.
[0004] A Network Management System (NMS) in a communication network refers to a set of software and hardware tools used by network operators to monitor, control, and manage communications network. The NMS may be responsible for monitoring and supervision of network elements, faults or abnormalities detection and diagnosis in the network, configuration management, security management, performance management, etc. In NMS, for any event that happens on any network node or network device such as a router, a gateway, a switch and the like, a network manager needs to know for monitoring operation of network communication. The event information may be sent to the network manager in form of any notification or alert. Network devices and/or nodes are also configured to monitor their activity, health status and other parameters, and send alerts to network manager or another relevant network component. For these alerts, conditions may be unusual activity(ies), failure(s), state change(s) and/or the like. These alerts or notifications and/or alarms are also called as traps.
[0005] In network management system (NMS), number of alarms/traps consumed by a fault processor (FP) for raising or clearing in a second is called transactions per second (TPS). Sometimes the TPS is stable and less in number, whereas at some other times the TPS shoots up to large number. In existing solutions, the FP is used to process all the consumed alarms in a continuous sequence. Many of these alarms may be undesirable or less important for monitoring and reporting to the network manager. This unnecessarily consumes network resources, which results in greater computational processing, and higher time consumption, and accordingly has no economic significance.
[0006] Thus, there exists an imperative need in the art to provide a solution for managing traps in a communication network, which the present disclosure aims to address.

SUMMARY OF THE DISCLOSURE
[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 managing one or more traps in a communication network. The method comprises receiving, by a transceiver unit at a collector module, one or more traps from one or more nodes of the communication network, the one or more traps comprising one or more trap attributes and a node identifier. Further, the method comprises generating, by a generator unit at the collector module, one or more final trap attributes by adding one or more additional trap attributes to the one or more trap attributes of the one or more traps. Further, the method comprises matching, by a matching unit at the collector module, one or more final trap attributes for each node identifier with at least one of one or more attributes for each node identifier provisioned in a set of blacklisting data and one or more attributes for each node identifier provisioned in a set of whitelisting data. Further, the method comprises tagging, by a tagging unit at the collector module, one or more traps as one of a blacklisted tag and a whitelisted tag based on the matching. Further, the method comprises managing, by a managing unit at the collector module, the one or more traps based on the tagging.
[0009] In an exemplary aspect of the present disclosure, the method further comprises receiving, by the transceiver unit, at least one trap with one or more missing attributes.
[0010] In an exemplary aspect of the present disclosure, the one or more missing attributes are fetched from a pre-defined dictionary stored by a network management entity in the communication network.

[0011] In an exemplary aspect of the present disclosure, the method further comprises discarding, by a discarding unit at the collector module, at least one of the one or more traps tagged as the blacklisted tag.
[0012] In an exemplary aspect of the present disclosure, the method further comprises transmitting, by the transceiver unit at the collector module, one or more alarms corresponding to one or more whitelisted traps to a fault processor.
[0013] In an exemplary aspect of the present disclosure, the method further comprises provisioning, by a user interface at the collector module, the set of blacklisting data comprising one or more node identifiers and one or more trap attributes for each of the one or more node identifiers.
[0014] In an exemplary aspect of the present disclosure, the method further comprises provisioning, by the user interface at the collector module, the set of whitelisting data comprising one or more node identifiers and one or more trap attributes for each of the one or more node identifiers.
[0015] Another aspect of the present disclosure may relate to a system for managing one or more traps in a communication network. The system comprises a collector module. The collector module further comprises a transceiver unit configured to receive one or more traps from one or more nodes of the communication network, the one or more traps comprising one or more trap attributes and a node identifier. The collector module further comprises a generator unit connected to at least the transceiver unit. The generator unit is configured to generate one or more final traps by adding one or more additional trap attributes to the one or more trap attributes of the one or more traps. The collector module further comprises a matching unit connected to at least the generator unit. The matching unit is configured to match one or more final trap attributes for each node identifier with at least one of one or more attributes for each node identifier provisioned in a

set of blacklisting data and one or more attributes for each node identifier provisioned in a set of whitelisting data. The collector module further comprises a tagging unit connected to at least the matching unit. The tagging unit is configured to tag one or more traps as one of a blacklisted tag and a whitelisted tag based on the matching. The collector module further comprises a managing unit connected to at least the tagging unit. The managing unit is configured to manage the one or more traps based on the tagging.
[0016] Yet another aspect of the present disclosure may relate to a non-transitory computer readable storage medium storing instruction for managing one or more traps in a communication network. The instructions include executable code. The executable code when executed by one or more units of a system comprising a collector module, causes a transceiver unit of the collector module to receive one or more traps from one or more nodes of the communication network, the one or more traps comprising one or more trap attributes and a node identifier. Further, executable code when executed, causes a generator unit of the collector module to generate one or more final traps by adding one or more additional trap attributes to the one or more trap attributes of the one or more traps. Further, executable code when executed, causes a matching unit of the collector module to match one or more final trap attributes for each node identifier with at least one of one or more attributes for each node identifier provisioned in a set of blacklisting data and one or more attributes for each node identifier provisioned in a set of whitelisting data. Further, executable code when executed, causes a tagging unit of the collector module to tag one or more traps as one of a blacklisted tag and a whitelisted tag based on the matching. Further, executable code when executed, causes a managing unit of the collector module to manage the one or more traps based on the tagging.
[0017] Yet another aspect of the present disclosure may relate to a user equipment (UE). The UE comprises at least a transmitter unit configured to send to a system comprising a collector module, a request for receiving an indication related to managing one or more traps in a communication network. Further, the UE

comprises at least a receiver unit configured to receive, from the system, the
indication in response to the request. The one or more traps in the communication
network are managed based on receiving, by a transceiver unit at the collector
module, one or more traps from one or more nodes of the communication network,
5 the one or more traps comprising one or more trap attributes and a node identifier.
Further, the one or more traps are managed based on generating, by a generator unit at the collector module, one or more final trap attributes by adding one or more additional trap attributes to the one or more trap attributes of the one or more traps. Further, the one or more traps are managed based on matching, by a matching unit
10 at the collector module, one or more final trap attributes for each node identifier
with at least one of one or more attributes for each node identifier provisioned in a set of blacklisting data and one or more attributes for each node identifier provisioned in a set of whitelisting data. Further, the one or more traps are managed based on tagging, by a tagging unit at the collector module, one or more traps as
15 one of a blacklisted tag and a whitelisted tag based on the matching. Further, the
one or more traps are managed based on managing, by a managing unit at the collector module, the one or more traps based on the tagging.
OBJECTS OF THE INVENTION
20
[0018] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.
[0019] It is an object of the present disclosure to provide a system and a method for
25 blacklisting and/or whitelisting a plurality of traps received from one or more nodes
of a wireless communication system.
[0020] It is another object of the present disclosure to provide a system and a
method that supports expression-based segregation as well as match-based
30 segregation of blacklisted or whitelisted traps.
7

[0021] It is yet another object of the present disclosure to provide a dictionary profile and translation profile that is configurable in runtime.
[0022] It is yet another object of the present disclosure to provide a solution that
5 facilitates addition and dynamic modification of traps based on a trap value to form
a generic alarm.
[0023] It is yet another object of the present disclosure to provide a mechanism for identification and association of raise trap /clear trap that is configurable in runtime. 10
DESCRIPTION OF THE DRAWINGS
[0024] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods
15 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. Also, the embodiments shown in the figures are not to be construed as limiting the disclosure, but the possible variants of the method and system
20 according to the disclosure are illustrated herein to highlight the advantages of the
disclosure. It will be appreciated by those skilled in the art that disclosure of such drawings includes disclosure of electrical components or circuitry commonly used to implement such components.
25 [0025] 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.
[0026] FIG. 2 illustrates an exemplary block diagram of a system for managing one
30 or more traps in a communication network, in accordance with exemplary
implementations of the present disclosure.
8

[0027] FIG. 3 illustrates a method flow diagram for managing one or more traps in a communication network, in accordance with exemplary implementations of the present disclosure. 5
[0028] FIG. 4 illustrates an exemplary blacklisting procedure, in accordance with exemplary implementations of the present disclosure.
[0029] FIG. 5 illustrates an exemplary whitelisting procedure, in accordance with
10 exemplary implementations of the present disclosure.
[0030] FIG. 6 illustrates an exemplary method flow for adding missing attributes from pre-defined dictionary, in accordance with exemplary implementations of the present disclosure. 15
[0031] The foregoing shall be more apparent from the following more detailed description of the disclosure.
DETAILED DESCRIPTION
20
[0032] In the following description, for the purposes of explanation, various 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
25 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 address any of the problems discussed above or might address only some of the problems discussed above.
30 [0033] The ensuing description provides exemplary embodiments only, and is not
intended to limit the scope, applicability, or configuration of the disclosure. Rather,
9

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
5 disclosure as set forth.
[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
10 specific details. For example, circuits, systems, processes, and other components
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
15 which is depicted as a flowchart, a flow diagram, a data flow diagram, a structure
diagram, or a block diagram. Although a flowchart may describe the operations as
a sequential process, many of the operations 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
20 included in a figure.
[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
25 aspect or design described herein as “exemplary” and/or “demonstrative” is not
necessarily to be construed as preferred or advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques 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
30 description or the claims, such terms are intended to be inclusive in a manner similar
10

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”
5 includes one or more processors, wherein processor refers to any logic circuitry for
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
10 Integrated Circuits, Field Programmable Gate Array circuits, any other type of
integrated circuits, etc. The processor may perform signal coding data processing, input/output processing, and/or any other functionality that enables the working of the system according to the present disclosure. More specifically, the processor or processing unit is a hardware processor.
15
[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
20 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 one or more features of the present disclosure. Also, the user
25 device may contain at least one input means configured to receive an input from
unit(s) which are required to implement the one or more features of the present disclosure.
[0039] As used herein, “storage unit” or “memory unit” refers to a machine or
30 computer-readable medium including any mechanism for storing information in a
form readable by a computer or similar machine. For example, a computer-readable
11

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
that may be required by one or more units of the system to perform their respective
5 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
or data. The interface may also be referred to a set of rules or protocols that define
10 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.
[0041] All modules, units, components used herein, unless explicitly excluded
15 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
microprocessors in association with a DSP core, a controller, a microcontroller,
Application Specific Integrated Circuits (ASIC), Field Programmable Gate Array
20 circuits (FPGA), any other type of integrated circuits, etc.
[0042] As used herein, the transceiver unit include at least one receiver and at least
one transmitter configured respectively for receiving and transmitting data, signals,
information or a combination thereof between units/components within the system
25 and/or connected with the system.
[0043] As used herein, the ‘traps’ refer to notification messages generated by
network devices (such as routers, switches, servers, etc.) to indicate events like, but
not limited to, system errors, network faults, performance thresholds exceeded,
30 configuration changes, and security breaches.
12

[0044] As used herein, a ‘raise trap’ refers to an event notification sent by a network
device (like a router, switch, or server) to a network management system (NMS)
(or a monitoring system) when an event (such as a critical error, security breach,
performance issue, etc.) occurs on the network. The raise trap alerts administrators
5 or automated systems so that they can take appropriate actions to investigate and
resolve the issue. Further, as used herein, a ‘clear trap’ is a subsequent notification
that informs the NMS (or monitoring system) that the issue raised previously in a
raise trap has been resolved or cleared. This helps the network administrators to
understand the current status of the network and whether further action is needed
10 or not.
[0045] Further, in accordance with the present disclosure, it is to be acknowledged that the functionality described for the various components/units can be implemented interchangeably. While specific embodiments may disclose a
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.
[0046] As discussed in the background section, the current known solutions have several shortcomings. In the NMS architecture, a collector module acts as a gateway
25 for receiving traps from different nodes. Different nodes may belong to different
vendors. Sometimes, there are cases where the collector module observes huge traffic resulting in high transactions per second (TPS). This high TPS is further responsible for unnecessary processing of alarms in message stream, that are sent to fault processor (FP). This may result in a hang state or unresponsive state or
30 unstable state of databases and/or the fault processor. Also, the FP service must be
stable, and all the alarms must be processed for raise/clear operations/notifications,
13

irrespective of the TPS being high or low. The present disclosure aims to overcome
the above-mentioned and other existing problems in this field of technology by
providing method and system of managing one or more traps in a communication
network. The present solution uses a blacklisting mechanism or whitelisting
5 mechanism for blocking or allowing alarms to message stream and fault processing
service. According to the solution, whenever the collector module receives traps from a node, the collector module fetches blacklisting details or whitelisting details based on a node name/identifier. If the node is found and applicable for blacklisting, then the collector module fetches a blacklisting criteria of the node by applying
10 regular expression based on trap attributes and blocks the alarm to message stream
and fault processing service. Also, if the node is found and applicable for whitelisting, then the collector module fetches a whitelisting criteria of the node by applying regular expression based on trap attributes and allows the alarm to message stream and fault processing service. Also, some nodes send only few trap
15 attributes where the nodes miss few mandatory attributes. For such mandatory
attributes, the NMS maintains a dictionary of pre-defined attributes for configured nodes. NMS extracts its attributes from the dictionary, and streams alarm data to fault processor along with raise/clear trap notification identification.
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] upon which the features of the present disclosure may be implemented in
25 accordance with exemplary implementation of the present disclosure. In an
implementation, the computing device [100] may implement a method for managing one or more traps in a communication network utilising the system of the present disclosure. In another implementation, the computing device [100] itself implements the method for managing one or more traps in a communication
30 network using one or more units configured within the computing device [100],
14

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 hardware
processor [104] coupled with bus [102] for processing information. The hardware
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]
10 for storing information and 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-
15 purpose machine that is 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
cursor movement on the display [112]. This input device typically has two degrees
15

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.
[0051] The computing device [100] may implement the techniques described
5 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 computing device [100] in response to the processor [104] executing one or more
10 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 process steps described herein. In alternative implementations of the present
15 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
[118] coupled to the bus [102]. The communication interface [118] provides a two-
20 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
telephone line. As another example, the communication interface [118] may be a
25 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
various types of information.
30
16

[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
transmit a requested code for an application program through the Internet [128], the
5 ISP [126], the local network [122], the 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] Referring to FIG. 2, an exemplary block diagram of a system [200] for
managing one or more traps in a communication network, is shown, in accordance with the exemplary implementations of the present disclosure. The system [200] comprises at least one collector module [201]. The collector module [201] further comprises at least one transceiver unit [202], at least one generator unit [204], at
15 least one matching unit [206], at least one tagging unit [208], at least one managing
unit [210], at least one discarding unit [212], at least one user interface [214], and a storage unit [216]. Also, all of the components/ units of the system [200] are assumed to be connected to each other unless otherwise indicated below. Also, in Fig. 2 only a few units are shown, however, the system [200] may comprise multiple
20 such 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 reside in a server or a network entity.
[0055] The system [200] is configured for managing one or more traps in a
25 communication network, with the help of the interconnection between the
components/units of the system [200].
[0056] The transceiver unit [202] may receive one or more traps from one or more
nodes of the communication network. Each of the one or more traps may comprise
30 one or more trap attributes and a node identifier. In an implementation, the
transceiver unit [202] may receive at least one trap with one or more missing
17

attributes. The trap attributes may include, but not limited to, trap identifier (ID),
SAP ID, managed node, node type, event time, host name, circle/state, severity
(critical/major/indeterminate/warning/minor), internet protocol (IP) address,
server, bay, RAC number, and alarm type (raise/clear). Here, each node may be
5 associated with one or more traps. For example, a network node, say, a session
management function (SMF) module generates a trap of “power supply failure” and “device health status”. Also, each node is associated with a node identifier, for example, the node identifiers can be internet protocol (IP) addresses, service access point (SAP) identifier, and media access control (MAC) addresses. Continuing with
10 the above example, say the SMF module (i.e., the SMF node) may be identified by
the IP address 19x.15y.z.w (referred to as ‘SMF node’ for ease of reference). A person skilled in the art would appreciate that the above example is provided for understanding purposes only and does not limit or restrict the present disclosure in any possible manner. Also, each trap comprises one or more trap attributes. For
15 example, the one or more trap attributes for power supply failure trap at the SMF
node are operating time of the server of the SMF node, and maximum load capacity of the server of the SMF node etc. Pertinently, the alarms may contain some standardized attributes, which may be referred to as ‘generic alarms’. Also, the traps may originate from various nodes. Hence, the traps from two different node may
20 not contain same attributes. Thus, basis the configured trap attribute values, the
traps may be transformed into generic alarm format. This dynamic modification of configurations may also facilitate effecting the modifications without the restart of service.
25 [0057] The generator unit [204] may be connected to at least the transceiver unit
[202]. The generator unit [204] may generate one or more final trap attributes by adding one or more additional trap attributes to the one or more trap attributes of the one or more traps. In an implementation, the one or more missing attributes may be fetched from the pre-defined dictionary stored by the network management
30 entity in the communication network. These additional trap attributes may be added
for the missing attributes. For this purpose, the pre-defined dictionary is stored by
18

a network management entity (NME, or as used herein, network management
system (NMS)) in the communication network. Thus, in an example, the SMF node
may be a pre-configured node and the mandatory parameters of the SMF node may
be maintained in the pre-defined dictionary. In the above example, where operating
5 time of the server of the SMF node, and maximum load capacity of the server of
the SMF node are the attributes of the power supply failure trap that are received by the transceiver unit [202]. Further, say for example, another attribute, that is, temperature attribute of the SMF node server is a mandatory attribute of the power supply failure trap of the SMF node and is missing in the set of trap attributes
10 received by the transceiver unit [202]. Since the temperature attribute of power
supply failure trap is the mandatory attribute, the temperature attribute for the power supply failure trap may be maintained in the pre-defined dictionary. Thus, the temperature attribute may be fetched from the pre-defined dictionary. A person skilled in the art would appreciate that the above example is provided for
15 understanding purposes only and does not limit or restrict the present disclosure in
any possible manner. The missing attributes may be added to the one or more trap attributes as one or more additional trap attributes to generate one or more final trap attributes. In an implementation, the one or more missing attributes are fetched from the pre-defined dictionary along with an identification of a trap type, i.e., a raise
20 trap or a clear trap. Also, whether the trap is a raise trap or a clear trap, may be
determined using a configured attribute and its associated values. For example, if a trap has an identifier attribute OID XX, and for example, the value of the identifier attribute is A1 then it is a raise trap else if the value is B2 then it is a clear trap. Further, as the nodes may change the identifier attribute, then the suitable change
25 can be applied with an identification of the trap type without the restart of a service.
Also, the additional trap attributes may be added in case a trap translation for the node is also available in the pre-defined dictionary. Here, based on a node configuration, additional trap attributes and their values may be added, for example, trap occurrence count, etc. An exemplary method flow for adding the missing
30 attributes from the pre-defined dictionary is explained in this disclosure with
reference to Fig. 6. Also, in an implementation, the pre-defined dictionary as well
19

as the trap translation may be configurable in runtime. For avoiding application restart, a cache refresh of service may be available in order to update the service with latest data added / modified in runtime with use of configuration files.
5 [0058] The matching unit [206] may be connected to at least the generator unit
[204]. The matching unit [206] may match the one or more final trap attributes for each node identifier with at least one of one or more attributes for each node identifier provisioned in a set of blacklisting data and one or more attributes for each node identifier provisioned in a set of whitelisting data. Here, the blacklisting
10 data refers to a data comprising one or more trap attributes associated with a node
identifier which are to be blacklisted, meaning that these final attributes of the node may not be considered for forwarding in the message stream and/or the fault processing service. Also, the whitelisting data refers to a data comprising one or more trap attributes associated with a node identifier which are to be whitelisted,
15 meaning that these final attributes of the node may be forwarded in the message
stream and/or the fault processing service. The blacklisting data and the whitelisting data, in an implementation, may be stored in the storage unit [216]. Continuing with the above example, say the final attributes of the power supply failure trap of the SMF node are the operating time of the server of the SMF node, the maximum load
20 capacity of the server of the SMF node, and the temperature of the server of the
SMF node. The matching unit [206] may match the final trap attributes with one or more attributes for each node identifier provisioned in a set of blacklisting data and/or the one or more attributes for each node identifier provisioned in a set of whitelisting data. In the above example, the final trap attributes of the power supply
25 failure trap (i.e., the operating time of the server of the SMF node, the maximum
load capacity of the server of the SMF node, and the temperature of the server of the SMF node) are matched in at least one of the blacklisting data and the whitelisting data. In an implementation, based on the node identifier, a set of blacklisting details or a set of whitelisting details may be fetched. For example, if
30 the node identifier of a node suggests that the traps related to the node identifier are
to be blocked for message stream and/or FP service, then the final trap attributes
20

are matched only in the blacklisting data, and if the node identifier of a node
suggests that the traps related to the node identifier are to be allowed for message
stream and/or FP service, then the final trap attributes are matched only in the
whitelisting data. In an implementation, the set of blacklisting details may be
5 fetched for implementing a blacklisting procedure, and the set of whitelisting details
may be fetched for implementing a whitelisting procedure. An exemplary blacklisting procedure is described in this disclosure with reference to Fig. 4. Also, an exemplary whitelisting procedure is described in this disclosure with reference to Fig. 5. Continuing with the above example, say the SMF node identifier (i.e.,
10 19x.15y.z.w) suggests that the traps for this SMF node are to be allowed, then the
final traps are matched in the whitelisting data. In case the final traps are found and/or match the one or more attributes for the SMF node identifier provisioned in the whitelisting data, then the node may further be tagged accordingly with a whitelisted tag. A person skilled in the art would appreciate that the above example
15 is provided for understanding purposes only and does not limit or restrict the present
disclosure in any possible manner. Also, in an implementation, the collector module [201] comprises a user interface [214]. In an implementation, the user interface [214] may be used to provision the blacklisting data comprising one or more node identifiers and one or more attributes for each of the one or more node identifiers.
20 Further, in an implementation, the user interface [214] may be used to provision the
whitelisting data comprising one or more node identifiers and one or more attributes for each of the one or more node identifiers.
[0059] The tagging unit [208] is connected to at least the matching unit [206]. The
25 tagging unit [208] may tag the one or more traps as one of a blacklisted tag and a
whitelisted tag based on the matching.
[0060] The managing unit [210] is connected to at least the tagging unit [208]. The
managing unit [210] may manage the one or more traps based on tagging. For this
30 purpose, based on the tagging, a blacklisting criteria or a whitelisting criteria may
be fetched by the managing unit [210]. That is, the managing unit [210] fetches the
21

blacklisting criteria in case the trap is tagged with a blacklisted tag, and the
managing unit [210] fetches the whitelisting criteria in case the trap is tagged with
a whitelisted tag. Pertinently, some nodes traps need to be blacklisted (i.e., trap
occurrence can be ignored for these blacklisted nodes), so that it facilitates avoiding
5 extra data processing and resources wastage. The blacklisting criteria or the
whitelisting criteria may be fetched by the managing unit [210] by applying a
regular expression and at least one of the one or more final trap attributes of the
trap. Here, the regular expression refers to a regex function as generally known in
the art (for example: “(^(?)-DEL_(?))”). The regular expression may be used here
10 to match a pattern of values of the one or more final trap attributes of the trap. Also,
for matching any particular trap attribute value, a match-based expression may be used. If a match is found, a criteria (i.e., the blacklisting criteria or the whitelisting criteria) is considered met.
15 [0061] Further, in an implementation, the collector module [201] comprises a
discarding unit [212]. The discarding unit [212] may discard at least one of the one or more traps tagged as the blacklisted tag. Here, for example, a trap is tagged with the blacklisted tag, then the trap is discarded, i.e., blocked from getting forwarded in the message stream and/or the fault processor service. Further, in an
20 implementation, the transceiver unit [202] may transmit one or more alarms
corresponding to one or more whitelisted traps to a fault processor. Here, for example, a trap is tagged with the whitelisted tag, then the trap is allowed, i.e., forwarded in the message stream and/or the fault processor service. A person skilled in the art would appreciate that the above example(s) are provided for understanding
25 purposes only and do not limit or restrict the present disclosure in any possible
manner.
[0062] Referring to FIG. 3, an exemplary method flow diagram [300] for managing
one or more traps in a communication network, in accordance with exemplary
30 implementations of the present disclosure is shown. In an implementation the
22

method [300] is performed by the system [200]. Also, as shown in Fig. 3, the method [300] starts at step [302].
[0063] At step 302, the method comprises receiving, by a transceiver unit [202] at
5 a collector module [201], one or more traps from one or more nodes of the
communication network, the one or more traps comprising one or more trap attributes and a node identifier. In an implementation, the method further comprises receiving, by the transceiver unit [202], at least one trap with one or more missing attributes. The trap attributes may include, but not limited to, trap identifier (ID),
10 SAP ID, managed node, node type, event time, host name, circle/state, severity
(critical/major/indeterminate/warning/minor), internet protocol (IP) address, server, bay, RAC number, and alarm type (raise/clear). Here, each node may be associated with one or more traps. For example, a network node, say, a session management function (SMF) module generates a trap of “power supply failure” and
15 “device health status”. Also, each node is associated with a node identifier, for
example, the node identifiers can be internet protocol (IP) addresses and media access control (MAC) addresses. Continuing with the above example, say the SMF module (i.e., the SMF node) may be identified by the IP address 19x.15y.z.w (referred to as ‘SMF node’ for ease of reference). A person skilled in the art would
20 appreciate that the above example is provided for understanding purposes only and
does not limit or restrict the present disclosure in any possible manner. Also, each trap comprises one or more trap attributes. For example, the one or more trap attributes for power supply failure trap at the SMF node are operating time of the server of the SMF node, and maximum load capacity of the server of the SMF node
25 etc.
[0064] At step 304, the method comprises generating, by a generator unit [204] at
the collector module [201], one or more final trap attributes by adding one or more
additional trap attributes to the one or more trap attributes of the one or more traps.
30 In an implementation, the one or more missing attributes may be fetched from the
pre-defined dictionary stored by the network management entity in the
23

communication network. These additional trap attributes may be added for the
missing attributes. For this purpose, the pre-defined dictionary is stored by a
network management entity (NME, or as used herein, network management system
(NMS)) in the communication network. Thus, in an example, the SMF node may
5 be a pre-configured node and the mandatory parameters of the SMF node may be
maintained in the pre-defined dictionary. In the above example, where operating time of the server of the SMF node, and maximum load capacity of the server of the SMF node are the attributes of the power supply failure trap that are received by the transceiver unit [202]. Further, say for example, another attribute, that is,
10 temperature attribute of the SMF node server is a mandatory attribute of the power
supply failure trap of the SMF node and is missing in the set of trap attributes received by the transceiver unit [202]. Since the temperature attribute of power supply failure trap is the mandatory attribute, the temperature attribute for the power supply failure trap may be maintained in the pre-defined dictionary. Thus, the
15 temperature attribute may be fetched from the pre-defined dictionary. A person
skilled in the art would appreciate that the above example is provided for understanding purposes only and does not limit or restrict the present disclosure in any possible manner. The missing attributes may be added to the one or more trap attributes as one or more additional trap attributes to generate one or more final trap
20 attributes. In an implementation, the one or more missing attributes are fetched from
the pre-defined dictionary along with an identification of a trap type, i.e., a raise trap or a clear trap. Also, the additional trap attributes may be added in case a trap translation for the node is also available in the pre-defined dictionary. An exemplary method flow for adding the missing attributes from the pre-defined dictionary is
25 explained in this disclosure with reference to Fig. 6.
[0065] At step 306, the method comprises matching, by a matching unit [206] at
the collector module [201], the one or more final trap attributes for each node
identifier with at least one of one or more attributes for each node identifier
30 provisioned in a set of blacklisting data and one or more attributes for each node
identifier provisioned in a set of whitelisting data. Here, the blacklisting data refers
24

to a data comprising one or more trap attributes associated with a node identifier
which are to be blacklisted, meaning that these final attributes of the node may not
be considered for forwarding in the message stream and/or the fault processing
service. Also, the whitelisting data refers to a data comprising one or more trap
5 attributes associated with a node identifier which are to be whitelisted, meaning that
these final attributes of the node may be forwarded in the message stream and/or the fault processing service. The blacklisting data and the whitelisting data, in an implementation, may be stored in the storage unit [216]. Continuing with the above example, say the final attributes of the power supply failure trap of the SMF node
10 are the operating time of the server of the SMF node, the maximum load capacity
of the server of the SMF node, and the temperature of the server of the SMF node. The matching unit [206] may match the final trap attributes with one or more attributes for each node identifier provisioned in a set of blacklisting data and/or the one or more attributes for each node identifier provisioned in a set of whitelisting
15 data. In the above example, the final trap attributes of the power supply failure trap
(i.e., the operating time of the server of the SMF node, the maximum load capacity of the server of the SMF node, and the temperature of the server of the SMF node) are matched in at least one of the blacklisting data and the whitelisting data. In an implementation, based on the node identifier, a set of blacklisting details or a set of
20 whitelisting details may be fetched. For example, if the node identifier of a node
suggests that the traps related to the node identifier are to be blocked for message stream and/or FP service, then the final trap attributes are matched only in the blacklisting data, and if the node identifier of a node suggests that the traps related to the node identifier are to be allowed for message stream and/or FP service, then
25 the final trap attributes are matched only in the whitelisting data. In an
implementation, the set of blacklisting details may be fetched for implementing a blacklisting procedure, and the set of whitelisting details may be fetched for implementing a whitelisting procedure. An exemplary blacklisting procedure is described in this disclosure with reference to Fig. 4. Also, an exemplary whitelisting
30 procedure is described in this disclosure with reference to Fig. 5. Continuing with
the above example, say the SMF node identifier (i.e., 19x.15y.z.w) suggests that the
25

traps for this SMF node are to be allowed, then the final traps are matched in the
whitelisting data. In case the final traps are found and/or match the one or more
attributes for the SMF node identifier provisioned in the whitelisting data, then the
node may further be tagged accordingly with a whitelisted tag. A person skilled in
5 the art would appreciate that the above example is provided for understanding
purposes only and does not limit or restrict the present disclosure in any possible
manner. Also, in an implementation, the method further comprises provisioning, by
a user interface [214] at the collector module [201], the set of blacklisting data
comprising one or more node identifiers and one or more trap attributes for each of
10 the one or more node identifiers. Further, in an implementation, the method further
comprises provisioning, by a user interface [214] at the collector module [201], the set of whitelisting data comprising one or more node identifiers and one or more trap attributes for each of the one or more node identifiers.
15 [0066] At step 308, the method comprises tagging, by a tagging unit [208] at the
collector module [201], the one or more traps as one of a blacklisted tag and a whitelisted tag based on the matching.
[0067] At step 310, the method comprises managing, by a managing unit [210] at
20 the collector module [201], the one or more traps based on tagging. For this purpose,
based on the tagging, a blacklisting criteria or a whitelisting criteria may be fetched
by the managing unit [210]. That is, the managing unit [210] fetches the blacklisting
criteria in case the trap is tagged with a blacklisted tag, and the managing unit [210]
fetches the whitelisting criteria in case the trap is tagged with a whitelisted tag. This
25 blacklisting criteria or the whitelisting criteria may be fetched by the managing unit
[210] by applying a regular expression and at least one of the one or more final trap attributes of the trap.
[0068] Further, in an implementation, the method further comprises discarding, by
30 a discarding unit [212] at the collector module [201], at least one of the one or more
traps tagged as the blacklisted tag. Here, for example, a trap is tagged with the
26

blacklisted tag, then the trap is discarded, i.e., blocked from getting forwarded in
the message stream and/or the fault processor service. Further, in an
implementation, the method further comprising transmitting, by the transceiver unit
[202] at the collector module [201], one or more alarms corresponding to one or
5 more whitelisted traps to a fault processor. Here, for example, a trap is tagged with
the whitelisted tag, then the trap is allowed, i.e., forwarded in the message stream and/or the fault processor service. A person skilled in the art would appreciate that the above example(s) are provided for understanding purposes only and do not limit or restrict the present disclosure in any possible manner.
10
[0069] Referring to FIG. 4, which illustrates an exemplary blacklisting procedure, in accordance with exemplary implementations of the present disclosure. As shown in block 402, a node sends one or more traps to a collector module shown in block 404. Further, as shown in block 406, it is checked whether the trap is eligible for
15 blacklisting. If it is found that single or multiple attributes combination (i.e., one or
more trap attributes) matches a blacklisting data at block 408, then the alarms are blocked/blacklisted as shown in block 410. If it is found that single or multiple attributes combination (i.e., one or more trap attributes) does not match a blacklisting data at block 408, then the alarms are allowed and forwarded in the
20 message stream as shown in block 412. Further, the alarms are forwarded to the
fault processor as shown in block 414.
[0070] Referring to FIG. 5, which illustrates an exemplary whitelisting procedure, in accordance with exemplary implementations of the present disclosure. As shown
25 in block 502, a node sends one or more traps to a collector module shown in block
504. Further, as shown in block 506, it is checked whether the trap is eligible for whitelisting. If it is found that single or multiple attributes combination (i.e., one or more trap attributes) does not match a whitelisting data at block 508, then the alarms are blocked/blacklisted as shown in block 510. If it is found that single or multiple
30 attributes combination (i.e., one or more trap attributes) matches a whitelisting data
at block 508, then the alarms are allowed and forwarded in the message stream as
27

shown in block 512. Further, the alarms are forwarded to the fault processor as shown in block 514.
[0071] Referring to FIG. 6, which illustrates an exemplary method flow for adding
5 missing attributes from pre-defined dictionary, in accordance with exemplary
implementations of the present disclosure. As shown in block 602, a node sends one or more traps to a collector module shown in block 604. Further, as shown in block 606, it is checked whether the dictionary feature and trap translation for the node is applicable or not. Pertinently, the dictionary feature and trap translation for
10 the node is applicable if the one or more traps sent by the node to the collector
module comprises at least one missing attribute. Further, the missing attribute(s)/pre-defined trap attribute(s) for the node is added/appended to the one or more traps sent by the node to the collector module as shown in block 608. Further, the alarms/traps are allowed and forwarded in the message stream as shown
15 in block 610. Further, the alarms are forwarded to the fault processor as shown in
block 612.
[0072] The present disclosure further discloses a user equipment (UE). The UE comprises at least a transmitter unit configured to send to a system [200] comprising
20 a collector module [201], a request for receiving an indication related to managing
one or more traps in a communication network. This indication when received by the UE confirms whether the management of the one or more traps was successful or not, that is, whether the traps that were to be blacklisted have been blacklisted successfully (and therefore are not considered for processing), and the traps that
25 were to be whitelisted have been whitelisted successfully (and therefore are
considered for processing). Further, the UE comprises at least a receiver unit configured to receive, from the system [300], the indication in response to the request. The one or more traps in the communication network are managed based on receiving, by a transceiver unit [202] at the collector module [201], one or more
30 traps from one or more nodes of the communication network, the one or more traps
comprising one or more trap attributes and a node identifier. Further, the one or
28

more traps are managed based on generating, by a generator unit [204] at the
collector module [201], one or more final trap attributes by adding one or more
additional trap attributes to the one or more trap attributes of the one or more traps.
Further, the one or more traps are managed based on matching, by a matching unit
5 [206] at the collector module [201], one or more final trap attributes for each node
identifier with at least one of one or more attributes for each node identifier
provisioned in a set of blacklisting data and one or more attributes for each node
identifier provisioned in a set of whitelisting data. Further, the one or more traps
are managed based on tagging, by a tagging unit [208] at the collector module [201],
10 one or more traps as one of a blacklisted tag and a whitelisted tag based on the
matching. Further, the one or more traps are managed based on managing, by a managing unit [210] at the collector module [201], the one or more traps based on the tagging.
15 [0073] The present disclosure further discloses a non-transitory computer readable
storage medium storing instruction for managing one or more traps in a communication network. The instructions include executable code. The executable code when executed by one or more units of a system [200] comprising a collector module [201], causes a transceiver unit [202] of the collector module [201] to
20 receive one or more traps from one or more nodes of the communication network,
the one or more traps comprising one or more trap attributes and a node identifier. Further, the executable code when executed causes a generator unit [204] of the collector module [201] to generate one or more final traps by adding one or more additional trap attributes to the one or more trap attributes of the one or more traps.
25 Further, the executable code when executed causes a matching unit [206] of the
collector module [201] to match one or more final trap attributes for each node identifier with at least one of one or more attributes for each node identifier provisioned in a set of blacklisting data and one or more attributes for each node identifier provisioned in a set of whitelisting data. Further, the executable code
30 when executed causes a tagging unit [208] of the collector module [201] to tag one
or more traps as one of a blacklisted tag and a whitelisted tag based on the matching.
29

Further, the executable code when executed causes a managing unit [210] of the collector module [201] to manage the one or more traps based on tagging.
[0074] As is evident from the above, the present disclosure provides a technically
5 advanced solution for managing one or more traps in a communication network.
The present solution enables for blacklisting and/or whitelisting a plurality of traps received from one or more nodes of a wireless communication system. Further, the present solution supports expression-based segregation as well as match-based segregation of blacklisted or whitelisted traps. Further, the present solution provides
10 a dictionary profile and translation profile that is configurable in runtime. Further,
the present solution facilitates addition and dynamic modification based on a trap value to form a generic alarm. Further, the present solution provides a mechanism for identification and association of raise/clear trap that is configurable in runtime. Also, the present solution provides facilitates fast and easy integration of new
15 network elements with a network management system (as the configuration of
network elements is needed to be updated for authentication with their various endpoints for various communication requests). Also, the present solution is easily adaptable to version upgrades for existing network elements.
20 [0075] While considerable emphasis has been placed herein on the disclosed
implementations, it will be appreciated that many implementations can be made and that many changes can be made to the implementations without departing from the principles of the present disclosure. These and other changes in the implementations of the present disclosure will be apparent to those skilled in the art, whereby it is to
25 be understood that the foregoing descriptive matter to be implemented is illustrative
and non-limiting.
30

We Claim:
1. A method for managing one or more traps in a communication network, the
method comprising:
- receiving, by a transceiver unit [202] at a collector module [201], one or more traps from one or more nodes of the communication network, the one or more traps comprising one or more trap attributes and a node identifier;
- generating, by a generator unit [204] at the collector module [201], one or more final trap attributes by adding one or more additional trap attributes to the one or more trap attributes of the one or more traps;
- matching, by a matching unit [206] at the collector module [201], one or more final trap attributes for each node identifier with at least one of one or more attributes for each node identifier provisioned in a set of blacklisting data and one or more attributes for each node identifier provisioned in a set of whitelisting data;
- tagging, by a tagging unit [208] at the collector module [201], one or more traps as one of a blacklisted tag and a whitelisted tag based on the matching; and
- managing, by a managing unit [210] at the collector module [201], the one or more traps based on the tagging.

2. The method as claimed in claim 1, further comprising receiving, by the transceiver unit [202], at least one trap with one or more missing attributes.
3. The method as claimed in claim 2, wherein the one or more missing attributes are fetched from a pre-defined dictionary stored by a network management entity in the communication network.
4. The method as claimed in claim 1, further comprising discarding, by a discarding unit [212] at the collector module [201], at least one of the one or more traps tagged as the blacklisted tag.

5. The method as claimed in claim 1, the method further comprising transmitting, by the transceiver unit [202] at the collector module [201], one or more alarms corresponding to one or more whitelisted traps to a fault processor.
6. The method as claimed in claim 1, the method further comprising provisioning, by a user interface [214] at the collector module [201], the set of blacklisting data comprising one or more node identifiers and one or more trap attributes for each of the one or more node identifiers.
7. The method as claimed in claim 6, the method further comprising provisioning, by the user interface [214] at the collector module [201], the set of whitelisting data comprising one or more node identifiers and one or more trap attributes for each of the one or more node identifiers.
8. A system for managing one or more traps in a communication network, the system comprising a collector module [201], the collector module [201] further comprising:

- a transceiver unit [202] configured to receive one or more traps from one or more nodes of the communication network, the one or more traps comprising one or more trap attributes and a node identifier;
- a generator unit [204] connected to at least the transceiver unit [202], the generator unit [204] configured to generate one or more final traps by adding one or more additional trap attributes to the one or more trap attributes of the one or more traps;
- a matching unit [206] connected to at least the generator unit [204], the matching unit [206] configured to match one or more final trap attributes for each node identifier with at least one of one or more attributes for each

node identifier provisioned in a set of blacklisting data and one or more attributes for each node identifier provisioned in a set of whitelisting data;
- a tagging unit [208] connected to at least the matching unit [206], the tagging unit [208] configured to tag one or more traps as one of a blacklisted tag and a whitelisted tag based on the matching; and
- a managing unit [210] connected to at least the tagging unit [208], the managing unit [210] configured to manage the one or more traps based on the tagging.

9. The system as claimed in claim 8, wherein the transceiver unit [202] is further configured to receive at least one trap with one or more missing attributes.
10. The system as claimed in claim 9, wherein the one or more missing attributes are fetched from a pre-defined dictionary stored by a network management entity in the communication network.
11. The system as claimed in claim 8, wherein the collector module [201] further comprises a discarding unit [212], wherein the discarding unit [212] is configured to discard at least one of the one or more traps tagged as the blacklisted tag.
12. The system as claimed in claim 8, wherein the transceiver unit [202] is further configured to transmit one or more alarms corresponding to one or more whitelisted traps to a fault processor.
13. The system as claimed in claim 8, wherein the collector module [201] further comprises a user interface [214], wherein the user interface [214] is configured to provision the set of blacklisting data comprising one or more node identifiers and one or more trap attributes for each of the one or more node identifiers.

14. The system as claimed in claim 13, wherein the collector module [201] further comprises a user interface [214], wherein the user interface [214] is configured to provision the set of whitelisting data comprising one or more node identifiers and one or more trap attributes for each of the one or more node identifiers.
15. A user equipment comprising:

- at least a transmitter unit configured to send to a system [200] comprising a collector module [201], a request for receiving an indication related to managing one or more traps in a communication network; and
- at least a receiver unit configured to receive, from the system [300], the indication in response to the request,
wherein the one or more traps in the communication network are
managed based on:
o receiving, by a transceiver unit [202] at the collector module [201], one or more traps from one or more nodes of the communication network, the one or more traps comprising one or more trap attributes and a node identifier;
o generating, by a generator unit [204] at the collector module [201], one or more final trap attributes by adding one or more additional trap attributes to the one or more trap attributes of the one or more traps;
o matching, by a matching unit [206] at the collector module [201], one or more final trap attributes for each node identifier with at least one of one or more attributes for each node identifier provisioned in a set of blacklisting data and one or more attributes for each node identifier provisioned in a set of whitelisting data;
o tagging, by a tagging unit [208] at the collector module [201], one or more traps as one of a blacklisted tag and a whitelisted tag based on the matching; and

o managing, by a managing unit [210] at the collector module [201], the one or more traps based on the tagging.