Method and system for managing performance data of a node in a network

Abstract

The present disclosure relates to a method and a system for managing performance data of a node in a network The present disclosure encompasses transmitting, by a transceiver unit [202], a counter reset request to at least one of a plurality of nodes in the network. The method comprises in response to the counter reset request, receiving, by the transceiver unit [202], via a load balancer associated with at least one of the plurality of nodes, Performance Management (PM) data from said nodes. The method comprises updating, by a processing unit [204], the PM data by adding an instance metadata. The method comprises transmitting, by the transceiver unit [202], the updated PM data to a storage unit [206].

Description

METHOD AND SYSTEM FOR MANAGING PERFORMANCE DATA OF A NODE IN A NETWORKTECHNICAL FIELD

[0001] Embodiments of the present disclosure relate generally to the field of wireless communication systems. More particularly, embodiment of the present disclosure relate to method and system for managing performance data of a node in a network.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] 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] One of the major problems encountered in today’s network technology is related to the fetching of Performance Management (PM) data from network elements. A single NMS cluster may need to monitor FCAPS (Fault, Configuration, Accounting, Performance, and Security) data from over 50,000 RAN instances, with performance counter data being collected at 15-minute intervals. However, a significant challenge arose in efficiently processing and storing the entirePM data in a matter of minutes. This fast processing is crucial for enabling subsequent operations such as Key Performance Indicator (KPI) calculation and smooth data dump towards the Northbound Interface (NBI).

[0005] Further, over time, various solutions have been developed to enhance PM data processing and KPI management. However, there are certain challenges with existing solutions. One notable technical limitation and shortcoming is the fixed counter data pull interval of 15 minutes. While this interval may be suitable for some scenarios, it may not be sufficient for capturing real-time or near real-time data fluctuations. In rapidly changing network environments, 15 minutes may be a too long a time gap, potentially leading to missed or delayed data updates. This limitation can impact the accuracy and responsiveness of the system's monitoring and analysis capabilities.

[0006] Thus, there exists an imperative need in the art to provide improved methods for PM data processing and KPI management, which the present disclosure aims to address these needs by offering solution that overcome the limitations of existing system.SUMMARY

[0007] This section is provided to introduce certain aspects of the present disclosure in a simplified form that are further described below in the detailed description. This summary is not intended to identify the key features or the scope of the claimed subject matter.

[0008] An aspect of the present disclosure may relate to a method for managing performance data of a node in a network, the method comprising transmitting, by a transceiver unit, a counter reset request to at least one of a plurality of nodes in the network. The method further comprises, in response to the counter reset request, receiving, by the transceiver unit, via a load balancer associated with at least one of the plurality of nodes, Performance Management (PM) data from said nodes. The method comprises updating, by a processing unit, the PM data by adding an instance metadata. The method further comprises transmitting, by the transceiver unit, the updated PM data to a storage unit.

[0009] In an exemplary aspect of the present disclosure, the method further comprises configuring, by the 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.

[0010] In an exemplary aspect of the present disclosure, the method further comprises storing by a 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.

[0011] In an exemplary aspect of the present disclosure, the load balancer is configured to receive the 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 from the load balancer based on a round-robin selection mechanism implemented by the load balancer.

[0012] In an exemplary aspect of the present disclosure, upon receiving, by the transceiver unit, the 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.

[0013] In an exemplary aspect of the present disclosure, the method further comprises, storing by the storage unit the updated PM data, via a PM node, into a secondary database, wherein the PM node is configured to poll the plurality of updated PM data from the storage unit based on a configurable polling interval and batch size of the plurality of PM data.

[0014] Another aspect of the present disclosure may relate to a system for managing performance data of a node in a network, 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 from said nodes. The system comprises a processing unit connected to at least the transceiver unit, wherein the processing unit configured to update the PM data by adding an instance metadata. The transceiver unit is further configured to transmit the updated PM data to a storage unit.

[0015] Yet another aspect of the present disclosure may relate 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 to a collector node in the network, wherein the 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 in the network; on receiving the PM data from the network node,updating the PM data by adding an instance metadata; and transmitting the updated PM data to a storage unit.

[0016] Yet another aspect of the present disclosure may relate to a non-transitory computer readable storage medium storing instruction for managing performance data of a node in a network, the instructions include executable code which, when executed by one or more units of a system, causes a 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 from said nodes. Further, the instructions include executable code which, when executed causes a processing unit of the system to update the 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 to a storage unit.OBJECTS OF THE DISCLOSURE

[0017] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.

[0018] It is an object of the present disclosure to provide a system and a method for managing performance data of a node in a network.

[0019] It is an object of the present disclosure to provide a system and a method for cells PM processing and KPI management.

[0020] It is another object of the present disclosure to provide a solution that processes a PM data and puts the data to a stream counter category wise.

[0021] It is yet another object of the present disclosure to provide a solution to flush the received data to a persistent database (DB) in batches.DESCRIPTION OF THE DRAWINGS

[0022] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in which like reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. 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.

[0023] FIG. 1 illustrates an exemplary block diagram of a computing device

[0100] upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure.

[0024] FIG. 2 illustrates an exemplary block diagram of a system

[0200] for managing performance data of a node in a network, in accordance with exemplary implementations of the present disclosure.

[0025] FIG. 3 illustrates a method flow diagram

[0300] for managing performance data of a node in a network, in accordance with exemplary implementations of the present disclosure.

[0026] FIG. 4 illustrates an exemplary architecture diagram of a system

[0400] for managing performance data of a node in a network, in accordance with exemplary implementations of the present disclosure.

[0027] FIG. 5 illustrates an exemplary scenario method flow diagram

[0500] for managing performance data of a node in a network, in accordance with exemplary implementations of the present disclosure.

[0028] The foregoing shall be more apparent from the following more detailed description of the disclosure.DETAILED DESCRIPTION

[0029] 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 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.

[0030] The ensuing description provides exemplary embodiments only, and is not 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. It should be understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope of the disclosure as set forth.

[0031] 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 may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail.

[0032] 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 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.

[0033] 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 necessarily to be construed as preferred or advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar words are used in either the detailed description or the claims,such terms are intended to be inclusive — in a manner similar to the term “comprising” as an open transition word — without precluding any additional or other elements.

[0034] 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 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, 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.

[0035] As used herein, “a user equipment”, “a user device”, “a smart-user-device”, “a smartdevice”, “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 phone, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, wearable device or any other computing device which is capable of implementing the features of the present disclosure. Also, the user device may 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.

[0036] 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”), 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.

[0037] 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 moremodules or one or more units with each other, which also includes the methods, functions, or procedures that may be called.

[0038] All modules, units, components used herein, unless explicitly excluded herein, may be software modules or hardware processors, the processors being a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more 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.

[0039] 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.

[0040] As used herein the term KPI stands for Key Performance Indicator and refers to a quantifiable metric or measurement used to evaluate the performance and effectiveness of a system or process. KPIs are typically defined based on specific goals, objectives, or performance targets established for the system. KPIs are utilized to assess the performance of the network management system (NMS) in terms of its ability to monitor and manage the Performance Management (PM) data from Network Elements. These indicators may include parameters such as data retrieval speed, processing efficiency, data storage capacity, and accuracy of data analysis. By tracking and analysing KPIs, the NMS can gauge its performance, identify areas for improvement, and ensure that the system meets the desired operational standards.

[0041] As discussed in the background section, the current known solutions for managing performance data of a node in a network, have several shortcomings such as to process and store a large volume of Performance Management (PM) data from Network Elements. While the prior solution states that more than 50,000 RAN instances FCAPS data monitoring can be supported by a single NMS Cluster, it does not address the potential scalability issues associated with processing and storing such a massive amount of data. As the existing systems aims to perform tasks like KPI calculation and data dump towards the Northbound Interface (NBI), it is crucial to ensure that the underlying infrastructure can handle the processing and storage requirements in a timely and efficient manner. Without addressing this shortcoming, there is a risk of performance degradation, delays in data processing, and potential data loss, limiting the overall effectiveness of the system in handling large-scale PM data.

[0042] 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 performance data of a node in a network.

[0043] It implements a configurable batch mechanism that enables the sending of counter reset requests to connected nodes. This mechanism allows for efficient management of counter data, ensuring accurate and timely resets across the network. Additionally, the solution employs a configurable batch mechanism to flush counter data to the database. This ensures that the counter information is stored securely and promptly, enhancing data integrity and availability.

[0044] Hereinafter, exemplary embodiments of the present disclosure will be described with reference to the accompanying drawings.

[0045] FIG. 1 an exemplary block diagram of a computing device

[0100] 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

[0100] may also implement a method for managing performance data of a node in a network utilising the system. In another implementation, the computing device

[0100] itself implements the method for managing performance data of a node in a network using one or more units configured within the computing device

[0100] , wherein said one or more units are capable of implementing the features as disclosed in the present disclosure.

[0046] The computing device

[0100] may include a bus

[0102] or other communication mechanism for communicating information, and a hardware processor

[0104] coupled with bus

[0102] for processing information. The hardware processor

[0104] may be, for example, a general -purpose microprocessor. The computing device

[0100] may also include a main memory

[0106] , such as a random-access memory (RAM), or other dynamic storage device, coupled to the bus

[0102] for storing information and instructions to be executed by the processor

[0104] , The main memory

[0106] also may be used for storing temporary variables or other intermediate information during execution of the instructions to be executed by the processor

[0104] , Such instructions, when stored in non-transitory storage media accessible to the processor

[0104] , render the computing device

[0100] into a special-purpose machine that is customized to perform the operations specified in the instructions. The computing device

[0100] further includes a read only memory (ROM)

[0108] orother static storage device coupled to the bus

[0102] for storing static information and instructions for the processor

[0104] ,

[0047] A storage device

[0110] , such as a magnetic disk, optical disk, or solid-state drive is provided and coupled to the bus

[0102] for storing information and instructions. The computing device

[0100] may be coupled via the bus

[0102] to a display

[0112] , such as a cathode ray tube (CRT), Liquid crystal Display (LCD), Light Emitting Diode (LED) display, Organic LED (OLED) display, etc. for displaying information to a computer user. An input device

[0114] , including alphanumeric and other keys, touch screen input means, etc. may be coupled to the bus

[0102] for communicating information and command selections to the processor

[0104] , Another type of user input device may be a cursor controller

[0116] , such as a mouse, a trackball, or cursor direction keys, for communicating direction information and command selections to the processor

[0104] , and for controlling cursor movement on the display

[0112] , 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.

[0048] The computing device

[0100] may implement the techniques described herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware and / or program logic which in combination with the computing device

[0100] causes or programs the computing device

[0100] to be a special-purpose machine. According to one implementation, the techniques herein are performed by the computing device

[0100] in response to the processor

[0104] executing one or more sequences of one or more instructions contained in the main memory

[0106] , Such instructions may be read into the main memory

[0106] from another storage medium, such as the storage device

[0110] , Execution of the sequences of instructions contained in the main memory

[0106] causes the processor

[0104] to perform the process steps described herein. In alternative implementations of the present disclosure, hard-wired circuitry may be used in place of or in combination with software instructions.

[0049] The computing device

[0100] also may include a communication interface

[0118] coupled to the bus

[0102] , The communication interface

[0118] provides a two-way data communication coupling to a network link

[0120] that is connected to a local network

[0122] , For example, the communication interface

[0118] 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

[0118] may be a local area network (LAN) card to provide a data communication connection to a compatibleLAN. Wireless links may also be implemented. In any such implementation, the communication interface

[0118] sends and receives electrical, electromagnetic or optical signals that carry digital data streams representing various types of information.

[0050] The computing device

[0100] can send messages and receive data, including program code, through the network(s), the network link

[0120] and the communication interface

[0118] , In the Internet example, a server

[0130] might transmit a requested code for an application program through the Internet

[0128] , the ISP

[0126] , the local network

[0122] , the host

[0124] and the communication interface

[0118] , The received code may be executed by the processor

[0104] as it is received, and / or stored in the storage device

[0110] , or other non-volatile storage for later execution.

[0051] Referring to FIG. 2, an exemplary block diagram of a system

[0200] for managing performance data of a node in a network, is shown, in accordance with the exemplary implementations of the present disclosure. The system

[0200] comprises at least one transceiver unit

[0202] , at least one processing unit

[0204] and at least one storage unit

[0206] , Also, all of the components / units of the system

[0200] are assumed to be connected to each other unless otherwise indicated below. As shown in the figures all units shown within the system

[0200] should also be assumed to be connected to each other. Also, in FIG. 2, only a few units are shown, however, the system

[0200] may comprise multiple such units or the system

[0200] may comprise any such numbers of said units, as required to implement the features of the present disclosure. Further, in an implementation, the system

[0200] may be present in a user device / user equipment to implement the features of the present disclosure. The system

[0200] 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

[0200] may reside in a server or a network entity. In yet another implementation, the system

[0200] may reside partly in the server / network entity and partly in the user device.

[0052] The system

[0200] is configured for managing performance data of a node in a network, with the help of the interconnection between the components / units of the system

[0200] ,

[0053] The system comprises a transceiver unit

[0202] configured to transmit a counter reset request to at least one of a plurality of nodes in the network. The present disclosure encompasses the transceiver unit

[0202] is a device capable of both transmitting and receiving signals wherein the transceiver unit

[0202] sending a signal (the counter reset request) to one or more nodes within a larger interconnected network. The counter reset request instructs a device to reset its counter toa predefined state. In one example, the processing unit

[0204] , connected to the transceiver unit

[0202] , is 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 timing for various tasks and manages the timing to send the 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. Moreover, the processing unit

[0204] 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.

[0054] In an implementation of the present disclosure, the transceiver unit is further configured 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 from said node. The present disclosure encompasses the load balancer configured to receive the PM data from at least one of the plurality of nodes. Further, performance Management (PM) data, in an example, includes metrics and information related to the performance and efficiency of the nodes, such as response times, error rates, throughput, etc. The load balancer, on receiving the PM data from at least one of the plurality of nodes, transmits the PM data to the system

[0200] based on a round-robin selection mechanism.

[0055] The round-robin selection mechanism distributes tasks or data in a cyclic order and is executed by the load balancer. In other words, the load balancer will handle the data reception of PM data from the plurality of nodes, and the transceiver unit

[0202] is set up to get this PM data from the load balancer. The data transmission to the system

[0200] is based on a round-robin method, ensuring balanced data transmission to the system

[0200] ,

[0056] In another example, upon receiving the PM data from one of the plurality of nodes, the transceiver unit

[0202] is further configured to remove the copy of stored counter reset request from the cache database. For example, when the transceiver unit

[0202] receives PM data from any node in the network, it will then remove the corresponding counter reset request that was temporarily stored in the cache database.

[0057] Thereafter, the processing unit

[0204] is configured to update the PM data by adding an instance metadata. The instance metadata refers to additional data that provides information about each instance of PM data, such as the time of collection, node identity, or other relevant attributes.

[0058] The transceiver unit

[0202] is further configured to transmit the updated PM data to the storage unit

[0206] , In other words, the transceiver unit

[0202] is capable of sending the updated PM data, which now includes instance metadata, to a designated storage unit

[0206] , The storage unit

[0206] is further configured to store the updated PM data, via a PM node, into a secondary database. The PM node is configured to poll the plurality of PM data from the storage unit

[0206] based on a configurable polling interval and batch size of the plurality of PM data. The polled PM data is then stored into the secondary database.

[0059] Referring to FIG. 3, an exemplary method flow diagram

[0300] for managing performance data of a node in a network, in accordance with exemplary implementations of the present disclosure is shown. In an implementation the method

[0300] is performed by the system

[0200] , Also, as shown in FIG. 3, the method

[0300] starts at step

[0302] ,

[0060] At step 304, the method comprises, transmitting, by a transceiver unit

[0202] , a counter reset request to at least one of a plurality of nodes in the network. The counter reset request instructs a device to reset its counter to a predefined state.

[0061] Moreover, the method further encompasses storing 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.

[0062] In one example, configuring, by the processing unit

[0204] , 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 timing for various tasks and manages the timing to send the 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.

[0063] At step 306, the method comprises, in response to the counter reset request, receiving, by the transceiver unit

[0202] , via a load balancer associated with at least one of the plurality of nodes, Performance Management (PM) data from said nodes. The present disclosure encompasses the load balancer configured to receive the PM data from at least one of the plurality of nodes. Further, performance Management (PM) data, in an example, includes metrics and information related to the performance and efficiency of the nodes, such as response times, error rates, throughput, etc.The load balancer, on receiving the PM data from at least one of the plurality of nodes, transmits the PM data to the system

[0200] based on a round-robin selection mechanism.

[0064] The round-robin selection mechanism distributes tasks or data in a cyclic order and is executed by the load balancer. In other words, the load balancer will handle the data reception of PM data from the plurality of nodes, and the transceiver unit

[0202] is set up to get this PM data from the load balancer. The data transmission to the system

[0200] is based on a round-robin method, ensuring balanced data transmission to the system

[0200] ,

[0065] In another example, upon receiving the PM data from one of the plurality of nodes, the copy of stored counter reset request is removed from the cache database by the transceiver unit

[0202] , For example, when the transceiver unit

[0202] receives PM data from any node in the network, it will then remove the corresponding counter reset request that was temporarily stored in the cache database.

[0066] At step 308, the method comprises, updating, by a processing unit

[0204] , the PM data by adding an instance metadata. The instance metadata refers to additional data that provides information about each instance of PM data, such as the time of collection, node identity, or other relevant attributes.

[0067] At step 310, the method comprises, transmitting, by the transceiver unit

[0202] , the updated PM data to the storage unit

[0206] , For example, the transceiver unit

[0202] is capable of sending the updated PM data, which now includes instance metadata, to a designated storage unit

[0206] , Further, storing by the storage unit

[0206] , the updated PM data, via a PM node, into a secondary database. The PM node is configured to poll the plurality of PM data from the storage unit

[0206] based on a configurable polling interval and batch size of the plurality of PM data. The polled PM data is then stored into the secondary database.

[0068] Thereafter, the method terminates at step 312.

[0069] Referring to FIG. 4, an exemplary architecture diagram of a system

[0400] for managing performance data of a node in a network, in accordance with exemplary implementations of the present disclosure, is shown.

[0070] In an implementation, the process

[0400] is performed by the collector

[0402] which is similar to the transceiver unit

[0202] and processing unit

[0204] as stated in FIG. 2. The collector

[0402] sends a counter reset request to at least one of a plurality of network elements

[0404] , The counter reset request instructs the network element

[0404] to reset its counter to a predefined state.

[0071] In one example, the load balancer

[0406] is configured to receive the PM data from at least one of the network element

[0404] , Further, Performance Management (PM) data, in an example, includes metrics and information related to the performance and efficiency of the network element

[0404] , such as response times, error rates, and throughput. The data transmission from the load balancer

[0406] to the collector

[0402] is based on a round-robin method, ensuring balanced data transmission. The collector

[0402] is further configured to store a copy of the transmitted counter reset request in an IO cache

[0408] ,

[0072] The collector

[0402] then receives the PM data and removes corresponding request entries from the IO Cache

[0408] and sends the updated PM data to the Stream

[0410] which act as the storage unit as stated in FIG. 2. Then, a PM Auditor

[0412] receives unremoved entries from the IO Cache

[0408] , audits them to ensure all requests are correctly processed and accounted for, and verifies data integrity. Further, the collector

[0402] transmits updated PM data to the stream

[0410] , The stream

[0410] is configured to store the updated PM data, via a PM node

[0414] , into a DB

[0416] (which acts as the secondary database as stated in FIG. 2). For example, the updated PM data, from the stream

[0410] is transmitted to the PM node

[0414] , and then stored in the secondary database

[0416] ,

[0073] Referring to FIG. 5, an exemplary scenario method flow diagram

[0500] for managing performance data of a node in a network, in accordance with exemplary implementations of the present disclosure, is shown.

[0074] The process begins at step

[0502] with the initiation of the counter reset scheduler by the Collector.

[0075] Step

[0504] - Collector Runs Scheduler: The Collector node runs a scheduler to send counter reset requests to network nodes at configured intervals, ensuring timely data collection. All instances connected to the NMS are distributed among available collector nodes. Each collector node sends counter reset requests in batches to the assigned instances, with configurable batch sizes and delays.

[0076] Step

[0506] - Collector Adds Request Details to IO Cache with FlowID: Each request sent by the Collector is logged in the IO Cache using a unique flowID. This helps in tracking and managing each request.

[0077] Step

[0508] - Node Sends PM Data to Configured Load Balancer of NMS: Upon receiving a counter reset request, the network node sends the corresponding PM data to the Load Balancer configured at the NMS end.

[0078] Step

[0510] - Load Balancer of NMS Distributes PM Data Between Configured Collectors: The Load Balancer forwards the PM data to one of the connected collector nodes using a round robin algorithm, ensuring even distribution and load balancing.

[0079] Step

[0512] - Collector Removes Request Details from IO Cache Using Received Data FlowID: The collector, upon receiving the PM data, uses the flowID to identify the corresponding request in the IO Cache and removes the entry, marking the request as completed.

[0080] Step

[0514] - Request Details Unremoved from IO Cache: Any unremoved entries in the IO Cache indicate PM data that was not received. These entries are utilized by the PM Auditor for auditing to ensure all data is collected accurately.

[0081] Step

[0516] - Collector Processes the PM Data by Adding Instance Metadata and Puts to Stream Category Wise: The collector processes the received PM data, adds relevant instance metadata, and categorizes the data before sending it to the stream, i.e., storage unit for further handling.

[0082] Step

[0518] - PM Node Polls Data from Stream in Batch Wise Manner: The PM node periodically polls data from the stream in batches. The polling interval and batch size are configurable based on the PM node’s processing capacity and database limitations.

[0083] Step

[0520] - PM Node Adds Data to a Queue Counter Wise: The polled data is then categorized and added to a queue based on counters. This ensures organized processing and queuing for storage.

[0084] Step

[0522] - Counter Data is Flushed to DB in Batches: Finally, the counter data is flushed to the Database in batches, where the DB is a secondary database. Both the batch size and the flush interval are configurable to optimize performance and storage efficiency.

[0085] In an exemplary scenario of the present solution, the following step-by-step procedure for fetching and processing of PM data may be followed:

[0086] In the first step, users can request various types of reports for a given duration. The system supports three main types of reports: All, Instance Select, and Bulk reports. The "All" report type allows users to generate a comprehensive report for all instances within a selected circle of a node. The "Instance Select" report type enables users to generate reports for specific instances of a node, offering detailed insights into selected parts of the network. The "Bulk" report type is designed for scenarios where users need reports for multiple instances; users can upload a sheet listing the required instances, and the system will generate the corresponding reports.

[0087] Once a report request is submitted, it is received by the PM node, which initiates the processing of the request. The system then notifies the user that the report generation has begun. To enhance efficiency and reduce processing time, multiple report requests are distributed among available PM nodes.

[0088] Upon completion of the report, it is automatically dumped to a predefined FTP path. The system updates the report status in the user interface (UI) to "completed," indicating that the report is ready for download. Users can download the completed report multiple times without the need for recalculating the data, providing convenience and saving processing resources.

[0089] The present disclosure may relate 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 to a collector node in the network, wherein the 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 in the network; on receiving the PM data from the network node, updating the PM data by adding an instance metadata; and transmitting the updated PM data to a storage unit.

[0090] The present disclosure further discloses a non-transitory computer readable storage medium storing instruction for managing performance data of a node in a network, the instructionsinclude executable code which, when executed by one or more units of a system, causes: a transceiver unit

[0202] of the system

[0200] 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

[0202] of the system

[0200] to receive, via a load balancer associated with at least one of the plurality of nodes, Performance Management (PM) data from said nodes, in response to the counter reset request. Further, the instructions include executable code which, when executed causes a processing unit

[0204] of the system

[0200] to update the PM data by adding an instance metadata. Further, the instructions include executable code which, when executed causes the transceiver unit

[0202] of the system

[0200] to further transmit the updated PM data to a storage unit

[0206] ,

[0091] As is evident from the above, the present disclosure provides a technically advanced solution for managing performance data of a node in a network. Firstly, the invention enables the retrieval of PM (Performance Management) data for all instances connected to the Network Management System (NMS). This feature significantly enhances the monitoring and analysis capabilities by providing a comprehensive view of performance across the network. Furthermore, the invention incorporates a storage mechanism with a hundred percent fault tolerance capacity for PM data. This ensures the reliability and durability of stored data, eliminating the risk of data loss or corruption. The invention's ability to maintain data integrity even in the face of failures is a significant technical achievement. The present solution also describes a horizontal scaling mechanism, which supports load distribution and parallel processing. This advancement enables the system to handle increasing workloads efficiently and effectively. It allows for the seamless expansion of the system's capacity by adding more resources, ensuring optimal performance even in high-demand scenarios. Additionally, the invention offers support for counter data reporting of selected instances within a provided time duration. This technical feature provides flexibility and granularity in data reporting, allowing users to focus on specific instances and analyse their performance over a defined period. It enhances the usability and relevance of the collected data, empowering users to gain valuable insights and make informed decisions.

[0092] In summary, the technical advancements have notable effects on the present invention. They enhance the comprehensiveness and accuracy of PM data retrieval, ensure fault-tolerant storage, facilitate efficient load distribution, and offer selective counter data reporting. These advancements collectively contribute to the invention's technical effectiveness and demonstrate its potential for significant impact in the field of network performance monitoring and management.

[0093] 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 be understood that the foregoing descriptive matter to be implemented is illustrative and non-limiting.

[0094] 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 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 functionality described herein, are considered to be encompassed within the scope of the present disclosure.

Claims

We Claim:

1. A method for managing performance data of a node in a network, the method comprising: transmitting, 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, by the transceiver unit [202], via a load balancer associated with at least one of the plurality of nodes, Performance Management (PM) data from said nodes; updating, by a processing unit [204], the PM data by adding an instance metadata; and transmitting, by the transceiver unit [202], the updated PM data to a storage unit [206],2. The method as claimed in claim 1, further comprising: configuring, by the processing unit [204], 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 as claimed in claim 1, further comprising: storing by a storage unit [206] 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 as claimed in claim 1, wherein the load balancer is configured to receive the 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 from the load balancer based on a round-robin selection mechanism implemented by the load balancer.

5. The method as claimed in claim 3, wherein upon receiving, by the transceiver unit [202], the 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 as claimed in claim 1, further comprising: storing the updated PM data, by the storage unit [206] via a PM node, into a secondary database, wherein the PM node is configured to poll the plurality of updated PM data from the storage unit [206] based on a configurable polling interval and batch size of the plurality of PM data.

7. A system for managing performance data of a node in a network, the system 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 from said nodes; a processing unit [204] connected to at least the transceiver unit [202] , wherein the processing unit [204] configured to: o update the PM data by adding an instance metadata; and the transceiver unit [202] configured to transmit the updated PM data to a storage unit [206],8. The system as claimed in claim 7, wherein the processing unit [204] is further 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 as claimed in claim 7, wherein a storage unit [206] 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 as claimed in claim 7, wherein the load balancer is to receive the 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 from at least one of the plurality of nodes based on a round-robin selection mechanism implemented by the load balancer.

11. The system as claimed in claim 9, wherein upon receiving the PM data from one of the plurality of nodes, the transceiver unit [202] is further configured to: remove the copy of stored counter reset request from the cache database.

12. The system as claimed in claim 7, wherein the storage unit [206] is further configured to:store the updated PM data, via a PM node, into a secondary database, wherein the PM node is configured to poll the plurality of PM data from the storage unit [206] based on a configurable polling interval and batch size of the plurality of PM data.

13. A network node compri sing : 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 to a collector node in the network, wherein the 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 in the network;■ on receiving the PM data from the network node, updating the PM data by adding an instance metadata; and■ transmitting the updated PM data to a storage unit.

14. A non-transitory computer-readable storage medium storing instructions for managing performance data of a node in a network, the instructions comprising executable code which, when executed by one or more units of a system [200], causes: a transceiver unit [202] of the system [200] to transmit a counter reset request to at least one of a plurality of nodes in the network; the transceiver unit [202] of the system [200] 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 from said nodes; a processing unit [204] of the system [200] to update the PM data by adding an instance metadata; and the transceiver unit [202] of the system [200] to transmit the updated PM data to a storage unit [206],

Images