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 PERFORMANCE DATA AND ASSOCIATE PERFORMANCE DATA OF A
NETWORK NODE”
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 PERFORMANCE DATA AND ASSOCIATE PERFORMANCE DATA OF A NETWORK NODE
FIELD OF INVENTION
[0001] Embodiments of the present disclosure relate, generally, to the field of wireless communication systems. More particularly, embodiment of the present disclosure relates to method and system for managing performance data and associate performance data of a network node.
BACKGROUND
[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] In a wireless communication network, a handover involves transferring a connected cellular call or data session from one base station to another without interrupting the session. Soft handovers, allowing parallel connections across multiple channels, aim to enhance service continuity. Conventionally, handover process has relied on substantial handovers, where connections to new channels are established before disconnecting from existing ones.
[0004] A source cell initiates handovers to various target cells, potentially ranging from 64 to 256 or more, depending on the node type. However, operational issues such as performance degradation during handovers necessitate detailed performance management (PM) data. The users require insights into PM data for both source and target cells to ensure efficient handover management.

[0005] Thus, there exists an imperative need in the art to optimise handover performance based on pairwise data from source and target cells, which the present disclosure aims to address.
SUMMARY
[0006] 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.
[0007] An aspect of the present disclosure relates to a method for managing performance data and associate performance data of a network node. The method comprising transmitting, by a transceiver unit, a counter reset request to at least one of a plurality of nodes in the network. Further, receiving, by the transceiver unit, in response to the counter reset request, via a load balancer associated with at least one of the plurality of nodes, Performance Management (PM) data and associate Performance Management (associate PM) data from said nodes. The method comprising updating, by an updation unit, the PM data and the associate PM data by adding an instance metadata. Further, transmitting, by the transceiver unit, the updated PM data and the updated associate PM data to a storage unit.
[0008] In an exemplary aspect of the present disclosure, the method further comprises configuring, by a processing unit, a scheduler to initiate the transmission of counter reset request to at least one of the plurality of nodes in the network at a pre-defined time interval.
[0009] In an exemplary aspect of the present disclosure, the method further comprises storing, by the storage unit, a copy of the transmitted counter reset

request in a cache database and allocating a counter reset request flow id to the stored copy of counter reset request.
[0010] In an exemplary aspect of the present disclosure, the load balancer is configured to receive the PM data and the associated PM data from at least one of the plurality of nodes, and wherein receiving, by the transceiver unit, via the load balancer, the PM data from at least one of the plurality of nodes comprises receiving the PM data and the associate PM data from the load balancer based on a round-robin selection mechanism implemented by the load balancer.
[0011] In an exemplary aspect of the present disclosure, upon receiving, by the transceiver unit, the PM data and the associate PM data from one of the plurality of nodes, the method further comprises removing the copy of stored counter reset request from the cache database.
[0012] In an exemplary aspect of the present disclosure, the method further comprises, storing the updated PM data and the updated associate PM data, via the storage unit and a PM node, into a secondary database, wherein the PM node is configured to poll the plurality of at least the updated PM data and the updated associate PM data from the storage unit based on a configurable polling interval and batch size of the plurality of PM data and associate PM data.
[0013] Another aspect of the present disclosure relates to a system for managing performance data and associate performance data of a network node, the system comprising a transceiver unit configured to transmit a counter reset request to at least one of a plurality of nodes in the network. The transceiver unit is further configured to, in response to the counter reset request, receive, via a load balancer associated with at least one of the plurality of nodes, Performance Management (PM) data and associate Performance Management (associate PM) data from said nodes. The system comprises an updation unit configured to update the PM data and updated PM data by adding an instance metadata. The transceiver unit is further

configured to transmit the updated PM data and updated associate PM data to a storage unit.
[0014] Yet another aspect of the present disclosure relates to a network node comprising a memory and a processor coupled to the memory, wherein the processor is configured to, in response to receiving a counter reset request, transmit, via a load balancer, Performance Management (PM) data and associate Performance Management (associate PM) data to a collector network node, wherein the PM data and the updated PM data is usable by the collector node to manage performance data of the network node based on transmitting the counter reset request to network node; on receiving the PM data and the associate PM data from the network node, updating the PM data and the associate PM data by adding an instance metadata; and transmitting the updated PM data and the updated associate PM data to a storage unit.
[0015] Yet another aspect of the present disclosure relates to a non-transitory computer readable storage medium storing instruction for managing performance data and associate performance data of a network node, the instructions include executable code which, when executed by one or more units of a system, causes the transceiver unit of the system to transmit a counter reset request to at least one of a plurality of nodes in the network. Further, the instructions include executable code which, when executed causes the transceiver unit of the system to receive, in response to the counter reset request, via a load balancer associated with at least one of the plurality of nodes, Performance Management (PM) data and associate Performance Management (associate PM) data from said nodes. Further, the instructions include executable code which, when executed causes an updation unit of the system to update the PM data and updated PM data by adding an instance metadata. Further, the instructions include executable code which, when executed causes the transceiver unit of the system to further transmit the updated PM data and updated associate PM data to a storage unit of the system.

OBJECTS OF THE DISCLOSURE
[0016] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.
[0017] It is an object of the present disclosure to provide a system and a method for managing performance data and associate performance data of a network node.
[0018] It is another object of the present disclosure to provide a solution for visualization and reporting pairwise PM data.
[0019] It is yet another object of the present disclosure to provide a solution to provide configurable interval for pairwise PM data and audit support for retrieving missed data.
DESCRIPTION OF THE DRAWINGS
[0020] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in which like reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. 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 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.

[0021] 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.
5 [0022] FIG. 2 illustrates an exemplary block diagram of a system for managing
performance data and associate performance data of a network node, in accordance with exemplary implementations of the present disclosure.
[0023] FIG. 3 illustrates a method flow diagram for managing performance data
10 and associate performance data of a network node, in accordance with exemplary
implementations of the present disclosure.
[0024] FIG. 4 illustrates an exemplary network architecture for managing
performance data and associate performance data of a network node, in accordance
15 with exemplary implementations of the present disclosure.
[0025] FIG. 5 illustrates an exemplary scenario method flow diagram for managing performance data and associate performance data of a network node, in accordance with exemplary implementations of the present disclosure. 20
[0026] The foregoing shall be more apparent from the following more detailed description of the disclosure.
DETAILED DESCRIPTION
25
[0027] In the following description, for the purposes of explanation, various specific details are set forth to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific details. Several features
30 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
7

problems discussed above or might address only some of the problems discussed above.
[0028] The ensuing description provides exemplary embodiments only, and is not
5 intended to limit the scope, applicability, or configuration of the disclosure. Rather,
the ensuing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing an exemplary embodiment. Various changes may be made in the function and arrangement of elements without departing from the spirit and scope of the disclosure as set forth.
10
[0029] Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it will be understood by one of ordinary skill in the art that the embodiments may be practiced without these specific details. For example, circuits, systems, processes, and other components
15 may be shown as components in block diagram form in order not to obscure the
embodiments in unnecessary detail.
[0030] Also, it is noted that individual embodiments may be described as a process which is depicted as a flowchart, a flow diagram, a data flow diagram, a structure
20 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 included in a figure.
25
[0031] The word “exemplary” and/or “demonstrative” is used herein to mean serving as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples. In addition, any aspect or design described herein as “exemplary” and/or “demonstrative” is not
30 necessarily to be construed as preferred or advantageous over other aspects or
designs, nor is it meant to preclude equivalent exemplary structures and techniques
8

known to those of ordinary skill in the art. Furthermore, to the extent that the terms
“includes,” “has,” “contains,” and other similar words are used in either the detailed
description or the claims, such terms are intended to be inclusive—in a manner like
the term “comprising” as an open transition word—without precluding any
5 additional or other elements.
[0032] As used herein, a “processing unit” or “processor” or “operating processor” 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
10 purpose processor, a conventional processor, a digital signal processor, a plurality
of microprocessors, one or more microprocessors in association with a Digital Signal Processing (DSP) core, a controller, a microcontroller, Application Specific Integrated Circuits, Field Programmable Gate Array circuits, any other type of integrated circuits, etc. The processor may perform signal coding data processing,
15 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.
[0033] As used herein, “a user equipment”, “a user device”, “a smart-user-device”,
20 “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
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
25 phone, laptop, a general-purpose computer, desktop, personal digital assistant,
tablet computer, wearable device or any other computing device which me be
implement the features of the present disclosure. Also, the user device may contain
at least one input means configured to receive an input from unit(s) which are
required to implement the features of the present disclosure.
30
9

[0034] As used herein, “storage unit” or “memory unit” refers to a machine or
computer-readable medium including any mechanism for storing information in a
form readable by a computer or similar machine. For example, a computer-readable
medium includes read-only memory (“ROM”), random access memory (“RAM”),
5 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 functions.
10 [0035] 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 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
15 called.
[0036] All modules, units, components used herein, unless explicitly excluded
herein, may be software modules or hardware processors, the processors being a
general-purpose processor, a special purpose processor, a conventional processor,
20 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 circuits (FPGA), any other type of integrated circuits, etc.
25 [0037] 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 and/or connected with the system.
30 [0038] As described in the background section, in wireless communication
network, handovers may be performed for transferring a connected cellular call or
10

data session from one base station to another without interrupting the session.
Generally, a source cell may initiate handovers to various target cells. However,
operational issues such as performance degradation during handovers necessitate
detailed performance management (PM) data. The present invention addresses the
5 critical challenge of seamless handovers (HO) in telecommunications and mobile
communications systems. This present invention introduces a solution that
facilitates the retrieval, processing, and analysis of PM data for source-target cell
pairs. By enabling a detailed view of performance metrics, the present invention
supports real-time monitoring, reporting, and strategic analysis, thereby optimizing
10 handover processes in telecommunications networks.
[0039] The present disclosure aims to overcome the above-mentioned and other
existing problems in this field of technology by configuring interval for retrieval of
pairwise PM data (i.e., PM data and associate PM data), auditing support for
15 retrieving missed data, and visualization and reporting of pairwise PM data.
[0040] Hereinafter, exemplary embodiments of the present disclosure will be described with reference to the accompanying drawings.
20 [0041] FIG. 1 illustrates an exemplary block diagram of a computing device [100]
upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure. In an implementation, the computing device [100] may also implement a method for managing performance data of a network node utilising the system. In another
25 implementation, the computing device [100] itself implements the method for
managing performance data of a network node using one or more units configured within the computing device [100], wherein said one or more units may be implement the features as disclosed in the present disclosure.
30 [0042] The computing device [100] may include a bus [102] or other
communication mechanism for communicating information, and a hardware
11

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]
5 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-
10 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].
15 [0043] 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
20 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
25 information and command selections to the processor [104], and for controlling
cursor movement on the display [112]. This input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allow the device to specify positions in a plane.
30 [0044] The computing device [100] may implement the techniques described
herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware
12

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
5 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
10 disclosure, hard-wired circuitry may be used in place of or in combination with
software instructions.
[0045] The computing device [100] also may include a communication interface
[118] coupled to the bus [102]. The communication interface [118] provides a two-
15 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
20 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.
25
[0046] 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
30 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,
13

and/or stored in the storage device [110], or other non-volatile storage for later execution.
[0047] Referring to FIG. 2, an exemplary block diagram of a system [200] for
5 managing performance data and associate performance data of a network node, is
shown, in accordance with the exemplary implementations of the present disclosure. The system [200] comprises at least one transceiver unit [202], at least one updation unit [204], at least one processing unit [206] and at least one storage unit [208]. Also, all the components/ units of the system [200] are assumed to be
10 connected to each other unless otherwise indicated below. As shown in the figures
all units shown within the system [200] should also be assumed to be connected to each other. Also, in FIG. 2 only a few units are shown, however, the system [200] may comprise multiple such units or the system [200] may comprise any such numbers of said units, as required to implement the features of the present
15 disclosure. Further, in an implementation, the system [200] may be present in a user
device/ user equipment to implement the features of the present disclosure. The system [200] may be a part of the user device or may be independent of but in communication with the user device (may also referred herein as a UE). In another implementation, the system [200] may reside in a server or a network entity. In yet
20 another implementation, the system [200] may reside partly in the server/ network
entity and partly in the user device.
[0048] The system [200] is configured for managing performance data and
associate performance data of a network node, with the help of the interconnection
25 between the components/units of the system [200]. Such network nodes may be in
communication with each other in a communication network. Examples of such network nodes may include, but are not limited to, a base station, a gNodeB, and an eNodeB.
30 [0049] In one example, the approaches of the present subject matter may be
implemented in scenarios when a handover may be performed for transferring a
14

session, associated with a User Equipment (UE), from one network node to another.
In the context of the present invention, when a handover takes place from one
network node (e.g., a base station), referred to as a source network node to another
network node, referred to as a target network node, a plurality of data may be taken
5 into consideration for ensuring a smooth handover. The data associated with the
source network node may be referred to as ‘Performance Management (PM) data’ and the data associated with the target network node may be referred to as ‘Associate Performance Management (PM) data’.
10 [0050] Examples of such PM data and associate PM data may include, but are not
limited to, metrics and information related to the performance and efficiency of the source and target nodes, such as response times, error rates, and throughput. It may be again noted that all such examples of PM data and associate PM data are only exemplary, and other types of performance metrics may also be considered, and
15 would lie within the scope of the present subject matter. Furthermore, any amount
of PM data and associate PM data may be taken into consideration, and does not impact the outcome of the invention.
[0051] In operation, in one example, the transceiver unit [202] may be configured
20 to transmit a counter reset request to at least one of a plurality of nodes in the
network. For example, the present disclosure encompasses that the transceiver unit [202], referred herewith, is to send a signal (the counter reset request) to one or more nodes within a larger interconnected network. The counter reset request instructs the network node to reset its counter to a predefined state. 25
[0052] In one example, the system [200] may further include the processing unit
[206] configured to configure a scheduler to initiate the transmission of counter
reset request to at least one of the plurality of nodes in the network at a pre-defined
time interval. The scheduler is a component or software module that manages
30 timing for various tasks and manages the timing to send out counter reset requests,
15

coordinating when these requests may be made. The scheduler operates based on a set schedule, with fixed time intervals for initiating the counter reset requests.
[0053] In another example, the storage unit [208] is further configured to store a
5 copy of the transmitted counter reset request in a cache database and allocate a
counter reset request flow id to the stored copy of counter reset request.
[0054] Continuing further, the transceiver unit is then configured to receive, in response to the counter reset request, via a load balancer associated with at least
10 one of the plurality of nodes, Performance Management (PM) data and associate
Performance Management (associate PM) data from said nodes. The present disclosure encompasses the load balancer is configured to receive the PM data from at least one of the plurality of nodes. The load balancer, on receiving the PM data and the associate performance management (associate PM) data from at least one
15 of the plurality of nodes, transmits the PM data and the associate performance
management (associate PM) data to the system [200] based on a round-robin selection mechanism.
[0055] The round-robin selection mechanism distributes tasks or data in a cyclic
20 order and executed by the load balancer. In other words, the load balancer will
handle the data reception, and the transceiver unit [202] is set up to get this PM data and the associate performance management (associate PM) data from the load balancer. The data transmission to the system [200] is based on a round-robin method, ensuring balanced data recapture from the nodes. 25
[0056] As described previously, the performance management (PM) data may refer
to the data associated with the network node from where the handover may be
initiated. Further, the associate performance management (associate PM) data may
refer to the data associated with the network node to where the handover may be
30 completed.
16

[0057] In another example, upon receiving the PM data and the associate PM data
from one of the plurality of nodes, the processing unit [206] is further configured
to remove the copy of stored counter reset request from the cache database. For
example, when the transceiver unit [202] receives PM data and the associate PM
5 data from any network node, it will then remove the corresponding counter reset
request that was temporarily stored in the cache database.
[0058] Continuing with the present example, thereafter, the updation unit [204], connected to at least the transceiver unit [202], may update the PM data and
10 associate PM data by adding an instance metadata. The instance metadata refers
herewith is to additional data that provides information about each instance of PM data, such as the time of collection, node identity, or other relevant attributes and updated PM data and associate PM data refers to the performance management (PM) data and associate performance management (associate PM data) that has
15 been modified by the system to include additional metadata (such as timestamps,
node identifiers, sequence numbers).
[0059] Thereafter, the transceiver unit [202] may transmit the updated PM data and updated associate PM data to a storage unit [208]. In other words, the transceiver
20 unit [202] is capable of sending the updated PM data, which now includes instance
metadata, to a designated storage unit [208]. The storage unit [208] is further configured to store the updated PM data and the updated associate PM data, via a PM node, into a secondary database. For example, the PM node is configured to poll the plurality of updated performance management (PM) data and the updated
25 associate performance management (associate PM) data from the storage unit [208]
based on a configurable polling interval and a batch size of the plurality of the updated PM data and updated associate PM data. The polled updated PM data and updated associate PM data are then stored into the secondary database.
30 [0060] Referring to FIG. 3, an exemplary method flow diagram [300] for managing
performance data and associate performance data of a network node, in accordance
17

with exemplary implementations of the present disclosure is shown. In an
implementation the method [300] is performed by the system [200]. Further, in an
implementation, the system [200] may be present in a server device to implement
the features of the present disclosure. Also, as shown in FIG. 3, the method [300]
5 starts at step [302].
[0061] At step 304, the method may comprise transmitting, by a transceiver unit [202], a counter reset request to at least one of a plurality of nodes in the network. For example, the present disclosure encompasses that the transceiver unit [202],
10 referred herewith, is to send a signal (the counter reset request) to one or more nodes
within a larger interconnected network. The counter reset request instructs the network node to reset its counter to a predefined state. Such network nodes may be in communication with each other in a communication network. Examples of such network nodes may include, but are not limited to, a base station, a gNodeB, and
15 eNodeB.
[0062] In one example, the system [200] may further include a processing unit
[206] configured to configure a scheduler to initiate the transmission of counter
reset request to at least one of the plurality of nodes in the network at a pre-defined
20 time interval. The scheduler is a component or software module that manages
timing for various tasks and manages the timing to send out counter reset requests, coordinating when these requests may be made. The scheduler operates based on a set schedule, with fixed time intervals for initiating the counter reset requests.
25 [0063] In another example, the storage unit [208] is further configured to store a
copy of the transmitted counter reset request in a cache database and allocate a counter reset request flow id to the stored copy of counter reset request.
[0064] At step 306, in response to the counter reset request, the method further
30 comprises receiving, by the transceiver unit [202], via a load balancer associated
with at least one of the plurality of nodes, Performance Management (PM) data and
18

associate Performance Management (associate PM) data from said nodes. The
present disclosure encompasses the load balancer is configured to receive the PM
data from at least one of the plurality of nodes. The load balancer, on receiving the
PM data and the associate performance management (associate PM) data from at
5 least one of the plurality of nodes, transmits the PM data and the associate
performance management (associate PM) data to the system [200] based on a round-robin selection mechanism.
[0065] The round-robin selection mechanism distributes tasks or data in a cyclic
10 order and executed by the load balancer. In other words, the load balancer will
handle the data reception, and the transceiver unit [202] is set up to get this PM data and the associate performance management (associate PM) data from the load balancer. The data transmission to the system [200] is based on a round-robin method, ensuring balanced data recapture from the nodes.
15
[0066] In one example, the approaches of the present subject matter may be implemented in scenarios when a handover may be performed for transferring a session, associated with a User Equipment (UE), from one network node to another. In the context of the present invention, when a handover takes place from one
20 network node (e.g., a base station), referred to as a source network node to another
network node, referred to as a target network node, a plurality of data may be taken into consideration for ensuring a smooth handover. The data associated with the source network node may be referred to as ‘Performance Management (PM) data’ and the data associated with the target network node may be referred to as
25 ‘Associate Performance Management (PM) data’.
[0067] Examples of such PM data and associate PM data may include, but are not
limited to, metrics and information related to the performance and efficiency of the
source and target nodes, such as response times, error rates, and throughput. It may
30 be again noted that all such examples of PM data and associate PM data are only
exemplary, and other types of performance metrics may also be considered, and
19

would lie within the scope of the present subject matter. Furthermore, any amount of PM data and associate PM data may be taken into consideration, and does not impact the outcome of the invention.
5 [0068] In another example, upon receiving the PM data and the associate PM data
from one of the plurality of nodes, the processing unit [206] is further configured
to remove the copy of stored counter reset request from the cache database. For
example, when the transceiver unit [202] receives PM data and the associate PM
data from any network node, it will then remove the corresponding counter reset
10 request that was temporarily stored in the cache database.
[0069] At step 308, the method further comprises, updating, by an updation unit [204], the PM data and associate PM data by adding an instance metadata. The instance metadata refers herewith is to additional data that provides information
15 about each instance of PM data, such as the time of collection, node identity, or
other relevant attributes and updated PM data and associate PM data refers to the performance management (PM) data and associate performance management (associate PM data) that has been modified by the system to include additional metadata (such as timestamps, node identifiers, sequence numbers).
20
[0070] At step 310, the method further comprises, transmitting, by the transceiver unit [202], the updated PM data and associate Performance Management (associate PM) data to a storage unit [208]. In other words, the transceiver unit [202] is capable of sending the updated PM data, which now includes instance metadata, to a
25 designated storage unit [208]. The storage unit [208] is further configured to store
the updated PM data and the updated associate PM data, via a PM node, into a secondary database. For example, the PM node is configured to poll the plurality of updated performance management (PM) data and the updated associate performance management (associate PM) data from the storage unit [208] based on
30 a configurable polling interval and a batch size of the plurality of the updated PM
20

data and updated associate PM data. The polled updated PM data and updated associate PM data are then stored into the secondary database.
[0071] Thereafter, the method terminates at step 312. 5
[0072] Referring to FIG. 4, an exemplary network architecture diagram for managing performance data and associate performance data of a network node, in accordance with exemplary implementations of the present disclosure, is shown.
10 [0073] In an implementation, the process [400] is initiated by the collector which
acts as a transceiver unit [202]/processing unit [206] as stated in FIG. 2. The collector is to send a signal (the counter reset request) to one or more network elements, referred to as one or more network nodes in FIG. 2, within a larger interconnected network. The counter reset request instructs the network element to
15 reset its counter to a predefined state.
[0074] As depicted in FIG. 4, the load balancer is configured to receive the PM data and the associated PM data from the network element. In one example, the load balancer, on receiving the PM data and the associate performance management
20 (associate PM) data from the network element, transmits the PM data and the
associate performance management (associate PM) data to the collector based on a round-robin selection mechanism. The collector is further configured to store a copy of the transmitted counter reset request in a cache database, referred to as IO Cache in FIG. 4, and allocate a counter reset request flow id to the stored copy of
25 counter reset request.
[0075] As further depicted in FIG. 4, in another example, when the collector
receives PM data and the associate PM data from any network element, it will then
remove the corresponding counter reset request that was temporarily stored in the
30 IO cache and sends the updated PM data and associates PM data to the Stream
(which act as the storage unit as stated in FIG. 2). The stream is configured to store
21

the updated PM data and associated PM data, via a PM node, into a secondary database, referred to as ‘DB’ in FIG. 4.
[0076] In another example, as depicted in FIG. 4, the unremoved entries in the IO
5 Cache may be used by a Performance Management (PM) auditor for auditing. It
may be noted that the unremoved entries in the IO Cache may indicate that the
collector had stored a copy of counter reset request, for a network element, in the
IO Cache, however, a set of PM data and associate PM data was not received from
the corresponding network element. As a result, the temporarily stored request was
10 not removed from the IO Cache.
[0077] Referring to FIG. 5, an exemplary scenario method flow diagram [500] for managing performance data and associate performance data of a network node, in accordance with exemplary implementations of the present disclosure, is shown.
15
[0078] The system architecture for fetching and processing Performance Management (PM) data and associate Performance Management (associate PM) data begins with the collector component of the Network Management System (NMS). The collector initiates the process and sends a signal (the counter reset
20 request) to network elements within a larger interconnected network. The counter
reset request instructs the network elements to reset its counter to a predefined state.
[0079] Each collector node tracks every request it sends out by logging these
requests in a distributed Input/Output (IO) cache system. Each request is assigned
25 a unique flow identifier (flow-ID) to ensure tracking and management. When a
network element, or cell, receives a counter reset request, it responds by sending the PM data and the associate PM data and the counter data in a single, unified request back to the collector.
30 [0080] Upon receiving the PM data and the associate PM data from the network
element, the collector uses the flow-ID to identify and match the data with the
22

corresponding request in the IO cache. Once the data is correctly matched, the
collector removes the entry from the IO cache, confirming that the request has been
fulfilled. The collector then processes the received data, separating the PM data and
the associate PM data from the counter data, and places each type of data into the
5 stream for further processing.
[0081] The PM node is responsible for fetching the PM data and the associate PM
data from the stream. The configuration of the PM node allows it to control the
volume of data pulled in a single request and the frequency of these data pulls.
10 These parameters can be adjusted to optimize performance based on processing
capacity and system requirements. Once the PM node retrieves the data, it processes it and records the counter values for each source and target cell pair, ensuring detailed and accurate data management.
15 [0082] The processed data entries are added to a queue by the PM node. From this
queue, the data is periodically flushed to a persistent database (DB) in batches. Both the size of these batches and the interval at which data is flushed to the DB are configurable, allowing for fine-tuned control over the data storage process.
20 [0083] To ensure complete data retrieval, the system verifies if data for all cells
connected to the NMS has been received. If so, no request entries will remain in the IO cache. Any leftover request entries in the IO cache indicate data that may have been missed. These entries are utilized by the PM auditor, a component designed to recover any missed data, ensuring data integrity and consistency across the system.
25
[0084] The present disclosure further discloses a non-transitory computer readable storage medium storing instruction for managing performance data and associate performance data of a network node, the instructions include executable code which, when executed by one or more units of a system, causes a transceiver unit
30 [202] of the system [200] to transmit a counter reset request to at least one of a
plurality of nodes in the network. Further, the instructions include executable code
23

which, when executed causes the transceiver unit [202] of the system [200] to in
response in response to the counter reset request, receive, via a load balancer
associated with at least one of the plurality of nodes, Performance Management
(PM) data from said nodes. Further, the instructions include executable code which,
5 when executed causes an updation unit [204] of the system [200] to update the PM
data by adding an instance metadata. Further, the instructions include executable code which, when executed causes the transceiver unit [202] of the system [200] to further transmit the updated PM data to a storage unit [208] of the system [200].
10 [0085] As is evident from the above, the present disclosure provides a technically
advanced solution for optimising handover performance based on pairwise data, i.e., PM data and associate PM data from source and target cells. The present invention encompasses many advantages over the existing prior arts such as:
15 • Retrieving PM data for all source and target cell pairs connected to NMS.
• To storing pairwise data with hundred percent fault tolerance capacity.
• The horizontal scaling mechanism to support load distribution and parallel processing.
• To support for pairwise counter data reporting of selected cells for provided
20 time duration.
• The HO in cell performance data degrades. But this HO in cell is neighbour to
many cells. The Pairwise counter data helps to identify exact which HO out cell
to this HO in cell problem is there.
• To reduce effort to find exact problematic cell as without pairwise counter data
25 we need to corelate KPI values of all 64 neighbour cells.
[0086] 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
30 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
24

be understood that the foregoing descriptive matter to be implemented is illustrative and non-limiting.
[0087] Further, in accordance with the present disclosure, it is to be acknowledged
5 that the functionality described for the various components/units can be
implemented interchangeably. While specific embodiments may disclose a
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
10 as limiting the scope of the present disclosure. Consequently, alternative
arrangements and substitutions of units, provided they achieve the intended functionality described herein, are considered to be encompassed within the scope of the present disclosure.
25

We Claim:
1. A method [300] for managing performance data and associate performance
data of a network node, the method [300] comprising:
- transmitting [304], by a transceiver unit [202], a counter reset request to at least one of a plurality of nodes in the network;
- in response to the counter reset request, receiving [306], by the transceiver unit [202], via a load balancer associated with at least one of the plurality of nodes, Performance Management (PM) data and associated Performance Management (associate PM) data from said nodes;
- updating [308], by an updation unit [204], the PM data and the associate PM data by adding an instance metadata; and
- transmitting [310], by the transceiver unit [202], the updated PM data and the updated associate PM data to a storage unit [208].
2. The method [300] as claimed in claim 1, further comprising:
- configuring, by a processing unit [206], a scheduler to initiate the
transmission of counter reset request to at least one of the plurality of nodes
in the network at a pre-defined time interval.
3. The method [300] as claimed in claim 1, further comprising:
- storing, by the storage unit [208], a copy of the transmitted counter reset request in a cache database; and
- allocating a counter reset request flow id to the stored copy of counter reset request.
4. The method [300] as claimed in claim 1, wherein the load balancer is
configured to receive the PM data and the associated PM data from at least one of
the plurality of nodes, and wherein receiving, by the transceiver unit [202], via the
load balancer, the PM data from at least one of the plurality of nodes comprises

receiving the PM data and the associate PM data from the load balancer based on a round-robin selection mechanism implemented by the load balancer.
5. The method [300] as claimed in claim 3, wherein upon receiving, by the
transceiver unit [202], the PM data and the associate PM data from one of the
plurality of nodes, the method further comprises:
- removing the copy of stored counter reset request from the cache database.
6. The method [300] as claimed in claim 1, further comprising: storing the updated PM data and the updated associate PM data, via the storage unit [208] and a PM node, into a secondary database, wherein the PM node is configured to poll the plurality of at least the updated PM data and the updated associate PM data from the storage unit [208] based on a configurable polling interval and batch size of the plurality of PM data and associate PM data.
7. A system [200] for managing performance data and associate performance data of a network node, the system [200] comprising:
- a transceiver unit [202] configured to:
o transmit a counter reset request to at least one of a plurality of nodes
in the network; and o in response to the counter reset request, receive, via a load balancer
associated with at least one of the plurality of nodes, Performance
Management (PM) data and associate Performance Management
(associate PM) data from said nodes;
- an updation unit [204] configured to:
o update the PM data and updated PM data by adding an instance metadata; and
- the transceiver unit [202] configured to transmit the updated PM data and
updated associate PM data to a storage unit [208].

8. The system [200] as claimed in claim 7, further comprising a processing
unit [206] configured to:
- configure a scheduler to initiate the transmission of counter reset request to
at least one of the plurality of nodes in the network at a pre-defined time
interval.
9. The system [200] as claimed in claim 7, wherein the storage unit [208] is
further configured to:
- store a copy of the transmitted counter reset request in a cache database; and
allocate a counter reset request flow id to the stored copy of counter reset
request.
10. The system [200] as claimed in claim 7, wherein the load balancer is to receive the PM data and the associate PM data from at least one of the plurality of nodes, and wherein the transceiver unit [202] is configured to receive, via the load balancer, the PM data and the associate PM data from at least one of the plurality of nodes based on a round-robin selection mechanism implemented by the load balancer.
11. The system [200] as claimed in claim 9, further comprising a processing unit [206], wherein upon receiving the PM data and the associate PM data from one of the plurality of nodes, the processing unit [206] is configured to:
- remove the copy of stored counter reset request from the cache database.
12. The system [200] as claimed in claim 7, wherein the updation unit [204] is
further configured to:
- store the updated PM data and the updated associate PM data, via the storage
unit [208] and a PM node, into a secondary database, wherein the PM node
is configured to poll the plurality of at least the updated PM data and the
updated associate PM data from the storage unit [208] based on a

configurable polling interval and batch size of the plurality of PM data and associate PM data.
13. A network node comprising:
- a memory; and
- a processor coupled to the memory, wherein the processor is configured to:
o in response to receiving a counter reset request, transmit, via a load balancer, Performance Management (PM) data and associate Performance Management (associate PM) data to a collector network node, wherein the PM data and the updated PM data is usable by the collector network node to manage performance data of the network node based on:
▪ transmitting the counter reset request to network node; ▪ on receiving the PM data and the associate PM data from the network node, updating the PM data and the associate PM data by adding an instance metadata; and ▪ transmitting the updated PM data and the updated associate PM data to a storage unit [208].