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 FRONT END PARSING OF PERFORMANCE COUNTERS”
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 FRONT END PARSING OF PERFORMANCE COUNTERS
FIELD OF INVENTION
[0001] Embodiments of the present disclosure generally relate to network performance management systems. More particularly, embodiments of the present disclosure relate to methods and systems for front end parsing of performance counters for monitoring performance of network elements.
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] In order to ensure a good customer experience, it is essential to monitor the performance of the wireless network by monitoring the Key Performance Indicators (KPIs) to assess the quality of service related to various network elements in a network. A vendor may need to implement new software versions of various network elements based on the requirements given by service providers which may involve the addition of new counters. Generally, new counter families get introduced or get discontinued with changes in the software versions. This requirement of implementation of new software upgrades may occur frequently and may include the introduction of new counters either to fix bugs or enhance the existing features or to introduce some new feature(s). Further, new releases and new functionalities may be provided by the original equipment manufacturers, and the service provider may need to upgrade its services to be able to effectively monitor the performance of the new features through the newly introduced counters. For the implementation of these new versions of software(s) and the updating of the performance counters (i.e., performance management (PM) data) related with these new versions, that is in other words, for the accommodation of changes in the performance management (PM) data, costly adaptors need to be developed every time.
[0005] Thus, there exists an imperative need in the art to perform front end parsing of the PM counters for monitoring the performance of network elements overcoming the above concerns, 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 may relate to a method for front end parsing of performance counters for monitoring performance of network elements. The method comprises receiving, by a transceiver via a graphical user interface (GUI) from a user, a new performance counter file related to one or more network elements (NEs), for performing a software upgrade on the one or more NEs. Further, the method encompasses parsing automatically, by an Operations Support System (OSS), the new performance counter file. Further, the method encompasses identifying, by an identification unit, a set of new performance counters based on the parsing of the new performance counter file. Furthermore, the method comprises updating, by an updating unit, a north bound interface (NBI) unit, based on the set of new performance counters.
[0008] In an exemplary aspect of the present disclosure, prior to the receiving, by the transceiver, the new performance counter file related to the one or more NEs, the method comprises receiving, by the transceiver from a vendor element management system (vendor EMS), a performance data comprising one or more raw performance counters. Further the method comprises parsing automatically, by the OSS, the performance data. The method further comprises calculating, by a computation unit, a set of key performance indicators based at least on the parsed performance data.
[0009] In an exemplary aspect of the present disclosure, the identifying, by the identification unit, the set of new performance counters comprises calculating, by a computation unit, a set of key performance indicators based at least on the new performance counter file.
[0010] In an exemplary aspect of the present disclosure, wherein for updating the north bound interface (NBI) unit, the method comprises receiving, by the

transceiver via the GUI from the user, a selection related to one of: an enabling and a disabling of the one or more counters among the set of new performance counters, for updating the NBI unit. Further the method comprises updating, by the updating unit, the NBI unit based on the received selection related to one of: the enabling and the disabling, of the one or more counters among the set of new performance counters.
[0011] In an exemplary aspect of the present disclosure, the receiving, by the transceiver, the selection of the one or more counters, comprises receiving a selection related to at least one of a counter category, a counter group, and a sub-category information.
[0012] Another aspect of the present disclosure may relate to a system for front end parsing of performance counters for monitoring performance of network elements. The system comprises a transceiver that is configured to receive, via a graphical user interface (GUI) from a user, a new performance counter file related to one or more network elements (NEs), for performing a software upgrade on the one or more NEs. Further the system comprises an operations support system (OSS) that is connected to at least the transceiver, the OSS is configured to parse automatically, the new performance counter file. Further the system comprises an identification unit that is connected to at least the OSS, the identification unit is configured to identify a set of new performance counters based on the parsing of the new performance counter file. Furthermore, the system comprises an updating unit that is connected to at least the identification unit, the updating unit is configured to update a north bound interface (NBI) unit, based on the set of new performance counters.
[0013] Yet another aspect of the present disclosure may relate to a non-transitory computer readable storage medium storing instructions for front end parsing of performance counters for monitoring performance of network elements, the instructions include executable code which, when executed by one or more units of

a system, causes: a transceiver of the system to receive, via a graphical user interface (GUI) from a user, a new performance counter file related to one or more network elements; an operations support system (OSS) of the system to parse automatically, the new performance counter file; an identification unit of the system to identify a set of new performance counters based on the parsing of the new performance counter file; and an updating unit of the system to update a north bound interface (NBI) unit, based on the set of new performance counters.
[0014] Yet another aspect of the present disclosure may relate to a user equipment (UE) for enabling front end parsing of performance counters for monitoring performance of network elements. The UE comprises a processing unit configured to send to a system, via a graphical user interface (GUI) from a user, a new performance counter file related to one or more network elements (NEs), for performing a software upgrade on the one or more NEs. The operations support system (OSS) of the system is then configured to parse automatically, the new performance counter file received from the user equipment. The identification unit of the system is configured to identify a set of new performance counters based on the parsing of the new performance counter file; and the updating unit of the system is configured to update a north bound interface (NBI) unit, based on the set of new performance counters.
OBJECTS OF THE DISCLOSURE
[0015] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.
[0016] It is an object of the present disclosure to provide a system and a method for front end parsing of performance counters for monitoring performance of network elements.

[0017] It is another object of the present disclosure to provide a solution that saves time and cost involved in the development of adaptors needed for accommodating changes in the performance counter data or the data related to performance management of network elements. 5
[0018] It is yet another object of the present disclosure to provide a solution that tests the new software and functionalities immediately without loss of time.
DESCRIPTION OF THE DRAWINGS
10
[0019] 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,
15 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
20 drawings includes disclosure of electrical components or circuitry commonly used
to implement such components.
[0020] FIG. 1 illustrates an exemplary block diagram representation of 5th generation core (5GC) network architecture. 25
[0021] FIG. 2 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.
7

[0022] FIG. 3 illustrates an exemplary block diagram of a system for front end parsing of performance counters for monitoring performance of network elements, in accordance with exemplary implementations of the present disclosure.
5 [0023] FIG. 4 illustrates a method flow diagram for front end parsing of
performance counters for monitoring performance of network elements, in accordance with exemplary implementations of the present disclosure.
[0024] FIG. 5 illustrates an exemplary design flow for storing a counter information
10 in a database, in accordance with exemplary implementations of the present
disclosure.
[0025] FIG. 6 illustrates an exemplary method flow for creating a new version of
counters for a domain, a node, and a vendor, in accordance with exemplary
15 implementations of the present disclosure.
[0026] FIG. 7 shows a first exemplary user interface of a KPI editor showing a list of domains, technology, node, vendor, new software version, and previous software version, in accordance with exemplary implementations of the present disclosure. 20
[0027] FIG. 8 shows a second exemplary user interface a KPI editor for creating a new software version of counters for a domain, a node, and a vendor, in accordance with exemplary implementations of the present disclosure.
25 [0028] The foregoing shall be more apparent from the following more detailed
description of the disclosure.
DETAILED DESCRIPTION
30 [0029] In the following description, for the purposes of explanation, various
specific details are set forth in order to provide a thorough understanding of
8

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
5 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,
10 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.
15
[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
20 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
25 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.
30
9

[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
5 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
10 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
15 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
20 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.
25 [0035] As used herein, “a user equipment”, “a user device”, “a smart-user-device”,
“a smart-device”, “an electronic device”, “a mobile device”, “a handheld device”, “a wireless communication device”, “a mobile communication device”, “a communication device” may be any electrical, electronic and/or computing device or equipment, capable of implementing the features of the present disclosure. The
30 user equipment/device may include, but is not limited to, a mobile phone, smart
phone, laptop, a general-purpose computer, desktop, personal digital assistant,
10

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. 5
[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”),
10 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.
15 [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 more modules or one or more units with each other, which also includes the methods, functions, or procedures that may be
20 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,
25 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.
30 [0039] As used herein the transceiver unit or transceiver include at least one
receiver and at least one transmitter configured respectively for receiving and
11

transmitting data, signals, information or a combination thereof between units/components within the system and/or connected with the system.
[0040] Further, in accordance with the present disclosure, it is to be acknowledged
5 that the functionality described for the various the 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.
15 [0041] As discussed in the background section, the current known solutions have
several shortcomings. The present disclosure aims to overcome the above-mentioned and other existing problems in this field of technology by providing method and system of front-end parsing of one or more performance counters for monitoring performance of network elements (NEs). Based on the implementation
20 of the present solution there is no need for developing an adaptor interface every
time when an original equipment manufacturer (OEM) brings a new software version which involves introduction of new counters. The present disclosure further saves the cost of development of adapters and time. Furthermore, the present disclosure saves time of adopting to the changes in performance counters and makes
25 the system ready to monitor new functionalities and features introduced in the new
software versions instantly.
[0042] Particularly, in the present solution performance data in the form of raw
counters is periodically collected from the element management systems (EMSs)
30 of various vendors and the performance data is then parsed. Further, one or more
Key performance metrics are derived by defining formula with one or more
12

counters along with some mathematical operations. In an implementation, these key
performance metrics may be defined by an admin user using a KPI Editor which is
a front-end mechanism through which the admin users can define the key
performance metrics using the raw counters which are visible in a graphical user
5 interface (GUI). Further, a new performance counter file is received for performing
software upgrade on one or more network elements (NEs). This new performance
counter file is parsed automatically, and a set of new performance counters is
identified, and all counters are displayed for the user to select. The user can enable
or disable counter(s) as required to support the new Software Version in no time
10 with zero development efforts. Also, a north bound interface (NBI) is updated based
on the set of new performance counters for monitoring performance of the network element(s) of a communication network.
[0043] Furthermore, the communication network may include but is not limited to
15 a 5th generation network, where based on the implementation of features of the
present disclosure a front-end parsing of performance counters for monitoring performance of network function(s) / network element(s) is provided. Further, an exemplary block diagram representation of 5th generation core (5GC) network architecture is shown in FIG. 1, in accordance with exemplary implementation of
20 the present disclosure. As shown in figure 1, the 5GC network architecture [100]
includes a user equipment (UE) [102], a radio access network (RAN) [104], an access and mobility management function (AMF) [106], a Session Management Function (SMF) [108], a Service Communication Proxy (SCP) [110], an Authentication Server Function (AUSF) [112], a Network Slice Specific
25 Authentication and Authorization Function (NSSAAF) [114], a Network Slice
Selection Function (NSSF) [116], a Network Exposure Function (NEF) [118], a Network Repository Function (NRF) [120], a Policy Control Function (PCF) [122], a Unified Data Management (UDM) [124], an application function (AF) [126], a User Plane Function (UPF) [128], a data network (DN) [130], wherein all the
30 components are assumed to be connected to each other in a manner as obvious to
the person skilled in the art for implementing features of the present disclosure.
13

[0044] Radio Access Network (RAN) [104] is the part of a mobile
telecommunications system that connects user equipment (UE) [102] to the core
network (CN) and provides access to different types of networks (e.g., 5G network).
5 It consists of radio base stations and the radio access technologies that enable
wireless communication.
[0045] Access and Mobility Management Function (AMF) [106] is a 5G core
network function responsible for managing access and mobility aspects, such as UE
10 registration, connection, and reachability. It also handles mobility management
procedures like handovers and paging.
[0046] Session Management Function (SMF) [108] is a 5G core network function
responsible for managing session-related aspects, such as establishing, modifying,
15 and releasing sessions. It coordinates with the User Plane Function (UPF) for data
forwarding and handles IP address allocation and QoS enforcement.
[0047] Service Communication Proxy (SCP) [110] is a network function in the 5G
core network that facilitates communication between other network functions by
20 providing a secure and efficient messaging service. It acts as a mediator for service-
based interfaces.
[0048] Authentication Server Function (AUSF) [112] is a network function in the
5G core responsible for authenticating UEs during registration and providing
25 security services. It generates and verifies authentication vectors and tokens.
[0049] Network Slice Specific Authentication and Authorization Function
(NSSAAF) [114] is a network function that provides authentication and
authorization services specific to network slices. It ensures that UEs can access only
30 the slices for which they are authorized.
14

[0050] Network Slice Selection Function (NSSF) [116] is a network function responsible for selecting the appropriate network slice for a UE based on factors such as subscription, requested services, and network policies.
5 [0051] Network Exposure Function (NEF) [118] is a network function that exposes
capabilities and services of the 5G network to external applications, enabling integration with third-party services and applications.
[0052] Network Repository Function (NRF) [120] is a network function that acts
10 as a central repository for information about available network functions and
services. It facilitates the discovery and dynamic registration of network functions.
[0053] Policy Control Function (PCF) [122] is a network function responsible for
policy control decisions, such as QoS, charging, and access control, based on
15 subscriber information and network policies.
[0054] Unified Data Management (UDM) [124] is a network function that centralizes the management of subscriber data, including authentication, authorization, and subscription information. 20
[0055] Application Function (AF) [126] is a network function that represents external applications interfacing with the 5G core network to access network capabilities and services.
25 [0056] User Plane Function (UPF) [128] is a network function responsible for
handling user data traffic, including packet routing, forwarding, and QoS enforcement.
[0057] Data Network (DN) [130] refers to a network that provides data services to
30 user equipment (UE) in a telecommunications system. The data services may
include but are not limited to Internet services, private data network related services.
15

[0058] Further referring to FIG. 2 that illustrates an exemplary block diagram of a
computing device [200] (or as used herein, computer system [200]) upon which the
features of the present disclosure may be implemented in accordance with
exemplary implementation of the present disclosure. The computing device [200]
5 is in communication with a communication network and in an implementation, the
computing device [200] implements a method for front end parsing of performance
counter(s) for monitoring performance of one or more network elements of the
communication network, by utilising a system [300]. In another implementation,
the computing device [200] itself implements the method for front end parsing of
10 performance counter(s) for monitoring performance of network elements using one
or more units (e.g., a processor etc.) configured within the computing device [200], wherein a person skilled in the art would appreciate that said one or more units are capable of implementing the features as disclosed in the present disclosure.
15 [0059] The computing device [200] may include a bus [202] or other communication
mechanism for communicating information, and a hardware processor [204] coupled with bus [202] for processing information. The hardware processor [204] may be, for example, a general-purpose microprocessor. The computing device [200] may also include a main memory [206], such as a random-access memory (RAM), or other dynamic storage device,
20 coupled to the bus [202] for storing information and instructions to be executed by the
processor [204]. The main memory [206] also may be used for storing temporary variables or other intermediate information during execution of the instructions to be executed by the processor [204]. Such instructions, when stored in non-transitory storage media accessible to the processor [204], render the computing device [200] into a special-purpose machine
25 that is customized to perform the operations specified in the instructions. The computing
device [200] further includes a read only memory (ROM) [208] or other static storage device coupled to the bus [202] for storing static information and instructions for the processor [204].
30 [0060] A storage device [210], such as a magnetic disk, optical disk, or solid-state drive
is provided and coupled to the bus [202] for storing information and instructions. The computing device [200] may be coupled via the bus [202] to a display [212], such as a
16

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 [214], including alphanumeric and other keys, touch screen input means,
etc. may be coupled to the bus [202] for communicating information and command
5 selections to the processor [204]. Another type of user input device may be a cursor
controller [216], such as a mouse, a trackball, or cursor direction keys, for communicating
direction information and command selections to the processor [204], and for controlling
cursor movement on the display [212]. 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
10 to specify positions in a plane.
[0061] The computing device [200] 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 [200] causes or programs the computing
15 device [200] to be a special-purpose machine. According to one implementation, the
techniques herein are performed by the computing device [200] in response to the processor [204] executing one or more sequences of one or more instructions contained in the main memory [206]. Such instructions may be read into the main memory [206] from another storage medium, such as the storage device [210]. Execution of the sequences of
20 instructions contained in the main memory [206] causes the processor [204] 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.
[0062] The computing device [200] also may include a communication interface [218]
25 coupled to the bus [202]. The communication interface [218] provides a two-way data
communication coupling to a network link [220] that is connected to a local network [222].
For example, the communication interface [218] 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,
30 the communication interface [218] may be a local area network (LAN) card to provide a
data communication connection to a compatible LAN. Wireless links may also be implemented. In any such implementation, the communication interface [218] sends and
17

receives electrical, electromagnetic or optical signals that carry digital data streams representing various types of information.
[0063] The computing device [200] can send messages and receive data, including
5 program code, through the network(s), the network link [220] and the communication
interface [218]. In the Internet example, a server [230] might transmit a requested code for
an application program through the Internet [228], the ISP [226226], the local network
[222], the host [224], and the communication interface [218]. The received code may be
executed by the processor [204] as it is received, and/or stored in the storage device [210],
10 or other non-volatile storage for later execution.
[0064] Further, referring to FIG. 3, an exemplary block diagram of a system [300] for front end parsing of one or more performance counters for monitoring performance of one or more network elements, is shown, in accordance with the
15 exemplary implementations of the present disclosure. The system [300] comprises
at least one transceiver [302], at least one operation support system [304], at least one identification unit [306], at least one updating unit [308], and at least one computation unit [310]. Also, all of the components/ units of the system [300] are assumed to be connected to each other unless otherwise indicated below. Also, in
20 Figure 3 only a few units are shown, however, the system [300] may comprise
multiple such units or the system [300] may comprise any such numbers of said units, as required to implement the features of the present disclosure. Further, in an implementation, the system [300] may be present in a user device/ user equipment [102] to implement the features of the present disclosure. In another
25 implementation, the system [300] may reside in a server or a network entity.
[0065] The system [300] is configured for the front-end parsing of the one or more
performance counters for monitoring the performance of the one or more network
elements, with the help of the interconnection between the components/units of the
30 system [300]. The front-end parsing of the one or more performance counters
comprises an updation of a north bound interface (NBI) unit based on a set of new performance counters. The system [300] therefore is configured for updating the
18

NBI unit for monitoring the performance of the one or more network elements. The NBI unit is a unit that allows one or more components (i.e., the one or more network elements) of a communication network to communicate with one or more higher-level components. 5
[0066] Particularly, when an original equipment manufacturer (OEM) provides
new releases and new functionalities to some components in the communication
network, the service provider needs to upgrade the adaptors to be able to effectively
monitor the performance of the new features through the newly introduced
10 counters. These newly introduced counters may be part of the new releases and new
functionalities that have been added/provided to the components by the OEM.
Further, since the NBI unit enables the protocol-supported communication between
the component(s) and applications or other higher-layer control programs (i.e., the
NBI unit is the interface that lets a specific component communicate with a higher-
15 level component in the same network), the NBI unit needs to be upgraded with the
new functionalities that the OEM has introduced for the components of the network
elements. That is, the NBI has to be upgraded with new set of adaptors to parse the
newly introduced performance counters.
20 [0067] More particularly, for the updation of the north bound interface (NBI) unit,
initially the transceiver [302] is configured to receive, via a graphical user interface (GUI) from a user, a new performance counter file related to one or more network elements (NEs), for performing a software upgrade on the one or more NEs. The graphical user interface (GUI) may be a digital interface through which the user
25 interacts with one or more electronic devices, one or more applications, and/or one
or more service, wherein such interaction is achieved using one or more graphical elements as per the requirements. Here, the new performance counter file may include information related to one or more performance counters, where said information may provide details relating to the performance of the one or more
30 network elements. The one or more network elements are one or more components
of the communication network, and the one or more network elements are
19

associated with at least one of an operating system, an application, a service and/or
a driver etc. Further the performance counter helps in finding the bottleneck of the
one or more NEs of the communication network, and in fine tuning the
communication network and performance of its network element(s). These
5 performance counters may be used to measure key performance metrics, key
performance indicators (KPIs) such as, but not limited to, throughput, delay, jitter, reference signal received power (RSRP), reference signal received quality (RSRQ), signal to Interference & Noise Ratio (SINR), etc. In an implementation, the transceiver [302], prior to receiving the new performance counter file related to the
10 one or more NEs, is configured to receive from a vendor element management
system (vendor EMS, that is, the entity for managing the network element(s) within the communication network), a performance data comprising one or more raw performance counters. In this implementation, after receiving the performance data, the operation support system (OSS) [304] is configured to parse automatically, the
15 performance data. Further in this implementation, the computation unit [310] is
configured to calculate a set of key performance indicators (KPIs) based at least on the parsed performance data. The key performance indicators are the benchmark on basis of which the optimal network performance is determined. It displays how well the network is serving to its user(s). The purpose of calculating these KPIs using
20 the one or more raw performance counters is to monitor the performance for the
end user.
[0068] Once the transceiver [302] receives the new performance counter file for performing the software upgrade on the one or more NEs, thereafter the operations
25 support system (OSS) [304] connected to the transceiver [302] is configured to
parse automatically, the new performance counter file. That is, once the new performance counter file is provided to the transceiver [302] of the system [300], it is parsed automatically to read the counters in the file. Also, in an implementation, the new performance counter file is uploaded via a user interface and received by
30 the system [300] at the transceiver [302]. The parsing may be performed via one or
more known parsing techniques.
20

[0069] Further, the identification unit [306], connected to the OSS [304], is
configured to identify a set of new performance counters based on the parsing of
the new performance counter file. In an implementation, the computation unit
5 [310], post the identification unit [306] identifying the set of new performance
counters, may calculate a set of key performance indicators based at least on the new performance counter file.
[0070] Furthermore, the updating unit [308], connected to at least the identification
10 unit [306], is configured to update the north bound interface (NBI) unit, based on
the set of new performance counters. More specifically, in an implementation, for updating by the updating unit [308], the north bound interface (NBI) unit, the GUI may display the set of new performance counters from that new performance counter file. Further, the transceiver [302] is configured to receive, via the GUI
15 from the user, a selection related to one of an enabling and a disabling of the one or
more counters among the set of new performance counters, for updating the NBI unit. This selection, in an implementation, is related to selecting at least one of a counter category, a counter group, and a sub-category information. For example, a counter category may be data traffic, a counter group may be uplink data traffic and
20 downlink data traffic in the data traffic may be, and a sub-category information may
be voice data, video data, etc. Thus, these may be useful for allocation of resources for the users when needed. The updating unit [308] is further configured to update the NBI unit based on the received selection related to one of the enabling and the disabling, of the one or more counters among the set of new performance counters.
25 In other words, a user (i.e., the admin user) can upload a new sample PM Counter
file using the GUI and the file is automatically parsed by the system [300]. As a result, all the counters are displayed for the user to select. Further, the user can enable or disable the counters as required and the platform (i.e., the network element) gets ready to support the new Software Version.
30
21

[0071] Referring to FIG. 4, an exemplary method flow diagram [400] for front end
parsing of one or more performance counters for monitoring performance of one or
more network elements, in accordance with exemplary implementations of the
present disclosure is shown. In an implementation the method [400] is performed
5 by the system [300]. Further, in an implementation, the system [300] may be present
in a server device to implement the features of the present disclosure. Also, as shown in Figure 4, the method [400] starts at step [402].
[0072] The front-end parsing of the one or more performance counters comprises
10 an updating of a north bound interface (NBI) unit based on a set of new performance
counters. The system [300] therefore is configured for updating the NBI unit for
monitoring the performance of the one or more network elements. The NBI unit is
a unit that allows one or more components (i.e., the one or more network elements)
of a communication network to communicate with one or more higher-level
15 components.
[0073] Particularly, when an original equipment manufacturer (OEM) provides new releases and new functionalities to some components in the communication network, the service provider needs to upgrade the adaptors to be able to effectively
20 monitor the performance of the new features through the newly introduced
counters. These newly introduced counters may be part of the new releases and new functionalities that have been added/provided to the components by the OEM. Further, since the NBI unit enables the protocol-supported communication between a controller the component(s) and applications or other higher-layer control
25 programs, (i.e., the NBI unit is the interface that lets a specific component
communicate with a higher-level component in the same network), the NBI unit needs to be upgraded with the new functionalities that the OEM has introduced for the components of the network elements. That is, the NBI has to be upgraded with new set of adaptors to parse the newly introduced performance counters.
30
22

[0074] At step [402], the method comprises receiving, by a transceiver [302] via a
graphical user interface (GUI) from a user, a new performance counter file related
to one or more network elements (NEs), for performing a software upgrade on the
one or more NEs. The graphical user interface (GUI) may be a digital interface in
5 through which the user interacts with the one or more electronic devices, one or
more applications, and/or one or more service, wherein such interaction is achieved using the one or more graphical elements as per the requirements. Here, the new performance counter may include information related to the one or more performance counters, where the said information may provide detail relating to the
10 performance of the one or more network elements. The one or more network
elements are one or more components of the communication network and the one or more network elements associated with at least one of the operating system an application, a service and/or a driver etc. Further the performance counter helps in finding the bottleneck of the one or more NEs of the communication network and
15 in fine tuning the communication network and performance of its network
element(s). These performance counters may be used to measure key performance metrics, key performance indicators (KPIs) such as, but not limited to, throughput, delay, jitter, reference signal received power (RSRP), reference signal received quality (RSRQ), signal to Interference & Noise Ratio (SINR), etc. In an
20 implementation, prior to the receiving, by the transceiver [302], the new
performance counter file related to the one or more NEs, the method comprises receiving, by the transceiver [302] from a vendor element management system (vendor EMS, that is, the entity for managing the network element(s) within the communication network), a performance data comprising one or more raw
25 performance counters. In this implementation, after receiving the performance data,
the method further comprises parsing automatically, by the OSS [304], the performance data. Further in this implementation, the method further comprises calculating, by a computation unit [310], a set of key performance indicators based at least on the parsed performance data. The key performance indicators are the
30 benchmark on basis of which the optimal network performance is determined. It
displays how well the networking is serving to its user(s).
23

[0075] Once the transceiver [302] receives the new performance counter file for
performing the software upgrade on the one or more NEs, the method at step 404
comprises parsing automatically, by an Operations Support System (OSS) [304],
5 the new performance counter file. That is, once the new performance counter file is
provided to the transceiver [302] of the system [300], it is parsed automatically to
read the counters in the file. Also, in an implementation, the new performance
counter file is uploaded via a user interface and received by the system [300] at the
transceiver [302]. The parsing may be performed via one or more known parsing
10 techniques.
[0076] Further, at step 406, the method comprises identifying, by an identification
unit [306], a set of new performance counters based on the parsing of the new
performance counter file. In an implementation, this identifying may also comprise
15 calculating, by a computation unit [310], a set of key performance indicators based
at least on the new performance counter file.
[0077] Furthermore, at step 408, the method comprises updating, by an updating unit [308], a north bound interface (NBI) unit, based on the set of new performance
20 counters. More specifically, in an implementation, the updating unit [308] for
updating the north bound interface (NBI) unit, the GUI may display the set of new performance counters from that new performance counter file. Further, in this implementation, the transceiver [302] may receive, via the GUI from a user, a selection related to the one of an enabling and a disabling of the one or more
25 counters among the set of new performance counters, for updating the NBI unit.
This selection, in an implementation, is related to selecting at least one of a counter category, a counter group, and a sub-category information. Further, in this implementation, the updating unit [308] may update the NBI unit based on the received selection related to one of an enabling and a disabling, of the one or more
30 counters among the set of new performance counters. In other words, a user (i.e.,
the admin user) can upload a new sample PM Counter file using the GUI and the
24

file is automatically parsed by the system [300]. As a result, all the counters are displayed for the user to select. Further, the user can enable or disable the counters as required and the platform (i.e., the network element) gets ready to support the new Software Version.
[0078] Referring to FIG. 5 which illustrates an exemplary design flow [500] for storing a counter information in a database, in accordance with exemplary implementations of the present disclosure. As show in FIG. 5, at an application server [502], a set of raw file(s) are uploaded for storing the counters for auto-parsing. Further, a set of microservice(s) [504] is used to create and/or update counters. Further, the set of microservice(s) [504] may store a counter information in a database [506]. With this, the counters are available for a key performance indicator (KPI) editor, which an authenticated user may be able to access.
[0079] Referring to FIG. 6 which illustrates an exemplary method flow [600] for creating a new version of counters for a domain, a node, and a vendor using a KPI editor, in accordance with exemplary implementations of the present disclosure. In an implementation, the node vendor is a performance management (PM) node vendor. As show in FIG. 6, a request for creating a new software version for a node vendor is created (refer step 602). This may be done via a representational state transfer (REST) protocol implementation. Further, a new software version creation response is returned at step 604 in response to the create request of step 602, as service implementation by creating/ adding the new software version for the node vendor. Further, at step 606, a node vendor version entry is updated with the software version for a node vendor as a data access object implementation. Further, at step 608, an update of version is performed for all categories of counters for which a new software version for the node vendor is added at step 604. Further, at step 610, an update of version is performed for all counters for which a new software version for a node vendor is added at step 604. Further, at step 612, an update of version is performed for a node vendor in a database maintaining the PM counters. Further, at step 614, an update of version is performed for PM categories

in the database maintaining the PM counters. Further, at step 616, an update of version is performed for KPI counters in the database maintaining the PM counters. An exemplary user interface [700] of the KPI editor showing a list comprising various heads such as domain, technology, node, vendor, new software version, and previous software version is shown in FIG. 7. Further, an exemplary user interface [800] for creating a new software version of counters for a domain, a node, and a vendor using a KPI editor is shown in FIG. 8. A person skilled in the art would appreciate that the explanation with reference to FIG. 6, and FIG. 7 and FIG. 8 are provided for understanding purposes only, and do not limit or restrict the present disclosure in any possible manner.
[0080] The present disclosure further discloses a non-transitory computer readable storage medium storing instructions for front end parsing of performance counters for monitoring performance of network elements, the instructions include executable code which, when executed by one or more units of a system, causes: a transceiver [302] of the system to receive, via a graphical user interface (GUI) from a user, a new performance counter file related to one or more network elements; an operations support system (OSS) [304] of the system to parse automatically, the new performance counter file; an identification unit [306] of the system to identify a set of new performance counters based on the parsing of the new performance counter file; and an updating unit [308] of the system to update a north bound interface (NBI) unit, based on the set of new performance counters.
[0081] The present disclosure further discloses a user equipment (UE) for enabling front end parsing of performance counters for monitoring performance of network elements. The UE comprises a processing unit configured to send to a system [300], via a graphical user interface (GUI) from a user, a new performance counter file related to one or more network elements (NEs), for performing a software upgrade on the one or more NEs. The operations support system (OSS) [304] of the system [300] is then configured to parse automatically, the new performance counter file received from the user equipment. The identification unit [306] of the system [300]

is configured to identify a set of new performance counters based on the parsing of the new performance counter file; and the updating unit [308] of the system [300] is configured to update a north bound interface (NBI) unit, based on the set of new performance counters.
[0082] As is evident from the above, the present disclosure provides a technically advanced solution for front end parsing of performance counters for monitoring performance of network elements. The present solution provides that there is no need for developing an adaptor interface every time when an OEM brings a new software version involving introduction of new counters. The present disclosure further saves the cost of development of adapters and time. Furthermore, the present disclosure saves time of adopting to the changes in performance counters and in monitoring new functionalities and features introduced in the new software versions. Also, the present disclosure tests the new software and functionalities immediately without loss of time. This disclosure can be adopted for any domain, not only for RAN but also for Core nodes, FTTX etc. In addition, it supports any technology like 4G, 5G, 6G etc. and is vendor agnostic. By this implementation strategy, there is no need for developing an adaptor interface every time an OEM brings a new Software Version which involves introduction of new counters, thereby saving a lot of time and efforts, as well as development costs.
[0083] 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.

We Claim:
1. A method [400] for front end parsing of performance counters for
monitoring performance of network elements, the method [400]
comprising:
- receiving, by a transceiver [302] via a graphical user interface (GUI) from a user, a new performance counter file related to one or more network elements (NEs), for performing a software upgrade on the one or more NEs;
- parsing automatically, by an Operations Support System (OSS) [304], the new performance counter file;
- identifying, by an identification unit [306], a set of new performance counters based on the parsing of the new performance counter file; and
- updating, by an updating unit [308], a north bound interface (NBI) unit, based on the set of new performance counters.
2. The method [400] as claimed in claim 1, wherein prior to the receiving, by
the transceiver [302], the new performance counter file related to the one or
more NEs, the method comprises:
- receiving, by the transceiver [302] from a vendor element management system (vendor EMS), a performance data comprising one or more raw performance counters;
- parsing automatically, by the OSS [304], the performance data; and
- calculating, by a computation unit [310], a set of key performance indicators based at least on the parsed performance data.
3. The method [400] as claimed in claim 1, wherein the identifying, by the
identification unit [306], the set of new performance counters comprises:
- calculating, by a computation unit [310], a set of key performance
indicators based at least on the new performance counter file.

4. The method [400] as claimed in claim 1, wherein for updating the north
bound interface (NBI) unit, the method comprises:
- displaying, by the GUI, the set of new performance counters;
- receiving, by the transceiver [302] via the GUI from the user, a selection related to one of: an enabling and a disabling of the one or more counters among the set of new performance counters, for updating the NBI unit; and
- updating, by the updating unit [308], the NBI unit based on the received selection related to one of: the enabling and the disabling, of the one or more counters among the set of new performance counters.

5. The method [400] as claimed in claim 4, wherein the receiving, by the transceiver [302], the selection of the one or more counters, comprises receiving a selection related to at least one of a counter category, a counter group, and a sub-category information.
6. A system [300] for front end parsing of performance counters for monitoring performance of network elements, the system [300] comprising:

- a transceiver [302] configured to receive, via a graphical user interface (GUI) from a user, a new performance counter file related to one or more network elements (NEs), for performing a software upgrade on the one or more NEs;
- an operations support system (OSS) [304] connected to at least the transceiver [302], the OSS [304] configured to parse automatically, the new performance counter file;
- an identification unit [306] connected to at least the OSS [304], the identification unit [306] configured to identify a set of new performance counters based on the parsing of the new performance counter file; and
- an updating unit [308] connected to at least the identification unit [306], the updating unit [308] configured to update a north bound interface (NBI) unit, based on the set of new performance counters.

7. The system [300] as claimed in claim 6, wherein prior to the transceiver
[302] receiving the new performance counter file related to the one or more
NEs:
- the transceiver [302] is configured to receive, from a vendor element management system (vendor EMS), a performance data comprising one or more raw performance counters;
- the OSS [304] is configured to parse automatically, the performance data; and
- a computation unit [310] is configured to calculate a set of key performance indicators based at least on the parsed performance data.
8. The system [300] as claimed in claim 6, wherein the system comprises a
computation unit [310], where post the identification unit [306] identifying
the set of new performance counters, the computation unit [310] is
configured to:
- calculate a set of key performance indicators based at least on the new
performance counter file.
9. The system [300] as claimed in claim 6, wherein for updating by the
updating unit [308], the north bound interface (NBI) unit:
- the GUI is configured to display the set of new performance counters;
- the transceiver [302] is configured to receive, via the GUI from the user, a selection related to one of: an enabling and a disabling of the one or more counters among the set of new performance counters, for updating the NBI unit; and
- the updating unit [308] is configured to update the NBI unit based on the received selection related to one of: the enabling and the disabling, of the one or more counters among the set of new performance counters.

10. The system [300] as claimed in claim 9, wherein while receiving the selection of the one or more counters, the transceiver [302] is configured to receive a selection related to at least one of a counter category, a counter group, and a sub-category information.
11. A user equipment (UE) for enabling front end parsing of performance counters for monitoring performance of network elements of a communication network, the UE comprising:
- a processing unit configured to send to a system [300], via a graphical user interface (GUI) from a user, a new performance counter file related to one or more network elements (NEs), for performing a software upgrade on the one or more NEs, wherein
o an operations support system (OSS) [304] of the system [300] is configured to parse automatically, the new performance counter file; o an identification unit [306] of the system [300] is configured to identify a set of new performance counters based on the parsing of the new performance counter file; and o an updating unit [308] of the system [300] is configured to update a north bound interface (NBI) unit, based on the set of new performance counters.